HCL Workload Automation, Version 9.4

Configuration steps for 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:
  1. Log in as <TWS_user> on your master domain manager
  2. Add the username and password for the master domain manager configured as backup to the useropts file. For details, see

    Setting user options.

  3. Set the environment variables by running tws_env as described in Setting the environment variables.
  4. 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, using composer:
  5. Type the workstation definition in the text editor, for example:
     DESCRIPTION "Backup master domain mananger"
     OS UNIX 
     NODE lab777
     TCPADDR 31111
       TYPE FTA 
    For more information about workstation definitions, see the HCL Workload Automation: User's Guide and Reference.
  6. 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 or only the not completed job streams are carried forward.
  7. 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, DM1 is not required.
Additionally, the following configuration procedures might be necessary. For information about these procedures, see HCL Workload Automation: Administration Guide.
  • Customizing and configuring global, local, and user options.
  • Customizing and configuring user authentication to allow users authorization on actions and objects, and to configure LDAP.
  • Setting connection security to enable SSL or GSKit for inter-component communications.