This document lists communication ports required by CA Workload Automation AE Clients and System Agents to work with CA Workload Automation AE Schedulers and Application Server(s) behind a firewall/DMZ.
What ports need to be open on the firewall for the CA WA System Agent and CA WA Clients to work with CA Workload Automation AE Scheduler / Application Server behind a firewall?
Release: All Supported Versions
Component: Workload Automation AE (AutoSys Edition):
CA WAAE Client Communication:
TCP/7163 - CA Connection Broker (a.k.a CA Secure Socket Adapter, SSA) port on both the Scheduler, Application Server host and the Client host needs to be open for bidirectional communication.
(WAAE Clients communicate with the Application Server through the SSA sockets)
CA WA System Agent Communication:
The following default ports should be open for unidirectional (Incoming) communication.
TCP/7520 - Agent Communication Port on the System Agent machine (CA WA Agent listens on this port for communication from Scheduler).
TCP/7500 - Application Server communication input port on the Application Server Machine (CA WAAE Application Server listens on this port for communication from the CA WA Agent).
TCP/7507 - Scheduler communication input port on the Scheduler machine (CA WAAE Scheduler listens on this port for communication from the CA WA Agent).
If the CA WA Agent is configured to use the SSA ports, then TCP/7163 port needs to be open bidirectionally.
Configure the Agent to Communicate Using SSA Ports
The aforementioned port numbers are the defaults and configurable.
For the environments behind the Firewall (The Link contains list of default ports): Configure the Firewall
Configure CA Workload Automation AE to Work with Agent
Configure Agent to work with CA Workload Automation AE
Communication requirements for AWS or Microsoft Azure Security Group