8.0 Configuring Multiple Instances of the Sentinel Driver

If you have more than one instance of the Sentinel driver, additional configuration is required. Each driver instance must have a unique identifier value.

  1. Set a unique value in the Sentinel Driver Instance Identifier GCV. For more information, see Sentinel Driver Instance Identifier.

    We recommend using 1, 2, 3, etc. for the unique identifier value.

  2. If you are using Sentinel RD, skip to Step 3. Otherwise, create three new queues based on the Sentinel Driver Instance Identifier.

    1. In the Sonic Management Console, select Configuration tab, then expand the Brokers folder.

    2. Expand esecBroker, then select Queues.

    3. Right-click a queue, then select New Queue.

    4. Specify pubReceiveEvent-n in the Name field.

      The n is the unique identifier value that you set in Step 1.

    5. Click OK to create the new queue.

    6. Repeat Step 2.c through Step 2.e twice more. Use the names of pubReceiveEventResponse-n and subReceiveResponse-n for each of the new queues.

      The n is the unique identifier value that you set in Step 1.

    7. Close the Management Console.

  3. Create an additional Identity Vault Collector.

    The additional Identity Vault Collector must contain the same unique identifier specified in the Sentinel driver. For more information on creating an Identity Vault Collector, see Section 7.3, Configuring the Identity Vault Collector.

You do not need to create a new connection factory. The existing connection factory can share the connection with multiple queues, as long as the queues contain the unique identifier.