How messages are passed between service integration and a WebSphere MQ network
When you program a WAS application that interoperates with WebSphere MQ through the default messaging provider and a service integration bus, service integration automatically handles most aspects of the conversion and mapping for messages. Understanding how this process works and the differences between the two environments helps you to program and troubleshoot the applications more effectively.
The basic message conversion process is the same whether the service integration bus is interoperating with WebSphere MQ through a WebSphere MQ link or with a WebSphere MQ server. For further information about different types of messaging with WebSphere MQ links and WebSphere MQ servers, read whichever of the following sections applies to the system's architecture:
Subtopics
- Differences between service integration and a WebSphere MQ network
Applications can use both service integration and WebSphere MQ to convey messages. Service integration messaging uses messaging engines, whereas WebSphere MQ uses queue managers.
- How service integration converts messages to and from WebSphere MQ format
Messages are converted between WebSphere MQ format and service integration format as they flow between the two systems.
- How to address bus destinations and WebSphere MQ queues
To understand how to access a service integration bus destination from WebSphere MQ, and a WebSphere MQ queue from a service integration bus, it is important to understand the different conventions that govern how these two resources are addressed.
- JNDI namespaces and connecting to different JMS provider environments
Interoperation with other JMS systems and clients is more straightforward if the messaging application connections are built using a connection factory and stored in a JNDI namespace. The JNDI namespace insulates the application from provider-specific information, and there are no differences that are significant for programming messaging applications.