Siebel Object Architecture

Hello!

Today I will try to explain about Siebel Layers. This is very important thing in Siebel, because it takes down how the relationships between tables in Siebel are managed.

So as you know every program that works with large amount of data use database’s to manage its data in one place.  In this place data can be quickly retrieved.

If you ever worked with some database programs (for example easiest of all Microsoft Access), then you should know what is and how is relationships managed in database. Relationship is link between two tables that links them together. There can be 1:M, 1:1, and M:M relationship types. For example to understand lets take two tables (Account, Contact). Account can have many contacts. So it will be 1:M link. So in Contacts table is column account that stores the ID of Account to whom particular contact belongs. This is easiest of all examples. So, why Siebel Layers is so important? Because in Siebel relationships is created between Business Components in Business Layer not in database layer, tables all in all don’t know about those relationships. This is biggest difference between Siebel and any other database program (like MySQL or that same Microsoft Access).

OK below you can read about Siebel Layers and in this Bookshelf Picture you can look at how the layers look like. The text below is taken from bookshelf using 8.0v and represents layers shown in link with picture:

1)      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.

2)      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.

3)      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.

4)      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.

5)      DBMS. The third-party database management system manages the Data Objects Layer. It is not a part of the Siebel Business Application.