siebel server Architecture

Siebel Application Entities

Siebel Clients Includes Siebel Web client, Dedicated Web Client, Wireless Client,
Mobile Web Client, handheld client, and Siebel Tools Client.

Siebel Enterprise Server Includes the logical grouping of Siebel Servers for a multiple server
deployment (for a single Siebel Server and single Web server deployment, the Siebel Enterprise Server contains a single Siebel Server and the Siebel Gateway Name Server). The Siebel Enterprise Server, collectively with the Siebel Gateway Name Server, provides both batch mode and interactive services to and on behalf of Siebel clients.

Siebel Gateway Name Server Includes the connection broker and name server for a single server deployment. (The name server is a separate entity for multiple
server deployments.)

Siebel Database Server Includes the RDBMS client software and Siebel tables, indexes, and
seed data.

Siebel File System Stores the data and physical files used by Siebel clients and Siebel
Enterprise Server.

The Siebel Enterprise Server environment represents the middle tier within the three-tiered Siebel eBusiness Applications environment.


Siebel Gateway Name Server

The Siebel Gateway Name Server is a logical entity, not a physical server consisting of a Name
Server.
The name server is the primary service of the Siebel Gateway Name Server, which coordinates the
Siebel Enterprise Server and Siebel Servers. A single Siebel Gateway Name Server can now support
multiple Siebel Enterprise Servers.

About Name Server

The Name Server provides the persistent backing of Siebel Enterprise Server configuration
information, including:
Definitions and assignments of component groups and components
Operational parameters
Connectivity information
As this information changes. such as during the installation or configuration of a Siebel Server. it is written to the siebns.dat file on the Name Server. At startup, the Siebel Server obtains its configuration information from the Name Server.s siebns.dat file.

The Name Server also serves as the dynamic registry for Siebel Server and component availability information. At startup, 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 no persistent (volatile) store. Periodically, the Name Server also flushes its current state to the siebns.dat file.
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.
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.

About Siebel Enterprise Server
The Siebel Enterprise Server is a logical grouping of Siebel Servers that supports a group of users accessing a common Siebel Database Server. The Siebel Enterprise Server can be configured, managed, and monitored as a single logical group, allowing the Siebel administrator to start, stop, monitor, or set parameters for Siebel Servers within a Siebel Enterprise Server.

You can set some Siebel Server parameters at the Siebel Enterprise Server level, and these parameters apply to every Siebel Server and component operating within that Siebel Enterprise Server; other parameters can be adjusted at the Siebel Server or component level to support fine-tuning.

If a parameter is set at the server level, then the server-specific value overrides the Siebel
Enterprise Server setting for the parameter on that server.
Each Siebel Server belonging to a Siebel Enterprise Server should connect to the same schema in the same database server. The Siebel Enterprise Server itself has no processes and, therefore, cannot have a state.

About Siebel Server
The Siebel Server is the middle-tier platform that supports both back-end and interactive processes for every Siebel client. These processes are components within the Siebel Server architecture and Support functions such as:
Mobile Web client synchronization
Operation of business logic for Siebel Web clients, as well as connectivity and access to the Siebel
Database Server and Siebel File System
Integration with legacy or third-party data
Automatic assignment of new accounts, opportunities, service requests, and other records
Workflow management
The Siebel Server supports both multiprocess and multithreaded components, and can operate
Components in background, batch, and interactive modes Many of the Siebel Server components can operate on multiple Siebel Servers simultaneously to support an increased number of users or larger batch workloads.

About Server Component Modes
Components can execute tasks in one of three run modes. Background , batch, or interactive.
Background mode components. Background mode components execute tasks to perform
background operations for the Siebel Server. After a background mode component task starts, it runs until you explicitly stop the task, or until the Siebel Server itself is shut down.

You can manually start a background mode component by using the Siebel Server Manager.
Components with a Default Tasks parameter set to a value greater than zero may start
automatically when the Siebel Server is started. Examples of background mode components
include Transaction Router, Replication Agent, and Workflow Monitor Agent.
Batch mode components. You must manually start these components by using the component
job process in the Server Manager GUI or by the Server Manager command-line interface. Batch mode components end after the task has been performed. Examples of batch mode components include Database Extract and Enterprise Integration Manager.
Interactive mode components. Interactive mode components start tasks automatically in
response to client requests. Interactive mode component tasks execute for as long as the client maintains the session, and end when the client disconnects. Examples of interactive mode components include Synchronization Manager and Application Object Managers.