Performing a direct upgrade from v 9.5.0.x or v 10.x.x to v 10.2.2

Detailed steps to perform a direct upgrade from version 9.5.0.x or v 10.x.x to version 10.2.2

To upgrade your environment using a direct upgrade procedure, perform the following steps:
  1. Converting default certificates, if you are using default certificates in your current environment. Use this procedure to convert the certificates from the .jks to the .pem format, then copy them to the workstations where you plan to install the server components (dynamic domain manager and its backups, master domain manager and its backups) and the Dynamic Workload Console.
    Certificates are now required when installing or upgrading HCL Workload Automation. You can no longer install nor upgrade HCL Workload Automation without securing your environment with certificates. The required certificates are:
    • ca.crt
    • tls.key
    • tls.crt
    For UNIX systems, ensure that all the files have the ownership of the user who installed the master domain manager and the correct permissions (644).
  2. Upgrading WebSphere Application Server Liberty on the workstations hosting Dynamic Workload Console and the server components (dynamic domain manager and its backups, master domain manager and its backups)
  3. Performing a direct upgrade of the Dynamic Workload Console and its database
  4. Performing a direct upgrade of the dynamic domain manager, its backups, and their database
  5. Performing a direct upgrade of the backup master domain manager and its database
    1. Switching the master domain manager to the upgraded backup master
    2. Making the switch permanent
  6. Performing a direct upgrade of the master domain manager
    1. Switching back to the master domain manager from the backup master domain manager
    2. Making the switch permanent
  7. Upgrading agents and domain managers
Environment with custom certificates
If you have version 9.5 installed with custom certificates, then after upgrading to 10.2 you must ensure that the parameters and the name of the relevant certificates in the localopts file are correct.
If you have previously used certificates generated with OpenSSL, check the paths in the following section:
  • For Open SSL, check:
    • SSL key
    • SSL certified
    • SSL key pwd
    • SSL CA certified
    • SSL random seed
If you have used GSKit, the relevant parameters are automatically migrated to the new OpenSSL parameters:
  • SSL Version
  • SSL Ciphers
  • CLI SSL Ciphers
  • CLI SSL Version

If the value of these fields corresponds to an incorrect path, then stop the WebSphere Application Server Liberty Base, make the necessary changes, and refer to the client's certificates, and then Restart.

For more information, see Setting local options.