Siebel Application Object Manager (AOM)

Application Object Managers (AOMs) host the Business Objects layer and Data Objects layer of the Siebel architecture.

 It is a server component that creates and processes data at multiple levels.

  • UI layer (supported by the Siebel Web Engine) 
  • Business object layer 
  • Processes business logic
  • Data object layer (supported by Data Manager) 

The AOM is used primarily to support Siebel Web client connections. 

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.

Siebel Application Object 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.

5 comments on “Siebel Application Object Manager (AOM)”

  1. Tejeshwer Reply

    Can you explain how AOMmakes connections with database server?
    And can those connection be pooled if yes then how?

  2. Ashish Kumar Reply

    How AOMmakes connections with database server?
    For this you need to understand the Logical Architecture of Siebel.
    There are 4 layers in Siebel Logical Architecture:
    1. Physical User Interface Layer.
    2. Logical User Interface Layer.
    3. Business Object Layer.
    4. Data Object Layer.
    I am writing articles for all the four layers, then your questions will be answered.

    And can those connection be pooled if yes then how?
    Pooling of the connection is taken care by siebns.dat file which sits in the gtwysrvr folder.

  3. Nitin Reply

    Hi Ashish,
    I also eagerly wants to know the step by step process which is followed when OM makes connection with DB and fetches out result

  4. Apeksha Bameta Reply

    If i am not wrong DATABASE SUB SUSTEM defined in Siebel Server take care of communication with Database.

  5. Abhishek Reply

    Object manager connect with the database with the help of using the profiles (named subsystem).

    Component parameter name and value: DataSource (ServerDataSrc, GatewayDataSrc)

    Parameters of these datasources define the Database connect string, UserName, password etc.

    Connect string is used from tnsnames.ora.

    Connection be either shared or dedicated and can connection pooling can also be used.

Leave A Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!