Services: DevOps Thought Leadership | JEE Consulting
An application connects to a bus, which is its local bus, and can exchange messages with other applications that connect to the same bus.
If you messaging infrastructure design is such; that you want WebSphere to appear as a Queue Manager to another independent MQ network then you can set up the SIB as such as to provide a gateway approach. You only need to do this is your JEE application running in WebSphere is not going to communicate with the final Queue directly. What I mean here is that the JEE application sends a message to a queue destination on a foreign network, but it does not know where this queue is. All it knows is to place the message in a SIB queue and the SIB will forward on to the gateway Queue Manager of the MQ network and the message with be routed through the MQ network by MQ to the destination Queue Manager and ultimate destination queue. This design is typical of large integrated message platforms.
Conversely it also means that another application in the MQ network which cannot see WebSphere will send messages destined for a queue that is running in the SIB. The MQ gateway Queue Manager will receive these messages from the local Queue Manger that the application directly communicates with, and routes the message to the SIB. Then WebSphere takes over to deliver to the intended queue destination. The final queue could have an EJB.MDB listening which consumes the message
To exchange messages with applications that connect to a WebSphere MQ network, you need a WebSphere MQ link that connects the local bus to a foreign bus that represents a WebSphere MQ network.
Applications that send a message to a queue in a WebSphere MQ queue manager or queue-sharing group can do so directly by configuring a WebSphere MQ server definition, or indirectly by using a WebSphere MQ link. This topic describes the message flow for a WebSphere MQ link.
With a WebSphere MQ link, there is a gateway messaging engine on the service integration bus and a gateway queue manager on the WebSphere MQ network.
Applications that are connected to the local bus send messages to a destination on a foreign bus. The messaging engine that the sending application is connected to on the local bus queues the messages on its link transmitter queue. Service integration flows the messages from the link transmitter queue to the corresponding known link transmitter queue in the gateway messaging engine. Messages then flow to a single sender channel transmitter queue, ready for transmission across the WebSphere MQ link.
The sender channel transmitter transmits messages over the WebSphere MQ link to a gateway queue manager or (for WebSphere MQ for z/OS® only) a queue-sharing group on the remote WebSphere MQ network.
The WebSphere MQ network appears as a foreign bus to the service integration bus and the service integration bus appears as a queue manager to the WebSphere MQ network.
The following figure illustrates an example of the message flow from a service integration bus to a WebSphere MQ network over a WebSphere MQ link.
Figure 1. Message flow between a service integration bus and a WebSphere MQ network
Steve Robinson has been working in IT for over 20 years and has provided solutions for many leading brands around the world. Steve specialises in JEE, DevOps and Thought Leadership.
In January 2013, I was awarded the prestigous 'IBM Champion' accolade.
IBM WebSphere Application Server 8.0 Administration Guide
WebSphere Application Server 7.0 Administration Guide
Contact | Articles | Shell Scripts | Java Code | JACL | Jython | WebSphere MQ | WebSphere Message Broker | WebSphere Blog | © Copyright 2006-2013 Robinson (UK) Limited