1. Deployment Planning Guide
  2. Application Object Manager

Application Object Manager

One 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 (alias SCCObjMgr_deu for German, for example), 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:

  • The business object layer starts an application user session, processes any required business logic, and sends a data request to the data manager.

  • The data manager creates an SQL query and forwards it the Siebel database.

  • The data manager receives the data from the database and forwards it to the business object layer for additional processing.

  • The business object layer forwards the result to the Siebel Web Engine, which helps create the user interface for the data. The Siebel Web Engine then forwards the Web pages to the Siebel Application Interface.

This topic is part of About the Siebel Enterprise Server and the Siebel Server.

Application Object Manager Implementation

An 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 Siebel Application Interface, or other components, as follows:

  • Communication with the Siebel database uses ODBC database connections. You can manage and tune database connections for optimal performance. You can optionally configure connection sharing for database connections.

  • Communication with the Siebel Application Interface uses SISNAPI (Siebel Internet Session API), a Siebel messaging format that runs on top of the TCP/IP protocol. SISNAPI connections use encryption and authentication based on Transport Layer Security (TLS).

  • Communication with other Siebel Enterprise Server components (including other Siebel Servers) also uses SISNAPI.

  • The Siebel Connection Broker (SCBroker) on each Siebel Server listens on a static, configurable TCP port for requests coming from the Siebel Application Interface. SCBroker forwards these requests to Application Object Manager processes.

For more information about the operation of multithreaded processes for Application Object Manager components, see Siebel System Administration Guide and Siebel Performance Tuning Guide.