Adapter for SAP 10.1 | webMethods Adapter for SAP Documentation | webMethods Adapter for SAP Installation and User’s Guide Documentation | Package Management | Using the 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 within a cluster must have exactly the same version. Also, the same service pack and fixes (updates) must have been applied.
Adapter packages
All adapter packages on one Integration Server should be replicated to all other Integration Servers in the cluster.
Adapter versions
In the cluster, all the adapters for SAP must be the same version, with the same fixes (updates) , the same SAP libraries (versions) applied, and the various "watt.sap.*.*" configuration switches should be identical.
User-defined adapter packages
Each package that you have configured containing adapter connections, adapter services, flow services, listeners, triggers, and notifications for Adapter for SAP, must exist on all Integration Servers in the cluster, so that all Integration Servers in the cluster can handle any given request.
The configuration and settings of all Adapter for SAP connections, adapter services, listeners, triggers and notifications must be identical throughout the cluster.
To ensure consistency, 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 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.
Adapter connections
If you configure a connection to the application server, this connection must appear on all servers in the cluster so that any Integration Server in the cluster can handle a given request identically.
If you plan to use connection pools in a clustered environment, see Considerations When Configuring Connections with Connection Pooling Enabled.
Adapter services
If you configure a specific adapter service, this same adapter service must appear on all servers in the cluster so that any Integration Server in the cluster can handle the request identically.
If you allow different Integration Servers to contain different services, you might not derive the full benefits of clustering. For example, if a client requests a service that resides on only one server, and that server is unavailable, the request cannot be successfully redirected to another server.
See Replicating Packages to webMethods Integration Servers for information about replicating adapter packages, connections, and adapter services across multiple Integration Servers in a cluster.