Bookshelf v7.5.3: Web Client Communication with Application Object Managers

Siebel Server Administration Guide > Application Object Manager Administration > About the Siebel Application Object Manager >

Web Client Communication with Application Object Managers

Figure 35 illustrates a view of the communication process between a typical Web client request, the Application Object Manager (AOM), and the Siebel environment. Each portion of the communication path is described following the figure (noted by numbers 1 through 6). For information on login and authentication issues during this communication process, see Security Guide for Siebel eBusiness Applications.

Figure 35. Web Client Communication with Application Object Managers

The Web client makes an HTTP request, which is received by the Web server and then sent to the Siebel Web Server Extension (SWSE).

Session Manager, a part of the SWSE, funnels requests using a Siebel Internet Session API (SISNAPI) connection to the AOM, a component of the Siebel Server. Many requests can use a single SISNAPI connection. See Configuring Session Manager for further information.

Initially, this connection is routed to the AOM in one of two ways:

If the Siebel Server is installed with Resonate Central Dispatch, the SWSE communicates using Resonate Central Dispatch with the AOM. The SWSE connections go to the enterprise VIP address and the enterprise virtual port number. Resonate Central Dispatch reroutes the communication to the appropriate AOM.

NOTE: All subsequent data relays from the SWSE go to the Resonate Central Dispatch VIP (Scheduler), which then routes it to the appropriate AOM. The AOM then returns the data reply directly to the SWSE.

If the Siebel Server is not installed with Resonate Central Dispatch, the SWSE communicates with the Name Server of the Siebel Gateway. The Name Server of the Siebel Gateway then returns the IP address and port number of the AOM to the SWSE and, from then on, the SWSE communicates directly with the AOM.

For more information on load balancing, see Network Configuration (Port Numbers). For more information on Resonate Central Dispatch, see the Siebel Server Installation Guide for the operating system you are using.

The AOM communicates with the database, if required, and requests data. (Some requests may not require a connection to the database—for example, some data may be cached.)

NOTE: AOMs have a 16 KB data memory limit when storing to the database.

The database returns the data of interest to the AOM, as necessary.

The AOM returns the requested data back to the SWSE over SISNAPI. If the client request includes a change of screen, the AOM merges the requested data with Web templates and sends this information back to the SWSE.

The SWSE passes the data through the Web server to the Web client browser. The data stream from the AOM updates certain fields, grids, or screens on the Web client browser to fulfill the client request.