Siebel 7 Essentials Student Guide Vol1-1

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.
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 Siebel 7 Core Consultant Course Siebel 7 Requirements Mapping Siebel eBusiness Application Integration 7 Configuring Siebel Marketing 7 Siebel Interactive Selling Suite 7: ServerBased Implementation Siebel Interactive Selling Suite 7: BrowserBased Implementation Installing and Extending Siebel Analytics 7 Creating Siebel 7 Reports Siebel 7 Migration Training Workshop Siebel eRoadmap Workshop Getting Started Workshop Siebel Employee Relationship Management 7 Workshop Key Success Factors for Siebel Implementations 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 Webbased 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 eBusiness Applications Siebel software migration Siebel Industry applications Technical topics Siebel Horizontal applications 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 midmarket 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: Module 1: Module 2: Module 3: Siebel 7 Essentials Training Introducing Siebel eBusiness Applications Using the Siebel Client Organizing Data Behind the User Interface
Architecture and Installation Module 4: Module 5: Module 6: Module 7: Exploring the Siebel Architecture How Clients Access Siebel Data Installing Siebel Software Server Administration
Access Control and Organization Setup Module 8: Module 9: Module 10: Module 11: Module 12: Access Control and Views Access Control and Data Access Control and View Types Creating an Organization Authenticating Users
Exploring Siebel Applications Module 13: Module 14: Module 15: Module 16: Understanding Object Definitions Behind a Siebel Application Using Siebel Tools to Examine Object Definitions Understanding the Siebel Data Model The Siebel Data Model: Party Business Components
Configuration Module 17: Module 18: The Configuration Process Managing Object Definitions
Siebel Systems, Inc. COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED
Siebel 7 Essentials
Volume 2 Configuration, Continued Module 19: Module 20: Module 21: Module 22: Module 23: Module 24: Module 25: Module 26: Module 27: Module 28: Module 29: Module 30: Module 31: Module 32: Module 33: Module 34: Module 35: Module 36: Editing and Compiling Object Definitions Understanding Siebel Template Files Configuring Applications and Screens Configuring Views Configuring List Applets Configuring Form Applets Understanding Business Components and Joins Business Components and Joins: Party Extension Tables Understanding Business Objects and Links Configuring Business Components and Fields Creating a New BC Using the Standard 1:M Extension Table Configuring Navigation Extending the Database Configuring Picklists Configuring Multi-Value Groups Configuring Access Control Localizing an Application Configuration Guidelines Volume 3 Data Loads Module 37: Module 38: Module 39: Module 40: Module 41: Introducing Enterprise Integration Manager Data Mapping Invoking Enterprise Integration Manager Setting Enterprise Integration Manager Options Access Control and Access Groups
ii COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED
Siebel 7 Essentials
Business Process Automation Module 42: Module 43: Module 44: Module 45: Module 46: Module 47: Module 48: Module 49: Module 50: Deployment Module 51: Module 52: Module 53: Conclusion Module 54: Final Words Using Siebel Remote to Support Mobile Clients Additional Siebel Remote Topics Migrating Data Between Environments Introducing Siebel Workflow Invoking Workflow Processes Additional Workflow Topics Introducing Assignment Manager Creating Sales Assignment Rules Creating Service Assignment Rules Invoking Assignment Manager Personalizing View and Applet Access Personalizing Content and Behavior
Siebel Systems, Inc. COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED
iii
Siebel 7 Essentials
iv COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED
Siebel 7 Essentials Training
i.1
Siebel Technical Training Siebel 7 Essentials

Version 7.0 Version 7.0 November 2001 November 2001
Module i: Siebel 7 Essentials Training
1 of 17
Siebel 7 Essentials
COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED
i.2
Siebel 7 Essentials
i.3
Module Objectives
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
3 of 17
Siebel 7 Essentials
i.4
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?
4 of 17
Siebel 7 Essentials
i.5
Training Site Information

Bathrooms Class duration and breaks
Telephones
Meals and refreshments
Fire Exits
Questions?
5 of 17
Siebel 7 Essentials
i.6
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
6 of 17
Siebel 7 Essentials
i.7
Course Objectives
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
7 of 17
Siebel 7 Essentials
i.8
Course Audience
This course is designed for:
Application Developers System Architects and Configurators Database Administrators Systems Administrators
8 of 17
Siebel 7 Essentials
i.9
Course Methodology
Subject matter will be delivered via:
Lecture and slide presentations Software demonstrations Class discussions Hands-on labs
9 of 17
Siebel 7 Essentials
i.10
Overview of Course Flow

1. Foundations 2. Architecture and Installation 3. Access Control and Organization Setup 4. Exploring Siebel Applications
5. Configuration
6. Data Loads
7. Business Process Automation
8. Deployment
9. Conclusion
10 of 17
Siebel 7 Essentials
i.11
Agenda
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
11 of 17
Siebel 7 Essentials
i.12
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
12 of 17
Siebel 7 Essentials
i.13
Agenda Continued
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
13 of 17
Siebel 7 Essentials
i.14
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
14 of 17
Siebel 7 Essentials
i.15
Agenda Continued
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
15 of 17
Siebel 7 Essentials
i.16
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
16 of 17
Siebel 7 Essentials
i.17
Summary
This module provides an introduction to the:
Instructor and fellow students (class participants) Training site Course materials, goals, audience, methodology, objectives, and agenda
17 of 17
Siebel 7 Essentials
i.18
Siebel 7 Essentials
Introducing Siebel eBusiness Applications
1.1
Module 1: Introducing Siebel eBusiness Applications
Siebel 7 Essentials
1.2
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
Why you need to know

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
2 of 25
Siebel 7 Essentials
1.3
Siebel eBusiness Enterprise

An integrated product suite that helps manage customer relationships Built on a common architecture
Industry Applications
Siebel eFinance Siebel eInsurance Siebel eHealthcare Siebel eCommunications Customer Applications A Siebel eMarketing Siebel eService Siebel eSales Siebel Interactive Selling Suite (ISS) Siebel eAutomotive Siebel eEnergy Siebel ePharma Siebel ePublic Sector
Employee Applications Siebel Call Center Siebel Handheld Siebel Service Siebel Wireless Siebel Sales Siebel Voice Siebel Field Service Partner Applications Siebel eChannel
For complete listing, see Siebel Bookshelf or www.siebel.com
Siebel eBusiness Architecture

Module 1: Introducing Siebel eBusiness Applications 3 of 25
Siebel 7 Essentials
1.4
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 Siebel eCustomer, MidMarket Edition Siebel eSales,MidMarket Edition Siebel eService, MidMarket Edition Employee Applications Siebel Call Center, MidMarket Edition Siebel Sales, MidMarket Edition Siebel Service, MidMarket Edition
Partner Applications Siebel eChannel, MidMarket Edition
Siebel eBusiness Architecture
4 of 25
Siebel MidMarket Edition
MME is a product line optimized to meet the fundamental eBusiness 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.
Siebel 7 Essentials
1.5
Business Entities
Siebel eBusiness Applications use entities to manage business relationships, for example
Accounts Opportunities Contacts Service Requests Activities Assets
5 of 25
Entity
A business entity is something in the real world in which we have a business interest.
Siebel 7 Essentials
1.6
Account
Is a business external to your company Represents a current or potential client, a business partner, or a competitor
6 of 25
Siebel 7 Essentials
1.7
Opportunity
Is a potential revenue-generating event Has the following characteristics
Possible association with an account Potential revenue Probability of completion Close date
7 of 25
Siebel 7 Essentials
1.8
Contact
Is a person with whom you do business Has the following characteristics
Name Job title Email address
8 of 25
Siebel 7 Essentials
1.9
Service Request
Is a request from a customer for information or assistance with a problem related to products or services purchased from your company Has the following characteristics
Status Severity Priority
9 of 25
Siebel 7 Essentials
1.10
Activity
Is a specific task or event to be completed Has the following characteristics
Start date and due date Priority Assigned to specific employees for completion
10 of 25
Siebel 7 Essentials
1.11
Asset
Is an instance of a purchased product Has the following characteristics
Asset number Product and part number Status
11 of 25
Siebel 7 Essentials
1.12
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
12 of 25
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.
Siebel 7 Essentials
1.13
Types of User Interfaces (UI)

High interactivity
Available for employee applications, supporting highly interactive enterprise users Requires Internet Explorer 5 or higher
Standard interactivity
Available for customer applications Behaves like traditional Web applications, requiring frequent page refreshes
13 of 25
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.
Siebel 7 Essentials
1.14
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
14 of 25
Siebel 7 Essentials
1.15
Differences Between High and Standard Interactivity

The following features are supported only by high interactivity
Client-side scripting
With access to Siebel objects on the client side
Interactive controls
Calculator, calendar date/time selector
Keyboard shortcuts
For frequently used commands
15 of 25
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.
Siebel 7 Essentials
1.16
Employee Application: Siebel Sales

Siebel Sales allows your sales force to manage accounts, sales opportunities, and contacts
Personalized content
16 of 25
Reference
For more information on Siebel Sales, go to www.siebel.com.
Siebel 7 Essentials
1.17
Employee Application: Siebel Call Center

Siebel Call Center allows your agents to coordinate and manage all customer interactions
Click menu button for more commands
17 of 25
Reference
For more information on Siebel Call Center, go to www.siebel.com.
Siebel 7 Essentials
1.18
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

Module 1: Introducing Siebel eBusiness Applications 18 of 25
Reference
For more information on Siebel eService, go to www.siebel.com.
Siebel 7 Essentials
1.19
Customer Application: Siebel eSales

Siebel eSales allows your customers to purchase products over the Web
Shopping cart Browse products
19 of 25
Reference
For more information on Siebel eSales, go to www.siebel.com.
Siebel 7 Essentials
1.20
Partner Application: Siebel eChannel

Siebel eChannel allows companies and their partners to work together to market and sell to, service, and retain customers
Company news
Recommended items
20 of 25
Reference
For more information on Siebel eChannel, go to www.siebel.com.
Siebel 7 Essentials
1.21
Applications Used in This Course

Siebel Call Center and Siebel eService are used during this course
Technology learned here applies to all Siebel applications
For information on all other Siebel eBusiness Applications, see

Siebel Bookshelf www.siebel.com
21 of 25
Siebel 7 Essentials
1.22
Standard Siebel Application

Functionality demonstrated so far is standard and prebuilt Data presented in the UI is stored in a database
Siebel Database
22 of 25
Siebel 7 Essentials
1.23
Changing the Standard Application

Standard Siebel applications can be changed to meet your business requirements 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
23 of 25
Siebel 7 Essentials
1.24
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
24 of 25
Siebel 7 Essentials
1.25
Summary
This module showed you how to:
Describe standard Siebel terminology and user interface behavior Describe Siebel employee, customer, and partner applications Describe standard features that can be changed
25 of 25
Siebel 7 Essentials
1.26
Siebel 7 Essentials
Using the Siebel Client
2.1
2
Module 2: Using the Siebel Client
Siebel 7 Essentials
2.2
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
2 of 25
Siebel 7 Essentials
2.3
Home Page
Logging in to a Siebel application displays a home page
Application-level menu
Frequently used screens Personalized content based on login
Drill down on hyperlink for more detail
3 of 25
Home Page
This is an example of a typical home page for a Siebel employee application.
Siebel 7 Essentials
2.4
Navigating the UI
Clicking on different UI elements navigates to different data
Screen tabs Show drop-down
Selected record List
View tabs Form
4 of 25
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 View Site 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.
Siebel 7 Essentials
2.5
Screens and Views

Screens and views show business entities and related data
Accounts screen
Indicates the subset of account data displayed in list
List
Subsets of account data that can be displayed Form
5 of 25
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.
Siebel 7 Essentials
2.6
Navigating Through Lists and Forms

Use next or previous record set buttons or menu button
Click menu button to navigate to first or last records in list
Navigate through records in a list
Navigate to next record or previous record in a form
6 of 25
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.
Siebel 7 Essentials
2.7
Drilling Down for More Information

Drill down on hyperlink to see more information
1. Clicking account hyperlink
2. presents account and contact data
7 of 25
Hyperlinks
Hyperlinks can be configured using Siebel Tools.
Siebel 7 Essentials
2.8
Navigating Through Views and Screens

Back and forward arrows
Use arrows to navigate to previous screens and views
History drop-down
Select from drop-down list to navigate to previous screens and views Current view is at top of list
Thread bar
Click on hyperlink to navigate to previous view

Current view
8 of 25
Back and Forward Arrows
These are the arrows available for navigation in the Siebel application. Do 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
Siebel 7 Essentials
2.9
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 Picklists and multi-value groups Queries Favorites Sorting Keyboard accelerators
9 of 25
Siebel 7 Essentials
2.10
Application-Level Menu
This menu applies to the entire application and shows available actions
10 of 25
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.
Siebel 7 Essentials
2.11
Using Menu Buttons

Menu buttons show available actions for lists and forms
Click to show menu for Opportunities list
Click to show menu for Opportunity form
11 of 25
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 applicationlevel menu. The menu button is available only in the high interactivity interface.
Siebel 7 Essentials
2.12
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
12 of 25
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 Record
If a record cannot be undone or deleted, the actions will be grayed out and unavailable to the user.
Siebel 7 Essentials
2.13
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 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
13 of 25
Save Button
The presence of the Save button does not negate the implicit record-level commit described above.
Siebel 7 Essentials
2.14
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
Module 2: Using the Siebel Client 14 of 25
More Examples of MVGs
Multiple addresses can be associated to an account 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.
Siebel 7 Essentials
2.15
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 (QBE)
Siebel eBusiness Applications support QBE, which helps you quickly and easily find the information you are looking for.
Siebel 7 Essentials
2.16
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 Help Contents Index and click the letter O
16 of 25
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.
Siebel 7 Essentials
2.17
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
Siebel 7 Essentials
2.18
Saving Queries
Use the application-level menu to save a query
1. Select Edit Query Save As 2. Name the query and click OK
18 of 25
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.
Siebel 7 Essentials
2.19
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
19 of 25
Predefined Queries
Navigate to Application Administration Predefined Queries to view predefined queries for the application.
Siebel 7 Essentials
2.20
Sorting Data
Click the Sort icon in a column to sort data in ascending or descending order
Click up arrow for ascending (A Z) order
Click down arrow for descending (Z A) order
20 of 25
Siebel 7 Essentials
2.21
Keyboard Accelerators
Provide an alternative to mouse clicking for performing commands
Also known as keyboard shortcuts
Two modes
Basic Extended
Examples of record shortcuts
See online help for a full list of keyboard shortcuts. Select Help Contents Index and click the letter K
21 of 25
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).
Siebel 7 Essentials
2.22
Controlling UI Presentation: Columns

Click the menu button and select Columns Displayed
Current columns in the list
Columns available to be used in the list
Click buttons to add to or remove from Selected Columns
Click buttons to sequence columns
22 of 25
Siebel 7 Essentials
2.23
Controlling UI Presentation: Show More

Toggle the list or form to show more or less detail for a record
1. Click Show more button
2. to show more details in form
23 of 25
Siebel 7 Essentials
2.24
Summary
Use the Siebel user interface (UI)
24 of 25
Siebel 7 Essentials
2.25
Lab
In the lab you will:
Practice using the Siebel Call Center application
25 of 25
Siebel 7 Essentials
2.26
Siebel 7 Essentials
Organizing Data Behind the User Interface
3.1
Module 3: Organizing Data Behind the User Interface
Siebel 7 Essentials
3.2
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
2 of 17
Siebel 7 Essentials
3.3
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
Form Business data item
3 of 17
Record
A record is a collection of related business data items presented in a list or form.
Siebel 7 Essentials
3.4
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

Module 3: Organizing Data Behind the User Interface 4 of 17
Siebel 7 Essentials
3.5
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 Multiple records displayed in a list
Business components work here Single record displayed in a form
Database
5 of 17
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.
Siebel 7 Essentials
3.6
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
6 of 17
Siebel 7 Essentials
3.7
Common Business Components

Business components representing common Siebel business entities include:
Account Opportunity Service Request Contact Activity
7 of 17
Siebel 7 Essentials
3.8
View
A collection of related lists and forms representing a functional business area
Business area
Account list
Account form
8 of 17
View
A view can also be referred to as a collection of applets, which may be of the type Form or List.
Siebel 7 Essentials
3.9
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 object is a collection of business components
Form references one business component
9 of 17
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.
Siebel 7 Essentials
3.10
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 object
Business component
Opportunity
Product
Contact
Business component
10 of 17
Siebel 7 Essentials
3.11
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
Business object
Account
3
Parent BC
Opportunity
Product
Contact
Child BC
11 of 17
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.
Siebel 7 Essentials
3.12
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 Account parent business component Account Record
Account
Opportunity
Product
Contact
Business object
Siebel 7 Essentials
3.13
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 business component Contact Record Business object
Opportunity
Product
Siebel 7 Essentials
3.14
Determine Business Components for a View

Use Help About View to determine business components for a view
Parent business component
Child business component
14 of 17
Siebel 7 Essentials
3.15
Siebel Applications Are characterized by three distinct layers

1.Data presentation 2. Business logic 3. Data storage
Account
Account
3
Contact
Opportunity
Product
15 of 17
Reference
Siebel Tools and Configuration Guide
Siebel 7 Essentials
3.16
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
16 of 17
Siebel 7 Essentials
3.17
Lab
Use About View to determine business components and business objects which organize and display data in some Siebel views
17 of 17
Siebel 7 Essentials
3.18
Siebel 7 Essentials
Exploring the Siebel Architecture
4.1
Module 4: Exploring the Siebel Architecture
Siebel 7 Essentials
4.2
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
2 of 23
Siebel 7 Essentials
4.3
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
Database Server Module 4: Exploring the Siebel Architecture
Siebel File System
3 of 23
Clients
Clients are discussed in more detail in the next module.
Siebel 7 Essentials
4.4
Logical Architecture
The Siebel architecture consists of:
Siebel Web Client (browser) Plugins for industry standard Web servers Siebel Gateway Server Siebel Enterprise Server One or more Siebel Servers Siebel Server Components Database Server Siebel File System
Browser Web Server Siebel Web Server Extension Image Cache
Gateway Server
Enterprise Server Siebel Server Component
Siebel Server Component
Database Server Module 4: Exploring the Siebel Architecture
Siebel File System
4 of 23
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 7 Essentials
4.5
Siebel Clients
Run in a variety of environments
Web browsers, WML devices, and PDAs (Windows CE and Palm)
Two modes of interaction

Standard mode High Interactivity mode
Connection state stored on Siebel Server, supporting reconnection if necessary
Browser
Web Server Siebel Web Server Extension Image Cache
Gateway Server
4
5 of 23
Reference
Siebel System Requirements and Supported Platforms
WML
WML (Wireless Markup Language) is intended for use with narrowband devices, including cellular phones and pagers.
Siebel 7 Essentials
4.6
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
Gateway Server Enterprise Server Enterprise Server Siebel Server Siebel Server Component Object Manager
Workflow Manager File System Manager
Siebel Server Siebel Server Component Component
6 of 23
Reference
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.
Siebel 7 Essentials
4.7
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
Gateway Server Enterprise Server Enterprise Server Siebel Server Siebel Server Component Object Manager
7 of 23
Siebel 7 Essentials
4.8
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
Gateway Server Enterprise Server Siebel Server Component
8 of 23
Gateway Server
The Gateway Server runs as a Windows service or UNIX daemon process.
Clustered Environments
The Gateway Server can be run in a clustered environment to provide redundancy and avoid a single point of failure.
Siebel 7 Essentials
4.9
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)

Gateway Server
Enterprise Server Enterprise Server Siebel Server Siebel Server Component Object Manager
9 of 23
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 7 Essentials
4.10
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 Siebel Server
Object Manager Workflow Manager File System Manager
Database Server
Siebel File System
10 of 23
Siebel 7 Essentials
4.11
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
Enterprise Server Siebel Server
Examples: Synchronization Manager Workflow Manager File System Manager Object Manager Communications Server
11 of 23
Server Components
Details about important server components are provided later in the module.
Siebel 7 Essentials
4.12
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 Siebel Server
Database Server
Siebel File System
12 of 23
Siebel 7 Essentials
4.13
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 Siebel Server Object Manager Siebel Web Engine Business Object Business Object Business Object Data Manager Component Siebel Server
13 of 23
Siebel 7 Essentials
4.14
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 Siebel Server Object Manager Business Object Business Object Data Manager Siebel Server Component
14 of 23
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.
Siebel 7 Essentials
4.15
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 Siebel Server Component Compo
Object Manager Data Manager
4
Siebel File System
Database Server
15 of 23
Extensible Schema
The predefined database schema is extensible.
Siebel 7 Essentials
4.16
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 Business Object HTML Siebel Web Engine Web Server SWSE Image Cache Browser
Siebel Templates
16 of 23
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 7 Essentials
4.17
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 Siebel Server Siebel Server Component File System Manager
Database Server
Siebel File System
17 of 23
Siebel 7 Essentials
4.18
Web Usage Scenario

Web Server Siebel Web Server Extension 2 1 6
Browser generates HTTP request
Web server recognizes that URL contains a Siebel request and passes it to the Siebel Web Engine (SWE)
SWE builds HTML page with data and template tags which is passed via the Web server to the browser
Object Manager Business Object Business Object Siebel Web Engine
Siebel Templates
Template used is based on the view requested as specified by operation
Data Manager Data Manager
SWE requests retrieved data from Object Manager
Object Manager retrieves data from Siebel database or external application
Inbound Outbound
Siebel Data
18 of 23
Siebel 7 Essentials
4.19
Overview: Logical Server Architecture

Web Server: Provides access to Siebel clients, processing requests using Siebel Web Server Extension Web Server Siebel Web Server Extension Image Cache
Gateway Server: Provides access to and distributes load for Siebel Servers
Gateway Server
Enterprise Server Siebel Server Enterprise Server: Group of Siebel Servers that access the same Database Server
Object Manager (Includes SWE)
Siebel Server Component Siebel Server: Runs one or more components that supply services to clients
4
Database Server: Predefined tables and columns that store Siebel data Database Server
Siebel File System
File System: Directory that stores compressed files used by Siebel applications
19 of 23
Reference
Siebel 7 Essentials
4.20
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 Gateway Server
High-speed LAN
Siebel Server
Web Server
SWSE
Siebel File System
Siebel Server Firewall Firewall Database Server
20 of 23
Siebel 7 Essentials
4.21
You Decide
Consult the documentation to determine which software to install on which machine(s) given your environment and requirements
21 of 23
Siebel 7 Essentials
4.22
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
22 of 23
Siebel 7 Essentials
4.23
Lab
Match Siebel architecture components to their descriptions
23 of 23
Siebel 7 Essentials
4.24
Siebel 7 Essentials
How Clients Access Siebel Data
5.1
Module 5: How Clients Access Siebel Data
Siebel 7 Essentials
5.2
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
2 of 24
Siebel 7 Essentials
5.3
Siebel Clients: Overview

Use a standard Web browser to display information in the user interface (UI) with data retrieved from the Siebel database Access Siebel data differently based on client type
Not all connect through Web Server and Siebel Web Server Extension (SWSE)
Browser
Web Server Siebel Web Server Extension
Gateway Server
Database Server Module 5: How Clients Access Siebel Data
Siebel File System
3 of 24
Reference
Siebel 7 Essentials
5.4
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
4 of 24
Reference
Siebel Web Client Administration Guide
Siebel 7 Essentials
5.5
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 Handheld Web Mobile Web
Web Server
Dedicated Web
Siebel Servers
Database Server
Siebel File System
5
5 of 24
Siebel 7 Essentials
5.6
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 Siebel Web Server Extension
Browser
Gateway Server
6 of 24
Siebel 7 Essentials
5.7
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
Object Manager Parameters .srf .cfg Database Templates
5
7 of 24
Siebel 7 Essentials
5.8
Siebel Application Components

Data that specifies the application is separate from the engine that executes the application
Web Clients Mobile and Dedicated Web Clients
Object Manager Parameters
Templates
.srf .cfg Database
8 of 24
Siebel 7 Essentials
5.9
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
.srf .cfg Database

Web Clients Mobile and Dedicated Web Clients Module 5: How Clients Access Siebel Data 9 of 24
Siebel 7 Essentials
5.10
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
Mobile and Dedicated Web Clients
Templates
.srf .cfg Database
10 of 24
Siebel 7 Essentials
5.11
Configuration File and Component Parameters

Contains initialization settings for the Object Manager including:
Gateway Server Enterprise Server Repository (.srf) file Application or server component
Object Manager Parameters .srf .cfg Database
Web Clients Mobile and Dedicated Web Clients Module 5: How Clients Access Siebel Data 11 of 24
LDAP directory server File system Database server (data source)
Templates
Siebel 7 Essentials
5.12
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
12 of 24
Siebel 7 Essentials
5.13
Application Component Locations

For Web and Wireless Web Clients, components reside on the server For all other clients, components reside on the client
5
Module 5: How Clients Access Siebel Data 13 of 24
Siebel 7 Essentials
5.14
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 Enterprise Server Siebel Server Siebel Server Object Manager Business Object Business Object Siebel Web Engine Data Manager Web Client Web Server Siebel Web Server Extension
HTTP
.cfg .srf Database Server

Siebel File System
14 of 24
Siebel 7 Essentials
5.15
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
Siebel 7 Essentials
5.16
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 Enterprise Server Siebel Server Siebel Server Object Manager Business Object Business Object Siebel Web Engine Data Manager Wireless Web Client .cfg .srf Database Server
Siebel File System
Web Server Siebel Web Server Extension WAP Server
16 of 24
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
Siebel 7 Essentials
5.17
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 Siebel Server Siebel Server Object Manager Business Object Business Object Siebel Web Engine Data Manager Mobile/Handheld Client
.cfg
.srf
Database Server
Siebel File System
5
17 of 24
Siebel 7 Essentials
5.18
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
18 of 24
Siebel 7 Essentials
5.19
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

SWSE
.cfg
.srf
Object Manager Business Object Business Object Siebel Web Engine Data Manager Siebel Server Siebel Server
5
Disconnected Processing
Disconnected processing refers to handheld and mobile Web client processing which has no connection to a Siebel Server or database server.
Siebel 7 Essentials
5.20
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 Client Web Server
SWSE
Enterprise Server Siebel Server .cfg .srf

Component
Object Manager Business Object SWE Data Manager Database Server

Siebel File System
20 of 24
Siebel 7 Essentials
5.21
All Clients
Siebel architecture supports a mixture all clients
Wireless Web Client WAP Server Web Server SWSE Web Client
Gateway Server Dedicated Web Client Web Server

SWSE
Enterprise Server Siebel Server Object Manager

Siebel Web Engine Data Manager Component
Mobile/Handheld Client
.cfg
.srf
Object Manager
Siebel Web Engine Data Manager
.cfg
.srf
.cfg
.srf
Database Server
Siebel File System
5
21 of 24
Siebel 7 Essentials
5.22
You Decide
Consult the documentation to determine which software to install on which machine(s) given your environment and client requirements
22 of 24
Siebel 7 Essentials
5.23
Summary
Identify the various Siebel clients Identify how each client accesses Siebel Servers and data
5
Siebel 7 Essentials
5.24
Lab
Complete a possible deployment diagram
24 of 24
Siebel 7 Essentials
Installing Siebel Software
6.1
Module 6: Installing Siebel Software
Siebel 7 Essentials
6.2
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
2 of 25
Siebel 7 Essentials
6.3
Consult the Documentation

Siebel System Requirements and Supported Platforms Siebel Release Notes Siebel Server Installation Guide Siebel Web Client Administration Guide
3 of 25
Siebel 7 Essentials
6.4
Pre-Installation Tasks
Prepare for installation Create operating system account(s) Create the Siebel database Create the Siebel file system directory and share it
4 of 25
Reference
Siebel Web Client Administration Guide
Siebel 7 Essentials
6.5
Prepare for Installation

Verify prerequisites defined in the documentation
Supported hardware Supported operating system (OS) Required third-party software
5 of 25
Siebel 7 Essentials
6.6
Prepare for Installation Continued

Identify where software will be installed
Which machine(s) What naming convention What directory structure
Example:
Web Client
Enterprise Server
Gateway Server Siebel Server
G1 S1
Siebel File System
C1 Machine/Host Names/Addresses: C1, G1, S1, D1, W1

Web Server
D1
Database Server
W1
6 of 25
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. The machine running the client browser.
C1
Siebel 7 Essentials
6.7
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
7 of 25
Owner Account
The Siebel Service Owner Account is used to run Windows processes or start UNIX daemon processes.
Siebel 7 Essentials
6.8
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: Database: Size: D1 siebeldb 500 MB
siebeldb
D1
8 of 25
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.
Siebel 7 Essentials
6.9
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:
Machine Name: File System: S1 C:\siebfile S1
C:\siebfile
9 of 25
File System
The default name is siebfile. You may change the name.
Siebel 7 Essentials
6.10
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
10 of 25
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.
Siebel 7 Essentials
6.11
Install Gateway Server

Invoke server installation program to install and configure Gateway Server on its designated machine Example:
Gateway Server
Destination Directory: OS Account: Machine Name: C:\sea701 NTSERV G1 G1
G1
Follow steps in installation wizard and consult documentation
11 of 25
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.
Reference
Siebel 7 Essentials
6.12
Verify Gateway Server

Inspect directory and files in the Siebel root directory Verify the Windows Service or UNIX daemon process is started Example:
12 of 25
Siebel 7 Essentials
6.13
Install Enterprise and Siebel Servers

Invoke server installation program to create and configure an Enterprise Server, Siebel Server, and ODBC data source Example:
Destination Directory: Enterprise Server Logical Name: File System: Database Machine Name: Database/Tablespace: Database User/Password: Siebel Server Machine Name: Siebel Server Logical Name: OS Account: C:\sea701 siebel HQ\G1\c:\siebfile D1 siebeldb SADMIN/SADMIN S1 siebel_S1 NTSERV
SiebSrvr_siebel
Gateway Name Server Hostname: G1
Enterprise Server
siebel
Siebel Server
S1
S1
C:\siebfile
ODBC Data Source
13 of 25
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. The file system is a shared directory.
File System
siebeldb
The default name of the database that was created in the pre-installation tasks. It will contain the Siebel database tables. 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.
SADMIN
siebel_S1
The name of the Siebel Server. You may set this to a different string of characters.
Siebel 7 Essentials
6.14
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:
14 of 25
Siebel 7 Essentials
6.15
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
Destination Directory: Siebel Database Server Directory: Siebel Server directory: Database User/Password: Database Table Owner: ODBC Data Source Name: C:\sea701 C:\sea701\dbsrvr C:\sea701\siebsrvr SADMIN/SADMIN SIEBEL/SIEBEL SiebSrvr_siebel
siebeldb
D1
Database Server
15 of 25
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. Siebel Server Installation Guide for Microsoft Windows Siebel Server Installation Guide for UNIX Siebel Tools Reference
Reference
Siebel 7 Essentials
6.16
Verify Database Server

Inspect directory and log files Verify database connection Verify schema and seed data Verify repository data Example:
16 of 25
Siebel 7 Essentials
6.17
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: Gateway Server Machine Name: Enterprise Server Logical Name: Siebel Server Logical Name: C:\sea701\SWEApp G1 siebel siebel_S1 W1
Web Server SWSE
17 of 25
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 Reference
The name of the machine on which the Web Server is installed. Siebel Server Installation Guide
Siebel 7 Essentials
6.18
Verify Siebel Web Server Extension

Inspect Web Server virtual directories on Internet Information Server
18 of 25
Siebel 7 Essentials
6.19
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
19 of 25
Siebel 7 Essentials
6.20
Managing License Keys

Once you have entered the license key, you can add, modify, or delete license keys
Navigate to Application Administration License Keys to add additional products
20 of 25
Siebel 7 Essentials
6.21
Verify Client
Verify application launch and connectivity to server Example:
Web Server Siebel Application SWE Command
21 of 25
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.
Siebel 7 Essentials
6.22
Post Installation
Example:
Gateway Server
G1 S1
Enterprise Server
siebel
Siebel Server
G1
Client
S1
C:\siebfile
File System
C1
Web Server SWSE
D1
siebeldb
W1
Web Server running Siebel Web Server Extension
Database Server
22 of 25
Siebel 7 Essentials
6.23
Classroom Installation
In the classroom, students will install all software on their desktop machines
Gateway Server
HOSTNAME00
D:\sea701\gtwysrvr
Enterprise Server
siebel HOSTNAME00
Web Server
Siebel Server Siebel Web Server Extension Database Server File System Mobile client
D:\sea701\siebsrvr
D:\sea701\SWEApp
HOSTNAME00
siebeldb
D:\sea701\dbsrvr D:\siebfile
C:\siebfile
C:\sea701\client
23 of 25
Siebel 7 Essentials
6.24
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
24 of 25
Siebel 7 Essentials
6.25
Lab
Install a Siebel Server Environment Please follow the directions carefully, and Run scripts to create users in the pay attention to the Siebel database 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
25 of 25
Siebel 7 Essentials
6.26
Siebel 7 Essentials
Server Administration
7.1
Module 7: Server Administration
Siebel 7 Essentials
7.2
Module Objectives
Use Server Manager to administer your Siebel Enterprise

Server Manager enables you to perform server administration duties required for your Siebel application
2 of 27
Reference
Siebel Server Administration Guide
Siebel 7 Essentials
7.3
Server Manager
Is a set of views that allow you to manage your Siebel Enterprise
3 of 27
Siebel 7 Essentials
7.4
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
4 of 27
Siebel 7 Essentials
7.5
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
5 of 27
Siebel 7 Essentials
7.6
Using Server Manager

There are two ways to use Server Manager
From the Siebel application interface
From the command line
6 of 27
Siebel 7 Essentials
7.7
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
7 of 27
Siebel 7 Essentials
7.8
Component Groups
Component Groups consist of related server components Navigate to Server Administration Enterprise Configuration to enable or disable component groups
Click the menu button
enable or disable component group

Module 7: Server Administration 8 of 27
Siebel 7 Essentials
7.9
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
9 of 27
Enable Component Groups
To execute components on the Siebel Server, the component group to which they belong must be enabled.
Siebel 7 Essentials
7.10
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 Administration Enterprise Configuration Component Definitions
Parameters for the Call Center Object Manager component

Reference
Siebel 7 Essentials
7.11
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
11 of 27
Siebel 7 Essentials
7.12
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
12 of 27
Siebel 7 Essentials
7.13
Setting Parameters Continued

Parameters are set at any of these levels
Enterprise Server Component Definition Server Component Task
Highest
Lowest
A parameter set at the task level overrides the same parameter set at a higher level
13 of 27
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.
Siebel 7 Essentials
7.14
Server Component Modes

A server component executes in one of three modes
Batch Background Interactive
14 of 27
Siebel 7 Essentials
7.15
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 Administration Enterprise Configuration Enterprise Component Groups.
Siebel 7 Essentials
7.16
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 Administration Enterprise Configuration Batch Component Admin

Click Synchronize button
Synchronized components
16 of 27
Synchronizing Components
Synchronize also needs to be performed whenever batch component definitions change, such as when parameters are updated or new component definitions are created.
Siebel 7 Essentials
7.17
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
Subset of Workflow Management component group
17 of 27
Default Tasks Parameter
Components with the parameter Default Tasks > 0 will start automatically when the Siebel Server is started. Navigate to Server Administration Enterprise Configuration Component Definitions to view or modify component parameters.
Siebel 7 Essentials
7.18
Interactive Components
The task runs in response to client requests
No need to manually start
The task stops when the client disconnects Examples

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 Administration Enterprise Configuration Enterprise Component Groups.
Siebel 7 Essentials
7.19
Component States
A server component may be in one of five states
State Online Running Offline Shutdown Description Tasks are currently not running for the assigned component, but new tasks can be started. Tasks are currently running for the assigned component on the Siebel Server, and new tasks are allowed to start. Currently running tasks continue to run, but new tasks cannot be started for the component. 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.
19 of 27
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.
Siebel 7 Essentials
7.20
Managing a Component
Navigate to Server Administration Servers Server Components to change a server component state
Select the component
and click the appropriate action
20 of 27
Siebel 7 Essentials
7.21
Starting a Batch Task

Navigate to Server Administration Enterprise Operations Component Requests
1. Create new request and select component
2. Modify parameters
3. Submit request
21 of 27
Component/Job
This list is populated when the batch components are synchronized on the Siebel Server.
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.
Siebel 7 Essentials
7.22
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
22 of 27
Reference
Siebel 7 Essentials
7.23
Monitoring a Task
A task updates its state during execution
Can be in one of the following states
State Starting up Running Paused Shutting Down Completed Exited with Error Killed Description Indicates that the task has been started Indicates that the task is executing normally Indicates that the task has been temporarily placed in a suspended state Indicates that the task has been instructed to stop, or the component or server is being shut down Indicates that the task ran to completion and exited normally Indicates that the task encountered an error during its processing and exited Indicates that the process was not able to shut down cleanly, and had to be forced to shutdown
23 of 27
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: Srvrmgr> list state values for task <task number>
Siebel 7 Essentials
7.24
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
24 of 27
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.
Siebel 7 Essentials
7.25
Viewing Task Information Continued

View log file on the Siebel Server
Note the task number
View file in /log directory
25 of 27
Log Files
In Windows environments, the log files are stored in: <Siebel_server_root>/siebsrvr/log In UNIX environments, log files are stored in: <Siebel_server_root>/enterprises/<siebel enterprise>/server/log
Siebel 7 Essentials
7.26
Summary
Use Server Manager to administer your Siebel Enterprise
26 of 27
Siebel 7 Essentials
7.27
Lab
Enable server components Synchronize batch components Start a task and view its log Use command-line Server Manager
27 of 27
Siebel 7 Essentials
7.28
Siebel 7 Essentials
Access Control and Views
8.1
Module 8: Access Control and Views
Siebel 7 Essentials
8.2
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
2 of 14
Reference
Authentication and Access Control Administration Guide
Siebel 7 Essentials
8.3
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
CFO
Forecasting
Field Sales Rep

Opportunities
Customers
Orders
Channel Partners Call Center Agent
Service Requests
Opportunities
3 of 14
Siebel 7 Essentials
8.4
Siebel eBusiness Solution: Access Control

Consists of all mechanisms used to control user access to views and data records in Siebel eBusiness Applications
4 of 14
Siebel 7 Essentials
8.5
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
5 of 14
Siebel 7 Essentials
8.6
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
6 of 14
Siebel 7 Essentials
8.7
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
7 of 14
Siebel 7 Essentials
8.8
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
8 of 14
Siebel 7 Essentials
8.9
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
9 of 14
Siebel 7 Essentials
8.10
Multiple Responsibilities
When users log in, they see the union of all views for their assigned responsibilities
10 of 14
Siebel 7 Essentials
8.11
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
11 of 14
Siebel 7 Essentials
8.12
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
12 of 14
Siebel 7 Essentials
8.13
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
13 of 14
Siebel 7 Essentials
8.14
Lab
Explore responsibilities and views for different users
14 of 14
Siebel 7 Essentials
Access Control and Data
9.1
Module 9: Access Control and Data
Siebel 7 Essentials
9.2
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

To effectively use Siebel eBusiness Applications, you need to understand how access to data is controlled
2 of 24
Reference
Siebel 7 Essentials
9.3
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
3 of 24
Siebel 7 Essentials
9.4
Controlling Access to Customer Data

Access to customer data can be restricted using the following access control mechanisms
Personal Position-based Organization-based
4 of 24
Siebel 7 Essentials
9.5
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
5 of 24
Siebel 7 Essentials
9.6
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
6 of 24
Siebel 7 Essentials
9.7
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

Module 9: Access Control and Data 7 of 24
Siebel 7 Essentials
9.8
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
8 of 24
Siebel 7 Essentials
9.9
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
9 of 24
Siebel 7 Essentials
9.10
Primary Position
If an employee has multiple positions, one is marked as primary
One position is defined as primary for an employee
Click the select button in the Position field to see all positions per employee
10 of 24
Siebel 7 Essentials
9.11
Change Position
Users can change position during a session by selecting View User Preferences Change Position Users can only log in as one position at a time By default, log in is based on the users primary position
11 of 24
Siebel 7 Essentials
9.12
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
12 of 24
Siebel 7 Essentials
9.13
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
13 of 24
Siebel 7 Essentials
9.14
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
14 of 24
Siebel 7 Essentials
9.15
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
15 of 24
Siebel 7 Essentials
9.16
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

Module 9: Access Control and Data 16 of 24
Siebel 7 Essentials
9.17
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
17 of 24
Siebel 7 Essentials
9.18
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)
18 of 24
Siebel 7 Essentials
9.19
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
19 of 24
Siebel 7 Essentials
9.20
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
20 of 24
Siebel 7 Essentials
9.21
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
21 of 24
Siebel 7 Essentials
9.22
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
22 of 24
Siebel 7 Essentials
9.23
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
23 of 24
Siebel 7 Essentials
9.24
Lab
Explore data level Access Control for different users
24 of 24
Siebel 7 Essentials
Access Control and View Types
10.1
Module 10: Access Control and View Types
10
Siebel 7 Essentials
10.2
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

To effectively use Siebel eBusiness Applications, you need to understand the different available view types
2 of 12
Reference
Siebel 7 Essentials
10.3
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
3 of 12
10
Siebel 7 Essentials
10.4
View Types
Different view types accommodate different users
My View My Teams View All View All Across Organization View
4 of 12
Siebel 7 Essentials
10.5
My View
Displays records for which a user has direct access
Can use any Access Control mechanism Examples: My Opportunities, My Accounts
5 of 12
10
Siebel 7 Essentials
10.6
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
6 of 12
Siebel 7 Essentials
10.7
My Teams View
Used by managers to display records for users who report to them
Examples: My Teams Opportunities, My Teams Service Requests
7 of 12
10
Siebel 7 Essentials
10.8
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
8 of 12
Siebel 7 Essentials
10.9
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
9 of 12
10
Siebel 7 Essentials
10.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
10 of 12
Siebel 7 Essentials
10.11
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
11 of 12
10
Siebel 7 Essentials
10.12
Lab
Explore different view types
12 of 12
Siebel 7 Essentials
Creating an Organization
11.1
Module 11: Creating an Organization
11
Siebel 7 Essentials Siebel Systems, Inc.
11.2
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
2 of 14
Siebel 7 Essentials
11.3
Organizational Hierarchy
Allows for the definition of organizations, divisions, and positions Use a top-down approach to define the company structure
Organization
Siebel Europe Northern Europe Consulting

Professional Services, Galway Consultant Consultant 9 10
Division
Sub-division
Professional Services, Amsterdam Consultant Consultant 7 8
Positions
3 of 14
11
11.4
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
4 of 14
Siebel 7 Essentials
11.5
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 Consulting

Professional Services, Rome Consultant Consultant 6 Consultant 4 5
Division Sub-division
Northern Europe Consulting

Professional Services, Galway Consultant Consultant 9 10
5 of 14
Professional Services, Madrid Consultant Consultant 3 Consultant 1 2
11
11.6
Defining Divisions
Navigate to Group Administration Divisions
Explorer view
Required field
Required field
6 of 14
Creating Divisions
Use caution when creating a division. Once you create a division: You cannot delete it You cannot change the organization.
Siebel 7 Essentials
11.7
Defining Organizations
Set Organization Flag to make a division an organization
Organization appears in Explorer View Set flag

Module 11: Creating an Organization 7 of 14
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
11.8
Defining Organizations Continued

Navigate to Group Administration Organizations
Explorer View
Required fields: Name, Currency
8 of 14
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.
Siebel 7 Essentials
11.9
Defining Positions
Navigate to Group Administration Positions Create positions based on your reporting structure
Ask the question Who needs to see what?
Explorer View
Reporting relationship
Required fields: Division, Position
9 of 14
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
11.10
Defining Responsibilities
Navigate to Application Administration Responsibilities
1. Create responsibility
2. Associate views to responsibility
10 of 14
Predefined Responsibilities
There are many predefined responsibilities provided as part of the Siebel seed data.
Siebel 7 Essentials
11.11
Defining Employees
Navigate to User Administration Employees to define employees
Required fields
Associate one or more positions
Associate one or more responsibilities
Specify additional data for the employee
11 of 14
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
11.12
Position and Responsibility

There is no relationship between position and responsibility Employees are assigned:
One or more positions One or more responsibilities
Division
Responsibility
Positions
Sales Manager All Opportunities My Teams Accounts All Accounts
Views
12 of 14
Reference
Siebel Applications Administration Guide
Siebel 7 Essentials
11.13
Summary
Define your companys organizational hierarchy in the Siebel application
13 of 14
11
11.14
Lab
Create the ABC organization hierarchy
14 of 14
Siebel 7 Essentials
Authenticating Users
12.1
12
Module 12: Authenticating Users
Siebel 7 Essentials
12.2
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
2 of 21
Siebel 7 Essentials
12.3
Authentication and Access

Authentication:
Determines and validates the users identity Is controlled inside or outside of the Siebel application
12
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
3 of 21
Reference
Siebel Authentication and Access Control Administration Guide
Siebel 7 Essentials
12.4
Business Challenge: Validating Users

How are users identified and validated?
Employees
Customers
Validation
Siebel Applications
Partners
4 of 21
Siebel 7 Essentials
12.5
Business Solution: Authentication

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
12
5 of 21
Reference
Siebel Authentication and Access Control Administration Guide
Siebel 7 Essentials
12.6
Siebel Authentication Manager

Runs within the Siebel object manager Verifies credentials Establishes connection to Siebel database
6 of 21
Siebel 7 Essentials
12.7
Two Types of Authentication

Internal authentication:
Verifies against the relational database (RDBMS) and Siebel application
Also known as database authentication
12
External authentication:
Uses an external file (or directory) and security adapter to authenticate users
7 of 21
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.
Siebel 7 Essentials
12.8
Internal Authentication
Requires a database (RDBMS) login and password for each user Is the default for Siebel applications Authenticates users accessing one or more Siebel applications
Browser
Web Server SWSE Credentials
1. User provides name and password
2. Password may be encrypted to prevent direct database access
Siebel Object Manager Encrypt password Connect using DB account
3. Connect to database
Siebel Database
Module 12: Authenticating Users 8 of 21
Accessing Multiple Siebel Applications
For example, employees may need access to Siebel Sales and Siebel Field service, and these applications use the same Siebel database.
Siebel 7 Essentials
12.9
Example of Internal Authentication

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
12
9 of 21
Creating Database Accounts
The grantusr.sql script is provided as part of Siebel seed data. Modify this script accordingly to create database accounts for your users.
Siebel 7 Essentials
12.10
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
10 of 21
Siebel 7 Essentials
12.11
External Authentication
Browser
12
Web Server SWSE Credentials 1. User provides information
Uses an external directory containing user credential and administrative information Allows for centralized management of user authentication across Siebel and non-Siebel applications
2. Verify credentials Authentication Service Directory
Siebel Object Manager
Security adapter
Login
Connect using DB account 4. Connect to database
Retrieve DB account and roles
Siebel Database
3. Roles applied to user as Siebel responsibilities
11 of 21
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.
Siebel 7 Essentials
12.12
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
12 of 21
Supported LDAP Directories
Refer to Siebel System Requirements and Supported Platforms for information on supported LDAP directories.
Siebel 7 Essentials
12.13
Example of External Authentication

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
12
2. Update system preferences 3. Activate user registration workflows
13 of 21
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
Siebel 7 Essentials
12.14
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
14 of 21
Siebel 7 Essentials
12.15
Benefits of External Authentication

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
12
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
15 of 21
Siebel 7 Essentials
12.16
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 to self-register

Click here for forgotten password
16 of 21
Siebel 7 Essentials
12.17
Web Single Sign On (Web SSO)

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
12
Authentication occurs at Web server level, not at application level

Credential collection and verification is external to Siebel applications
17 of 21
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 Applications
With Web SSO, users are given access to the specific applications to which they are entitled.
Siebel 7 Essentials
12.18
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 applications
Specify same parameters as in eapps.cfg
18 of 21
Reference
Siebel Web Client Administration Guide Siebel Authentication and Access Control Administration Guide
SingleSignon TrustToken
The Siebel Web Engine will operate in SSO mode when set to TRUE. 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.
Siebel 7 Essentials
12.19
Guidelines for Using Authentication

Desired Deployment or Functionality Requires no additional infrastructure components Offers centralized store for user credentials and roles Limits number of database accounts on RDBMS Supports dynamic user registration Supports Web SSO Database Authentication Security Adapter Web SSO
12
19 of 21
Siebel 7 Essentials
12.20
Summary
Describe the difference between authentication and Access Control Describe internal and external authentication and how each works in Siebel eBusiness applications
20 of 21
Siebel 7 Essentials
12.21
Lab
Examine the results of internal (database) authentication Create a database account for a user
12
21 of 21
Siebel 7 Essentials
12.22
Siebel 7 Essentials
Understanding Object Definitions Behind a Siebel Application
13.1
13
Module 13: Understanding Object Definitions Behind a Siebel Application
Siebel 7 Essentials
13.2
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
2 of 22
Siebel 7 Essentials
13.3
Siebel Applications
Consist of:
A reusable execution engine 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
13
3 of 22
Siebel 7 Essentials
13.4
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
4 of 22
Siebel 7 Essentials
13.5
Repository File Contains object definitions that specify:

Presentation of data Business logic Data storage
UI object definitions Business object definitions
Contact
13
Account Account
Opportunity
Product
Data object definitions
5 of 22
Reference
Siebel Tools Reference
Siebel 7 Essentials
13.6
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
Table S_PROD_INT
NAME PART_NUM VERSION
Columns
6 of 22
Siebel 7 Essentials
13.7
Business Object Definitions

Business object definitions specify the business logic for the application Two principle business object definitions
Business component Business object
13
Business object
Business component
7 of 22
Siebel 7 Essentials
13.8
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 component Internal Product
Name Part # Version
Fields
Base table
S_PROD_INT
NAME PART_NUM VERSION
Columns
8 of 22
Siebel 7 Essentials
13.9
Business Component Continued

Can include data from additional related tables
Some fields map to columns in these related tables
Business component Internal Product
Name Vendor Location Cost
13
Fields
NAME
LOC
STD_PRI_UNIT
Columns
S_PROD_INT Base table
S_ORG_EXT Additional table
S_PRI_LST_ITEM Additional table
Represents a logical grouping of data from one or more tables
9 of 22
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.
Siebel 7 Essentials
13.10
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 object (BO)
Account
Account Master BC provides focus for BO
Business component (BC)
Quote
Product
Contact
10 of 22
Business Object
The name of the business object is, by convention, the name of the master or driving business component.
Siebel 7 Essentials
13.11
Business Component Reuse

A business component can be:
Defined once in terms of a logical collection of columns from one or more tables Then used in many different business object contexts
Account
Account Contact BC appears as master in Contact BO
13
Contact
Contact Contact
Quote
Product
Contact BC appears as child in Account BO
Quote
Product
Account
11 of 22
Siebel 7 Essentials
13.12
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
12 of 22
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.
Siebel 7 Essentials
13.13
Applet Object Definition

Specifies a list or form that occupies a portion of a Siebel application window References one business component whose data can be viewed and edited through the list or form
13
Business component
Contact
First Name Job Title Email Address
13 of 22
Siebel 7 Essentials
13.14
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 component
Contact
First Name Job Title Email Address
14 of 22
Siebel 7 Essentials
13.15
View Object Definition

Specifies a view in a Siebel application References one business object Consists of multiple applet object definitions
Each applet must reference a business component in that business object
13
Account
Account
Quote
Product
Contact
15 of 22
Siebel 7 Essentials
13.16
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
16 of 22
Siebel 7 Essentials
13.17
Application Object Definition

Specifies a particular collection of screens available in a Siebel application Consists of multiple screen object definitions
13
Application
17 of 22
Siebel 7 Essentials
13.18
Major Object Definitions

Are related to each other
List Column or Control Applet View Screen Application
Field
Business Component
Business Object
Column
Table
1 or more contained in References
18 of 22
Siebel 7 Essentials
13.19
Object Definitions
Are grouped into three layers with different subject matters and purposes Reference definitions in the next lower layer and are insulated from those in lower layers
List Column or Control
13
Applet
View
Screen
Application UI Layer; defines content of the UI
Field
Business Component
Business Object
Business objects layer; captures the business logic
Column
Table
Data objects layer; provides a logical view of the underlying database
19 of 22
Siebel 7 Essentials
13.20
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 UI Object Definitions Business Object Definitions Data Object Definitions
Modified using HTML editor
Modified using Siebel Tools
20 of 22
Siebel 7 Essentials
13.21
Summary
Describe the major types of object definitions Describe the relationships between them
13
21 of 22
Siebel 7 Essentials
13.22
Lab
Examine object definitions that support the Call Center application and the relationships between them
22 of 22
Siebel 7 Essentials
Using Siebel Tools to Examine Object Definitions
14.1
14
Module 14: Using Siebel Tools to Examine Object Definitions
Siebel 7 Essentials
14.2
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
2 of 19
Siebel 7 Essentials
14.3
Object Definitions
Are data constructs that define elements of the:
User interface Business logic Data storage
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 Repository Data
14
Tools Application
Application Object Manager
Tools output is input for object manager
.srf
Configured Application
3 of 19
Reference
Siebel 7 Essentials
14.4
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
Name: Title: Inactive:
View
Name: Title: Account List View My Accounts
Inactive: FALSE
4 of 19
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.
Siebel 7 Essentials
14.5
Object Definition Properties

Describe characteristics of the object definition Have the following value types
User-defined names Numerical values Boolean values (TRUE and FALSE) Siebel-defined constants References to the names of other object definitions
Object definition
14
Field
Name: Text Length: Read Only : Type: Column: Account Products 500 FALSE DTYPE_TEXT PROD
5 of 19
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.
Siebel 7 Essentials
14.6
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 Explorer
Object List Editor

6 of 19
Siebel 7 Essentials
14.7
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 Tool bar icons exist for common user operations
Record Navigation Query Sort Menu invoked by right-clicking on object definition
14
7 of 19
Siebel 7 Essentials
14.8
Object Explorer
Displays by default a small set of the most commonly used object types
Use View Options and select the Object Explorer tab to add or remove object types from the Object Explorer
8 of 19
Siebel 7 Essentials
14.9
Properties Window
Displays the object definition selected in the Object List Editor
Open by selecting View Windows Properties 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
9 of 19
Siebel 7 Essentials
14.10
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
10 of 19
Siebel 7 Essentials
14.11
Viewing Parent/Child Object Definitions

Select object types and definitions alternately to examine child object definitions
Use Types tab 1. Expand parent object type (Applet) in OE 2. Select parent object definition in OBLE
14
3. Select desired child object type (Control) in OE
4. View child object definitions for selected parent definition in lower pane of OBLE
11 of 19
Siebel 7 Essentials
14.12
Additional Navigation Techniques

Use these techniques to navigate in the Tools application
Drill down on hyperlinks Forward/Back button Bookmarks
12 of 19
Siebel 7 Essentials
14.13
Using Drilldown
Drill down on a hyperlink to navigate to that object definition
Applet to business component Business component to table
Underlined in blue
14
13 of 19
Siebel 7 Essentials
14.14
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
14 of 19
Siebel 7 Essentials
14.15
Using Bookmarks
Use bookmarks to navigate directly to a specific object definition
Add a new bookmark
Display or hide bookmark window
14
Select the desired bookmark from the Bookmarks window

Module 14: Using Siebel Tools to Examine Object Definitions 15 of 19
Bookmarks
Bookmarks can serve very effectively as predefined queries.
Siebel 7 Essentials
14.16
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 in OE
Parent object definition displayed

16 of 19
Siebel 7 Essentials
14.17
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

Module 14: Using Siebel Tools to Examine Object Definitions 17 of 19
Siebel 7 Essentials
14.18
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
18 of 19
Siebel 7 Essentials
14.19
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
Note the convention used in the labs
Parent record in the OBLE Child record in the OBLE
14
Select Business Component > Account > Field > Account Role
Parent object type in the OE Child object type in the OE
19 of 19
Siebel 7 Essentials
14.20
Siebel 7 Essentials
Understanding the Siebel Data Model
15.1
Module 15: Understanding the Siebel Data Model
15
Siebel 7 Essentials
15.2
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
2 of 29
Siebel 7 Essentials
15.3
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

Defines the business logic Field Business Component Business Object
15
Defines how data storage is organized (makes up the Data Model)
Column
Table
3 of 29
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.
Siebel 7 Essentials
15.4
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
4 of 29
Siebel 7 Essentials
15.5
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
Columns (store single values only)
NAME
PART_NUM
UOM_CD
5 of 29
Siebel 7 Essentials
15.6
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)
6 of 29
Siebel 7 Essentials
15.7
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
7 of 29
Siebel 7 Essentials
15.8
Tables
Over 2000 tables in the database Three major types: Data, Interface, and Repository
Data S_PROD_INT
Interface EIM_PROD_INT
ROW_ID NAME PART_NUM UOM_CD
Repository S_TABLE
DESC_TEXT ALIAS ROW_ID NAME TYPE
8 of 29
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.
Siebel 7 Essentials
15.9
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
Enterprise Integration Manager for bulk importing and exporting of data Assignment Manager for automatic assignment of newly created records
15
Have names prefixed with S_ Are documented in the Siebel Data Model Reference
Module 15: Understanding the Siebel Data Model 9 of 29
Siebel 7 Essentials
15.10
Prominent Data Tables

Prominent tables storing data for the major business entities
S_PROD_INT
Internal Product
S_SRV_REQ
OWNER_EMP_ID ROW_ID SR_NUM DESC_TEXT RESOLUTION_CD
Service Request
Contact S_CONTACT
MID_NAME ROW_ID LAST_NAME FST_NAME
S_OPTY
ROW_ID BDGT_AMT NAME
Opportunity
PROG_NAME STG_NAME
10 of 29
Siebel 7 Essentials
15.11
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
11 of 29
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
Siebel 7 Essentials
15.12
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
12 of 29
Populating the Repository Tables
The repository tables are populated by the imprep.ksh script during the database server installation.
Siebel 7 Essentials
15.13
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
13 of 29
Siebel 7 Essentials
15.14
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 all new records Can NULL be stored in column? Non-null value required when importing data Identifies type and size of data
14 of 29
Siebel 7 Essentials
15.15
System Columns
Exist for all tables to store system data Are maintained by Siebel applications and tasks
15
Can be viewed from Help About Record
15 of 29
Siebel 7 Essentials
15.16
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
16 of 29
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.
Siebel 7 Essentials
15.17
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 _U: index based on a user key
15
Sequence affects the sort order in business components

Siebel 7 Essentials
15.18
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 S_PROD_LN
ROW_ID NAME DESC_TEXT
Asset S_PROD_INT
UOM_CD ROW_ID NAME PART_NUM
S_ASSET
ROW_ID ASSET_NUM MFGD_DT SERIAL_NUM
M:M relationship
1:M relationship
18 of 29
Siebel 7 Essentials
15.19
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
19 of 29
Siebel 7 Essentials
15.20
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
20 of 29
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.
Siebel 7 Essentials
15.21
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

Siebel 7 Essentials
15.22
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
NAME DESC_TEXT ROW_ID
S_PROD_INT
S_PROD_LN_PROD
PROD_ID ROW_ID PROD_LN_ID
22 of 29
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.
Siebel 7 Essentials
15.23
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.
Siebel 7 Essentials
15.24
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
ROW_ID PAR_ROW_ID ATTRIB_39
Extension table Stores the Stock Level field
24 of 29
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 Tables
A row in an extension table is created only if there is data to store in one of 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.
Siebel 7 Essentials
15.25
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
25 of 29
Siebel 7 Essentials
15.26
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
26 of 29
Siebel 7 Essentials
15.27
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
27 of 29
Siebel 7 Essentials
15.28
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
28 of 29
Siebel 7 Essentials
15.29
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
29 of 29
Siebel 7 Essentials
15.30
Siebel 7 Essentials
The Siebel Data Model: Party Business Components
16.1
Module 16: The Siebel Data Model: Party Business Components
16
Siebel 7 Essentials
16.2
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
2 of 22
Siebel 7 Essentials
16.3
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 Employee User Partner Access Group User List Account Position Division Organization
16
Person-related entities
Grouping for access control
Organizationrelated entities
3 of 22
Reference
Siebel 7 Essentials
16.4
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
4 of 22
Siebel 7 Essentials
16.5
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
5 of 22
Siebel 7 Essentials
16.6
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
ROW_ID FST_NAME LAST_NAME MID_NAME
S_USER
ROW_ID LOGIN PASSWORD
S_EMP_PER
HIRE_DT ROW_ID EXP_APPR_LMT
Stores majority of person-related data
Logical extension table to store user specific data
Logical extension table to store employee-specific data
6 of 22
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.
Siebel 7 Essentials
16.7
Person-Related Business Components Continued

Multiple business components use these tables
Consumer
Last Name Work Phone #
Employee
Last Name Login Name Hire Date
S_CONTACT
ROW_ID FST_NAME WORK_PH_NUM LAST_NAME MID_NAME
S_USER
ROW_ID LOGIN PASSWORD
S_EMP_PER
HIRE_DT ROW_ID EXP_APPR_LMT
7 of 22
16
Siebel 7 Essentials
16.8
Relationships for Responsibility

User-Responsibility (M:M) relationship uses the S_PER_RESP intersection table
Any user can be granted a responsibility
S_CONTACT
LAST_NAME MID_NAME ROW_ID FST_NAME
S_RESP
ROW_ID NAME DESC_TEXT BU_ID
S_PER_RESP
PER_ID ROW_ID RESP_ID
Stores responsibilities
8 of 22
Siebel 7 Essentials
16.9
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
9 of 22
Siebel 7 Essentials
16.10
Organization-Related Business Components

Store their main data in S_ORG_EXT May store additional data in S_BU
S_ORG_EXT
ROW_ID LOC PRTNR_FLG NAME INT_ORG_FLG
S_BU
ROW_ID NAME BU_FLG
=Y for Internal Division or Organization
Logical extension table to store organization name =Y for Channel Partner
10 of 22
Siebel 7 Essentials
16.11
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
ROW_ID LOC NAME INT_ORG_FLG
S_BU
ROW_ID BU_FLG
11 of 22
NAME
16
Siebel 7 Essentials
16.12
S_BU Table
Permits indexing on Organization name Supports organizational visibility
S_ORG_EXT
ROW_ID NAME LOC INT_ORG_FLG
S_BU
ROW_ID BU_FLG
12 of 22
Part of S_BU_U1 index
NAME
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.
Siebel 7 Essentials
16.13
Single-Organization Visibility
Is implemented by the BU_ID foreign key column in the table for a single-organization business component
Example of a singleorganization table S_CONTACT
LAST_NAME MID_NAME ROW_ID FST_NAME BU_ID
S_BU
ROW_ID BU_FLG NAME
16
13 of 22
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.
Siebel 7 Essentials
16.14
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
ROW_ID PRI_LST_CD BU_ID NAME EFF_START_DT
Example of a multipleorganization table
S_BU
ROW_ID BU_FLG NAME
S_PRI_LST_BU
ROW_ID PRI_LST_ID BU_ID
14 of 22
Multi-Org Business Components
Such business components have records that can be assigned to one or more organizations. Some examples are accounts, opportunities, and products.
Siebel 7 Essentials
16.15
Party Business Components

Consist of business components that represent people and organizational units
Account Contact User Organization Employee Position Household And so forth
Reference the S_PARTY table
16
15 of 22
Party
A way to think of party is that it is an abstraction of the business components that own records.
Siebel 7 Essentials
16.16
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
ROW_ID NAME PARTY_TYPE_CD PARTY_UID
S_CONTACT S_ORG_EXT
ROW_ID NAME LOC INT_ORG_FLG PAR_ROW_ID ROW_ID FST_NAME PAR_ROW_ID LAST_NAME MID_NAME
16 of 22
PARTY_TYPE_CD
The following are examples of the party type: organization, household,person,position, user list, and access group.
Siebel 7 Essentials
16.17
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
17 of 22
16
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.
Siebel 7 Essentials
16.18
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
18 of 22
Siebel 7 Essentials
16.19
S_PARTY Overview
S_PARTY and its extension tables are used to store data for many business components
S_PARTY
PARTY_UID NAME ROW_ID PARTY_TYPE_CD
Person-related tables S_CONTACT S_ORG_EXT S_POSTN S_USER S_BU Organization-related tables S_EMP_PER
16
Sample of S_PARTY extension tables

Module 16: The Siebel Data Model: Party Business Components 19 of 22
Siebel 7 Essentials
16.20
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
20 of 22
Siebel 7 Essentials
16.21
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
21 of 22
Siebel 7 Essentials
16.22
Lab
Examine how Access Control business components store data in the person and organization tables Examine how business components reference the S_PARTY table
22 of 22
Siebel 7 Essentials
The Configuration Process
17.1
Module 17: The Configuration Process
17
Siebel 7 Essentials
17.2
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
2 of 25
Siebel 7 Essentials
17.3
Siebel Applications
Siebel standard applications include a defined set of screens, views, lists and forms, and their associated templates
17
Module 17: The Configuration Process 3 of 25
Reference
Siebel 7 Essentials
17.4
Tailoring the Logical User Interface

Developers tailor the standard Siebel screens, views, lists, forms, and templates to better support users business needs
4 of 25
Siebel 7 Essentials
17.5
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 7 Essentials
17.6
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
6 of 25
Siebel 7 Essentials
17.7
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
7 of 25
Siebel 7 Essentials
17.8
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 S_CONTACT
LAST_NAME MID_NAME ROW_ID FST_NAME
S_CONTACT_X
ROW_ID
MID_NAME MID_NAME FST_NAME FST_NAME LAST_NAME LAST_NAME ROW_ID ROW_ID

8 of 25
Siebel 7 Essentials
17.9
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
Tools Application
Application Object Manager
Tools output is input for object manager
.srf
Configured Application
17
Siebel 7 Essentials
17.10
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
10 of 25
Siebel 7 Essentials
17.11
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
Siebel 7 Essentials
17.12
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
Server Machine Developer Workstation Developer Workstation Developer Workstation
12 of 25
Siebel 7 Essentials
17.13
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
Server Machine Master Repository Developer Workstation Local Repository
17
Siebel 7 Essentials
17.14
Set Up a Developer
To set up a developer as a configurator:
Install appropriate server and client software (as in Module 6) Install and verify the Tools client Create the developer Create a database user login Generate the local database template Extract the local database Initialize the local database Populate the local database
Special type of Siebel client
Tools Client
Gateway Server
ODBC
Database Server
14 of 25
Siebel 7 Essentials
17.15
Install Tools Client

Use the seatools installation program to install the Tools program and set up ODBC data sources Example:
Tools Client
Destination Directory: Siebel Remote Server: File System: Database Machine Name: Database/Tablespace: C:\sea701\tools SERVER01 HQ\SVR2\c:\siebfile SERVER02 siebeldb
SSD Local Db c:sea701/tools SSD c:/sea701/tools
D1
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. The name of the server on which the database software is installed.
SERVER02
siebeldb
The default name of the database created in the pre-installation steps, that will contain the Siebel tables.
Siebel 7 Essentials
17.16
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
16 of 25
Siebel 7 Essentials
17.17
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
Siebel 7 Essentials
17.18
Create a Database User Login

Create a corresponding database login using RDBMS tools and the grantusr.sql script as a template Example:
18 of 25
Reference
Applications Administration Guide
Siebel 7 Essentials
17.19
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
Reference
Siebel 7 Essentials
17.20
Extract the Local Database

Run the Database Extract server task to extract user data
20 of 25
Reference
Siebel 7 Essentials
17.21
Initialize the Local Database

Synchronize from the Tools client to create the local database (sse_data.dbf) and populate it with user data
17
Reference
Siebel 7 Essentials
17.22
Populate the Local Database

Use Siebel Tools to copy repository data from the server database to the local database
Tools Client Local Database
Server Database
22 of 25
Reference
Applications Administration Guide
Siebel 7 Essentials
17.23
Additional Developers
For each additional developer
1. 2. 3. 4. 5. Create the developer Create a database user login Extract the local database Initialize the local database Populate the local database
Developer Workstation Developer Workstation Developer Workstation
Server Machine
Master
Local
Local
Local
23 of 25
17
Siebel 7 Essentials
17.24
Summary
Explain the process of configuring a Siebel application List the critical elements of the Siebel configuration strategy Set up the Siebel developer environment
24 of 25
Siebel 7 Essentials
17.25
Lab
Set up an employee as a developer Extract a local database for the developer Populate the developers local database with repository data
17
Siebel 7 Essentials
17.26
Siebel 7 Essentials
Managing Object Definitions
18.1
Module 18: Managing Object Definitions
18
Siebel 7 Essentials
18.2
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
2 of 21
Siebel 7 Essentials
18.3
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
Admin
Contact User List Applet Contact User Creation View
Client
Client Parent Node Node List Applet
Product
Component Product Equivalent Product Internal Product Internal Product Attachment
3 of 21
18
Reference
Siebel 7 Essentials
18.4
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
4 of 21
Siebel 7 Essentials
18.5
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
5 of 21
18
Siebel 7 Essentials
18.6
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
6 of 21
Siebel 7 Essentials
18.7
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 Workstation
Master
Local
7 of 21
18
Siebel 7 Essentials
18.8
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
Check In
Local
8 of 21
Siebel 7 Essentials
18.9
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
9 of 21
18
Siebel 7 Essentials
18.10
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
10 of 21
Siebel 7 Essentials
18.11
Check Out Continued

Use Check Out to copy projects from the server to the local repository
11 of 21
18
Siebel 7 Essentials
18.12
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
12 of 21
Siebel 7 Essentials
18.13
Check In Continued
Use Check In to copy projects from the local to the server repository
13 of 21
18
Siebel 7 Essentials
18.14
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
14 of 21
Siebel 7 Essentials
18.15
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
15 of 21
18
Siebel 7 Essentials
18.16
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
16 of 21
Siebel 7 Essentials
18.17
Locking Projects
You can directly lock and unlock projects in the current repository (local or server)
Use Tools Lock Project
Set Locked property directly
17 of 21
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).
Siebel 7 Essentials
18.18
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
18 of 21
Siebel 7 Essentials
18.19
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
19 of 21
18
Siebel 7 Essentials
18.20
Summary
Explain the role of projects Manage object definitions using:
Check Out Check In Lock projects locally
20 of 21
Siebel 7 Essentials
18.21
Lab
Explore how projects work in Siebel Tools Check out a project from the server
21 of 21
18
Siebel 7 Essentials
18.22
Siebel 7 Essentials

Siebel 7 Essentials Student Guide Vol1-1

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Siebel 7 Essentials Student Guide Vol1-1

Încărcat de

Drepturi de autor:

Formate disponibile

Siebel Systems, Inc.

Re: Training Materials Siebel Systems Confidential and Proprietary Information

Copyright 2001 Siebel Systems, Inc.

Siebel Systems, Inc.

Technical Training from Siebel University

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

Siebel End User Education

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

ii COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Siebel Systems, Inc.

iv COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Siebel Systems, Inc.

Siebel 7 Essentials Training

Siebel Technical Training Siebel 7 Essentials

Module i: Siebel 7 Essentials Training

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Siebel 7 Essentials Training

Module i: Siebel 7 Essentials Training

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Siebel 7 Essentials Training

Module i: Siebel 7 Essentials Training

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Siebel 7 Essentials Training

Introductions and Expectations

What is your prior experience?

How do you expect to benefit from this course?

Module i: Siebel 7 Essentials Training

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Siebel 7 Essentials Training

Training Site Information

Meals and refreshments

Module i: Siebel 7 Essentials Training

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Siebel 7 Essentials Training

Module i: Siebel 7 Essentials Training

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Siebel 7 Essentials Training

Module i: Siebel 7 Essentials Training

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Siebel 7 Essentials Training

Module i: Siebel 7 Essentials Training

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Siebel 7 Essentials Training

Module i: Siebel 7 Essentials Training

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Siebel 7 Essentials Training

Overview of Course Flow

7. Business Process Automation

Module i: Siebel 7 Essentials Training

Siebel Systems, Inc.

COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED

Siebel 7 Essentials Training

Architecture and Installation

Module i: Siebel 7 Essentials Training