Siebel 7 Essentials Student Guide Vol1 PDF

Siebel Systems, Inc.
Siebel 7 Essentials
Student Guide, Volume 1
Version 7.0 November 2001

Part # 10PO2-PLT01-07000
10PO2-PLT01-07000
Copyright 2001 Siebel Systems, Inc., 2207 Bridgepoint Parkway, San Mateo, CA 94404. All
rights reserved. No part of this publication may be stored in a retrieval system, transmitted, or
reproduced in any way, including but not limited to photocopy, photographic, magnetic, or other
record, without the prior agreement and written permission of Siebel Systems, Inc.
Siebel Systems, Inc. considers information included in this document to be Confidential and
Proprietary. Your access to and use of this Confidential and Proprietary Information is subject to
the terms and conditions of the Siebel License Agreement or Non-Disclosure Agreement which
has been executed and with which you agree to comply.
Re: Training Materials Siebel Systems Confidential and Proprietary Information
Dear Siebel Education Student:
This letter will serve to confirm that all information that is disclosed orally, visually, and in printed
form during your visit to Siebel Systems, Inc. for formal training classes is to be treated as
Confidential in accordance with the terms of the applicable confidentiality agreement (the
Agreement) between Siebel Systems, Inc. and your Company.
Under the terms of the Agreement, please be advised that you may not:
1. disclose such information or materials except as specified in the Agreement, nor

2. use such information or materials other than for the specified purpose set forth in the
Agreement.
Also, the materials you receive during your visit are copyrighted works of Siebel Systems, Inc.
(regardless of whether they bear a copyright mark) and may be used only for the purpose of
supporting the training of your employees who attend Siebel System training courses. You may
not reproduce, disclose, or distribute these materials, in whole or in part, nor may you prepare
derivative works of them. These copyrighted works include the Student Guides, Labs Manuals,
Instructor Guides, and all course materials used in Siebel Systems, Inc. courses and workshops.
Copyright 2001 Siebel Systems, Inc. Siebel Systems, Inc.

Technical Training from Siebel University
Instructor-Led Training
Siebel University offers instructor-led courses and workshops on core Siebel architecture, functions,
and enabling technologies, in our Learning Centers or on-site at your company. Instructor-led training
sessions are conducted by instructors who have both a practical and a theoretical command of the
subject matter they teach. Lectures and demonstrations are reinforced by hands-on labs, discussions,
and question-and-answer sessions for maximum understanding and retention.
Siebel 7 Essentials Installing and Extending Siebel Analytics 7
Siebel 7 Core Consultant Course Creating Siebel 7 Reports
Siebel 7 Requirements Mapping Siebel 7 Migration Training Workshop
Siebel eBusiness Application Integration 7 Siebel eRoadmap Workshop
Configuring Siebel Marketing 7 Getting Started Workshop
Siebel Interactive Selling Suite 7: Server- Siebel Employee Relationship Management
Based Implementation 7 Workshop
Siebel Interactive Selling Suite 7: Browser- Key Success Factors for Siebel Implementa-
Based Implementation tions Workshop
Web-Based Training
Siebel University offers Web-based courses covering the complete line of Siebel eBusiness
Applications. This technology-enabled training is self-paced, interactive, and involves the use of
training products that are Internet, CD-ROM, and intranet playable. These CD-ROM-based and Web-
based products, available 24x7, feature modular design for effective learning, easy navigation, and
searchable topics.
Course Types: a wide variety of Web-based training divided into three types:
Functional Technical Selling topics
Course Subjects: Web-based courses cover the following training subjects:

Components of Siebel Siebel Industry Siebel Horizontal applications
eBusiness Applications applications
Siebel software migration Technical topics Navigation
For more information about Siebel Technical Education classes: http://siebeluniversity.siebel.com

Siebel End User Education
Uniquely Qualified to Train Siebel End Users

Siebel End User Education focuses exclusively on providing process-based education for Siebel
eBusiness Applications. Our global team of consultants blends the right mix of technology and
human interaction to generate interactive training solutions that accommodate all types of end users
on all tiers of the organizational hierarchy. These solutions may include one or a variety of the
following:
Consultative analysis and reviews
Targeted training courseware
Instructor-led classes
Self-paced study
Distance learning
Performance support systems
No other education consulting team focuses 100% of their efforts on Siebel eBusiness Applications
like Siebel End User Education. Our consultants have extensive industry experience, participate in
on-going training and certification on all Siebel eBusiness Applications, and possess advanced
business skills. In addition, Siebel Consultants have the advantage of working closely with internal
and external resources throughout Siebel Systems and its integration partners. Our global presence
enables us to deliver solutions in many languages, including most European and Asian languages. For
those customers who intend to use an internal training team, we will work with that team to provide
the Siebel eBusiness Application expertise and support they need during and beyond the rollout.
Flexible Education Solutions

Siebel End User training reaches beyond instruction of technical components and complex concepts.
It bridges the gap between old and new processes. End users need to know more than how Siebel
eBusiness Applications work; they need to know how it will affect them in accomplishing their job
responsibilities. Siebel End User Education has developed three distinct domains to categorize the
flexible education solutions that ensure optimal end-user deployments targeted to the customers
unique requirements and environment.
Transition: our innovative consultative services, like change communication and readiness,
that assist our customers in better planning and communicating a Siebel eBusiness
Application deployment.
Deployment: the development and delivery of training rollouts for both enterprise and mid-
market customers, whether it is to end users or a customer's internal team of trainers.
eLearning: the customized multimedia solutions used for self-paced learning, process
validation, and training support.
The process-oriented services we provide stem from a solid foundation of core skills in development
and delivery. Using this foundation, we cultivate the most appropriate, flexible solution that supports
our customers values yet inspires their end users in a way no other training experience has in the
past.
For more information about Siebel End User Education: http://siebeluniversity.siebel.com

Siebel 7 Essentials
Table of Contents
Volume 1
Foundations
Module i: Siebel 7 Essentials Training
Module 1: Introducing Siebel eBusiness Applications
Module 2: Using the Siebel Client
Module 3: Organizing Data Behind the User Interface
Architecture and Installation

Module 4: Exploring the Siebel Architecture
Module 5: How Clients Access Siebel Data
Module 6: Installing Siebel Software
Module 7: Server Administration
Access Control and Organization Setup

Module 8: Access Control and Views
Module 9: Access Control and Data
Module 10: Access Control and View Types
Module 11: Creating an Organization
Module 12: Authenticating Users
Exploring Siebel Applications

Module 13: Understanding Object Definitions Behind a Siebel Application
Module 14: Using Siebel Tools to Examine Object Definitions
Module 15: Understanding the Siebel Data Model
Module 16: The Siebel Data Model: Party Business Components
Configuration
Module 17: The Configuration Process
Module 18: Managing Object Definitions
Siebel Systems, Inc. i

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION
DUPLICATION IS PROHIBITED
Siebel 7 Essentials
Volume 2
Configuration, Continued
Module 19: Editing and Compiling Object Definitions
Module 20: Understanding Siebel Template Files
Module 21: Configuring Applications and Screens
Module 22: Configuring Views
Module 23: Configuring List Applets
Module 24: Configuring Form Applets
Module 25: Understanding Business Components and Joins
Module 26: Business Components and Joins: Party Extension Tables
Module 27: Understanding Business Objects and Links
Module 28: Configuring Business Components and Fields
Module 29: Creating a New BC Using the Standard 1:M Extension Table
Module 30: Configuring Navigation
Module 31: Extending the Database
Module 32: Configuring Picklists
Module 33: Configuring Multi-Value Groups
Module 34: Configuring Access Control
Module 35: Localizing an Application
Module 36: Configuration Guidelines
Volume 3
Data Loads
Module 37: Introducing Enterprise Integration Manager
Module 38: Data Mapping
Module 39: Invoking Enterprise Integration Manager
Module 40: Setting Enterprise Integration Manager Options
Module 41: Access Control and Access Groups
ii Siebel Systems, Inc.

Siebel 7 Essentials
Business Process Automation

Module 42: Introducing Siebel Workflow
Module 43: Invoking Workflow Processes
Module 44: Additional Workflow Topics
Module 45: Introducing Assignment Manager
Module 46: Creating Sales Assignment Rules
Module 47: Creating Service Assignment Rules
Module 48: Invoking Assignment Manager
Module 49: Personalizing View and Applet Access
Module 50: Personalizing Content and Behavior
Deployment
Module 51: Using Siebel Remote to Support Mobile Clients
Module 52: Additional Siebel Remote Topics
Module 53: Migrating Data Between Environments
Conclusion
Module 54: Final Words
Siebel Systems, Inc. iii

Siebel 7 Essentials
iv Siebel Systems, Inc.

Siebel 7 Essentials Training i.1
Siebel Technical Training i
Siebel 7 Essentials
Version
Version 7.0
7.0
November
November 2001
2001
Module i: Siebel 7 Essentials Training 1 of 17
Siebel 7 Essentials Siebel Systems, Inc.
COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Module i: Siebel 7 Essentials Training

Module Objectives i
This module provides an introduction to the:

` Instructor and fellow students (class participants)
` Training site
` Course materials, goals, audience, methodology, objectives, and
agenda
Why you need to know

Introductions and Expectations
Who are you?

` Name
` Company
` Role
What is your prior experience?
` Siebel eBusiness applications
` Relational database
` Programming
How do you expect to benefit from this course?

Training Site Information i
Bathrooms Class duration and breaks
Telephones Meals and refreshments
Fire Exits Questions?

Course Materials
Student Guide
` All slides presented during lecture
Lab Guide
` Hands-on lab exercises and solutions
Media
` Navigating Siebel 7 Applications CD-ROM
` Siebel 7 Call Center Fundamentals CD-ROM
` Siebel 7 Application Administration CD-ROM
` Bookshelf for Siebel 7 Applications CD-ROM

Course Objectives i
In this course, you will learn how to:

` Navigate the Siebel eBusiness user interface
` Describe the Siebel eBusiness architecture
` Install Siebel eBusiness software to set up your enterprise
` Control access to Siebel applications and data
` Define your organization structure
` Configure and localize a Siebel eBusiness application
` Load data into the Siebel database
` Automate business rules in your Siebel eBusiness application
` Support mobile clients
` Migrate data between environments

Course Audience
This course is designed for:

` Application Developers
` System Architects and Configurators
` Database Administrators
` Systems Administrators

Course Methodology i
Subject matter will be delivered via:

` Lecture and slide presentations
` Software demonstrations
` Class discussions
` Hands-on labs

Overview of Course Flow
1. 2. 3. 4.
Foundations Architecture Access Exploring
and Control and Siebel
Installation Organization Applications
Setup
5. 6. 7. 8.
Configuration Data Loads Business Deployment
Process
Automation
9.
Conclusion

Agenda i
Foundations
` 1: Introducing Siebel eBusiness Applications
` 2: Using the Siebel Client
` 3: Organizing Data Behind the User Interface
Architecture and Installation

` 4: Exploring the Siebel Architecture
` 5: How Clients Access Siebel Data
` 6: Installing Siebel Software
` 7: Server Administration

Agenda Continued
Access Control and Organization Setup

` 8: Access Control and Views
` 9: Access Control and Data
` 10: Access Control and View Types
` 11: Creating an Organization
` 12: Authenticating Users
Exploring Siebel Applications

` 13: Understanding Object Definitions Behind a Siebel Application
` 14: Using Siebel Tools to Examine Object Definitions
` 15: Understanding the Siebel Data Model
` 16: The Siebel Data Model: Party Business Components

Agenda Continued i
Configuration
` 17: The Configuration Process
` 18: Managing Object Definitions
` 19: Editing and Compiling Object Definitions
` 20: Understanding Siebel Template Files
` 21: Configuring Applications and Screens
` 22: Configuring Views
` 23: Configuring List Applets
` 24: Configuring Form Applets
` 25: Understanding Business Components and Joins
` 26: Business Components and Joins: Party Extension Tables

Agenda Continued
Configuration Continued
` 27: Understanding Business Objects and Links
` 28: Configuring Business Components and Fields
` 29: Creating a New BC Using the Standard 1:M Extension Table
` 30: Configuring Navigation
` 31: Extending the Database
` 32: Configuring Picklists
` 33: Configuring Multi-Value Groups
` 34: Configuring Access Control
` 35: Localizing an Application
` 36: Configuration Guidelines

Agenda Continued i
Data Loads
` 37: Introducing Enterprise Integration Manager (EIM)
` 38: Data Mapping
` 39: Invoking Enterprise Integration Manager
` 40: Setting Enterprise Integration Manager Options
` 41: Access Control and Access Groups
Business Process Automation

` 42: Introducing Siebel Workflow
` 43: Invoking Workflow Processes
` 44: Additional Workflow Topics
` 45: Introducing Assignment Manager
` 46: Creating Sales Assignment Rules

Agenda Continued
Business Process Automation Continued

` 47: Creating Service Assignment Rules
` 48: Invoking Assignment Manager
` 49: Personalizing View and Applet Access
` 50: Personalizing Content and Behavior
Deployment
` 51: Using Siebel Remote to Support Mobile Clients
` 52: Additional Siebel Remote Topics
` 53: Migrating Data Between Environments
Conclusion
` 54: Final Words

Summary i
This module provides an introduction to the:

` Instructor and fellow students (class participants)
` Training site
` Course materials, goals, audience, methodology, objectives, and
agenda


Introducing Siebel eBusiness Applications 1.1
Module 1: Introducing Siebel eBusiness

Applications

Module Objectives
After completing this module you will be able to:

` Describe standard Siebel terminology and user interface behavior
` Describe Siebel employee, customer, and partner applications
` Describe standard features that can be changed

` You will work with employee and customer applications
throughout this course
` Introducing Siebel eBusiness Applications and functionality
provides context for the rest of the course
Module 1: Introducing Siebel eBusiness Applications 2 of 25

Siebel eBusiness Enterprise
An integrated product suite that helps manage customer

relationships 1
Built on a common architecture
Industry Applications
Siebel eFinance Siebel eAutomotive

Siebel eInsurance Siebel eEnergy
Siebel eHealthcare Siebel ePharma
Siebel eCommunications Siebel ePublic Sector For complete listing,
see Siebel Bookshelf
or www.siebel.com
Customer Applications
A Employee Applications
Siebel eMarketing Siebel Call Center Siebel Handheld
Siebel eService Siebel Service Siebel Wireless
Siebel eSales Siebel Sales Siebel Voice
Siebel Interactive Selling Siebel Field Service
Suite (ISS)
Partner Applications
Siebel eChannel
Siebel eBusiness Architecture

Siebel MidMarket Edition (MME)
Designed for companies with fewer than 100 users

An integrated product suite that helps manage customer
relationships
Industry Applications
Siebel eFinance, MidMarket Edition
Siebel eInsurance, MidMarket Edition
Siebel eHealthcare, MidMarket Edition
Customer Applications Employee Applications

Siebel eCustomer, MidMarket Edition Siebel Call Center, MidMarket Edition
Siebel eSales,MidMarket Edition Siebel Sales, MidMarket Edition
Siebel eService, MidMarket Edition Siebel Service, MidMarket Edition
Partner Applications
Siebel eChannel, MidMarket Edition
Siebel eBusiness Architecture
Siebel MidMarket MME is a product line optimized to meet the fundamental eBusiness
Edition needs of most mid-sized companies. It is designed to provide basic sales
and service functionality. In general, MidMarket Edition has a much
simpler feature set than the Enterprise offering. The technical features not
built into the MidMarket Edition are those typically required by large
organizations, including UNIX support, server-to-server replication,
advanced database extensibility, and advanced Assignment Manager
functionality. MidMarket Edition is built upon Siebel's Web-based
architecture and shares the same look and feel of Siebel Enterprise.
Technical differences relevant to material covered in this course will be
pointed out as appropriate. For a detailed comparison, please refer to
Siebel SupportWeb.

Business Entities
Siebel eBusiness Applications use entities to manage business

relationships, for example 1
` Accounts
` Opportunities
` Contacts
` Service Requests
` Activities
` Assets
Entity A business entity is something in the real world in which we have a

business interest.

Account
Is a business external to your company

Represents a current or potential client, a business partner, or
a competitor

Opportunity
Is a potential revenue-generating event

Has the following characteristics 1
` Possible association with an account
` Potential revenue
` Probability of completion
` Close date

Contact
Is a person with whom you do business

Has the following characteristics
` Name
` Job title
` Email address

Service Request
Is a request from a customer for information or assistance with

a problem related to products or services purchased from your 1
company
` Status
` Severity
` Priority

Activity
Is a specific task or event to be completed

` Start date and due date
` Priority
` Assigned to specific employees for completion

Asset
Is an instance of a purchased product

1
` Asset number
` Product and part number
` Status

Types of Applications
Employee
` Internal application used by employees and partners
` Examples: Siebel Sales, Siebel Call Center, eFinance
Customer
` External application used by customers
` Examples: Siebel eService, Siebel eSales, Siebel eMarketing
Partner
` External application used by employees and partners
` Example: Siebel eChannel
Partners There are two types:

Alliance Partners are partners who team with Siebel Systems in the
market.
Channel Partners are partners authorized to resell Siebel eBusiness
Applications.

Types of User Interfaces (UI)
High interactivity
` Available for employee applications, supporting highly interactive
1
enterprise users
` Requires Internet Explorer 5 or higher
Standard interactivity
` Available for customer applications
` Behaves like traditional Web applications, requiring frequent
page refreshes
High Interactivity Available only with Siebel employee applications in the Siebel 7 release.
High interactivity relies on Java, JavaScript, and LiveConnect support from
the browser. It also requires JavaScript 1.2 Document Object Model
(DOM) technology and HTML frame support from the browser.
Standard Interactivity Available for customer applications, when the Web users browser is
unknown.

Benefits of High Interactivity UI
Reduces number of page refreshes

` User downloads complete HTML page initially
` Subsequent round trips fetch data required to update page
Saves data implicitly by stepping off record
` No need to click Save button
Supports highly interactive graphical UI elements
` Flowcharts, organization charts, interactive toolbars

Differences Between High and Standard Interactivity
The following features are supported only by high interactivity

` Client-side scripting
1
With access to Siebel objects on the client side
` Interactive controls
Calculator, calendar date/time selector
` Keyboard shortcuts
For frequently used commands
Client-side Scripting Using Siebel objects, customers can build sophisticated data validation
logic on the client side to further reduce the number of page refreshes
needed for high interactivity applications.
Interactive Controls These provide customers with added flexibility to design and customize
their applications.
Keyboard Shortcuts Allow employees to speed up routine tasks and thereby improve their
productivity.

Employee Application: Siebel Sales
Siebel Sales allows your sales force to manage accounts,

sales opportunities, and contacts
Personalized content
Reference For more information on Siebel Sales, go to www.siebel.com.

Employee Application: Siebel Call Center
Siebel Call Center allows your agents to coordinate and

manage all customer interactions 1
Click
menu
button for
more
commands
Reference For more information on Siebel Call Center, go to www.siebel.com.

Customer Application: Siebel eService
Siebel eService allows your customers to receive self-service

and assisted service over the Web
Frequently asked questions

allow customer self-service
Reference For more information on Siebel eService, go to www.siebel.com.

Customer Application: Siebel eSales
Siebel eSales allows your customers to purchase products

over the Web 1
Shopping cart
Browse products
Reference For more information on Siebel eSales, go to www.siebel.com.

Partner Application: Siebel eChannel
Siebel eChannel allows companies and their partners to work

together to market and sell to, service, and retain customers
Recommended
items
Company news
Reference For more information on Siebel eChannel, go to www.siebel.com.

Applications Used in This Course
Siebel Call Center and Siebel eService are used during this
course 1
` Technology learned here applies to all Siebel applications
For information on all other Siebel eBusiness Applications, see
` Siebel Bookshelf
` www.siebel.com

Standard Siebel Application
Functionality demonstrated so far is standard and prebuilt

Data presented in the UI is stored in a database
Siebel
Database

Changing the Standard Application
Standard Siebel applications can be changed to meet your

business requirements 1
In this course, you will configure Siebel Call Center and Siebel
eService to change some prebuilt functionality, for example:
` Change drilldowns and navigation
` Extend database to store new fields
` Display new fields in Siebel views
` Create new list and forms
` Create entities to manage your business
` Create picklists to control field values
` Change list and column names

Benefits of Deploying Siebel Applications
Applications are integrated, so they can work separately or

together
` Integrated applications access a common Siebel database
All Siebel eBusiness Applications are built on a common
architecture

Summary
This module showed you how to:

` Describe standard Siebel terminology and user interface behavior
1
` Describe Siebel employee, customer, and partner applications
` Describe standard features that can be changed


Using the Siebel Client 2.1
2
Module 2: Using the Siebel Client

Module Objectives

` Use the Siebel user interface (UI)

` Understanding the UI enables you to effectively use Siebel
applications
` Knowledge of standard application features provides context for
configuration later in the course
Module 2: Using the Siebel Client 2 of 25

Home Page
Logging in to a Siebel application displays a home page

Application-level menu
Frequently used screens

2
Personalized content
based on login
Drill down on hyperlink for more detail
Home Page This is an example of a typical home page for a Siebel employee
application.

Navigating the UI
Clicking on different UI elements navigates to different data

Screen tabs
Show drop-down
Selected record
List
View tabs
Form
Screens Clicking a screen tab navigates to a functional area of the application,

such as accounts, contacts, service requests, assets, campaigns, and so
on. Screen tabs indicate the most commonly used screens. To access all
available screens in the application, use the application-level menu and
select ViewSite Map.
Show Drop-Down Clicking here will show a subset of data for the functional application area.
View Tab Clicking a view tab shows data related to the selected record. For
example, clicking the view tab Account Team will show the account team
for the account Perrier Group of America.
Selected Record The selected record in a list is highlighted with a contrasting color.

Screens and Views
Screens and views show business entities and related data
Accounts screen
Indicates the subset

2
of account data
displayed in list
List
Subsets of account data that

can be displayed
Form
Show Drop-Down Shows a subset of data for the functional application area. Click a
selection in the drop-down list to navigate to a different subset of data.

Navigating Through Lists and Forms
Use next or previous record set buttons or menu button
Click menu
button to
navigate to Navigate through
first or records in a list
last records
in list
Navigate to next
record or previous
record in a form
First Record Selecting First Record in the menu will navigate to the first record in the
list.
Last Record Selecting Last Record will navigate to the last record in the list.

Drilling Down for More Information
Drill down on hyperlink to see more information
1. Clicking account hyperlink
2. presents
account and
contact data
Hyperlinks Hyperlinks can be configured using Siebel Tools.

Navigating Through Views and Screens
Use arrows to navigate to

Back and forward arrows previous screens and views
History drop-down
Current view is at
top of list
Select from drop-down list
to navigate to previous
screens and views
Thread bar
Click on hyperlink to navigate to previous view Current view
Back and Forward These are the arrows available for navigation in the Siebel application. Do
Arrows not confuse them with the browser back and forward arrows, as behavior
is very different.
Thread Bar The thread bar shows your:

Location among screens and views
Path as you drill down on a record

Working with Data in the UI
There are several mechanisms for working with data, such as:
` Application-level menu
` Menu buttons
` Creating and modifying data
2
` Picklists and multi-value groups
` Queries
` Favorites
` Sorting
` Keyboard accelerators

Application-Level Menu
This menu applies to the entire application and shows available

actions
Menu Items Menu items might vary depending on the Siebel application you are using.
These menu items are available in the standard Siebel Call Center
application.
High Interactivity UI The application-level menu is available only in the high interactivity
interface.

Using Menu Buttons
Menu buttons show available actions for lists and forms
Click to show menu

for Opportunities
list
2
Click to show
menu for
Opportunity form
Menu Button The menu button displays a menu of actions available for the list or form.
Notice that some of these actions are also available from the application-
level menu.
The menu button is available only in the high interactivity interface.

Creating Data
Click menu button or New to create a new record
Click New to
create new
record
Red asterisk
signifies required field
Click menu
button, then
select New
Record
Creating New Record Clicking the New button or choosing New Record in the menu renders the
same results in the UI. A field with an asterisk means it is a required field
for the record.
Undo and Delete If a record cannot be undone or deleted, the actions will be grayed out and
Record unavailable to the user.

Modifying and Saving Data
Modify data
` Select record field in the list or form, and change it
Save data implicitly
` Click off the record in a list or the field in a form to commit it to the
database
2
` Available in high interactivity interface
Save data explicitly
` Click Save to commit the record to the database
` Available in standard and high interactivity interfaces
Explicit save
Save Button The presence of the Save button does not negate the implicit record-level
commit described above.

Using Picklists and Multi-Value Groups

Drop-down arrow
Picklist
` Select a single value for a field
in a record Select an Account
Type for the account
Multi-value group (MVG)

` Associate one or more values
to a field in a record
Associate
members to the
account team
Select button
More Examples of Multiple addresses can be associated to an account

MVGs Sales teams can be made up of many team members
An opportunity can have multiple sources, such as phone call, trade
show, or conference
Multiple employees can be assigned to an activity
Drop-Down Arrow The drop-down arrow indicates that data can be selected from an
available source, such as a picklist, calendar, or calculator.
Select Button Clicking the select button in a field accesses a dialog box, which provides
a list of records from which to select.

Querying for Data
Use a query to retrieve specific data

2. Enter criteria in
appropriate fields
1. Select New Query

4. Query returns
all records
matching the
criteria
3. Select Run Query
What is a Query? A query retrieves information from a database, allowing you to:
Locate one or more records that meet specific criteria
Create a subset of data for viewing and reporting
Refresh the view to updated information
Query by Example Siebel eBusiness Applications support QBE, which helps you quickly and
(QBE) easily find the information you are looking for.

Query Operators
Wildcards (asterisks) can be used to search for multiple

characters, for example
` Ma* will find Madrid, but not San Mateo
` *Ma* will find Madrid and San Mateo
` * cannot be used in date or numeric fields
<= (less than or equal to) can be used on numeric or date fields
<> (not equal to) can be used on all fields
OR allows entry of more than one value for a field
See online help for a full list of

query operators.
Select HelpContentsIndex
and click the letter O
Null Criteria Running a query with no criteria will return all records in the list. This is
also a way to refresh your screen to see the most current information.

Refining Queries
Use Refine Query to modify an existing query
2. Enter additional or
modified criteria
2
Original query criteria
3. Select Run Query
4. Query returns all records matching both the

original and the additional criteria
1. Select Refine Query

Saving Queries
Use the application-level menu to save a query

1. Select EditQuerySave As
2. Name the query and click OK
Application-Level Menu You must use this menu to save queries. Optionally, you can perform the
other query functions from this menu, such as creating a new query,
refining an existing query, and running a query.
Saving Queries By default, queries are saved as private queries, and are only available to
the user who created them.

Using Favorites
Favorites are available queries

` Queries created and saved by the user
` Predefined queries provided by your administrator
Predefined queries
Created and saved by user
Predefined Queries Navigate to Application AdministrationPredefined Queries to view

predefined queries for the application.

Sorting Data
Click the Sort icon in a column to sort data in ascending or

descending order
Click up arrow for Click down arrow for

ascending (A Z) order descending (Z A) order

Keyboard Accelerators
Provide an alternative to mouse clicking for performing

commands
` Also known as keyboard shortcuts
Two modes
Examples of record shortcuts 2
` Basic
` Extended
See online help for a full list of

keyboard shortcuts.
Select
HelpContentsIndex and
click the letter K
Extended Mode This mode makes use of a small ActiveX control downloaded one time to
the browser when starting the Siebel application. Extended mode allows
the ability to map any key sequence to Siebel commands. This is the
default setting and is the most commonly used mode.
Basic Mode This mode is for users who 1) Do not wish to download the ActiveX control
to their browser client, or 2) Use browsers that are not able to accept and
run ActiveX controls. Limitations are that you cannot map any key
sequences that are already used by the browser, and you cannot map any
key sequences that use special keys (such as function keys and up/down
arrow keys).

Controlling UI Presentation: Columns
Click the menu button and select Columns Displayed
Current columns
Columns in the list
available to be
used in the list
Click buttons
to sequence
Click buttons
columns
to add to or
remove from
Selected
Columns

Controlling UI Presentation: Show More
Toggle the list or form to show more or less detail for a record
1. Click Show
2
more button
2. to show
more details
in form

Summary

` Use the Siebel user interface (UI)

Lab
In the lab you will:

` Practice using the Siebel Call Center application


Organizing Data Behind the User Interface 3.1
Module 3: Organizing Data Behind the User

Interface
3

Module Objectives

` Describe how data is organized behind the user interface (UI)
` Describe the relationship between data in the database and data
in the UI
` Describe the relationship between lists, forms, views, business
components, and business objects

` Knowing these fundamental concepts is important to
understanding and configuring Siebel applications
Module 3: Organizing Data Behind the User Interface 2 of 17

Lists and Forms Display Related Business Data
The Siebel UI displays a collection of related business data

items in lists and forms
` Each field in a list or form represents a business data item
Record List 3
Form
Business data item
Record A record is a collection of related business data items presented in a list or

form.

Business Data Stored in Database
Each business data item is stored in a specific database table

and column
List and form data come from many tables and columns
Record Table and columns
Database
Business data item

Business Components
Are a collection of data in the database reorganized to reflect

the users business
Organize data from the users business perspective for
presentation in the UI
Table and columns

3
Multiple records
displayed in a list
Business
components
work here Database
Single record
displayed in a form
Business Component A business component is a collection of data organized to reflect the

users business. A business component represents related fields of data
in a list or form.
Data in the UI Data appears in the UI according to the users business perspective, and
not by how it is organized in the database
Applets Lists and forms are types of applets.

Lists and Forms Reference Business Components
Each list or form references one and only one business

component
List references
one business
component
Form references
one business
component

Common Business Components
Business components representing common Siebel business

entities include:
` Account
` Opportunity
` Service Request
` Contact
` Activity
3

View
A collection of related lists and forms representing a functional

business area
Business
area
Account
list
Account
form
View A view can also be referred to as a collection of applets, which may be of

the type Form or List.

Business Object
Organizes business components (BC) in relationship to each

other so related data can be displayed in a view
List references
one business
component Business
3
object is a
collection of
business
components
Form references
one business
component
Business Object Business objects organize data and present it in a view, similar to how
business components organize data and present it in lists and forms.

Business Objects Relate Business Data
A business object (BO) contains information about the

relationships between business components (BC)
Represents a collection of BCs and the relationship between
them
Account
Account Business component

Business
object
Opportunity Product Contact Business component

Parent and Child Business Components
A business object (BO) contains a parent (or master) business

component (BC)
All other BCs within the BO are child BCs of the parent BC
Account
3
Business Account Parent BC
object
Opportunity Product Contact Child BC
Relationships Parent and child business components typically represent one-to-many

record relationships. A view in the UI shows the relationship of more one
or more business components within one business object.

Example: Parent Business Component
The Account business component is the parent business

component for the Account Contacts view
` One account record per view
Account form references Record

Account Account parent
business component
Account
Opportunity Product Contact
Business
object

Example: Child Business Component
The Contact business component is a child business

component for the Account Contacts view
` One or more contact records are related to the account
Account
Account Contact list references

Contact child
3
business component
Record
Business
object

Determine Business Components for a View
Use HelpAbout View to determine business components for

a view
Parent business component Child business component

Siebel Applications
Are characterized by three distinct layers
1.Data presentation 2. Business logic 3. Data storage
Account
Account 3
Reference Siebel Tools and Configuration Guide

Summary

` Describe how data is organized behind the user interface (UI)
` Describe the relationship between data in the database and data
in the UI
` Describe the relationship between lists, forms, views, business
components, and business objects

Lab

` Use About View to determine business components and business
objects which organize and display data in some Siebel views


Exploring the Siebel Architecture 4.1
Module 4: Exploring the Siebel Architecture

Module Objectives

` Identify the pieces that make up the Siebel Web architecture
` Identify the process by which Siebel requests are processed and
sent to the Web client
` Identify the role of each component of the architecture

` Enables you to understand the relationship between Siebel
software components, preparing you to successfully install them
Module 4: Exploring the Siebel Architecture 2 of 23

Siebel Web Architecture Overview
At a high level, the Siebel architecture consists of:

` A relational database and file system that store business data
` Servers that manage the business data and provide batch and
interactive services for clients
` Web clients that access the business data
Web Server
4
Siebel
Servers
Siebel
Database File System
Server
Clients Clients are discussed in more detail in the next module.

Logical Architecture
The Siebel architecture consists of:
Browser
` Siebel Web Client (browser)
` Plugins for industry standard Web Server
Web servers Siebel Web Image
Server Extension
` Siebel Gateway Server Cache
` Siebel Enterprise Server

Gateway Server
` One or more Siebel Servers
` Siebel Server Components
` Database Server Enterprise Server
Siebel Server Siebel Server
` Siebel File System Component Component
Database Siebel
Server File System
Browser Access Client browser access might be different depending on client deployment.
Differences in the Siebel clients will be explored in the next module.
Reference Siebel Server Installation Guide

Siebel Clients
Run in a variety of environments

` Web browsers, WML devices, and PDAs (Windows CE and
Palm)
Two modes of interaction
Browser
` Standard mode
` High Interactivity mode
Web Server
Siebel Web Image

Connection state Server Extension Cache
stored on Siebel Server,
supporting reconnection
Gateway Server
if necessary
4
Enterprise Server
Component Component
Reference Siebel System Requirements and Supported Platforms
WML WML (Wireless Markup Language) is intended for use with narrowband
devices, including cellular phones and pagers.

Web Server and Siebel Web Server Extension
Web server
` Identifies and passes Siebel requests to the Siebel Server
` Passes completed HTML application pages back to browser
Siebel Web Server Extension (SWSE)
` Extends Web server to recognize URLs with Siebel requests
` Routes requests to the appropriate Siebel Server component
Web Server
Siebel Web Image
Server Extension Cache
Gateway Server
Enterprise
EnterpriseServer
Server
Siebel
SiebelServer
Server Siebel Server
Siebel Server
Component
Object Manager Component
Component
Workflow Manager
File System Manager
Stateless Connection The Siebel Web Server Extension connection to the Object Manager is
stateless. This allows sessions to be dynamically load balanced across
Web servers at the HTTP request level. It also improves Web server
scalability and availability.

Image Cache
Siebel component residing on Web server that reduces load on

Siebel Servers and file system
` Images published to Web server
` Allows parallel download of images
Web Server
Siebel Web Image

Gateway Server
Enterprise
EnterpriseServer
Server
4
Siebel
SiebelServer
Siebel Server
Component
Component
Workflow Manager
File System Manager

Gateway Server: Name Server
Serves as a single entry point for accessing Enterprise

Server(s)
Dynamically registers Siebel Server and component availability
` Assigns work based on components requested by SWSE
Stores component definitions and assignments, operational
parameters, and connectivity information
` Stored in siebns.dat file in shared directory
Web Server
Siebel Web Image
Gateway Server
Enterprise Server
Component Component
Gateway Server The Gateway Server runs as a Windows service or UNIX daemon
process.
Clustered The Gateway Server can be run in a clustered environment to provide

Environments redundancy and avoid a single point of failure.

Gateway Server: Connection Brokering
Directs client requests to the least-laden Siebel Server running

the desired component
` Does not apply to mobile and handheld client connections
Uses Resonate Central Dispatch (optional third-party software)
Web Server
Siebel Web Image
Gateway Server
4
Enterprise
EnterpriseServer
Server
Siebel
SiebelServer
Siebel Server
Component
Component
Workflow Manager
File System Manager
Exceptions Mobile and handheld Web clients connect directly to the Siebel Server.
These clients are covered in more detail in the next module.
Load Balancing To enable optional load balancing, Resonate must be installed.

Siebel Server
Processes requests from Siebel clients

Controls server components running on a machine
Obtains configuration information from the Gateway Server
Runs as a Windows service or UNIX daemon process
Enterprise Server
Workflow Manager
File System Manager
Database
Server
Siebel
File System

Server Component
A type of program that executes on a Siebel Server to perform

a specific function or job
Examples:
` Importing and exporting data
` Configuring the database to monitor for user-defined conditions
` Managing access to File System
` Processing of client requests
` Integration with CTI middleware
Examples:
Enterprise Server
Synchronization Manager 4
Workflow Manager
Object Manager Component File System Manager
Workflow Manager
File System Manager
Object Manager
Communications Server
Server Components Details about important server components are provided later in the
module.

Enterprise Server
Supports groups of users accessing a single database server

Logically groups Siebel Servers sharing configuration
information
Supports common administration via Siebel Server Manager
Installed and configured as part of the first Siebel Server
installation
Gateway Server
Enterprise Server
Workflow Manager
File System Manager
Database Siebel
Server File System

Object Manager
Server component that creates and processes data at multiple

levels
` UI layer (supported by the Siebel Web Engine)
` Business object layer
Processes business logic
` Data object layer (supported by Data Manager)
Manages resources and session state
Enterprise Server
Object Manager
Siebel Web Engine
Business Object
Component
4
BusinessObject
Business Object
Data Manager

Data Manager
Provides an abstraction layer for the Object Manager

` Separates queries from business logic processing
Performs object and relational mapping for the Object Manager
Dynamically generates database-specific SQL statements in
response to Object Manager requests
Passes data result sets back to the Object Manager
Enterprise Server
Object Manager
Component
Business Object
Business Object
Data Manager
Performance The Data Manager uses optimal database-specific queries to enhance

performance:
Uses database-specific client access libraries for the best
performance
Takes advantage of database-specific functionality
Optimized to return only fields necessary for a specific request and
manages large result sets by caching a larger working set.

Database Server
Stores Siebel data within a predefined database schema on a

third-party relational database management system (RDBMS)
Supports Siebel Server and client access through native SQL
Accessed by Data Manager
Gateway Server
Enterprise Server
Component
Compo Component
4
Object Manager
Data Manager
Database Siebel
Server File System
Extensible Schema The predefined database schema is extensible.

Siebel Web Engine
Siebel Web Engine (SWE) runs as a service as part of the

Object Manager
Constructs the UI
` Processes Siebel requests
` Assembles templates to construct page framework
` Requests retrieved data from Object Manager
` Generates HTML, WML, and XML from template and data
` Pages passed to browser via the Web server and SWSE
Siebel Server
Object Manager
Business Object
Web Server
Business Object
Siebel HTML SWSE Browser
Templates
Siebel Web Engine
Image
Cache
Markup Languages Hypertext Markup Language (HTML), Wireless Markup Language (WML),
and Extensible Markup Language (XML) are used to define content and
presentation in a browser.

Siebel File System
The Siebel File System is a shared directory that stores

compressed files used by Siebel applications
` Examples: Product literature, sales tools, presentations
Read/write access is controlled by the File System Manager
component on Siebel Server
Gateway Server
Enterprise Server
Component
File System Manager

4
Database
Server Siebel
File System

Web Usage Scenario
6 SWE builds HTML

Web Server page with data
Siebel Web Server and template tags
Extension which is passed
via the Web server
2 Web server to the browser
recognizes that URL
contains a Siebel
1 Browser generates request and passes it
HTTP request to the Siebel Web Object Manager SWE
Engine (SWE) 5
BusinessObject
Object requests
Business
retrieved
Siebel Web Engine data from
Data Object
Template used is Data Manager
Manager
Siebel 3 Manager
based on the view
Templates
requested as specified
by operation 4 Object Manager
retrieves data from
Siebel database or
external application
Inbound Siebel Data
Outbound

Overview: Logical Server Architecture
Web Server:
Provides access to Siebel clients, Web Server
processing requests using
Siebel Web Image
Siebel Web Server Extension
Gateway Server:
Provides access to and Gateway Server
distributes load for
Siebel Servers
Enterprise Server
Object Manager
Enterprise Server: Component Siebel Server:
(Includes SWE)
Group of Siebel Servers Runs one or more
that access the same components that supply
Database Server services to clients
4
Database
Database Server: Server File System:
Predefined tables and columns Siebel
Directory that stores
that store Siebel data File System
compressed files used
by Siebel applications

Physical Architecture
The Gateway Server, Siebel Server, Database Server, and File

System can be implemented on one machine or spread across
multiple machines
The Siebel Server(s) should have a high-speed LAN
connection to the Database Server
Enterprise Server
High-speed LAN
Gateway Server
Siebel Server
Web Server
SWSE
Siebel
File System
Siebel Server
Firewall Firewall Database

Server

You Decide
Consult the documentation to determine which software to

install on which machine(s) given your environment and
requirements

Summary

` Identify the pieces that make up the Siebel Web architecture
` Identify the process by which Siebel requests are processed and
sent to the Web client
` Identify the role of each component of the architecture

Lab

` Match Siebel architecture components to their descriptions


How Clients Access Siebel Data 5.1
Module 5: How Clients Access Siebel Data

Module Objectives

` Identify the various Siebel clients
` Identify how each client accesses Siebel Servers and data

` To deploy Siebel clients, you must understand the architecture
that supports them and how each client accesses Siebel Servers
and data
Module 5: How Clients Access Siebel Data 2 of 24

Siebel Clients: Overview
Use a standard Web browser to Browser

display information in the user
interface (UI) with data retrieved
Web Server
from the Siebel database
Siebel Web
Access Siebel data differently based Server Extension
on client type
` Not all connect through Web Server Gateway Server
and Siebel Web Server Extension
(SWSE)
Enterprise Server
Component Component
Database Siebel 5
Server File System

Siebel Clients: Overview Continued
Five types deployed in Internet or intranet environments

` Siebel Web client
` Siebel Wireless Web client
` Siebel Handheld client
` Siebel Mobile Web client
` Siebel Dedicated Web client
Web Wireless Web Handheld Mobile Web Dedicated Web
Reference Siebel Web Client Administration Guide

Client Access Overview
Access to Siebel data differs based on client type

` Web and Wireless Web Clients connect through Web Server
` Handheld and Mobile Web Clients connect through Gateway Server
` Dedicated Web Client connects directly to Siebel database
Wireless Web Web
Mobile
Handheld Web
Web Server
Siebel
Dedicated Servers
Web
Siebel
Database
Server
File System
5

No Software on Web and Wireless Web Clients
Web and Wireless Web clients do not require Siebel software

installation
` Siebel applications run in standard browsers
` Connection state stored on Siebel Server
Web Server
Browser
Siebel Web
Server Extension
Gateway Server
Enterprise Server
Component Component

Siebel Applications
Consist of:
` An object manager
` Configuration (.cfg) file or Object Manager component
parameters defining the repository file and database
` A repository (.srf) file that specifies the configured application
` A set of template files that specify how to render the UI in the
users browser Web Clients
` A relational database Mobile and Dedicated Web Clients
Templates
Object Manager
Parameters
.srf
.cfg
Database 5

Siebel Application Components
Data that specifies the application is separate from the engine

that executes the application
Web Clients
Mobile and Dedicated Web Clients
Templates
Object Manager
Parameters
.srf
.cfg
Database

Object Manager
The Object Manager is an engine for Siebel eBusiness

Applications
` Builds a Siebel application at run time
` Single and reusable
` Same Object Manager for all applications
` Supports multiple users
Templates
Object Manager
Parameters
.srf
.cfg
Database
Web Clients
5

Siebel Repository File (.srf)
Separate file with object definitions that contain the application

configuration
` UI objects specify the data presentation
` Business objects specify the business rules and processes
` Data objects specify the data organization and storage
Used with Object Manager, builds a Siebel application at run
time Web Clients
Templates
Object Manager
Parameters
.srf
.cfg
Database

Configuration File and Component Parameters
Contains initialization settings for the Object Manager

including:
` Gateway Server ` LDAP directory server
` Enterprise Server ` File system
` Repository (.srf) file ` Database server (data source)
` Application or server component
Templates
Object Manager
Parameters
.srf
.cfg
Database
Web Clients
5

Configuration File and Component Parameters Continued
Some clients obtain initialization settings from both the

configuration file and Object Manager component parameters
` Web client
` Wireless Web client
Some clients obtain initialization settings exclusively from the
configuration file
` Mobile Web client
` Dedicated Web client
` Handheld client

Application Component Locations
For Web and Wireless Web Clients, components reside on the

server
For all other clients, components reside on the client
5

Web Client
Accesses Gateway Server and Siebel Server through Web

Server running SWSE
Accesses Siebel data through Object Manager
Results transformed by Siebel Web Engine and returned as
HTML pages to client browser
Gateway Server Web Server
Siebel Web
Enterprise Server Server Extension
Siebel
Siebel Server
Server
Object Manager
BusinessObject
Object HTTP
Business
Siebel Web Engine
Web Client
Data Manager
.cfg
.srf
Database Siebel
Server File System

Web Client Continued
Uses Web browser to launch HTML page specifying .swe page

.swe page invokes SWSE
SWSE (eapps.cfg) parameters identify Object Manager
Object Manager component parameters specify Enterprise
Server, Siebel Server, .cfg, and .srf
Web Client
.swe (SWSE)
Object Manager
5

Wireless Web Client
Connects to a Wireless Application Protocol (WAP) server

connected to a Web server with SWSE installed
Connects to a database server through the Object Manager
` Results are transformed and returned as WAP pages
Gateway Server Web Server

Siebel Web
Enterprise Server
Server Extension
Siebel Server
Siebel Server
Object Manager WAP Server
BusinessObject
Business Object
Siebel Web Engine

Data Manager
Wireless
Web Client
.cfg
.srf
Database Siebel
Server File System
WAP Server This is an extension to a Web Server to support wireless Web access. The
Wireless Application Protocol is a version of XML.
Reference Siebel Wireless Administration Guide

Handheld and Mobile Web Clients
Access local .cfg and .srf files

Directly access a local database and Siebel File System
Directly connect to their designated Siebel Server for
synchronization
Enterprise Server
Mobile/Handheld
Siebel
Siebel Server
Server Client
.cfg .srf
Object Manager
BusinessObject
Business Object
Siebel Web Engine

Data Manager
Database Siebel
File System
Server
5

Handheld and Mobile Web Clients Continued
Launch siebel.exe from program group or startup icon

Startup switch identifies .cfg
.cfg identifies .srf, application, local database, and Siebel
Server
Mobile and Handheld are not zero-footprint applications
Mobile Web
Client

Disconnected Processing
For disconnected activity, processing is provided by a local

Object Manager, Data Manager, and Siebel Web Engine
` Processing provided on client
` HTML delivered to browser by local Web server with SWSE
Mobile/Handheld
Client
Web Server
.cfg .srf
SWSE
Object Manager
BusinessObject
Business Object
Siebel Web Engine

Siebel
Siebel Server
Server
Data Manager
5
Disconnected Disconnected processing refers to handheld and mobile Web client

Processing processing which has no connection to a Siebel Server or database
server.

Dedicated Web Client
Uses the Mobile Web clients local processing to support

dedicated access to database
` No requirement for Web Server or SWSE
` Not a zero-footprint application
Dedicated Web
Enterprise Server
Client
Siebel Server
Web Server
Component
SWSE .cfg .srf
Object Manager
Business Object
SWE
Data Manager
Database Siebel
Server File System

All Clients
Siebel architecture supports a mixture all clients
Wireless WAP Web Server

Web Client
Web Client Server SWSE
Gateway Server
Dedicated Web Enterprise Server

Client Mobile/Handheld
Siebel Server Client .cfg .srf
Web Server
Object Manager
SWSE
Object Manager
Siebel Web Engine
Data Manager
Siebel Web Engine Component
Data Manager .cfg .srf
.cfg
Database Siebel
.srf Server File System
5

You Decide
Consult the documentation to determine which software to

install on which machine(s) given your environment and client
requirements

Summary

` Identify the various Siebel clients
` Identify how each client accesses Siebel Servers and data
5

Lab

` Complete a possible deployment diagram

Installing Siebel Software 6.1
Module 6: Installing Siebel Software

Module Objectives

` Install the Siebel Gateway Server, Siebel Server, Enterprise
Server, and Database Server to set up your Enterprise Server
environment
` Test server-to-database connectivity

` To determine correct installation parameters values
` To install Siebel software successfully
Module 6: Installing Siebel Software 2 of 25

Consult the Documentation
Siebel System Requirements and Supported Platforms

Siebel Release Notes
Siebel Server Installation Guide
Siebel Web Client Administration Guide

6

Pre-Installation Tasks
Prepare for installation

Create operating system account(s)
Create the Siebel database
Create the Siebel file system directory and share it
Siebel Web Client Administration Guide

Prepare for Installation
Verify prerequisites defined in the documentation

` Supported hardware
` Supported operating system (OS)
` Required third-party software

6

Prepare for Installation Continued
Identify where software will be installed

` Which machine(s)
` What naming convention
` What directory structure
Enterprise Server
Example:
Gateway Server
Siebel Server
G1
Web Client S1 Siebel
File System
C1
Machine/Host Web Server D1

Names/Addresses: C1, G1, S1, D1, W1
W1 Database
Server
D1 The machine running the third-party database software.
G1 The machine running the Siebel Gateway Server software.
S1` The machine running the Siebel Server software.
W1 The Web Server machine running the Siebel Web Server Extension
installed to access the Gateway and Siebel Servers.
C1 The machine running the client browser.

Create Operating System Account(s)
Create the Siebel Service Owner Account

` Used to run Enterprise Server processes and components
Create the Siebel Monitoring Account
` Required by optional Resonate Central Dispatch connection
brokering software
Consult the Siebel Server Installation Guide for exact steps and
privileges
Example:
NTSERV

6
Owner Account The Siebel Service Owner Account is used to run Windows processes or
start UNIX daemon processes.

Create the Siebel Database
Install the proper version of third-party RDBMS software

Create an empty database/tablespace with appropriate space
defined
Consult the Siebel Server Installation Guide for recommended
database configuration parameter settings
Example:
Machine Name: D1 D1
Database: siebeldb
Size: 500 MB siebeldb
Siebel Database The database administrator uses database vendor tools to create the
database. The scripts refer to the database using the default name
siebeldb. You may change the name.

Create the Siebel File System
Create the Siebel File System as a directory on a disk with

sufficient space
Must be accessible from machines running Siebel Enterprise
Servers and Siebel clients
Must support long and case-sensitive filenames
Example:
S1
Machine Name: S1
File System: C:\siebfile
C:\siebfile

6
File System The default name is siebfile. You may change the name.

Install and Verify Siebel Software
Install and verify:

` Gateway Server
` Enterprise and Siebel Servers
` Siebel Database Server
` Siebel Web Server Extension
` Prerequisite third-party or ancillary products (FirstLogic, Fulcrum,
and so forth) required by Siebel Servers
Installation The Gateway Server, Enterprise and Siebel Servers, and Siebel Database
Server can be installed either separately or simultaneously.
Client Browser Clients require a third-party browser on the client.

Install Gateway Server
Invoke server installation program to install and configure

Gateway Server on its designated machine
Example:
Gateway Server
Destination Directory: C:\sea701
G1
OS Account: NTSERV
Machine Name: G1
G1
Follow steps in installation wizard and consult documentation

6
Distributed Software As depicted earlier, depending on your deployment, you may run the
installer on multiple machines to distribute server software.
OS Account The account name is the operating system account that was created in the
pre-installation tasks.

Verify Gateway Server
Inspect directory and files in the Siebel root directory

Verify the Windows Service or UNIX daemon process is started
Example:

Install Enterprise and Siebel Servers
Invoke server installation program to create and configure an

Enterprise Server, Siebel Server, and ODBC data source
Example:
Gateway Name Server Hostname: G1
Enterprise Server
Enterprise Server Logical Name: siebel
siebel
File System: HQ\G1\c:\siebfile Siebel Server
Database Machine Name: D1 S1
Database/Tablespace: siebeldb
S1
Database User/Password: SADMIN/SADMIN C:\siebfile
Siebel Server Machine Name: S1

Siebel Server Logical Name: siebel_S1
SiebSrvr_siebel
OS Account: NTSERV
ODBC Data Source

6
siebel The default name for the logical grouping of servers in the enterprise. You
may set this to a different string of characters with a maximum length of 12
characters.
File System The file system is a shared directory.
siebeldb The default name of the database that was created in the pre-installation
tasks. It will contain the Siebel database tables.
SADMIN The default name for the system administration database login. It is
created when the grantusr.sql script is run as part of the database server
installation. SADMIN also corresponds to the default Siebel employee
created in the seed data.
siebel_S1 The name of the Siebel Server. You may set this to a different string of
characters.

Verify Enterprise and Siebel Servers
Inspect directory and SESsetup.log file in the Siebel root

directory
Verify the Windows Service or UNIX daemon process is running
Example:

Install Database Server
Invoke server installation program to install the DB Server

Configuration utility and its associated files
Run grantusr.sql script to create database users
Use the DB Server Configuration utility to create the database
schema and populate seed data
Use the DB Server Configuration utility to populate repository
data
Siebel Database Server Directory: C:\sea701\dbsrvr
Siebel Server directory: C:\sea701\siebsrvr Database
Server
Database User/Password: SADMIN/SADMIN D1
Database Table Owner: SIEBEL/SIEBEL
siebeldb
ODBC Data Source Name: SiebSrvr_siebel

6
SADMIN The default name for the system administration database login. Here it is
used to create the ODBC datasource. Since this corresponds to the
default employee in the seed data, you should not change this.
SIEBEL The default name of the siebeldb database owner. The login and owner
are set when the grantusr.sql script is run. There is no corresponding
employee. Therefore, you may change this value by modifying scripts and
parameters.
Reference Siebel Server Installation Guide for Microsoft Windows

Siebel Server Installation Guide for UNIX
Siebel Tools Reference

Verify Database Server
Inspect directory and log files

Verify database connection
Verify schema and seed data
Verify repository data
Example:

Install Siebel Web Server Extension
Install required Web Server

Install Siebel Web Server Extension
` Invoke eappweb installation program
Example:
Siebel Web Server Extension

Destination Directory: C:\sea701\SWEApp
Web Server
Gateway Server Machine Name: G1
SWSE
Enterprise Server Logical Name: siebel
Siebel Server Logical Name: siebel_S1
W1

6
G1 The name of the machine on which the Gateway Server was installed.
siebel The default name for the logical grouping of servers in the enterprise.
siebel_S1 The name of the Siebel Server. You may set this to a different string of
characters. Avoid spaces.
W1 The name of the machine on which the Web Server is installed.

Verify Siebel Web Server Extension
Inspect Web Server virtual directories on Internet Information

Server

Enter License Key
When initially connecting to the server, enter the license key

Connect to the server with Siebel Tools or the Mobile Web
client and enter the key when prompted

6

Managing License Keys
Once you have entered the license key, you can add, modify,
or delete license keys
` Navigate to Application AdministrationLicense Keys to add
additional products

Verify Client
Verify application launch and connectivity to server

Example:
Web Server Siebel Application SWE Command

6
SWE Command The SWE command is processed by the Siebel Web Engine. In this
example, the request is that SWE deliver the start page for user SADMIN.

Post Installation
Example:
Enterprise Server
Gateway Server
siebel
Siebel Server
G1
S1
G1
S1 File System
Client C:\siebfile
C1
D1
Web Server
SWSE
siebeldb
W1
Web Server running Siebel Database Server
Web Server Extension

Classroom Installation
In the classroom, students will install all software on their

desktop machines
Gateway Server D:\sea701\gtwysrvr
HOSTNAME00
Enterprise Server Siebel Server D:\sea701\siebsrvr

siebel
HOSTNAME00
Siebel Web D:\sea701\SWEApp
Web Server
Server Extension
siebeldb
HOSTNAME00 Database Server D:\sea701\dbsrvr
C:\siebfile File System D:\siebfile
Mobile client C:\sea701\client

6

Summary

` Install the Siebel Gateway Server, Siebel Server, Enterprise
Server, and Database Server to set up your Enterprise Server
environment
` Test server-to-database connectivity

Lab

` Install a Siebel Server Environment Please follow the
` Run scripts to create users in the directions carefully, and
Siebel database pay attention to the
parameters you are
` Install a Siebel Database Server entering
` Install a Siebel Mobile Web Client
Please type in the case
` Install a Siebel Web Server (upper versus lower) that
Extension is specified
` Verify client to server connectivity
` Prepare a virtual directory for a second Object Manager

6


Server Administration 7.1
Module 7: Server Administration

Module Objectives

` Use Server Manager to administer your Siebel Enterprise

` Server Manager enables you to perform server administration
duties required for your Siebel application
Module 7: Server Administration 2 of 27
Reference Siebel Server Administration Guide

Server Manager
Is a set of views that allow you to manage your Siebel

Enterprise

Server Manager Continued
Is used for a variety of administration duties, including:

` Enable, disable, startup, and shutdown components
` Assign components to execute on specific Siebel servers
` Stop, pause, and resume server tasks
` Monitor status for components and tasks
` Set parameters for servers and components

Administering the Siebel Enterprise
Server Manager connects to the Gateway Server

` Gathers all connectivity information for each Siebel Server within
the Siebel Enterprise
Server Manager then connects to each Siebel Server within the
Enterprise
` Displays servers for each enterprise supported by the Gateway
Server
Starts a Server Manager task on

each Siebel Server

Using Server Manager
There are two ways to use Server Manager
From the Siebel

application interface
From the command line

Server Components
A component is a type of program that performs a specific job

` One or more instances can execute as a task on the Siebel
Server
The standard Siebel application comes with many server
components, for example:
` Enterprise Integration Manager
For importing and exporting data
` Assignment Manager
For assigning work based on business rules
` Generate Database Triggers
For monitoring the database for user-defined conditions

Component Groups
Component Groups consist of related server components

Navigate to Server AdministrationEnterprise Configuration to
enable or disable component groups
Click the menu button
enable or disable component group

Component Groups Continued
Example: The Workflow Management component group

consists of five server components
Component group must

be enabled to utilize any
of the server
components
Enable Component To execute components on the Siebel Server, the component group to
Groups which they belong must be enabled.
7

Component Definitions
Use to customize existing components

` Example: Modify component definition so that the same
parameter values are in effect each time the task executes
Use to create custom components
` Example: Create EIM component definition called Import
Accounts to only import accounts
Navigate to Server AdministrationEnterprise Configuration
Component Definitions
Parameters
for the Call
Center Object
Manager
component

Tasks
When a component executes, it is called a task

` A task is an instantiation of a component and runs in computer
memory
` The same component may be instantiated many times
Example: Multiple Batch Assignment tasks can run concurrently on
the server
Several tasks can

run simultaneously

Setting Parameters
At startup, a task reads parameters and executes according to

their values
` Example: Define the assignment object to be used in a Batch
Assignment task
` Example: Define which mobile clients to extract in the Database
Extract task
Two types of parameters
` Static
Cannot be changed for executing tasks
Changes are effective for subsequent tasks
` Dynamic
Can be changed for executing tasks and take effect immediately

Setting Parameters Continued
Parameters are set at any of these levels

` Enterprise Highest
` Server
` Component Definition
` Server Component
Lowest
` Task
A parameter set at the task level overrides the same parameter
set at a higher level
Parameter Hierarchy Parameters set at the Enterprise level can be overridden by the same
parameters set at levels below it. This is also true for parameters set at
the Server, Component Definition, and Server Component levels.
7

Server Component Modes
A server component executes in one of three modes

` Batch
` Background
` Interactive

Batch Components
The task runs until completion, and then it stops

Started manually via:
` Graphical user interface
` Command-line interface
Examples
Subset of Enterprise Application

Integration component group
Subset of Remote component

group
Subset of Workflow Management

component group
Run Mode To determine the run mode for a component, navigate to Server
AdministrationEnterprise ConfigurationEnterprise Component Groups.
7

Synchronizing Batch Components
Must be synchronized between the Gateway Server and the

Database Server
` This post-installation task is required in order to execute batch
components on the Siebel Server
Navigate to Server AdministrationEnterprise Configuration
Batch Component Admin
` Click Synchronize button
Synchronized components
Synchronizing Synchronize also needs to be performed whenever batch component

Components definitions change, such as when parameters are updated or new
component definitions are created.

Background Components
The task runs continuously until the component is shutdown

` Runs repetitively, defined by a sleep time
Started:
` Manually via command line
` Automatically upon server startup
Examples

group
Subset of Workflow Management

component group
Default Tasks Components with the parameter Default Tasks > 0 will start automatically
Parameter when the Siebel Server is started. Navigate to Server Administration
Enterprise ConfigurationComponent Definitions to view or modify
component parameters.
7

Interactive Components
The task runs in response to client requests

` No need to manually start
The task stops when the client disconnects
Examples

group
Subset of System Management

component group
Subset of Siebel Call Center

component group
Run Mode To determine the run mode for a component, navigate to Server
AdministrationEnterprise ConfigurationEnterprise Component Groups.

Component States
A server component may be in one of five states
State Description
Online Tasks are currently not running for the assigned component, but
new tasks can be started.
Running Tasks are currently running for the assigned component on the
Siebel Server, and new tasks are allowed to start.
Offline Currently running tasks continue to run, but new tasks cannot be
started for the component.
Shutdown No processes are running for the component, and new tasks
cannot be started.
Unavailable Multi-threaded components that should be running are not,
indicating a run-time error.
Unavailable State When enabled multi-threaded components are unavailable, this indicates a
run-time error. Check the log files on the Siebel Server to troubleshoot the
problem.
7

Managing a Component
Navigate to Server AdministrationServersServer

Components to change a server component state
Select the component and click the appropriate action

Starting a Batch Task
Navigate to Server AdministrationEnterprise Operations

Component Requests
1. Create new request

and select component
2. Modify parameters 3. Submit request
Component/Job This list is populated when the batch components are synchronized on the
Siebel Server.
7
Parameters Parameters set at the task level override the same parameters set at other
levels.
Submit Request Click the menu button in the Component Requests form and then select
Submit request.
Command Line Batch tasks can also be started using server manager from the command
line.

Starting a Background Task
Via the UI
` Tasks with the parameter Default Tasks > 0 will start automatically
upon Siebel Server startup
Example: Transaction Router will
automatically start on the server
Using the command line

` Example: Start a Workflow Monitor Agent task
Component alias Siebel Server Parameters

Monitoring a Task
A task updates its state during execution

` Can be in one of the following states
State Description
Starting up Indicates that the task has been started
Running Indicates that the task is executing normally
Paused Indicates that the task has been temporarily placed in a
suspended state
Shutting Down Indicates that the task has been instructed to stop, or the
component or server is being shut down
Completed Indicates that the task ran to completion and exited normally
Exited with Error Indicates that the task encountered an error during its
processing and exited
Killed Indicates that the process was not able to shut down cleanly,
and had to be forced to shutdown
Task State The task state can be seen in the UI, in any of the following views:
Enterprise Task, Server Tasks and Tasks. The task state can also be
determined from the command line:
7
Srvrmgr> list state values for task <task number>

Viewing Task Information
Each task creates a log of its execution

View log via UI by drilling down on task number
Drill down
on task
number
to view
Task Info Log
Event Logging Event logging writes events to the log file based on the log level for each
event type. Events are logged at the server and component level. For
more information on configuring server events and component events, see
the Siebel Server Administration Guide.

Viewing Task Information Continued
View log file on the Siebel Server
Note
the task
number
View file in /log directory
Log Files In Windows environments, the log files are stored in:
<Siebel_server_root>/siebsrvr/log
In UNIX environments, log files are stored in: 7
<Siebel_server_root>/enterprises/<siebel enterprise>/server/log

Summary

` Use Server Manager to administer your Siebel Enterprise

Lab

` Enable server components
` Synchronize batch components
` Start a task and view its log
` Use command-line Server Manager


Access Control and Views 8.1
Module 8: Access Control and Views

Module Objectives

` Describe Access Control for Siebel eBusiness Applications
` Describe the difference between view level Access Control and
data level Access Control
` Identify the access control mechanisms used to restrict access to
views in Siebel eBusiness Applications
` Describe the relationships between views, users, and
responsibilities

` To effectively use Siebel eBusiness Applications, you need to
understand how access to views is controlled
Module 8: Access Control and Views 2 of 14
Reference Authentication and Access Control Administration Guide

Business Problem
Different users need access to different information

Access to information must be controlled so that
` Information is easy to find
` Users see only appropriate information
Customers
CFO Field Sales Rep
Opportunities
Forecasting
Orders
Channel Partners
Call Center Agent
Service Requests Opportunities


Siebel eBusiness Solution: Access Control
Consists of all mechanisms used to control user access to

views and data records in Siebel eBusiness Applications

Types of Access Control
View level Access Control (discussed in this module)

` Controls user access to views in Siebel eBusiness Applications
Data level Access Control (discussed in the next module)
` Controls user access to data records in Siebel eBusiness
Applications

Access to Views
Users require access to different views based on their job

function or role, for example:
` Call center agents need access to views displaying service
requests, calls in their queue, and campaign information
` Customers need access to views displaying their current orders
or available products
` Partners need access to views displaying sales opportunities or
service requests

Responsibility
Determines the set of views to which a user has access

Corresponds to a users job function or role
Views
associated with
the Field Sales
Representative
responsibility

Adding Views to Responsibilities
The same views can be added to one or more responsibilities
Call Center
Manager and
Universal Agent
responsibilities
share a common
set of views

Assigning Users to Responsibilities
Users can be assigned to one or more responsibilities
Mike Masters is
assigned to both
responsibilities:
Call Center
Manager and
Universal Agent

Multiple Responsibilities
When users log in, they see the union of all views for their
assigned responsibilities

Review: Users, Views, and Responsibilities
Responsibilities determine the set of views to which a user has

access
Views are associated to one or more responsibilities
Users are assigned to one or more responsibilities
A user sees the union of all associated views when he or she
logs in

Restricted Access to Views
If a view is not included in a users responsibility, the user will

not see a reference to the view in the:
` Site map
` Show drop-down list
` Detail tabs
If a user does not have access to any of the views in a screen:
` Screen tab is not displayed

Summary

` Describe Access Control for Siebel eBusiness Applications
` Describe the difference between view level Access Control and
data level Access Control
` Identify the access control mechanisms used to restrict access to
views in Siebel eBusiness Applications
` Describe the relationships between views, users, and
responsibilities

Lab

` Explore responsibilities and views for different users

Access Control and Data 9.1
Module 9: Access Control and Data

Module Objectives

` Describe the difference between master data and customer data
in Siebel eBusiness Applications
` Describe the different Access Control mechanisms used to
restrict access to data in Siebel eBusiness Applications

understand how access to data is controlled
Module 9: Access Control and Data 2 of 24

Types of Data
Customer data (discussed in this module)

` Includes dynamic, transactional data such as opportunities and
orders
` Is created and managed by users of the application
` Has access controlled at the record level
Master data (discussed later in the course)
` Includes static, referential data such as products and literature
` Is created and maintained by company administrators
` Can be grouped into catalogs and categories
` Can have access controlled at the catalog and category level

Controlling Access to Customer Data
Access to customer data can be restricted using the following

access control mechanisms
` Personal
` Position-based
` Organization-based

Personal Access Control
Access is limited to records a that user has created or to which

a user has been assigned
` Records can be restricted to a single user or a team of users
` Access is controlled by user ID
Examples
` In the My Service Requests view, a Web site visitor can see only
the service requests he or she has created
` In the My Expense Reports view, an employee can see only the
expense reports the employee has submitted for reimbursement
` In the My Activities view, a user can see only the activities the
user owns

Position-Based Access Control
Record access is limited to users based on their position within

an organization
A position is:
` A job title in a hierarchical reporting structure of an internal or
partner organization
` Represents a person or group of people that require access to a
set of data
` Is more stable than an individuals assignment to that position
People might change, but a position is static

Employees Per Position
Some positions have a single employee

` Typical toward the top of a reporting hierarchy where a job is
more specialized
For example, CEO, VPs
Some positions have multiple employees
` Typical toward the bottom of a reporting hierarchy where a job is
less specialized
For example, a group of call center agents all doing the same work
Roger Smith is associated with the CEO position

Primary Employee
When there are multiple employees per position, only one

employee is defined as the primary employee for a position
` When a position is assigned to a record, the primary employees
name appears in the primary field for the record, even if other
users are associated with the same position
Click the
select button
in the Last
Name field to
see all
employees
per position
One employee
is defined as
primary
employee for a
position

Positions Per Employee
Employees can have multiple positions if they do different

types of work or need to see different sets of data
Max Adams is associated with the

Call Center Manager, Field Sales
Representative, and Marketing
Administrator / Analyst positions

Primary Position
If an employee has multiple positions, one is marked as

primary
Click the select

One position is button in the
defined as Position field to
primary for an see all positions
employee per employee

Change Position
Users can change position during a session by selecting

ViewUser PreferencesChange Position
Users can only log in as one position at a time
By default, log in is based on the users primary position

Types of Position-Based Access Control
One or more positions can be associated with customer data

using the following types of position-based Access Control:
` Single position
` Team

Single Position Access Control
Assigns a single position to an individual record

` All users associated with the position have access to the record
In the My Quotes view, use the

Sales Rep field to assign a single
position to a record

Team Access Control
Assigns multiple positions, in the form of a team, to an

individual record
` All users associated with positions on the team have access to
the record
` A team can include internal and partner positions
In the My
Opportunities view,
use the Sales Team
field to assign
multiple positions to
a record

Team Fields
Vary according to the view in which they appear

Examples
` My Opportunities view has a Sales Team field
` My Accounts view has an Account Team field
` My Contacts view has a Contact Team field

Primary Position on a Team
One position on a team is designated as primary

By default, the position of the user who creates the record is
automatically placed on the team as primary
Primary position has additional privileges, such as:
` Merging and deleting records
` Forecasting an opportunity
` Designating another position as primary
Casey Chengs position is primary on this team

Organization-Based Access Control
Record access is limited to the organization(s) to which a

users positions are assigned
Provides another level of Access Control at the level of
business organizations rather than at the level of individual
users

Organization
Represents a part of a business enterprise for purposes of

restricting access to records
` Allows you to partition your company into logical groups, and then
display information appropriate to each of those groups
For example, you can restrict access to records for:
` Part of your company (division, department, business unit)
` A partner company that assists you in your business (channel
partner)
` An external company that purchases your products (account)

Types of Organization-Based Access Control
One or more organizations can be associated with data using

the following types of organization-based access control
` Single organization
` Multiple organization

Single Organization Access Control
Assigns a single organization to an individual record

` All users associated with the assigned organization have access
to the record
In the My Contacts view, use the

Organization field to assign a
single organization to a record

Multiple Organization Access Control
Assigns multiple organizations to an individual record

` All users associated with the assigned organizations have access
to the record
In the My Opportunities
view, use the Organization
field to assign multiple
organizations to a record

Review: Access Control Mechanisms
Personal Access Control

` Access is limited to records that a user has created or to which a
user has been assigned
Position-based Access Control
` Record access is limited to users based on their position within
an organization
Organization-based Access Control
` Record access is limited to the organization(s) to which a users
positions are assigned
Mechanisms are not mutually exclusive
` A record can be restricted by more than one Access Control
mechanism

Summary

` Describe the difference between master data and customer data
in Siebel eBusiness Applications
` Describe the different Access Control mechanisms used to
restrict access to data in Siebel eBusiness Applications

Lab

` Explore data level Access Control for different users

Access Control and View Types 10.1
Module 10: Access Control and View Types
10

Module Objectives

` Identify the independent relationship between view access and
data access
` Identify the different view types used to accommodate the Access
Control needs of different users

understand the different available view types
Module 10: Access Control and View Types 2 of 12

Relationship Between Views and Data
Access to views is independent of access to data

` For example, Mike Jones and Casey Cheng have access to the
same view based on their responsibilities, but see different data
in the view based on their user ID, position, or organization
10

View Types
Different view types accommodate different users

` My View
` My Teams View
` All View
` All Across Organization View

My View
Displays records for which a user has direct access

` Can use any Access Control mechanism
` Examples: My Opportunities, My Accounts
10

Special Access Views
Additional views have been created to accommodate

managers, administrators, and executives who have data
access needs that go beyond Access Control rules
` My Teams View
` All View
` All Across Organization View

My Teams View
Used by managers to display records for users who report to

them
` Examples: My Teams Opportunities, My Teams Service
Requests
10

All View
Used by administrators within an organization to display

records for the organization, where a valid owner has been
assigned to the record
` Examples: All Accounts, All Opportunities, All Service Requests

All Across Organizations View
Used by executives to display records for all organizations,

where a valid owner has been assigned to the record
` Examples: All Accounts Across Organizations, All Opportunities
Across Organizations
10

Administration Views
Displays all records in the database, even those without a valid

owner
` Navigate to Data Administration
` Because they shows all records in the database, access to these
views should be limited to very few people in your organization

Summary

` Identify the independent relationship between view access and
data access
` Identify the different view types used to accommodate the Access
Control needs of different users
10

Lab

` Explore different view types

Creating an Organization 11.1
Module 11: Creating an Organization
11

Module Objectives

` Define your companys organizational hierarchy in the Siebel
application

` Provides a framework for creating your companys reporting
structure, which ultimately determines record and view access for
employees
Module 11: Creating an Organization 2 of 14

Organizational Hierarchy
Allows for the definition of organizations, divisions, and

positions
Use a top-down approach to define the company structure
Organization Siebel Europe
Division Northern Europe

Consulting
Professional Services, Professional

Sub-division Services, Galway
Amsterdam
Positions Consultant
Consultant 7 8 Consultant
Consultant 9 10
11

Defining the Company Structure
Create the company structure by defining:

` Organizations
` Divisions
` Positions
` Responsibilities
` Employees
Company structure determines the records and views to which
employees have access

Defining Organizations and Divisions
Allows your company to:

` Partition itself into logical groups, and then segregate data based
on these groups
` Limit access to data based on the organization(s) and divisions(s)
to which positions are assigned
Organization
Siebel Europe
Southern Europe Division Northern Europe

Consulting Consulting
Sub-division
Professional Professional Professional Services, Professional

Services, Madrid Services, Rome Amsterdam Services, Galway
Consultant
Consultant 3 Consultant 6
Consultant 9 10
11

Defining Divisions
Navigate to Group AdministrationDivisions
Explorer view
Required field Required field
Creating Divisions Use caution when creating a division. Once you create a division:
You cannot delete it
You cannot change the organization.

Defining Organizations
Set Organization Flag to make a division an organization
Organization appears in Explorer View
Set flag
Divisions Organization A divisions organization will be the organization of its parent division. In
the event the parent division is null, the divisions organization will be the
default organization.
11

Defining Organizations Continued
Navigate to Group AdministrationOrganizations
Explorer View
Required fields:
Name, Currency
Creating Organizations Use caution when creating organizations. Once you create an
organization, you cannot delete it.
Organization Skills Optionally, you can define skills for your organization. For example, you
can define language or product expertise skills. Organization skills can be
used by Assignment Manager to assign work appropriately. You will learn
about Assignment Manager later in the course.

Defining Positions
Navigate to Group AdministrationPositions

Create positions based on your reporting structure
` Ask the question Who needs to see what?
Explorer View
Reporting relationship
Required fields:
Division, Position
Parent Position Specify a parent position to set up a reporting relationship.
Position Skills Optionally, you can define skills for positions, for example, language or
product expertise. Position skills can be used by Assignment Manager to
assign work appropriately. You will learn about Assignment Manager later
in the course.
11

Defining Responsibilities
Navigate to Application AdministrationResponsibilities
1. Create
responsibility
2. Associate
views to
responsibility
Predefined There are many predefined responsibilities provided as part of the Siebel
Responsibilities seed data.

Defining Employees
Navigate to User AdministrationEmployees to define

employees
Required fields Associate one or Associate one or

more positions more responsibilities
Specify additional data for the employee
Employees View Use this view to define other specific employee data, such as availability
and skills.
Employee Skills Optionally, you can define skills for your employees, for example,
language or product expertise. Employee skills can be used by
Assignment Manager to assign work appropriately. You will learn about
Assignment Manager later in the course.
11

Position and Responsibility
There is no relationship between position and responsibility

Employees are assigned:
` One or more positions
` One or more responsibilities
Division Professional Services,

Amsterdam
Responsibility
Consultant
Consultant 7 8 Sales Manager
Positions
All Opportunities
My Teams Accounts Views
All Accounts
Reference Siebel Applications Administration Guide

Summary

` Define your companys organizational hierarchy in the Siebel
application
11

Lab

` Create the ABC organization hierarchy

Authenticating Users 12.1
12
Module 12: Authenticating Users

Module Objectives

` Describe the difference between authentication and Access
Control
` Describe internal and external authentication and how each
works in Siebel eBusiness applications

` To effectively manage users across applications, you need to
understand the available options for authentication
Module 12: Authenticating Users 2 of 21

Authentication and Access 12
Authentication:
` Determines and validates the users identity
` Is controlled inside or outside of the Siebel application
Access Control:
` Determines the resources available to an authenticated user
` Is controlled within the Siebel application by positions,
responsibilities, organizations, user ID, and access groups
Reference Siebel Authentication and Access Control Administration Guide

Business Challenge: Validating Users
How are users identified and validated?
Employees
Customers Validation
Siebel Applications
Partners

Business Solution: Authentication 12
Authentication validates users before allowing them access to

applications
Performs two tasks
` Collects credentials, such as user name and password
` Verifies credentials against a master source
Reference Siebel Authentication and Access Control Administration Guide

Siebel Authentication Manager
Runs within the Siebel object manager

Verifies credentials
Establishes connection to Siebel database

Two Types of Authentication 12
Internal authentication:
` Verifies against the relational database (RDBMS) and Siebel
application
Also known as database authentication
External authentication:
` Uses an external file (or directory) and security adapter to
authenticate users
Directory A directory is an external data store containing information required to

allow users to connect to the Siebel database.
Security Adapter A security adapter is a plug-in to the authentication manager running

within the Siebel object manager.

Internal Authentication
Browser
Requires a database (RDBMS) login
and password for each user
Web
Is the default for Siebel applications Server 1. User
provides
Authenticates users accessing one SWSE name
or more Siebel applications and
Credentials password
2. Password may be encrypted to Siebel Object Manager

prevent direct database access
Encrypt password
3. Connect to database Connect using DB account
Siebel
Database
Accessing Multiple For example, employees may need access to Siebel Sales and Siebel
Siebel Applications Field service, and these applications use the same Siebel database.

Example of Internal Authentication 12
Scenario: Joe is a new employee and requires access to

Siebel Call Center
Administration steps
1. Database Administrator (DBA) creates RDBMS login and
password
2. DBA grants user proper access rights
3. System administrator creates Siebel employee record, which
defines login, position, and responsibility
Creating Database The grantusr.sql script is provided as part of Siebel seed data. Modify this
Accounts script accordingly to create database accounts for your users.

Example of Internal Authentication Continued
User authentication steps

1. Joe enters credentials (login and password) in Siebel Call Center
login form
2. Joes login and password are verified in RDBMS
3. Joes position and responsibility are determined in the Siebel
application
4. Joe starts using Siebel Call Center
` If Joes credentials are not validated in the RDBMS and Siebel
application, he receives an error message at login

External Authentication 12
Browser
Uses an external directory containing
user credential and administrative
Web information
Server
SWSE
Allows for centralized management of
1. User user authentication across Siebel and
provides non-Siebel applications
Credentials information
2. Verify
credentials
Login Authentication
Siebel Object Security
Service
Manager adapter
Retrieve DB
account and Directory
roles
Connect using DB account
4. Connect 3. Roles applied to user

Siebel as Siebel responsibilities
to database
Database
Security Adapter The security adapter uses the user credentials provided by a user or
supplied by an authentication service to retrieve the Siebel user ID, a
database account, and optionally, a set of roles from the directory.
Authentication Service An authentication service is an external service that verifies a users

credentials. It may be the same physical device as the directory, or it may
be a separate device.

External Authentication Continued
Standard Siebel software provides prebuilt security adapters

for LDAP and ADSI
` Lightweight Directory Access Protocol (LDAP) is an open network
protocol
LDAP security adapter allows Siebel applications to access standard
LDAP directories
` Active Directory Service (ADSI)
ADSI security adapter allows Siebel applications to access Microsoft
Active Directory
Supported LDAP Refer to Siebel System Requirements and Supported Platforms for
Directories information on supported LDAP directories.

Example of External Authentication 12
Scenario: Mary is a new customer and needs access to Siebel

eService
Administration steps
1. Enable eService to communicate with external directory by
updating parameters in eservice.cfg and eapps.cfg
` Restart Siebel Server to activate changes in eservice.cfg
` Restart Siebel Server and Web Server to activate changes in
eapps.cfg
2. Update system preferences
3. Activate user registration workflows
Parameters Refer to the Siebel Authentication and Access Control Administration

Guide for details on updating specific parameters in the application
configuration and eapps.cfg files.
System Preferences Set the following values:

SecThickClientExtAuthent = TRUE
SecExternalUserAdministration = FALSE
Workflow Processes Activate the following user registration workflow processes:

User Registration Process
User Registration SubProcess
User Registration Initial Process
User Registration Forgot Password Process

Example of External Authentication Continued
User authentication steps

1. Mary self-registers by providing credentials in Siebel HTML login
form
2. Credentials are verified against external LDAP directory
3. Database account information and roles are passed back to
eService Object Manager
4. Mary starts using Siebel eService

Benefits of External Authentication 12
From a user perspective

` Allows for login maintenance and self-registration
` Allows for Web Single Sign On
Ability to log in only once and access all applications within a Web
site or portal
From an administration perspective
` Reduces overhead by not having to maintain database logins
and passwords for each and every user
` External directory can be used for other applications

Maintaining Login Information
External authentication allows Web users to maintain their login

information
` Reduces burden on system administrator to maintain user login
information
Enter user ID and

password for
authentication
Click here for

Click here to forgotten password
self-register

Web Single Sign On (Web SSO) 12
Allows users to log in once via the Web to access multiple

applications at a given site
` Siebel applications support Web Single Sign On by allowing
users to provide one set of credentials for access to multiple
applications
Authentication occurs at Web server level, not at application
level
` Credential collection and verification is external to Siebel
applications
Web SSO In this type of implementation, users are authenticated by a third party at
the Web site level. Siebel applications support Web SSO by providing an
interface that allows the third party to pass user information to a Siebel
application. Once authenticated by the third party, a user does not have to
explicitly log in to the Siebel application. Web SSO allows deployment of
Siebel applications into existing Web sites or portals.
Access to Multiple With Web SSO, users are given access to the specific applications to
Applications which they are entitled.

Web Single Sign On (Web SSO) Continued
Enable or disable on Siebel Web Server Extension (SWSE) by

modifying the eapps.cfg and application.cfg files
Specify parameters in
each eApp section or
in [defaults] to apply
to all customer Specify same
applications parameters as
in eapps.cfg
Reference Siebel Web Client Administration Guide

Siebel Authentication and Access Control Administration Guide
SingleSignon The Siebel Web Engine will operate in SSO mode when set to TRUE.
TrustToken Default is NULL. This is a shared secret between the SWSE and the
security adapter. This setting must be the same on both the web engine
(eapps.cfg) and in the application configuration file.
UserSpec This is the variable name that specifies where the Web engine looks for
the users username. The value, REMOTE_USER by default, is populated
by the authentication mechanism.
UserSpecSource Values are Server or Header (default is Server). Set to Server if the
variable is within the server environment context. Set to Header if the
variable is within the HTTP request header context.

Guidelines for Using Authentication 12
Desired Deployment Database Security Web

or Functionality Authentication Adapter SSO
Requires no additional
infrastructure 9
components
Offers centralized store
for user credentials and 9 9
roles
Limits number of
database accounts on 9 9
RDBMS
Supports dynamic user 9 9
registration
Supports Web SSO 9

Summary

` Describe the difference between authentication and Access
Control
` Describe internal and external authentication and how each
works in Siebel eBusiness applications

Lab 12

` Examine the results of internal (database) authentication
` Create a database account for a user


Understanding Object Definitions Behind a Siebel Application 13.1
13
Module 13: Understanding Object Definitions

Behind a Siebel Application

Module Objectives

` Describe the major types of object definitions
` Describe the relationships between them

` Enables you to explore an existing application effectively
` Enables you to configure Siebel applications effectively
Module 13: Understanding Object Definitions Behind a Siebel Application 2 of 22

Siebel Applications
Consist of:
` A reusable execution engine
13
` A configuration file
` A repository file containing object definitions
` A set of physical user interface (UI) files that specify how to
render the UI in the users browser
` A relational database that stores user data

Physical UI files
Consist of:
` Siebel template files
` Cascading style sheets
` Image files
Are provided by Siebel Systems as part of a standard Siebel
application
Can be modified as required by customers to satisfy corporate
look-and-feel requirements
Will be discussed in detail in a later module

Repository File
Contains object definitions that specify:

13
` Presentation of data
` Business logic
` Data storage
UI object
definitions
Account Business object

Account definitions
Data object
definitions
Reference Siebel Tools Reference

Data Object Definitions
Data object definitions:

` Specify the logical structure of the data storage
` Provide a vendor-independent representation of the underlying
physical relational database
Two principle data object definitions
` Tables
` Columns
S_PROD_INT
Table
NAME PART_NUM VERSION
Columns

Business Object Definitions
Business object definitions specify the business logic for the

application 13
Two principle business object definitions
` Business component
` Business object
Business
object
Business
component

Business Component
Represents one fundamental business entity in the enterprise

` For example: Service Request, Contact, Activity
References a base table
Consists of multiple fields that characterize the business
component
` Many fields within the business component reference columns in
the base table
Business Internal Product

component Name Part # Version Fields
Base table S_PROD_INT

NAME PART_NUM VERSION Columns

Business Component Continued
Can include data from additional related tables

` Some fields map to columns in these related tables
13
Business Internal Product

component Name Vendor Location Cost Fields
NAME LOC STD_PRI_UNIT Columns

S_PROD_INT S_ORG_EXT S_PRI_LST_ITEM
Base table Additional Additional

table table
Represents a logical grouping of data from one or more tables
Business Component A business component can be thought of as a virtual database table

spanning multiple real tables. It organizes the data in the way the user
chooses to view the data and rather than by how it is organized for
effective data storage.

Business Object
Represents a major functional area of the enterprise

` For example: account management
Is a collection of related business components
` Account business object consists of accounts plus related
opportunities, contacts, products, and so forth
Has one business component that serves as the master or
driving business component
Business Account
object (BO)
Master BC provides
Account focus for BO
Business
component Quote Product Contact
(BC)
Business Object The name of the business object is, by convention, the name of the master
or driving business component.

Business Component Reuse
A business component can be:

` Defined once in terms of a logical collection of columns from one
13
or more tables
` Then used in many different business object contexts
Account Contact BC appears as

master in Contact BO
Account
Contact
Contact
Quote Product Contact
Contact BC appears as Quote Product Account

child in Account BO

UI Object Definitions
UI object definitions specify the content of the user interface

with which the user interacts
Three principle UI object definitions
` Screen
` View
` Applet
Screen
View
Applet
UI Object Definitions As mentioned earlier, the physical layout of the UI is determined by

template and other files in the physical UI layer. There are additional
object definitions (such as Web Page and Web Template) in the repository
that reference the template files. In addition there are object definitions that
relate views and applets to the template files. These object definitions also
are par t of the UI object definitions. They will be discussed in a later
module.

Applet Object Definition
Specifies a list or form that occupies a portion of a Siebel

application window 13
References one business component whose data can be viewed
and edited through the list or form
Business Contact
component First Name Job Title Email Address

Applet Object Definition Continued
Consists of multiple list column or textbox control object

definitions
` Reference a field in the applet-referenced business component
` Specify how the data for the field is displayed in the list or form
Business Contact
component First Name Job Title Email Address

View Object Definition
Specifies a view in a Siebel application

References one business object 13
Consists of multiple applet object definitions
` Each applet must reference a business component in that
business object
Account
Account
Quote Product Contact

Screen Object Definition
Specifies a screen in a Siebel application

` Is associated with a major functional area of the enterprise
Consists of multiple view object definitions that usually
reference the same business object
` Administration screens are an exception
Screen
Screen

Application Object Definition
Specifies a particular collection of screens available in a Siebel

application 13
Consists of multiple screen object definitions
Application

Major Object Definitions
Are related to each other
List Column
Applet View Screen Application
or Control
Business Business
Field
Component Object
1 or more
contained in
Column Table
References

Object Definitions
Are grouped into three layers with different subject matters and
purposes 13
Reference definitions in the next lower layer and are insulated
from those in lower layers
List Column
Applet View Screen Application
or Control
UI Layer; defines
content of the UI
Business Business
Field Business objects layer;
Component Object
captures the business logic
Data objects layer; provides a logical

Column Table view of the underlying database

Siebel Applications
Are configured to meet customer requirements by using:

` An HTML editor to modify the template and other physical UI files
` Siebel Tools to modify the object definitions
Configurable layers
Physical UI files Modified using HTML editor
UI Object Definitions
Business Object Definitions Modified using Siebel Tools
Data Object Definitions

Summary

` Describe the major types of object definitions
13
` Describe the relationships between them

Lab

` Examine object definitions that support the Call Center
application and the relationships between them

Using Siebel Tools to Examine Object Definitions 14.1
14
Module 14: Using Siebel Tools to Examine Object
Definitions

Module Objectives

` Describe the differences between object types and object
definitions
` Use Siebel Tools to examine parent and child object definitions
` Search for object definitions with a given property value

` Enables you to configure Siebel applications effectively
` Enables you to examine mappings that support bulk data transfer
Module 14: Using Siebel Tools to Examine Object Definitions 2 of 19

Object Definitions
Are data constructs that define elements of the:

` User interface
` Business logic
` Data storage
14
Are stored in the Siebel repository, a subset of tables in the
Siebel database that contains object definitions
Are examined, created, and edited using Siebel Tools
Are compiled into the repository file for a configured application
Database Application
Repository Tools
Object Manager
Data Application
Tools output is input

.srf Configured
for object manager
Application

Object Definition
Consists of a set of properties with assigned values

Is created from a template called an object type
Object type Object definition

View View
Name: Name: Account List View
Title: Title: My Accounts
Inactive: Inactive: FALSE
Object Terminology The terms object type and object definition, as used here, should not be
confused with similar terms (object, object class, object instance) found in
object-oriented design and programming languages.

Object Definition Properties
Describe characteristics of the object definition

Have the following value types
` User-defined names
` Numerical values 14
` Boolean values (TRUE and FALSE)
` Siebel-defined constants
` References to the names of other object definitions
Object definition
Field
Name: Account Products
Text Length: 500
Read Only : FALSE
Type: DTYPE_TEXT
Column: PROD
Referencing Names A property that references the name of another object definition must
match the name exactly in spelling (spaces do count) and case. A value of
Prod is not the same as PROD.

Examining Object Definitions
Use the Siebel Tools object list editor to display object

definitions
` Select an object type in the Object Explorer
` Object definitions appear in the Object List Editor
Property Object
definition
Object Object List

Explorer Editor

Siebel Tools User Interface
Differs from the Web client

` All data in a list applet can be selected for editing
` Changes made to an object definition are automatically saved
when leaving the record
` Right-clicking to invoke context-sensitive menu is supported
14
` Tool bar icons exist for common user operations
Record Navigation Query Sort Menu invoked by
right-clicking on
object definition

Object Explorer
Displays by default a small set of the most commonly used

object types
` Use ViewOptions and select the Object Explorer tab to add or
remove object types from the Object Explorer

Properties Window
Displays the object definition selected in the Object List Editor

` Open by selecting ViewWindowsProperties Window
` Properties are listed in alphabetical order
` The value is shown next to property name
14
Properties
Window
Does not show Changed

or Project properties

Hierarchy of Object Types
Some object types contain child object types

` For instance Business Component has Field child object type
Object
Explorer
displays
hierarchy
Multiple
levels of
hierarchy

Viewing Parent/Child Object Definitions
Select object types and definitions alternately to examine child

object definitions
1. Expand parent object 2. Select parent object
type (Applet) in OE definition in OBLE
Use Types tab
14
3. Select desired child object 4. View child object definitions for selected
type (Control) in OE parent definition in lower pane of OBLE

Additional Navigation Techniques
Use these techniques to navigate in the Tools application

` Drill down on hyperlinks
` Forward/Back button
` Bookmarks

Using Drilldown
Drill down on a hyperlink to navigate to that object definition

` Applet to business component
` Business component to table
Underlined
14
in blue

Using the Forward/Back Button
Use the back button to return to object definition last examined

Use the forward button to return to the current object definition
Forward and back

Using Bookmarks
Use bookmarks to navigate directly to a specific object

definition
Add a new Display or hide
bookmark bookmark window
14
Select the desired

bookmark from the
Bookmarks window
Bookmarks Bookmarks can serve very effectively as predefined queries.

Object Explorer: Flat Tab
Removes all hierarchy and shows all object types in a single

list
Helps developers:
` Find a child object with an unknown parent
` See how object definitions and properties are typically used
Select any
object type Parent object definition
in OE displayed

Repository Search
Use Search Repository to find multiple object types at once

` Locate definitions regardless of object type or position in
hierarchy
14
Select one
or more
Double-click
to navigate to
definition

Summary

` Describe the differences between object types and object
definitions
` Use Siebel Tools to examine parent and child object definitions
` Search for object definitions with a given property value

Lab

` Use Siebel Tools to examine object definitions in the Siebel
repository
` Use Siebel Tools to examine references between UI, business,
and data object definitions 14
Note the convention used in the labs
Parent record Child record

in the OBLE in the OBLE
Select Business Component > Account > Field > Account Role
Parent object type Child object type

in the OE in the OE


Understanding the Siebel Data Model 15.1
Module 15: Understanding the Siebel Data Model

15

Module Objectives

` Describe the purpose of the Siebel Data Model
` Describe the role of primary and foreign keys, indexes, and user
keys
` Identify prominent tables in the Siebel Data Model
` Locate foreign keys for different relationships

` Enables you to understand how data is accessed in existing
Siebel applications
` Enables you to map your business logic to the Siebel Data Model
` Enables you to configure the data layer as necessary for your
implementation
` Provides information that will be important in addressing
performance issues
Module 15: Understanding the Siebel Data Model 2 of 29

The Siebel Data Model
Defines how the data used by Siebel applications is stored in a

standard third-party relational data base
` Specifies the tables and indexes
Is designed to support the data requirements across Siebel
eBusiness applications
Business Business
Defines the business logic Field
Component Object 15
Defines how data storage

is organized (makes up Column Table
the Data Model)
Data Model for Vertical The Siebel Data Model has been extended for some industry applications
Applications to incorporate additional tables and columns specific to the industry
application.

Understanding the Data Model
In order to develop and install a Siebel application, you need to

understand:
` What data is stored in the Siebel database
` The pieces that make up the Siebel database
` The rules and policies for using those pieces
` The consequences of those rules and policies
The pieces to understand
` Tables
` Columns
` Indexes
` User Keys
` Primary and foreign keys

Siebel Data
Is stored in normalized tables in a relational database

` Each table has multiple columns storing single value data
` Data schema is organized to eliminate repeated storage of data
Table S_PROD_INT
15
ROW_ID
NAME
PART_NUM
UOM_CD
Columns (store
single values only)

Primary Key
Is a column that uniquely identifies each row in a table

` ROW_ID serves as the primary key for Siebel database tables
S_PROD_INT
NAME
PART_NUM
ROW_ID
UOM_CD
Primary Key
(PK)

ROW_ID
Is a column in every table

` Contains a Siebel-application-generated identifier that is unique
across all tables and mobile users
Is the means by which Siebel applications maintain referential
integrity
` Database referential integrity constraints not used
Is managed by Siebel applications and must not be modified by
users
15

Tables
Over 2000 tables in the database

Three major types: Data, Interface, and Repository
Data Interface Repository
S_PROD_INT EIM_PROD_INT S_TABLE
DESC_TEXT
ALIAS
ROW_ID
NAME
PART_NUM
UOM_CD
ROW_ID
NAME
TYPE
NAME
PART_NUM
ROW_ID
UOM_CD
Creating the Schema The database schema is created by the install.ksh script during the Siebel
database server installation. Additional tables can be created by
developers using Siebel Tools.
Type The type of a table is specified by its Type property.

Data Tables
Store the user data

` Business data
` Administrative data
` Seed data
` Transaction data for mobile users
Are populated and updated:
` By the users through the Siebel eBusiness applications
` By server processes such as
15
Enterprise Integration Manager for bulk importing and exporting of
data
Assignment Manager for automatic assignment of newly created
records
Have names prefixed with S_
Are documented in the Siebel Data Model Reference

Prominent Data Tables
Prominent tables storing data for the major business entities

Internal Service
Product S_SRV_REQ Request
S_PROD_INT
OWNER_EMP_ID
ROW_ID
SR_NUM
DESC_TEXT
RESOLUTION_CD
NAME
PART_NUM
ROW_ID
UOM_CD
Contact Opportunity
S_CONTACT S_OPTY
ROW_ID
BDGT_AMT
NAME
PROG_NAME
STG_NAME
MID_NAME
ROW_ID
LAST_NAME
FST_NAME

Interface Tables
Are a staging area for importing and exporting data

Are used only by the Enterprise Integration Manager server
component
Are named with prefix EIM_
Are documented in the Interface Tables Reference
15
Naming Convention for Interface tables for the current release are prefixed with EIM_. Interface
Interface Tables tables for the 6.x releases are prefixed with IF6_ to distinguish them from
the current tables. Interface tables for earlier releases have a _IF suffix.
Reference Siebel Interface Tables Reference

Repository Tables
Contain the object definitions that specify one or more Siebel

applications
` Client application configuration
UI, business, and object definitions
` Mappings used for importing and exporting data
` Rules for transferring data to mobile clients
Are updated using Siebel Tools
Populating the The repository tables are populated by the imprep.ksh script during the
Repository Tables database server installation.

Columns
Each table has multiple columns to store user and system data
` Defined by the Column child object definitions
Columns determine the data that can be stored in that table
15

Column Properties
Important properties of columns

` Properties of existing tables and columns should not be edited
Understanding these properties is important
` Determines the size and type of data that can be stored in a
column
` Limits proposed modifications to a standard application
Value assigned to Can NULL be Non-null value required Identifies type

all new records stored in column? when importing data and size of data

System Columns
Exist for all tables to store system data

Are maintained by Siebel applications and tasks
15
Can be viewed from HelpAbout Record

User Key
Specifies columns that must contain a unique set of values

Prevents users from entering duplicate records
Is used to determine the uniqueness of records during data
import operations
Cannot be edited
Not all columns in a user

key may be required
User Keys Customers cannot modify user keys. The information about the user keys
for a table has been incorporated into data that support EIM and remote
synchronization. In addition there is a predefined index (see next slide)
based on the Siebel-defined user key.

Index
Is a separate data structure that stores a data value for a

column and a pointer to the corresponding row
` Are used to retrieve and sort data rapidly
Can be created by configurators (to produce a custom index)
Should be inspected to assess performance issues for query
and sort operations
_P: index based on primary key

15
_U: index based on a user key
Sequence affects
the sort order in
business
components

Relationships Between Tables
Siebel database tables are related to one another

Understanding the relationships between tables is important to
implementing your business logic
Product Line Asset

S_PROD_LN S_PROD_INT S_ASSET
ROW_ID
ROW_ID
NAME
DESC_TEXT
ASSET_NUM
MFGD_DT
SERIAL_NUM
UOM_CD
ROW_ID
NAME
PART_NUM
M:M relationship 1:M relationship

Foreign Key Table Columns
Are columns in a table that refer to the primary key column of a

related (parent) table
` Are named with suffix _ID
Capture relationships between Siebel database tables
Are maintained by Siebel applications and tasks to ensure
referential integrity and should never be updated directly using
SQL
15

1:M Relationships
Are captured using foreign key table columns in the table on

the many side of the relationship
Foreign key column for

the 1:M Product Asset
relationship
S_PROD_INT S_ASSET
ROW_ID
ASSET_NUM
MFGD_DT
MID_NAME
PROD_ID
ROW_ID
NAME
PART_NUM
UOM_CD
Foreign Key Columns Since an product could have many assets (product instances) associated
with it, a foreign key column cannot be located in the S_PROD_INT table.
It might then have to contain multiple ROW_IDs which would violate the
basic rule of a single value for a column.

Finding Foreign Keys for 1:M Relationships
Inspect the Foreign Key Table property in a Column object

definition to determine the column that serves as the foreign
key
15
Foreign key column for

the 1:M Asset Product
relationship

M:M Relationships
Are captured using foreign key table columns in a third table

called the intersection table
Intersection table for M:M

Product Product Line
relationship
S_PROD_LN S_PROD_INT
ROW_ID
NAME
PART_NUM
UOM_CD
NAME
DESC_TEXT
ROW_ID
S_PROD_LN_PROD
PROD_ID
ROW_ID
PROD_LN_ID
Intersection Tables An intersection table must be used for a M:M relationship since a foreign
key column cannot be located in either of the base tables. Siebel Systems
refers to this type of table as an intersection table. In other parts of the
database world this type of table is also known as an association or
correlation table.

Finding the Intersection Table
Certain configuration and administration activities may require

determining the intersection table that supports a M:M
relationship
To locate an intersection table execute the following query in
Siebel Tools
Parent tables
15
Intersection
table
Query Use the following steps to execute the query:

1. Select the Flat tab in the Object Explorer and then select the
Column object type.
2. Rearrange the columns in the OBLE to display Parent Table,
Name, Foreign Key Table, and User Key Sequence at the
beginning of the applet.
3. Execute a query for which [User Key Sequence] = 1 or 2 and
[Foreign Key Table] = S_CONTACT or S_EVT_ACT.
4. Sort the results by Parent Table.
5. Look for a Parent Table that appears in two adjacent rows where
the Foreign Key Table is S_CONTACT in one row and
S_EVT_ACT in the other row.

1:1 Extension Table
Is a special table that has a 1:1 relationship with a base table

` Foreign key for the relationship:
Is located in the extension table
Is named PAR_ROW_ID
Provides additional columns for business components
referencing the base table
` A base and extension table can be considered as a single logical
table
Base table S_PROD_INT S_PROD_INT_X Extension table
ROW_ID
NAME
PART_NUM
UOM_CD
ROW_ID
PAR_ROW_ID
ATTRIB_39
Stores the Stock
Level field
ROW_ID The ROW_ID for a row in a 1:1 extension table is, by convention, the
same as that of the related row in the base table, and is an exception to
the general rule that ROW_IDs are unique across all tables. There is no
guarantee this convention will continue in future releases.
Rows in Extension A row in an extension table is created only if there is data to store in one of
Tables its columns. For example, a new product record that does not have a value
for the Stock Level field would create a row in the base table but not in the
extension table.

1:1 Extension Table Continued
Are used:
` To provide flexibility for both Siebel engineering and customer
use
Known as standard 1:1 extension tables
` To support multiple business components referencing the
S_PARTY table (discussed in next module)
15

Standard 1:1 Extension Tables
Prebuilt for many major tables

` Have the name of the base table with suffix _X
Contain 40 plus generic columns of varying types
` Store additional fields for business components beyond those
mapped to the base table

Generate a Table Report
To produce a report that summarizes the important details

about a table for reference
` In Tools, run a query to select the tables of interest
Report will include all tables displayed in the Object List Editor
` Select ReportTables to generate a detail report on the columns
and indexes
Make sure that Table is selected in the Object Explorer
15

Summary

` Describe the purpose of the Siebel Data Model
` Describe the role of primary and foreign keys, indexes, and user
keys
` Identify prominent tables in the Siebel Data Model
` Locate foreign keys for different relationships

Lab

` Examine tables, columns, indexes, and user keys that make up
the Siebel Data Model
` Determine the form of relationships between tables in the Siebel
Data Model
15


The Siebel Data Model: Party Business Components 16.1
Module 16: The Siebel Data Model: Party Business

Components
16

Module Objectives

` Identify tables used for storing data about persons
` Identify tables used for storing data about organizations
` Describe the role of S_PARTY and its extension tables

` Enables you to configure business components related to access
control
` Enables you to import Access Control data properly and populate
the desired tables
Module 16: The Siebel Data Model: Party Business Components 2 of 22

Party
Refers to instances of entities that have access to records

` Person-related entities
` Organization-related entities
` Groupings created for access to master data
Allows for grouping of instances of different types of entities
Contact Account
Employee Position
Access Group
User Division 16
User List
Partner Organization
Person-related Grouping for Organization-

entities access control related entities

Topics For This Module
How person-related data is stored

How organization-related data is stored
How party business components use the S_PARTY table

Person
Represents anyone associated with a Siebel application

May be someone:
` Using the application
Employee at a company that deployed a Siebel application
Individual at a channel partner
Customer logging in to the Web site
` Referred to in the application
Individual external to your company associated with the business
process
16

Person-Related Business Components
Store their main data in S_CONTACT

May store additional data in S_USER and S_EMP_PER
` Serve as logical extension tables
S_CONTACT S_USER S_EMP_PER

ROW_ID
FST_NAME
HIRE_DT
LAST_NAME
MID_NAME
ROW_ID
LOGIN
PASSWORD
ROW_ID
EXP_APPR_LMT
Stores majority of Logical extension table to Logical extension table to
person-related data store user specific data store employee-specific data
Persons In Siebel 7 applications, the types of person entities have been arranged
hierarchically. A Person is anyone with a record in the S_CONTACT table.
A Contact is a Person with a Contact Team. A User is a Contact that can
log in (that is, has a User ID), and an Employee is a User that has the
EMP_PER flag set in the S_EMP_PER table.

Person-Related Business Components Continued
Multiple business components use these tables
Consumer
Last Name Work Phone #
Employee
Last Name Login Name Hire Date

ROW_ID
FST_NAME
WORK_PH_NUM
HIRE_DT
LAST_NAME
MID_NAME
ROW_ID
LOGIN
PASSWORD
ROW_ID
EXP_APPR_LMT
16

Relationships for Responsibility
User-Responsibility (M:M) relationship uses the S_PER_RESP

intersection table
` Any user can be granted a responsibility
S_CONTACT S_RESP
LAST_NAME
MID_NAME
ROW_ID
FST_NAME
ROW_ID
NAME
DESC_TEXT
BU_ID
S_PER_RESP
PER_ID
ROW_ID
RESP_ID
Stores responsibilities

Organization-Related Data
Represents any business enterprise associated with a Siebel

application
` The company or part of the company deploying the Siebel
application (division, organization)
` An external company that purchases your products (account)
` A partner company that assists you in your business (channel
partner)
16

Organization-Related Business Components
Store their main data in S_ORG_EXT

May store additional data in S_BU
S_ORG_EXT S_BU
ROW_ID
LOC
PRTNR_FLG
NAME
INT_ORG_FLG
ROW_ID
NAME
BU_FLG
=Y for Internal Division or Logical extension table to
Organization store organization name
=Y for Channel Partner

Organization-Related Business Components Continued
Multiple business components use these tables
Account
Name Location
Organization
Name Internal Org Flag Organization BU Name
S_ORG_EXT S_BU
ROW_ID
LOC
ROW_ID
BU_FLG
NAME
INT_ORG_FLG
NAME
16

S_BU Table
Permits indexing on Organization name

Supports organizational visibility
S_ORG_EXT S_BU
ROW_ID
BU_FLG
ROW_ID
NAME
LOC
INT_ORG_FLG
NAME
Part of S_BU_U1 index
S_BU Table While there are only a few additional columns in the S_BU table, storing
Organization information in this separate table allows organizations to be
identified solely by their name. Other entities such as Accounts are
identified by their name and location.

Single-Organization Visibility
Is implemented by the BU_ID foreign key column in the table

for a single-organization business component
Example of a single-
organization table
S_CONTACT S_BU
LAST_NAME
MID_NAME
ROW_ID
FST_NAME
BU_ID
ROW_ID
BU_FLG
NAME
16
Single-Organization Remember these business components have records that can be

Business Components assigned to one and only one organization. Some examples are contacts,
service requests, and positions.

Multi-Organization Visibility
Is implemented by an intersection table between S_BU and the

table for the multiple-organization business component
` Intersection tables for organization have a _BU suffix
Price List
S_PRI_LST Example of a multiple- S_BU

organization table
ROW_ID
PRI_LST_CD
BU_ID
NAME
EFF_START_DT
ROW_ID
BU_FLG
NAME
S_PRI_LST_BU
ROW_ID
PRI_LST_ID
BU_ID
Multi-Org Business Such business components have records that can be assigned to one or
Components more organizations. Some examples are accounts, opportunities, and
products.

Party Business Components
Consist of business components that represent people and

organizational units
` Account
` Contact
` User
` Organization
` Employee
` Position
` Household
` And so forth
16
Reference the S_PARTY table
Party A way to think of party is that it is an abstraction of the business

components that own records.

S_PARTY Table
Serves as the base table for all party business components

` Stores the party name and party type
Has multiple extension tables that store the business data for
the party business components
User
Party Name Last Name Login Name
S_PARTY S_CONTACT
S_ORG_EXT
ROW_ID
FST_NAME
PAR_ROW_ID
LAST_NAME
MID_NAME
ROW_ID
NAME
PARTY_TYPE_CD
PARTY_UID
ROW_ID
NAME
LOC
INT_ORG_FLG
PAR_ROW_ID
PARTY_TYPE_CD The following are examples of the party type: organization,

household,person,position, user list, and access group.

Party
Includes business components that represent groupings of

party instances
` User List: grouping of Users
` Access Group: grouping of Access Group Members
Can contain only non-person party entities such as organizations,
divisions, and positions
User List
Party Name Party Type Code
S_PARTY
16
ROW_ID
NAME
PARTY_TYPE_CD
PARTY_UID
User List A User List allows for ad-hoc groupings or persons of all types
(employees, contacts, and so forth).
Access Group An Access Group allows for ad-hoc groupings of non-person groups.

S_PARTY_PER
Is an intersection table that relates two instances of parties

Used to implement relationships between
` User Lists and Users
` Employees and Positions
` Access Groups and Members
S_PARTY_PER
ROW_ID
PERSON_ID
PARTY_ID
S_PARTY
ROW_ID
NAME
PARTY_TYPE_CD
Module 16: The Siebel Data Model: Party Business Components
PARTY_UID 18 of 22

S_PARTY Overview
S_PARTY and its extension tables are used to store data for
many business components
Person-related tables
S_PARTY PARTY_UID
NAME
ROW_ID
PARTY_TYPE_CD
S_ORG_EXT S_BU
S_POSTN Organization-related tables
16
Sample of S_PARTY extension tables

Relevance in Subsequent Activities
Configuring business components

` All person-related business components use S_CONTACT
` All organization-related business components use S_ORG_EXT
` Over 100 party-related business components reference S_PARTY
but store their data in one of many S_PARTY extension tables
Importing data for party-related business components
` Must populate columns in S_PARTY table in addition to tables that
store the data of interest to users
Importing data for business components related to organizations
` For single-organization data, must populate BU_ID
` For multi-organization data, must populate the corresponding
intersection table

Summary

` Identify tables used for storing data about persons
` Identify tables used for storing data about organizations
` Describe the role of S_PARTY and its extension tables
16

Lab

` Examine how Access Control business components store data in
the person and organization tables
` Examine how business components reference the S_PARTY
table

The Configuration Process 17.1
Module 17: The Configuration Process
17

Module Objectives

` Explain the process of configuring a Siebel application
` List the critical elements of the Siebel configuration strategy
` Set up the Siebel developer environment

` Understanding the configuration process is critical to carrying out
a successful configuration
` Following a reasonable configuration strategy can expedite your
configuration efforts and make your configured application robust
and upgradeable
Module 17: The Configuration Process 2 of 25

Siebel Applications
Siebel standard applications include a defined set of screens,

views, lists and forms, and their associated templates
17

Tailoring the Logical User Interface
Developers tailor the standard Siebel screens, views, lists,

forms, and templates to better support users business needs

Tailoring the Physical User Interface
Use the existing physical UI files whenever possible

When necessary, copy existing files and modify as needed
` Modify Siebel template files to change layout
Use an HTML or text editor
` Modify cascading style sheets to change colors, fonts, and so on
Use a text editor
` Modify, add, or replace image files to make your organizations
images available to the application
Create or modify these files using an appropriate graphics program
17

Siebel Business Entities
Siebel standard applications utilize a set of Siebel business

components that implement a defined business logic
Account
Service Request Contact Action
Product

Tailoring the Business Logic
Developers also tailor the application by modifying the

definitions of the business components to implement the
business logic appropriate to the users organization
Account Add fields

Modify form of
the relationship
Service Request Contact Action
Modify properties
of existing fields
Product
17

Extending the Data Layer
Siebel standard applications contain a defined set of database

tables
Developers can tailor the application by extending the set of
database tables in a limited and controlled manner
S_CONTACT2_X
S_CONTACT1_X
ROW_ID
LAST_NAME
FST_NAME
MID_NAME
S_CONTACT S_CONTACT_X
ROW_ID
LAST_NAME
FST_NAME
MID_NAME
LAST_NAME
MID_NAME
ROW_ID
FST_NAME
ROW_ID

Configuring a Siebel Application
Configuring is the process of modifying a standard Siebel

application using Siebel Tools to meet business needs
Object definitions are edited and created
` Developers do not modify code in siebel.exe
` Developers do not write SQL directly
Database Application
Repository
Tools
Object Manager
Data Application
Tools output is input

.srf Configured
for object manager
Application
17

Configuration Strategy
Make minimal changes to the standard application

` Decreases the possibility of unexpected interactions
Use existing object definitions in the standard repository
whenever possible
` Ensures that a new configuration can be upgraded with minimal
effort
` Modify definitions as required rather than creating new ones
Creating new object definitions can lead to redundant configuration
` Do not delete seemingly-unused object definitions
Other object definitions might reference them
` Use existing template files
Modify where necessary
Modifying a template for one view or applet can have unexpected
consequences if another view or applet uses the same template

Configuration Strategy Continued
Plan your configuration project from the top down

` First, determine what the UI and application will do when you
have finished
` Then, determine what changes to the business objects layer this
will require
` Finally, determine what changes you must make to the data layer
Make as few as possible
Make the changes from the bottom up
` First, edit the data layer definitions (if necessary)
` Then, edit the business object layer definitions as required
` Finally, edit or create the templates and UI layer definitions to
display the data correctly
17

Create a Separate Development Environment
To isolate the development effort from the enterprises

production database, set up a development environment
Each developer or group can work on a different aspect of the
development effort
` Use Siebel-supplied mechanisms to separate the development
effort into projects
Test all customization and extensions thoroughly in this
environment before deploying to end users
Developer Developer Developer

Server Machine
Workstation Workstation Workstation

Develop on the Local Repository
Always make changes to the object definitions in the local

repository
` Cannot undo or back out changes when made directly on the
server
` Changes made directly on the server are immediately available to
other developers
Incomplete changes on the server will cause problems
Use Siebel-supplied mechanisms to copy definitions between
server and local databases
Developer
Server Master Workstation Local
Machine Repository Repository
17

Set Up a Developer
To set up a developer as a Special type of Siebel client

configurator: Tools
Client
` Install appropriate server and Gateway Server
client software (as in Module
6)
` Install and verify the Tools
Enterprise Server
client
` Create the developer Siebel Server
` Create a database user login Component

` Generate the local database
template
` Extract the local database
` Initialize the local database
ODBC Database
` Populate the local database
Server

Install Tools Client
Use the seatools installation program to install the Tools

program and set up ODBC data sources
Example:
Tools
Client
Destination Directory: C:\sea701\tools
Siebel Remote Server: SERVER01

D1
File System: HQ\SVR2\c:\siebfile
Database Machine Name: SERVER02 SSD Local Db c:sea701/tools

SSD c:/sea701/tools
Database/Tablespace: siebeldb
ODBC User Data sources
17
SERVER01 The name of the server on which you installed the Siebel Server.
File System Should be the directory that was created and shared in the pre-installation
tasks.
SERVER02 The name of the server on which the database software is installed.
siebeldb The default name of the database created in the pre-installation steps, that
will contain the Siebel tables.

Verify Tools Client
Inspect directory and SSDsetup.log file (in the Tools directory)

Verify application launch and database connection
` Example:
ODBC data source for

the server database

Create the Developer
Add the developer as an employee and associate a position

and responsibility
Register the developer as a mobile client
17
Reference Siebel Remote and Replication Manager Administration Guide

Create a Database User Login
Create a corresponding database login using RDBMS tools

and the grantusr.sql script as a template
Example:
Reference Applications Administration Guide

Generate the Local Database Template
Run the Generate New Database server task to generate a

local database template
` Snapshot of the current database schema version
17

Extract the Local Database
Run the Database Extract server task to extract user data

Initialize the Local Database
Synchronize from the Tools client to create the local database

(sse_data.dbf) and populate it with user data
17

Populate the Local Database
Use Siebel Tools to copy repository data from the server

database to the local database
Database
Repository Tools
Data Client
Local
Server Database
Database
Reference Applications Administration Guide

Additional Developers
For each additional developer

1. Create the developer
2. Create a database user login
3. Extract the local database
4. Initialize the local database
5. Populate the local database
Developer Developer Developer

Server Machine
Master Local Local Local

17

Summary

` Explain the process of configuring a Siebel application
` List the critical elements of the Siebel configuration strategy
` Set up the Siebel developer environment

Lab

` Set up an employee as a developer
` Extract a local database for the developer
` Populate the developers local database with repository data
17


Managing Object Definitions 18.1
Module 18: Managing Object Definitions
18

Module Objectives

` Explain the role of projects
` Manage object definitions using:
Check Out
Check In
Lock projects locally

` Checking projects in and out is a critical part of your configuration
effort
` Allows multiple developers to work together on a configuration
effort
Module 18: Managing Object Definitions 2 of 21

Projects
Are named sets of object definitions in a repository

` Only one version of a project exists in a repository at a time
Are a mechanism to organize object definitions so that a single
developer can exclusively work on them as a group
Repository Client
Admin Client
Contact User List Applet Parent Node
Contact User Creation View Node List Applet
Product
Component Product Internal Product
Equivalent Product Internal Product Attachment

18

Projects Continued
A standard Siebel application is delivered with a large number

of existing projects
New projects can be created by
` Selecting the Project object type and
` Creating a new record in the Object List Editor

Assigning Object Definitions to Projects
Every object definition must belong to one, and only one,

project:
` A Siebel-supplied project
` A user-created project
A top-level object definition has a Project property
` Child object definitions belong to the parent project
Child object definitions

have no Project
property

18

Viewing Object Definitions by Project
View object definitions in a project using the Project drop-down

list
` Displays the object types for which there are object definitions in
the selected project
` Select **All Projects** at the top of the list to see all projects
Project drop-down

Repositories
Master copy of repository resides on server database

` Stores tested object definitions for complete developer team
Each developer has copy of the repository on local developer
(client) workstation
` Developers perform all editing on their local repository
Server Machine Developer Developer Developer

Master Local

18

Copying Projects
Object definitions in one or more projects can be copied

` From the server to the local developer repository (Get, Check
Out)
` From the local developer repository to the server (Check In)
Overwrites the version in the destination repository
Project
Get, Check Out
Server Local
Check In

Getting Projects
Use Get to populate a newly-initialized local database with a

copy of all projects in the server repository
Use Get to refresh a read-only project in a local repository
` Need object definitions modified by other developers to update
your local copy

18

Check Out
Use Check Out to modify object definitions in a project

Check Out:
` Copies all object definitions in project on server to local database
Local copy of project is overwritten by server version
` Locks project on server repository
Prevents other developers from modifying that project
` Locks the project in the local repository
Permits developer to make changes to object definitions in that
project

Check Out Continued
Use Check Out to copy projects from the server to the local
repository

18

Check In
Use Check In when object definitions in project have been

edited and tested
Check In:
` Copies object definitions from local repository to server repository
` Replaces versions of checked out object definitions with new
versions and unlocks projects
Can also check in object definitions in newly-created projects
` Releases locks on both server and local copies of project
Maintain Lock leaves project locked for further local modification by
current developer

Check In Continued
Use Check In to copy projects from the local to the server

repository

18

Project Differences
Use Project Differences to view details of changes made to

checked-out projects prior to checking them in
` Detect mistakes or omissions before changes are committed to
server repository
Invoke using Diff button in Check In window

Canceling Check Out
Discards changes made to checked-out project if:

` Changes are no longer required
` Local project has become corrupted
To cancel check out of a project
` Check out project from server again
Replaces modified object definitions in local repository with original
version from server repository
Repeating check out is permitted for person who last checked out
project
` Then check in project to unlock project on both local and server
repositories

18

Undo Check Out
Use Undo Check Out to release lock on a project on the server

without checking in edited object definitions
` Makes original project available to another developer
` Can be followed by Get project to restore original object
definitions in local database
Alternate way to cancel check out
Undo Check Out:
` Releases lock on server
` Retains lock on local database
Developer can continue to modify object definitions but will not be
able to check them in to server

Locking Projects
You can directly lock and unlock projects

in the current repository (local or server)
Use Tools Lock

Project
Set Locked
property directly

18
Project Drop-Down You can select the **My Locked Projects** entry in the Project drop-down
to display only those projects you have locked (either by checking them
out or locking them directly).

Locking Projects Locally
Consider when:
` Prototyping your ideas without preventing other developers from
checking out the project
` Intending to discard (rather than save) your work
Allows developer to make and test modifications locally
Prevents developer from checking them in to server repository

Master Local

Locking Projects on the Server
Prevents developer from undoing the changes and restoring

the original definitions
Allows other developers to get object definitions in an
incomplete, inconsistent, and untested state
Siebel Systems recommends that developers never directly
lock projects on the server
Always use Check Out and modify the object definitions locally

Master Local
18

Summary

` Explain the role of projects
` Manage object definitions using:
Check Out
Check In
Lock projects locally

Lab

` Explore how projects work in Siebel Tools
` Check out a project from the server

18


Siebel 7 Essentials Student Guide Vol1 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Siebel 7 Essentials Student Guide Vol1 PDF

Uploaded by

Copyright:

Available Formats

Siebel Systems, Inc.

Version 7.0 November 2001

Dear Siebel Education Student:

1. disclose such information or materials except as specified in the Agreement, nor

Copyright 2001 Siebel Systems, Inc. Siebel Systems, Inc.

Course Subjects: Web-based courses cover the following training subjects:

For more information about Siebel Technical Education classes: http://siebeluniversity.siebel.com

Uniquely Qualified to Train Siebel End Users

Flexible Education Solutions

For more information about Siebel End User Education: http://siebeluniversity.siebel.com

Architecture and Installation

Access Control and Organization Setup

Exploring Siebel Applications

Siebel Systems, Inc. i

ii Siebel Systems, Inc.

Business Process Automation

Siebel Systems, Inc. iii

iv Siebel Systems, Inc.

Siebel Technical Training i

Module i: Siebel 7 Essentials Training 1 of 17

Siebel 7 Essentials Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Module i: Siebel 7 Essentials Training

Siebel 7 Essentials Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

This module provides an introduction to the:

Module i: Siebel 7 Essentials Training 3 of 17

Siebel 7 Essentials Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Introductions and Expectations

Who are you?

Module i: Siebel 7 Essentials Training 4 of 17

Siebel 7 Essentials Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Training Site Information i

Bathrooms Class duration and breaks

Telephones Meals and refreshments

Fire Exits Questions?

Module i: Siebel 7 Essentials Training 5 of 17

Siebel 7 Essentials Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Module i: Siebel 7 Essentials Training 6 of 17

Siebel 7 Essentials Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

In this course, you will learn how to:

Module i: Siebel 7 Essentials Training 7 of 17

Siebel 7 Essentials Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

This course is designed for:

Module i: Siebel 7 Essentials Training 8 of 17

Siebel 7 Essentials Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Subject matter will be delivered via:

Module i: Siebel 7 Essentials Training 9 of 17

Siebel 7 Essentials Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Overview of Course Flow

Module i: Siebel 7 Essentials Training 10 of 17

Siebel 7 Essentials Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Architecture and Installation

Module i: Siebel 7 Essentials Training 11 of 17

Siebel 7 Essentials Siebel Systems, Inc.