Siebel Application Object Manager Infrastructure
A Siebel Application Object Manager component is implemented as a multithreaded process on the Siebel Server. At runtime, a parent process starts one or more multithreaded processes, according to the Siebel Application Object Manager configuration.
Each Siebel Application Object Manager process can host multiple user sessions (as tasks), which in turn are implemented as threads within the process. These threads might be dedicated to particular user sessions, or they might serve as a pool that can be shared by multiple user sessions. (For each process, a few threads also start that are dedicated to performing core functions for the process.)
As more users log in to the system, additional processes can be instantiated to host these users.
In this chapter, the term thread is often used interchangeably with task, except when you are using thread pooling. For details, see Using Thread Pooling for Siebel Application Object Managers.
The terms multithreaded server or MT server are alternative terms for multithreaded process (a process that supports multiple threads). For example, the names of the Siebel Application Object Manager parameters
MaxMTServersandMinMTServersrefer to multithreaded processes.
Siebel Application Object Manager components, which run in interactive mode, handle processing for Siebel Web Client sessions, in which the application user interface (UI) resides. The Siebel Application Object Manager task manages Siebel business objects and data objects and performs business logic for the client session.
Generally, each Siebel Application Object Manager task starts in response to a request from a Siebel Web Client running in a Web browser, and ends when the client disconnects.