Performance Tuning Guide > Tuning the Siebel Application Object Manager for Performance >

AOM Infrastructure


An AOM 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 AOM configuration.

Each process can host multiple user sessions (as tasks), which in turn are implemented as threads within the process. These threads may be dedicated to particular user sessions, or they may 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 into the system, additional processes may be instantiated to host these users.

AOM components, which run in interactive mode, handle processing for Siebel Web Client sessions, in which the application user interface (UI) resides. The AOM task manages Siebel business objects and data objects and performs business logic for the client session.

Generally, each AOM task starts in response to a request from a Siebel Web Client running in a Web browser, and ends when the client disconnects. Threads that handle login sessions based on the anonymous user may be reused for other login requests. The anonymous user is discussed later in this chapter.

AOM Communications with Other Modules

Each AOM task uses Siebel Server infrastructure capabilities to communicate with the Siebel Database, the Web server (through the SWSE), and other Siebel Enterprise Server components.

About Tuning the AOM

Tuning activities directly or indirectly applicable to AOM components may involve any or all of the following:

Some other chapters in this book discuss AOM tuning that relates to using other modules, such as Siebel Communications Server or Siebel eConfigurator.


 Performance Tuning Guide 
 Published: 24 October 2003