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.
About this task
Upgrade a dynamic domain manager and a backup dynamic domain manager 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
- Log in as root or Administrator to the workstation where you plan to install.
- Download the installation images from HCL License Portal.
- Browse to the folder image_location/TWS/interp_name.
-
If possible, stop both dynamic domain manager and backup dynamic domain manager.
If this is not possible, launch the configureDB script at a time when the server components are processing a low workload. If the configureDB script should fail because of conflicts with the server components, restart the script.
-
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
-
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 commands, see Reference.
-
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.
- If you have copied any template .xml files from the templates folder to the overrides folder, check for any differences between the default .xml files just upgraded in the templates folder and the templates you are using in the overrides folder. If any differences are present, update the files in the overrides folder accordingly.
-
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