Siebel 8.

0 Essentials

Configuration Strategy and Process

1 of 25

Module 20: Configuration Strategy and Process

Module Objectives
To know the process of modifying Siebel application using Tools To know the recommended configuration strategy

To learn the Development environment architecture and set it up to

carry out a successful configuration

Configuration Strategy and Process

3 of 25

Configuring a Siebel Application

Configuring is the process of using Siebel Tools to modify an

as-delivered Siebel application to meet business needs Developers edit and create the object definitions using Siebel Tools. They do not write SQL directly

Configuration Strategy and Process

4 of 25

Configuration Strategy

Make as few changes as possible Reuse existing objects in the Siebel Repository as far as possible to reduce the effort during application upgrade Plan your application design from the top down Define User Interface
Define the underlying business logic

Configure from the bottom up

Define data model to support business logic Modify data layer objects Modify objects at business layer

Configure user interface objects

Configuration Strategy and Process

5 of 25

Configuration Strategy
Modify definitions as required than creating new ones

Creating new object definitions can lead to redundant configuration and increases the maintenance work
Do not delete, make inactive or rename unused object definitions as

they might be referenced by other object definitions Use the existing template files whenever possible. When necessary, copy existing files and modify as needed.
Siebel template files: Use a HTML editor text editor to modify layout Cascading style sheets: Use text editor to modify fonts, colours etc. Image files: Use graphics program to add your organizations images

Configuration Strategy and Process

6 of 25

Customizing Siebel Applications

Refers to large-scale changes to the base product

Creation of new modules that do not exist within the Siebel application. This may involve use of database extensibility, many new business components, and many new business objects Significant changes to out-of-the-box behavior Use of scripting
Inappropriate customization of the Siebel application can cause

Decreased maintainability and therefore increased cost of ownership Performance degrade Potential impacts with future upgrades Increased testing effort

Configuration Strategy and Process

7 of 25

Development Environment
A separate Development environment needs to be set up to isolate

the developers effort from the enterprises production database

Each developer or group to work independently Enables testing of customizations and extensions deployment to end users
Use the Check Out/Check In mechanisms to copy object definitions

between server and local repositories Changes should be done on the objects in the local repository first
Cannot undo the changes directly done on the server

Configuration Strategy and Process

8 of 25

Development Environment Architecture

Siebel Remote is used to establish a local development

environment Siebel Developer Web Client provides full Siebel application functionality in a local environment
Accesses a local DB containing a subset of the server database Synchronizes with the server database, as necessary Implements a development and testing environment for individual developers

Configuration Strategy and Process

9 of 25

Steps to set up Development Environment

Enable the Development Environment Create the Developer Create a User Login Generate the Local Database Template Extract Local Database Modify and verify the Configuration Settings Verify ODBC Settings

Initialize the Local Database

Perform Full Get

Configuration Strategy and Process

10 of 25

Enable the Development Environment

Siebel Remote Component group must be enabled for

development using the local database

Restart the Siebel Server and synchronize components after enabling a component group

Configuration Strategy and Process

11 of 25

Create the Developer

Add the developer as an employee Associate a position and responsibility Register the developer as a mobile client. Routing model ensures that only the necessary data is routed to the

mobile user

Add developer as an Employee

Add a new Mobile Client..

..for User Id: AALEXIS..

..As a STANDARD Mobile Client

Configuration Strategy and Process

12 of 25

Create a User Login

Each user accessing a local database must be set up with a database

user account
Add database accounts on the appropriate database and then add these accounts to the group SSE_ROLE
Example:

Configuration Strategy and Process

13 of 25

Generate Local Database Template

A Database Template is a cached representation of Siebel tables and

indexes that are stored in a database file (DBF)

You create a database template on the server
To generate a local database template, run the Generate New

Database server task

Configuration Strategy and Process

14 of 25

Extract Local Database

Run the Database Extract server component to extract data from the

server database for each mobile user

Temporarily stores it in a compressed file The data in this file is used to populate the users local database during the database initialization process The mobile user must have a valid position in the organizations reporting hierarchy for the database extract to be successful

Configuration Strategy and Process

15 of 25

Modify and Verify Configuration Settings

Modify configuration information for Siebel Tools and Siebel

Developer Web Client

Tools in ..\tools\BIN\<Language Code>\tools.cfg Client in ..\client\BIN\<Language Code>\<application>.cfg
Both configuration files hold critical information to ensure proper

behavior of local executables:

Native client connection information for the local database ODBC connection for the server ODBC connection for the local database Location of the local Siebel file system Location of the local Siebel Repository File (SRF)

Configuration Strategy and Process

16 of 25

Example Configuration Settings

Example: tools.cfg (edited for length)

Available Data Sources

Connect String specification to Local database (DBF File)

ODBC Connection to Server Specific for Oracle Database Setting for Case Insensitivity Path for Siebel file system Server Connection String

Configuration Strategy and Process

17 of 25

Verify Web Client ODBC Connections

Ensure that the Web Client ODBC connection references the local

database
The database file parameter of SEAW Local Db default instance must match ConnectString in [Local] section of uagent.cfg
ConnectString must point to local DB: \client\LOCAL\sse_data.dbf

Configuration Strategy and Process

18 of 25

Verify Tools ODBC Connections

Ensure that the Tools ODBC connection references the local DB

The database file parameter of SSD Local Db default instance must match ConnectString in [Local] section of tools.cfg

Configuration Strategy and Process

19 of 25

Test Tools ODBC Login

Check user IDs and passwords, and then test the connection

Configuration Strategy and Process

20 of 25

Initialize Local Database

Initialization creates a local database file, sse_data.dbf from template upon

first login to client

Stores on the developers local machine Populates local database with data from compressed files

Configuration Strategy and Process

21 of 25

Perform Full Get

Extracts repository data

Populates local database with a read-only copy of the projects and object definitions stored on the server database Must be performed before compiling Initiate from Siebel Tools, Tools menu->Check Out
SRF must be based on the full set of Siebel objects

Configuration Strategy and Process

22 of 25

Whole Idea
Steps to create a usable local database

Configuration Strategy and Process

23 of 25

Module Highlights
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
Plan configuration project from the top down, make changes from the bottom up Development and production environments are separate

Siebel Remote is used to establish a local development environment

Create the development environment by:

Installing Siebel Tools on the client Enabling Siebel Remote on the server Creating a developer, login, and remote user on the server Generating, extracting, and initializing a local database Verifying login and data sources

Configuration Strategy and Process

24 of 25

Lab
In this lab you will setup an employee

Configuration Strategy and Process

25 of 25