This article describes how to upgrade Smart ID Certificate Manager to the latest version. For all other upgrade paths, contact Nexus.
...
| Note |
|---|
8.4.0 was replaced by 8.4.1. For more information, see Release note Certificate Manager 8.4.1. |
Prerequisites
...
To upgrade the CMDB (Certificate Manager Database), run the appropriate script in the MSSQL Server Management Studio, MySQL client, Oracle SQLPlus, or PostgreSQL client.
Verify that no errors occurred.
Database | Script | Comment |
|---|
MSSQL | database/CMDBUpgrade_MSSQL_x_x_x.sql | The following applies: If there are no scripts included in the release bundle, go to the next step in this upgrade instruction (Upgrade Certificate Manager services). If there are scripts included in the release bundle, run all included scripts.
|
MySQL | database/CMDBUpgrade_MySQL_x_x_x.sql |
Oracle | database/CMDBUpgrade_Oracle_x_x_x.sql |
PostgreSQL | database/CMDBUpgrade_PostgreSQL_x_x_x.sql |
MariaDB | database/CMDBUpgrade_MariaDB_x_x_x.sql | Starting from 8.2.x to 8.3.0, you must run the database script for MariaDB. |
AzureSQL | database/CMDBUpgrade_AzureSQL_x_x_x.sql | Starting from 8.6.x to 8.7.0, you must run the database script for AzureSQL. |
2. Upgrade Certificate Manager services
...
| Expand |
|---|
|
Make a backup copy of these folders before applying any changes: <cm-server-home>/config <cm-server-home>/lib
On the server(s) running the Nexus CF, Nexus CIS or Nexus SNMP services: Do the configuration changes in <cm-server-home>/config/ described in the respective files under the <server> folder.
Note the important changes described in the file changes-formats.txt. The file is located here: <Upgrade\Upgrade from CM 8.0.x to 8.1.0\server>. The tool used in changes-formats.txt requires updated lib files. Therefore those instructions should be executed after the new jar files has been replace in the final upgrade instruction. From Upgrade files CM 8.1.0/server/inputviews, add the following files to <cm-server-home>/inputviews, or replace if any of these files already exist:
|
...
| Expand |
|---|
|
Do the following: Shut down all the Certificate Manager clients. Make sure Java SE 17 is installed and set as default Java on the system. Certificate Manager clients can be run on both 32-bit and 64-bit JDKs with the following limitations: Linux:
64-bit Java is required in order to use clients with Personal. Windows:
After the upgrade, if a javaw.exe binary exists under the C:\Windows\SysWOW64 folder, clients will continue to run on 32-bit Java even if default JDK is 64-bit. Remove this binary (and javaws.exe, java.exe) in order to run the clients on 64-bit Java.
Backup the <cm-client-home>/config folder. Uninstall the Certificate Manager clients components, see Uninstall Certificate Manager server components and clients. On Windows use "Programs and Features" to uninstall "Certificate Manager Clients Components". On Linux, run <cm-client-home>/install/setup.sh -u.
Remove any remaining hotfix jar files in the <cm-client-home>/lib folder. On Linux, if there is a <cm-client-home>/P11 folder, backup any config file with customizations to Personal Desktop Client and then delete the folder.
Install the new version of the clients, included in the delivery of Certificate Manager. Apply any customizations to the new configuration files in the <cm-client-home>/config folder.
The officer role "Use AWB" is now used for read-only access to the AWB and no longer has permission to do manual builds of CRLs and CILs. Instead, the role "Manual build of CRL and CIL" is needed to perform manual builds. The officer profile that was previously used by the officer that performed manual builds must now be modified to include the role "Manual build of CRL and CIL". |
4. Upgrade Certificate Manager Protocol Gateway
See Upgrade Protocol Gateway.
...
