Developing and Deploying Siebel eBusiness Applications > Getting Started with Siebel Tools >

Siebel Object Architecture

Siebel eBusiness architecture includes a core set of object definitions that are grouped into different layers depending on the object's function and characteristics. Additionally, there is a core set of HTML templates and style sheets that control the appearance of the user interface (see Figure 6). You can modify object definitions and templates, or create new ones, to tailor Siebel applications to meet your organization's business requirements.

Siebel Web templates occupy the top layer of the architecture. Siebel object definitions are grouped into the middle three layers. The physical RDBMS database occupies the bottom layer. You modify Web templates and style sheets using a text editor or a raw code HTML editor. You modify Siebel object definitions using Siebel Tools.

Objects depend on objects defined in the layers below, but are insulated from each other. Changes to objects in one layer require little or no changes to the layers below. For example, you can control how data is presented by modifying objects in the user interface layer, without having to modify objects in the business logic layer. Likewise, you can change the color and other style characteristics of the user interface by modifying Web templates and style sheets, without having to modify object definitions.

Figure 6.  Siebel Object-Based, Layered Architecture

• Physical User Interface Layer. This layer contains Siebel Web template files that control the style and structure of the user interface. Web templates consist of HTML tags and proprietary Siebel tags. Siebel tags are embedded within the HTML of template files and serve as placeholders for user interface objects defined in the repository, such as controls and applets. At run time the Siebel Web Engine reads the tags, replaces them with interactive Web controls and values based on the UI object definitions, and renders the HTML that will be read by the user's browser.
• Logical User Interface Layer. Object definitions in this layer are the visual representation of objects in the Business Objects Layer. They define the interface presented to the user at run time, and allow users to manipulate data. Examples of user interface objects include applets, views, and controls, such as buttons and check boxes. User interface objects also define the information that associates objects in the repository with the Siebel Web templates.
• Business Objects Layer. Object definitions in this layer describe individual business entities (such as Accounts, Contacts, or Activities) and the logical groupings and relationships among these entities. Business objects are based on data object definitions.
• Data Objects Layer. Object definitions in this layer provide a logical representation of the underlying physical database. For example, object definitions such as table, column, and index describe the physical database. These object definitions are independent of the installed RDBMS.
• DBMS. The third-party database management system manages the Data Objects Layer. It is not a part of the Siebel eBusiness Application.

Each layer of the Siebel object model contains several principal object types. Most of these object types contain child objects that further define the given object type.

For detailed information about the Siebel Object Architecture, read Configuring Siebel eBusiness Applications.