Connecting to a Communication Process (CP)
The agents and the Automic Web Interface connect to communication processes (CPs). A connection to the database of the AE is not required for this purpose because data exchanged between clients (Automic Web Interface and agents) and the Automation Engine is exclusively exchanged through CPs.
Connections are established in several steps.
- The agent attempts to connect to a randomly selected communication process (CP) as specified in the parameter CP.PORTS= in the [PORTS] section of the INI file of the Automation Engine, see Automation Engine.
- The agent selects the communication process (CP) with the best connection count. One communication process (CP) can handle 99999 connections on all platforms. The exceptions is zLinux where the limit is 65000.
- Upon establishing a connection, the communication process (CP) provides the client (Automic Web Interface or agent) the performance values for the connection and information about all addresses of communication processes (CP) known in the system.
- The addresses are used to update the corresponding sections of the INI file entries.
The number of agents, the number of connections per communication process, and the number of concurrent users logged in do have an upper limit. For the current upper limit of each, refer to the log files of the primary work process (PWP) and the communication processes (CP).
See also: