Third Party Clustering Software
Windchill supports its own method of clustering which is capable of supporting multiple client facing application server nodes. Load balancer software can be used with the secondary cache servers (application server nodes) to perform fail over clustering. However, there is only a single Main Cache server. Third-party clustering software such as Microsoft Clustering Services can fulfill the requirements for fail over clustering of a monolithic Windchill system or for the Main Cache server.
The following are some of the requirements that fail over clustering software must be capable of handling:
The fail over clustering software must allow the fail over node to fully assume the identity of the system being replaced transparently. Ideally, the systems IP address and host name should match the replaced system.
The fail over system should be able to start the appropriate services necessary. Since only a single Windchill method server can execute queues, it is vital that the replacement system is not running and executing queues while the original system is performing the same task.
If the cluster software decision brings up a fail over depending on conditions that may not be permanent, the cluster software must be able to terminate any processes on the original system smoothly. For example, both systems may be processing queue entries if the following applies:
A condition to prevent the background method server system from responding to the cluster software monitoring.
It started up a new system to replace the original.
The original system began functioning again over time.
Was this helpful?