Configuring a master domain manager configured as backup
About this task
After you install a master domain manager
configured as backup, perform the following additional configuration steps:
- Log in as TWS_user on your master domain manager.
- Add the username and password for the master domain manager configured as backup to the useropts file. For details, see Setting user options.
- Set the environment variables by running tws_env as described in Setting the environment variables.
- Define the master domain manager configured as
backup as a full status autolink fault-tolerant agent in the HCL Workload Automation database, using the
composer command interface or the Dynamic Workload Console. In this example with
composer, type the following command:
composer new
- Type the workstation definition in the text editor, for example:
For more information about workstation definitions, see Workstation definition .CPUNAME BDM1 DESCRIPTION "Backup master domain mananger" OS UNIX NODE lab777 TCPADDR 31111 FOR MAESTRO TYPE FTA AUTOLINK ON BEHINDFIREWALL OFF FULLSTATUS ON end
- Run JnextPlan -for 0000 to include the master domain manager configured as backup workstation in the
plan and to send the Symphony™ file to
it. Note: Ensure that the global option carryforward is set to all, otherwise only incomplete job streams are carried forward.
- Change the workstation limit to allow jobs to run on the workstation. For example, set the
number of jobs to run concurrently on the workstation to 10:
conman "limit DM1;10"
Note: If you are logged into the master domain manager configured as backup, the workstation name (DM1 in the above example) is not required.
Additionally, the following configuration procedures might be necessary:
- Customizing and configuring global, local, and user options. See the relevant sections in Customizing and configuring HCL Workload Automation
- Customizing and configuring user authentication to allow users authorization on actions and objects, and to configure LDAP. See Configuring authentication.
- Setting connection security to enable SSL or GSKit for inter-component communications. See the relevant sections in Connection security overview.