Configuring a fault-tolerant agent
About this task
After installing a fault-tolerant agent, define the workstation in the database and link the workstation from the master. You can perform this task by using the Dynamic Workload Console or the command line interface. For information, see User's Guide and Reference. The following is an example of how to configure a fault-tolerant agent after installation using the command line interface:
- Log in to the master domain manager as TWS_user.
- Set the environment variables by running tws_env.sh.
- Create the workstation definition in the HCL Workload Automation database.
Open a command line window and enter the following commands:
composer new
- Type the workstation definition in the text editor. For example:
Run JnextPlan with the option -for 0000 to add the agent workstation definition to the plan and to send the Symphony file to it. For more information about workstation definitions, see Workstation definition.CPUNAME F235007_00 DESCRIPTION "fault-tolerant agent" OS UNIX NODE lab235007 TCPADDR 31111 DOMAIN MASTERDM FOR MAESTRO TYPE FTA AUTOLINK ON BEHINDFIREWALL OFF FULLSTATUS OFF END
Note: Ensure that the global option carryforward is set to all, otherwise only incomplete job streams are carried forward. - If you set the autolink parameter to OFF, issue the link command
from the master domain manager to link the agent and to download the
Symphony file to it:
conman “link workstation?
- 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 F235007_00;10"
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.