The ComAgent establishes the following connections:
- Automatic connections between all MPs having the same parent OAM server pair
- Automatic connections between MPs that have different parent OAM servers, according to application-specific connection configuration rules. The application-specific connection configuration rules are provided with the system and augment the configuration rules built in to ComAgent.
- Manually configured connections between MPs and remote servers
The automatic and configured connections can be grouped together as Connection Groups. Inserting Remote Server entries establishes connections to the servers.
Remote Servers are configured using the
Communication Agent > Configuration > Remote Servers GUI pages. The most important attribute of a Communication Agent Remote Server is an IP Address that can be reached via a server’s
Internal Management Interface (
IMI). The IP address uniquely identifies the Remote Server and provides the means by which Communication Agent can establish transport connections to/from the Remote Server. The Remote Server attributes include:
- Name
- IP Address
- Connection Mode: {client, server}
- Local Server Group: group of servers that should connect to the Remote Server
Note: Use and to perform this configuration.
The pages provide a way for you to create and configure Remote Servers and Connection Groups, and to assign a Connection Group to the services.
By default, Communication Agent has the “Remote Servers” and “Connection Status” screens enabled.
The configuration is performed in the following order:
- Remote Servers
- Connection Groups
- Routed Services
Note: Default configuration of Routed Services has a pre-defined Connection Group associated with it. This screen can be used to manage user-defined Connection Groups associated with the service.