Bookshelf Home | Contents | Index | Search | PDF

Siebel Tools Reference > Siebel Architecture (Basic Concepts) >

Operating Architecture Overview

---

The client-server architecture of the standard HTML client is illustrated in Figure 11.

Figure 11.  Client-Server Architecture for Siebel Web Engine

Siebel applications are implemented on one or more servers using three major components: the object manager, the Siebel Web Engine, and the data manager: These components are described as follows:

• Object Manager. The object manager hosts a Siebel application, providing the central processing for HTTP transactions, database data, and metadata (object definitions in the repository that are relevant to the current state of the Siebel application). The Siebel Web Engine and data manager operate as facilities inside the object manager.

  Object definitions at all three levels of the object layer hierarchy—Web interface definitions, business object definitions, and data object definitions—are processed in the object manager. However, in terms of the runtime objects based on the object definitions, only the business object layer objects (business object, business component, and so on) are instantiated there directly. Web interface objects are instantiated in the Siebel Web Engine, and data objects are instantiated in the data manager.

  The object manager also implements the mechanism by which the Web interface objects receive notification of various state changes of the business component.

• Siebel Web Engine. This is also called SWE. The user interface in Siebel applications is generated as HTML pages on the server, and is passed to an unmodified Web browser through HTTP. The Siebel Web Engine (in combination with the Siebel plug-in on the Web server) makes possible the deployment of these applications. A Web browser client (or other Siebel client) interacts with the server-based object manager through the Siebel Web Engine, providing the means for the user to view and edit data. SWE retrieves and updates data by interfacing with the object manager. A notification mechanism between SWE and the object manager is used so that when one applet modifies data in any business component, all other applets are notified immediately so that they can update their data on the screen.
• Data Manager. The data manager is a facility inside the object manager that issues SQL queries in response to object manager requests, and passes back database result sets to the object manager. The data manager is composed of one connector DLL for each type of database connection supported by the system. The object manager dynamically loads the appropriate DLL based upon the required data source.

Bookshelf Home | Contents | Index | Search | PDF