Server Upgrade

To validate the authenticity and integrity of the Debian and the RPMClosedFile format for software package distributed by RPM Package Manager package, refer to Validating Debian and RPM Packages.

Server Upgrade Quickstart

  1. Check and execute the Server Pre-upgrade steps.
  2. Upgrade:
  3. Check and execute the Server Post-Upgrade steps.
  4. Restart the EKMClosedEnterprise Key Management - previous name of the product. Service (refer to EKM Service Management).
  5. Note
    The EKMClosedEnterprise Key Management - previous name of the product. service restart shall, as needed, migrate the CORE Data Base to the enhanced schema specified by the new release. It is a one-time procedure that may result in a longer restart time.

  6. Test the upgraded system by running the ucl server test command.
  7. Note
    If you run the command while the upgraded server is engaged in the EKMClosedEnterprise Key Management - previous name of the product. service restart, the server shall appear as "unreachable". Wait and repeat the command. As needed, proceed to Server Upgrade Troubleshooting.

Server Pre-upgrade

Before upgrading CORE server software, save custom changes you made in the listed files that are overwritten during the upgrade.

Server Post-Upgrade

The post-upgrade may require multiple steps if there is a significant gap between your previous and the new releases. The following table summarizes the required procedures. To use this table:

  1. Select the Upgrading from Release ... and follow the instructions specified in the Upgrade to Release ...
  2. Once this step is finished, continue the same procedure, starting from the release in Upgrade to Release ...

For example, to upgrade from 2.0.1904 to 2.0.2010, you will have to perform procedures specified in Post-upgrade to 2.0.1907, Post-upgrade to 2.0.2001, and Post-upgrade to 2.0.2007.

Upgrading from Release ... Upgrade to Release ... Requirement
2.0.1806 or earlier Post-upgrade to 2.0.1807 As needed
2.0.1807 or earlier Server Upgrade Mandatory
2.0.1904 or earlier Post-upgrade to 2.0.1907 Mandatory
2.0.1910 or earlier Post-upgrade to 2.0.2001 As needed
2.0.2004 or earlier Post-upgrade to 2.0.2007 Mandatory

Post-upgrade to 2.0.1807

Post-upgrade to 2.0.1808

Post-upgrade to 2.0.1907

Post-upgrade to 2.0.2001

Post-upgrade to 2.0.2007

Server Upgrade Troubleshooting

  1. Restart the server and repeat the ucl server test from EP1.
  2. If the "server unreachable" problem remains:
    1. Examine Tomcat Logs on the unreachable server.
    2. If it does not reveal a reasonable cause, proceed to repair the upgrade