Using the bridge

Connect to other messaging servers.

A key aspect of the micro broker is its ability to connect to other messaging servers, such as other micro broker or enterprise messaging servers in the back-end of the architecture. This capability is provided by the bridge component within the micro broker. Users can configure the bridge to connect the micro broker to a remote messaging server using a bi-directional link. Messages sent to the micro broker can be routed to the remote broker and messages sent to the remote broker can be routed to the micro broker.

In its simplest form, the bridge allows topics within a micro broker to be mapped directly to topics within the remote broker and/or messages sent to queues within the micro broker similarly to be routed to queues in the remote broker. The bridge allows more complex processing of messages flowing over the bridge by providing a transformation framework. Users can define additional processing logic to be run against each message. For example, the message payload is not modified by the bridge by default but a transformation could be defined to reformat it.

• Components of the bridge
  
• Transmission control
  
• Message routing and transformations
  
• JMS message handling in the bridge
  
• Bridging to a JMS provider using JNDI
  
• Bridging to WebSphere MQ
  
• Administering the micro broker bridge
  This example shows how to obtain a reference to the bridge to define a pipe to a remote broker and add a flow in each direction to send messages between the two brokers.