Parallel upgrade from version 9.5.0.x or 10.x.x to version 10.2.2

About this task

To upgrade your environment using a parallel 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
  3. Encrypting passwords (optional)
  4. Upgrading the Dynamic Workload Console and its database
  5. Creating the HCL Workload Automation administrative user on the workstations which will host the components at 10.2.2 level.
  6. Upgrading the database for the server components
  7. Installing a new dynamic domain manager configured as a backup
    1. Switching the manager to the upgraded backup
    2. Making the switch permanent
  8. Upgrading the database schema for the server components
  9. Installing the new master domain manager configured as a backup
    1. Switching the manager to the upgraded backup
    2. Making the switch permanent
  10. Customizing and submitting the optional FINAL job stream
  11. Installing a new backup dynamic domain manager to replace the backup dynamic domain manager which you have switched to become the current dynamic domain manager.
  12. Cleaning up your environment
  13. Optionally dismiss all back-level components
  14. Upgrading agents and domain managers
  15. Optionally install a new backup master domain manager at version 10.2.2 to ensure failover capabilities.
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