Siebel Server Administration Guide > Siebel Enterprise Server Architecture > Siebel Gateway >

Name Server

The Name Server provides the persistent backing of Siebel Server configuration information, including:

As this information changes—such as during the installation or configuration of a Siebel Server—it is written to the Name Server, specifically to the siebns.dat file. At start up, the Siebel Server obtains its configuration information from the Name Server's siebns.dat file. For further information on this file, see Backing Up the Siebel Gateway Name Server Data.

The Name Server also serves as the dynamic registry for Siebel Server and component availability information. At start up, a Siebel Server within the Siebel Enterprise Server notifies the Name Server of its availability and stores its connectivity information—such as network addresses—in the Name Server's nonpersistent (volatile) store.

Enterprise components (including the Server Manager) query the Name Server for Siebel Server availability and connectivity information. When a Siebel Server shuts down, this information is cleared from the Name Server.

In a Windows environment, the Name Server runs as a Windows service. In a UNIX environment, the Name Server runs as a daemon process.

A single Name Server can potentially serve several databases in an environment (such as multiple development and test environments). For purposes of mitigating dependencies and improving recoverability, you should keep the Siebel production environment separate from other Siebel environments (development or test) by using a separate Name Server.

If you decide to maintain multiple development or test environments on one Name Server, make sure that you use a distinct Siebel Enterprise Server for each table owner (or database for SQL server platforms).

NOTE:  Do not maintain the development, test, and production environments on the same Name Server.

You can specify and create a new Siebel Enterprise Server when you install the first Siebel Server for a table owner or database.

NOTE:  In a Windows environment, there can be only one Name Server installed per machine.

In a UNIX environment, the Name Server runs as a daemon process.

Impact of Failure

When the Name Server goes down, service to active user connections is not immediately interrupted. All Siebel Server components and object managers currently running continue to do so. However, no new Siebel Server components can be started or added. Server administration functions become limited.

High-Availability Solution

Siebel eBusiness Applications supports a number of server clustering technologies that are platform-specific to achieve high-availability for the Name Server. For example, Microsoft Cluster Service is supported on the Windows platform, while a number of vendor solutions are supported on the UNIX platform. For the most current information on server cluster support, see the Siebel Server Installation Guide for the operating system you are using.

Resource Requirements

The Name Server requires very few system resources. Follow the hardware recommendations listed in the system requirements and supported platforms document for your Siebel application.


 Siebel Server Administration Guide, Version 7.5, Rev. C 
 Published: 18 April 2003