Network Deployment (Distributed operating systems), v8.0 > Applications > Messaging resources > Interoperation with WebSphere MQ > Interoperation using the WebSphere MQ messaging provider
Network topologies: Interoperating by using the WebSphere MQ messaging provider
There are several network topologies, clustered and not clustered, that allow WAS to interoperate with WebSphere MQ by using WebSphere MQ as an external JMS messaging provider. For providing high availability, some topologies are more suitable than others.
For completeness, this topic describes a wide range of topologies, including clustered and highly available topologies. Note that, for clustering and high availability, use the network deployment or z/OS version of the product.
In this topic "application server" refers to an application server that is running on WAS and "queue manager" refers to a queue manager that is running on WebSphere MQ.
The WAS high availability framework eliminates single points of failure and provides peer to peer failover for applications and processes running within WAS. This framework also allows integration of WAS into an environment that uses other high availability frameworks, such as High Availability Cluster Multi-Processing (HACMP), in order to manage non-WAS resources.
The following examples show the main network topologies for interoperating withWebSphere MQ using the WebSphere MQ messaging provider. Each of the four examples describes two network topologies, with varying locations for the application servers and queue managers.
- Interoperation when WAS application server is not clustered and WebSphere MQ queue manager is not clustered
- The application server and the queue manager run on different hosts
- The application server and the queue manager run on the same host
- Interoperation when WAS application servers are clustered but WebSphere MQ queue manager is not clustered
- The queue manager runs on a different host from any of the application servers
- The application servers run on several hosts, one of which hosts a queue manager
- Interoperation when WAS application servers are clustered and WebSphere MQ queue managers are clustered
- The queue managers run on different hosts from the application servers
- The queue manager runs on the same hosts as the application servers
- Connect WAS application servers to WebSphere MQ for z/OS with queue-sharing groups
- The application servers and the queue managers run in the same LPAR
- The application servers and the queue managers run in different LPARs
Concept topic