Siebel Remote and Replication Manager Administration Guide > Implementing Replication Manager >

Installing Servers and File Systems on the Regional Node

To install the regional node, you must configure a new Siebel Enterprise Server on the regional node that contains a name that is different from the name that the headquarters node uses. For more information, see About the Siebel Enterprise and the Siebel Enterprise Server.

To install servers and file systems on the regional node

1. Install the Siebel Name Server.

   For more information, see the following items:

   • Requirements for Connectivity with the Siebel Name Server
   • Siebel Installation Guide for the operating system you are using
   • Siebel System Administration Guide
2. Install the ODBC driver that the RDBMS vendor uses for your implementation.

   For more information, see Requirements for the ODBC Driver.

3. Install the Siebel Server.

   When the Siebel Server installation program prompts you, make sure you specify the correct connectivity information for the Siebel Name Server, Siebel File System, and Database Configuration Utilities on the regional node. Each regional node must be associated with a unique Siebel Enterprise Server name. For more information, see Requirements for Installing the Siebel Server on the Regional Node.

4. Install the Database Configuration Utilities.

   Configuring the Database Configuration Utilities on the regional node is very different from setting it up on the headquarters node. For more information, see Installing the Server Database Configuration Utilities on the Regional Node.

5. Install the Siebel File System.

   For more information, see Installing the Siebel File System on the Regional Node.

For more information on installing these components, see the Siebel Server installation guide for your operating system.

Requirements for Connectivity with the Siebel Name Server

You must install and make sure the Siebel Name Server is running before you install the regional node. The Siebel Name Server includes a persistent store that includes configuration parameters and run-time information. This name server is part of the Siebel Gateway. Each Siebel Server accesses the name server at start up and periodically while the Siebel Server runs. A reliable network connection to the name server must exist. It is strongly recommended that you install a name server that is local to your regional node.

Requirements for the ODBC Driver

If your implementation uses an Oracle RDBMS, then it is not necessary to install an ODBC driver. For other supported RDBMS vendors, you must install an ODBC driver. For more information about the name of the required ODBC driver and version information, see Siebel System Requirements and Supported Platforms on Oracle Technology Network.

Requirements for Installing the Siebel Server on the Regional Node

Note the following requirements for installing a Siebel Server on the regional node:

• Each regional node must contain at least one Siebel Server that synchronizes the regional node with the parent node. This Siebel Server might also support users. Your implementation might require more Siebel Servers, depending on the number of users and applications.
• The Siebel Server on the regional node can be at the same version and installed on the same operating system as the parent server. For example, if you run the headquarters node on Windows 2003, then the regional node can use Windows 2003.
• In a heterogeneous server environment, the Siebel Server and server database that you install on the regional node can be deployed to a different operating system. The version and patching level of the server database that you install on the regional node must be the same as the version and patching level of the server database that you install on the headquarters node.
• The server databases on the headquarters node and the regional node must use the same RDBMS. For example, if the RDBMS in the headquarters node is Oracle, then the RDBMS on the regional node must also be Oracle.
• The regional database can be on the same computer or on a separate computer in the same regional location, according to the following requirements:
  • The number of users
  • The number of connected web clients
  • Database sizing requirements
  • Computer performance requirements
• It is recommended that you set the NLS_LANG environment variable to the same value for the headquarters node and for the regional nodes. This configuration makes sure that the language environments of the server database and the client application are the same. The NLS_LANG variable sets the language and territory environment that the server session uses and the client application. The language and territory sections of the NLS_LANG variable determine the default values for other parameters, such as date format, numeric characters, and linguistic sorting. For more information, see the Siebel Installation Guide for the operating system you are using.

For more information about the Siebel Enterprise Server, see About the Siebel Enterprise and the Siebel Enterprise Server.