Resolution:
Description:
============
Making a clustered pair of BW engines listening to a topic behave as a load balanced pair so that they alternate messages to be processed. Both the engines are processing the same messages now.

Environment:
===========
All BW versions.
  
Resolution:
==========
Topics are similar to broadcast.  loadbalancing or distributed behavior cannot be achieved cannot be achieved when there are multiple JMS Topic subscribers as they will all receive the same message. It is not possible to make each one receive a different message as distributed RV behavior.

A Bridge can be set up for topics to queue and on the BW side you can have a JMS queue receiver. This way it can receive different messages in a load balanaced manner. You can have multiple engines to have multiple receivers.

Example: On the EMS server side, bridge configuration file "bridges.conf" will have  the settings and the EMS server should pass topic messages to this queue similar to the following:

[topic:source.topic]
  queue=target.queue

On the BW application side, you will configure your JMS queue receiver to listen to this target.queue. Deploy the clustered instances of this BW application and you will see each BW instance alternating messages and processing them.