The main purpose of creating an InterConnection Adapter is to view remote servers and allow users to build distributed views.
Environments that contain multiple management systems, databases, firewalls and other management components have different options for the overall configuration. An InterConnection Adapter (ICA) enables server communications through firewalls.
The InterConnection adapter connection mechanism operates in the same way as the Operations Center console-to-server connection.
It is possible to use the ICA over an HTTPS port. The ICA follows a process of determining the other required ports. If the default of CORBA.bidir=true has not changed in the /OperationsCenter_install_path/html/classes/CORBA.properties file, the server uses one port for bidirectional IIOP communications.
The following sections detail using an InterConnection adapter:
To create an InterConnection Adapter:
Create an adapter for .
For general instructions, see Section 5.1, Creating an Adapter.
Define the adapter properties.
When specifying InterConnection adapter properties (see Table A-32, Operations Center InterConnection Adapter Properties), specify the host name and HTTP port of other Operations Center server. For example, enter Mosserver:8080, or just enter Mosserver because 8080 is the default HTTP port.
The state of the InterConnection Adapter and its elements is not reported to the Operations Center server and because of this, does NOT contribute to the state of the andnodes. InterConnection Adapter element states only propagate to the Service Views ( view) for hierarchy elements.
In addition, many features are NOT available for InterConnection Adapter elements in the hierarchy. For example:
Creation of new element operations.
Pre-existing class-specific operations.
and property pages.
Alarm filters.