Configuring the Agent › Configure Communication with a Scheduling Manager

Configure Communication with a Scheduling Manager

You can change your scheduling manager connection information or add a connection to a different scheduling manager. If you are using the agent with two scheduling managers that require different socket types for communication, you can specify a main and auxiliary socket for the agent.

To configure communication with a scheduling manager, configure the following agent parameters on the agent:

communication.inputport

Specifies the main port number the agent uses to listen for incoming messages from the scheduling manager. You need this port when you configure the scheduling manager to work with the agent.

Default: 7520

Limits: 1024-65534

communication.inputport.aux

Optional. Specifies the auxiliary port number the agent uses to listen for incoming messages from the scheduling manager.

communication.manageraddress_n

Specifies the address of the scheduling manager that the agent works with, where n is an integer that corresponds to the scheduling manager being configured. This value corresponds to the IP address in the connection details for the scheduling manager. You can specify a list of addresses for the scheduling manager.

Example: 172.24.36.107 (IPv4) or 0:0:0:0:0:FFFF:192.168.00.00 (IPv6)

Notes:

• You can specify a DNS name instead of the IP address for the scheduling manager. However, your agent computer must be able to resolve the DNS name at all times. If there is a DNS outage and your agent computer cannot resolve DNS names, the agent cannot communicate with the scheduling manager.
• If the scheduling manager address never changes, enter the DNS name for the scheduling manager in the hosts file for your agent computer. This entry helps ensure that the IP address can be resolved after DNS disruptions.

communication.managerid_n

Specifies the name of the scheduling manager instance that the agent works with, where n is an integer that corresponds to the scheduling manager being configured.

Default: CENTRAL_MANAGER

Example: MYSERVER

communication.managerport_n

Specifies the port that the scheduling manager listens on for communication from agents, where n is an integer that corresponds to the scheduling manager being configured. This value corresponds to the port number in the connection details for the scheduling manager.

Default: 7507

Limits: 1024-65534

communication.monitorobject_n

Specifies the monitor object for the scheduling manager that is used in agent alive ping.

communication.receiver.socket.aux

Specifies the type of socket the agent uses for its auxiliary port. The value of this parameter must be different from the communication.receiver.socket.main parameter. You can specify the following socket types:

• plain
• dylan

Note: CA Workload Automation DE does not require this parameter.

communication.receiver.socket.main

Specifies the type of socket the agent uses for its main port. The value of this parameter must be different from the communication.receiver.socket.aux parameter. You can specify the following socket types:

• plain
• dylan

Default: plain

Note: CA Workload Automation DE does not require this parameter.

communication.socket_n

Defines the socket type the agent and scheduling manager use for communication, where n is an integer starting at one that corresponds to the scheduling manager being configured. The following socket types are available:

• plain
• dylan

Default: plain

Note: CA Workload Automation DE does not require this parameter.

Note: You can configure the agent to work with multiple scheduling managers by adding additional definitions in the agentparm.txt file.

Example: Configure the Agent to Communicate with a Scheduling Manager

In this example, the following configuration parameters are set in the agentparm.txt file for a scheduling manager running under the instance “ACE” at address 130.200.146.134. The scheduling manager listens for incoming messages from the agent on port 49155:

communication.inputport=7520
communication.managerid_1=ACE
communication.manageraddress_1=130.200.146.134
communication.managerport_1=49155
communication.monitorobject_1=CAEWA_AGENT/AGENTMON1.0/MAIN
communication.receiver.socket.main=plain
communication.socket_1=plain