Siebel Server Administration Guide > Application Object Manager Administration >

About the Siebel Application Object Manager

Application Object Managers (AOMs) host the Business Objects layer and Data Objects layer of the Siebel architecture. The Web clients host the Siebel application user interface layer. The AOM is used primarily to support Siebel Web client connections. To do this, the AOM operates like a Siebel Dedicated Web Client with two key differences: it does not require any software installation on the client machine and it handles multiple users simultaneously by making requests on their behalf.

AOMs are hosted as components in the Siebel Server and run on the application server (the machine that hosts the Siebel Server). The Siebel Server provides the infrastructure for an AOM to serve multiple Siebel Web client users. Multiple AOM components can run on a single Siebel Server installation. AOM components can be configured to run as multithreaded processes in the Siebel Server. Like other Siebel Server components, you can administer AOM components using the Siebel Server Manager.

AOMs 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 AOM 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 AOM tasks until the sessions are terminated. After startup, AOMs do not achieve their full run-time environments until after the first connect, therefore, leading to possible delays during the first connection. For further information on the communication of Web clients and AOMs, see Web Client Communication with Application Object Managers.

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 Web clients. When they reconnect to an AOM, Web client users will automatically retrieve the new Siebel application configuration. User preferences set and saved by Web client users will be saved on the Siebel Server.

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

Figure 34 shows the different ways in which different Siebel clients connect to the AOMs.

Figure 34.  Client Deployments

Click for full size image


 Siebel Server Administration Guide 
 Published: 23 June 2003