Installing the master domain manager as a backup master domain manager

Before you begin

Before beginning the installation, ensure you have completed the following steps:

About this task

You install a master domain manager at the latest product version level configured as the new backup master domain manager by running the serverinst script. The installation process is able to detect the presence of an existing master domain manager and automatically configures this one as the backup master domain manager. The new backup master domain manager is configured to point to the existing database instance.

The HCL Workload Automation administrator installs the master 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 schema for the server components
--dbhostname	database hostname
--dbport	database port
--dbname	database name
--dbuser	database user name
--dbpassword	database password
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	Creating the HCL Workload Automation administrative user
WebSphere Application Server Liberty Base information
--wlpdir	WebSphere Application Server Liberty Base installation directory	Installing WebSphere Application Server Liberty Base

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

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 master domain manager as a backup, perform the following steps:

Procedure

Log in as root or Administrator to the workstation where you plan to install the master domain manager.
Browse to the folder where the serverinst command is located in image_location/TWS/interp_name.
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> --wlpdir <Liberty_installation_dir>\wlp
--licenseserverid <license_server_ID>
--sslkeysfolder <certificate_files_path> --sslpassword <keystore_truststore_password>
```
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> --wlpdir <Liberty_installation_dir>/wlp
--licenseserverid <license_server_ID>
--sslkeysfolder <certificate_files_path> --sslpassword <keystore_truststore_password>
```
where
--acceptlicense

Specify yes to accept the product license.

--rdbmstype|-r rdbms_type
The database type. Supported databases are:
- db2
- oracle
- ids (informix, only on UNIX operating systems)
- onedb
- mssql
This parameter is optional. The default value is db2.
--dbhostname db_hostname

The host name or IP address of database server.

--dbport db_port

The port of the database server.

--dbname db_name

The name of the HCL Workload Automation database.

--dbuser db_user

The database user that has been granted access to the HCL Workload Automation tables on the database server.

--dbpassword db_password

The password for the user that has been granted access to the HCL Workload Automation tables on the database server.

--wauser user_name

The user for which you are installing HCL Workload Automation.

--wapassword wauser_password

The password of the user for which you are installing HCL Workload Automation.

On Windows operating systems

Supported characters for the password are alphanumeric, dash (-), underscore (_) characters, and ()|?*~+.

On UNIX operating systems

Supported characters for the password are alphanumeric, dash (-), underscore (_) characters, and ()|?=*~+.

--wlpdir

The path where WebSphere Application Server Liberty Base is installed.

--licenseserverid

The ID of the license server which processes license usage information. This parameter is required. For more information about enabling your product license, see Enabling product license management. For more information about creating and setting up the license server, see What is the HCL License & Delivery Portal (FlexNet Portal)?
--sslkeysfolder
The name and path of the folder containing certificates in .pem format. The installation program automatically processes the keystore and truststore files using the password you specify with the --sslpassword parameter. The folder must contain the following files:
- ca.crt
  
  The Certificate Authority (CA) public certificate.
- tls.key
  
  The private key for the instance to be installed.
- tls.crt
  
  The public part of the previous key.
You can optionally create a subfolder to contain one or more *.crt files to be added to the server truststore as trusted CA. This can be used for example to add to the list of trusted CAs the certificate of the LDAP server or DB2 server. Additionally, you can store here any intermediate CA certificate to be added to the truststore. The subfolder must be named additionalCAs.
This parameter is required if you set the --dbsslconnection parameter to true.
--sslpassword

The password for the custom certificates and the path to the folder containing certificates in .pem format with the sslkeysfolder parameter. You can optionally encrypt the password using the secure script. For more information, see Optional password encryption - secure script.
Note: The values for the following parameters must match the values you provided when creating and populating the database:
- --rdbmstype
- --dbhostname
- --dbport
- --dbname
- --dbuser
- --dbpassword
Note: Before starting the deployment of a new master domain manager or backup master domain manager on an already used database, be sure that no failed plan creation/extension has been performed. If a failed plan creation/extension has been performed, resolve the failure before attempting the new deployment or unlock the database by running the planman unlock db command.
To verify that the installation completed successfully, browse to the directory where you installed the master domain manager and type the following commands:
```
 . ./tws_env.sh
```
```
optman ls
```
This command lists the HCL Workload Automation configurations settings and confirms that HCL Workload Automation installed correctly.

Results

You have now successfully installed the master domain manager as the backup master domain manager.

What to do next

You can now proceed to Configuring security if this was not done in the previous installation, or to Switching the master domain manager to the new backup master.