Configuring Siebel Business Applications > Architecture of Siebel Business Applications >

About the Siebel Object Architecture

This topic describes the Siebel object architecture. It includes the following topics:

• Overview of the Physical User Interface Layer
• Overview of the Logical User Interface Object Layer
• Overview of the Business Object Layer
• Overview of the Data Objects Layer
• Hierarchy of Object Types and Relationships
• About Classes

Siebel CRM separates the metadata that defines objects and files, such as web templates and style sheets, into several architectural layers. Figure 1 describes this Siebel object architecture.

Figure 1. Siebel Object Architecture

Explanation of Callouts

The architecture includes the following items:

1. Physical user interface objects layer. Includes the physical files, templates, style sheets, and other metadata that reference files. Siebel CRM uses these files to render the user interface that it displays in the client. For more information, see Overview of the Physical User Interface Layer.
2. Logical user interface object layer. Includes object definitions for the user interface that Siebel CRM displays in the Siebel client. These objects define the visual elements that Siebel CRM displays and that the user uses in a Web browser. A user interface object references a business object. For more information, see Overview of the Logical User Interface Object Layer.
3. Business object layer. Includes objects that define business logic and organize data from underlying tables into logical units. For more information, see Overview of the Business Object Layer.
4. Data objects layer. Includes object definitions that map the data structures from the underlying relational database to Siebel CRM. These objects provide access to these structures through object definitions that reside in the business object layer. For more information, see Overview of the Data Objects Layer.

Siebel CRM insulates objects in each layer of the Siebel Object Architecture from the layers above and below each layer, including the RDBMS (Relational Database Management System) that resides at the bottom of the architecture. This configuration allows you to modify or configure Siebel objects in one layer without affecting objects that reside in other layers. Siebel CRM separates the database in the RDBMS from the object architecture, so you can make any necessary database modifications with only minimal effect on the layers of the Siebel CRM architecture.