Failure to Connect to the Server in a Non-Clustered Server Configuration

In a non-clustered server configuration, the software redirects business function processing if it cannot connect to the primary server. These steps describe what occurs during the initial stages of an attempt to call a business function to run on an application server:

1. The user calls a business function on a server.

2. The software checks to see if the server has been failed over from the primary server to a secondary server or to the client workstation.

3. If processing has been directed to another server, the software remaps the business function and sends the CallObject message to the secondary server or to the client workstation to run the business function.

4. If the server has not been failed over, the software sends the CallObject message to the original server to run the business function.

In the second phase of business function processing, the software attempts to run the logic on the application server or client workstation. These steps describe what occurs during the second stage of processing:

1. If the business function runs without error, either on the original server or the failover alternative, the request has been processed.

2. If the client workstation request is not successfully processed by the server, the software increments a reconnect counter and attempts one reconnection.

3. If the value on the reconnect counter is greater than 1, the business function fails. If the value on the reconnect counter is not greater than 1, the software reconnects to the server and attempts to run the business function.

4. If the client is unable to reconnect to the server, the request is redirected to a secondary server if one is defined, or to the client workstation if one is not defined.

If cache has been created on the server, the user must exit the application and restart it.