Installing a new backup dynamic domain manager

Procedure for installing a dynamic domain manager configured as a backup.

Install a new dynamic domain manager at the latest product version level configured as the new backup dynamic domain manager 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. IBM® Workload Scheduler 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 IBM Workload Scheduler 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...
Database information
--rdbmstype database type Upgrading the database for the server components
--dbhostname database hostname
--dbport database port
--dbname database name
--dbuser database user name
--dbpassword database password
IBM Workload Scheduler information
--wauser IBM Workload Scheduler administrative user name Creating the IBM Workload Scheduler administrative user
--wapassword IBM Workload Scheduler administrative user password
WebSphere Application Server Liberty Base information
--wlpdir WebSphere Application Server Liberty Base installation directory Installing WebSphere Application Server Liberty
Security information
--sslkeysfolder location of converted certificates Converting default certificates
--sslpassword password of converted certificates Converting default certificates
Before starting the installation, ensure the following steps have been completed:
  1. Converting default certificates. Because you are installing a dynamic domain manager, also copy locally the jwt.crt file created in the conversion procedure.
  2. Upgrading WebSphere Application Server Liberty on the workstation where you plan to install the dynamic domain manager and on the workstation where you plan to install the backup dynamic domain manager.
  3. Encrypting passwords (optional)
  4. Upgrading the Dynamic Workload Console and its database
  5. Creating the IBM Workload Scheduler administrative user on the workstations which will host the components at 10.2.4 level.
  6. Upgrading the database for the server components
  7. Customizing and submitting the optional FINAL job stream

You can run the serverinst command specifying a typical set of parameters. In this case, default values are used for all remaining parameters. For more information about all serverinst parameters and default values, see Server components installation - serverinst script.

A properties file named serverinst.properties is available if you do not want to type parameters in the command line. This is expecially useful if you need to specify many parameters or if you want to reuse the file for several installations. The file is located in image_location/TWS/interp_name.

You can specify values in the properties file, type them in the command line, or use both methods. If a parameter is specified both in the properties file and in the command line, the command line value takes precedence.

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.
  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
        --sslkeysfolder certificate_files_path --sslpassword keystore_truststore_password
        --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
        --sslkeysfolder certificate_files_path --sslpassword keystore_truststore_password 
        --mdmhttpsport mdm_https_host_name --wlpdir Liberty_installation_dir/wlp
  4. 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 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 proceed to Cleaning up your environment.