1. Installation Guide
  2. Restoring the Siebel Gateway Cluster Topology

Restoring the Siebel Gateway Cluster Topology

Your Siebel Gateway cluster topology could, in rare situations, get out of sync with the Siebel Application Interface, leading to an inability to connect to a Siebel Gateway. This problem can occur only when you have taken down the primary Siebel Gateway service node and removed it from a cluster. In order to prevent a situation where no valid Siebel Gateway connection information is available following a Siebel CRM update installation, an upgrade sequence is provided that resolves the described problem. This task is part of Configuring the Siebel Gateway Cluster.

The file cgclientstore.dat, located in SIEBEL_AI_ROOT\applicationcontainer_external\webapps on the Siebel Application Interface, is a runtime file that is created when the Siebel Gateway cluster is first created. In normal operation, this file contains the names of all of the Siebel Gateway service nodes (Tomcat instances) that are currently running, and provides connection information for a running instance in response to requests. These three nodes would include, for example:

  • The primary Siebel Gateway service node, from which the Siebel Gateway was bootstrapped. For example, this node might be GTWY1.

  • Additional Siebel Gateway service nodes that were added as part of a cluster. For example, these nodes might be GTWY2 and GTWY3.

The applicationinterface.properties file, located in SIEBEL_AI_ROOT\applicationcontainer_external\webapps on the Siebel Application Interface, includes the following entry, where GTWY1 represents the primary Siebel Gateway service node. The CGHostURI parameter setting provides a backup source for connection information for a running Siebel Gateway service node, in case cgclientstore.dat is empty. The following is an example value for CGHostURI, allowing connection to GTWY1:

CGHostURI=https://GTWY1.us.oracle.com:4431/siebel/v1.0/cloudgateway

Assume, for this troubleshooting scenario, that the customer has taken down GTWY1 and removed it from the cluster. In that case, CGHostURI indicates an invalid Siebel Gateway service node. When you update to the current Siebel CRM release, you must follow the upgrade sequence here to avoid a case where cgclientstore.dat is empty and CGHostURI points to an invalid node.

  1. Install Siebel CRM for all Siebel Gateway nodes before you update any other modules.

  2. Stop the Siebel Gateway service instances that start automatically following installation.

  3. Start the Siebel Gateway registry instances.

  4. Start the Siebel Gateway service instances.

  5. Install Siebel CRM for all Siebel Application Interface instances, Siebel Servers, and so on.

When you perform the update in this sequence, then cgclientstore.dat is repopulated with connection information for running instances of Siebel Gateway service node, in response to requests. For more information about starting and stopping the Siebel Gateway, see Starting the Siebel Gateway. See also the information about starting and shutting down a Siebel CRM deployment, located in Siebel System Administration Guide.

Related Topics

Changing the Primary Nodes for a Siebel Gateway Cluster

Related Books

Siebel System Administration Guide