Choosing messaging providers for a mixed environment
If your existing or planned messaging environment involves both WebSphere® MQ and WebSphere Application Server systems, choose between the default messaging provider, the WebSphere MQ messaging provider, or a mixture of the two, by considering your messaging requirements, your business environment, and the needs of each messaging application.
About this task
For messaging between application servers, with interaction with a WebSphere MQ system, you can use the default messaging provider or the WebSphere MQ provider. Neither provider is necessarily better than the other. The choice of providers depends primarily on factors relating to your business environment and planned changes to that environment, and also on what each JMS application needs to do. Moreover, these two types of messaging providers are not mutually exclusive:
- You can configure both types of providers within one cell.
- Different applications can use the same, or different, providers.
Factors relating to your business environment include the following:
- Messaging requirements
- Existing skill set
- Existing messaging infrastructure
- Planned changes to that infrastructure
Configuring and managing your messaging infrastructure is simpler if you use just one provider. If your messaging is primarily in WebSphere MQ, you should probably choose the WebSphere MQ messaging provider. Similarly, if your messaging is primarily in WebSphere Application Server, you should probably choose the default messaging provider.
DMP). If the application needs to communicate with one or more WebSphere MQ destinations, you can choose any of the following solutions depending upon your business environment, usage scenarios, and system topologies:
- Use the WebSphere MQ messaging
provider (solution
MQP
). - Use the default messaging provider to integrate a WebSphere MQ server (a WebSphere MQ queue manager or queue-sharing
group) as a bus member (solution
DMP interop bus member
). - Use the default messaging provider to integrate a WebSphere MQ network as a foreign bus,
by using WebSphere MQ links (solution
DMP interop, foreign bus
).
For more information about these solutions, see Interoperation with WebSphere MQ: Comparison of key features.
rightsolution. Most requirements have multiple possible solutions, and the absence of an asterisk does not necessarily mean that you cannot use that solution. To derive best guidance from using each of these tables:
- Focus on the rows that reflect your most important requirements.
- For all the rows that you consider, count the number of asterisks for each solution.