This product was previously named Micromuse Netcool/OMNIBUS. Create an adapter for each instance of a Netcool object server on the network (see Section 2.1, Creating an Adapter). Also modify the adapter properties (see Section A.15, IBM Micromuse Netcool).
If the Netcool user account names do not match the Operations Center user account names, edit the /OperationsCenter_install_path/database/examples/NetcoolAccountMap.properties file. The format for mapping the Operations Center user account names to the corresponding Netcool names is:
formula01=ncool05
Multiple group definitions with the same class or group name cause warning messages to appear in the formula.trc file. Duplicate group names do not display in the Operations Center console.
The Netcool adapter can communicate with the Netcool server using a relay connection to provide secure cross-host communications. The relay connection acts as an intermediary, accepting and delivering messages to one server to another.
All the relay connection components are installed automatically with the Operations Center product. Unzip the /OperationsCenter_install_path/Relay.zip file and use the following instructions to set up the relay connection between Operations Center and the server:
To set up the relay connection between the Operations Center and the Netcool server:
Follow the instructions for installing the relay application in the readme.txt file on the Operations Center CD.
This includes information on modifying the config/relay.properties file.
Configure the Netcool adapter properties that pertain to the relay.
Note the following port requirements for using the relay connection:
The relay requires an open port for relay administration, set in the mosrelay.adminPort property in the config/relay.properties file. This port might not be used for any other purpose.
In addition, configure each relay with its own port for each required listener configuration. Refer to the config/relay.properties file for information on configuring relay listeners.
Each relay is defined by a set of properties prefixed with "mosrelay.<RelayName>", where <RelayName> is the name of the relay. Each relay definition must contain listener properties specifying how client connections are received. For the required listener properties, see the config/relay.properties file.
The mosrelay.<RelayName>.listener.security property specifies the security level for connections accepted on the listener port. The three valid values are:
ssl: All communications are encrypted with SSL.
sslWithClientAuth: SSL with client certification authentication.
unsecured: Cleartext communications.
To support SSL, supply a trusted server certificate for the relay. If not using the default keystore in the /config directory, use the specified properties in relay.properties to point to the appropriate keystore.
Operations Center validates SSL certificate dates and flags certificates with expired dates or dates that are not yet valid.
If using self-signed certificates, the process for creating and trusting certificates is identical to the process for the Operations Center server.
If your relays are configured to verify client certificates, remember that the Operations Center server certificate must also be trusted by the VM running the relay.
On the adapter side, specify the following Netcool adapter properties to transmit communications to/from the Netcool server:
RelayServe: Name of the server on which the relay connection exists.
RelayPort: The port number configured for use by the Netcool adapter for relay communications.
RelaySecurity: The security level for the relay server: SSL or unsecured (meaning use cleartext, which is not case-sensitive).
Note there are three valid values in the config/relay.properties file and two valid settings for the RelaySecurity adapter property.
What is important to remember about these two sets of settings: If the adapter is set to SSL security, the relay can be set to SSL or sslWithClientAuth. The names are not case sensitive.
In the case of sslWithClientAuth, the relay requests and validates the Operations Center server certificate as part of the SSL handshake. In either case, the adapter should be set to SSL.
If the Netcool system contains a large number of alarm columns, but only a few are relevant in Operations Center, configure the Alarm Columns adapter property (see Section A.15, IBM Micromuse Netcool) to load only the selected alarm columns. Operations Center does not mine any other alarm data. This can conserve memory and alarm history storage space.