Installing a new backup dynamic domain manager

Procedure for installing the new backup dynamic domain manager

At this phase in the procedure, you have installed a fresh backup dynamic domain manager at the latest product version level and switched it to become the new dynamic domain manager. To complete the environment set up, you now need to install a new backup dynamic domain manager at the latest product version level by running the serverinst script.

The procedure to install the dynamic domain manager and backup dynamic domain manager is exactly the same, with the difference that it is performed on two different workstations and that each installation points to its local WebSphere Application Server Liberty Base installation. HCL Workload Automation determines whether or not a dynamic domain manager is already present in the environment and proceeds to install a dynamic domain manager or backup dynamic domain manager accordingly.

The HCL Workload Automation administrator installs the dynamic domain manager as the backup. The following information is required:
Table 1. Required information

Required information for performing the installation
Command parameter Information type Provided in...
HCL Workload Automation information
--wauser HCL Workload Automation administrative user name Creating the HCL Workload Automation administrative user
--wapassord HCL Workload Automation administrative user password
WebSphere Application Server Liberty Base information
--wlpdir WebSphere Application Server Liberty Base installation directory Installing WebSphere Application Server Liberty Base
Before starting the installation, ensure the following steps have been completed:
  1. Installing WebSphere Application Server Liberty Base on the workstation where you plan to install the dynamic domain manager and on the workstation where you pan to install the backup dynamic domain manager
  2. Encrypting passwords (optional)
  3. Upgrading the database schema for the dynamic domain manager
  4. Creating the HCL Workload Automation administrative user
  5. Distribute the Symphony file to the new dynamic domain manager configured as backup:
    1. Ensure that the optman cf option is set to all.
    2. To distribute the Symphony file to the new dynamic domain manager configured as backup, run JnextPlan -for 0000 or wait until the end of the production plan.
    3. Restore the previous setting of the optman cf option, if you previously modified the value.

You can run the serverinst command specifying a typical set of parameters. In this case, default values are used for all remaining parameters.

Default values are stored in the serverinst.properties file, located in image_location/TWS/interp_name.

If you need to modify any of the default values, edit the serverinst.properties file, but do not modify the serverinst.template file located in the same path.

To install the dynamic domain manager as a backup, perform the following steps:
  1. Log in to the workstation where you plan to install as root.
  2. Browse to the folder where the serverinst command is located:
    On Windows operating systems
    image_location\TWS\interp_name
    On UNIX operating systems
    image_location/TWS/interp_name
  3. Start the installation specifying a typical set of parameters. In this case, default values are used for all remaining parameters:
    On Windows operating systems
    cscript serverinst.vbs --acceptlicense yes --rdbmstype db_type 
        --dbhostname db_hostname --dbport db_port --dbname db_name 
        --dbuser db_user --dbpassword db_password --wauser wa_user 
        --wapassword wa_password --componenttype DDM --domain domain_name
        --master mdm_name --mdmbrokerhostname mdm_broker_host_name 
        --mdmhttpsport mdm_https_host_name --wlpdir Liberty_installation_dir\wlp
    On UNIX operating systems
    ./serverinst.sh --acceptlicense yes --rdbmstype db_type 
        --dbhostname db_hostname --dbport db_port --dbname db_name 
        --dbuser db_user --dbpassword db_password --wauser wa_user 
        --wapassword wa_password --componenttype DDM --domain domain_name 
        --master mdm_name --mdmbrokerhostname mdm_broker_host_name 
        --mdmhttpsport mdm_https_host_name --wlpdir Liberty_installation_dir/wlp

You have now successfully installed the backup dynamic domain manager at the new product version level.

For more information about all serverinst parameters and default values, see Server components installation - serverinst script.

What to do next

You can now optionally proceed to Switching back to the old dynamic domain manager (optional).