Users of CA Process Automation use a supported browser (CA Process Automation Client) to connect to Orchestrators, possibly through a load balancer, to perform configuration, to create and modify automation objects, to start and monitor processes and to respond to interaction requests.
CA Process Automation Clients communicate with an Orchestrator through its HTTP port. Multiple clients and consoles can be initiated from the same desktop systems and can point to the same or different Orchestrators - even Orchestrators in different domains.
Orchestrators and Agents communicate bi-directionally to perform process operations.
Orchestrators also need to communicate with one or more Relational Database Management systems for access to CA Process Automation data persisted in the CA Process Automation Runtime, Library, and Reporting databases, as well as the CA Embedded Entitlements authentication and authorization directory.
A Domain Orchestrator will also perform mirroring, heartbeat and configuration updates with the Agents and with other Orchestrators.
For Proxy Agents or Touchpoints, a particular Agent is configured to communicate with the remote host through SSH (v2). The remote host must be running an SSH Server and, for some operations, must have a write-accessible file system.
Communication between Agents on UNIX or Windows boxes is based on TCP/IP. Data transmitted between CA Process Automation components is encrypted.
This section contains the following topics:
The Attached PDF file; PAM 4.1 Communications.pdf, lists all Ports in use by CA Process Automation, EEM and the Apache load balancer to assist withconfiguration of Networking to allow successful use of CA Process Automation.
Release: ITPASA99000-4.1-Process Automation-Add On License for-CA Server Automation