Bookshelf Home | Contents | Index | Search | PDF

Siebel Analytics Installation and Configuration Guide > Installing the Siebel Analytics Cluster Server Feature >

About the Siebel Analytics Cluster Controller Setup

---

Figure 1 shows a typical small cluster server setup.

Figure 1.  A Typical Cluster Controller Server/Client Setup

As Figure 1 shows, a small cluster consists of the following components:

• The primary cluster controller server
• The secondary cluster controller server
  • Services new ODBC requests
  • Monitors the health of the Siebel Analytics Server nodes that participate in this cluster

When a new ODBC request comes into either the primary or secondary cluster controller server, the following events occur:

• One of the cluster controller servers responds with a Siebel Analytics Server name and port number.
• The ODBC client uses this returned Siebel Analytics Server name and port number to connect to the Siebel Analytics Server directly.
• The ODBC request goes through the Siebel Analytics Server CLIENT_SERVER_PORT (9703 in Figure 1).
• The session assignment goes to the primary cluster controller's CLIENT_CONTROLLER_PORT (9706 in Figure 1).

The cluster controller servers monitor the Siebel Analytics Server nodes' health by using a heartbeat mechanism through TCP/IP to verify that the Siebel Analytics Server node is still functioning properly.

• The Siebel Analytics Server node includes a Server Manager and Siebel Analytics Server.
• The Server Manager starts, stops, and restarts the Siebel Analytics Server on behalf of the cluster controller server.
• Each Siebel Analytics Server node loads the repository, so that the server knows from which database to get data.

Bookshelf Home | Contents | Index | Search | PDF