Upload
freecharge
View
46
Download
7
Embed Size (px)
DESCRIPTION
fghjklkjhgghj
Citation preview
Siebel Application Architecture 1 of 22
Siebel 8.0 Essentials
Module 14: Siebel Application Architecture
Siebel Application Architecture 3 of 22
Module Objectives
• To describe the major types of object definitions• To describe the relationships between them
Siebel Application Architecture 4 of 22
The Siebel Application Architecture
• Recall that the Siebel Application consists of:– An execution engine that provides the application behavior
• The Siebel Server(s); more specifically, their components– Configuration files and the Siebel Gateway Name Server that specify operating parameters for the execution engine
• Most configuration parameters are stored in the Gateway Name Server
– A relational database that stores user data– A set of physical User Interface (UI) files that specify how to render the UI in the user’s– A Siebel Repository File (SRF) containing compiled object definitions
Siebel Application Architecture 5 of 22
The Siebel Application Architecture…
• Object definitions are created, modified, and stored in special tables in the database and compiled to the SRF
Siebel Application Architecture 6 of 22
Siebel Repository File (SRF)• Contains compiled object definitions that specify:
– Presentation of data– Business logic– Physical table storage
Siebel Application Architecture 7 of 22
Object Definitions
• Provide the foundation for application execution• Are grouped in three layers with different purposes• Refer to definitions in the next lower layer
Siebel Application Architecture 8 of 22
Data Layer
• Data layer object definitions specify the logical structure of the physical database
– Definitions are metadata, not data• In the Data layer, there are two principal data object definitions:
– Table definitions– Column definitions
S_SRV_REQ
SR_NUM INS_ PRODUCT SR_AREA
Table
Column
Siebel Application Architecture 9 of 22
Business Layer
• Business object definitions specify the business logic for the application• In the Business layer, there are two principal objects:
– Business component– Business object
Business Object
Business Component
Siebel Application Architecture 10 of 22
Business Component (BC)
• Represents one fundamental business entity in the enterprise– For example: Service Request, Contact, Activity
• Represents a logical grouping of data from one or more tables• Refers to a base table• Consists of multiple fields that characterize the business component
– Many fields within the business component reference columns in the base table
Service Request
SR # Type Area
S_SRV_REQ
SR_NUM INS_ PRODUCT SR_AREA
Business Component
Base Table
Field
Column
Siebel Application Architecture 11 of 22
Business Component…
• Can include data from additional related tables– Some fields map to columns in these related tables
Service Request
SR # Account Owner
SR_NUM NAME LOGIN
S_SRV_REQ S_ORG_EXT Owner-S_USER
Business Component
Field
Column
Base Table
Additional Table
Siebel Application Architecture 12 of 22
Business Object (BO)
• Is a collection of related Business components (BCs)• Represents a major functional area of the enterprise• For example, order management• Contains specific details about the relationships between BCs• One BC is the master or driving BC• Organizes related business components
Service Request
Service Request
Action Account
Business Object (BO)
Parent BC provides focus for BO
Business Component(BC)
Siebel Application Architecture 13 of 22
Comparing BCs and BOs
• Business Objects provide focus to views and organize BCs• Business Components provide data to applets and control data manipulation in tables
Siebel Application Architecture 14 of 22
UI Object Definitions
• There are five principal UI objects within the user interface
1. Application
2. Screen
3. View
5. List Column or Control
4. Applet
Siebel Application Architecture 15 of 22
Control and List Column Object Definitions
• Provide the ability to display and manipulate data
This column displays data in a columnar list
This Control displays data in
a field via a form
Siebel Application Architecture 16 of 22
Applet Object Definition
• A section of a view, such as a list or form• References one business component whose data can be viewed and edited through the list or form• Consists of list column or textbox control object definitions• Refer to fields in the applet-referenced business component• Specify how the data for the fields is displayed in the list or form
Service Request
SR # Last Name Owner
Siebel Application Architecture 17 of 22
View Object Definition
• Specifies a view in a Siebel application• Contains multiple applet object definitions • Service Request – My Service Request View
BO
BC
View references one BO
Applet references one BC
Siebel Application Architecture 18 of 22
Screen Object Definition• Specifies a screen in a Siebel application
– Is associated with a major functional area of the enterprise• Contains multiple view object definitions that usually refer to the same business object
– Administration screens are an exception
Views in Screen
Screens
Siebel Application Architecture 19 of 22
Application Object Definition
• Specifies a particular collection of screens available in a Siebel application
Siebel Application Architecture 20 of 22
Configuring Siebel Applications
• Is accomplished by using:– An HTML editor to modify template and other physical UI files– Siebel Tools to modify object definitions
Siebel Application Architecture 21 of 22
Module Highlights• Siebel architecture uses object definitions that specify application behavior• Use Siebel Tools to:
– Create, store, and modify object definitions in the database– Compile object definitions into the SRF for more efficient run-time
access• Object definitions are grouped into three layers:
– UI Layer• Includes applications, screens, views, applets and list
columns/controls– Business Layer
• Includes business objects and business components– Data Layer
• Includes tables and columns
Siebel Application Architecture 22 of 22
Lab
• In the lab you will:– Examine how UI layer object definitions reference business layer
object definitions