Bookshelf Home | Contents | Index | PDF |
Deployment Planning Guide > Siebel Architecture Overview > About Siebel Enterprise Server and Siebel ServerThe Siebel Enterprise Server is a logical grouping of Siebel Servers that connect to one Siebel database. The Siebel Servers in a Siebel Enterprise Server are configured, managed, and monitored as a single logical group, allowing the Siebel administrator to start, stop, monitor, or set server parameters for all Siebel Servers within the Siebel Enterprise Server. Siebel ServerThe Siebel Enterprise Server is composed of one or more Siebel Servers. Siebel Servers function as application servers and are 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:
Many of the Siebel Server components can operate on multiple Siebel Servers simultaneously. This allows Siebel applications to scale across many Siebel Servers to support large numbers of users. Other Siebel Server components provide additional functionality besides application support. This includes the following:
Siebel Connection Broker (SCBroker)This server component provides load balancing for multiple Application Object Managers (AOMs) running on the same Siebel Server. Siebel Server ImplementationThe Siebel Server runs as a system service under Windows and a process under UNIX. This system service or process monitors and controls the state of all 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. You can configure interactive mode and batch mode components to run as multiple processes or as multithreaded processes. Background mode components run as multiple processes only. For information on administering the Siebel Server system service or process, see Siebel System Administration Guide. Application Object Manager (AOM)One of the most important types of server components is the Application Object Manager (AOM). These server components run in interactive mode. They process user requests and are application- or service-specific. For example, the Siebel Employee Relationship Management component group contains the Employee Relationship Object Manager. This AOM provides the session environment in which this application runs. AOMs also contain a data manager and the Siebel Web Engine. When an AOM receives a user request to start an application, the AOM follows this procedure:
Application Object Manager ImplementationAn Application Object Manager (AOM) server component is implemented as a multithreaded process on the Siebel Server. At run time, a parent process starts one or more AOMs as multithreaded processes, according to the AOM configuration. The terms multithreaded server or MT server are alternative terms for the multithreaded process.
Each thread in an AOM hosts tasks that are typically linked to one user session. These threads may be dedicated to particular user sessions, or they may serve as a pool that can be shared by user sessions. For each AOM, a few threads are dedicated to housekeeping functions. Each AOM task uses the Siebel Server to communicate with the Siebel Database, the Web server (through the SWSE), and other Siebel Enterprise Server components, as follows:
|
Deployment Planning Guide |