Bookshelf Home | Contents | Index | Search | PDF

Siebel Server Installation Guide for Microsoft Windows > Clustering Your Siebel Deployment for Failover > Installing Siebel eBusiness Applications with MSCS >

Clustering the Siebel Server with MSCS

---

Follow the procedure below to cluster your Siebel Servers unless your database is Oracle and you are configuring an active-active cluster, as discussed under Active-Active Configuration. In the latter case, see Active-Active Server Clustering With Oracle Database for instructions.

NOTE:  If installing multiple Siebel Servers on a cluster (whether or not they are all registered with the cluster solution), select Static port allocation in the Component Port Selection dialog, then specify a unique port number for each component. Components operated by all Siebel Servers on a cluster must use unique port numbers, to ensure that they do not conflict when operating on the same node or Siebel Server.

To cluster the Siebel Server with MSCS

Install the Siebel Server on the primary node.

The Siebel Server must be installed on a clustered disk drive that is a resource in the same cluster resource group in which the Siebel Server resource will run.

For information, see Installing the Siebel Server.

CAUTION:  When configuring the Siebel Server, do not answer, "Yes," to the prompt on the Co-located Siebel Gateway Name Server screen! If you select this option, the Configuration Wizard uses the physical machine name of the node on which installation is being performed. Instead, leave this check box blank and specify the logical host name on the Gateway Name Server Hostname screen.

Move the cluster resource group from the first node to the second node.
Open a DOS command window on the second node and navigate to the drive that belongs to the cluster resource group in which the Siebel Server was installed; for example:

I:\SIEBEL_ROOT\siebsrvr\ADMIN

Enter:

cluster_srvr.bat svcpasswd

where:

svcpasswd is the Windows OS password.

NOTE:  This batch file is created at the time the first node is installed with the gateway. It will configure the second node instance of the Gateway Name server.

Using Cluster Administrator, create a resource for the Siebel Server service within the resource group previously created for the Siebel Server:
Use the following parameters:

Resource Type: Generic Service

Service Name: siebsrvr_Enterprise_Name_hostname

Dependencies: Physical Disk, Network Name, IP Address, Gateway Service (if the Siebel Server is in the same resource group)

NOTE:  The service name must match the name used in the Windows registry under: regedit > HK_LOCAL_MACHINE > SYSTEM > Current Control Set > Services.

Click Use Network Name for computer name.

This concludes the procedure for Windows NT users.

If your platform is Windows 2000, launch Server Manager in command line mode:

NOTE:  Switch back to the first installed node before performing this step. You must do this while the server is running on the first installed node.

Enter the following command:

srvrmgr /e /g /u /p

where:

e = the name of the Enterprise Server to which this cluster resource group belongs.

g = either the cluster group host name for the Siebel Gateway, if the Gateway was clustered, or the machine name for the Siebel Gateway for this Enterprise Server.

u = Siebel Administrator user name, for example, sadmin.

p = Siebel Administrator password.

Set the proper server name by entering the following command:

change param ServerHostAddress = virtualhost_name for server logical_Siebel_Server_Name

where:

virtualhost_name is the name assigned to the logical clustered server constituted of two or more physical servers.

Using Cluster Administrator, test failover by switching the SiebSrvr between cluster nodes.

To uninstall a clustered Siebel Server in MSCS environment

Make sure that the Siebel Server is running on the primary node, then follow the standard uninstallation procedures. For instructions, see Uninstalling Siebel eBusiness Applications.

NOTE:  If the Siebel Server is not running on the primary node, you must switch it there.

To uninstall the second node for Siebel Server:
Open a command prompt session on the same node.
Navigate to the \BIN subdirectory of the Siebel Server installation directory.
Execute the SiebCTL.exe utility using the following command:

siebctl -d -S siebsrvr -i "Siebel Enterprise Name_Siebel Server Name"

where:

Siebel Enterprise Name is the name of the Enterprise Server into which the Siebel Server was installed.

Siebel Server Name is the name of the Siebel Server.

For example, siebctl -d -S SiebSrvr -i MerlinEnt_MerlinSrv

NOTE:  Make sure spacing before and after each parameter is correct. The -i parameter is required for removing the Siebel Server on the second node.

Uninstall the first node following the standard uninstallation procedures. For instructions, see Uninstalling Siebel eBusiness Applications.

To troubleshoot a clustered Siebel Server

Make sure the Siebel Server can be brought online on each node in the cluster using the cluster manager for your clustering solution.
Using Siebel Server Manager, verify all enabled components are either running, online, or available.

NOTE:  Depending upon the number of Siebel components that are enabled on a Siebel Server, the resources (CPU and memory) required to start up a Siebel Server can be substantial. Therefore, avoid starting several Siebel Servers on the same node concurrently.

Verify that you can run the components on every node on which the Siebel Server can be made online. For example, run EIM on an empty batch, or run a Workflow Process using the Workflow Simulator.
If you are not able to start a component on a node, 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 related log files for the component.
If you have installed Siebel Remote, verify the following:
The column APP_SERVER_NAME in the table S_NODE contains the Virtual Machine name for all Remote Clients. Test this by performing a database extract and then querying the S_NODE table.
The DockConnString parameter in the remote client cfg file is referencing the Virtual Server Name. This must be configured properly to ensure remote synchronization works after a cluster failover.
When a Siebel Remote Server is made active on a node, the hostname remains consistent. If possible, have a Siebel Remote user defined and extracted prior to the test and perform synchronization for the remote user on each node the Siebel Remote Server is made online.

Active-Active Server Clustering With Oracle Database

If your database is Oracle and you will be clustering the Siebel Server, using active-active configuration, use the following procedure.

To cluster the Siebel Server in active-active configuration

Install the Siebel Server on the primary node.

This creates an ODBC datasource called SiebSrvr_siebel.

Move the cluster resource group from the first node to the second node.
From the first installed node, open a DOS command window and navigate to the drive that belongs to the cluster resource group in which the Siebel Server was installed; for example:

E:\SIEBEL_ROOT\siebsrvr\ADMIN

Enter:

cluster_srvr.bat svcpasswd

where:

svcpasswd is the Windows OS password.

NOTE:  This batch file is created at the time the first node is installed with the gateway. It will configure the second node instance of the Gateway Name server.

Using Cluster Administrator, create a resource for the Siebel Server service within the resource group previously created for the Siebel Server.
Use the following parameters:

Resource Type: Generic Service

Service Name: siebsrvr_Enterprise_Name_hostname

Dependencies: Physical Disk, Network Name, IP Address, Gateway Service (if the Siebel Server is in the same resource group)

NOTE:  The service name must match the name used in the Windows registry under: regedit > HK_LOCAL_MACHINE > SYSTEM > Current Control Set > Services.

Click Use Network Name for computer name.
Install the Siebel Server on the second node in the second cluster resource group, giving it a host name (for example, NSIEBSRVR2).

This second installation overwrites the previous ODBC datasource Siebsrvr_siebel to the new location.

Switch the second cluster resource group from the second node back to the first.
Open a DOS command window and navigate to the drive on which you created that cluster resource group; for example:

I:\SIEBEL_ROOT\siebsrvr\ADMIN

Using Cluster Administrator, create a resource for the Siebel Server service within the resource group previously created for the Siebel Server:
Use the following parameters:

Resource Type: Generic Service

Service Name: siebsrvr_Enterprise_Name_hostname

Dependencies: Physical Disk, Network Name, IP Address, Gateway Service (if the Siebel Server is in the same resource group)

NOTE:  The service name must match the name used in the Windows registry under: regedit > HK_LOCAL_MACHINE > SYSTEM > Current Control Set > Services.

Click Use Network Name for computer name.
Enter:

cluster_srvr.bat svcpasswd

where:

svcpasswd is the Windows OS password.

NOTE:  This batch file is created at the time the first node is installed with the gateway. It will configure the second node instance of the Gateway Name server.

Launch the ODBC Data Source Administrator and click the System DSN tab.
Add a new ODBC system DSN datasource, giving it a different name; for example, SiebSrvr_NSIEBSRVR2.

When finished, close out of the ODBC Data Source Administrator utility.

Launch Server Manager in command line mode and enter the following command:

change param connect = new system DSN datasource name for server first_cluster_resource_host name

where:

first_cluster_resource_host name =the name you gave the host in Step 6 above.

For more information about using Server Manager, see the Siebel Server Administration Guide.

Switch the cluster resource group from the first node to the second.
Using the drive described in Step 3 as an example, navigate to E:\SIEBEL_ROOT\siebsrvr\temp\ and make a backup copy of SiebelOdbc.dsn by saving it with a different name.
Edit SiebelOdbc.dsn by globally replacing all references to SiebSrvr_siebel to the new system DSN datasource name (for example, SiebSrvr_NSIEBSRVR2) and save the file.
Open a DOS command window and enter:

regedit SiebelOdbc.dsn

Exit DOS.

Bookshelf Home | Contents | Index | Search | PDF