Changing the Primary Nodes for a Siebel Gateway Cluster

After you have configured and deployed the primary Siebel Gateway and additional nodes for a Siebel Gateway cluster, you can optionally change which service and registry nodes serve as the primary nodes for the cluster. This task is part of Configuring the Siebel Gateway Cluster.

Note the following requirements for using this feature:

You can change the primary node for the Siebel Gateway service, for the Siebel Gateway registry, or both.
You can set the primary service node and primary registry node on two different host computers.
For either operation, the current primary node does not have to be running in order to specify a different node as the primary. The node you are specifying as the new primary must be running.
If you attempt to delete the cluster, this action removes all of the nodes from the cluster hierarchy except the primary service node and primary registry node. You must add additional nodes to the Siebel Gateway cluster before it can function as a cluster again.
Before you can restore a prior release of Siebel CRM, the primary service node and registry node for the Siebel Gateway cluster must be located on the same host computer. Also validate that the applicationcontainer_internal\webapps\gateway.properties file for this primary service node (and for no other node) includes the setting Primed=True. This primary service node must be operational in order to serve as the primary Siebel Gateway node after restoring a prior release. Otherwise, cluster modification might fail and the Siebel Gateway service might go down. See also Requirements for Uninstalling Siebel CRM.

To change the primary node for the Siebel Gateway service

In the Siebel Deployment screen in Siebel Management Console, navigate to the Hierarchy - Gateway Service Cluster view.

For more information about this screen, see Siebel Management Console Screens. Under Gateway Service, the primary service node within this cluster is shown with bold text.
Select the node that you want to designate as the primary service node.
Click the Primary button.

A dialog box prompts you to confirm that you want to designate this node as the primary service node for the cluster.
Click OK to confirm this change.

An alert box indicates that the change has been made.
Click OK again.

The Siebel Deployment screen appears again, which includes the cluster for which you changed the service node.

To change the primary node for the Siebel Gateway registry

In the Siebel Deployment screen in Siebel Management Console, navigate to the Hierarchy - Gateway Registry Cluster view.

For more information about this screen, see Siebel Management Console Screens. Under Gateway Registry, the primary registry node within this cluster is shown with bold text.
Select the node that you want to designate as the primary registry node.
Click the Primary button.

A dialog box prompts you to confirm that you want to designate this node as the primary registry node for the cluster.
Click OK to confirm this change.

An alert box indicates that the change has been made.
Click OK again.

The Siebel Deployment screen appears again, which includes the cluster for which you changed the registry node.

To change the primary node for the Siebel Gateway service

To change the primary node for the Siebel Gateway registry

Related Topics