Using Central Monitoring Administration, you can add Integration Services to Infrastructure Management Servers and manage them.
To add or edit an Integration Service, perform the following steps:
Provide the following details:
|Integration Service Name||Name for the Integration Service. The name must be unique for each server to which you want to add the Integration Service.|
|Infrastructure Management Server||Name of the server to which you want to add the Integration Service|
|DNS Name / IP Address||Name or the IP address of the host where the Integration Service runs|
|Connection to Infrastructure Management Server||Communication protocol between the Integration Service and the Infrastructure Management Server. The supported connection types are as follows:|
If you select the Direct access using SSL TCP/IP option, you must add the
|Port Number||Port number through which the Integration Service listens to the Infrastructure Management Server. The default port number is 12124.|
|Events Destination||Destination where you want the Integration Service to send the events that are received from the BMC PATROL agents. The supported destination types are as follows:|
Event settings on the BMC PATROL Agent override the event destination settings on the Integration Service. For example, on a BMC PATROL Agent, if the specified event destination is a cell, the Integration Service sends events to the specified cell, irrespective of the setting specified in the Events Destination option.
Events are routed through the Integration Service to the Infrastructure Management Server cell or the remote cell using port number 3183 (default port) or the Staging Adapter port number that you specified while installing the Integration Service. BMC recommends that the PATROL Agent pconfig variable
The Events Destination is the setting at the Integration Service. Even when you select the default Use current Integration Service settings option, the events destination changes to one of the other two options during subsequent edits. If you want to change the event destination of the Integration Service from the Infrastructure Management Server connected to the Integration Service option to the remote cell or the Integration Service local cell, select the Cell Name option. Selecting the Use current Integration Service settings option falls back to the Infrastructure Management Server connected to the Integration Service option.
|Integration Service Cluster Name||Name of the Integration Service cluster to which you want to add the Integration Service|
You also have the option to create a new cluster. Click New to add a new Integration Service cluster. For more information about adding a new Integration Service cluster, see Managing an Integration Service cluster through Central Monitoring Administration.
|Is Staging Integration Service||Indicates whether the Integration Service is a staging Integration Service|
A staging Integration Service is an interim Integration Service that is used as the initial phone home for the BMC PATROL Agents. The final phone home settings are set for the BMC PATROL Agents through the staging policies.
Note: If an Integration Service is already part of an Integration Service cluster, you cannot set it as a staging Integration Service.
The Integration Service is added to the Infrastructure Management Server and is displayed in the Integration Services area. A staging Integration Service is denoted by the icon as shown in the following figure:
When you convert a staging Integration Service to a normal Integration Service, the icon is not removed in the Integration Services area. You must refresh the page for the icon to be removed.
If the Apache ports on the Central Server are changed after the Child Server is registered, perform the following steps to display the new added Integration Service details:
Add or edit the following entries at the end of the file and save the file. Use the appropriate protocol and port number.
If a Central Server is installed on a custom RMI port and not on the default port 1099, the communication from the Child Servers to the Central Server fails.
Workaround: In the <installation directory>\pw\custom\conf\pronet.conf file, add the property
pronet.cadmin.usejmsforcmastatus=true for all the Child Servers connected to the Central Server.