Siebel Server
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 which 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 (alias, for example, SCCObjMgr_deu for Siebel Call Center for German) and the Synchronization Manager (alias SynchMgr).
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 (alias TxnRoute) and Workflow Monitor Agent (alias WorkMon).
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 (alias DbXtract) and Enterprise Integration Mgr (alias EIM).
Many of the Siebel Server components can operate on multiple Siebel Servers simultaneously, allowing Siebel applications to scale across many computers to support large numbers of users.
Other Siebel Server components provide additional functionality, including the following:
Synchronization for Siebel Mobile Web Clients and Siebel Mobile disconnected applications
Integration with legacy or third-party data
Automatic assignment of new accounts, opportunities, service requests, and other records
Workflow management
Document generation
This topic is part of About the Siebel Enterprise Server and the Siebel Server.
Siebel Connection Broker (SCBroker)
The Siebel Connection Broker component provides load balancing of connection requests to multiple Application Object Manager threads or processes running on the same Siebel Server.
Siebel Server Implementation
The Siebel Server runs as a system service under Windows and as a process under UNIX. This system service or process monitors and controls the state of all of the server components on that Siebel Server. Each Siebel Server is one instantiation of the Siebel Server system service or process within the current Siebel Enterprise Server.
Interactive and batch components can be configured to run as multiple processes or in some cases as multithreaded processes. Application Object Manager components (which are interactive) can run as multiple processes and as multiple threads for each process. Background mode components can run as multiple processes only.
For information about administering the Siebel Server system service or process, see Siebel System Administration Guide.
Language Support
It is strongly recommended to install the same set of languages on each server instance in your Siebel Enterprise Server. However, you can deploy different languages on different Siebel Servers, as needed. For more information, see Siebel Installation Guide. See also Siebel Global Deployment Guide.