Configuring multiple Integration for BMC Remedy Service Desk instances

Integration for BMC Remedy Service Desk provides manual load balancing and a failover mechanism when multiple instances of Integration for BMC Remedy Service Desk are employed. The mcell.dir file has a unique gateway definition entry for each instance of Integration for BMC Remedy Service Desk. If one of the gateways becomes nonfunctional, the other gateways can be tried in a defined sequence until the event is propagated successfully.

Running multiple instances of Integration for BMC Remedy Service Desk requires configuration changes in the Integration for BMC Remedy Service Desk integration module and the BMC Impact Manger cell.

A script (create_instance.sh for UNIX; create_instance.bat for Windows) creates an Integration for BMC Remedy Service Desk instance and a file named ibrsdinstances in the IBRSD_HOME/bin directory that contains the names of all new instances.

Configuring the Integration for BMC Remedy Service Desk integration module for running multiple instances

From a command line, navigate to the IBRSD_HOME/bin directory and enter one of the following commands, depending on your operating system:

• UNIX:
  ./create_instance.sh instanceName port encryptionKey
• Microsoft Windows:
  create_instance instanceName port encryptionKey 
  
  On Windows computers, the script creates a service for each additional instance of Integration for BMC Remedy Service Desk. The service name is in the following format: IBRSDInstanceName. For example, if you have created an instance, ibrsd1, the service name would be IBRSDinst1.
  
  For example, the following command creates a service named IBRSDinst2 and adds the entry inst2 to the ibrsdinstances file:
  
  create_instance inst2 9898 key1
  
  The instance name is inst2, the port number is 9898, and the encryption key is key1.

Configuring the cell for running multiple instances

Perform the following procedure to propagate events to different Integration for BMC Remedy Service Desk instances:

To configure a cell for multiple Integration for BMC Remedy Service Desk instances

1. In the mcell.dir file for the cell, add the Integration for BMC Remedy Service Desk gateway entry.
2. Configure propagation policies to route events to specific integration instances of Integration for BMC Remedy Service Desk.
   For example, you can configure one propagation policy to send all PATROL events to Instance1 of Integration for BMC Remedy Service Desk, and configure another propagation policy to send all IBM Tivoli events to Instance2 of Integration for BMC Remedy Service Desk.
   
   For information about creating propagation policies, see Creating event management propagation policies.

Starting the Integration for BMC Remedy Service Desk instances and the cell

Perform one of the following actions, depending on your operating system:

• Microsoft Windows: Start Integration for BMC Remedy Service Desk instances from the Windows services.
• UNIX: Start each instance of Integration for BMC Remedy Service Desk separately by providing the instance name as a parameter to the ibrsd.sh script, as in the following example:
  ./ibrsd.sh instanceName start

Querying the status of an Integration for BMC Remedy Service Desk instance

To check the status of an Integration for BMC Remedy Service Desk instance, perform one of the following actions, depending on your operating system:

• Microsoft Windows: Open the Services window and verify that the Integration for BMC Remedy Service Desk service exists and is started.
• UNIX: Enter the following command:
  ./ibrsd.sh instanceName status