Adding or editing an Integration Service through Central Monitoring Administration

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:

1. Log on to BMC TrueSight Operations Management Console. In the navigation pane, expand Administration and click Central Monitoring Administration. The Central Monitoring Administration opens in a new tab. 
2. In the navigation pane of the Central Monitoring Administration console, click the Servers drawer.
3. Select a Infrastructure Management Server to which you want to add an Integration Service.

4. Click Add, or select an already added Integration Service and click Edit.
   Provide the following details:

   Field	Description
   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: Direct access using TCP/IP Direct access using SSL TCP/IP        If you select the Direct access using SSL TCP/IP option, you must add the pronet.apps.agent.conntype=ssltcp line in the custom/conf/pronet.conf file and then restart the Integration Service.
   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: Use current Integration Service settings—Indicates that the events must be sent to the destination that is configured in the Integration Service. By default, the destination configured in the Integration Service is the cell that is installed with the Integration Service. If the cell is not installed with the Integration Service, the destination is the Infrastructure Management Server cell to which the Integration Service is connected. Cell Name—Indicates the events must be sent to a remote cell. If you select this option, you must also specify the name of the remote cell. Infrastructure Management Server connected to the Integration Service—Indicates that the events must be sent to the Infrastructure Management Server cell. Ensure that you have already added an entry for the remote cell in the mcell.dir file on the Integration Service computer. If you have installed only the Integration Service and not the cell, the mcell.dir file does not exist. You must manually create the following directory path and the mcell.dir file, and add an entry for the remote cell in the file. (Microsoft Windows) integrationServiceInstallationDirectory\BPPMAgent\Agent\server\etc (Solaris or Linux) integrationServiceInstallationDirectory/BPPMAgent/Agent/server/etc Also, create the %MCELL_HOME% environment variable with the following value: (Microsoft Windows) integrationServiceInstallationDirectory\BPPMAgent\Agent\server (Solaris or Linux) integrationServiceInstallationDirectory/BPPMAgent/Agent/server Note 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 /EventSetup/Configuration/ForwardEventsToIS  be set to Yes. For information about pconfig variables, see the BMC PATROL Agent Reference Manual. 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.

5. Click Add.

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:

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:

1. Locate the custom pronet.conf file on the Child Server:
   • (Microsoft Windows) installationDirectory/pw/custom/conf/pronet.conf
   • (UNIX or Linux) installationDirectory\pw\custom\conf\pronet.conf

2. Add or edit the following entries at the end of the file and save the file. Use the appropriate protocol and port number.
   

   pronet.cadmin.protocol=http|https
   pronet.cadmin.port=<userDefinedPort>

where:

• http/https denotes the protocol that you use. For example, if you are using HTTP, pronet.cadmin.protocol=http
• <userDefinedPort> is the port on which the Apache web server is running