Upgrading the Dynamic Workload Console

This section describes how to upgrade the Dynamic Workload Console from version 9.3 or later, to the current version.

The graphic displays the typical flow of an upgrade procedure beginning with the creation and population of the Dynamic Workload Console database, the installation of the Dynamic Workload Console, and the export of the Dynamic Workload Console settings to a file
When upgrading your HCL Workload Automation environment, it is a good practice to start with the upgrade of the Dynamic Workload Console first. If you upgrade the console to the new product version level, you can then use it to verify that your environment is working after upgrading the remaining components.
With Version 9.5, the Dynamic Workload Console is based on a new architectural foundation that does not include Jazz for Service Management nor Dashboard Application Services Hub, therefore, the upgrade procedure from previous versions involves performing the following tasks:
  1. Creating and populating the database. Alternatively, by default, the installation script is configured to install and use a Derby database.
  2. A fresh installation of the latest product version.
  3. Import of the repository settings from the previous Dynamic Workload Console installation.
  4. Creating new roles by configuring them to access the Dynamic Workload Console as described in Configuring roles to access the Dynamic Workload Console.

Each Dynamic Workload Console installation also requires creating and populating the database (unless the default Derby database is used), the creation of the HCL Workload Automation administrative user, and the installation of WebSphere Application Server Liberty Base. To complete the installation, you can import the repository settings from your previous console installation to maintain the same customized settings.