Communication processes (CPs ) are used to connect certain components (such as agents and UserInterfaces) with the work processes (WPs ) and to handle their communication. The CP selection for the individual components takes place automatically and is workload-dependent. In an Automation Engine systemAn environment that is managed by Automation Engine components. [Formerly called "UC4 system."] that uses several CPs you can distribute the CPs over several areas and in doing so, you can manipulate the CP selection. Ideally, each area represents a certain network.
By default, the CP selection takes place as follows:
Note that Automic recommends running CPs and WPs in the same secure network zone. Should the CPs be located in different network zones, separated by a firewall, please observe and configure the necessary firewall exceptions. To enable CP selection, agents will be presented with a complete CP list as soon as they connect to the Automation EngineThis component drives an Automation Engine system and consists of different types of server processes.. Should some of the CPs be placed behind a firewall – from the agent's point of view – the connections of the agents to the CPs have to be configured in the firewall itself.
The CP selection can be restricted to certain CPs by grouping them into network areas. Use the parameter NetArea= ([TCP/IP] section) for this purpose which is located in the Automation Engine's INI file. The values for net area parameters may be userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management.-defined, but they have to be alphanumerical and should start with a letter.
Note that only CPs can be grouped in net areas. The WPs of an Automation Engine system must use the same net area. Any attempt to start a WP whose NetArea definition differs from the definition of the active WPs will have the effect that this WP will end itself immediately.
If the parameter NetArea is not defined, the name of the Automation Engine system will be used instead.
You may use any number of net areas. To ensure stability Automic recommends using at least two CPs per net area.
The extended CP selection takes place as follows:
Remember to delete the CP_LIST in the agent's configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied., in case you change the CPs' assignment to the different net areas.
The following use case represents a situation where it is useful to limit the CPs for the CP selection by the agent.
An Automation Engine system is divided into two different networks. Both networks use agents. "Network 1" contains server processes, communications processes CP001, CP002 and CP003 and the databaseA database is an organized collection of data including relevant data structures.. In "Network 2" the CPs CP004 and CP005 are being used. These communication processes serve to connect the agents of "Network 2" with the server processes (CPs + WPs) in "Network 1".The two network areas are separated by a firewall that is configured statically and should only accept known connections.
Illustration 1: NetArea Definition
Illustration 2: Connections between components and the connection directions
Illustration 1 shows the NetArea "InnerNet" and its assignment to the CPs CP001, CP002 and CP003 whereas NetArea "OuterNet" is assigned to CP004 and CP005. Illustration 2 shows the connections between components and their directions, indicated by arrows. The agents of "Network 1" connect exclusively to CPs of NetArea "InnerNet", the agents of "Network 2" connect exclusively to CPs of NetArea "OuterNet". In this case, the agents' connections do not have to be configured in the firewall .
Illustration 2 in addition shows the necessary connections for CP operation in other network zones. For Network 1 only database connections by CPs drawn in red are known. Please note that CP-CP-connections only occur in special cases or are necessary if an agent's registeredThis is the status of a task that runs within a group and is waiting for its start. output file should be displayed by way of the UserInterface, where agent and UI are connected to different CPs. These connections are denoted by red-dotted lines.
Note: In the firewall you only have to configure connections that are known to CP004, CP005, regardless of the number of agents that are used in "Network 2". Connections that must be configured statically are shown as red dots along the firewall line.
In order to ensure that the agents only connect to CP004 and CP005 the following steps are required:
For CP001, CP002 and CP003:
For CP004 and CP005:
The following INI-file parameters must be specified in the Automation Engine:
Network 1:
[GLOBAL]
system=UC4
[TCP/IP]
pwpport=2270
NetArea=InnerNet
[PORTS]
cp1=2217
cp2=2218
cp3=2219
wp1=2271
wp2=2272
wp3=2273
Network 2:
[GLOBAL]
system=UC4
[TCP/IP]
pwpport=2270
NetArea=OuterNet
[PORTS]
cp4=2220
cp5=2221
wp1=2271
wp2=2272
wp3=2273
When you start server processes or agents via the UserInterface's System Overview or by using the scriptA particular Automation Engine object type. element MODIFY_SYSTEM, the WP selects a CP, and the CP contacts the responsible ServiceManager. If the CPs are located in different net areas within the Automation Engine system, this fact is considered for the CP selection.
The following behavior applies:
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |