Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
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.
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.
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
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
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
i.1
1 of 17
Siebel 7 Essentials
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
4 of 17
Siebel 7 Essentials
i.5
Telephones
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
5. Configuration
6. Data Loads
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
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
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
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
1.1
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
2 of 25
Siebel 7 Essentials
1.3
Employee Applications Siebel Call Center Siebel Handheld Siebel Service Siebel Wireless Siebel Sales Siebel Voice Siebel Field Service Partner Applications Siebel eChannel
Siebel 7 Essentials
1.4
4 of 25
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
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
14 of 25
Siebel 7 Essentials
1.15
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
Personalized content
16 of 25
Reference
Siebel 7 Essentials
1.17
17 of 25
Reference
Siebel 7 Essentials
1.18
Reference
Siebel 7 Essentials
1.19
19 of 25
Reference
Siebel 7 Essentials
1.20
Company news
Recommended items
20 of 25
Reference
Siebel 7 Essentials
1.21
21 of 25
Siebel 7 Essentials
1.22
Siebel Database
22 of 25
Siebel 7 Essentials
1.23
23 of 25
Siebel 7 Essentials
1.24
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
2.1
2
Module 2: Using the Siebel Client
Siebel 7 Essentials
2.2
Module Objectives
After completing this module you will be able to:
Use the Siebel user interface (UI)
2 of 25
Siebel 7 Essentials
2.3
Home Page
Logging in to a Siebel application displays a home page
Application-level menu
3 of 25
Home Page
Siebel 7 Essentials
2.4
Navigating the UI
Clicking on different UI elements navigates to different data
Screen tabs Show drop-down
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
Siebel 7 Essentials
2.5
List
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
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
7 of 25
Hyperlinks
Siebel 7 Essentials
2.8
History drop-down
Select from drop-down list to navigate to previous screens and views Current view is at top of list
Thread bar
Current view
8 of 25
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
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
Siebel 7 Essentials
2.11
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
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.
If a record cannot be undone or deleted, the actions will be grayed out and unavailable to the user.
Siebel 7 Essentials
2.13
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
Picklist
Select a single value for a field in a record Select an Account
Type for the account
Select button
Module 2: Using the Siebel Client 14 of 25
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
1. Select New Query 4. Query returns all records matching the criteria 3. Select Run Query
Module 2: Using the Siebel Client 15 of 25
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
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
Module 2: Using the Siebel Client 17 of 25
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
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
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
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
22 of 25
Siebel 7 Essentials
2.23
23 of 25
Siebel 7 Essentials
2.24
Summary
This module showed you how to:
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
3.1
Siebel 7 Essentials
3.2
Module Objectives
After completing this module you will be able to:
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
2 of 17
Siebel 7 Essentials
3.3
Record
List
3 of 17
Record
Siebel 7 Essentials
3.4
Record
Database
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
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
Siebel 7 Essentials
3.6
6 of 17
Siebel 7 Essentials
3.7
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
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 component
Opportunity
Product
Contact
Business component
10 of 17
Siebel 7 Essentials
3.11
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
Account
Opportunity
Product
Contact
Business object
Module 3: Organizing Data Behind the User Interface 12 of 17
Siebel 7 Essentials
3.13
Account
Account Contact list references Contact child business component Contact Record Business object
Module 3: Organizing Data Behind the User Interface 13 of 17
Opportunity
Product
Siebel 7 Essentials
3.14
14 of 17
Siebel 7 Essentials
3.15
Account
Account
3
Contact
Opportunity
Product
15 of 17
Reference
Siebel 7 Essentials
3.16
Summary
This module showed you how to:
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
In the lab you will:
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
4.1
Siebel 7 Essentials
4.2
Module Objectives
After completing this module you will be able to:
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
2 of 23
Siebel 7 Essentials
4.3
Web Server
4
Siebel Servers
3 of 23
Clients
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
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 7 Essentials
4.5
Siebel Clients
Run in a variety of environments
Web browsers, WML devices, and PDAs (Windows CE and Palm)
Browser
Gateway Server
4
Siebel Server Component
5 of 23
Reference
WML
WML (Wireless Markup Language) is intended for use with narrowband devices, including cellular phones and pagers.
Siebel 7 Essentials
4.6
Gateway Server Enterprise Server Enterprise Server Siebel Server Siebel Server Component Object Manager
Workflow Manager File System Manager
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
Web Server Siebel Web Server Extension Image Cache
Gateway Server Enterprise Server Enterprise Server Siebel Server Siebel Server Component Object Manager
Workflow Manager File System Manager
7 of 23
Siebel 7 Essentials
4.8
Stores component definitions and assignments, operational parameters, and connectivity information
Stored in siebns.dat file in shared directory
Web Server Siebel Web Server Extension Image Cache
8 of 23
Gateway Server
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
Enterprise Server Enterprise Server Siebel Server Siebel Server Component Object Manager
Workflow Manager File System 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
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
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
Object Manager Workflow Manager File System Manager
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
Object Manager Workflow Manager File System Manager
Database Server
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
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
Siebel 7 Essentials
4.16
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
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
17 of 23
Siebel 7 Essentials
4.18
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
Siebel Templates
Inbound Outbound
Module 4: Exploring the Siebel Architecture
Siebel Data
18 of 23
Siebel 7 Essentials
4.19
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
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
This module showed you how to:
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
In the lab you will:
Match Siebel architecture components to their descriptions
23 of 23
Siebel 7 Essentials
4.24
Siebel 7 Essentials
5.1
Siebel 7 Essentials
5.2
Module Objectives
After completing this module you will be able to:
Identify the various Siebel clients Identify how each client accesses Siebel Servers and data
2 of 24
Siebel 7 Essentials
5.3
Gateway Server
3 of 24
Reference
Siebel 7 Essentials
5.4
Web
Wireless Web
Handheld
Mobile Web
Dedicated Web
4 of 24
Reference
Siebel 7 Essentials
5.5
Web Server
Dedicated Web
Siebel Servers
Database Server
5
5 of 24
Siebel 7 Essentials
5.6
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
Templates
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
Siebel 7 Essentials
5.10
Used with Object Manager, builds a Siebel application at run time Web Clients
Mobile and Dedicated Web Clients
Templates
10 of 24
Siebel 7 Essentials
5.11
Templates
Siebel 7 Essentials
5.12
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
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
14 of 24
Siebel 7 Essentials
5.15
.swe (SWSE)
Object Manager
5
Module 5: How Clients Access Siebel Data 15 of 24
Siebel 7 Essentials
5.16
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 7 Essentials
5.17
.cfg
.srf
Database Server
5
17 of 24
Siebel 7 Essentials
5.18
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
.cfg
.srf
Object Manager Business Object Business Object Siebel Web Engine Data Manager Siebel Server Siebel Server
5
Module 5: How Clients Access Siebel Data 19 of 24
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
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
Mobile/Handheld Client
.cfg
.srf
Object Manager
Siebel Web Engine Data Manager
.cfg
.srf
.cfg
.srf
Database Server
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
This module showed you how to:
Identify the various Siebel clients Identify how each client accesses Siebel Servers and data
5
Module 5: How Clients Access Siebel Data 23 of 24
Siebel 7 Essentials
5.24
Lab
In the lab you will:
Complete a possible deployment diagram
24 of 24
Siebel 7 Essentials
6.1
Siebel 7 Essentials
6.2
Module Objectives
After completing this module you will be able to:
Install the Siebel Gateway Server, Siebel Server, Enterprise Server, and Database Server to set up your Enterprise Server environment Test server-to-database connectivity
2 of 25
Siebel 7 Essentials
6.3
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 7 Essentials
6.5
5 of 25
Siebel 7 Essentials
6.6
Example:
Web Client
Enterprise Server
G1 S1
Siebel File System
D1
Database Server
W1
6 of 25
D1
G1
S1`
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
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
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
9 of 25
File System
Siebel 7 Essentials
6.10
10 of 25
Installation
The Gateway Server, Enterprise and Siebel Servers, and Siebel Database Server can be installed either separately or simultaneously.
Client Browser
Siebel 7 Essentials
6.11
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
12 of 25
Siebel 7 Essentials
6.13
Enterprise Server
siebel
Siebel Server
S1
S1
C:\siebfile
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
14 of 25
Siebel 7 Essentials
6.15
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
16 of 25
Siebel 7 Essentials
6.17
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
18 of 25
Siebel 7 Essentials
6.19
19 of 25
Siebel 7 Essentials
6.20
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
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
This module showed you how to:
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
In the lab you will:
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
Siebel 7 Essentials
Server Administration
7.2
Module Objectives
After completing this module you will be able to:
Use Server Manager to administer your Siebel Enterprise
2 of 27
Reference
Siebel 7 Essentials
Server Administration
7.3
Server Manager
Is a set of views that allow you to manage your Siebel Enterprise
3 of 27
Siebel 7 Essentials
Server Administration
7.4
4 of 27
Siebel 7 Essentials
Server Administration
7.5
Server Manager then connects to each Siebel Server within the Enterprise
Displays servers for each enterprise supported by the Gateway Server
5 of 27
Siebel 7 Essentials
Server Administration
7.6
6 of 27
Siebel 7 Essentials
Server Administration
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
7 of 27
Siebel 7 Essentials
Server Administration
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
Siebel 7 Essentials
Server Administration
7.9
9 of 27
To execute components on the Siebel Server, the component group to which they belong must be enabled.
Siebel 7 Essentials
Server Administration
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
Reference
Siebel 7 Essentials
Server Administration
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
11 of 27
Siebel 7 Essentials
Server Administration
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
Dynamic
Can be changed for executing tasks and take effect immediately
12 of 27
Siebel 7 Essentials
Server Administration
7.13
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
Server Administration
7.14
14 of 27
Siebel 7 Essentials
Server Administration
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
Run Mode
To determine the run mode for a component, navigate to Server Administration Enterprise Configuration Enterprise Component Groups.
Siebel 7 Essentials
Server Administration
7.16
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
Server Administration
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
17 of 27
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
Server Administration
7.18
Interactive Components
The task runs in response to client requests
No need to manually start
Run Mode
To determine the run mode for a component, navigate to Server Administration Enterprise Configuration Enterprise Component Groups.
Siebel 7 Essentials
Server Administration
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
Server Administration
7.20
Managing a Component
Navigate to Server Administration Servers Server Components to change a server component state
20 of 27
Siebel 7 Essentials
Server Administration
7.21
2. Modify parameters
Module 7: Server Administration
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
Server Administration
7.22
Component alias
Siebel Server
Parameters
22 of 27
Reference
Siebel 7 Essentials
Server Administration
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
Server Administration
7.24
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
Server Administration
7.25
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
Server Administration
7.26
Summary
This module showed you how to:
Use Server Manager to administer your Siebel Enterprise
26 of 27
Siebel 7 Essentials
Server Administration
7.27
Lab
In the lab you will:
Enable server components Synchronize batch components Start a task and view its log Use command-line Server Manager
27 of 27
Siebel 7 Essentials
Server Administration
7.28
Siebel 7 Essentials
8.1
Siebel 7 Essentials
8.2
Module Objectives
After completing this module you will be able to:
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
2 of 14
Reference
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
Customers
Orders
Service Requests
Module 8: Access Control and Views
Opportunities
3 of 14
Siebel 7 Essentials
8.4
4 of 14
Siebel 7 Essentials
8.5
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
7 of 14
Siebel 7 Essentials
8.8
Call Center Manager and Universal Agent responsibilities share a common set of views
8 of 14
Siebel 7 Essentials
8.9
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
11 of 14
Siebel 7 Essentials
8.12
12 of 14
Siebel 7 Essentials
8.13
Summary
This module showed you how to:
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
In the lab you will:
Explore responsibilities and views for different users
14 of 14
Siebel 7 Essentials
9.1
Siebel 7 Essentials
9.2
Module Objectives
After completing this module you will be able to:
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
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
3 of 24
Siebel 7 Essentials
9.4
4 of 24
Siebel 7 Essentials
9.5
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
6 of 24
Siebel 7 Essentials
9.7
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
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
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
12 of 24
Siebel 7 Essentials
9.13
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
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
15 of 24
Siebel 7 Essentials
9.16
Siebel 7 Essentials
9.17
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
18 of 24
Siebel 7 Essentials
9.19
19 of 24
Siebel 7 Essentials
9.20
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
In the My Opportunities view, use the Organization field to assign multiple organizations to a record
21 of 24
Siebel 7 Essentials
9.22
22 of 24
Siebel 7 Essentials
9.23
Summary
This module showed you how to:
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
In the lab you will:
Explore data level Access Control for different users
24 of 24
Siebel 7 Essentials
10.1
10
Siebel 7 Essentials
10.2
Module Objectives
After completing this module you will be able to:
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
2 of 12
Reference
Siebel 7 Essentials
10.3
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
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
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
This module showed you how to:
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
In the lab you will:
Explore different view types
12 of 12
Siebel 7 Essentials
Creating an Organization
11.1
11
Siebel 7 Essentials Siebel Systems, Inc.
COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED
Creating an Organization
11.2
Module Objectives
After completing this module you will be able to:
Define your companys organizational hierarchy in the Siebel application
2 of 14
Siebel 7 Essentials
Creating an Organization
11.3
Organizational Hierarchy
Allows for the definition of organizations, divisions, and positions Use a top-down approach to define the company structure
Organization
Division
Sub-division
Positions
3 of 14
11
Siebel 7 Essentials Siebel Systems, Inc.
COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED
Creating an Organization
11.4
Company structure determines the records and views to which employees have access
4 of 14
Siebel 7 Essentials
Creating an Organization
11.5
11
Siebel 7 Essentials Siebel Systems, Inc.
COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED
Creating an Organization
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
Creating an Organization
11.7
Defining Organizations
Set Organization Flag to make a division an organization
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
Siebel 7 Essentials Siebel Systems, Inc.
COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED
Creating an Organization
11.8
Explorer View
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
Creating an Organization
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
9 of 14
Parent Position
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
Siebel 7 Essentials Siebel Systems, Inc.
COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED
Creating an Organization
11.10
Defining Responsibilities
Navigate to Application Administration Responsibilities
1. Create responsibility
10 of 14
Predefined Responsibilities
There are many predefined responsibilities provided as part of the Siebel seed data.
Siebel 7 Essentials
Creating an Organization
11.11
Defining Employees
Navigate to User Administration Employees to define employees
Required fields
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
Siebel 7 Essentials Siebel Systems, Inc.
COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED
Creating an Organization
11.12
Division
Responsibility
Positions
Views
12 of 14
Reference
Siebel 7 Essentials
Creating an Organization
11.13
Summary
This module showed you how to:
Define your companys organizational hierarchy in the Siebel application
13 of 14
11
Siebel 7 Essentials Siebel Systems, Inc.
COMPANY CONFIDENTIAL AND PROPRIETARY INFORMATION DUPLICATION IS PROHIBITED
Creating an Organization
11.14
Lab
In the lab you will:
Create the ABC organization hierarchy
14 of 14
Siebel 7 Essentials
Authenticating Users
12.1
12
Siebel 7 Essentials
Authenticating Users
12.2
Module Objectives
After completing this module you will be able to:
Describe the difference between authentication and Access Control Describe internal and external authentication and how each works in Siebel eBusiness applications
2 of 21
Siebel 7 Essentials
Authenticating Users
12.3
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 7 Essentials
Authenticating Users
12.4
Employees
Customers
Validation
Siebel Applications
Partners
4 of 21
Siebel 7 Essentials
Authenticating Users
12.5
12
5 of 21
Reference
Siebel 7 Essentials
Authenticating Users
12.6
6 of 21
Siebel 7 Essentials
Authenticating Users
12.7
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
Authenticating Users
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
3. Connect to database
Siebel Database
Module 12: Authenticating Users 8 of 21
For example, employees may need access to Siebel Sales and Siebel Field service, and these applications use the same Siebel database.
Siebel 7 Essentials
Authenticating Users
12.9
12
9 of 21
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
Authenticating Users
12.10
10 of 21
Siebel 7 Essentials
Authenticating Users
12.11
External Authentication
Browser
12
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
Security adapter
Login
Siebel Database
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
Authenticating Users
12.12
12 of 21
Refer to Siebel System Requirements and Supported Platforms for information on supported LDAP directories.
Siebel 7 Essentials
Authenticating Users
12.13
12
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
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
Authenticating Users
12.14
14 of 21
Siebel 7 Essentials
Authenticating Users
12.15
12
15 of 21
Siebel 7 Essentials
Authenticating Users
12.16
16 of 21
Siebel 7 Essentials
Authenticating Users
12.17
12
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.
With Web SSO, users are given access to the specific applications to which they are entitled.
Siebel 7 Essentials
Authenticating Users
12.18
Specify parameters in each eApp section or in [defaults] to apply to all customer applications
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
Authenticating Users
12.19
12
19 of 21
Siebel 7 Essentials
Authenticating Users
12.20
Summary
This module showed you how to:
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
Authenticating Users
12.21
Lab
In the lab you will:
Examine the results of internal (database) authentication Create a database account for a user
12
21 of 21
Siebel 7 Essentials
Authenticating Users
12.22
Siebel 7 Essentials
13.1
13
Siebel 7 Essentials
13.2
Module Objectives
After completing this module you will be able to:
Describe the major types of object definitions Describe the relationships between them
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
13
Account Account
Opportunity
Product
5 of 22
Reference
Siebel 7 Essentials
13.6
Columns
6 of 22
Siebel 7 Essentials
13.7
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
13
Fields
NAME
LOC
STD_PRI_UNIT
Columns
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
Has one business component that serves as the master or driving business component
Business object (BO)
Account
Account Master BC provides focus for BO
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
13
Contact
Contact Contact
Quote
Product
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
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
13
Business component
Contact
First Name Job Title Email Address
13 of 22
Siebel 7 Essentials
13.14
Business component
Contact
First Name Job Title Email Address
14 of 22
Siebel 7 Essentials
13.15
13
Account
Account
Quote
Product
Contact
15 of 22
Siebel 7 Essentials
13.16
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
13
Application
17 of 22
Siebel 7 Essentials
13.18
Field
Business Component
Business Object
Column
Table
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
Field
Business Component
Business Object
Column
Table
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
20 of 22
Siebel 7 Essentials
13.21
Summary
This module showed you how to:
Describe the major types of object definitions Describe the relationships between them
13
21 of 22
Siebel 7 Essentials
13.22
Lab
In the lab you will:
Examine object definitions that support the Call Center application and the relationships between them
22 of 22
Siebel 7 Essentials
14.1
14
Module 14: Using Siebel Tools to Examine Object Definitions
Siebel 7 Essentials
14.2
Module Objectives
After completing this module you will be able to:
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
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
.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
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
Object Explorer
Module 14: Using Siebel Tools to Examine Object Definitions
Siebel 7 Essentials
14.7
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
9 of 19
Siebel 7 Essentials
14.10
10 of 19
Siebel 7 Essentials
14.11
14
4. View child object definitions for selected parent definition in lower pane of OBLE
11 of 19
Siebel 7 Essentials
14.12
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
14 of 19
Siebel 7 Essentials
14.15
Using Bookmarks
Use bookmarks to navigate directly to a specific object definition
Add a new bookmark
14
Bookmarks
Siebel 7 Essentials
14.16
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
Siebel 7 Essentials
14.18
Summary
This module showed you how to:
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
In the lab you will:
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
15.1
15
Siebel 7 Essentials
15.2
Module Objectives
After completing this module you will be able to:
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
2 of 29
Siebel 7 Essentials
15.3
15
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
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
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
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
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
NAME PART_NUM ROW_ID UOM_CD
Interface EIM_PROD_INT
ROW_ID NAME PART_NUM UOM_CD
Repository S_TABLE
DESC_TEXT ALIAS ROW_ID NAME TYPE
8 of 29
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
Siebel 7 Essentials
15.9
Data Tables
Store the user data
Business data Administrative data Seed data Transaction data for mobile users
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
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 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
12 of 29
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
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
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
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
Siebel 7 Essentials
15.18
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
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
ROW_ID NAME PART_NUM UOM_CD
S_ASSET
ROW_ID ASSET_NUM MFGD_DT MID_NAME PROD_ID
20 of 29
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
15
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
ROW_ID NAME PART_NUM UOM_CD
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
15
Intersection table
Module 15: Understanding the Siebel Data Model 23 of 29
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
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
ROW_ID NAME PART_NUM UOM_CD
S_PROD_INT_X
ROW_ID PAR_ROW_ID ATTRIB_39
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.
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
To support multiple business components referencing the S_PARTY table (discussed in next module)
15
25 of 29
Siebel 7 Essentials
15.26
26 of 29
Siebel 7 Essentials
15.27
15
27 of 29
Siebel 7 Essentials
15.28
Summary
This module showed you how to:
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
In the lab you will:
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
16.1
16
Siebel 7 Essentials
16.2
Module Objectives
After completing this module you will be able to:
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
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
16
Person-related entities
Organizationrelated entities
3 of 22
Reference
Siebel 7 Essentials
16.4
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
16
5 of 22
Siebel 7 Essentials
16.6
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
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
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
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
S_ORG_EXT
ROW_ID LOC PRTNR_FLG NAME INT_ORG_FLG
S_BU
ROW_ID NAME BU_FLG
10 of 22
Siebel 7 Essentials
16.11
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
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
S_BU
ROW_ID BU_FLG NAME
S_PRI_LST_BU
ROW_ID PRI_LST_ID BU_ID
14 of 22
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
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
ROW_ID NAME PARTY_TYPE_CD PARTY_UID
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
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
ROW_ID NAME PARTY_TYPE_CD PARTY_UID
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
Siebel 7 Essentials
16.20
20 of 22
Siebel 7 Essentials
16.21
Summary
This module showed you how to:
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
In the lab you will:
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
17.1
17
Siebel 7 Essentials
17.2
Module Objectives
After completing this module you will be able to:
Explain the process of configuring a Siebel application List the critical elements of the Siebel configuration strategy Set up the Siebel developer environment
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
4 of 25
Siebel 7 Essentials
17.5
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
Module 17: The Configuration Process 5 of 25
Siebel 7 Essentials
17.6
Service Request
Contact
Action
Product
6 of 25
Siebel 7 Essentials
17.7
Service Request
Contact
Action
Product
17
7 of 25
Siebel 7 Essentials
17.8
S_CONTACT_X
ROW_ID
Siebel 7 Essentials
17.9
Tools Application
.srf
Configured Application
17
Module 17: The Configuration Process 9 of 25
Siebel 7 Essentials
17.10
Configuration Strategy
Make minimal changes to the standard application
Decreases the possibility of unexpected interactions
10 of 25
Siebel 7 Essentials
17.11
17
Module 17: The Configuration Process 11 of 25
Siebel 7 Essentials
17.12
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
Use Siebel-supplied mechanisms to copy definitions between server and local databases
Server Machine Master Repository Developer Workstation Local Repository
17
Module 17: The Configuration Process 13 of 25
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
D1
17
Module 17: The Configuration Process 15 of 25
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
16 of 25
Siebel 7 Essentials
17.17
17
Module 17: The Configuration Process 17 of 25
Reference
Siebel 7 Essentials
17.18
18 of 25
Reference
Siebel 7 Essentials
17.19
17
Module 17: The Configuration Process 19 of 25
Reference
Siebel 7 Essentials
17.20
20 of 25
Reference
Siebel 7 Essentials
17.21
17
Module 17: The Configuration Process 21 of 25
Reference
Siebel 7 Essentials
17.22
Server Database
22 of 25
Reference
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
Module 17: The Configuration Process
Local
Local
Local
23 of 25
17
Siebel 7 Essentials
17.24
Summary
This module showed you how to:
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
In the lab you will:
Set up an employee as a developer Extract a local database for the developer Populate the developers local database with repository data
17
Module 17: The Configuration Process 25 of 25
Siebel 7 Essentials
17.26
Siebel 7 Essentials
18.1
18
Siebel 7 Essentials
18.2
Module Objectives
After completing this module you will be able to:
Explain the role of projects Manage object definitions using:
Check Out Check In Lock projects locally
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
5 of 21
18
Siebel 7 Essentials
18.6
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
Developer Workstation
Developer Workstation
Master
Module 18: Managing Object Definitions
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)
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
10 of 21
Siebel 7 Essentials
18.11
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
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
14 of 21
Siebel 7 Essentials
18.15
Then check in project to unlock project on both local and server repositories
15 of 21
18
Siebel 7 Essentials
18.16
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
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
Allows developer to make and test modifications locally Prevents developer from checking them in to server repository
Server Machine Developer Workstation Developer Workstation Developer Workstation
Master
Module 18: Managing Object Definitions
Local
18 of 21
Siebel 7 Essentials
18.19
Master
Module 18: Managing Object Definitions
Local
19 of 21
18
Siebel 7 Essentials
18.20
Summary
This module showed you how to:
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
In the lab you will:
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