WAS v8.5 > End-to-end paths > Messaging resources > Choose a messaging provider

Choose messaging providers for a mixed environment

If wer existing or planned messaging environment involves both WebSphere MQ and WAS systems, choose between the default messaging provider, the WebSphere MQ messaging provider, or a mixture of the two.

For messaging between application servers, with interaction with a WebSphere MQ system, we can use the default messaging provider or the WebSphere MQ provider.

These two types of messaging providers are not mutually exclusive. We 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:

Configuring and managing your messaging infrastructure is simpler if we use just one provider. If wer messaging is primarily in WebSphere MQ, you should probably choose the WebSphere MQ messaging provider. Similarly, if your messaging is primarily in WAS, you should probably choose the default messaging provider.

If wer business environment does not clearly indicate that you should use just one provider, then you should consider using a mixture of the two, and choosing the most appropriate messaging provider for each application. A useful way of doing this is to identify the types of destinations (service integration bus, or WebSphere MQ queue or topic) the application is using. If the application uses only bus destinations, the natural choice is to use the default messaging provider (solution "DMP"). If the application needs to communicate with one or more WebSphere MQ destinations, we can choose any of the following solutions depending upon your business environment, usage scenarios, and system topologies:

For more information about these solutions, see Interoperation with WebSphere MQ: Comparison of key features.

To help you choose between these solutions, several of the following steps contain tables in which each row represents a business or system requirement, and asterisks (*) indicate the solutions that are likely to be most effective for meeting the requirement. These tables are designed to provide general guidance, rather than to identify precisely a "right" solution. Most requirements have multiple possible solutions, and the absence of an asterisk does not necessarily mean that we cannot use that solution. To derive best guidance from using each of these tables:

The solutions with the largest number of asterisks are likely to be the most effective.

  1. If we have limited experience of WebSphere MQ or WAS, and are trying to decide which product best meets your messaging needs, see Comparison of WAS and WebSphere MQ messaging.

    Whichever of these products you choose as the main focus for the messaging, we can still use either the default messaging provider or the WebSphere MQ provider for interoperation between the products.

  2. Consider your business environment, to see if we can use just one provider.

    In deciding which provider to use, consider the following constraints:

    • The current and future messaging requirements
    • The existing messaging infrastructure
    • The skill set that we have in your organization

    If the majority of your messaging is today performed in WebSphere MQ, continue with that approach and configure WebSphere MQ as an external JMS provider (that is, use the WebSphere MQ messaging provider) in WAS. If the JMS requirements of your WAS applications are limited, it is debatable whether using a service integration bus for those applications gives sufficient benefit.

    If we have messaging applications in WAS that have no requirement to interoperate with your WebSphere MQ network, use the default messaging provider (the service integration bus). If wer WAS messaging requirements demand a tighter integration with WAS, the service integration bus provides the following benefits:

    If we choose to use the default messaging provider to interoperate between service integration and WebSphere MQ, be aware there is an added cost involved in converting messages between service integration format and WebSphere MQ format.

    Also consider the following messaging scenarios:

    • A large installed backbone of WebSphere MQ queue managers, perhaps with WebSphere Message Broker.

      To use WAS to run a newly introduced messaging application, we can deploy a WAS (JMS) messaging application that will exchange messages with an existing application that uses a WebSphere MQ queue or topic.

    • A WAS installation, perhaps with existing web and enterprise applications, but no WAS messaging application.

      If we have no existing messaging infrastructure, we can deploy a WAS (JMS) messaging application to exchange messages with an existing WAS messaging application that uses a service integration bus destination.

    • An infrastructure that uses WAS to connect WAS messaging applications.

      Introduce WAS (JMS) messaging between a pair of WAS applications.

    • An infrastructure that includes both WebSphere MQ and service integration buses. This might be the result of a merger, or because the message traffic tends to be from WAS to WAS, or from WebSphere MQ to WebSphere MQ, but not typically between WAS and WebSphere MQ.

      Deploy a WAS (JMS) messaging application to exchange messages with an application that uses a WebSphere MQ queue or topic.

    • A WebSphere Process Server or WebSphere Enterprise Service Bus infrastructure, which uses Service Component Architecture (SCA).

      Choose either a WebSphere MQ or a service integration bus binding for the SCA components.

  3. If wer business environment does not clearly indicate that you should use just one messaging provider, use a mixture of the two and choose the most appropriate provider for each application, based upon the destination types the application uses.

    The application might need to exchange messages with existing partner applications or services that use one or more known destinations of known type. Alternatively, the partner applications or services might not yet be deployed and the choice of destination type might still be open, in which case the solution architect needs to decide how best to connect the applications or services together.

    If the application uses multiple destinations, there are four possible outcomes:

    If there is no clear business or technical reason why the application uses WebSphere MQ destinations rather than bus destinations, and the partner application is also a WAS JMS application, consider migrating the existing destinations to service integration so the application uses only bus destinations.

  4. If the application uses only bus destinations, configure the application and its JMS resources to use the default messaging provider.

  5. If the application uses only WebSphere MQ destinations (queues or topics), use the following checklist to determine which provider solution to use.

    Provider checklist for an application that uses only WebSphere MQ destinations. The first column of this table lists the checklist questions for the business or system requirements for an application that uses only WebSphere MQ destinations. In the second column, the requirements that are met by the WebSphere MQ messaging provider (MQP) solution are marked with an asterisk. In the third column, the requirements that are met by the default messaging provider bus member (DMP interop, bus member) solution are marked with an asterisk. In the fourth column, the requirements that are met by the default messaging provider foreign bus (DMP interop, foreign bus) solution are marked with an asterisk. In columns two to four, any requirements that are not met by the solution shown in that column are not marked with an asterisk.

    Question: MQP DMP interop, bus member DMP interop, foreign bus
    Is performance critical?

    (If so, use WebSphere MQ directly, rather than perform message conversion.)

    		*
    Does the application have to send or receive large messages (that is, messages > 500k.)? *
    Is location transparency desirable for simplifying programming and deployment of applications? * *
    Does the application have to consume from a WebSphere MQ queue, the configuration of which is fixed?

    (That is, the queue cannot be moved to service integration and we do not want to deploy a push-style WebSphere MQ application to send messages to a bus destination.)

    		* *
    Is the partner application a JMS application that will run outside WAS, as a bus or WebSphere MQ client?

    (Do not mix service integration and WebSphere MQ unless we have to do so; a pure WebSphere MQ or service integration solution is simpler and avoids the cost of converting messages between service integration and WebSphere MQ formats.)

    		*
    Is the partner application a non-JMS (non-WebSphere Application Server) application?

    (Wherever possible choose a pure WebSphere MQ or service integration solution. Use the MQI WebSphere MQ client, or the XMS WebSphere MQ client, or the XMS bus client depending on your API preference.)

    		*
    Do you prefer traffic passing between your WebSphere MQ network and WAS applications to be funneled into a single long-running connection? *
    Do to use the high availability features of WAS? *
    Is XA two-phase commit (2PC) needed between the application and a WebSphere MQ queue-sharing group? * See 1 * See 2
    Is XA two-phase commit (2PC) needed between the application and a WebSphere MQ cluster? *
    Are you using the WebSphere Enterprise Service Bus to mediate messages from, or deliver them to, a WebSphere MQ queue?

    (For example, using WebSphere Business Integration adapters, or connecting to a service provider such as CICS .)

    		*
    Does the application have to consume from a WebSphere MQ queue, the configuration of which is fixed?

    (that is, the queue cannot be moved to service integration and we don't want to deploy a push-style WebSphere MQ application to send messages to a bus destination.)

    		* *  

    • 1 Provided that WebSphere MQ v7.0.1 is used.
    • 2 XA two-phase commit can be used with the WebSphere MQ link, but it only covers the sending of the message to the WebSphere MQ link. It does not cover the subsequent sending of the message from the WebSphere MQ link to a WebSphere MQ queue manager using store and forwards.

  6. If the application uses a mixture of bus and WebSphere MQ destinations, for example consuming from service integration and sending to WebSphere MQ, then either of the default messaging provider interoperation models can support this using a single connection factory or activation specification. Use the following checklist to help decide between a bus member and a foreign bus solution.

    Provider checklist for an application that uses a mixture of bus and WebSphere MQ destinations. The first column of this table lists the checklist questions for the business or system requirements for an application that uses a mixture of bus and WebSphere MQ destinations. In the second column, the requirements that are met by the default messaging provider bus member (DMP interop, bus member) solution are marked with an asterisk. In the third column, the requirements that are met by the default messaging providerforeign bus (DMP interop, foreign bus) solution are marked with an asterisk. In columns two and three, any requirements that are not met by the solution shown in that column are not marked with an asterisk.

    Question: DMP interop, bus member DMP interop, foreign bus
    Does the application have to consume from a WebSphere MQ shared queue? *
    Do you prefer traffic passing between your WebSphere MQ network and WAS applications to be funneled into a single long-running connection? *
    Do you need distributed WebSphere MQ in versions earlier than WAS v7 and WebSphere MQ v7? *
    Do you want store and forward capabilities to allow the application to continue to send messages when the WebSphere MQ queue manager is unavailable? *
    Do you prefer not to configure server connection channels?

    (This is because they open a port, which might be seen as a security risk.)

    		* See 1
    Do you prefer to define a server connection channel, rather than a pair of sender and receiver channels? *
    Do you only want to use bindings connections? *  

  7. If the destination types are not yet known, decide the relative priorities of the known concerns then use the following checklist to assess how well each of them is addressed by the possible provider solutions.

    The underlying choice is what type of destinations this application should use. The destination types are not yet fixed, so any of the four solutions is possible, but as a general rule you should aim for solution "DMP" or "MQP", because a pure WebSphere MQ or service integration solution is simpler and avoids the cost of converting messages between service integration and WebSphere MQformats.

    Provider checklist for an application for which the destination types are not yet known. The first column of this table lists the checklist questions for the business or system requirements for an application for which the destination types are not yet known. In the second column, the requirements that are met by the default messaging provider (DMP) solution are marked with an asterisk. In the third column, the requirements that are met by the WebSphere MQ messaging provider (MQP) solution are marked with an asterisk. In the fourth column, the requirements that are met by the default messaging provider bus member (DMP interop, bus member) solution are marked with an asterisk. In the fifth column, the requirements that are met by the default messaging provider foreign bus (DMP interop, foreign bus) solution are marked with an asterisk. In columns two to five, any requirements that are not met by the solution shown in that column are not marked with an asterisk.

    Question: DMP MQP DMP interop, bus member DMP interop, foreign bus
    Do we have an existing base of strong skills in managing WebSphere MQ? * * *
    Do you want management of all messaging to be handled by the WebSphere MQ team? *
    Do we have administrators skilled in WAS but not in WebSphere MQ? *
    Do you want a messaging product with a large installed base (including references) and a wide choice of ISV tools? *
    Are you reluctant to buy a separately licensed product in addition to WAS? *
    Are you reluctant to install and manage a separate product in addition to WAS? *
    Are you already using WebSphere Message Broker?

    (If so, you need WebSphere MQ anyway).

    		* * *
    Does the application need to send or receive large messages (that is, messages > 500k.)? *
    Is location transparency desirable for simplifying programming and deployment of applications? * * *
    Do the throughput requirements need multiple parallel channels or routes? * * *
    Is the partner application a JMS application that will also run in WAS?

    (Service integration runs in the WAS application server. On distributed platforms that means it is in-process. )

    		*
    Is the partner application a JMS application that will run outside WAS, as a bus or WebSphere MQ client?

    (Do not mix service integration and WebSphere MQ unless we have to do so; a pure WebSphere MQ or service integration solution is simpler and avoids the cost of converting messages between service integration and WebSphere MQ formats.)

    		* *
    Is the partner application a non-JMS (non-WAS) application?

    (Wherever possible choose a pure WebSphere MQ or service integration solution. Use the MQI WebSphere MQ client, or the XMS WebSphere MQ client, or the XMS bus client depending on your API preference.)

    		* *
    Is maintenance of strict message order important? *
    Does the application require the flexibility and convenience of a WebSphere MQ cluster?

    (WebSphere MQ clustering makes administration simpler and provides selective parallelism of clustered queues. That is, instances of a clustered queue can be created on any (but not necessarily all) queue managers in the WebSphere MQ cluster. Messages sent to the clustered queue can be addressed to a specific instance of the queue, or allowed to select an instance dynamically based on workload management statistics. clustering provides some of this flexibility, but we cannot create partitions of a bus destination on a subset of the messaging engines in a cluster bus member.)

    		* * *
    Does the application need the level of high availability provided by WebSphere MQ for z/OS shared queues? * * *
    Do to use the high availability or scalability features of WAS clustering? * * *


Subtopics


Related concepts:

Introduction: Messaging resources
Interoperation with WebSphere MQ: Comparison of key features


Related


Manage messaging with the WebSphere MQ messaging provider
Manage messaging with the default messaging provider


Reference:

Comparison of WAS and WebSphere MQ messaging


+

Search Tips   |   Advanced Search