Installing a new backup master domain manager

Installing the new backup master domain manager

Before beginning the installation, ensure you have converted the certificates, as described in Converting default certificates.

You can perform a typical installation, as described in the following scenario, or you can customize the installation parameters, as described in FAQ - master domain manager and backup master domain manager customizations.

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

The procedure to install the backup master domain manager is exactly the same as installing a master domain manager. The backup master domain manager is installed on a workstation different from the master domain manager and points to its local WebSphere Application Server Liberty Base installation. IBM® Workload Scheduler detects the presence of an existing master domain manager in the environment and proceeds to install a backup master domain manager.

The IBM Workload Scheduler administrator installs the master domain manager. The following information is required:

Table 1. Required information
Required information for performing the upgrade
Command parameter	Information type	Provided in..
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	Creating the IBM Workload Scheduler administrative user
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

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

Log in to the workstation where you plan to install.
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
    --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
        --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
- ORALE
- 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 IBM Workload Scheduler database.

dbuser db_user

The user that has been granted access to the IBM Workload Scheduler tables on the database server.

dbpassword db_password

The password for the user that has been granted access to the IBM Workload Scheduler tables on the database server. Special characters are not supported.

wauser user_name

The user for which you are installing IBM Workload Scheduler.

wapassword wauser_password

The password of the user for which you are installing IBM Workload Scheduler.

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 any alphanumeric, dash (-), underscore (_) characters, and ()|?=*~+.

wlpdir

The path where WebSphere Application Server Liberty Base is installed.

--sslkeysfolder keystore_truststore_folder
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. Note that if certificates being installed are part of a chain consisting of 3 or more certificates (one Root CA, followed by one or more Intermediate CAs, followed by the end user certificate), then this file must contain the Root CA certificate only. Any Intermediate CA certificates must be stored in the additionalCAs subfolder, which therefore becomes a mandatory subfolder. Each Intermediate CA must be stored in the additionalCAs subfolder in its own file.
  Note: From V10.2.3, if certificates being installed are part of a chain, the ca.crt can contain also the intermediate CAs. In this case, it must begin with one or more intermediate CA certificates and end with the Root ca.
- tls.key
  
  The private key of the end user certificate for the instance to be installed.
- tls.crt
  
  The public part of the previous key, that is the end user certificate.
For UNIX systems, ensure that all the files have the ownership of the user who installed the master domain manager and the correct permissions (644).
You can optionally create a subfolder to contain one or more *.crt files to be added to the server truststore as trusted CA, whose name must be additionalCAs. 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. Note that if the end user certificate being installed in the instance is part of a chain consisting of 3 or more certificates (one Root CA, followed by one or more Intermediate CAs, followed by the end user certificate), then the Intermediate CAs certificates must be stored in the additionalCAs subfolder, which therefore becomes a mandatory subfolder. Each Intermediate CA must be stored in the additionalCAs subfolder in its own file.
For further information about how to generate custom certificates, see Managing certificates using Certman.
--sslpassword ssl_password

The password for the certificates.
For more information, see sslkeysfolder.
You can optionally encrypt the password using the secure script. For more information, see Optional password encryption - secure script.
To verify that the installation completed successfully, browse to the directory where you installed the backup master domain manager and type the following commands:
```
 . ./tws_env.sh
```
```
optman ls
```
This command lists the IBM Workload Scheduler configurations settings and confirms that IBM Workload Scheduler installed correctly.

You have now successfully installed the backup master domain manager and it is inserted in the next production plan. To have the backup domain manager added immediately to the production plan, run

JnextPlan -for 0000

You can now proceed to Ensuring communication in your environment.