Configuring CA ESP System Agent to communicate with multiple CA ESP Workload Automation subsystems

Document ID : KB000054911
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

CA ESP System Agents can be configured to communicate with multiple CA ESP Workload Automation subsystems when a few configuration changes are made

Solution:

These examples pertain to all currently supported ESP and System Agent releases.

This example will show how to configure a CA ESP Agent to communicate with two CA ESP Workload Manager subsystems.
All required and/or optional parameters will not be coded only those which must be unique.
Complete details for each parameter can be found in the following documentation:
CA ESP Workload Automation Installation and Configuration Guide
CA ESP System Agent Administrator's Guide

The scenario is one agent named AGENT1 and two ESP subsystems named ESP1 and ESP2.

First, on the ESP1 side:

In the init parms code AGENTRCV:
AGENTRCV DEFINE NAME(ESP1RCV) PORT(4000)

In the AGENTDEF member code:
MANAGER NAME(ESP1_MANAGER) TCPIP

Second, on the ESP2 side:

In the init parms code AGENTRCV:
AGENTRCV DEFINE NAME(ESP2RCV) PORT(4001)

In the AGENTDEF member code:
MANAGER NAME(ESP2_MANAGER) TCPIP

In the AGENTDEF member for both ESP1 and ESP2 code:
AGENT AGENT1 ADDRESS(agent1_ip_address) PORT(4002) NT ASCII TCPIP PREFIXING

The things to keep in mind here are:

  1. The NAME on the AGENTRCV parameter can be any 8 characters as long as they start with an alphabetic or national character.
  2. The PORT on the AGENTRCV parameter can be any port that is not currently in use where the ESP subsystem is running
  3. The NAME on the MANAGER must be unique for each ESP subsystem
  4. The PORT on the AGENT parameter can be any port not currently in use on the server where the agent is installed
  5. Again see the documentation regarding the keywords NT ASCII TCPIP and PREFIXING

Third, on the AGENT1 side:

In the agentparm.txt code:

agentname=AGENT1

communication.managerid_1=ESP1_MANAGER
communication.manageraddress_1=esp1_ip_address
communication.managerport_1=4000
communication.monitorobject_1=AGENT1/AGENTMON1.0/MAIN

communication.managerid_2=ESP2_MANAGER
communication.manageraddress_2=esp2_ip_address
communication.managerport_2=4001
communication.monitorobject_2=AGENT1/AGENTMON2.0/MAIN

communication.inputport=4002

The things to keep in mind here are:

  1. communication.managerid_1 must be unique and match what is coded on the MANAGER parameter for ESP1 subsystem
  2. communication.managerid_2 must be unique and match what is coded on the MANAGER parameter for ESP2 subsystem
  3. communication.managerport_1 must match what is coded on the AGENTRCV parameter for ESP1 subsystem
  4. communication.managerport_2 must match what is coded on the AGENTRCV parameter for ESP2 subsystem

All ip_addresses can be either the dotted ip address or a DNS name

The above configuration can be expanded so that the agent communicates with as many ESP subsystems as required.

For example to add a third ESP subsystem ESP3 code:

In the init parms code AGENTRCV:
AGENTRCV DEFINE NAME(ESP3RCV) PORT(4003)

In the AGENTDEF member code:
MANAGER NAME(ESP3_MANAGER) TCPIP
AGENT AGENT1 ADDRESS(agent1_ip_address) PORT(4002) NT ASCII TCPIP PREFIXING

In the agentparm.txt code:
communication.managerid_3=ESP3_MANAGER
communication.manageraddress_1=esp3_ip_address
communication.managerport_3=4003
communication.monitorobject_3=AGENT1/AGENTMON3.0/MAIN

After changes to the AGENTDEF member have been made the new AGENTDEF can be loaded in ESP ISPF pagemode by entering:
OPER LOADAGDF

After changes to the agentparm.txt have been made the agent must be stopped and started for the changes to take effect.