Bookshelf Home | Contents | Index | PDF |
Developing and Deploying Siebel Business Applications > Overview of Developing a Siebel Application > About Developing a Siebel Application > About the Siebel Object ArchitectureThe metadata that defines Siebel CRM objects and other files, such as web templates and style sheets, is divided in several architectural layers. Figure 5 illustrates the architecture. The architecture includes the following layers:
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) at the bottom of the architecture. This allows you to change or customize Siebel objects in one layer without affecting other layers. Because Siebel CRM separates the database in the RDBMS from the object architecture, you can make database changes with only minimal affect on Siebel CRM. For more information, see Configuring Siebel Business Applications. About the Sequence You Use to Define ObjectsIt is useful to think of configuration tasks in terms of the Siebel object architecture. You might work from the bottom up, starting with data objects first, then business objects, and then user interface objects. Or you might work in one layer only, modifying objects as needed. For the NREC example in this book, you modify objects in the user interface layer first. |
Developing and Deploying Siebel Business Applications | Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |