Performing a direct upgrade of the dynamic domain manager, its backups, and their database

Complete this procedure to upgrade the dynamic domain manager and the backup dynamic domain manager from version 9.5.0.x to version 10.2.x.

About this task

Upgrade a dynamic domain manager and a backup dynamic domain manager from version 9.5.0.x to version 10.2.x by running the serverinst script. Launch the script on the workstation where the dynamic domain manager is running to upgrade the dynamic domain manager, then launch the script on the workstation where the backup dynamic domain manager is running to upgrade the backup dynamic domain manager.

Procedure

  1. Log in to the workstation where you plan to install.
  2. On UNIX™ operating systems, ensure that umask is set to 022. To verify that umask is set to the correct value, from a command prompt, run the umask command. If the value is different from 022, modify it by running the following command: 
    umask 022
    On Windows operating systems, ensure you have the correct rights on the folder where you plan to install.
  3. Download the installation images from HCL License Portal.
  4. Browse to the folder image_location/TWS/interp_name.
  5. Stop all HCL Workload Automation services and WebSphere Application Server Liberty, by running the following commands: 
    conman stop; wait
conman shut; wait
conman ShutDownLwa
stopappserver
  6. To update the database version, run the following command:
    On Windows operating systems
    cscript configureDb.vbs –-componenttype=DDM --rdbmstype db_type --dbhostname db_hostname --dbport db_port --dbname db_name --dbuser db_user --dbpassword db_password --dbadminuser db_administrator --dbadminuserpw db_administrator_password
    On UNIX operating systems
    ./configureDb.sh –-componenttype=DDM --rdbmstype db_type --dbhostname db_hostname --dbport db_port --dbname db_name --dbuser db_user --dbpassword db_password --dbadminuser db_administrator --dbadminuserpw db_administrator_password
    For more information about the configureDb script, see Database configuration - configureDB script.
  7. If your current version is earlier than 10.2.1, your certificates need to be updated before they can work with version 10.2.2. The update is performed automatically, but you need to provide the password for the certificates. Define an environment variable with name JKS_SSL_PASSWORD and set it to the password you defined for the certificates. You can optionally encrypt the password using the secure script. For more information about the secure script, see Optional password encryption - secure script.
  8. Check your FIPS settings. Starting from version 10.2.1, FIPS is no longer supported. If FIPS is enabled in your current environment, specify the enablefips parameter when installing and set it to false. This will disable FIPS by changing the related keywords in the localopts and ita.ini files. For more information, see Q: My environment is FIPS compliant. What happens if I upgrade to version 10.2.2?. If FIPS is not enabled in your current environment, you can skip the enablefips parameter.
  9. Start the installation launching the following command:
    On Windows operating systems
    cscript serverinst.vbs --acceptlicense yes --inst_dir INST_DIR
    On UNIX operating systems
    ./serverinst.sh --acceptlicense yes --inst_dir INST_DIR

    where INST_DIR is the directory where the component is installed. To find out the installation directory, see Finding out what has been installed in which HCL Workload Automation instances.

    Note: The acceptlicense and inst_dir parameters are required. All other parameters are ignored by the serverinst command, except for the following two optional parameters: lang and skipcheckprereq.

    For further details about the serverinst script, see Server components installation - serverinst script.

  10. After the installation has completed, run the following commands to start up HCL Workload Automation services and WebSphere Application Server Liberty: 
    conman start
conman startappserver
StartUpLwa

What to do next

You have now successfully upgraded the dynamic domain manager and its backup. You can now proceed to Performing a direct upgrade of the backup master domain manager and its database.