Configuring multiple integration gateway instances

Service Desk Integration Gateway (SDiG) provides manual load balancing and a failover mechanism when multiple instances of SDiG are employed. The mcell.dir file has a unique gateway definition entry for each instance of a SDiG. 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 SDiG requires configuration changes in the Service Desk integration module and the BMC Impact Manger cell.

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


Configuring the 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:

  • UNIX
    ./ instanceName port encryptionKey
  • Microsoft Windows
    create_instance instanceName port encryptionKey 
    On Windows computers, the script creates a service for each additional instance of SDiG. The service name is in the following format: IBRSDInstanceName.

    For example, the following command creates a service named IBRSDinst1 and adds the entry inst1 to the ibrsdinstances file: 

    create_instance inst1 9898 key1

    The instance name is inst1, the port number is 9898, and the encryption key is key1.

Configuring multithreading


This configuration is needed if you are using the new Service Desk Integration Gateway (SDiG).

To increase your system performance, you need to increase the number of threads used for processing. Perform the following:

  1. Open the IBRSD_HOME/conf/IBRSD.conf file for editing.
  2. Enter the required values for the ThreadPool.initialSize and ThreadPool.maxSize properties.

    ThreadPool.initialSize = 2
    ThreadPool.maxSize = 5
  3. Save the file.

Configuring the BMC TrueSight Infrastructure Management cell for running multiple instances

Perform the following procedure to propagate events to different SDiG instances:

To configure a cell for multiple SDiG instances

  1. In the mcell.dir file of the cell, add the SDiG entry.
  2. Configure propagation policies to route events to specific integration instances of SDiG.
    For example, you can configure one propagation policy to send all PATROL events to Instance1 of SDiG, and configure another propagation policy to send all IBM Tivoli events to Instance2 of SDiG. 

    For information about creating propagation policies, see Creating event management propagation policies.

  Starting the SDiG instances and the cell

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

  • (Windows) Start SDIG instances from the Windows services.
  • (UNIX) Start each instance of SDIG separately by providing the instance name as a parameter to the script, as in the following example:
    ./ instanceName start

  Querying the status of Service Desk integration gateway instance

To check the status of an SDiG instance, perform one of the following actions, depending on your operating system:

  • (Windows) Open the Services window and verify that the SDiG service exists and is started.
  • (UNIX) Enter the following command:
    ./ instanceName status

Was this page helpful? Yes No Submitting... Thank you