WebSphere MQ Adapter 6.5 | webMethods WebSphere MQ Adapter Documentation | webMethods WebSphere MQ Adapter Installation and User’s Guide Documentation | Package Management | WebSphere MQ Adapter in a Clustered Environment | Clustering Considerations and Requirements | Requirements for Each Integration Server in a Cluster
 
Requirements for Each Integration Server in a Cluster
The following table describes the requirements of each Integration Server in a given cluster:
All Integration Servers in a given cluster must have identical...
For Example...
Integration Server versions
All Integration Servers in the cluster must be the same version, with the same service packs and fixes applied.
Adapter packages
All WebSphere MQ Adapter packages on one Integration Server should be replicated to all other Integration Servers in the cluster.
Adapter versions
All WebSphere MQ Adapters in the cluster must be the same version, with the same service packs and fixes applied.
User-defined adapter packages
Each package that you have configured containing adapter connections, adapter services, flow services, listeners, triggers, and notifications for WebSphere MQ Adapter, must exist on all of Integration Servers in the cluster, so that all Integration Servers in the cluster can handle any given request.
To ensure consistency, we recommend that you create all packages on one server, and replicate them to the other servers. If you allow different servers to contain different services, you might not derive the full benefits of clustering. For example, if a client requests a service that resides in only one server, and that server is unavailable, the request cannot be successfully redirected to another server.
For information about replicating packages, see the chapter on managing packages in the webMethods Integration Server Administrator’s Guide for your release.
Note:
If you plan to use connection pools in a clustered environment, see Considerations When Configuring Connections with Connection Pooling Enabled.