Server clustering is almost transparent to the client. A client can issue requests to a server that is in a clustered environment in the same way it issues a request to a server that is not in a clustered environment.

When a client connects to a server that is in a clustered environment (using the Context class), the server returns information about the other servers in the cluster to the client. In the event that a request is not processed, the client can use this information to connect to another server in the cluster to have the request fulfilled.

Whether you are using the Context or TContext class to communicate with the webMethods Integration Server, the redirection of failed requests is transparent to the client. The logic to handle redirection is in the webMethods Integration Server Context or TContext class.

To improve the failover capability, before your client calls Context or TContext to connect to an Integration Server in the cluster, have your client issue the setRetryServer method in that class to specify another server to try if the first server the client tries to connect to is unavailable.

No special processing is required in your clients.