LAST MODIFIED DATE: June 17, 2008

VERSION: This applies to Exceed onDemand version 6 and higher.

PROBLEM:

When a working Exceed onDemand client is attempting to connect to an Exceed onDemand cluster where the Preferred Cluster Manager (PCM) is down, how does the Exceed onDemand Client identify which host to attempt to connect to?

SOLUTION:

Exceed onDemand handles this type of scenario and automatically redirects the connection to a new node. This is transparent to the end users.

During your first connection to the cluster, a list of all the hosts is created/stored in a file called clusterhosts.txt and stored on the client side. The clusterhosts.txt file can be found under:
(%APPDATA%\Hummingbird\Connectivity\6.00\Exceed onDemand\Client\)

If for some reason the Primary Cluster manager goes down, the Exceed onDemand Client will then access this file and query the next host in the list and continue onwards through the list until the new Primary Cluster Manager responds.

If the Primary Cluster Manager goes down and the Exceed onDemand Client has never connected to the PCM, the Clusterhosts.txt file is never created. In this situation the administrator has two options:

1. To input any other Exceed onDemand Host address from the cluster into the Host address.
   The Exceed onDemand Host contacted will redirect the Client to the new PCM if it is not the PCM.
2. As part of the Exceed onDemand client install, the administrator can manually add the Clusterhosts.txt file to the Client. Location:
   (%APPDATA%\Hummingbird\Connectivity\6.00\Exceed onDemand\Client\)
   This will allow the Exceed onDemand Client to then query the next host in the list until it finds the PCM.