Bookshelf Home | Contents | Index | Search | PDF

Siebel Server Installation Guide for Microsoft Windows > Clustering Your Siebel Deployment for Failover >

Testing and Troubleshooting Clustering

---

After you have installed the Siebel Gateway and Siebel Server successfully, use the Cluster Manager program to start and stop the Siebel Server on each node of the cluster.

NOTE:  Depending on the number of Siebel components on a Siebel Server, the resources required to start a Siebel Server can be substantial. Therefore, avoid starting (or bringing online) several Siebel Servers on the same node concurrently.

To verify that Siebel application and the clustering technologies you have implemented are operating correctly

Test each Siebel Server by bringing each node in the cluster online and validate that all enabled components are either running, online, or available.
Test that each component runs on every node on which the Siebel Server is active. For example, run EIM on an empty batch, or run a Workflow Process using the Workflow Simulator.

NOTE:  If a component on a node will not start, examine the Siebel Server log file (SIEBEL_ROOT\enterprises\enterprise-name\siebel-server-name\logs\enterprise-name.siebel-server-name.log) as well as the log files for the component.

If Siebel Remote is installed, check the column APP_SERVER_NAME in the S_NODE table to make sure it contains the Virtual Machine name for all Remote Clients. Test this by performing a database extract and then querying the S_NODE table.
Verify that when a Siebel Remote Server is activated on a node, the hostname remains consistent. If possible have a Siebel Remote user defined and extracted prior to the tests and perform synchronization for the remote user on each node the Siebel Remote Server is made online on.

Bookshelf Home | Contents | Index | Search | PDF