Network topologies: Interoperating using the IBM MQ messaging provider

In this topic "application server" refers to an application server running on WebSphere Application Server and "queue manager" refers to a queue manager running on IBM 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.

Example topologies:

• WebSphere application servers not clustered and IBM 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

• WebSphere application servers are clustered but IBM 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

• WebSphere application servers are clustered and IBM 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 WebSphere application servers to IBM 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