Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Deployment Planning Guide > Siebel Architecture Overview > About the Siebel Enterprise Server and the Siebel ServerThis topic describes the Siebel Enterprise Server and Siebel Server, and also the Application Object Manager components of the Siebel Server. For information about applicable installation and configuration tasks, see the Siebel Installation Guide for the operating system you are using. Siebel Enterprise ServerThe Siebel Enterprise Server is a logical grouping of one or more Siebel Servers that connect to one Siebel database. You can configure some server parameters at the Enterprise level. Such parameters are inherited by individual Siebel Servers and applicable components. Some parameters can be overridden at the server level or component level. You use the Siebel Enterprise Server installer for installing Siebel Gateway Name Server, Siebel Server, Siebel Database Configuration Utilities, and Siebel EAI Connectors. After the initial configuration of the Siebel Enterprise and each Siebel Server using the Siebel Configuration Wizards, some subsequent configuration and administration tasks might be performed by one or more administrators using Siebel Server Manager. Server Manager supports both a command-line UI and a GUI. Siebel ServerEach 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:
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:
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 ImplementationThe 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 both multiple processes and 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 Pack InstallationIt is strongly recommended to install the same set of languages on each server computer in your Siebel Enterprise. However, in the Siebel Server Configuration Wizard you can deploy different languages on different Siebel Servers, as needed. For more information, see the Siebel Installation Guide for the operating system you are using. See also Siebel Global Deployment Guide. Application Object ManagerOne of the most important types of server components is the Application Object Manager. These server components always run in interactive mode. They process user requests and are application- or service-specific. For example, the Siebel Call Center component group contains the Call Center Object Manager, one for each language deployed on the Siebel Server. This Application Object Manager provides the session environment in which this application runs. Internally, each Application Object Manager also contains a data manager and the Siebel Web Engine. When an Application Object Manager receives a user request to start an application, it follows this procedure:
Application Object Manager ImplementationAn Application Object Manager server component is implemented as a multithreaded process on the Siebel Server. At run time, a parent process starts one or more Application Object Managers as multithreaded processes, according to the Application Object Manager configuration. The terms multithreaded server or MT server are alternative terms for the multithreaded process, which is also called an Application Object Manager process. Each thread in an Application Object Manager hosts tasks that are typically linked to one user session. These threads might be dedicated to particular user sessions, or they might serve as a pool that can be shared by user sessions. For each Application Object Manager, a few threads are dedicated to housekeeping functions. Each Application Object Manager task communicates with the Siebel database, the Web server (through the SWSE), or other components, as follows:
For more information about the operation of multithreaded processes for Application Object Manager components, see Siebel System Administration Guide and Siebel Performance Tuning Guide. |
![]() |
![]() ![]() |
Siebel Deployment Planning Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |