HCL Workload Automation, Version 9.4

Configuring a master domain manager

About this task

After you installed a master domain manager, if you did not select to automatically add the final job stream during installation, follow the steps in this section to add the FINAL and FINALPOSTREPORTS job streams to the database.

The FINAL job stream is placed in production every day and runs JnextPlan before the start of a new day.

The FINALPOSTREPORTS job stream, responsible for printing post production reports, follows the FINAL job stream and starts only when the last job listed in the FINAL job stream (SWITCHPLAN) is completed successfully.

The installation creates the <TWS_INST_DIR>\TWS\Sfinal file that contains the FINAL and FINALPOSTREPORTS job stream definitions.

You can use the <TWS_INST_DIR>\TWS\Sfinal or create a customized new file for the FINAL job stream. For details about customizing the final job stream, see HCL Workload Automation: User's Guide and Reference.

The following steps gives an example of how to configure a master domain manager after the installation:
  1. Log in as <TWS_user> or as administrator.
  2. Set the environment variables. See Setting the environment variables.
  3. Add the FINAL and FINALPOSTREPORTS job stream definitions to the database by running the following command from the /opt/HCL/TWA/TWS directory: 
    composer add Sfinal
    where Sfinal is the name of the file that contains the FINAL and FINALPOSTREPORTS job stream definitions.
  4. Add the FINAL and the FINALPOSTREPORTS job streams to the plan by running: 
    JnextPlan
    You can automate this step after installation. See HCL Workload Automation: User's Guide and Reference.
  5. When JnextPlan completes, check the status of HCL Workload Automation: 
    conman status
    If HCL Workload Automation started correctly, the status that is returned by the command is Batchman LIVES.
  6. Change the workstation limit value to run jobs. The default job limit after installation is 0, so no jobs run at any time. Raise the job limit to allow jobs to run, for example, to run 10 jobs at the same time: 
    conman "limit ;10"
    If no workstation name is specified for the limit command, the default value is the current login workstation.
    Note: If the priority of jobs is HI (100) or GO (101), the limit is ignored and the jobs run even if the limit is 0, unless the workstation fence is greater than or equal to the priority.
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.