Siebel Server Administration Guide > Application Object Manager Administration >

Overview of Siebel Application Object Manager


Siebel Application Object Managers host the Business Objects layer and Data Objects layer of the Siebel architecture. The Web clients host the Siebel application user interface layer. The Siebel Application Object Manager is used primarily to support Siebel Web client connections. To do this, the Application Object Manager 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.

Siebel Application Object Managers 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 a Siebel Application Object Manager to serve multiple Siebel Web client users. Multiple Siebel Application Object Manager components can run on a single Siebel Server installation. Siebel Application Object Manager components can be configured to run as multithreaded processes in the Siebel Server. Like other Siebel Server components, you can administer Siebel Application Object Manager components using the Siebel Server Manager.

Siebel Application Object Managers communicate with clients using the TCP/IP protocol. 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, Siebel 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 further information on the communication of Web clients and Application Object Managers, 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 application's 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 Application Object Manager, 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 difference in deployment between the different client types and how they connect to the Application Object Managers.

Figure 34. Client Deployments

Click for full size image


 Siebel Server Administration Guide, Version 7.5, Rev. C 
 Published: 18 April 2003