Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel System Administration Guide > Application Object Manager Administration > About the Siebel Application Object ManagerSiebel 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 a Web server that contains the Siebel Web Server Extension plug-in (SWSE). Communication between the Web server 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 repository file (SRF) is installed as part of each Siebel Server installation. Any changes to the repository file must be applied to the appropriate Siebel Server installations that serve the modified application to the Siebel Web Clients. When they reconnect to an Application Object Manager, Siebel Web Client users automatically retrieve the new Siebel application configuration. 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 AllocationThe 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:
|
![]() |
![]() ![]() |
Siebel System Administration Guide | Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |