Integration Server 10.3 | Clustering Guide | An Overview of Clustering | Client Applications
 
Client Applications
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. Integration Server clustering provides failover capabilities only to HTTP-based webMethods clients, such as those clients built using the webMethods Context and TContext classes.
When a client connects to a server in a cluster by calling the Context or TContext class, the server returns information about the other servers in the cluster to the client. To improve failover capability, before your client calls Context or TContext, have your client issue the setRetryServer method in that class to specify another server to try in case the first server the client tries to connect to is unavailable.
You can use setRetryServer in a stateful cluster, and in a stateless cluster if your application does not require features that are not supported by stateless clusters. If a request is not processed, the client can use this information to connect to another server in the cluster to have the request fulfilled. In a stateful cluster, the server returns a list of cluster members to the client, which can then automatically switch to other servers if the one it is connected to becomes unresponsive.
Note:
You can use the setAllowRedir method in the Context class on each client to specify whether the client should connect to other servers in the cluster after a connectivity failure.
No special processing is required in your clients.