The Siebel Enterprise Server is a logical grouping of one or more Siebel Servers that connect to one Siebel Database.

Each Siebel Server functions as an application server and is composed of server components. Each server component performs a defined function.

Server components or groups of components determine what applications and services a Siebel Server supports. Components run in one of several modes:

  • Interactive mode. Interactive mode components start tasks automatically in response to user requests. Interactive tasks run until the user ends the session. Examples of interactive components include the Application Object Managers (AOMs) and the Synchronization Manager.
  • Background mode. Background mode components handle background processing tasks. Typically, background tasks are called by interactive tasks. Background tasks run until they are explicitly shut down. Examples of background components include Transaction Router and Workflow Monitor Agent.
  • Batch mode. Batch mode components handle processing of asynchronous work requests. When the task is complete, the component exits. Examples of batch components are Database Extract and Enterprise Integration Manager (EIM).

Many of the Siebel Server components can operate on multiple Siebel Servers simultaneously, allowing Siebel applications to scale across many server machines to support large numbers of users.

Other Siebel Server components provide additional functionality, including the following:

  • Siebel Mobile Web Client synchronization
  • Integration with legacy or third-party data
  • Automatic assignment of new accounts, opportunities, service requests, and other records
  • Workflow management
  • Document generation

The Gateway Server is a logical server that consists of the Siebel Name Server and optionally Resonate Central Dispatch. These two components can reside on separate physical servers. The Gateway Name Server is a repository for configuration information about each Siebel Server. When Siebel Servers or components come online or go offline the Name Server data is refreshed with the connect strings. Clients will also use the Gateway Name server to connect to the Siebel Servers if Resonate Central Dispatch (which is used to load balance and manage client connections to Siebel Enterprise) is not implemented.

Since the Siebel Application server component of the Siebel server maintains the connectivity information pertaining to every component in Siebel Enterprise, the 24 x 7 availability of the Siebel Application server is crucial to the functioning of the Siebel  server, and also for ensuring that client connections to Siebel servers are not disrupted. This is where eG Enterprise helps administrators!