About the Siebel Application Object Manager

Siebel Application Object Manager (Application Object Manager) components host the Business Objects layer and Data Objects layer of the Siebel architecture. The Siebel Web Clients host the Siebel application user interface layer. The Application Object Manager supports Siebel Web Client connections and handles multiple users simultaneously by making requests to the Siebel Server on behalf of the clients.

Application Object Managers are hosted as components in the installed Siebel Server and run on the Siebel Server computer (sometimes called the application server computer). The Siebel Server provides the infrastructure for an Application Object Manager to serve multiple Siebel Web Client users. Multiple Application Object Manager components can run on a single Siebel Server installation. Application Object Manager components can be configured to run as multithreaded processes in the Siebel Server. Like other Siebel Server components, you can administer Application Object Manager components using the Siebel Server Manager.

Application Object Managers communicate with clients using the TCP/IP protocol through the Siebel Application Interface. Communication between the Siebel Application Interface and the Application Object Manager can be compressed and encrypted. An independent session is established to serve incoming connect requests from each client. Subsequent requests from clients are directed to the same Application Object Manager tasks until the sessions are terminated.

After startup, Application Object Managers do not achieve their full run-time environments until after the first connect, therefore, leading to possible delays during the first connection. For more information about how the Siebel Web Clients and Application Object Managers communicate, see Siebel Performance Tuning Guide.

The Siebel runtime repository is installed as part of each Siebel database installation. User preferences set and saved by Siebel Web Client users are saved on the Siebel Server.

Note: If you are running the Siebel Server in a UNIX environment, then Application Object Managers support Siebel eScript, but not Siebel Visual Basic.

About Application Object Manager Memory Allocation

The Application Object Manager caches information in two different ways. Some information is cached and used by every connection and other information is stored for each user connection.

Memory allocation for the Application Object Manager can be broken into three areas:

• User memory. The user area maintains specific information about each user's session. Typically, each user uses 3 MB to 4 MB of memory, although the memory required depends on the Siebel application in use. This memory is released when the task is completed.

• Shared memory between users. Shared memory is for common structures used by every user and is the largest segment of Application Object Manager memory. It contains definitions for business objects, business components, controls, and other metadata items from the Siebel repository. This memory is loaded as needed and remains loaded for the life of the process. Application Object Manager processes commonly use more than 150 MB.

• Administrative memory. The administrative area of memory used by Application Object Manager manages the component itself. This memory is relatively small and is used to manage communication between the Application Object Manager and other Siebel Server components. It runs the listener and coordinates threads and tasks.