Configuration Strategy 20.

Time: Lecture: 15 – 20 minutes; labs: no labs

Siebel 8.0 Essentials
Intent: To explain the basic principles for configuring a Siebel
application. This is the first of several modules in the Configuration
section of the course that explains how to change the standard (as-
delivered) application.
Flow: Configuring the UI layer; configuring the Business layer;
configuring the Data Objects layer; a way to approach the configuration
Module 20: Configuration Strategy process
Key Terms:
Tailoring
Configuration Strategy
Development Environment

Copyright © 2007, Oracle. All rights reserved.

Siebel 8.0 Essentials

 Configuration Strategy 20.2

Each objective and “why you need to know” should be stated aloud.
Module Objectives
n After completing this module you should be able to:
} List the critical elements of the Siebel configuration strategy

n Why you need to know:

} Following a reasonable configuration strategy can expedite your
configuration efforts and make your configured application robust
and upgradeable

Copyright © 2007, Oracle. All rights reserved. 2 of 16

Siebel 8.0 Essentials

 Configuration Strategy 20.3

Set the scene for the module by explaining what is meant by

Configuring a Siebel Application “configuration” in Siebel terms.
n Configuring is the process of using Siebel Tools to modify an The term “configuration” describes the process of changing any of the
as-delivered Siebel application to meet business needs objects in the as-delivered application, be it the UI, the business logic, or
the data objects.
n Object definitions are edited and created
} Developers do not modify code in siebel.exe
} Developers do not write SQL directly

Object
Manager

SRF

Repository
Data Siebel
Repository File

Copyright © 2007, Oracle. All rights reserved. 3 of 16

Reference Using Siebel Tools

Developing and Deploying Siebel Business Applications:
Setting Up a Developer’s Local Database

Siebel 8.0 Essentials

 Configuration Strategy 20.4

Remind students that customers get a as-delivered application, with a

Siebel Applications standard set of views, screens, and so on. The as-delivered application is
what they start with.
n Siebel as-delivered applications include a predefined set of
screens, views, lists, forms, and their associated templates The screenshot illustrates the look-and-feel of the UI, which students
have already seen.

A predefined view

Copyright © 2007, Oracle. All rights reserved. 4 of 16

Siebel 8.0 Essentials

 Configuration Strategy 20.5

The job of a developer at the UI level is to modify the appearance of the

Tailoring the Logical User Interface application, so that it better reflects the business needs of the company
and the users.
n Developers tailor the as-delivered Siebel screens, views, lists,
and forms to better support users’ business needs In the Logical UI, you can modify the layouts of the applets, views,
screens, and applications (for example: which fields appear in what order
in an applet, which applets appear in what order in a view, and so forth).
Modifying templates is a change to the physical user interface, not the
logical user interface, and is handled in the customer’s HTML editor of
A tailored view
choice, not in Tools. This is discussed in more detail later in the class.

Copyright © 2007, Oracle. All rights reserved. 5 of 16

Siebel 8.0 Essentials

 Configuration Strategy 20.6

Siebel applications are also specified by a set of physical UI files that

Tailoring the Physical User Interface specify how the logical UI will be physically rendered in a browser.
Developers should use the existing swe templates, CSSs, and image files,
n Use the existing physical UI files whenever possible to the extent possible. Reducing customization of object definitions
n When necessary, copy existing files and modify as needed reducing not only development work but on-going maintenance, as well.
Use an HTML or
a text editor to
modify layout

Use a text editor •Siebel template files

to modify colors, •Cascading style sheets
fonts, etc. •Image files

UI files Object
Manager
Use a graphics
program to add
.cfg SRF
your
organization’s Database
images Configuration File Server Siebel
Repository File

Copyright © 2007, Oracle. All rights reserved. 6 of 16

Siebel 8.0 Essentials

 Configuration Strategy 20.7

In the as-delivered application, business logic is represented as a set of

Siebel Business Entities defined relationships between the supplied business components.
n Siebel as-delivered applications utilize a set of Siebel business You might remind students how we explored some of those business
components that implement the defined business logic entities and logic in earlier modules.

Account

Service Request Contact Action

Product

Copyright © 2007, Oracle. All rights reserved. 7 of 16

Siebel 8.0 Essentials

 Configuration Strategy 20.8

Configuration can take place at the Business Layer by changing elements

Tailoring the Business Logic associated with the business entities to better represent the business logic
of the organization. For example, you might add another field to support
n Developers also tailor the application by modifying the data not currently represented, or change a relationship from M:M to
definitions of the business components to implement the
1:M.
business logic appropriate to the users’ organization
The names of the business components do not change. For example,
suppose a company uses the term “Customer” instead of “Account.” You
Account Add fields
Modify form of
would change the applets, views, and screen text to say “Customer”
the relationship instead of “Account”, but the application still uses the Account business
component. (Changing the name of the BC would involve a massive
project of tracking down everything that referred to that BC by name and
Service Request Contact Action changing it, and would not be an effective use of time or resources.)

Modify properties
of existing fields
Product

Copyright © 2007, Oracle. All rights reserved. 8 of 16

Siebel 8.0 Essentials

 Configuration Strategy 20.9

This slide is done differently to capture the idea that developers are not
Extending the Data Layer expected to do much configuration at the Data layer. Hence, we use
terms like “extending” the Data layer in a limited and controlled manner.
n Siebel as-delivered applications contain a large, predefined set
of database tables The as-delivered application comes with a predefined data model, that is,
a standard set of tables. You can configure the application at the Data
n Developers can tailor the application by extending the set of
Objects layer by adding columns to tables, or by adding new tables to
database tables
extend the functionality of the data model.
} Recommendation is to perform this in a limited and controlled
manner Note that Siebel Systems supplies predefined extension tables.
Use existing extension … create custom tables Customers can also create their own extension tables. Also note that
tables to store additional on a very limited basis there are possible consequences when you extend the data model; for
attributes, or…
example, it can affect EIM data imports.

LAST_NAME
FST_NAME
MID_NAME
ROW_ID
CX_OPTY
Extension tables and columns and their usage in Siebel applications are

LAST_NAME
FST_NAME
MID_NAME
ROW_ID
S_OPTY S_OPTY_X
CREATED
CREATED_BY
CURCY_CD
ROW_ID

discussed in upcoming modules.

ROW_ID
ATTRIB_44

Copyright © 2007, Oracle. All rights reserved. 9 of 16

Siebel 8.0 Essentials

 Configuration Strategy 20.10

The next two slides highlight a sensible approach to configuration.

Configuration Strategy
n Make minimal changes to the as-delivered application
n Use existing object definitions in the as-delivered repository
whenever possible
} Ensures that a new configuration can be upgraded
with minimal effort
n Modify definitions as required, rather than creating new ones
} Creating new object definitions can lead to redundant configuration
and increase the maintenance effort

Copyright © 2007, Oracle. All rights reserved. 10 of 16

Siebel 8.0 Essentials

 Configuration Strategy 20.11

The next two slides highlight a sensible approach to configuration.

Configuration Strategy Continued
n Do not delete, make inactive, or rename seemingly unused
object definitions
} Other object definitions might reference them
} Deleting does not save memory, storage space, or improve
performance
n Use existing template files
} Modify only when changes are essential
} Modifying a template for one view or applet can have unexpected
consequences if another view or applet uses the same template

Copyright © 2007, Oracle. All rights reserved. 11 of 16

Siebel 8.0 Essentials

 Configuration Strategy 20.12

This slide presents more on basic configuration principles.

Configuration Strategy Continued The points here can be a little confusing. You can definitely work in
n Plan your configuration project from the top down more than one layer at a time. The point is that you should make any
} First, determine UI and application functionality
given modification at as high a level in the architecture as possible (much
configuration only requires modification of the UI), but make the lowest
} Then, determine what changes are necessary at the Business
layer to implement UI functionality
level modifications first.
} Finally, determine what changes are necessary at the Data layer to For example, if you have to make a modification at the Business Object
implement Business layer changes Level, you make the Business Object–level modification first, and then
n Keep changes to a minimum modify the UI level to display it properly.
Determine UI Functionality
Similarly, if you find that you absolutely must extend the Data layer, do
that first. Then configure the Business Object layer to use the extensions.
Finally, display the extensions in the UI.
Determine Required
Business Layer Changes

Determine Required Data

Layer Changes

Copyright © 2007, Oracle. All rights reserved. 12 of 16

Siebel 8.0 Essentials

 Configuration Strategy 20.13

This slide presents more on basic configuration principles.

Configuration Strategy Continued The points here can be a little confusing. You can definitely work in
n Make changes from the bottom up more than one layer at a time. The point is that you should make any
} First, edit Data layer definitions, if necessary
given modification at as high a level in the architecture as possible (much
configuration only requires modification of the UI), but make the lowest
} Then, edit Business layer definitions, as required
level modifications first.
} Finally, edit or create the templates and UI layer definitions to
display the data correctly For example, if you have to make a modification at the Business Object
Level, you make the Business Object–level modification first, and then
modify the UI level to display it properly.
Edit or Create UI Layer
Templates and Definitions
Similarly, if you find that you absolutely must extend the Data layer, do
that first. Then configure the Business Object layer to use the extensions.
Finally, display the extensions in the UI.
Edit Business Layer
Definitions, as Required

Edit Data Layer

Definitions, if Necessary

Copyright © 2007, Oracle. All rights reserved. 13 of 16

Siebel 8.0 Essentials

 Configuration Strategy 20.14

This slide provides an overview of the general idea of a development

Create a Separate Development Environment environment, which is discussed in detail in the slides to follow.
n To isolate the development effort from the enterprise’s The slide also introduces the idea of separate configurators working in
production database, set up a development environment isolation to implement and then test changes in a local repository, and
then propagate those changes to the server in a controlled manner. That
n Each developer or group can work on a different aspect of the
is the “development environment.”
development effort
} Use Siebel-supplied mechanisms to separate the development
effort into projects
n Test all customization and extensions thoroughly before
deploying to end users

Server Machine Developer Developer Developer

Workstation Workstation Workstation

Copyright © 2007, Oracle. All rights reserved. 14 of 16

Siebel 8.0 Essentials

 Configuration Strategy 20.15

By working in an isolated development environment, the developer

Develop on the Local Repository avoids any disruption of mission-critical applications and deploys the
upgrade to users when it is fully functional.
n Always make changes to the object definitions in the local
repository “Siebel-supplied mechanisms…” include the check-in and check-out
} Cannot undo or back out changes when made directly on the
processes, and the use of archive files (.sif).
server
} Changes made directly on the server are immediately available to
other developers
n Incomplete changes on the server cause problems
n Use Siebel-supplied mechanisms to copy definitions between
server and local databases

Server Machine Developer

Workstation
Server Local
repository repository

Copyright © 2007, Oracle. All rights reserved. 15 of 16

Siebel 8.0 Essentials

 Configuration Strategy 20.16

Review Question: When would developers working on a Siebel

Module Highlights configuration modify the code in siebel.exe?
n Configuring is the process of using Siebel Tools to modify an Answer: They wouldn’t.
as-delivered Siebel application
n Recommended configuration strategy:
} Tailor existing logical UI, physical UI, and business entities to
minimize development and support effort
} Do not delete, make inactive or rename unused object definitions
} Use existing template files
n Plan configuration project from the top down, make changes
from the bottom up
n Development and production environments are separate
} Enables developer or group to work independently
} Enables developer to test customizations before deploying

Copyright © 2007, Oracle. All rights reserved. 16 of 16

Siebel 8.0 Essentials