How to configure ESP Agent to communicate with multiple ESP subsystems
Article ID: 54911
Updated On:
Products
Issue/Introduction
How to configure ESP Agent to communicate with multiple ESP subsystems?
Environment
Component: WORKLOAD AUTOMATION AGENTS
Resolution
Example#1: Agent AGENT1 communicates with ESP subsystems ESP1 and ESP2
On ESP1:
In the init parms, code AGENTRCV:
AGENTRCV DEFINE NAME(ESP1RCV) PORT(4000)
In the parmlib member AGENTDEF, code:
MANAGER NAME(ESP1_MANAGER) TCPIP
On ESP2:
In the init parms, code AGENTRCV:
AGENTRCV DEFINE NAME(ESP2RCV) PORT(4001)
In the parmlib member AGENTDEF, code:
MANAGER NAME(ESP2_MANAGER) TCPIP
In the parmlib member AGENTDEF for both ESP1 and ESP2, code:
AGENT AGENT1 ADDRESS(agent1_ip_address) PORT(<port>) NT ASCII TCPIP PREFIXING
Note:
The NAME on the AGENTRCV parameter can be any 8 characters as long as they start with an alphabetic or national character.
The PORT on the AGENTRCV parameter can be any port that is not currently in use where the ESP subsystem is running
The NAME on the MANAGER must be unique for each ESP subsystem
The PORT on the AGENT parameter can be any port not currently in use on the server where the agent is installed
Check the documentation regarding the keywords NT ASCII TCPIP and PREFIXING
On AGENT1:
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
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. After changes to the agentparm.txt have been made the agent must be stopped and started for the changes to take effect.
2. After changes to the AGENTDEF member have been made the new AGENTDEF can be loaded in ESP ISPF pagemode by entering:
OPER LOADAGDF
Note:
communication.managerid_1 must be unique and match what is coded on the MANAGER parameter for ESP1 subsystem
communication.managerid_2 must be unique and match what is coded on the MANAGER parameter for ESP2 subsystem
communication.managerport_1 must match what is coded on the AGENTRCV parameter for ESP1 subsystem
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.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Example#2 Agent AGENT1 communicates with ESP1, ESP2, and adding subsystem ESP3
In the init parms, code AGENTRCV:
AGENTRCV DEFINE NAME(ESP3RCV) PORT(4003)
In the parmlib member AGENTDEF, code:
MANAGER NAME(ESP3_MANAGER) TCPIP
AGENT AGENT1 ADDRESS(agent1_ip_address) PORT(4002) NT ASCII TCPIP PREFIXING
In the agentparm.txt code:
agentname=AGENT1
communication.managerid_3=ESP3_MANAGER
communication.manageraddress_1=esp3_ip_address
communication.managerport_3=4003
communication.monitorobject_3=AGENT1/AGENTMON3.0/MAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. After changes to the agentparm.txt have been made the agent must be stopped and started for the changes to take effect.
2. After changes to the AGENTDEF member have been made the new AGENTDEF can be loaded in ESP ISPF pagemode by entering:
OPER LOADAGDF
Feedback
