Installing the dynamic domain manager and backup dynamic domain manager
Considerations about installing the dynamic domain manager and backup dynamic domain manager
A dynamic domain manager is the management hub in a domain running both static and dynamic workload. All communications to and from the dynamic agents in the domain are routed through the dynamic domain manager.
The dynamic domain manager and backup dynamic domain manager require a dedicated database and a dedicated Open Liberty.
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 Open Liberty 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.
Command parameter | Information type | Provided in... |
Database information | ||
--rdbmstype | database type | Creating and populating the database for the dynamic domain manager |
--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 and Installing the master domain manager and backup master domain manager |
--wapassord | HCL Workload Automation administrative user password | |
--master | The master domain manager name | |
--mdmbrokerhostname | The fully qualified host name or IP address of the master domain manager contacted by the dynamic domain manager. | |
--mdmhttpsport | The port of the master domain manager host used by the broker to contact master domain manager. | |
Open Liberty information | ||
--wlpdir | Open Liberty installation directory | Installing Open Liberty |
- Installing Open 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.
- Encrypting passwords (optional).
- Creating and populating the database for the dynamic domain manager
- Creating the HCL Workload Automation administrative user
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.
- Log in to the workstation where you plan to install as root.
- 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
- 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
Result
You have now successfully installed the dynamic domain manager and backup dynamic domain manager.
For more information about all serverinst parameters and default values, see Server components installation - serverinst script.