About Standard 1:M Extension Tables 102 Creating the Appraisals Business Component 102 Creating a Link Between Houses and Appraisals 105 Adding the Appraisals Business Component to a Business Object Create a New Appraisals List Applet 107 Creating the House Detail - Appraisals View 108 Adding the House Detail - Appraisals View to the Houses Screen

0
11
.0
This guide has been updated to reflect product name changes. It was previously published as Developing and Deploying Siebel eBusiness Applications.1
What’s New in This Release
What’s New in Developing and Deploying Siebel Business Applications.7. Version 8. Version 7.
Developing and Deploying Siebel Business Applications Version 8.

What’s New in This Release ■
12
Developing and Deploying Siebel Business Applications Version 8.0
.

each customization topic provides cross-references to more information for those who wish to expand their knowledge. It is not intended to present a solution design or suggest a comprehensive implementation methodology.0
13
. Rather. This chapter includes the following topics: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ Goals and Scope of Developing and Deploying Siebel Business Applications Introducing NREC on page 14 NREC’s Business Objectives on page 14 NREC’s User Profiles on page 15 Siebel Business Functionality on page 15 NREC’s Implementation Strategy on page 16 Introduction to Application Software Testing on page 17 Overview of the Siebel Testing Process on page 20 Project Team on page 22 Sample Project Design Documentation on page 23 NREC’s Business Requirements on page 24 Reviewing NREC’s Design on page 27
The NREC example is a simple example used to highlight particular tasks. requirements.
Developing and Deploying Siebel Business Applications Version 8. If you follow the procedures in this book you will have a functioning implementation (without the data) that has some very typical customizations that are easy to complete.2
Introducing the Business Case
This chapter introduces you to a fictitious company that is used as an example throughout this book. However. and implement Siebel applications for your specific requirements. it highlights particular aspects of NREC’s solution design to present tasks in a real-world context. it does not delve into every conceivable customization you may wish to make. design. This book also presents the basic strategy to take to plan. The goal is to learn by doing. cross-references are supplied for each element of the strategy so you can get more detailed information where necessary. By following how this strategy is applied to NREC. These customizations will give you a taste of what is possible. and the details of the company’s solution design. Again. It summarizes a simple business case giving you a sense of the objectives. you can learn how to apply it to your company.
Goals and Scope of Developing and Deploying Siebel Business Applications
This book presents an actual implementation of Oracle’s Siebel Business Applications at a fictitious company.

S. NREC is a U. business rules within the Siebel application streamline inefficiencies in the current process.
Key Business Processes
NREC’s Business Objectives
Today NREC uses a homegrown solution to manage its pool of houses and buyer leads. Through prenegotiated contracts with partner real estate agencies.
14
Developing and Deploying Siebel Business Applications Version 8. However the company realizes that this is an inadequate approach. NREC records the buyer’s information and. allowing participants access to the key information they need to do their job. It regularly faxes partner real estate agencies with information about available houses and dispatches leads in an ad-hoc manner. rather than handling the leads itself. In addition. These real estate agencies represent buyers.Introducing the Business Case ■ Introducing NREC
Introducing NREC
The fictitious company used as an example in this book is National Real Estate Clearinghouse (NREC). Real estate agents use NREC to find houses that match buyers needs. NREC maintains a database of houses for sale and makes this information available to a nationwide network of partner real estate agencies. see Figure 1. NREC is able to close sales with fewer incurred costs than traditional real estate agencies. NREC has decided to address these problems by implementing a Siebel Business solution. For an illustration of these interactions. Potential buyers call into a toll-free number to inquire about houses. NREC also solicits interest directly from buyers.0
. For example. It acts as an agent for people who are selling houses. buyer leads can be automatically dispatched to partners based on agreed-upon assignment rules. In addition.-based company that participates in the residential real estate industry. which is costing it money and making it difficult to attract new independent real estate agencies to join its distribution network. agents will automatically be notified by email when an opportunity has been assigned to them. This solution is both employee and partner facing. NREC passes them onto one of the agencies in its distribution network.
Figure 1.

Real Estate Agent Manager. Real Estate Agent.
■
■
Siebel Business Functionality
NREC is planning to implement the following functionality to support its business needs. These modules share a common back end. and to track their own opportunities. making sure that everyone always sees the most up-to-date information. Siebel Partner Portal.
NREC’s User Profiles
■ NREC Application Administrators. Real estate agents of the partner agencies log into the NREC Partner Portal site to manage opportunities and contact information. browse houses for sale. ■ ■ ■ ■ ■ ■ ■ ■ ■ Account Management Activity Management Assignment Manager Business Process Designer Contact Management Opportunity Management Partner Management Personalization Product Information
Access Requirements
In analyzing its requirements. NREC determined that it had the following data access needs.0
15
. Managers at partner real estate agencies log into the NREC Partner Portal site to track opportunities and activities for every agent in the agency.
Developing and Deploying Siebel Business Applications Version 8. and track activities related to each opportunity. and activities. contact information. They also log in to see houses for sale. For all examples that show the user interface. while the partner application are based on Siebel Partner Portal.Introducing the Business Case ■ NREC’s User Profiles
The employee applications in NREC’s implementation are based on Siebel Sales and Siebel Partner Manager. use Siebel Partner Portal. It is responsible for adding houses as they become available and adding leads that are then automatically sent to a partner agency. NREC operates the Partner Portal Web site for its partner real estate agencies and their agents. This book assumes that the configuration for the employee applications is proceeding successfully and focuses on the configuration of the partner application. They also perform administration tasks such as managing partner information.

Users synchronize the local database with the server database when necessary. and so on) through a graphical user interface connected to the corporate intranet. Define. The project team refines and documents functional and technical requirements that support the business goals. A phased approach helps NREC minimize risk and realize a return on its investment incrementally. Mobile access. Additionally. read Siebel Installation Guide for Microsoft Windows. The Siebel Web client is an HTML. The project team assembles. assigning responsibilities. ■ The Web client—through which users connect to the Siebel server with their browser—meets the first and second requirements. when needed.
Siebel eRoadmap Methodology
NREC follows Siebel’s eRoadmap Methodology through each one of its implementation phases.
NREC’s Implementation Strategy
NREC has chosen to implement Siebel business applications using a phased approach. but the Web pages are served from the local Siebel application rather than a server.
■
For more information about deploying the Mobile Web client.0
. The mobile Web client provides the same HTML interface as the Web client. Access through corporate intranet. defines the project approach and scope. The Mobile Web client meets the third requirement because agents can log into Siebel Business Applications and work offline in a local database that resides on the agent’s computer.
16
Developing and Deploying Siebel Business Applications Version 8. NREC Administrators and employees need to be able to administer the implementation (creating new users. They must be able to synchronize with the central corporate database.Introducing the Business Case ■ NREC’s Implementation Strategy
■
Access through low-bandwidth Internet connections.
■
■
NREC plans to implement Siebel’s Web client and Mobile Web client to meet the three requirements. Create Prototype. thereby increasing the probability of project success. and implements project management controls. The project team designs a hard-copy mock-up of the solution and uses the discovery stage requirements to develop application screen flows and design layouts. NREC’s partner agents must be able to access data over low-bandwidth connections (such as dial-up connections) without having to install Siebel software on their personal computers. Web interface providing access to Siebel applications through either the Internet or an intranet. and so on) and maintain user data (houses. contacts. opportunities. The stages include the following: ■ ■ ■ Discover. NREC employees need to be able to access and manipulate data on their laptops even without being connected to a corporate database. The Siebel eRoadmap Methodology provides a six-stage framework for implementing Siebel Business Applications. NREC’s users and partners will experience the benefits of the project as early as possible. the project team can take feedback gathered during the early phases and incorporate it into the end solution.

A defect discovered in the requirements definition phase as a requirement gap can be a hundred times less expensive to address than if it is discovered after the application has been deployed. user training. Functional testing.0
17
. The team then focuses on a successful transition from the production pilot to a full rollout. The scenario for the book assumes that a design team has planned out the details and has provided NREC developers with design specifications used in configuration. Higher User Acceptance. The ability of the application to perform reliably is critical in delivering consistent service to the users or customers. technical infrastructure. Performance. User perception of quality is extremely important to the success of a deployment. Sustain. including a user acceptance test of the application using production data. Identifying defects early in the project is a critical factor in reducing the total cost of ownership. the network. The testing strategy and its objectives must be reviewed to identify any inadequacies in planning. extensions. Improved Deployment Quality. Conversely. well-planned and executed testing can deliver significant benefit to a project. Without well-planned testing.Introducing the Business Case ■ Introduction to Application Software Testing
■ ■ ■
Configure.
Introduction to Application Software Testing
Testing is a key component of any application deployment project. The project team first conducts a Production Pilot that field-tests and revises every aspect of the new implementation. Deploy. Test cases must be updated to include testing scenarios that were discovered during testing and were not previously identified. Hardware and software components of the project must also meet a high level of quality. An outage caused by inadequate resources can result in lost business. The project team conducts a full-function test. and stress testing can provide an early assessment of the project to handle the production load and allow IT organizations to plan accordingly. When in production. Validate. The testing process determines the readiness of the application. usability testing. and external interfaces required to support the new implementation.
■
■
Developing and Deploying Siebel Business Applications Version 8. project teams may be forced to make under-informed decisions and expose the business to undue risk. The project team configures the application. reliability. including: ■ Reduced Deployment Cost. Evaluate to identify opportunities for improvement. Research shows that the cost of resolving a defect increases dramatically in later deployment phases. it must be designed to adequately inform deployment decisions. and performance testing can provide insights into deficiencies from the users’ perspective early enough so that these deficiencies can be corrected before releasing the application to the larger user community. and the help desk. Therefore.
■
The tasks covered in this book are primarily in the configuration and deployment stages of the eRoadmap Methodology. a serious defect can result in lost business and affect the success of the project.

Validates that all programs and interfaces external to the Siebel application function correctly. lower user adoption. These testing classifications are used to break down the problem of testing into manageable pieces.
Common Test Definitions
There are several common terms used to describe specific aspects of software testing. Developers test their code against predefined design specifications. Here are some of the common terms that are used throughout this book. Code additions or changes may unintentionally introduce unexpected errors or regressions that did not exist previously. This test is usually performed using an automation tool to simulate user load while measuring resources used. and failure to achieve business returns. Software projects that attempt to save time and money by lowering their initial investment in testing find that the cost of not testing is much greater. A unit test is an isolated test that is often the first feature test that developers perform in their own environment before checking changes into the configuration repository. ■ Integration Testing. Usability Testing.Introducing the Business Case ■ Introduction to Application Software Testing
Inserting testing early and often is a key component to lowering the total cost of ownership. Unit Testing. User interaction with the graphical user interface (GUI) is tested to observe the effectiveness of the GUI when test users attempt to complete common tasks. Functional and performance requirements are verified to make sure there are no user task failures and no prohibitive response times. This must be conducted in an environment that has realistic test data. User Acceptance Test. Stress Testing. or interface may negatively affect the functionality of another module. Insufficient investment in testing may result in higher deployment costs. application. This test identifies the maximum load a given hardware configuration can handle.
■
■
■ ■
■ ■
18
Developing and Deploying Siebel Business Applications Version 8. Users test the complete. Unit testing prevents introducing unstable components (or units) into the larger application. Client and server response times are both measured. Sometimes adding a new module. end-to-end business processes. Performance Testing. Test scenarios usually simulate expected peak loads. Regression tests are executed when a new build or release is available to make sure existing and new features function correctly. Regression Testing.0
.

Figure 2. returns the correct value). These stages (illustrated in Figure 2) are iterative in nature. while minimizing their business risk to promote a successful completion of a Siebel project. The Siebel implementation is composed of activities logically grouped into eight distinct eRoadmap stages to make sure proper project management and control techniques are used during the life cycle of a project. The first stage is the development of a testing strategy by the testing team to define environmental simulation requirements and testing approaches. Tested units are then moved into the testing environment. functional testing begins when prototyping begins and continues throughout the configuration of the Siebel application as developers test each unit they configure. As mentioned earlier. The test team then verifies whether or not the module functions correctly (for example.Introducing the Business Case ■ Introduction to Application Software Testing
Siebel eRoadmap Implementation Methodology
The Siebel eRoadmap implementation methodology accelerates project implementations by focusing on the key strategic and tactical areas that must be addressed to maximize the customer's return on investment. establish priorities. and define and create proper functional and load test scripts. and has the correct interface. has the correct layout (for example. The output of this stage is a comprehensive Test Plan.
Developing and Deploying Siebel Business Applications Version 8. where the appropriate units are combined to form a corresponding module. After validating a module.
Siebel eRoadmap Implementation Methodology
Testing is an end-to-end process that begins when you start to configure the Siebel application. drop-down menus and text fields).0
19
. functional testing continues using business processes and scenarios to verify whether or not all modules work together as required.

Overview of the Siebel Testing Process
Testing processes occur throughout the implementation lifecycle. User Acceptance testing (UAT) consists of testing the Siebel application using the appropriate business owners and end users. and are closely linked to other configuration. Next. Finally. is validation that the Siebel application operates with other applications and interfaces. and operations processes. Each of the seven testing processes described in this book are highlighted in bold in the diagram and are outlined briefly in the following topics: ■ ■ ■ ■ ■ ■ ■ Plan Testing Strategy on page 20 Develop Tests on page 21 Execute Siebel Functional Tests on page 21 Execute Integration Tests on page 21 Execute User Acceptance Tests on page 21 Execute Performance Tests on page 22 Improve Testing on page 22
Plan Testing Strategy
The test planning process makes sure that the testing performed is able to inform the deployment decision process.Introducing the Business Case ■ Overview of the Siebel Testing Process
The next stage of functional testing. middleware. The first step is to establish a benchmark of performance through the completion of a performance test. minimize risk. load balancer.0
. This must be conducted in an environment that has realistic test data. and provide a structure for tracking progress. execute the test over an extended period of time (longevity test) to determine durability of an application as well as capture any defects that become visible over time. Develop a testing strategy early and use effective communications to coordinate among all stakeholders of the project. Without proper planning many customers may perform either too much or too little testing. complete a capacity test by adding users until you reach the number of users expected to use the application over its life. When performing UAT. and middleware). make sure that you have users who are familiar with the existing business processes. and email). The process is designed to identify key project objectives and develop plans based on those objectives. deployment. Performance testing provides an assessment of whether or not an infrastructure performs and scales to your requirements. Test the Siebel application in a test environment that allows the Siebel application to interoperate with the other required applications (such as CTI.
20
Developing and Deploying Siebel Business Applications Version 8. System and Integration testing. This phase requires an image of the full database and all interfaces with the Siebel application (such as CTI.

Do not start development work in earnest until there is agreement that the designed solution meets requirements. Unfortunately. integrates with other applications and infrastructure in your environment. The development team is fully engaged in implementing features. This is typically a very busy time in the project. If a design is flawed from the beginning. Integration testing occurs on the system as a whole to make sure that the Siebel application functions properly when connected to related applications and other infrastructure components. Developers and testers finalize the test cases based on approved technical designs. The written test cases can also serve as blueprints for developing automated test scripts. as well as verifying acceptability to the user community from both the lines of business and the IT organization. the test cases identified during the planning process are developed. the cost to redesign after implementation can be high. middleware. business analysts and developers verify that the design meets the business unit requirements. and business processes to verify that the Siebel application functions correctly. The business analyst who defines the requirements must approve the design.Introducing the Business Case ■ Overview of the Siebel Testing Process
Develop Tests
In the test development process. Design evaluation is the first form of testing. process. Functional tests are performed progressively on components (units). validated earlier. this process is often neglected. Integration with various backend.0
21
. Test cases must be developed with strong participation from the business analyst to understand the details of usage and corner use cases. and the defecttracking process is used to manage quality. In this process. and technology are all preparing for the rollout.
Execute User Acceptance Tests
You perform user acceptance testing on the complete system and focus on validating support for business processes. when people. Preventing design defects or omissions at this stage is more cost effective than addressing them later in the project. and third-party applications must be verified. Test execution and defect resolution are the focus of this process.
Developing and Deploying Siebel Business Applications Version 8. and often the most effective.
Execute Integration Tests
Integration testing verifies that the Siebel application. modules.
Execute Siebel Functional Tests
Functional testing is focused on validating the Siebel Business application components.

Table 1 shows the breakdown of resources needed at each stage in NREC’s implementation project. This must be conducted in an environment that has realistic test data.
Project Team
It is a common practice to have a dynamic project team wherein the number and specialty of people varies according to the stage of the implementation. Both configuration changes and new software releases must be tested to verify that quality is sustained. capacity. Test plans and test cases must be reviewed to determine their effectiveness.
Improve Testing
Testing is not complete when the application is rolled out. The testing process must be evaluated after deployment to identify opportunities for improvement. After the initial deployment. Oracle delivers regular maintenance and major software releases that may need to be applied. In addition. regular configuration changes are delivered in new releases. In this process. Test cases must be updated to include testing scenarios that were discovered during testing and were not previously identified.
NREC’s Project Resources Development Phases
Project Resources
Project Manager Lead Business Analyst Lead Configuration Specialist Lead Architect Configuration Specialist Architect
Definition
X X
Discovery
X X X
Design
X X X
Configuration
X X X
Validation
X X X
Deployment
X X X
X
X X
X X X
X X X
22
Developing and Deploying Siebel Business Applications Version 8. The testing strategy and its objectives must be reviewed to identify any inadequacies in planning.
Table 1.Introducing the Business Case ■ Project Team
Execute Performance Tests
Performance testing validates that the application can meet specified service levels for performance. For example.0
. tests are run on the complete system simulating expected loads and verifying performance. and reliability.

identify any special visibility associated with a view. or the Site Map. Applet designs are reference documents created for each applet. Screen Flow. Customers can submit these documents to Oracle’s Siebel Expert Services for a design review. View design documentation must show what applets are part of the view definition. The business component design template is used to define the properties of business components. Business Object Design. the customer may omit important information and reduce the value of the review. and the properties associated with each field.
■
■
■
■
■
Developing and Deploying Siebel Business Applications Version 8. Applet designs are created after the implementation team decides what entities to track in their Siebel applications.Introducing the Business Case ■ Sample Project Design Documentation
Table 1.
NREC’s Project Resources Development Phases
Project Resources
Training Specialist Documentation Specialist
Definition
Discovery
Design
Configuration
Validation
X X
Deployment
X X
Sample Project Design Documentation
The types of documents listed in this section capture the business requirements and detailed design of NREC’s Siebel solution. a My Team’s View or an All View. The business object design template is used after business components are designed. and multi-value links. the fields that are available on the applet. for example. They comprehensively document an applet’s properties. view tabs (third-level navigation). This indicates the parent and associated child records in the user interface. The types of documents used to capture the design are: ■ Entity Relationship Diagram. Design documentation is a critical part of an implementation. multi-value fields. joins. single-value fields. They define the scope of the solution and document the detailed specifications needed for configuration.0
23
. View Design. If documents are not submitted or the templates are not used to guide them through the documentation process. These documents are outputs of the design stage of the Siebel eRoadmap implementation methodology. This type of diagram (see Figure 3 on page 28) shows the relationships between the major entities that are part of NREC’s solution. It must also document how the user navigates through the views using drilldowns. including the user properties. The screen design template lists the views available from each screen and indicates the default view for each screen. Entities include object definitions such as business components and business objects. They must also include a mock-up or screen shot of the applet. The template groups business components and identifies links between business components. Business Component Design. Applet Design.

Includes test cases based on approved technical designs. Some of these requirements are satisfied using standard Siebel functionality. Gaps require configuration work to modify the standard application to meet the specific requirements. These requirements provide the basis for the tasks covered in later chapters.
■ ■ ■
■
NREC’s Business Requirements
By progressing through the Discovery and Design stages of Siebel’s eRoadmap methodology.
Manage the List of Houses for Sale
NREC requires the ability to manage the list of houses that are currently for sale. and any subreports available.Introducing the Business Case ■ NREC’s Business Requirements
■
Report Design. The report template includes the business component. Workflow Policies. If the gap is more than 25%. such as price. The Testing Strategy Document identifies key project objectives and provides a structure for tracking progress. Assignment Rules. NOTE: As a general rule. The written test cases can also serve as blueprints for developing automated test scripts. Report templates track key information relating to reports. and square feet.0
. keeping a history of appraisals.
24
Developing and Deploying Siebel Business Applications Version 8. Workflow Policy templates gather the key information needed to create workflow rules. it may mean that standard functionality is not being employed. a gap analysis results in less than 25% of the functionality requiring customization. Other requirements cannot be satisfied with standard functionality and are identified as gaps. Testing Strategy Document. This includes storing key characteristics. Test cases must be developed with strong participation from the business analyst to understand the details of usage and corner use cases. Test Cases Document. number of bedrooms. Assignment Manager templates gather the key information needed to create assignment rules. and pulling in any data about renovation history from an external file that is supplied by a third-party vendor. Without proper planning you may perform either too much or too little testing. It is always a good practice to engage Oracle’s Siebel Expert Services for a Configuration Design Review to verify gaps and required configuration changes. Actuate file used. whether the report is dynamic or static. the project team identified and documented the detailed requirements.

Use standard 1:M table to store appraisal data and expose fields in the user interface. such as square feet. and so on. “Personalization. Use Siebel Personalization to filter the list of houses based on the user’s ZIP Code. Configure static pick lists for fields.”
Provide users with predefined values to choose from when entering house features.
Table 2.
Track the features of each house. number of bedrooms. Display renovation information for each house. Read Chapter 17. Create virtual business component to store and display data from flat file. Read “Creating a Virtual Business Component” on page 137. assessor) for each house. Entering and editing records for houses. Read “Configuring the House Detail .Introducing the Business Case ■ NREC’s Business Requirements
Table 2 lists the detailed requirements for the House entity and lists where you can find the tasks in this book that describe how to implement the requirement. Read “Configuring Pick Lists” on page 119. Add columns to S_PROD_IN T to store additional attributes and expose them in the user interface.
Requirements Summary for the House Entity Comment Create a new screen for Houses and add to the Siebel eChannel application. Create new view to display the data.0
25
.
Display houses to partner users based on ZIP Code.
Requirement Track houses for sale. Read “Configuring the House Detail View” on page 87. Track and display previous appraisal information (date. amount. Cross Reference to Task Read “Creating the Houses Screen” on page 97.Appraisals View” on page 101.
Read “Configuring the Internal Product Business Component” on page 92 and “Modify Existing Product Applets to Display NREC Attributes” on page 93.
Developing and Deploying Siebel Business Applications Version 8. Modify Internal Product business component to allow updates and add necessary controls to the Product Form Applet.

Users may choose values for house attributes—square feet. “Assignment Manager.
Requirement For each opportunity.
Read Chapter 15. Send an email notification to partner agents when a new opportunity is assigned to them. “Siebel Business Process Designer.0
. and so on—from a list rather than enter them.Introducing the Business Case ■ NREC’s Business Requirements
Manage Opportunities
NREC needs to give its internal employees as well as its partner agents ability to manage opportunities.
Read “Static Pick Lists” on page 120. Assign opportunities to partner agents based on ZIP Code. Table 3 summarizes the requirements for the opportunity entity.”
26
Developing and Deploying Siebel Business Applications Version 8.
Table 3. Cross Reference to Task Read “Configuring the House Detail View” on page 87. price range.
Requirements Summary for the Opportunities Entity Comment Add columns to the base opportunity table S_OPTY to store the additional attributes. track the house features that the buyer is looking for and buyer characteristics.” Read Chapter 16. Opportunities that come into NREC directly are passed on to a partner agency based on location. Opportunities are recorded for potential buyers and include contact information and information about the type of house the buyer is interested in. Use Assignment Manager to assign opportunities to partner agencies. Add pick lists for each of the fields that need pre-defined values. Use Business Process Designer to automatically send email notification.

The standard Activity management functionality meets NREC requirements well. There are no gaps identified. is particularly useful for describing the design. Constrain the values in the pick applet so it only shows the opportunities for the account associated with the activity. except for the gaps listed in Table 4. depending on the sales stage: Account Detail .
Table 4.0
27
.
Requirements Summary for the Activities Entity Comment Add the opportunity to the Activity List and Form Applets.Contacts (SCW)
Configure dynamic drilldown that implements the conditions described in the business requirement.Introducing the Business Case ■ Reviewing NREC’s Design
Manage Activities
NREC requires the ability to manage activities for each opportunity and contact. Cross Reference to Task “Exposing Fields in the User Interface” on page 82 “Dynamic Pick Lists” on page 122 “Constraining a Pick List” on page 124
Requirement Display the opportunity associated with each activity. An entity relationship diagram.
Reviewing NREC’s Design
The following sections describe NREC’s solution design. such as the one shown in Figure 3. allow users to associate an opportunity to an activity.
Allow users to navigate from the Opportunity Detail view to one of the following views. Create a dynamic pick list that allows users to update the Opportunity field on the Account Form Applet.
“Creating a Dynamic Drilldown” on page 127
Manage Contacts
The standard Contact management functionality meets NREC requirements. You may refer back to Figure 3 often when completing the tasks in subsequent chapters. When entering an activity.Activities (SCW) Account Detail .
Developing and Deploying Siebel Business Applications Version 8.

or M:M) between the major entities of NREC’s solution.
NREC Entity Relationship Diagram
Business Object Layer
This section defines the business objects and business components that represent the entities that make up NREC’s solution. It also shows external data being handled by the virtual business component named House Renovations. For example. The diagram shows the relationships (1:1.0
. house information will be stored in the table called S_PROD_INT.
Figure 3. 1:M. The diagram also shows the tables used to store the data for each entity. ■ ■ ■ ■ ■ Accounts Activities Contacts Internal Products Opportunities
28
Developing and Deploying Siebel Business Applications Version 8.
Business Objects
The NREC implementation plans to use the following business objects.Introducing the Business Case ■ Reviewing NREC’s Design
Data Layer
NREC will implement the entities shown in Figure 3.

Applets
30
Developing and Deploying Siebel Business Applications Version 8. A new screen for Houses will be created for NREC. and Activities screens are standard in the Partner Portal application.0
. There are other screens.Introducing the Business Case ■ Reviewing NREC’s Design
User Interface Layer
At the user interface layer.
Screens. such as Partner Management and Application Administration. The applets are either list applets or form applets. Each view contains one or more applets. Views. Contacts. that will be implemented for NREC. The views that make up each screen are either master-detail views or list-form views. NREC is planning to implement five screens for the Partner Portal.
Figure 4. The Opportunities. NOTE: Figure 4 is a simple representation of part of NREC’s user interface layer.

Using this structure prevents the activities in one environment from interfering with activities in another environment.3
Installing Siebel Applications
This chapter provides you with an overview of a typical installation. seed data. development tools. configuration work in the development environment does not interfere with testing activities in the test environment. The example gives details. A test environment is used to test customizations. The server machine in the development environment is often called the development server. there is a cross reference to where you can find detailed instructions. using NREC as an example. This chapter includes the following topics: ■ ■ ■ ■ Siebel Application Environments The Development Environment on page 32 The Test Environment on page 34 The Production Environment on page 35
This chapter does not provide you with installation instructions. It tells you the different environments to set up to support the implementation process and then describes the hardware and software NREC installed in each environment. but ultimately it consists of hundreds or even thousands of users and live business data. and a small set of data (repository data.
■
■
Developing and Deploying Siebel Business Applications Version 8. The production environment is the live Siebel operational environment. and production. For each product mentioned in the following sections. The test environment is a separate machine (or several machines) with business data but no development tools. patches.0
31
. test. before applying them to the production environment. and sample transactional data). software. The three environments are development. NREC chose to install Siebel products in three separate environments—one environment for each stage in the implementation process. For example. Production.
Siebel Application Environments
Following the recommendation of Oracle. This environment is used to test the application with data that simulates the live production environment. several client machines. ■ Development. such as the machine names on which products were installed. The environment is used for developing customized applications and configurations. A production environment might be very similar to the test environment at the end of testing. and version upgrades. It typically consists of a server machine. Each environment contains hardware. and data. Test.

using actual data for your organization. Do your initial configuration in the development environment.”
32
Developing and Deploying Siebel Business Applications Version 8. testing occurs. on which machine the NREC installed each product.
Software and Data in Each Environment
Each environment corresponds to a stage in the application rollout. one for each developer who configure Siebel applications.
1 2
Development.
3
The subsequent parts of this guide correspond to these three environments and stages.Installing Siebel Applications ■ The Development Environment
Figure 5 shows the typical content of each environment.
The Development Environment
Table 5 lists and describes which products to install in the development environment. NREC installed Siebel Tools on two machines. and where you can find installation instructions. You can have as many developers working simultaneously as you like.0
. After you have thoroughly tested your work in the test environment. as long you set up each developer’s machine according to the instructions in Chapter 5. you migrate the configuration and user data to the production environment and roll out the product to your users. Here you configure business rules and set up the data to simulate the production environment. each part telling you what NREC did at each stage.
Figure 5. Production or Deployment. Copy the configuration data from the development environment to the test environment and continue work there. After the set up is complete. “Setting Up a Developer’s Local Database. Test.

and where you can find installation instructions.
Table 6. and configure.Installing Siebel Applications ■ The Test Environment
Table 5. NOTE: The NREC example assumes a Windows environment. on which machine NREC installed each product. Product
Software Installed in the Development Environment Description A client in which application layers reside on the user’s personal computer.
Software Installed in the Test Environment Machine Name TEST_DB_server Where to Find Installation Instructions Product documentation for the database platform. Siebel database schema Siebel File System Siebel Gateway Server
TEST_DB_server TEST_server TEST_server
Siebel Installation Guide for Microsoft Windows Siebel Installation Guide for Microsoft Windows Siebel Installation Guide for Microsoft Windows
34
Developing and Deploying Siebel Business Applications Version 8. read Siebel System Requirements and Supported Platforms on Siebel SupportWeb. For example IBM DB2 Universal Database. For detailed information on supported software. or SQL Server. Machine Names DEV_tools_A DEV_tools_B Where to Find Installation Instructions Siebel Installation Guide for Microsoft Windows
Siebel Mobile Web Client
Sample Database
DEV_tools_A DEV_tools_B
Siebel Installation Guide for Microsoft Windows and the release notes documentation for your Siebel application.0
.
Microsoft Internet Explorer
DEV_client_A DEV_tools_B
The Test Environment
Table 6 lists which products to install in the test environment. evaluate. go to the Microsoft Web site for installation instructions. Oracle.
Product Installed by NREC Database software. The Web browser used to display the interface for the Siebel Web Client and the Mobile Web Client. If this software is not preinstalled on the client computer. The sample database that you can use to test.

you copy the contents of one of the client machines to your mobile Web Client machines. it installed the server-side software on PROD_server. Also. go to the Microsoft Web site for installation instructions. you distribute a URL to your application to your Web Client users.0
35
. For example.
Product Installed by NREC Siebel Server Siebel Mobile Web Client
Web server such as Microsoft Internet Information Server (IIS) or IBM HTTP Server. during rollout to users. NREC installed the Production software on machines with names starting with PROD. Microsoft Internet Explorer
TEST_client_B (and other client machines from which to test access)
The Production Environment
The software you install in your production environment is typically the same as the software installed in the test environment (shown in Table 6 on page 34). Eventually.Installing Siebel Applications ■ The Production Environment
Table 6.
Software Installed in the Test Environment Machine Name TEST_server TEST_client_A (and other client machines from which to test access) TEST_server Where to Find Installation Instructions Siebel Installation Guide for Microsoft Windows Siebel Installation Guide for Microsoft Windows Product documentation for the Web server. If this software is not preinstalled on the client computer.
Developing and Deploying Siebel Business Applications Version 8.

Siebel object definitions are grouped into the middle three layers. You can modify object definitions and templates. This chapter includes the following topics: ■ ■ ■ ■ ■ Siebel Object Architecture Understanding the Object Definition Sequence on page 39 Using Siebel Tools on page 40 The Configuration Process on page 46 Other Key Tasks for Managing Object Definitions on page 53
Siebel Object Architecture
Siebel Business architecture includes a core set of object definitions that are grouped into different layers depending on the object’s function and characteristics.
Developing and Deploying Siebel Business Applications Version 8. to tailor Siebel applications to meet your organization’s business requirements. For more information about Siebel Tools. You modify Web templates and style sheets using a text editor or a raw code HTML editor. Siebel Web templates occupy the top layer of the architecture. read Using Siebel Tools. The physical RDBMS database occupies the bottom layer. You modify Siebel object definitions using Siebel Tools.4
Getting Started with Siebel Tools
This chapter describes key concepts and common tasks that get you started using Siebel Tools. or create new ones.0
37
. You may refer back to these tasks as you work through the configuration tasks in subsequent chapters. Additionally. there is a core set of HTML templates and style sheets that control the appearance of the user interface (see Figure 6 on page 38).

Getting Started with Siebel Tools ■ Siebel Object Architecture
Objects depend on objects defined in the layers below. For example. This layer contains Siebel Web template files that control the style and structure of the user interface. such as controls and applets. Web templates consist of HTML tags and proprietary Siebel tags. such as buttons and check boxes. At run time the Siebel Web Engine reads the tags. Likewise. and allow users to manipulate data. you can control how data is presented by modifying objects in the user interface layer. Logical User Interface Layer. User interface objects also define the information that associates objects in the repository with the Siebel Web templates.
Siebel Object-Based. Examples of user interface objects include applets. you can change the color and other style characteristics of the user interface by modifying Web templates and style sheets. views. replaces them with interactive Web controls and values based on the UI object definitions. They define the interface presented to the user at run time. but are insulated from each other. without having to modify object definitions.
■
38
Developing and Deploying Siebel Business Applications Version 8.
Figure 6. Siebel tags are embedded within the HTML of template files and serve as placeholders for user interface objects defined in the repository. and controls. and renders the HTML that will be read by the user’s browser. without having to modify objects in the business logic layer. Layered Architecture
■
Physical User Interface Layer. Changes to objects in one layer require little or no changes to the layers below. Object definitions in this layer are the visual representation of objects in the Business Objects Layer.0
.

Business Objects Layer. Object definitions in this layer describe individual business entities (such as Accounts, Contacts, or Activities) and the logical groupings and relationships among these entities. Business objects are based on data object definitions. Data Objects Layer. Object definitions in this layer provide a logical representation of the underlying physical database. For example, object definitions such as table, column, and index describe the physical database. These object definitions are independent of the installed RDBMS. DBMS. The third-party database management system manages the Data Objects Layer. It is not a part of the Siebel Business Application.

■

■

Each layer of the Siebel object model contains several principal object types. Most of these object types contain child objects that further define the given object type. For detailed information about the Siebel Object Architecture, read Configuring Siebel Business Applications.

Understanding the Object Definition Sequence
When configuring Siebel applications it is useful to think of configuration tasks in terms of the Siebel object model hierarchy shown in Figure 6 on page 38. Sometimes you work from the bottom up—data objects first, then business objects, and then user interface objects. Other times you work in one layer only, modifying objects as needed. Figure 7 shows the general sequence of tasks.

Figure 7.

Development Sequence

Developing and Deploying Siebel Business Applications Version 8.0

39

Getting Started with Siebel Tools ■ Using Siebel Tools

Using Siebel Tools
Siebel Tools is a declarative software development environment used to create and modify object definitions in the Siebel repository. Using Siebel Tools you can configure a standard Siebel application without modifying source code or SQL code. NOTE: You use an HTML code editor, not Siebel Tools, to modify Web templates. However, you can also view a color-coded rendition of Web templates using the Web Template Window in Siebel Tools. You can also specify a default HTML editor to open from within the Siebel Tools application. For more information, read “Setting Tools Options” on page 45.

Windows in Siebel Tools
Most of the work you do in Siebel Tools is through the Object Explorer Window, the Object List Editor, or the Object Properties Window. Each of these windows is described in the following sections.

Object Explorer
The Object Explorer is your starting point for working with object definitions. You use it to navigate through the Siebel object type hierarchy. It shows you the top level object types and lets you to expand them to reveal their child object types. You can also click the Flat tab to view object types listed alphabetically in a nonhierarchical structure. The Project drop-down list lets you display the object types for locked projects or a particular project only.

40

Developing and Deploying Siebel Business Applications Version 8.0

Getting Started with Siebel Tools ■ Using Siebel Tools

Not every top level object appears in the Object Explorer by default. You can display or hide object types by setting your Development Tools Options. Choose View > Options and then click the Object Explorer tab. Add or remove objects from the list of visible objects. Figure 8 shows the Object Explorer.

Figure 8.

Object Explorer

Developing and Deploying Siebel Business Applications Version 8.0

41

Getting Started with Siebel Tools ■ Using Siebel Tools

Object List Editor
The Object List Editor appears to the right of the Object Explorer. It lists the object definitions for the object type selected in the Object Explorer. For example, in Figure 9 the Object List Editor displays the object definitions for the Applet object type. Use the Object List Editor to create, modify, or delete object definitions.
Object Explorer Object List Editor

Figure 9.

Object List Editor

Object Properties Window
The Properties Window displays the property values for the object definition selected in the Object List Editor. It provides you with property definitions at a glance. The property window is often more convenient than the Object List Editor when you view or edit objects that have many properties. You can show or hide the properties window by doing the following.

Wizards
Siebel Tools includes many wizards that guide you through the process of creating new object definitions. Wizards assist you by prompting for key information necessary to define a particular object, such as an applet or a view. Then, based on the information entered, it creates the object definition and any related object definitions. You do not have to use wizards to create objects. You can also create objects by adding records in the Object List Editor. But this requires thorough knowledge of the Siebel Object Model hierarchy. This guide uses wizards wherever possible.

Developing and Deploying Siebel Business Applications Version 8.0

43

Web Layout Editor
Use the Web Layout Editor to drag user interface objects such as applets and controls and drop them into placeholders in Siebel Web templates.
2
Choose an object to create. The New Object Wizards dialog box appears. and then choosing Edit Web Layout. as shown in the following illustration.0
. You access the Web Layout Editor by selecting any of the following objects. The selected wizard opens.Getting Started with Siebel Tools ■ Using Siebel Tools
To open a New Object Wizard 1
Choose File > New Object. rightclicking. You use the Web Layout Editor to design the layout of applets and views. ■ ■ ■ Applets and Applet Web templates Views and View Web templates Web Templates
44
Developing and Deploying Siebel Business Applications Version 8.

Getting Started with Siebel Tools ■ Using Siebel Tools
Figure 11 shows the Web Layout Editor. These settings define your working language in Siebel Tools. Some of the options are described below.0
45
. These options are available by choosing View > Options. text strings such as an applet title can be defined in several languages. ■ Language Settings tab. Applet Web Layout Editor
Setting Tools Options
There are several options in Siebel Tools that you can set to facilitate your configuration work. The Tools Language Mode determines the locale-specific data that is:
■ ■ ■
Displayed in the Tools interface Available to edit Compiled to the SRF file
Developing and Deploying Siebel Business Applications Version 8. Objects can have locale-specific attributes. For example. and then choosing the tab for the options to configure.
Drag controls listed in this window to empty placeholders on the Web template Example of a control mapped to a placeholder in the Web template
Empty placeholder
Figure 11.

Web Template Editor tab. When working in this mode. For more information about language modes. ■ ■ Check In/Out tab. When you select this check box you can switch between the following two modes:
■ ■
Base. checking out object definitions (projects) from the development server as needed. That is.
46
Developing and Deploying Siebel Business Applications Version 8. read Using Siebel Tools. Language Override.
When the Enable Language Override check box is clear. the attribute is overwritten for the current language. you can work in base mode only. changes made to locale-specific attributes are stored in the base table. read “About the Local Development Environment” on page 58. For an overview of the development environment.0
. This setting defines the development server database and your local client database to be used in the check in and check out process. ■ ■ ■ ■ ■ “Checking Out Projects from the Server” “Making Configuration Changes” on page 48 “Compiling Projects” on page 48 “Testing Changes” on page 50 “Checking In Projects” on page 52
Checking Out Projects from the Server
You typically do your configuration work in a local database. changes are stored in a child locale table. When working in this mode.Getting Started with Siebel Tools ■ The Configuration Process
■
Transferred to and from the server during the check in and check out process
The current Tools Language Mode is displayed in the status bar located in the lower right corner of the Siebel Tools interface. Use this setting to define a default Web template editor. To edit locale-specific attributes. The changes apply to every language.
The Configuration Process
The typical process for configuration applications using Siebel Tools can be broken down into the following basic steps. select the Enable Language Override check box. When working in the Web Layout Editor you can click the Edit Template button on the toolbar to open the Web template using a default editor.

3 4
Select the project or projects to check out.0
47
. with the Check In/Out tab active. Click Options.Getting Started with Siebel Tools ■ The Configuration Process
To check out a project 1
In Siebel Tools. as shown in the following illustration. The default value is Siebel Repository. The Development Tools Options window appears. choose Tools > Check Out.
Developing and Deploying Siebel Business Applications Version 8. as shown in the following illustration.
2
Make sure you have selected the correct repository. The Check Out dialog box appears.

0
. make sure the Server and Client data sources are specified correctly. Read “Locking Projects in Your Local Repository” on page 53. This is how the procedures in subsequent chapters are written. There are various options for compiling the repository.cfg). During this time. In the Check Out dialog box. You disable password encryption in the Tools configuration file (tools.
48
Developing and Deploying Siebel Business Applications Version 8. CAUTION: Password encryption must be disabled when checking projects in and out. While running.Getting Started with Siebel Tools ■ The Configuration Process
5 6 7
In the Development Tools Options window. but you must remember to do it for each object you modify. a client application maintains a lock on the SRF file. You can compile at the project level—selected projects.
Compiling Projects
After you have made your configuration changes. your Mobile Web Client application that reads the repository file does not reflect the changes you have made. you can make configuration changes using Siebel Tools.
Making Configuration Changes
When you check out a project. without checking them out from a server database. Until you do so.
To compile projects 1
Exit Web Client applications that are running on the SRF file to compile. The Check Out dialog box appears. NOTE: You can also lock projects locally. extending business logic. Compiling individual objects is faster. click Check Out. you must compile them into a Siebel repository file. all projects—or you can compile individual objects. and extending the database. This prevents other developers from checking out the project. such as modifying user interface objects. Close the Development Tools Options window. all locked projects. the project remains locked in the server database and in your local database.

srf.
3
In the Object Compiler window. siebel. a typical path to an SRF file for a Mobile Web Client installed for testing on a developer’s machine is C:\Program Files\Siebel\7. as shown in the following illustration.7\web client\OBJECTS\siebel. or all projects. locked projects. The SRF file in this directory is locked because the Siebel Tools program itself reads from it constantly as it runs. The SRF file for your application is in the objects directory of your Siebel application client directory. click Compile. Compiling only the locked projects (those currently checked out) is faster than compiling all projects.
4
In the Object Compiler window. indicate whether to compile selected projects. choose Tools > Compile Projects. For example. Compiling locked projects is also often easier than selecting individual projects from the list. The Object Compiler window appears. click Browse to select the SRF file to compile. you will receive an error and be prevented from compiling.srf. NOTE: Be sure to make a backup copy of the repository file. NOTE: Do not try to compile to the objects directory of Tools.Getting Started with Siebel Tools ■ The Configuration Process
2
In Siebel Tools.0
49
. After compilation is successful.
5
In the Object Explorer window.
Developing and Deploying Siebel Business Applications Version 8. If you attempt to compile to this filename and path. the SRF file you specified contains the configuration changes you made.

Application > Views. or business objects. You cannot compile child-level objects. In the Object Compiler dialog box.0
.
3 4 5
Right-click and choose Compile Selected Objects. business components. select the repository file (SRF) to which to direct your changes. The objects can belong to different projects.
Registering New Views in the Application
When you add a new view to an application. You do this by registering the new view in the application using Administration Application > Views and then associating it to a responsibility. After compilation is successful. The Object Compiler dialog box appears.Getting Started with Siebel Tools ■ The Configuration Process
To compile individual objects 1
In the Object Explorer. You can check this by verifying the value of the repository file parameter in the application’s configuration file. This type of testing is considered to be Unit Testing. The View list appears. Click the menu button and then choose New Record. If you are working with existing views.
2
In the Object List Editor. select the object type to compile. these steps are not necessary. The views are already registered in the application.
To register new views in the application 1 2
From the application-level menu.
Testing Changes
When you have compiled objects into a new repository file. views. NOTE: Make sure the correct SRF file—the one you compiled your changes to—is defined for the application to test. Typically developers set up a Mobile Web Client on their machine to use for testing and point the Web Client to the repository file that has been recompiled with configuration changes.
50
Developing and Deploying Siebel Business Applications Version 8. the SRF file contains the configuration changes that you made. you can see the results of your changes in the client application. Click Compile. select the object or objects to compile. You can only select top level objects such as. you must make it visible in the client application before you can test it. applets. choose Site Map > Administration . which is one element of an overall testing strategy.

Application > Responsibilities. NOTE: You cannot edit the responsibilities that are part of the seed data that ships with the product. You must create a new responsibility to be able to associate new views to it. if you added a new applet to a view. Enter a description and select whether the view is to be available for local access in the Mobile Web Client.
To verify your changes 1 2
Start your client application. select the Responsibility to which to associate the view. click the menu button and then choose New Record.Getting Started with Siebel Tools ■ The Configuration Process
3
In the View Name field click the select button. You can copy one of the sample responsibilities. When a user with the responsibility logs into the application.
4 5 6
Choose a view and then click OK. you can log in to your Web Client application to verify the results of your configuration changes. Save the record.
Developing and Deploying Siebel Business Applications Version 8. The Responsibilities list appears.
3 4
Note any differences between what you find and the expected appearance or behavior. For example.
To associate views with a responsibility 1
From the application-level menu.0
51
. and then customize it for your purposes. If you find problems. Navigate to the objects you modified. choose Site Map > Administration .
Verifying Your Changes
After you have made any new views available in the application. Compile the project. The view is associated with the responsibility.
3 4
In the Views list. such as Siebel Administrator. Test the changes. repeat the following cycle:
a b c
Return to Siebel Tools to make configuration changes necessary to fix the problem. go to the view to make sure the applet appears where it is supposed to. From the Add Views dialog box select a view. The View picklist appears.
2
In the Responsibilities list. the view appears in the user interface.

2 3 4 5 6
52
Click Options. this may require you to check in projects before your work is complete because other developers may be dependent on a feature you have added to your project.
To check in changes 1
Choose Tools > Check In. Close the Development Tools Options dialog box. make sure the server and client Data Sources are pointing to the correct databases. In some cases. ■ ■ ■ ■ Test objects before you check them in. as shown in the following illustration. Keep in mind that the work of other developers may depend on the objects you are configuring.
For overview information about the development environment. As you did during check-out. Click the Locked/New Projects option button. read “About the Local Development Environment” on page 58. Validate projects using the Validate button in the Check-In dialog box. you need to check the project back into the development server. The Check In dialog box appears. Check in dependent projects at the same time to make sure the configuration on the server remains consistent.0
. Here are some guidelines for checking in projects.Getting Started with Siebel Tools ■ The Configuration Process
Checking In Projects
After you confirm completion of your configuration changes. Click Check In.
Developing and Deploying Siebel Business Applications Version 8. The Development Tools Options dialog box appears.

it is good practice to lock the project locally rather than checking it out from the server.0
53
. select the object or objects to export. It does not lock the project on the server database. This is useful when you are working in a multiple repository development environment and want to share object definitions.
To view project differences
■ Click the Diff button in the Check In dialog box.
Exporting Object Definitions
You can export object definitions making them available to import into another repository.
To lock a project locally
■ In the Tools Object List Editor select the project or other object type to modify.Getting Started with Siebel Tools ■ Other Key Tasks for Managing Object Definitions
Other Key Tasks for Managing Object Definitions
This section covers other tasks that are useful for working with object definitions. you can view the differences between projects on your local repository and the projects on the server repository. In the Object List Editor. while still allowing you to modify and test changes in your local repository.
Developing and Deploying Siebel Business Applications Version 8. This way the project remains unlocked on the server. then choose Tools > Lock Project. Tools locks the project in your local repository so you can make changes. NOTE: Do not lock a project locally on the server repository. Siebel Tools displays the checked out projects that have been modified since the last check out. so be aware that any changes you make are not saved.
To export object definitions 1 2
In the Object Explorer.
Locking Projects in Your Local Repository
When you are prototyping ideas or are making changes to object definitions that you plan to discard.
Viewing Project Differences Before Check In
Before checking in changes. select the object type to export. This is useful for finding errors or omissions before committing your changes to the server. You cannot check your changes back to the server. allowing other developers to check out the project from the server.

The Import Wizard opens and the object archive file opens.
2
Choose Tools > Import From Archive. Siebel Tools only shows information from only one repository at any time.
3 4
Find the object archive file (SIF) to import. The Export to Archive File dialog box appears. You cannot add objects to an existing export file. NOTE: A local or server database can contain more than one repository. NOTE: If you do not lock the projects affected by the import. The Select Archive File to Import dialog box appears.
54
Developing and Deploying Siebel Business Applications Version 8. However. the Import Wizard prompts you to lock them in the second dialog box of the wizard. To import object definitions you need to have access to the archive files (SIF) and the target repository needs to be the active repository on your local machine. NOTE: This file overwrites any existing SIF files with the same name. This is the active repository.
4
If you want to include additional objects in the export file:
a b c
Do not click Save.
5
Select a conflict resolution option. The object or objects are saved as files with an SIF extension. Return to the Object Explorer and select the object type to export. You can change the active repository by selecting the Repositories object type in the Object Explorer window or by choosing File > Open Repository.
5 6
Enter the path to the directory where the archive file is to be to stored.
To import archive files 1
Lock the projects that will contain the objects you are importing. Click open. Click Save. Repeat Step 2 and Step 3. NOTE: You can remove objects from the Export to Archive dialog box by selecting the object and pressing Delete.Getting Started with Siebel Tools ■ Other Key Tasks for Managing Object Definitions
3
Choose Tools > Add to Archive.
Importing Object Definitions
You can import object definitions from an archive file into your local repository.0
.

and then choosing Repository or File.
7
If there are no differences. or both. you can update the value in the Resolution column by selecting the attribute. Shows the object types in which differences were found. If the action for the object difference is merge.0
55
.Getting Started with Siebel Tools ■ Other Key Tasks for Managing Object Definitions
6
Click next. The Import Wizard checks for differences between the object definitions in the current repository and the object definitions in the archive file. the Import Wizard displays the following:
■ ■
Conflicting Objects. If there are differences. Shows whether the object exists in the archive file only. in the current repository. the object definition is imported.
■
Developing and Deploying Siebel Business Applications Version 8. Attribute Differences. Object Differences. and shows the conflict resolution action that has been defined. right-clicking. You can change the action if necessary. Shows the object attributes that have different values.

Getting Started with Siebel Tools ■ Other Key Tasks for Managing Object Definitions
56
Developing and Deploying Siebel Business Applications Version 8.0
.

Table 7.” In those chapters you can log in to the SAMPLE database using the SADMIN user name and password.” but before developers can do any configuration work. For a list of tasks and where in the application they are performed. “Getting Started in the User Interface Layer” through Chapter 10.Server Configuration screen Siebel Tools Siebel Tools
“Setting Up Database Users” on page 59 “Creating Positions” on page 59 “Associating Responsibilities” on page 60 “Setting Up Developers as Siebel Employees” on page 60 “Setting Up Developers as Mobile Web Clients” on page 61 “Generating a New Database Template” on page 62 “Extracting the Local Database” on page 65 “Initializing Each Developer’s Local Database” on page 67 “Performing a Full Get” on page 67
Developing and Deploying Siebel Business Applications Version 8. It is not necessary to complete these tasks to be able to follow the configuration examples in Chapter 6. “Installing Siebel Applications. NOTE: This chapter gives you an overview of the sequence of tasks that need to be performed to set up a developer’s local database.0
57
. Task
Tasks for Setting Up a Developer’s Local Database Where Performed RDBMS Software Administration .User screen Administration .Server Configuration screen Administration .Siebel Remote screen Administration . For example.5
Setting Up a Developer’s Local Database
After you have installed software as described in Chapter 3. each developer must be set up with a local database.User screen Administration . then each developer initializes their local database by downloading repository data from the server. see Table 7. “Modifying the Look and Feel of the Web Client. an administrator creates database users and runs Siebel Remote server tasks to generate local databases.User screen Administration . The process for setting up a local database includes tasks typically performed by an administrator and tasks performed by each developer.

Working on a local database gives you the option of not checking in changes to the server.0
. ■ Check out. they check them back into the server database. as determined by each user’s visibility rules. Copies selected projects (including any changes made by the developer) from the local database back to the server database and releases the lock on the server. provides the following benefits. Development Environment Working on a local database using check in and check out. A local database is a snapshot of the server database that is stored on a user’s machine. Check in. Copies selected projects from the server database to the local database and locks the projects on the server. The development environment is illustrated in Figure 12. the server database remains a clean backup.
58
Developing and Deploying Siebel Business Applications Version 8. rather than directly on the server database. Developers check out object definitions from the server database. then after making and testing changes on their local machines. ■ Allows you to roll back unwanted changes without overwriting the work of other developers. Locking the project on the server prevents other developers from checking it out. The data in each local database is a subset of the server database.
■
Figure 12.Setting Up a Developer’s Local Database ■ About the Local Development Environment
About the Local Development Environment
Developers working with Siebel Tools work on a local database. Until you check in changes.

0
59
. Make sure the user name clearly identifies the developer. However. The exact steps for adding users and placing them in this role group depend on the database software you are using.” For example. For more information about setting up database users. NOTE: The position information is used by the Siebel Remote’s routing rules and may affect the outcome of a database extraction. Read “Moving Modified Web Templates and Related Files” on page 177. You must manage Siebel Web template files using a third-party source control application or a manual process. none fit the role of the developer. assume NREC set up positions for two developers. Positions determine which records are available to each user. such as the first initial plus the last name. Allows developers to prototype configuration changes by locking a project locally rather than checking out and locking the project on the server. For more information. read the product documentation for the specific database application your organization uses. Establish a convention in choosing user names. A position can be any appropriate job title. There are several positions that are part of the seed data that ships with the Siebel product. such as the developer’s actual job title or simply the word “Developer. called Developer 1 and Developer 2. read “Checking Out Projects from the Server” on page 46 and “Checking In Projects” on page 52. read Siebel Remote and Replication Manager Administration Guide.
Developing and Deploying Siebel Business Applications Version 8.
Setting Up Database Users
Each user accessing a local database must be set up with a database user account.
Creating Positions
Positions represent an actual job position in your organization. For more information about positions. Work with your database administrator to add database accounts on the appropriate database and then add these accounts to the group SSE_ROLE. For information on how to perform check in and check out. Allows you to work remotely because you are not required to be connected to the development server.Setting Up a Developer’s Local Database ■ Setting Up Database Users
■ ■ ■
Allows several developers to concurrently use a single repository. so you need to create a new position for the users on your development team.
NOTE: Siebel Web templates are not included in the check in and check out mechanism used to control object definitions. read Siebel Applications Administration Guide. The user name used for the account is the name that appears in Siebel Tools when a developer locks a project.

0
.” An alternative to using a predefined responsibility is to create your own.
Setting Up Developers as Siebel Employees
After developers have a database account. The easiest choice is to assign developers the Siebel Administrator responsibility. For more information about responsibilities.
To set up an employee user 1 2
Log in to the development server with a user name and password that have administrator privileges. It is already defined as seed data and it provides access to every view. From the application-level menu. You can associate the users to this responsibility when you register the developer as an employee in “Setting Up Developers as Siebel Employees. and the necessary positions and responsibilities are defined. read Siebel Applications Administration Guide. the responsibility must include access to the views necessary to perform testing and development tasks. such as the SADMIN user name and SADMIN password. you can set up each developer as an employee in your Siebel application.User > Employees. For developers. The Employee list appears. Because the Siebel Administrator responsibility is already defined as part of seed data. you do not need to create a new one.Setting Up a Developer’s Local Database ■ Associating Responsibilities
Associating Responsibilities
Responsibilities determine which views users have access to. choose Site Map > Administration .
60
Developing and Deploying Siebel Business Applications Version 8.

This provides Siebel Remote with the information it needs to create a local database file for the developer and populate it with the appropriate data. this information is also included in each local database. Responsibilities determine which views a person has access to. NREC chose to associate the Siebel Administrator responsibility to each developer. For this reason. you must register developers as mobile Web clients. The developer’s last name. When you create a local database for the developer.
Developing and Deploying Siebel Business Applications Version 8.Setting Up a Developer’s Local Database ■ Setting Up Developers as Mobile Web Clients
3
In the Employees list.Siebel Remote screen. An alternative is to create a new responsibility that only allows developers access to a particular set of views. Developers typically need access to every view for the purpose of testing and entering test data. The login name must match the user’s database account name.
Password
NREC
Position Responsibility
Developer_1 Siebel Administrator
NOTE: The employee information for each developer resides on the development server. This field is read-only. Example Value Pat Adams PADAMS
Field First Name Last Name User ID
Comments The developer’s first name.0
61
. The user’s password to the application is the same as the user’s password on the database account. Enter the login names in uppercase letters for compatibility across databases.
Setting Up Developers as Mobile Web Clients
After setting up developers as Siebel Employees. you must set up developers as mobile Web clients because Siebel Remote uses this information to retrieve the local database during initialization. SADMIN) with access to the Administration . add a new record and complete the fields in the following table. The user name to be used for logging on to Siebel Tools (and for identifying which user has checked out a project). NOTE: Although Siebel Remote is not used for the check-in and check-out of projects.
To register a developer as a new mobile Web client 1
Log in to your Siebel application using an account (for example. Positions determine which records are visible to users.

This value is used to log into the local database during initialization. Complete the fields in the following table. It can contain only single-byte. if you did not select Siebel Remote during the installation process. with a maximum of eight characters. If you enabled Siebel Remote during the server installation process.Siebel Remote > Mobile Clients. The User ID makes a good mobile Web client name. NOTE: Before you can run server components. You create a database template on the server. or other invalid characters for a DOS filename. In the Mobile Clients list. However.EXTRACT ONLY model does not allow synchronization. which is appropriate in the case of a developer.0
.Setting Up a Developer’s Local Database ■ Generating a New Database Template
2
From the application-level menu. you need to enable it manually and then synchronize batch components. The name cannot include spaces. read Siebel Remote and Replication Manager Administration Guide. in this case the development server.
3 4 5
In the Parent Server form. this is already done for the Remote component group. and Siebel Remote. and the underscore (_) and hyphen (-) characters. language preference. Field Mobile Client Example Value PADAMS Description Enter the mobile Web client name in uppercase letters. The Mobile Client view appears with mobile Web clients for the Parent Server displayed. alphanumeric characters. choose Site Map > Administration . the component group to which it belongs must be enabled at the enterprise-level. For detailed information about Siebel Remote.
62
Developing and Deploying Siebel Business Applications Version 8. periods. routing models. choose the appropriate parent node. click New. This value identifies the routing model to which the mobile Web client belongs.
Generating a New Database Template
A database template is a cached representation of Siebel tables and indexes that are stored in a database file (DBF). Siebel Remote uses the template to create the local database for each developer. The MOBILE CLIENT . read Siebel System Administration Guide.
User ID Routing Model
PADAMS MOBILE CLIENT EXTRACT ONLY
For more detailed information about mobile Web clients. It is used simply for a snapshot of data. You create the database template by running the Generate New Database server component (GenNewDb). For instructions. read Siebel Remote and Replication Manager Administration Guide.

enter the name of the server on which to run the GenNewDb job. choose Navigate > Site Map > Administration . the Execution Server field displays the name of the server that actually ran the job.Server Management > Jobs. click the select button and use standard query techniques to select SQL Anywhere Database. After the job completes.
5 6
In the Job Parameters list. In the Requested Server field. and then click OK to return to the main window. replace this value with sse_encr.0
63
. In the Jobs list. click New. click New.
7
Modify the values of other parameters as necessary by repeating Step 5 and substituting different parameter names in Step 6. select Generate New Database. In the Name field.dbf and appears automatically. To use an encrypted template file.
Developing and Deploying Siebel Business Applications Version 8.
To generate a new database template (GenNewDb) 1 2 3 4
From the application-level menu.dbf. Set the UseDdlFile parameter to FALSE only when you run the Generate New Database component after a schema change. The Value field typically defaults to sse_utf8.Setting Up a Developer’s Local Database ■ Generating a New Database Template
Running the Generate New Database Server Component
The following procedure explains how to generate a new database template. In the Component/Job field. Table 8 lists the parameters and default values for the Generate New Database component.

the name is padded with consecutive digits.dbf. If no value is specified at run time. with the Generate New Database job still selected. A parameter value specified at component run time is used only for the current run of the Generate New Database component. is a Unicode file that supports all languages.0
. The password assigned to the local database administrator account on the Mobile Web Clients. Default for SQL Anywhere is SQL. Alternatively. A new database file generates. Set the DbaPwd parameter to the password for the DBA user ID in the empty database template file.dbf provides standard Sybase encryption of the local database template. Password for the DBA account.
64
Developing and Deploying Siebel Business Applications Version 8. the value specified in an administrative view is used. sse_encr. this takes a few minutes.Setting Up a Developer’s Local Database ■ Generating a New Database Template
8
In the Jobs list. Table 8 shows the start-up parameters for generating new database components. Name SQL Anywhere Database
Selected Parameters for the Generate New Database Component Alias DbfFile Required or Optional Required Default Value and Usage Notes SQL Anywhere database filename to initialize. click Start. Do not specify the Table Space parameter unless you intend to build a custom empty database file using the specified table space.. the default value is the first 8 characters of the enterprise name. The default value.
Table 8. for example 1234.
DBA Password
DbaPwd
Optional
New DBA Password
NewDbaPwd
Optional
Table Space
TSpace
Optional
Space name in DB template to store Siebel tables. Typically. If no value is specified at component run time or in an administrative view.. If the enterprise name has less than 8 characters. sse_utf8.

Do not specify the Index Space parameter unless you intend to build a custom empty database file using the specified index space. Client database engine type. The default is TRUE. The default is FALSE.
Index Space
Use Transaction Log File Use DDL File
UseTxnLog
Optional
UseDdlFile
Optional
Interface Tables Warehouse Tables Client Db Type
IFaceTbls WarehouseTbls ClientDbType
Optional Optional Optional
Create interface tables and indexes. For more information about positions and organizations. NOTE: The mobile user must have a valid position in the organization’s reporting hierarchy for the database extract to be successful.Setting Up a Developer’s Local Database ■ Extracting the Local Database
Table 8. Name
Selected Parameters for the Generate New Database Component Alias ISpace Required or Optional Optional Default Value and Usage Notes Space name in DB template to store Siebel indexes. For detailed information about Siebel Remote. If the value is set to TRUE. The default is FALSE—it means that the schema is read directly from the database. it means the schema is read from the DDL file.0
65
.
Developing and Deploying Siebel Business Applications Version 8. read Siebel Remote and Replication Manager Administration Guide. set the UseDDLFile parameter to FALSE. When a schema change takes place in your environment. Create Warehouse tables and indexes. read Siebel Applications Administration Guide. The data in this file is used to populate the user’s local database during the database initialization process.
Extracting the Local Database
The Database Extract server component extracts data from the server database for each mobile user and temporarily store it in a compressed file. The default is FALSE. The default is SQL Anywhere. GenNewDb then reads the latest schema from the database rather than the DDL file. Use when creating a new template file. Use when creating a new template file.

the read-only Execution Server field displays the name of the server that ran the job. The Mobile Web Client database is extracted. The following example shows a portion of the server directory tree after you run Database Extract for mobile Web clients (and developers) named PADAMS and SSCOTT. and are placed in the directory serversiebel_srvr_root\docking\user\outbox. enter the name of the server on which to run the Database Extract job.Setting Up a Developer’s Local Database ■ Extracting the Local Database
To run a database extract for a Mobile Web Client 1 2 3 4
From the application-level menu. click New and add the necessary parameters. select Database Extract from the picklist. click Start. NOTE: The installation program also places a directory named txnproc in the docking directory within the Siebel server root directory. In the Component/Job field. this is the same as the Requested Server.0
. The required parameter for Database Extract is Client Name. These files contain the data required to initialize the user’s local client database. which consists of multiple files. Each mobile user downloads these files to create a local database and local file system (copies of literature files). This may take a few minutes.
66
Developing and Deploying Siebel Business Applications Version 8. In the Jobs list. NOTE: After the job completes. siebel docking padams inbox outbox sscott inbox outbox txnproc Running the Database Extract task creates a database snapshot for a given user. choose Navigate > Site Map > Administration .Server Management > Jobs. with the Database Extract record still selected. The Database Extract program creates the appropriate directories for each mobile Web client.
6
In the Jobs list. which is located below the Jobs list and the Job Detail form. click New. Do not modify the contents of this directory under any circumstances.
Sample Directory Tree After Running Database Extract
Each registered mobile Web client requires a separate directory on the Siebel Remote server. For a Database Extract Job.
5
In the Job Parameters list. The value for the Client Name parameter is the name of the Mobile Web Client. In the Requested Server field.

Siebel Tools includes an initialization program that creates this file.
To perform the initial full get of every project from the repository 1
Start Siebel Tools.dbf and stores it on the developer’s local machine. Having a read-only copy of the full repository on your local machine allows you to compile a Siebel repository file for your local database.Setting Up a Developer’s Local Database ■ Initializing Each Developer’s Local Database
Initializing Each Developer’s Local Database
After you extract each developer’s local database. For information about the machines on which NREC installed different software. NREC used DEV_tools_A. This process is called a full get. If initialization is successful.
To initialize a developer’s local database 1
Go to the machine on which Siebel Tools is installed. NREC used DEV_tools_B. the sse_data. A full get is equivalent to checking out every project from the server. called sse_data. choosing Local in the Connect field. for the second developer. This is required for testing changes locally. “The local Siebel database was not found. For more information about the check in and check out process. for example c:\siebdev). see Table 5 on page 33. developers must now initialize their local databases. The following message appears.dbf file appears in the tools_root\local directory (where tools_root is the directory in which Siebel Tools has been installed. Initialization creates a local database file. you must populate it with a read-only copy of the projects and object definitions stored on the server database. however the projects are not locked and you cannot modify the object definitions until you check out a project from the server database or lock a project locally. Would you like to connect to the Siebel Remote server to initialize the local database?”
3
Click Yes.
2
Log in and connect to the Local database.0
67
. For the first developer. read “About the Local Development Environment” on page 58.
Developing and Deploying Siebel Business Applications Version 8. Siebel Tools connects to the Siebel Remote server and initializes the developer’s local database.
Performing a Full Get
After initializing a local database.

These data sources must match those shown in the Control Panel. Click Options.
7
In the Check Out dialog box. Click the All projects option button. In the Development Tools Options window.
68
Developing and Deploying Siebel Business Applications Version 8. under ODBC Data Sources.
For more information about working with projects. All objects from the server repository are copied to your local repository.
3 4 5 6
Choose the name of your development repository from the Repository pick list. meaning that your currently open local repository has the same contents as the server repository from which you did the full get. as shown in the following illustration.0
. click Get. The Check Out dialog box appears. make sure that your Server Data Source points to your server development database and your Client Data Source points to the local database you previously initialized and are currently running against.Setting Up a Developer’s Local Database ■ Performing a Full Get
2
Choose Tools > Check Out. read Using Siebel Tools.

and applets—and provides you with hands-on experience with basic configuration. You use this project to group the new and modified object definitions. you configure existing applets based on NREC requirements. This makes it easier for you to find your work and makes it easy to export and import the object definitions. you complete configuration tasks focusing on the user interface level of the object hierarchy. Working through the tasks in this chapter helps you understand the hierarchy of the major user interface objects—applications. The NREC example helps place the tasks in context of making configuration changes to meet business needs. This chapter includes the following topics: ■ ■ ■ ■ ■ ■ Creating an NREC Project Setting Your Target Browser on page 70 Creating Strings on page 70 Inactivating Screens on page 73 Inactivating Views on page 75 Configuring NREC’s Activity Applets on page 78
Creating an NREC Project
Before configuring object definitions. create a new project for NREC.0
69
. You can follow these tasks like a tutorial. In the latter part of the chapter. screens. right-click and choose New Record. views. The Projects window opens in the Object List Editor.6
Getting Started in the User Interface Layer
This chapter gets you started defining and modifying object definitions using Siebel Tools.
2
In the Projects window.
Developing and Deploying Siebel Business Applications Version 8.
To create a new project 1
In the Object Explorer. select the Project object type. The chapter starts off by leading you through the process of narrowing down the preconfigured application to just those screens and views relevant to NREC. configuring against your sample database. Following the NREC example.

Getting Started in the User Interface Layer ■ Setting Your Target Browser
3
Enter a new record with the following properties. the text that is displayed on the screens and views is stored in the repository and compiled to an SRF file. For example. Territory. Although you do not configure for different browsers in this guide. Internet Explorer 5.
Creating Strings
In Siebel applications. Every time you want to use “Account Team” on other views.
Setting Your Target Browser
Use the Target Browser feature of Siebel Tools to configure applications conditionally for different browsers. the server uses the SRF file to determine which fields to show. These names are stored in the SRF file. select the target browsers and move them to the Selected pane—for example. The Configuration Context toolbar appears. for example. Moving the objects that you create or modify helps you keep track of your configuration changes. Netscape 4. the view has fields with names such as Account Name. select IE 5. This model of keeping the strings separate from the view definitions is called symbolic strings. Otherwise. and so on.0
.0. Property Name Locked Value NREC Configuration TRUE
The project is now available for you to use. and field. you use the same link as you did on the first view. Status. The Target Browser Configuration dialog box appears.
3
From the list of available browsers.
2
From the drop-down list in the Target Browser field. Account Team. but there are some strong advantages to using symbolic strings. It may seem awkward to not have text directly on a view definition.7. choose Target Browser Config. ■ Reduces redundancy because many objects can refer to one symbolic string. Siebel Tools requires that you have a target browser set. you only need to define the term “Account Team” one time. When you display a page.
70
Developing and Deploying Siebel Business Applications Version 8. For example. when you display information on accounts. Netscape 6. view. you can not open the Web Layout Editor. Site.
To set a target browser 1
Choose View > Toolbars > Configuration Context. and what text (strings) are associated with each field. This includes the names of every screen.

To work with symbolic strings you must make it visible. The symbolic string model does not include other types of strings typically supplied as seed data. By using symbolic strings. “Client Team”. and List Column Display Names.Getting Started in the User Interface Layer ■ Creating Strings
■
Results in a more consistent user interface. Each symbolic string record represents a word or phrase. Simplifies translations by eliminating duplicated translations of the same word.
Creating Symbolic String References
You create new symbolic strings in Siebel Tools. time. including English. The Symbolic String object is hidden by default.
Strings Not Included in the Symbolic Strings Model
The symbolic strings model includes text strings stored in the repository and referenced by UI objects such as Applet Titles. The literal display value is retrieved from one of the several translations stored as symbolic string locale records based on the current Tools language mode. The use of symbolic strings also helps prevent inconsistent translations. For example “Acct. By reusing the same symbolic string. Reduces localization costs. Team”. “Account Group”. for example the NREC Configuration project. Although the NREC example does not cover localization. If the term “Account Team” is on five views. All translations of that word or phrase. and so on.
Developing and Deploying Siebel Business Applications Version 8. are stored as child symbolic string locale records. Symbolic strings created by Oracle are included in the Symbolic Strings project. error messages. the term is translated once. Control Captions. you update the symbolic string and that change then appears in all views that use that symbolic string. Simplifies maintenance because you only have to maintain one string for a given term. Because the symbolic strings are reused. If you need to change the name from “Account Team” to “Client Group”. and is language-independent. many custom implementations of Siebel applications are localized. such as LOVs. the EnableToolsConstrain parameter in the tools. This saves on localization costs and reduces the overall time for the project.0
71
. the same term does not exist multiple times. and inconsistencies. “Act. and predefined queries. NOTE: To be able to create symbolic strings. Team”. Create all custom symbolic strings in your custom projects.
■
■ ■
How the Symbolic Strings Model is Implemented
Symbolic strings are implemented using a top-level object in the Siebel repository called Symbolic Strings and a child object called Symbolic String Locale. you avoid having slightly different phrasing used on similar views. for example Account or Contact. it would need to be translated five times. This is much more efficient and effective than having to change each view individually.cfg file must be set to FALSE. User interface objects refer to symbolic string records for text strings.

Siebel Tools enforces a predefined prefix for the symbolic string name. In the Development Tools Options dialog box. select the Symbolic Strings object type. Name X_Bathrooms X_Bedrooms X_House_ID X_Number_of_Bathrooms X_Number_of_Bedrooms X_Square_Feet Current String Value Bathrooms Bedrooms House ID Number of Bathrooms Number of Bedrooms Square Feet Project NREC Configuration NREC Configuration NREC Configuration NREC Configuration NREC Configuration NREC Configuration
Notice that as you create each symbolic string.
To create a symbolic string 1 2 3
Check out the project in which to create the Symbolic String. This is because the Siebel Tools language mode is set to ENU. In the Object Explorer. a Symbolic String Locale record is automatically added that has ENU as the language. The Object Explorer now shows the Symbolic String object. click the Object Explorer tab.Getting Started in the User Interface Layer ■ Creating Strings
To expose the Symbolic String object 1 2 3
In Siebel Tools. Calculated value based on the current Tools language mode and the String Value property of the corresponding child Symbolic String Locale object. create a new record using the following table to complete the necessary fields. add the new symbolic strings as shown in the following table. choose View > Options.
72
Developing and Deploying Siebel Business Applications Version 8. The value used for the prefix is defined in the SymStrPrefix parameter in the tools.cfg file.
Current String Value
Definition
Some of the customizations you make for the NREC project involve adding new fields or changing the names of existing fields. This helps you distinguish custom symbolic strings from those created by the Siebel System (SBL_). In the Object List Editor. such as X_. To get started on this effort. and then click OK. Click the check box for the Symbolic String object. You make these changes by adding new symbolic strings or by editing the Symbolic String Locale of an existing string.0
. Description of the symbolic string. Property Name Description Unique name of the symbolic string.

and Campaigns. Page Tabs and Screen Menu Items. This removes the screens from the user interface. assume NREC has chosen to inactivate the Screen Page Tab and Screen Menu Items in the repository. because these screens are not part of the design. However. but leaves the screen objects active in the repository. These screens are not part of the design and NREC does not plan to use them in the future. Solutions.0
73
. These links are controlled by two child objects of the Application object. Page Tabs and Screen Menu Items
An alternative approach is to create a responsibility that does not include any of the views within the screen and assign users to that responsibility.
Developing and Deploying Siebel Business Applications Version 8. ■ ■ Page Tabs control the first-level navigation tabs in the user interface.Getting Started in the User Interface Layer ■ Inactivating Screens
Inactivating Screens
NREC’s implementation of the Siebel Partner Portal application does not include every screen that comes with the product. such as Service. Screen Menu Items control the links that appear on the Site Map.
Page Tabs (first-level navigation) link to screens and are always accessible
Screen Menu Items link from the Site Map to other screens
Figure 13. Therefore. You can remove these links by making the object types inactive. NREC has decided to remove the screens from the user interface. This approach allows you to add the screens back in the user interface without having to recompile the repository file. Screens appear in the user interface as first-level navigation tabs and as links on the Site Map. as shown in Figure 13 on page 73. NREC has chosen to remove the screens by inactivating objects in the repository.

This moves the application object to the NREC project making it easier for you to track changes. applets. Inactivate every Page Tab record except the following.
8
Inactivate the unnecessary screens listed under Step 6 on page 74 in the Screen Menu Item window by selecting the Inactive field for each record. The others are not part of the design. SCW is a designation used for many of the Siebel Partner Portal screens. this is the SRF file used by the Mobile Web client installed on your machine for testing. NOTE: The application object named Siebel eChannel is the application called Partner Portal. Inactive Screen Menu Items do not appear on the Site Map at run time. For example:
74
Developing and Deploying Siebel Business Applications Version 8.
9
Compile and Unit Test your changes. The project to which the application belongs (Siebel eChannel) is locked and a Pencil Icon appears in the W column indicating that you can modify the record.
7
In the Object Explorer.
6
Inactivate unnecessary screens listed in the Page Tabs window by selecting the check box in the Inactive field for each record.
a b
Choose Tools > Compile Projects. The Page Tabs window appears in the Object List Editor.Getting Started in the User Interface Layer ■ Inactivating Screens
To inactivate screen page tabs and screen menu items 1 2
In the Object Explorer. The inactive Page Tabs turn red in the repository and do not appear as first-level navigation tabs user interface at run time. The Screen Menu Items window appears. In the Object Explorer. select the Screen Menu Item object type (child of Application). Select the Siebel eChannel application. The employee application is Siebel Partner Manager. and so on. select the Page Tab object type (child of Application). Typically. In the Object Compiler dialog box.
4 5
Change the value for the Project property from Siebel eChannel to NREC Configuration.
3
Lock the project locally by choosing Tools > Lock Project.
■ ■ ■ ■
Accounts Screen (SCW) Activities Screen (SCW) Contacts Screen (SCW) Opportunities Screen (SCW)
NOTE: These are the screens that remain active in NREC’s application. select the Selected Projects or Locked Projects option button and then define the path to the Siebel repository file (SRF) to which you are compiling your changes. views. expand the Application object type.0
.

Accounts screen Views associated with the Accounts screen (Screen View object type)
Figure 14. These views appear in the user interface below the screen tabs as shown in Figure 14.srf file before you compile any changes.
Inactivating Views
Each screen in the Siebel application has a set of related views. read “Compiling Projects” on page 48. For more information about compiling. Click Compile. which is a child object of the Screen object type.
e
Open the Partner Portal application. The results of your changes appear when you start Siebel Partner Portal.Getting Started in the User Interface Layer ■ Inactivating Views
C:\Program Files\Siebel\7. Siebel Tools compiles the object definitions for the locked project to the repository file.0
75
. Views are associated to a screen using the Screen View object type. select the NREC Configuration project.
c d
In the projects list.7\web client\OBJECTS\ENU\siebel.srf NOTE: Be sure to make a back up of the siebel. Screens and Views
Developing and Deploying Siebel Business Applications Version 8.

The first level is the row of page tabs across the top of the frame for navigating to other screens.Assets View (SCW) Account Detail . active screens.Revenue Schedule View DC (SCW) Account Detail . The fourth level (not shown in Figure 14) is a drop-down list to select different grandchild views.Orders View (SCW) Account Detail .
Active Screens and Views in NREC’s eChannel Application Inactivate these views Account Detail .Projects View (SCW) Account Detail .. are not part of NREC’s Partner Portal solution. Proposals..Quotes View (SCW) Account Detail . All Accounts.Service Requests View (SCW) Account Presentations View (SCW) Account Proposals View (SCW) SI Com Account Briefing View (eApps)
For these screens.Getting Started in the User Interface Layer ■ Inactivating Views
There are four levels of navigation in Siebel applications. many of the views associated with the Opportunities Screen.0
. Table 9 summarizes the views that are to be inactive. The second level is the Show drop-down list to select different context views (for example My Accounts.Revenue Schedule View (SCW) Account Detail . such as Attachments. For more information about configuring navigation levels.Revenue Schedule Chart View (SCW) Account Detail .
Table 9. My Team’s Accounts).Account Team View (SCW) Account Detail . The third level is the second row of tabs to navigate to other views. Accounts Screen (SCW)
Activities Screen (SCW)
FS Activity Part Movements
76
Developing and Deploying Siebel Business Applications Version 8. read Configuring Siebel Business Applications. Quotes. NREC has chosen to inactivate the unnecessary views associated with each of the remaining. For example. Presentations. and Sales Teams. Many of the views associated with screens show data or contain functionality that is not part of NREC’s design.

NREC’s Business Requirements
Two applets appear on NREC’s Activities view: Activity List Applet and the Activity Detail Applet. reposition controls. read Configuring Siebel Business Applications. retrieves the relevant data from the Siebel database.
7 8
Repeat steps 2 through 7 for each active screen in the NREC example. you compile and Unit Test your changes. in which case you work with an external cascading style sheet (read Chapter 6. The Screen View window appears in the Object List Editor. select the Screen View object type (child of Screen). Objects such as controls and list columns are mapped to placeholders in Web templates. and “Testing Changes” on page 50.
6
Select the Inactive field for the views that are not part of NREC’s design. Tasks include defining object properties in the Object List Editor and mapping controls to placeholders in Web templates using the Web Layout editor. To determine which views to inactivate. Read “Compiling Projects” on page 48.Getting Started in the User Interface Layer ■ Configuring NREC’s Activity Applets
5
In the Object List Editor. you may also want to change style aspects of an applet. Compile and Unit Test. such as the color scheme. These applets need to be modified to meet NREC’s business requirements. After completing the procedures. right-click in Screen View window. Most of the time. For more information about Web templates. Modifying or creating applets is primarily done in Siebel Tools. and uses the HTML contained in the Web template to display the applet in the user interface. The business requirements and related tasks are listed below. However.
About Applets and Applet Web Templates
Applets are rendered in the user interface by combining objects definitions stored in the Siebel repository with layout and formatting information contained in applet Web templates. the Siebel Web Engine creates these objects.
78
Developing and Deploying Siebel Business Applications Version 8. see Table 9 on page 76. NOTE: To move the Inactive field next to the Name field. “Getting Started in the User Interface Layer”).0
.
Configuring NREC’s Activity Applets
To configure NREC’s applets you add and remove fields from the user interface. places them in the appropriate spot in the Web template. and modify text labels. and then choose Columns Displayed. At run time. you do not need to modify Web templates themselves.

Partner agents need to have the ability to track which opportunity is associated with each activity. Campaign. and Fund Request.0
79
. The design team prepared a view mock-up. No work is required in the underlying business object layer or data object layer. you must add the opportunity field to both applets. Read “Removing Fields (List Columns and Controls) from the User Interface” on page 80. Activity Detail View Mock-up
Developing and Deploying Siebel Business Applications Version 8. Additionally they require that the fields appear in a particular order. The tasks in this section give you some handson practice configuring applets. shown in Figure 15. that shows what the view and applets will look like after they are complete. Read “Exposing Fields in the User Interface” on page 82.
Figure 15. You will remove fields such as Associated Cost.
■
These tasks are in the user interface layer of the Siebel Object Model. Therefore. This functionality is not available in the preconfigured application. and reorder the remaining fields based on NREC’s design.Getting Started in the User Interface Layer ■ Configuring NREC’s Activity Applets
■
To enhance usability NREC requires that unnecessary fields be removed from the user interface.

80
Developing and Deploying Siebel Business Applications Version 8. NOTE: You need to have your target browser set before you can open the Web Layout Editor. In the Object List Editor. Make sure the Application drop-down menu is set to All Applications. select Activity Detail Applet (SCW).Getting Started in the User Interface Layer ■ Configuring NREC’s Activity Applets
Removing Fields (List Columns and Controls) from the User Interface
You can remove fields from the user interface using the Web Layout Editor.
To remove fields from the user interface 1 2 3 4
In the Object Explorer. select the Applet object type. but they are not rendered in the user interface at run time. Lock the project locally by choosing Tools > Lock Project. Change the Project property from Activity (SCW) to NREC Configuration.
5
Right-click and then choose Edit Web Layout. you delete it from the Web template. Read “Setting Your Target Browser” on page 70. The Web Layout Editor appears with the Base mode of the applet displayed. This unbinds the list column or control from the Web template. The objects remain intact as child objects of the applet.0
. For each field (list columns or controls) that you do not want to be displayed.

To turn off the preview. (Optional) Move the End field to the position formerly occupied by the Duration field.
Choose File > Save. and % Complete. Each field has two controls: a label (mapped to a symbolic string) and a field (mapped to a field in the database).Getting Started in the User Interface Layer ■ Configuring NREC’s Activity Applets
6
Pull down the Mode menu (in the Toolbar) and choose 3: Edit as shown in the following illustration.
3: Edit mode selected Inactive placeholder Control (Priority) mapped to a placeholder
7
In the Web Layout Editor. delete the following fields: Account. right-click and then choose Preview. in the Web Layout Editor. right-click and then choose Preview. Duration.
a b c 8 9
Select a control or use Control while clicking to select multiple controls. see the mock-up in Figure 15 on page 79.
Developing and Deploying Siebel Business Applications Version 8. To verify how the applet renders in the user interface. To determine where to place the field.0
81
. Right-click and then choose Delete.
10 Choose File > Close.

such as controls. each one a slight variation on the base word. Objects that appear in the user interface. Such a search may produce many possible results. and “Opportunity #”. Expand the List object type. ■ ■ List applets require that the field be defined as a list column object. However.
82
Developing and Deploying Siebel Business Applications Version 8. Form applets require that the field be defined as a control object.
Adding the Opportunity Field to the Activity List Applet (SCW)
On list applets. “OPPORTUNITY”. “Opportunity”. In the Object List Editor. If the project is not locked.Getting Started in the User Interface Layer ■ Configuring NREC’s Activity Applets
Exposing Fields in the User Interface
NREC’s partner agents must be able to associate an Opportunity record with an Activity record. After list column or control objects are defined. and then select the List Column object type (a child object of List). read Configuring Siebel Business Applications. Your selection in this pick list then populates the field. find and select the Activity List Applet (SCW). expand the List object type (a child object of Applet). For the Activity List Applet (SCW) you need to define the Opportunity field as a List Column before mapping it to a Web template. fields. screens. The List Columns window appears in the Object List Editor. For detailed information about configuring applets. The String Reference pick list can search for text. you may get “Opportunity:”. “Opportunities”. fields are defined as List Column object types. views. and so on each have a display name or caption. you can search for the term “Opportunity” and get a listing of existing symbolic strings that start with that word.
In the Object Explorer. do the following. For example.
a b 4 5
Choose Tools > Lock Project. For example. The Opportunity field is already defined on the underlying business component—the Action business component—so that what is required is to expose the field in the user interface. you can reconfigure the applets to display it. The Caption field or Display Name field contains the text that appears in the user interface. The tasks for exposing the opportunity field in the user interface differ slightly for a list applet and form applet. Change the Project property from Activity (SCW) to NREC Configuration. instead you use the pick list in the appropriate String Reference field to select an existing symbolic string to use.
To define a list column object for a list applet 1 2 3
In the Object Explorer. the objects are mapped to placeholders in Web templates. expand the Applet object type. Although the field does not appear by default. NOTE: The Activity Detail Applet (SCW) is a form applet.0
. the Activity List Applet and the Activity Detail Applet do not include the Opportunity field by default. You do not put text directly into these fields.

the Display Name field shows the selected string. Note that after you pick this symbolic string. Select one that has an initial capital letter and no colon after it.0
83
.
To add a control object to a form applet 1 2 3
In the Object Explorer. fields are defined as Control object types. In the Object List Editor.
Runtime
TRUE
Adding the Opportunity Field to a Activity Detail Applet (SCW)
For form applets. add a new record using the properties shown in the following table. Property Name Display Name String Reference Value Opportunity SBL_OPPORTUNITY1004224537-11Q Description This is a name of the list column record. When the property is set to TRUE. select the Control object type (child of Applet). the application makes a run-time check to determine if a pick list. calendar. the Action business component). Field Opportunity The values available from the drop-down list are the fields defined on the parent business component of the Applet (in this case. calculator.Getting Started in the User Interface Layer ■ Configuring NREC’s Activity Applets
6
In the List Columns window. In the Object Explorer. For the Activity Detail Applet (SCW) you define the Opportunity field as a control before mapping it to a Web template. Use the pick list and search for an Opportunity symbolic string. find and select the Activity Detail Applet (SCW). or MVG pop-up button must be provided. expand the Applet object type. There are several symbolic strings that start with “Opportunity”.
Developing and Deploying Siebel Business Applications Version 8.

0
. In this case. In the Object List Editor. add a new record with the properties shown in the following table. This method is an alternative to defining the controls in the Object List Editor as described in the previous section.
84
Developing and Deploying Siebel Business Applications Version 8. select the Activity List Applet (SCW). Use the pick list and search for an Opportunity symbolic string. Note that NREC’s design requires that you follow the same procedure for mapping the Opportunity control to the Web templates for the Activity Detail Applet (SCW) as well. You can move controls by dragging and dropping them or by using the Shift to Previous Placeholder and Shift to Next Placeholder buttons on the toolbar. Property Name Caption . so that the string on the form applet matches the one used on the list applet. There are several symbolic strings that start with “Opportunity”.Getting Started in the User Interface Layer ■ Configuring NREC’s Activity Applets
4
In the Controls window of the Object List Editor.
4 5
Change the mode to 3: Edit List. HTML Control Type. Right-click and choose Edit Web Layout. Note that after you pick this symbolic string. Select one that has an initial capital letter and no colon after it.
Mapping List Columns or Controls to Web Templates
After you have defined the list column and control object types for the applets. Field HTML Type Opportunity Field Field defined on the parent business component. and then define the necessary properties. The following procedure uses the Opportunities list column on Activity List Applet (SCW) as an example.String Reference Value Opportunity SBL_OPPORTUNITY1004224537-11Q Description Unique name of the control object. drop it onto the template. Make room for the Opportunity field by rearranging the controls that are already mapped to the Web template.
To map fields (controls and list columns) from an applet to a Web template 1 2 3
In the Object Explorer. You do this using the Web Layout Editor. the parent business component is Action. the Caption field shows the selected string. you are ready to map them to placeholders in a Web template. select the Applet object type. The process for mapping list columns or controls to Web templates is the same for both list applets and form applets. NOTE: It is also possible to create controls while working in the Web Layout Editor. To do this you drag a control type from the toolbar. The Web Layout Editor appears with the applet displayed in Base mode. Select the same symbolic string you selected in Step 6 on page 83.

NOTE: You can also export the preview to an HTML file by choosing File > Export.
8 9
Make adjustments as necessary. You may need to resize the label to fit.
7
To verify how the applet renders in the user interface. drag the Opportunity list column and drop it into an empty placeholder in the Web template. right-click and then choose Preview.
Opportunity List Column added. and then choosing a file name and location in the Save As dialog. Choose File > Save.0
85
.Getting Started in the User Interface Layer ■ Configuring NREC’s Activity Applets
6
From the Controls/Columns window. choose View > Windows > Controls.
Developing and Deploying Siebel Business Applications Version 8.
NOTE: On a form applet you need to add the label (OpportunityLabel) and the text box (Opportunity). as shown in the following illustration. NOTE: If the Controls/Columns window is not open.
10 Repeat the procedure for the Activity Detail Applet (SCW).

0
.Getting Started in the User Interface Layer ■ Configuring NREC’s Activity Applets
Reviewing the Results
In the previous sections you removed the unnecessary fields from applets. Activity Applets
86
Developing and Deploying Siebel Business Applications Version 8. the applets appear as shown in Figure 16. and changed the display name and caption of a field. After you compile your changes and perform a Unit Test. added a new field.
New Opportunity list column
New Opportunity label and text box
Figure 16.

business objects. Working through the material this way gives you a good understanding of the object definition sequence and give you plenty of practice with many of the common configuration tasks.7
Configuring the House and Opportunity Entities
In this chapter you will work in three layers of the object model—data objects layer. This involves both modifying existing object definitions and creating new ones. The product entity in the Siebel data model meets NREC’s needs reasonably well.0
87
. it is presented at a higher level with a cross reference to the detailed procedure. These columns will be used to store the following additional attributes for each house. You can follow the tasks in this chapter like a tutorial. If a task also occurs later in the chapter. For example. such as square feet and number of bedrooms.
Configuring the House Detail View
NREC’s House Detail view needs to be able to display the current list of houses for sale and the details for each house. ■ ■ ■ ■ ■ ■ Creating and modifying views Creating and modifying applets Creating and modifying business components Modifying business objects Adding columns to an existing base table Using 1:M extension tables
The tasks in each section start at the database layer then progress up to the user interface layer. Tasks are covered in detail where they first appear. ■ ■ ■ ■ ■ ■ Address City Number of Bathrooms Number of Bedrooms Price Square Feet
Developing and Deploying Siebel Business Applications Version 8. and includes the following tasks. assume NREC’s design team has decided to extend the internal products base table by adding additional columns. However. You can extend the standard data model to meet your unique business requirements. configuring against the sample database. and user interface object—with the goal of constructing four views based on NREC’s design specifications. attributes such as square feet and number of bedrooms are not part of the Siebel data model.

In this section you will add columns to the internal products table. read Configuring Siebel Business Applications. and then modify objects in the business object layer and the user interface layer to accommodate the columns changes. The tasks for accomplishing this are: ■ ■ ■ ■ ■ ■ “Extending the Database by Adding New Columns to the Base Table” on page 89 “Configuring the Internal Product Business Component” on page 92 “Modify Existing Product Applets to Display NREC Attributes” on page 93 “Creating the House Detail View” on page 96 “Creating the Houses Screen” on page 97 “Compiling and Unit Testing” on page 100
88
Developing and Deploying Siebel Business Applications Version 8. You will modify existing objects as well as create new objects where appropriate.Configuring the House and Opportunity Entities ■ Configuring the House Detail View
■ ■
State ZIP Code
NOTE: Although List Price exists as standard field on the Internal Product business component.0
. For detailed information about extending the data model. assume that NREC’s design team has decided to add a column to S_PROD_INT to keep the house attributes stored in one table.

Developing and Deploying Siebel Business Applications Version 8. House Detail View Mock-Up
Extending the Database by Adding New Columns to the Base Table
You add columns to a base table using the Database Extension Designer.0
89
. This is a new list-form view using existing applets.Configuring the House and Opportunity Entities ■ Configuring the House Detail View
Figure 17 shows a mock-up of NREC’s House Detail View. This involves adding columns to the base table using the Object List Editor in Siebel Tools and then applying the changes your local database schema.
Figure 17.

NOTE: The project field is read-only for tables. For example. Name X_ADDRESS X_BATHROOMS X_BEDROOMS X_CITY X_PRICE X_STATE X_SQFT X_ZIP_CODE Physical Type Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Length 30 30 30 30 30 30 30 30
NOTE: Names of extension columns begin with X_ (for example. S_PROD_INT.Configuring the House and Opportunity Entities ■ Configuring the House Detail View
Adding New Columns to the Products Table
First you must add the columns to the base table. select S_PROD_INT. Only public tables can be extended.
90
Developing and Deploying Siebel Business Applications Version 8. In the Tables window.0
. The User Names of extension columns end with Ext (for example. Notice that the table is of type Data (Public). expand the Table object type. select Column object type (child of table). X_ADDRESS). In the Columns window. add the records shown in the following table. The names of the columns for the S_PROD_INT table appear in the Object List Editor. You cannot change the project from Newtable to NREC Configuration. The logical database schema is changed based on the information you entered. X_ADDRESS Ext). You do this by creating additional Column object definitions for the base table object.
To add a new column to a base table 1 2 3
In the Object Explorer. you have to physically apply the schema changes to your local database. Siebel Tools automatically enforces these conventions. you are adding columns to the products table. Lock the project locally by choosing Tools > Lock Project.
4 5
In the Object Explorer.
Applying Schema Changes to Your Local Database
After you have added columns to the base table as described in the previous section. but you still need to physically apply the changes to your local database.

4
Click OK. select the Table object type. In the Tables window. A warning appears indicating that you are connected to a local database and asking if you want to continue. choose Current Row.0
91
.
Developing and Deploying Siebel Business Applications Version 8.Configuring the House and Opportunity Entities ■ Configuring the House Detail View
To apply schema changes to the local database 1 2 3
In the Object Explorer. Update the database to reflect the changes made to the dictionary. and updated if required. Current Query option. Click Apply. This option forces each database object to be compared with the data dictionary. Update the database to reflect modifications made to the tables in the current query only. The Apply Schema dialog box appears. This updates the database to reflect the schema change to the current selected row only (S_PROD_INT).
5
In the Tables pick list. select S_PROD_INT. Other options are:
■ ■
All. as shown in the following illustration.

Do not specify a table space or index space. the columns you added to the logical schema as described in “Extending the Database by Adding New Columns to the Base Table” on page 89 now physically exist on your local database and are available to use in your configuration. Lock the project locally by choosing Tools > Lock Project. After this process has been completed.
7
Verify that the ODBC (Open DataBase Connectivity) connection specified in the ODBC Data Source text box is correct for your environment.Configuring the House and Opportunity Entities ■ Configuring the House Detail View
6
Enter the Database user password.
Configuring the Internal Product Business Component
After you have applied the extension columns to your local database schema. you need to apply these changes to the server database. but this process does not apply physical database extension changes. The following procedure uses the square feet attribute as an example.
To add fields to the Internal Products business component 1 2 3 4 5
In the Object Explorer. expand the Business Component object type. you can add the fields to the business component that will use the columns to store data. after you have tested changes in the local database environment. you need to go through a separate process to apply database extension changes to the server database. In the NREC example. read Configuring Siebel Business Applications. Change the value of the Project property from Product to NREC Configuration. NOTE: The default password is SIEBEL. For information on this process.
NOTE: Typically. you add fields to the Internal Product business component. Checking in a project copies configuration changes to the server. If you are connected to the Sample database use “SIEBEL” as the Database user and the Database user password. NOTE: You cannot apply schema changes to any database other than the one to which you are currently connected.
92
Developing and Deploying Siebel Business Applications Version 8. you need to add fields for the attributes listed at the beginning of this section as described in “Configuring the House Detail View” on page 87. Additionally.0
. In the Object Explorer. select the Internal Product business component. In the Business Components window. To complete the NREC example. select the Field object type (child of Business Component).
8
Click Apply to apply the new columns to the physical schema on your local database. you need to modify specific properties of the business component so users can update records. and “SEAW Samp Db default instance” as the ODBC data source. Therefore.

Change the values of the following properties from the default value of TRUE to FALSE. Assume that NREC’s design team has determined that configuring the following two applets is easier than creating new ones. Choose View > Windows > Properties Window.0
93
. Name Address Bathrooms Bedrooms City Price Square Feet State Zip Code Column X_ADDRESS X_BATHROOMS X_BEDROOMS X_CITY X_PRICE X_SQFT X_STATE X_ZIP_CODE
To change the default properties of the Internal Products business component 1 2 3
Select the Internal Product business component in the business component window. ■ ■ Product List Applet Product Form Applet
These applets are already based on the Internal Product business component and meet NREC’s needs reasonably well. you can display them in the user interface. add records for the fields shown in the following table.
Modify Existing Product Applets to Display NREC Attributes
After the fields are added to the business component.
Developing and Deploying Siebel Business Applications Version 8.Configuring the House and Opportunity Entities ■ Configuring the House Detail View
6
In the Fields window. Field No Delete No Insert No Merge No Update Value FALSE FALSE FALSE FALSE
Changing the values of these properties enables users to enter records using applets based on this business component.

In the Web Layout Editor. users can add them to the display by choosing Columns Displayed from the applet-level menu.String Reference field. Add List Column objects for each of the new fields shown in the following table. Fields with a Show In List property set to FALSE appear gray in the Web Template layout editor. read “Exposing Fields in the User Interface” on page 82.
■ ■
Change the display name of the Part # list column to House ID. and choose Edit Web Layout.
■ ■ ■
Class Compensable Customizable
94
Developing and Deploying Siebel Business Applications Version 8. Name Address Bathrooms Bedrooms City Price Square Feet State ZIP Code Display Name Street Address Bathrooms Bedrooms City Price Square Feet State ZIP Code Field Address Bathrooms Bedrooms City Price Square Feet State ZIP Code Show In List FALSE TRUE TRUE FALSE TRUE TRUE FALSE FALSE
NOTE: The Show In List property determines whether the field is displayed by default in the list applet. The following procedure covers configuring the Product List Applet. and then change the value of the Project property from Product (SSE) to NREC Configuration. Change the display name of the Name list column to Summary.0
.
To expose fields in the Product List Applet 1 2 3
Navigate to the Product List Applet. right-click it. However. Note that the object hierarchy is Applet > List >List Column. For detailed procedures. delete the following unnecessary columns for the 1: Base mode of the applet. Remember that to set the Display Name field you must select a symbolic string using the pick list in the Display Name .
5 6
Select the Product List Applet record.Configuring the House and Opportunity Entities ■ Configuring the House Detail View
The following procedures cover exposing fields in the user interface at a more abstract level than was covered in the previous chapter. These fields are hidden by default in the user interface.
4
Change the display name of existing list columns. Lock the project locally by choosing Tools >Lock Project.

including the fields to be hidden by default. 11 Delete the following unnecessary columns.
13 Choose File > Save.
■ ■
Class Vendor
12 Add the fields that you defined in Step 3 on page 94.0
95
.
10 Switch to the 3: Query mode of the applet. The result resembles the following illustration. NOTE: You can switch applet modes using the Mode drop-down list on the Configuration Context Toolbar. including the fields to be hidden by default.
8 9
Choose File > Save.
Developing and Deploying Siebel Business Applications Version 8. Repeat Step 6 on page 94 through Step 8 on page 95 for the 2: Edit mode.Configuring the House and Opportunity Entities ■ Configuring the House Detail View
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description Effective End Date Effective Start Date Equivalent Product Lead Time Orderable Organization Product Line Revision Serialized Service Product Unit of Measure
7
Add the fields that you defined in Step 3 on page 94. 14 Choose File > Close.
Drag the column names from the Controls/Columns window to a Field placeholder in the Web Layout Editor.

Use the View Wizard to create the view using the applets modified in the previous sections. Choose File > Save.
7 8
In the Web Layout Editor. This type of view is the standard list-form view. In the Web Layout Editor delete the unnecessary controls and add the new controls. Use Figure 17 on page 89 to determine what controls to add and delete. They want to have the Products List Applet on top and the Products Form Applet below.0
. Change the caption of the Name control to Summary. Add Control objects (child of Applet) for each of the new fields as shown in the following table.String Reference field. Name Address Bathrooms Bedrooms City Price Square Feet State ZIP Code Field Address Bathrooms Bedrooms City Price Square Feet State ZIP Code Caption Street Address Bathrooms Bedrooms City Price Square Feet State ZIP Code
4
Modify the caption property of the existing controls. and then choose File > Close. Remember that to set the Caption field you must select a symbolic string using the pick list in the Caption .
Creating the House Detail View
NREC wants to create a new view to display the Product List and Product Form Applets.
To configure the Product Form Applet 1 2 3
Navigate to the Product Form Applet.
96
Developing and Deploying Siebel Business Applications Version 8.
5 6
Select the Product Form Applet record.Configuring the House and Opportunity Entities ■ Configuring the House Detail View
Configuring the Product Form Applet
The following procedure covers configuring the Product Form Applet. and right-click and then choose Edit Web Layout. map the EditRecord control to the appropriate placeholder.
■ ■
Change the caption of the Part # control to House ID. Lock the project locally by choosing Tools >Lock Project. and then change the value of the Project property from Product (SSE) to NREC Configuration.

In the Web Layout view. choose File > Close. you must add it to a screen so it appears in the user interface. Set the Home Page visibility using the View Web Template Item object. This screen groups the views related to the Houses entity. in this case.
2
Under the General tab.
Creating the Houses Screen
After creating the view. Field Project Name Title Business Object Web Template Selected Applets Value NREC Configuration NREC House Detail View House Detail View Internal Product View Detail (Parent with Pointer) Product List Applet Product Form Applet
The wizard creates the view and related objects. or Sales Rep.
To create the Houses screen 1
Create a symbolic string for the term “Houses”. After creating the screen. read “To create a symbolic string” on page 72. set the Visibility Applet Type property of the View object. NREC decided to create a new screen for houses.0
97
.
NOTE: When creating views with special visibility properties. Manager. you need to define a Screen View child object to associate the screen with the House Detail View. The New Object Wizards appears. When done looking at the preview.
4 5 6
To review the results of the wizard. The New View wizard opens.
3
Complete the wizard using the information from the following table. However. select the View object and select the NREC House Detail View. For more information. such as Organization.
Developing and Deploying Siebel Business Applications Version 8. Right-click it and choose Edit Web Layout.Configuring the House and Opportunity Entities ■ Configuring the House Detail View
To create a new view 1
Choose File > New Object. The only exception to this rule is the Home Page. right-click and choose Preview. select View and then click OK. not the View Web Template Item object.

expand the Screen object type. In the Screen Views window. you will select this category name as the screen view’s Parent Category. The Screen View window opens in the Object List Editor. Enter a new record with the properties shown in the following table.Configuring the House and Opportunity Entities ■ Configuring the House Detail View
2
In the Object Explorer. Text that appears in the Show drop-down menu. add a new record using the values shown in the following table.
98
Developing and Deploying Siebel Business Applications Version 8. select the Screen View object type (child of Screen). Provides a name for the category.0
. This screen view and future screen views will be grouped together within this category.String Reference. Add a new record with values shown in the following table. right-click and choose New Record. When you define screen views. Description Name of associated view.
6
Before adding the NREC House Detail View to the Houses screen. Field View Type Parent Category Value NREC House Detail View Aggregate View NREC This puts this screen view in the NREC category on the Site Map. Set this using Viewbar Text .
Category Name Viewbar Text
NREC
More Info
7
Now add the NREC House Detail View.
3 4
In the Screen window. Field Type Value Aggregate Category Description This defines a category that appears in the Site Map under the Houses heading (to be defined in Step 4 on page 99). add a category to group this screen view and future screen views in the Site Map. Field Name Project Viewbar Text Value NREC House Screen NREC Configuration Houses
5
In the Object Explorer. The Screens window opens in the Object List Editor. Screen Views associate views to a screen.

These objects are child objects of the Application object type.0
99
. select the Screen object type again. add a new record with the properties shown in the following table. In the Object Explorer. In the Application window. select the Siebel eChannel application. right-click and enter a record with the properties shown in the following table.
To define Page Tabs and Screen Menu Items 1 2 3 4
In the Object Explorer. Field Screen Value NREC House Screen Description Screen associate with the Screen Menu Item.
5 6
In the Object Explorer. select the NREC House Screen record and set the Default View property
Defining Page Tab and Screen Menu Items
For screens to appear in the user interface. the NREC House Detail View is the default view for the NREC category. select the Screen Menu Item object type (child of Application). Field Screen Sequence Text Value NREC House Screen 125 Houses Description Screen object associated with the page tab.
Developing and Deploying Siebel Business Applications Version 8.
10 In the Screen window. Determines the sequence in which view tabs are displayed.String Reference. Also make the NREC House Detail View the default view for the House screen. In the Object List Editor. to NREC House Detail View. Text that appears in the tab.Configuring the House and Opportunity Entities ■ Configuring the House Detail View
Field Viewbar Text Sequence
Value More Info 20
Description Text that appears in the Show drop-down menu. Page tabs appear as the tabs across the top of the application and Screen Menu Items appear in the Site Map. Set this using Viewbar Text . In the Screen Menu Item window.
8 9
Preferably. In the Page Tab window. select the Page Tab (child of Application) object type. Select the NREC category record and set the Category Default View property to NREC House Detail View. expand the Application object type. Determines the sequence in which the page tabs appear. you must define Page Tab and Screen Menu Items.

read “Testing Changes” on page 50. such as Siebel Administrator. You must create a new responsibility to be able to associate new views to it. ■ ■ Register the House Detail View in the application. Associate the House Detail View to a responsibility. You can copy one of the sample responsibilities. NOTE: You cannot edit the responsibilities that are part of the seed data that ships with the product. you must perform the following tasks using a Siebel employee application.
100
Developing and Deploying Siebel Business Applications Version 8.0
. After compiling the changes to a repository file. such as Siebel Call Center or Siebel Sales. you can access the new view. but before testing the changes. When you log in as SADMIN. For detailed procedures.
Compiling and Unit Testing
Now you are ready to compile and Unit Test your changes. You can create a new responsibility for testing.Configuring the House and Opportunity Entities ■ Configuring the House Detail View
Field Sequence Text
Value 15 Houses
Description Determines the sequence that the item appears. You must complete these steps any time you create a new view. Text that appears as the link on the Site Map. You cannot do these tasks in Siebel Partner Portal because it does not have the administrative views exposed. call it NREC Test. and then customize it for your purposes. and then associate the SADMIN user to the responsibility.

In the NREC example. you will use the 1:M extension table for S_PROD_INT. Review the ER diagram in “Data Layer” on page 28 for more information about NREC data entities and their relationships. which is named S_PROD_INT_XM. This is a one-to-many relationship between the Products entity (Houses) and the Appraisals entity.
Figure 18. appraisal value. Each house can be associated with many appraisal records. assume that the NREC design team has decided to create a new business component for appraisals. which will store its data in a standard one-to-many extension table. The standard Siebel data model does not include an appraisals entity.0
10 1
. appraiser) for a particular house. therefore. NREC House Detail
Configuring the House Detail Appraisals View
The House Appraisals view is designed to provide a list of appraisal details (date.Configuring the House and Opportunity Entities ■ Configuring the House Detail Appraisals View
Figure 18 shows what the applets and view look like after configuring them.
Developing and Deploying Siebel Business Applications Version 8.

Because the extension tables themselves are already part of the data model. read “Creating the Appraisals Business Component. see Figure 19 on page 110. read Configuring Siebel Business Applications. you need to create a new applet to display the list of Appraisals in the bottom applet. However. this practice must also be followed when the extension table is used by only one business component. However. you use the TYPE column to group records. The business component must have a Type field that defaults to a unique value and a search specification that finds only those records that contain this value. The view displays a detailed house record in the top applet and a list of appraisals in the bottom applet. ■ ■ ■ ■ ■ ■ ■ “Creating the Appraisals Business Component” on page 102 “Creating a Link Between Houses and Appraisals” on page 105 “Adding the Appraisals Business Component to a Business Object” on page 106 “Create a New Appraisals List Applet” on page 107 “Creating the House Detail . This column maps to the foreign key field using in the one-to-many link. You can extend the data model for your purposes and track entities that are not part of the standard Siebel data model. To see the end result of the configuration work. For the top applet. The NREC design team has also determined that a master-detail view is required to display this data.Configuring the House and Opportunity Entities ■ Configuring the House Detail Appraisals View
For more information about extension tables. For details of how this is accomplished.Appraisals View” on page 108 “Adding Additional Columns to the Opportunity Base Table” on page 111 “Compiling and Unit Testing” on page 109
About Standard 1:M Extension Tables
One-to-many extension tables are predefined tables that have one-to-many relationships with base tables. ■ PAR_ROW_ID. you can use the Product Form Applet that you configured as described in “Modify Existing Product Applets to Display NREC Attributes” on page 93. Displaying data from a 1:M extension table requires the following steps. They have generic columns that you can use to store additional data. and so on).” With this practice you can use a single one-to-many extension table to store data for multiple business components. ATTRIB_02. as well as three fields that provide the user key and map to the following columns. you do not need to modify the database schema. The names of one-to-many extension tables contain the suffix _XM. When using a one-to-many extension table to store data.
102
Developing and Deploying Siebel Business Applications Version 8. You create a new business component for the entity to be tracked.
Creating the Appraisals Business Component
To display data from a one-to-many extension table you must define a new business component with fields that map to the generic columns in the extension table (ATTRIB_01.0
. NOTE: There are more than 20 one-to-many extension tables in the standard data model.

select the BusComp icon and then click OK. and then click Next.
4
Enter the columns and field names as shown in the following table.
To create the Appraisals business component 1
Choose File > New Object. Enter the information from the following table.
2 3
Under the General tab. Field Project Name Table Value Product (SSE) Appraisals S_PROD_INT_XM
The Single Value Fields dialog box appears. Used to store the name of the Appraiser. This column is used to group records in the extension table. Will be set to a unique predefault value. The New Object Wizards dialog box appears.0
10 3
.
Developing and Deploying Siebel Business Applications Version 8. The New Business Component wizard appears. The value in the name needs to make the record unique for each parent record. The following procedure guides you through creating the appraisals business component for the NREC example. and TYPE must be unique to satisfy the U1 index of the _XM table. This column maps to the field being tracked in the business component. and then click Add for each one. Parent Row ID. TYPE. Map this column to the Type field. You set a default value for the Type field and then configure the business component to search for those records in the extension table that contains this value. Comments. PAR_ROW_ID. Appraised value of the property.Configuring the House and Opportunity Entities ■ Configuring the House Detail Appraisals View
■ ■
NAME. Used to group records. Column in Base Table ATTRIB_01 ATTRIB_02 ATTRIB_03 PAR_ROW_ID NAME TYPE Field Name Date Appraisal Value Comments Par Row Id Name Type Description Date the appraisal is done.
NOTE: The combination of NAME.

select the Field object type (child of Business Component).Configuring the House and Opportunity Entities ■ Configuring the House Detail Appraisals View
5
When done adding all the fields. expand the Business Component object type.
To set the unique fields to be required 1
In the Object Explorer.
4
In the Object Explorer. select the Appraisals business component. The Business Component Wizard creates the business component based on the information you entered.
104
Developing and Deploying Siebel Business Applications Version 8. In the Appraisals business component’s Search Specification field. The Business Component window appears in the Object List Editor.
4
For each of the following fields. PAR_ROW_ID.
Because the combination of NAME. The list of fields that you created in a previous procedure appear in the Fields window of the Object List Editor. select the Field object type (child of Business Component). and TYPE must be unique to satisfy the U1 index of the _XM table. The Business Component window appears in the Object List Editor. In the Business Component window. In the Object Explorer. The list of fields that you created in a previous procedure appear in the Fields window of the Object List Editor.0
. click Finish. expand the Business Component object type. set the check mark on the Required property.
2 3
In the Business Component window.
■ ■ ■
Name Par Row Id Type
To set the search specification for the business component and the Predefault Value of the Type field 1 2 3
In the Object Explorer. these fields must be marked as Required in the Appraisals business component. select the Appraisals business component. enter the following text: [Type]= ‘Appraisals’ This sets the business component to retrieve only those records in which the Type field contains the value Appraisals.

select the Field object type (child of Business Component). The Type field always defaults to Appraisals. The link object establishes the one-to-many relationship between the parent business component (Internal Products) and the child business component (Appraisals).
2 3 4 5
In the Business Component window. select Link. In the Fields window. as shown in the following illustration. you can create a master-detail view to display the data. right-click and choose New Record.
To expose the Row_Id field in the Internal Product business component 1
In the Object Explorer. Before you can create the link. You must create a Link object to establish this relationship. right-click and choose New Record. there can be many Appraisal records. When the relationship exists. Set the Name property to Row_Id and in the Column property select ROW_ID.0
10 5
.
To create a link between Internal Product and Appraisals 1 2
In the Object Explorer. This field is necessary to link with the Par Row Id field in the Appraisals business component. select the Internal Product business component. expand the Business Component object type.Configuring the House and Opportunity Entities ■ Configuring the House Detail Appraisals View
5
Select the Type field and then enter Appraisals as the Predefault Value. In the Links list applet. In the Object Explorer.
Developing and Deploying Siebel Business Applications Version 8. you must expose the Row_Id field in the Internal Products business component. The Business Component window appears in the Object List Editor.
Search Specification for the Appraisals business component Predefault Value for the Type field
Creating a Link Between Houses and Appraisals
The relationship between Houses and Appraisals is one-to-many—for each house record.

The Business Object Component window appears in the Object List Editor. In the Object Explorer. the Opportunity business object is analogous to the Opportunities screen. Name of the parent business component. business objects correspond to a screen in Siebel applications. For example. Generally. Name of the child business component. select the Business Object Component object type (child of business object). expand the Business Object object type. You must associate the Appraisals business component that you create.
106
Developing and Deploying Siebel Business Applications Version 8. In the Object List Editor. They also gather the Link objects that associate two business components with one another. Primary key value in the parent table. Field Name Example Value Internal Product/ Appraisals NREC Configuration Internal Product Appraisals Row_Id Par Row ID Comment The convention is to use the name of the parent and child business component in the name of the link. Foreign key value in the child table.Configuring the House and Opportunity Entities ■ Configuring the House Detail Appraisals View
3
Enter values for the properties as shown in the following table.0
. to the Internal Products business object. Name of the project. as described in “Creating the Appraisals Business Component” on page 102.
To add the business component to a business object 1 2 3
In the Object Explorer. Internal Products business object is the business object on which the Houses screen is based.
Project Parent Business Component Child Business Component Source Field Destination Field
Adding the Appraisals Business Component to a Business Object
Business objects group related business components together. select the Internal Product business object.

Configuring the House and Opportunity Entities ■ Configuring the House Detail Appraisals View
4
In the Business Object Component window. and then click Next. select the templates to use. It displays a list of appraisal records for a single house record. as shown in the following table. Field BusComp Value Appraisals Comments This is the business component you created as described in “Creating the Appraisals Business Component” on page 102. The wizard makes sure you define the correct properties and automatically maps the necessary list columns and controls to the Applet Web Templates. enter the values shown in the following table. and then click Next. Field Project Applet Name Display Title Business Component Value NREC Configuration Appraisals List Applet Appraisals Appraisals
4
In the Web Layout . The type of applet called for in this case is a list applet. you are ready to expose the appraisal data in the user interface. You do this by creating a new applet. You can use the List Applet Wizard to create the applet. In the General dialog box. select List Applet icon and then click OK.
To create the Appraisal list applet 1
Choose File > New Object. The link defines the master-detail relationship between the parent and child business components. The New Objects Wizard appears. enter a new record using the values shown in the following table.
2 3
Under the Applets tab. Field Template for Base read-only mode Template for Edit List mode Template for Edit mode Value Applet List (Base/EditList) Applet List (Base/EditList) Applet List Edit (Edit/New/Query)
Developing and Deploying Siebel Business Applications Version 8.
Link
Internal Product/ Appraisals
Create a New Appraisals List Applet
Now that you have configured the business object layer.General dialog box.0
10 7
.

enter the information shown in the following table.Appraisals View Appraisals Internal Product
4 5
In the View Web Layout . The New Applet Wizard creates a new list applet based on the information you entered and displays the applet in Edit Web Layout Mode.
3
In the New View dialog box.
To create the Appraisals view 1
Choose File > New Object.
2
Under the General tab.Appraisals View
Next you need to create a new view to display the Product Form applet and the Appraisals List applet. and then click Next. select the View icon and click OK. select the following two applets and then click Next:
■ ■
Product Form Applet Appraisals List Applet
108
Developing and Deploying Siebel Business Applications Version 8. Field Project View Name View Title Business Object Value NREC Configuration House Detail . In the Finish dialog box. select the View Detail (Parent with Pointer) Web template and then click Next.Fields dialog box.0
. The New Object Wizard appears. leave the controls selected by default and then click Next. Choose File > Close. select the following fields and then click Next. review the information entered and then click Finish. The New View Wizard opens.Applets dialog box.Configuring the House and Opportunity Entities ■ Configuring the House Detail Appraisals View
5
In the Web Layout .
8 9
You can preview the applet by right-clicking in the Layout window and then choosing Preview. Use the New View wizard to complete the steps.Select Template dialog box.
■ ■ ■
Appraisal Value Date Name
6 7
In the second Web Layout . In the Web Layout .
Creating the House Detail .Fields dialog box.

Field View Type Parent Category Viewbar Text Menu Text Value House Detail . review the information you entered and then click Finish. ■ ■ ■ ■ Compile your changes. add the record as shown in the following table. In the Screen View window.Appraisals View to the Houses Screen.Appraisals View in the application.
7 8
You can preview the applet by right-clicking in the Layout window and then choosing Preview. In the Object Explorer.Appraisals View to the Houses Screen
After you have created the view. In this case. NREC adds the House Detail .0
10 9
. do the following. you need to associate it with a screen. expand the Screen object type. read “Creating the House Detail View” on page 96. Register the House Detail .Appraisals View Detail View NREC Appraisals Appraisals
Compiling and Unit Testing
After you have completed your configuration work. The New View wizard creates the applet and the necessary supporting objects and opens the applet in the Edit Web Layout mode. select the Screen View object type (child of Screen).Configuring the House and Opportunity Entities ■ Configuring the House Detail Appraisals View
6
In the Finish dialog box. In the Object Explorer.Appraisals View to a responsibility that you can use to test.
Adding the House Detail . Unit Test your work. select the NREC House Screen. Use the procedure “To create a symbolic string” on page 72. Choose File > Close. Add House Detail .
To associate the House Detail . The Screens window appears in the Object List Editor.
Developing and Deploying Siebel Business Applications Version 8.Appraisals view to the Houses Screen 1 2
Create a symbolic string with the text “Appraisals”. For the detailed procedure.
3 4 5
In the Screens window.

For detailed information about extending the database. many of the attributes that NREC needs to track for each opportunity are not part of the standard Siebel data model. For example. However. House Detail .0
.Appraisals View
Configuring the Opportunity Details View
NREC uses Partner Portal’s standard Opportunity Details view so partner agents can enter and display information about opportunities. read Configuring Siebel Business Applications.Appraisals View as it is rendered at run time.
Figure 19. the standard data model does not include the number of bedrooms or bathrooms that a potential buyer may be interested in. The additional attributes are: ■ ■ ■ ■ ■ Agent Number of Bathrooms Number of Bedrooms Price Range Square Feet
NREC follows an approach similar to what they did for the Houses entity—add columns to the base table and then modify the objects at the business logic layer and user interface layer accordingly.Configuring the House and Opportunity Entities ■ Configuring the Opportunity Details View
Figure 19 shows the House Detail . The high-level configuration tasks are: ■ ■ ■ ■ “Adding Additional Columns to the Opportunity Base Table” on page 111 “Adding Fields to the Opportunity Business Component” on page 112 “Modifying Applets to Display Additional Attributes” on page 113 “Compiling and Unit Testing” on page 116
110
Developing and Deploying Siebel Business Applications Version 8.

The Opportunity Detail view is the default view for the Opportunities screen.Configuring the House and Opportunity Entities ■ Configuring the Opportunity Details View
Figure 20 shows a mock-up design for the Opportunity Detail View. For detailed instructions. The procedure is covered here at a high-level. Opportunity Detail View Mock-Up
Adding Additional Columns to the Opportunity Base Table
The steps for adding columns to the base table are the same steps you followed to add additional columns to the internal products table. The mock-up shows both the standard fields and the fields added for NREC. The Opportunity Form applet is the detail applet. It is a list-form view. review the tasks covered in “Extending the Database by Adding New Columns to the Base Table” on page 89.
Figure 20.0
11 1
.
Developing and Deploying Siebel Business Applications Version 8. The Opportunity List Applet is the master applet.

Configuring the House and Opportunity Entities ■ Configuring the Opportunity Details View
To add additional columns to the Opportunity base table 1 2
Navigate to the Opportunity base table S_OPTY. For detailed instructions.
Adding Fields to the Opportunity Business Component
After extending the database to support NREC’s additional attributes. Add the column records as shown in the following table. Add the fields as shown on the following table. The steps covered in this procedure are at a high-level. and then change the value of the Project property to NREC Configuration. Name Agent Number of Bathrooms Number of Bedrooms Price Range Square Feet Column X_AGENT X_BATHROOMS X_BEDROOMS X_PRICE_RANGE X_SQUARE_FEET
These fields are now available to expose in the user interface. You do this by adding the fields to the Opportunity business component. review the procedures covered in “Configuring the Internal Product Business Component” on page 92. Lock the project locally.
112
Developing and Deploying Siebel Business Applications Version 8. Name X_AGENT X_BATHROOMS X_BEDROOMS X_PRICE_RANGE X_SQUARE_FEET Type Varchar Varchar Varchar Varchar Varchar Length 50 20 20 20 20
3
Apply the schema to the local database.0
. The fields map to the extension columns in the S_OPTY.
To add fields to the Opportunity business component 1 2 3
Navigate to the Opportunity business component. you need to define the fields in the business object layer.

NREC’s design is to modify the default applets that appear on the Opportunity Detail View to include the new fields. Name Agent Contact Number of Bathrooms Number of Bedrooms Price Range Square Feet Field Agent Key Contact Id Number of Bathrooms Number of Bedrooms Price Range Square Feet Display Name Agent Contact Bathrooms Bedrooms Price Range SQFT Show in List TRUE TRUE TRUE TRUE TRUE TRUE
The list columns are now available to map to applet Web templates. modifying existing objects is typically a preferable method because it requires less configuration work and causes fewer problems with future upgrades. the next step is to expose them in the user interface. The following procedures are the high-level steps required for modifying the existing Opportunity list and form applets to display new fields added to the Opportunity business component. If the Show in List property is FALSE or null. Delete all unnecessary list columns that are not shown in Figure 20 on page 111.
4 5
Reselect the Opportunity List Applet (SCW) applet. Add the List Columns as shown in the following table. The columns to delete include:
■ ■ ■
Revenue Close Date Lead Quality
Developing and Deploying Siebel Business Applications Version 8. Read “Exposing Fields in the User Interface” on page 82. Open the Web Layout Editor. The Show in List property determines whether the field appears by default in the list applet. Use the procedure “To create a symbolic string” on page 72. Navigate to the Opportunity List Applet (SCW). However. the procedures differ slightly for form and list applets.Configuring the House and Opportunity Entities ■ Configuring the Opportunity Details View
Modifying Applets to Display Additional Attributes
Now that the fields are added to the business component. As discussed in the previous chapter.
To expose the new fields on the Opportunity List Applet (SCW) 1 2 3
Create a symbolic string for the term “Price Range”.0
11 3
. users can add it to the list applet at run time by choosing Display Columns from the applet-level menu. These two applets are: ■ ■ Opportunity List Applet (SCW) Opportunity Form Applet (SCW)
An alternative is to create new applets.

0
11 5
.
Developing and Deploying Siebel Business Applications Version 8. Delete all unnecessary controls that are not shown in Figure 20 on page 111.Configuring the House and Opportunity Entities ■ Configuring the Opportunity Details View
To expose new fields on the Opportunity Form Applet (SCW) 1 2
Navigate to the Opportunity Form Applet (SCW). Name Agent Contact Number of Bathrooms Number of Bedrooms Price Range Square Feet Caption Agent Contact Bathrooms Bedrooms Price Range SQFT Field Agent Key Contact Id Number of Bathrooms Number of Bedrooms Price Range Square Feet
3 4
Reselect the Opportunity Form Applet (SCW) applet. Add the Controls as shown in the following table. press the Ctrl key while selecting. The controls to delete include:
■ ■ ■ ■ ■ ■ ■ ■ ■
Description Site Probability % Close Organization Revenue Expected Value Committed Sales Team
NOTE: To select multiple controls. Open the Web Layout Editor and select an active mode.

Compiling and Unit Testing
After you have made your changes you are ready to compile and Unit Test your results. Modified Opportunity List and Form Applets
116
Developing and Deploying Siebel Business Applications Version 8. When done.
6
Repeat Step 4 on page 115 and Step 5 for each active applet mode. the Web layout resembles the following illustration.Configuring the House and Opportunity Entities ■ Configuring the Opportunity Details View
5
Map the controls you created in Step 2 on page 115 to complete the layout as shown in Figure 20 on page 111.
Figure 21. Figure 21 shows what the applets look like after being modified.0
.

then troubleshooting errors may be a major effort. In the event a test fails.Configuring the House and Opportunity Entities ■ Testing the House and Opportunity Entities
Testing the House and Opportunity Entities
NREC’s testing plan calls for periodic integration and regression testing.0
11 7
. If these tests are performed too infrequently. and to make sure that the application still can interact with other applications and products.
Developing and Deploying Siebel Business Applications Version 8. These tests are necessary to make sure that the changes you have made up to this point do not prevent previously existing features from working. NREC can quickly locate the faulty configuration change and make the appropriate modifications. NREC’s test plan makes sure these checks happen at specific strategic intervals in the configuration process.

0
.Configuring the House and Opportunity Entities ■ Testing the House and Opportunity Entities
118
Developing and Deploying Siebel Business Applications Version 8.

The list of values table is maintained by an administrator.0
11 9
.
Developing and Deploying Siebel Business Applications Version 8. Drilldowns. “Configuring Pick Lists” “Creating Drilldowns” on page 126 “Configuring Multi-Value Groups” on page 129 “Testing the Configuration Changes” on page 132
Configuring Pick Lists
NREC wants to take advantage of pick lists to standardize data entry and minimize mistakes. Dynamic pick lists draw their data from user-maintained tables. There are two types of pick lists: static and dynamic. You will work with some new objects as well as some of the objects that you configured in previous chapters. Static pick lists draw their data from the Siebel list of values table. Using pick lists you can populate a field by choosing values from a list rather than typing them in fields.8
■ ■ ■ ■
Pick Lists. and MVGs
This chapter takes a second pass at configuring. You can complete the tasks in this chapter using your sample database.

To complete the NREC configuration. Drilldowns. When the user clicks the drop-down arrow to the right of the field. The values in the pick list are predefined by an administrator or developer and stored in the list of values table.
Figure 22. A bounded pick list restricts the user to choose values from the list only. and MVGs ■ Configuring Pick Lists
Static Pick Lists
A static pick list is a list of predefined values that the user invokes from a field in an applet. ■ ■ ■ ■ Bathrooms Bedrooms Price Range Square Feet
The following procedure uses the Price Range field on the Opportunities business component as an example. Static Pick List A pick list can be bounded or unbounded. create pick lists for the remaining fields as well. With an unbounded pick list the user can choose a value from the list or type a entry directly into the field.0
. The New Objects Wizard appears. Figure 22 shows a pick list for the Price field. The user chooses a value from the list. and then clicks Save to enter the value for the field. NREC’s requirement is to have pick lists for the following fields on the Opportunity business component.
To create a new static pick list 1
Choose File > New Object.
120
Developing and Deploying Siebel Business Applications Version 8.Pick Lists. a single-column pick list appears.

and so on
8
In the next Pick List Definition dialog box. The wizard creates the Pick List object and related objects and adds the list of values to the database.100. In the List of Values dialog box.000 200.000 . click the Create new List of Values option button.000 .
4 5 6 7
Click the Static option button and then click Next. enter a comment in the Comment field and leave the Search Specification and Bounded Pick List check boxes blank.000 150.200.150. and then click Next. click the Create new Pick List option button and then click Next. and MVGs ■ Configuring Pick Lists
2
Under the General tab. The Pick List Type dialog box appears. for each value to appear in the list. In the next Pick List Definition dialog box.000 . enter the value shown in the following table. The Pick List wizard opens. enter Price Range as the name of the pick list. and it displays the controls that map to the field you selected in Step 3.000 .Pick Lists. Field Name Value Value Price 0 . and then click Next. and then click OK. In the Pick List Definition dialog box. Not selecting the Bounded check box allows the user to type in a value or choose one from the list. select the Pick List icon.
3
In Pick List dialog box. Field Project Business Component Field Value NREC Configuration Opportunity Price Range
The field is one you created in “Adding Additional Columns to the Opportunity Base Table” on page 111.
9
In the Finish dialog box..250. and then click Enter. A bounded pick list forces the user to enter a value that has been predefined on the list.. review the information and then click Finish.
Developing and Deploying Siebel Business Applications Version 8.0
12 1
. enter the values shown in the following table. Drilldowns. enter a name for the list and then.000 100.

For the current example lock the Action business component locally and then change the value of the Project property to NREC Configuration. Pop-up applet that displays the a list of records from which the user can choose.
Before creating a dynamic pick list you must lock the projects for both the pick business component and the originating business component.
Dynamic Pick Lists
Like static pick lists. a dynamic pick list draws its values from another user-maintained business component. which includes: ■ Pick List. The NREC design includes a dynamic pick list on the Activity Detail Applet. In the current example.
To create a dynamic pick list 1 2 3
Select the Action business component and lock it. In the current example. In the General Tab. In previous chapters. NOTE: The originating business component is the one on which you are creating the dynamic pick list. Notice that the pick list is available on the Price field in both the list and the form applet. dynamic pick lists populate fields by presenting the user with a list of values. you have already associated the Opportunity business component with the NREC Configuration project.0
. Choose File > New Object. The opportunity field that you exposed on the applet (read “Adding the Opportunity Field to a Activity Detail Applet (SCW)” on page 83) is a joined field. rather than drawing the values from the list of values table. and MVGs ■ Configuring Pick Lists
10 Compile and Unit Test. including the originating business component and the pick business component. which is locked. See Figure 22 on page 120. The Pick List Wizard helps you through the process of creating a dynamic pick list and related objects. select the Pick List icon. ■ ■ Pick Maps. it is the Opportunity business component.Pick Lists. Drilldowns.
122
Developing and Deploying Siebel Business Applications Version 8. The pick business component is the one from which you are picking values to display to the user. and then click OK. Child object of a business component field that map the source field in the pick business component with the target field in the originating business component. Creating a dynamic pick list on this field allows users to update the activity record by pulling in the opportunity name from the Opportunity table. Change its Project property to NREC Configuration. it is the Action business component.
The pick list appears as a drop-down list on the Price fields in the user interface. However. Fields that use dynamic pick lists are typically joined fields displaying data from a table other than the business component’s base table. Pick Applet. Object that defines the properties of the pick list.

In the Pick Map dialog box. Field in Originating Business Component Opportunity Field in Pick Business Component Opportunity Oppty Id This information is used to define the Pick Maps for the Pick List. accept the defaults.
Created Opportunity NREC leave blank Describe this pick list
8 9
In the Pick List Specifications dialog box.
Field
Opportunity
5 6 7
In the Pick List Type dialog box. and then click Next. Name of the Pick List. enter the values shown in the following table. Field Pick Business Component (business component to base the pick list on) Field to sort by Name Search Specification Comment Value Opportunity Description This is the business component from which you are drawing values to display to the user. Drilldowns. click the Dynamic option button and click Next. enter the values shown in the following table. Enter a comment that will help you identify this pick list in the future.Pick Lists. In the Pick List Definition dialog box. They are the mappings between the source field and the target field. click the Create New Pick List option button and click Next. Business component in the project that contains the field for which you are defining the pick list. and then click Next. leave the check boxes clear. Field Project Business Component Value NREC Configuration Action Description Project to which the pick list will belong. In the next Pick List Definition dialog box. use the drop-down lists to choose the fields shown in the following table.
Developing and Deploying Siebel Business Applications Version 8. and MVGs ■ Configuring Pick Lists
4
In the Pick List dialog box. and then click Add.0
12 3
. This is optional. Records are sorted by this field in the pick applet. Field for which you are defining the pick list.

These two fields must match for the record to be displayed in the pick applet. You can create more than one constrain pick map. Drilldowns. Constrain pick maps do not copy the values of the field from the originating business component to the pick business component.
124
Developing and Deploying Siebel Business Applications Version 8. This pick map defines fields on the originating business component and a field on the pick business component. If an appropriate pick applet did not exist. configured in the previous section. there is already an Opportunity pick applet defined. then the New Applet Wizard opens. you can constrain the Opportunity pick applet. To constrain a pick list you create another pick map with a Constrain property set to TRUE. pick maps. For example. to display only the opportunities for the account associated with the activity. Following the NREC example. review the information you entered and then click Finish.Pick Lists.
11 Compile and Unit Test. you constrain the list of records displayed in the Opportunity Pick Applet based on the Account field. and determines if a pick applet already exists that can be used to display the records. so the New Applet Wizard does not open. and MVGs ■ Configuring Pick Lists
10 In the Finish dialog box.
NOTE: Be sure to compile the Activity project.
The Pick List wizard creates the pick list.
Opportunity Pick Applet displays records from the Opportunity business component
Dynamic pick list on the Opportunity field
Constraining a Pick List
You can filter a pick applet to display only records that have field values that match corresponding fields in the originating business component’s records. The results resemble the following illustration. They serve as a filter to determine which records appear in the pick applet.0
. For the NREC example.

To test.
7
Compile and Unit Test. Drilldowns. In the Object Explorer. and opportunities. In the Object List Editor. In the Object List Editor.
3 4 5 6
In the Object Explorer.Pick Lists. select the Opportunity field. In the Object List Editor. Select an activity and then open the Opportunity pick list. Field Account Name Pick List Field Account Constrain TRUE
The Account Name field on the originating business component must match the Account field on the pick list business component for the record to be displayed in the pick applet. The Action business component is the originating business component. NOTE: The Opportunity business component is the pick business component.
Developing and Deploying Siebel Business Applications Version 8. The Pick Opportunity list shows only the opportunities that match the selected account. expand the Business Component object type. you need to have some data entered for accounts. and MVGs ■ Configuring Pick Lists
To create a constrain pick map 1 2
In the Object Explorer. enter the record as shown in the following table. expand the Field object type (child of Business Component). select the Action business component. activities.0
12 5
. The Opportunity Field is the field from which the pick applet is invoked. select the Pick Map object type (child of Field).

When you click on the drilldown on the left. you drill down to the Opportunity Detail Contacts view as shown in Figure 23. such as the value of a field. A static drilldown always takes the user to the same view. and MVGs ■ Creating Drilldowns
Creating Drilldowns
Using drilldowns. Drilldowns. A dynamic drilldown can take the user different views depending on certain conditions. Fields with drilldowns appear as hyperlinks in the user interface.Pick Lists.0
. the view below appears.
Figure 23. when you click on the Name field in the Opportunity List Applet. Drilldown Example Drilldowns can be either static or dynamic. For example.
126
Developing and Deploying Siebel Business Applications Version 8. users can click a field and display another view that has more information about the field.

For a dynamic drilldown. For the current example. For example. NREC wants to configure the drilldown shown in Figure 23 on page 126 so that it is dynamic.
Field on which the drilldown behavior is implemented
Destination view for the drilldown
Figure 24. such as the value of a field. and MVGs ■ Creating Drilldowns
You configure drilldowns in Siebel Tools. When the conditions expressed in the dynamic drilldown destinations are false.Activities view. Drilldowns. The Drilldown object type is a child object of the Applet object type.Pick Lists. ■ Define a drilldown object for the Opportunity Detail . The requirement is the following: ■ ■ If the opportunity sales stage is Prospecting.
Developing and Deploying Siebel Business Applications Version 8. you define each candidate view by creating a drilldown object. For example. the parent drilldown acts as the default. Otherwise. the drilldown object definition for the Name field of the Opportunity List applet as shown in Figure 24.Contacts view. Static Drilldown
Creating a Dynamic Drilldown
A dynamic drilldown links to a different view depending upon certain conditions. Qualification. It defines the field on which the drilldown behavior is to be implemented and the view that appears when the user clicks the field. Dynamic drilldown destinations are defined as child objects of the default drilldown object.
Dynamic drilldowns require one or more dynamic drilldown destination object types. They are child objects of a drilldown object. Dynamic drilldown destination objects define the conditions that determine when to go to a particular drilldown object.Activities View (SCW). or Closing. go to the Opportunity Detail . Note that this is the behavior of the existing drilldown object. you need to do the following.0
12 7
. go to the Opportunity Detail . You express the conditions under which each drilldown object is activated by defining one or more dynamic drilldown destinations.

In the Dynamic Drilldown Destinations applet.
3 4
In the Object Explorer. select the drilldown object named Original. enter a new record using the values shown in the following table. select the Drilldown Object object type. Drilldowns.
2 3
In the Object Explorer. and MVGs ■ Creating Drilldowns
■
Define destination drilldown objects as children of the Original drilldown object. select Dynamic Drilldown Destination object type (a child object of Drilldown Object).Contacts (SCW) view or Opportunity Detail . Destination Drilldown Object Activities Activities Activities
Name Prospecting Qualification Closing
Field Sales Stage Sales Stage Sales Stage
Value 01 .Qualification 03 . In the Drilldown Object list. This is the applet from which the user can drill down.Activities (SCW) depending on the value of the Sales Stage field.Activities (SCW)
To create Drilldown Destination Objects 1
Select the drilldown object to serve as the parent (default) of your dynamic drilldown destinations. NOTE: Original is the existing drill drilldown object. When you drill down on the name column it takes you to Opportunity Detail . The target view defined in this drilldown object serves as the default for when the conditions in the Drilldown Destination objects are false. enter the records as shown in the following table.Closing
Sequence 1 2 3
4
Compile and Unit Test. This drilldown serves as the default when the conditions expressed in child drilldown destination objects are false.Prospecting 02 .
128
Developing and Deploying Siebel Business Applications Version 8. expand the Applet object type. Field Name Hyperlink Field View Values for First Drilldown Activities Name Opportunity Detail . For the current example. Navigate to the Opportunity List Applet.0
. In the Object List Editor.Pick Lists.Contact view. It displays the Opportunity Detail .
To create a dynamic drilldown object 1 2
In the Object Explorer. select the Opportunity List Applet (SCW).

The results of the configuration work are shown in Figure 25. Multi-Value Field
Creating an MVG
You can use the MVG Wizard to create the objects necessary for MVGs. For example. and an MVG applet pops up displaying a set of child records. and MVGs ■ Configuring Multi-Value Groups
Configuring Multi-Value Groups
Multi-value groups (MVGs) incorporate child data into an applet. The New Object Wizards dialog box appears. They provide you with a way to display multiple child records for a single parent record. ■ ■ ■ Multi-Value Link Multi-Value Field Multi-Value Group Applet. NREC’s requirement is to create a MVG on the Opportunity Form Applet (SCW) to display the contacts associated with each opportunity. the user clicks the select button in a multi-value field.
Developing and Deploying Siebel Business Applications Version 8. Instead. if necessary
To configure a multi-value field using the MVG Wizard 1
Choose File > New Object.Pick Lists. the wizard creates the following objects that are necessary to implement the MVG. Drilldowns. yet they do not require a master-detail view. Based on the information you enter.
Multi-value field MVG Applet
Figure 25.0
12 9
.

In the Multi Value Fields dialog box. Drilldowns. Opportunity is the parent business component in the Opportunity/Contact Link object.
4
In the second Multi Value Group dialog box. Click Add and then click Next.
7 8
In the Multi Value Link dialog box. select the Opportunity/Contact link and then click Next. Unique name for the Multi Value Link object. choose the Last Name field. For example. and then click Next. Field Project Master Business Component Value NREC Configuration Opportunity Description Project to which the MVG will belong.0
. use the drop-down list to choose a field from the detail business component to use to create the multi-value field in the master business component.Pick Lists.
a b c
From the drop-down list. The Multi Value Group wizard appears. leave every check box clear. The name of the master business component. enter the values as shown in the following table. click the MVG icon and then click OK. do not select any fields or check boxes. and then click Next. doing so can have performance benefits by reducing the number of SQL queries that are executed to populate the MVG for each record.
130
Developing and Deploying Siebel Business Applications Version 8. For example.
6
In the Primary ID Field dialog box. accept the default for Multi Value Link properties.
3
In the Multi Value Group dialog box. Contact is the child business component defined in the Opportunity/Contact link object. Use the default value of NREC Contact Last Name for the Multi Value Field Name. and MVGs ■ Configuring Multi-Value Groups
2
Under the General tab. NOTE: Although this procedure does not cover implementing primaries.
NREC Contact
5
In the Direct Links dialog box. This dialog box displays every link that describes a master-detail relationship between the business components defined in Step 3 and Step 4. Field Detail Business Component Multi Value Link Name Value Contact Description This is the name of the detail business component. enter the values as shown in the following table. Click Next.

Exposing the MVG in the User Interface
After you create the underlying objects necessary to display the MVG. See Figure 25 on page 129. the MVG Applet Wizard opens so you can define one. review the information you entered and then click Finish. select the Opportunity Form (SCW) applet. If a suitable applet is not found. The multi-value field appears in the applet with a select button next to it. Select the Contact control. In the current example. It also searches the repository for an existing multi-value group applet that can be used to display the data in the user interface. Drilldowns. the Contacts MVG Applet already exists.
5
Compile and Unit Test. Change the fields as shown in the following table.
Developing and Deploying Siebel Business Applications Version 8. and MVGs ■ Configuring Multi-Value Groups
9
In the Finish dialog box. Expand the Control object type (child of Applet). You could also have created a new MVG applet using the MVG Applet Wizard.
To expose the MVG in the user interface 1 2 3 4
In the Object Explorer. The Opportunity Form (SCW) applet already has a Contact field. It needs to be redefined so it shows the Contact MVG.Pick Lists. When the user clicks the select button. you can expose the multi-value field in the user interface. Field Field MVG Applet Runtime Current Value Key Contact Id <blank> FALSE New Value NREC Contact Last Name Contact MVG Applet TRUE
NOTE: The Contacts MVG is suitable for NREC’s purposes. The Multi Value Group Wizard uses the information you entered to create the necessary objects for a multi-value group. so the MVG Applet wizard does not open. the MVG applet appears.0
13 1
.

and that the application still can interact with other applications and products. NREC’s test plan makes sure these checks happen at specific strategic intervals in the configuration process. In the event a test fails.Pick Lists. If these tests are performed too infrequently. NREC can quickly locate the faulty configuration change and make the appropriate modifications. These tests are necessary to make sure that the changes you have made up to this point do not prevent previously existing features from working. Drilldowns. and MVGs ■ Testing the Configuration Changes
Testing the Configuration Changes
NREC’s testing plan calls for periodic integration and regression testing. then troubleshooting errors may be a major effort.0
.
132
Developing and Deploying Siebel Business Applications Version 8.

9

Creating a Virtual Business Component

This chapter describes creating a virtual business component. It follows the NREC example, building on work you did in Chapter 7, “Configuring the House and Opportunity Entities,” for configuring the House entity. Read this chapter for a general overview of virtual business components and the steps for configuring them. Keep in mind that this example is relatively simple. It uses a simple file as an external data source rather than an external database or external application. For more information about how virtual business components can be used to integrate external data, read Overview: Siebel Enterprise Application Integration and Integration Platform Technologies: Siebel Enterprise Application Integration.

Virtual business components are based on business services. Business services determine the behavior of the VBC and define how the VBC manipulates data. You can base VBCs on predefined business services provided by Oracle, such as the XML Gateway, or you can create your own business service. You create both virtual business components and business services in Siebel Tools.

Developing and Deploying Siebel Business Applications Version 8.0

13 3

Creating a Virtual Business Component ■ NREC’s Virtual Business Component

NREC’s Virtual Business Component
Assume that NREC stores house renovation data in a comma-delimited text file that a third-party vendor provides to NREC. NREC’s design includes a virtual business component used to retrieve the data from the file and display it in the Partner Portal application. Partner agents and NREC employees can use it to display a history of renovation information for each house stored in NREC’s Siebel database. Figure 26 shows NREC’s external file of renovation data. Figure 27 shows how the data from this file is displayed in the user interface.

Figure 26. NREC’s External File of Renovation Data NREC’s requirement is to display this data in a standard master-detail view showing a house record in the top applet and a list of renovations in the bottom applet.

Figure 27. Applet Displaying Data from a VBC The steps for configuring a virtual business component for the NREC’s scenario are: ■ ■ ■ ■ ■ “Creating a Business Service” on page 135 “Creating a Virtual Business Component” on page 137 “Creating Fields for the Virtual Business Component” on page 138 “Defining User Properties for the Virtual Business Component” on page 138 “Creating a Link” on page 139

134

Developing and Deploying Siebel Business Applications Version 8.0

Creating a Virtual Business Component ■ Creating a Business Service

■ ■ ■

“Updating the Business Object” on page 140 “Exposing the Fields in the User Interface” on page 140 “Creating a New View” on page 141

Creating a Business Service
Business services are objects that define sets of functionality. For example, a business service can perform tasks such as moving data or converting data formats. Like business components, business services are objects stored in the Siebel repository. However, rather than interacting with tables and data as business components do, business services interact with other objects. Virtual business components use business services to provide the functionality to manipulate external data. Business services define the methods, properties, and states that determine the behavior of virtual business components. There are many predefined business services provided for specialized needs, such as using XML to display data in a Siebel application. You can also create your own business services. In the NREC example, you use Siebel Tools to create a business service that reads and writes data to a commadelimited text file. For more information about business services, read Siebel Object Interfaces Reference and Integration Platform Technologies: Siebel Enterprise Application Integration. In the NREC example, the steps for creating the business service are: ■ ■ “Defining the Business Service” on page 135 “Defining Business Service Scripts” on page 136

Defining the Business Service
You create business service objects using Siebel Tools.

To define a business service 1 2 3
Create a symbolic string for the term “NREC Text File Handler”. In the Object Explorer, expand the Business Service object type. In the Business Services window, enter a new record as shown in the following table. Field Name Project Class Display Name Value NREC Text File Handler NREC Configuration CSSService NREC Text File Handler

Developing and Deploying Siebel Business Applications Version 8.0

13 5

Creating a Virtual Business Component ■ Creating a Business Service

Defining Business Service Scripts
After defining the Business Service, you can define the business service scripts that actually do the processing associated with the NREC Text File Handler business service object. Sample code for this example is shown in “Code Samples” on page 143. Business Service methods to implement are listed in Table 10.

Table 10. Method Init

Business Service Methods Custom Method Name in Code Sample Pal_Init Description Creates the initial link between the columns in the VBC and the columns in the external data source. Inserts a record into the external data source. Provides any default values for new rows. In the current example, there are no default values. Queries the external data source and returns rows that match a given value. In the current example, the method queries the text file and returns rows that have a matching value for the current House_ID field. Handles requests that come into the business service and calls other functions as appropriate. Updates an existing row in an external data source. Deletes a row in the external data source.

Insert PreInsert

Pal_Insert Pal_PreInsert

Query

Pal_Query

Service_PreInvokeMethod

Service_PreInvokeMethod

Update Delete

Not used in sample code Not used in sample code

For more information about business service methods, read Siebel Object Interfaces Reference.

To define and write the business service script for NREC Text File Handler 1 2 3
Select the NREC Text File Handler business service. With the business service selected, right-click, and then choose Edit Server Scripts. Select Visual Basic as the scripting language and then click OK. The script editor appears with Service_PreInvokedMethod selected as the service.

4

Enter the custom functions by doing the following.

136

Developing and Deploying Siebel Business Applications Version 8.0

Creating a Virtual Business Component ■ Creating a Virtual Business Component

a b c d

Expand the (general) icon in the script editor and then select the (declarations) icon. In the text entry window, enter the code for the custom function. Choose File > Save.

An icon representing the function appears in the left pane as shown in the following illustration. Repeat Step a through Step c for each custom function.

5 6

Select the Service_PreInvokeMethod icon. Copy the sample code into the text entry window, replacing the existing stub text. Choose File > Save. After saving your work, Business Service Server Script objects are available, as shown in the following illustration.

Creating a Virtual Business Component
When creating a virtual business component you do not use the Business Component Wizard because it forces you to select a table on which the business component is to be based and does not set the class to CSSBCVExtern.

To create a virtual business component 1 2
In the Object Explorer, select the Business Component object type. Right-click in the Object List Editor and choose New Record.

Developing and Deploying Siebel Business Applications Version 8.0

13 7

Field Name Project Class Value NREC Renovations VBC NREC Configuration CSSBCVExtern Comments Unique name for the virtual business component Choose a locked project Provides the virtual business component functionality
Creating Fields for the Virtual Business Component
After creating the virtual business component you need to create the fields to display in the Siebel application. In the Object List Editor.Creating a Virtual Business Component ■ Creating a Virtual Business Component
3
Enter Values for the following properties as shown in the following table. select NREC Renovations VBC. select Single Value Field object type (child of Business Component).
138
Developing and Deploying Siebel Business Applications Version 8. Enter each of the records as shown in the following table. Read the Pal_Init function in the “Code Samples” on page 143. the parameters are defined in the script attached to the business service. These fields display data retrieved from the House Renovations file shown in Figure 26 on page 134. NREC’s requirement is to define the following fields for the business component: ■ ■ ■ Date Description House_ID
To add fields to the virtual business component 1 2 3 4
In the Object Explorer. In the Object Explorer. Name Date Description House_ID Type DTYPE_TEXT DTYPE_TEXT DTYPE_TEXT Comments Date the renovation was recorded Description of the renovation House Identification Number
Defining User Properties for the Virtual Business Component
The user properties required by the NREC Renovations VBC are Service Name and Service Parameters. The Service Name user property defines which business service the VBC invokes. In this example.0
. The Service Parameters define the parameters that are passed into the business service upon initialization. expand the Business Component Object type.

Creating a Virtual Business Component ■ Creating a Link
To define virtual business component user properties 1
Select the NREC Renovations VBC business component. select the Business Component User Prop object type (child of business component). Field Name Project Parent Business Component Value Internal Product/NREC Renovations VBC NREC Configuration Internal Product Description Unique name for the link. The script for the current example specifies the service parameters as the full path to the file name. User Property Name Service Name Service Parameters
Value NREC Text File Handler D:\NREC\nrec. Add the user properties records as shown in the following table.Description
Comments Name of the business service. then clicking the Object Explorer tab. Date. Project to which the object belongs.House_ID. See NREC’s entity relationship diagram shown in Figure 3 on page 28. and there can be no spaces in the comma-delimited strings. Therefore. Internal Product is the business component that NREC is using to store houses. The check box for Business Component User Prop is in the Business Component hierarchy.0
13 9
.
To create a link between parent and child business components 1 2
Select the Link object type. Service parameters vary depending on the business service being used. NOTE: If the Business Component User Prop is not visible in the Object Explorer. then you need to make it visible by choosing View > Options to display the Development Tools Options dialog box. there can be many renovations recorded for one house.
Developing and Deploying Siebel Business Applications Version 8. and column names.3.
2 3
In the Object Explorer. add a new record as shown in the following table. you need a link to create the parent-child relationship between the Internal Product business component and the NREC Renovations VBC business component. Parent business component. In the Links window. The parameters must be separated by semicolons.txt.
Creating a Link
The relationship between houses and house renovations is one to many (1:M). number of columns.

The steps to do this include: ■ ■ ■ “Creating a New List Applet” on page 141 “Creating a New View” on page 141 “Adding the View to a Screen” on page 142
140
Developing and Deploying Siebel Business Applications Version 8. you can expose the fields defined in the NREC Renovations VBC in the user interface. Column in the child record that stores the parent ID. Often this field is Row Id. In this case. Field Business Component Link Value NREC Renovations VBC Internal Product/NREC Renovations VBC
The NREC Renovations VBC business component is added to the Internal Product business object.0
.
Destination Field
House_ID
Updating the Business Object
Like any business component. Select the Business Object Component object type (child of business object). Select the Internal Product business object. Unique ID on the parent record. add a new record as shown in the following table.Creating a Virtual Business Component ■ Updating the Business Object
Field Child Business Component Source Field
Value NREC Renovations VBC Part #
Description Child Business component.
To add the Renovations business component to the Internal Product business object 1 2 3 4
Expand the Business Object object type. a virtual business component must be grouped together with objects of similar focus using a business object. you need to add the Renovation VBC business component to the Internal Product business object. Now that you have a link defined for the Internal Product/ NREC Renovations VBC relationship. In the Business Object Components window. the unique field is a manually entered value.
Exposing the Fields in the User Interface
When the business object layer has been configured.

In the next section. The New Object dialog box appears.
Creating a New View
To display the Renovations list applet you need to add it to a view. NREC requires a standard masterdetail view. In the New Objects Wizard dialog box.Creating a Virtual Business Component ■ Exposing the Fields in the User Interface
Creating a New List Applet
To display the data from the NREC Renovations VBC you must create a new applet. This displays the renovation records for each house record. Field Project Applet Name Display Title Business Components Web Templates Value NREC Configuration Renovations List Applet Renovations NREC Renovations VBC Base: Applet List (Base/List Edit) Edit List: Applet List Edit (Edit/New/Query) Edit: Applet List Edit (Edit/New/Query) Fields Controls House_ID. you create a master-detail view to contain the applet. select View. Description Accept default controls selected for the applet.
Developing and Deploying Siebel Business Applications Version 8. Complete the wizard using the values as shown in the following table. The NREC design specifies a standard list applet.0
14 1
. Click the Applets tab and then select List Applet.
To create a new view 1 2
Choose File > New Object. To create it you use the List Applet New Object wizard. showing the House Form applet on top and the Renovations list applet on the bottom. The New View Wizard opens.
To create a new list applet to display renovation data 1 2 3
Choose File > New Object. Date.

perform the following tasks. Select the Screen View object type (child of Screen). Field Project Name Title Business Object Web Template Applets Value NREC Configuration House Details .0
. read “Creating the Houses Screen” on page 97.Renovations View Detail View NREC Renovations 30 Renovations
Compiling and Testing
After you have completed your configuration work. Select the NREC House Screen.
142
Developing and Deploying Siebel Business Applications Version 8.Renovations View Renovations Internal Product View Detail (Parent with Pointer) Product Form Applet Renovations List Applet
Adding the View to a Screen
The next step is to add the new view to a screen. For information about the Houses Screen. you add the House Details .Renovations View to the NREC House screen.
To add a view to a screen 1 2 3 4 5
Add a symbolic string for the term “Renovations”. Field View Type Parent Category Viewbar Text Sequence Menu Text Value House Details . In the Screen View window.Creating a Virtual Business Component ■ Compiling and Testing
3
Complete the wizard using the values as shown in the following table. Expand the Screen Object type. add a new record using the properties as shown in the following table. For the current example.

Creating a Virtual Business Component ■ Code Samples
■
Compile your changes. copy the code into the General:Declarations text entry window. ■ ■ ■ ■ ■ “(declaration)” “Pal_Init” “Pal_Insert” on page 144 “Pal_PreInsert” on page 145 “Pal_Query” on page 146
(declaration)
Dim Dim Dim Dim Dim FieldCount As Integer NoOfRecords As Integer DataSource As String ColumnsReqd As String VBCName as String
Pal_Init
Sub Pal_Init (Inputs as PropertySet. then choose File > Save.0
14 3
.
■ ■ ■
Code Samples
The following is the code breakdown for the NREC’s example business service. review Figure 26 on page 134. Add House Renovations to a responsibility that you can test. To see what the results look like.Renovations View in the application. the Internal Product business object belongs to the Product project by default. Read “Defining Business Service Scripts” on page 136 for the steps for defining the code and associating it with the business service. Register the House Details . Be sure to compile changes for the projects that contain objects you modified. There are two sets of code to be copied: ■ ■ “Code to Copy into General:Declarations” “Code to Copy into Service:Service_PreInvokeMethod” on page 149
Code to Copy into General:Declarations
For each of the following code samples. Outputs as PropertySet) Dim theFieldName(100) As String Dim ParamText as String ' Identify setup details of calling VBC and add as Parameter to Service
Developing and Deploying Siebel Business Applications Version 8. Unit Test your work. For example.

* ************************************************************************************
Developing and Deploying Siebel Business Applications Version 8. This service does not provide any defaults.theKey For i = 1 to NoOfValues If InputFields(i) = theKey Then PadReqd = 0 If OutputStr <> "" Then OutputStr = OutputStr & ".OutputStr Close #1 End Sub
Pal_PreInsert
Sub Pal_PreInsert (Outputs As PropertySet) ' ' ' ' ' ************************************************************************************ * A Pre Insert Method is Required before any insert is applied.Creating a Virtual Business Component ■ Code Samples
End If Next i End If ' *********************************************************************** ' * Create the Output String for Writing to the File in the right order * ' ************************************************************************* Open DataSource For Input As #1 For Count = 1 To FieldCount PadReqd = 1 ' Identify by default we need a Pad string in the file Input #1. so this points to the first field by default. Its use is * * to provide Default Values." End If OutputStr = OutputStr & " " End If Next Count Close #1 ' *************************************************** ' * Create the Output String In the DataSource File * ' ***************************************************** Open DataSource For Append As #1 Print #1." End If OutputStr = OutputStr & InputValues(i) End If Next i If PadReqd = 1 Then If OutputStr <> "" Then OutputStr = OutputStr & ".0
14 5
. But * * must return a populated property set.

Outputs Service_PreInvokeMethod = CancelOperation ElseIf MethodName = "Delete" Then 'Pal_Delete Inputs . then troubleshooting errors may be a major effort. NREC can quickly locate the faulty configuration change and make the appropriate modifications.Creating a Virtual Business Component ■ Testing the Virtual Business Component
Pal_Insert Inputs. NREC’s test plan makes sure these checks happen at specific strategic intervals in the configuration process. Document these changes in an Entity-Relationship Diagram (ERD).
Documenting Your Changes in an ERD
NREC has made changes to data objects (Chapter 7. and that the application still can interact with other applications and products. These tests are necessary to make sure that the changes you have made up to this point do not prevent previously existing features from working. “Creating a Virtual Business Component”).
150
Developing and Deploying Siebel Business Applications Version 8. If these tests are performed too infrequently. “Configuring the House and Opportunity Entities”) and has added a virtual business component (Chapter 9.Not Yet Completed Service_PreInvokeMethod = CancelOperation Else Service_PreInvokeMethod = ContinueOperation End If End Function
Testing the Virtual Business Component
NREC’s testing plan calls for periodic integration and regression testing. In the event a test fails.0
.

Use Figure 28 as a guide. This is a sketch of the relationships between data objects.
4 5
Drag and drop entity shapes from the palette to the canvas. Enter the values as shown in the following table. all seven entities (from Entity0 to Entity6) are listed. Right-click and then choose New Record. In Siebel Tools you can create a true ERD that is stored in the database. NREC Entity Relationship Diagram
To create an entity relationship diagram 1 2
In the Object Explorer. In the Entities list. select the Entity Relationship Diagram object type. The Entity Relationship Diagram Canvas appears.0
15 1
. Click on the canvas background to deselect any shapes.Creating a Virtual Business Component ■ Documenting Your Changes in an ERD
Figure 28 shows the NREC Entity Relationship Diagram. You need seven entity shapes.
Figure 28. Field Name Project Status Value NREC House ERD NREC Configuration Scope
3
Right-click on the record and then choose Edit Entity Relationship Diagram.
Developing and Deploying Siebel Business Applications Version 8.

directly connecting from one entity to another. For example. Repeat Step b and Step c as needed. or M:M) to all entities.
a b c d a b c d
Select a relationship line. Adjust the column display to show the Name.0
.
In the Object Explorer. They do not reshape themselves to avoid other lines or entities. look carefully at the business components and tables listed and select the most appropriate pairing. Use abbreviations or a single word to indicate each entity.
152
Developing and Deploying Siebel Business Applications Version 8.Agent. If there are multiple relationships possible. Add a reshaping point by pressing Ctrl+A.Creating a Virtual Business Component ■ Documenting Your Changes in an ERD
6
Edit the Entity information to name each one and bind it to a business component as shown in the following table. Then you can connect the right side of the line to the next entity. When the relationship binds. Keep the names short to improve legibility. the line thickness increases. Entity 1. with the Independent Agency (Partner) link to Real Estate Agent. The lines start off as straight lines.
10 Edit relationship line names. 1:M. and Entity 2 columns. Entity Entity0 Entity1 Entity2 Entity3 Entity4 Entity5 Entity6 Name House Renovations (VBC) House (Product) Appraisals Buying Interest Activity Plan Contact Independent Agency (Partner) Business Component NREC Renovations VBC Internal Product Appraisals Opportunity Activity Plan Contact Account Home Search
7
Add relationship lines (1:1.
b
Select a relationship and then click OK. Attach the left side of the line to an entity. The Bind Relationships window opens.
9
(Optional) Improve legibility by reshaping the relationship lines. Edit the name of each relationship line to indicate the names of both entities. bind its relationship. Move the reshaping point as needed to adjust the line. and wait for the line to redisplay to show its endpoints. In a later step you can adjust the shapes of the lines to improve the legibility of the diagram. use the name Partner .
a
Right-click a relationship line and choose Bind Entity Relation.
8
For each relationship line. If no relationships are listed. select Entity Relation (child of Entity Relationship Diagram). using Figure 28 on page 151 as a guide. then there is no link or join between the business components.

0
.Creating a Virtual Business Component ■ Documenting Your Changes in an ERD
154
Developing and Deploying Siebel Business Applications Version 8.

10 Modifying the Look and Feel of the Web Client
This chapter follows the NREC example to highlight key tasks and information about configuring the look and feel of the user interface. These tasks lead you through the process of modifying the principal user interface elements based on NREC’s requirements.
Developing and Deploying Siebel Business Applications Version 8. Web templates.0
15 5
. Tasks include modifying graphics. NREC’s requirement is to modify the look and feel of the user interface to match their corporate Web site. This includes modifying the shape of tabs and buttons and changing the color scheme. and cascading style sheets.

see Figure 30 and Figure 31.Modifying the Look and Feel of the Web Client ■
For the before-and-after look of the user interface. NREC’s Modified Look and Feel
156
Developing and Deploying Siebel Business Applications Version 8.
Figure 30.0
. Standard Look and Feel
Figure 31.

Modifying the Look and Feel of the Web Client ■
The tasks that are required to make the changes are covered in the rest of this chapter.0
15 7
. ■ ■ ■ “Adding a New Logo to the Banner” on page 160 “Modifying the Screen Bar and View Bar Colors” on page 163 “Modifying Applet Colors” on page 164
Developing and Deploying Siebel Business Applications Version 8.

and the Mobile and Dedicated Web Clients. Files Image files Style Sheets Web templates Directory Path siebsrvr_root\webmaster\images\language_code siebsrvr_root\webmaster\files\language_code siebsrvr_root\WEBTEMPL
Developing and Deploying Siebel Business Applications Version 8. The locations of the files are listed below. They are stored under the root directory of your Siebel installation. Files Image files Style Sheets Web templates ■ Directory Path tools_root\PUBLIC\language_code\IMAGES tools_root\PUBLIC\language_code\FILES tools_root\WEBTEMPL
Siebel Server. The files in the Siebel Tools installation directory are used when objects such as views and applets are rendered using the Preview option in the Edit Web Layout window. The locations of the files for a Siebel Server installation are shown in the following table. For the locations of Web templates and supporting files. Because these files are outside a Siebel repository they are not controlled by the Siebel Tools Check In and Check Out Process. read “Location of Siebel Web Templates and Related Files.”
Location of Siebel Web Templates and Related Files
Siebel Web templates and supporting files are installed with the Siebel Server. ENU is the code for English and FRA is the code for French. The files in the Siebel Server installation directory are used by the Siebel Web engine when rendering the user interface in the Web Client. For example. use a third-party source control application to make sure developers do not overwrite each other’s work. The locations of the files in the Siebel Tools installation directory are shown in the following table. Siebel Tools. NOTE: In the directory paths listed below. If multiple developers are modifying files outside the repository.0
15 9
.Modifying the Look and Feel of the Web Client ■ User Interface Elements
Source Control for Web Template and Related Files
Siebel Web templates and supporting files such as graphics and cascading style sheets are not stored in the Siebel repository. ■ Siebel Tools. language_code is the three letter code of the language pack for the installed software.

rather than having to run the Mobile Web client and navigate to the applet where the changes would appear. it is easier to debug the files this way. the Preview functionality displays the Web template and the objects that are mapped to it as they would be rendered in the user interface. Siebel Tools parses the file when you save it and identifies any syntax errors that may occur. After the change is verified using Siebel Tools. The typical development process for Siebel Web templates varies depending on whether the changes are simple or complex.Modifying the Look and Feel of the Web Client ■ The Web Template Development Process
■
Siebel Mobile or Dedicated Web Client. After you have tested the changes locally. For complex template development. The locations of these files are shown in the following table. launch the application. NOTE: The modifications presented in this chapter are relatively simple. read Siebel Developer’s Reference. Files Image files Style Sheets Web templates Directory Path client_root\PUBLIC\language_code\IMAGES client_root\PUBLIC\language_code\FILES client_root\WEBTEMPL
The Web Template Development Process
When modifying Siebel Web templates you typically work with the files stored on your local machine. For minor changes. developers can manually copy the changed template into the Web template directory of their Siebel Mobile Web Client.
160
Developing and Deploying Siebel Business Applications Version 8. The tasks are written assuming that you are using this development process.
Adding a New Logo to the Banner
The banner area is the top frame in the application frame set. it is easiest to make the changes to the Web templates in the Siebel Tools directory. translating the various parts of the template into SWE syntax. For simple changes. you copy them to the appropriate directory on the server to make them available to the Siebel Web Engine. such as creating new Web templates or significantly modifying the layout of existing templates. For more information about SWE tags and syntax. Additionally. the process must include creating a prototype in HTML. and do final testing. The files in the Mobile or Dedicated Web Client installation directories are used when rendering the user interface for these clients. and then debugging as described in the previous paragraph. such as moving the position of a control placeholder. It contains the application banner and the Powered by Siebel logo. ■ Simple Web template modifications.0
. ■ Complex Web template development.

choose View > Options. you add your company’s logo to the left side of the banner. To do this. Your default HTML editor opens the dCCFrameBanner. In the Web Template Explorer find dCCFrameBanner.
4
Right-click in the window that displays the HTML. The Web Template Explorer appears. Banner Frame with Your Logo In this example. The content of the template is displayed. you need to complete the following two tasks: ■ ■ “Modifying the Banner Frame Web Template” on page 161 “Modifying the Banner Color Scheme” on page 162
Modifying the Banner Frame Web Template
The first step for adding a new logo to the Frame Banner is to add the image file to the Images directory and then modify the Web template to include the new image. dCCFrameBanner is the banner frame template for customer and partner applications. For example:
■ ■
tools_root\PUBLIC\language_code\IMAGES client_root\PUBLIC\language_code\IMAGES
2 3
In Siebel Tools choose View > Windows > Web Templates Window.
To add a logo to the banner frame 1
Add the image file you will use as your logo to the images directory of your Siebel Tools installation and to the Images directory of your test application.swt file.0
16 1
. and then define the path to the editor to use.Modifying the Look and Feel of the Web Client ■ Adding a New Logo to the Banner
The banner frame has its own Siebel Web template file that you can modify. NOTE: Make a backup copy of the dCCFrameBanner.
Figure 34. and then choose Edit Template. assume that the NREC requirement is to add their corporate logo to the banner frame and change the color scheme of the frame to match their corporate Web site. NOTE: If you have not set your default HTML Editor.
5
Find the following line of HTML:
Developing and Deploying Siebel Business Applications Version 8.swt file. click the Web Template Editor tab. For example. as shown in Figure 34.

directory to the Web Templates directory in your client installation.}
3
Change the value of the background-color property and the color property as shown below:
162
Developing and Deploying Siebel Business Applications Version 8. dCCmain. TD. The banner selector defines display rules for the banner frame. Find the following line: <td width="100%" class="bannerFade">&nbsp.css.
To modify the banner background color 1
Navigate to the client_root\public\language_code\files directory and then open the file dCCmain.css. you modify the rules defined in the cascading style sheet for your application.banner TD A:hover { background-color: #afc2ea.swt from the Web Templates directory in your Tools installation 11 Clear your browser’s cache directory and then open the Siebel application to be tested. NOTE: The cascading style sheet for Employee applications is main. TD.</td>
8
Remove the class=”bannerfade” property as shown: <td width="100%">&nbsp.
10 Copy the file dCCFrameBanner.
For the current example. To modify the background color.0
.banner TD A. TD. font-weight:bold. To change the color scheme of the banner frame. In this example you work with the banner selector. color: #003399. you change the value of the Background-color property. read Configuring Siebel Business Applications. Changes appear similar to Figure 34 on page 161. is the cascading style sheet for Siebel Customer and Partner Applications.
Modifying the Banner Color Scheme
The color schemes and other styles in Siebel Web templates are controlled using a cascading style sheet. textdecoration:none.Modifying the Look and Feel of the Web Client ■ Adding a New Logo to the Banner
<td class="applicationMenu"><span valign="top"><swe:image name="BANNER_GLOBE_LOGO" category="HTML Control Icons"/></span></td>
6 7
Replace the file name “BANNER_GLOBE_LOGO” with the name of your logo file.
2
Find the following selector and properties in the Banner Definitions section of the file: . For a list of selectors used in cascading style sheets.banner.banner TD A:visited.</td>
9
Save the file.css. The file. open the Partner Portal application.

0
16 3
.applicationMenu { background:#BDD3FF.gif. see Figure 33 on page 158. Controls the background color of the view bar frame (second-level navigation). TD. TD. color: #333399. which are controlled using the cascading style sheet. The image that controls the screenbar background is: dccscrnbar_back. TD. Clear your browser’s cache directory and then open the Siebel application to be tested. Tier2Rule.Modifying the Look and Feel of the Web Client ■ Modifying the Screen Bar and View Bar Colors
. open the Partner Portal application.
Figure 35. These frames contain color elements.
Developing and Deploying Siebel Business Applications Version 8. For the current example. Additionally. Open this image and modify color accordingly. It is only used for customer and partner applications. The NREC requirement is to modify the background color for the screenbar and viewbar to match the background of the other user interface elements that were defined for the banner frame. }
6 7
Save the file. }
5
Change the value of the background-color property as shown below: .) This image is a tiling background used to make sure that the backgrounds display well in both Internet Explorer and Netscape browsers.banner TD A:visited.banner TD A. The selectors that control the viewbar background are: ■ ■ Tier2On. The banner frame appears with the new background color. as shown in Figure 35.}
4
Find the following line: . font-weight:bold.banner. the background color of the screen bar frame is controlled using a graphic image.applicationMenu { background:#123783.banner TD A:hover { background-color: #BDD3FF. textdecoration:none. Controls the background color of the screen bar frame (first-level navigation tabs. Banner Frame with Modified Color Scheme
Modifying the Screen Bar and View Bar Colors
The screenbar and viewbar are the frames that hold the screen tabs and the show drop-down list. For an example. Controls the background color of the view bar frame (second-level navigation). in the case of customer and partner applications.

The applet styles define the color of the tab that appears at the top of the applet and the color of the control bar where applet-level menus and buttons appear. AppletStyle3.0
. AppletTitle. AppletStyle7.tier2Back TD. as shown in the following illustration. AppletBorder.tier2OnNormal font-size: 9pt.css file is the cascading style sheet for Siebel Employee Applications. AppletBack. clear the browser cache. }
TR. TD.
2
Locate the tier2 selectors and then modify the value for the background color as shown below: . and then open the application.}
3
Save the dCCmain. the selectors for each applet style are: ■ ■ ■ AppletStyle1.css file. Child.tier2On. The border around the content of the applet.tier2Rule {background-color:#BDD3FF. TD.Modifying the Look and Feel of the Web Client ■ Modifying Applet Colors
To modify screenbar and viewbar style 1
Navigate to the client_root\PUBLIC\language_code\FILES directory and then open the file dCCmain. The selector for grandchild applet style. The dCCmain. The background color of the applet content. font-weight:bold. ■ ■ ■ ■ AppletButtons. } {background-color:#003366. The selector for child applet style. background-color: #BDD3FF. The bar where applet buttons appear. The area where the applet title appears. you modify the definitions for the following subelements.
164
Developing and Deploying Siebel Business Applications Version 8.css. color:#000000. The selector for parent applet style.
Modifying Applet Colors
There are three major applet styles in your Siebel application: Parent.
Each applet style is defined by sub-elements To modify the appearance of each applet style. The background color on the screenbar and viewbar reflects your changes. In the cascading style sheet. text-decoration:none.tier2On. and Grandchild.

NREC can quickly locate the faulty configuration change and make the appropriate modifications. These tests are necessary to make sure that the changes you have made up to this point do not prevent previously existing features from working.
166
Developing and Deploying Siebel Business Applications Version 8.Modifying the Look and Feel of the Web Client ■ Testing the Web Client Changes
Testing the Web Client Changes
NREC’s testing plan calls for periodic integration and regression testing. then troubleshooting errors may be a major effort. and that the application still can interact with other applications and products. NREC’s test plan makes sure these checks happen at specific strategic intervals in the configuration process. If these tests are performed too infrequently. In the event a test fails.0
.

The following topics describe these tests in more detail. Typical components include back-office applications. Execute Integration Tests Process
Developing and Deploying Siebel Business Applications Version 8. define your test cases to test the integration points between the Siebel application and other applications or components. and security infrastructure.11 Testing the NREC Deployment
NREC’s test plan includes testing their entire development environment prior to porting to their production environment. In Integration Testing you verify that this unit functions correctly when inserted into the complete. larger environment. integration middleware. network infrastructure components. Some of these tests need to be repeated in the production environment as well. In this process. as well as explain some of the automated testing options available.0
16 7
. ■ ■ ■ ■ ■ ■ “Execute Integration Tests” on page 167 “Execute User Acceptance Tests” on page 168 “Executing Performance Tests” on page 168 “Improve Testing” on page 169 “Benefits of Functional Test Automation” on page 170 “Benefits of Load Test Automation” on page 172
Execute Integration Tests
Completion of the Functional Testing process verifies that the Siebel application functions correctly as a unit.
Figure 36. Figure 36 illustrates this process. and validating endto-end business processes that span multiple systems. Tests in this process must focus on exercising integration logic.

In the User Acceptance testing process. Hopefully. approving at each phase of the project to make sure that there are no surprises.
Figure 37. stress. you need to make sure that the functionality provided is acceptable to the business users. Figure 37 illustrates this process. open the deployment up to a larger community of trained users and ask them to simulate running their business.
168
Developing and Deploying Siebel Business Applications Version 8. Each is intended to measure different key performance indicators. Diagram of the Execute Acceptance Tests Process
Executing Performance Tests
There are three types of performance test cases that are typically executed: response time. Design User Acceptance testing to simulate live business as closely as possible.0
. who have ownership of the architecture and infrastructure. Performance tests are typically managed by specialized members of the testing and administration organizations. and reliability testing. the business user has been engaged all along.Testing the NREC Deployment ■ Execute User Acceptance Tests
Execute User Acceptance Tests
When the application as a whole has been validated. Complete this process by having the user community representative (business user) approve the acceptance test results.

if the product is configured for 5000 users. For example. In addition. Oracle delivers regular maintenance and major software releases. regular configuration changes are delivered in new releases. you add five users every three seconds. Use a baseline to measure scalability by comparing results between the baseline and target loads. Excessive login rate causes the application server tier to consume 100% CPU. Diagram of the Execute Performance Tests Process Execute each script for a single user to validate the health of the environment. Set randomization ranges based on determining the relative think times of expert and new users when compared to the average think times in the script.
Figure 38. Users need to be started at a controlled rate to prevent excessive resource utilization due to large numbers of simultaneous logins. Configuration changes and new software releases must be tested to verify that the quality of the system is sustained. add one user every three seconds.Testing the NREC Deployment ■ Improve Testing
Figure 38 illustrates the process for performance test execution. For every 1000 users of configured capacity. and logins begin to fail. This rate depends on the total configured capacity of the deployment.0
16 9
. The first step involves validating recorded user-type scripts in the system test environment.
Developing and Deploying Siebel Business Applications Version 8. Randomize think times during load testing to prevent inaccuracies due to simulated users executing transactions simultaneously. Obtain a low userload baseline before attempting the target user load.
Improve Testing
After the initial deployment. This is a continuous effort using a phased deployment approach.

First.
170
Developing and Deploying Siebel Business Applications Version 8. it can become quite costly. Review test plans and test cases to determine their effectiveness. a strategy for testing functionality across the life of the application is built by identifying a regression test suite. By streamlining the regression test process. Update test cases to include testing scenarios exposed during testing that were not previously identified. which component introduced the largest number of defects). as shown in Figure 39.0
. This provides an opportunity to measure the observed risk of specific components (for example. organizations are able to incorporate change into their applications at a much lower cost.Testing the NREC Deployment ■ Benefits of Functional Test Automation
This ongoing life cycle of the application is an opportunity for continuous improvement in testing.
Benefits of Functional Test Automation
Functional testing provides validation of the functional processes of your Siebel application. A project-level final review meeting (also called a post-mortem) provides an opportunity to have a discussion about what went well and what could have gone better with respect to testing. Diagram of the Improve Testing Process Review the testing strategy and its objectives to identify any inadequacies in planning. This test suite provides an abbreviated set of test cases that can be run with each delivery to identify any regression defects that may be introduced. Without test automation. this can be accomplished by having users log on and manually perform the tasks in a business process. The use of automation is particularly helpful for executing regression tests. A full review of the logged defects (both open and closed) can help calibrate the risk assessment performed earlier. Although this can be effective.
Figure 39.

which you can replay later to execute the test.0
17 1
. you can prepare a test script that exercises the functionality of a particular module or performs the tasks in a comprehensive business process. and some have more.
Using Siebel Test Automation for Functional Testing
Siebel Test Automation objects support the automation of functional tests on the following types of Siebel applications: ■ ■ ■ Standard Web Client Mobile Web Client Dedicated Web Client
You can use a third-party test automation tool to write. such as QuickTest Pro from Mercury Interactive. you start a recorder and perform a series of steps in the application.
■ ■
■ ■
Not all functional test automation tools have all of these features. This avoids the need to hard-code data values into a test script. Tests can be shared among multiple testers. provide features (like those listed below) for creating and running functional test scripts: ■ Test script recording. When using a third-party tool. you start the test using a test tool and let it run on its own. record. The test tool records the session in a script. Test automation eliminates the need for multiple human test passes and reduces the risk of human errors in the testing process. and run test scripts on these types of applications.
Developing and Deploying Siebel Business Applications Version 8. For more information on available features. Data value parameterization.Testing the NREC Deployment ■ Benefits of Functional Test Automation
By using a test automation tool. and across multiple cycles of application testing. Then you can share and use this script repeatedly. Rather than composing a script in a text editor.
Key Features of Functional Test Tools
Tools for functional test automation. it is only supported for test automation. refer to the documentation that accompanies the test tool for information about the specific features and functionality that it provides. Rather than manually performing the tasks in the test script each time. This approach leads to better application configurations and increased user acceptance because it allows you to perform additional software testing with little additional cost. NOTE: The Siebel Test Automation framework does not provide generalized automation services. The test tool records important statistics for identifying functional errors. Automated test execution. You can use variables in your test script that pull in data values from an external table during test execution. refer to the documentation for your testing tool. Result tracking. Reusable tests.

The test tool records the session. such as response time and reliability.
■ ■ ■
Not all load testing tools have all of these features. provide features (like those listed below) for simulating a multiple-user environment: ■ Test script recording.) Then the test tool sends the Web page to the Correlation Library. of your Siebel application while it is under a load of multiple users. and some have more. The Correlation Library parses the Web page and returns to the test tool the appropriate correlation information for the Web page. The test tool records important statistics. A single test script can be executed simultaneously by many virtual users from a single machine. and troubleshooting. how many users to add. such as how to use the Siebel Correlation Library. In addition. Controlled test execution. By using a test automation tool. this can be accomplished by having many users log on and run through a business process during a specified period of time. it can become quite costly. Use the test tool to specify parameters that indicate how the load test is run. such as how quickly to add users.0
. (This HTTP traffic equates to a Web page. such as memory usage and response times. Result tracking. For more information on load testing.
Architectural Overview of Load Testing
The Siebel Correlation Library allows you to use a third-party tool to automate load testing on Siebel applications.
172
Developing and Deploying Siebel Business Applications Version 8. Without load test automation. and which scripts to run. This is a dynamically linked library (DLL) that provides services necessary to help the testing tool generate and execute test scripts against your Siebel application. read the chapter on Automating Load Tests in Testing Siebel Business Applications. such as LoadRunner from Mercury Interactive. best practices. The correlation information provides for parameterization of data values. For more information. you can simulate the load and achieve more comprehensive and precise results without the cost associated with multiple human testers.Testing the NREC Deployment ■ Benefits of Load Test Automation
Benefits of Load Test Automation
Load testing measures key performance indicators (KPIs). Rather than composing a script in a text editor. for tracking KPIs and isolating bottlenecks. When the Correlation Library is installed and your test environment is properly set up. The Correlation Library essentially acts as an interpreter for the test tool. Although this can be effective. refer to the documentation for your load testing tool. The test tool records the HTTP traffic from the Siebel application. Virtual users. which you can use to perform the test. the Correlation Library helps the test tool translate the recorded test session into a script that can be executed to test your Siebel application. you start a recorder and perform a series of steps in the application. a load testing automation tool reduces the risk associated with user errors.
Key Features of Load Test Tools
Tools for load test automation.

dll file in your Siebel Server installation (siebsrvr\bin on Windows. the BIN directory of the load testing tool). ■ ■ Install your load testing tool. perform the following steps. such as Contact Name and Account Name. You can find the ssdtcorr.dll) to a location that is accessible to the load testing tool (for example. If you have not purchased a license for Siebel Test Automation. siebsrvr/lib on UNIX). refer to the documentation from your test tool vendor. Application data entities are those that are associated with the function of the application. set up your test tool so that it communicates properly with the Correlation Library.
Developing and Deploying Siebel Business Applications Version 8. because they are not handled by the Correlation Library.0
17 3
. For more information. you must also parameterize the transaction data entities. and SWE Count.Testing the NREC Deployment ■ Benefits of Load Test Automation
In addition to the application data entities that are parameterized by the Correlation Library. such as Row ID. Copy the Correlation Library (ssdtcorr. Transaction data entities are those that contain record data entered into the application by users. Transaction data entities must be parameterized manually.
NOTE: The Correlation Library is licensed for use only by licensed users of Siebel Test Automation. In addition.
Setting Up Your Load Testing Environment
To set up your environment for automated load testing using Siebel Test Automation. SWE Timestamp. you are not permitted to write to or otherwise access the Correlation Library.

Web templates and cascading style sheets are migrated by manually copying the files from the development server to the test server. read “Migrating Nonrepository Data from Development to Test” on page 178.” Modified Web templates and files such as cascading style sheets. The Repository Migration Configuration Utility exports the repository data from the source environment. Nonrepository data.
Developing and Deploying Siebel Business Applications Version 8. make sure the developers check in their projects from their local databases back to the server before the migration. such as assignment rules and LOVs. such as new or modified applets. For more information. Therefore.
Migrating Repository Data from Development to Test
This section explains how you migrate repository data from a source environment to a target environment. For more information. The result is that the database schema and object definitions of target environment matches source environment. views. such as adding columns to a base table (read Chapter 7.0
17 5
. imports the object definitions. read “Moving Modified Web Templates and Related Files” on page 177. After migration begins. NOTE: If you only need to migrate user interface and business object definitions.
Repository data and database schema changes are migrated using the Repository Migration Configuration Utility. you can use the Export and Import Repository Utilities. the source is the development environment and the target is the test environment. You use the Repository Migration Configuration Utility to migrate data when there has been a configuration or a database schema change in the source environment. “Configuring the House and Opportunity Entities”). and business components. and then updates the physical database schema of the target database.12 Migrating to the Test Environment
This chapter tells you how to migrate your configuration from the development environment to the test environment. For more information.
Preparing for the Repository Migration
Migration occurs between one server and another. read “Migrating Repository Data from Development to Test. read Going Live with Siebel Business Applications. Following the NREC example. Nonrepository data is migrated using the Application Deployment Manager. For detailed information about managing repositories. developers must not make any more changes—such changes will be lost. The data to be migrated includes: ■ ■ ■ Repository data.

and then click Next. and then click Next. Screen ODBC Data Source Name Database User Name Description Enter the ODBC data source name. The following succession of screens appears. When the configuration session completes. Enter the source database user name and source database password.
176
Developing and Deploying Siebel Business Applications Version 8. The RDBMS Platform screen appears. either accept the default value or choose the Browse button to select a directory. The Siebel Database Server Directory screen appears.
To migrate a repository 1
Launch the Database Server Configuration Utility by choosing Start > Programs > Siebel Enterprise Server version_number > Configure DB Server. select Migrate Repository from the list of operations.
2
Specify your Siebel Gateway Name Server Address and Enterprise Server Name and click Next. The Siebel Database Operations screen appears. NOTE: If testing in the test environment reveals problems. You launch the Repository Migration Configuration Utility from the Siebel Database Configuration Utility. these problems can be corrected either in the development environment (and the changes migrated again) or in the test environment.
Migrating the Repository
The Repository Migration Configuration Utility is a wizard that prompts you for the required information as you proceed through a succession of dialog boxes. and then click Next.0
.
7
Progress by completing the information as shown in the following table. select the platform for your environment and then click Next.Migrating to the Test Environment ■ Migrating Repository Data from Development to Test
Before migrating the repository you also need to stop all server tasks on the target environment and disconnect database access until the migration is complete.
5
In the RDBMS Platform screen. The Siebel Server Directory screen appears. the migration can be executed immediately or at a later time using the command line. either accept the default value or choose the Browse button to select a directory.
3
In the Siebel Server Directory screen.
4
In the Siebel Database Server Directory screen. The Gateway Server Address screen appears. and then clicking Next.
6
In the Siebel Database Operations screen.

Applicable only if you indicated that the target database is IBM DB2. Enter the target database ODBC datasource. You can accept this configuration by clicking finish. there are no screens about table spaces. Select the target RDBMS platform.
Moving Modified Web Templates and Related Files
Every Siebel Server installation includes a set of Web templates (SWT files) and other related files (such as image files and cascading style sheets). Select whether the target database is Unicode. NREC needs to migrate the files modified as described in this chapter from the development environment to the test environment. There are no 4KB. For Microsoft SQL server.
Index Table Space Name (Oracle-specific)
Applicable only if you indicated that the target database is Oracle. 16-KB. Enter the 16-KB table space name and 32-KB table space name.
Configuration Parameter Review
Summary screen gives a list of your choices.
16-KB Table Space Name (DB2-specific)
Applicable only if you indicated that the target database is IBM DB2. For example. Enter the database repository name and the target database repository name. you must copy the modified files to the target environment. There are two questions about index and table space. Enter the target database user name and password.0
17 7
.Migrating to the Test Environment ■ Moving Modified Web Templates and Related Files
Screen Database Table Owner Source Database Repository Name Target RDBMS Platform Target Database Encoding Target Database ODBC Datasource Target Database User Name Target Database Table Owner Index Table Space Name (DB2-specific)
Description Enter the source database table owner and source table owner password. and 32-KB table spaces in Oracle. IBM DB2 UDB v7.1 is the default. If you make changes to any of these files in your source environment. Enter the index table space name and 4-KB Table Space Name. Enter the target database table owner and table owner password.
Developing and Deploying Siebel Business Applications Version 8.

and so on) from one Siebel application environment to another. ADM can move customization data from a development environment to a testing environment. ADM eliminates the former process of transferring this data manually. The bulk of the administrative tasks to migrate data using ADM are performed at the Application Deployment Manager screen in the Siebel application GUI. responsibilities. NOTE: The term migrating is used in the ADM context as the moving of data from one environment to another. Files Cascading Style Sheets Images Web Templates File Location siebsrvr_root\webmaster\images\language_code siebsrvr_root\webmaster\images\language_code siebsrvr_root\WEBTEMPL
Migrating Nonrepository Data from Development to Test
Migrating application run-time customization data from one Siebel application environment to another is a common requirement when going live to a new development. assignment rules. For example. if required. The following data types are available for migration with ADM: ■ ■ ■ ■ ■ ■ ■ ■ ■ Access Groups Assignment Rule Expense Types List of Value (LOV) Product Feature Product Line Public Predefined Query (PDQs) Responsibility State Model
178
Developing and Deploying Siebel Business Applications Version 8. These tasks are intended for those with Siebel administrator responsibility. Application Deployment Manager (ADM) is a feature that automates the process of migrating enterprise customization data (views.Migrating to the Test Environment ■ Migrating Nonrepository Data from Development to Test
To move Web templates and related files from Development to Test
■ Copy any new or modified files of the following types from the development server to the test server. No changes to the data take place during migration. The ADM set-up process in the ADM GUI creates a template in which one data type can be migrated on a regular basis.0
. or production environment. The fundamental structure of this template is the deployment project. test. The Application Deployment Manager (ADM) feature automates the migration of the Siebel application run-time customization data. The deployment project consists of one or more data types that can be migrated.

Using Siebel Tools you can add more data types for use with ADM.0
17 9
.Migrating to the Test Environment ■ Migrating Nonrepository Data from Development to Test
■ ■
User List View
These data types are preconfigured in the standard Siebel Business application. read Siebel Application Deployment Manager Guide. For more information on migrating nonrepository data and using ADM.
Developing and Deploying Siebel Business Applications Version 8.

Migrating to the Test Environment ■ Migrating Nonrepository Data from Development to Test
180
Developing and Deploying Siebel Business Applications Version 8.0
.

interface tables are intermediate database tables between the Siebel database and another database. however. “Required Application Administration Tasks. you need to understand some fundamental concepts. read Siebel Enterprise Integration Manager Administration Guide.
Interface Tables
As illustrated in Figure 40. you have moved the application (including your configuration changes) from development to test and have performed the setup tasks described in Chapter 14.
Figure 40. you use EIM to load data from the interface tables into the Siebel base tables. This chapter tells you how to load data from your legacy applications into a Siebel database.
Basic EIM Concepts
To begin working with EIM. you need to have actual corporate data in your Siebel database. you or your database administrator first load it into Siebel interface tables using your database-software-specific utility. you have been working only with the sample data available with your Siebel installation. Generally. this chapter deals only with bulk imports. The section “Import Example” on page 182. Because the current goal is to load data into a Siebel database.13 UsingEnvironment Data Into the EIM to Load Test
You have already completed many of the tasks to prepare your test environment. using the Siebel Enterprise Integration Manager (EIM).0
18 1
. provides more detailed information about the specific import example presented in this chapter. exports. For example. merges. Process Flows Between Siebel Database and Other Databases Rather than loading legacy data directly into Siebel base tables. This chapter focuses on one specific import example: loading account data for the NREC. Up until now. and deletes. which are described in this section. For detailed information about EIM. This exchange of data can include bulk imports. EIM is used to exchange data between Siebel database tables and other data sources.” To do further development and testing work.
Developing and Deploying Siebel Business Applications Version 8. Then.

To do this. There is also a brief explanation of the parameters that appear in the configuration file. ■ EIM process For the step-by-step instructions on running the EIM process.
Import Example
This chapter focuses on how NREC used EIM to import its account data into the Siebel database. read “Using the Interface Tables” on page 182. Check results.
Using the Interface Tables
Read Siebel Enterprise Integration Manager Administration Guide for information on using these tables. the NREC administrator needed to load the applicable interface table (EIM_ACCOUNT). For more information. read “Running EIM” on page 187. The process pulls the accounts data from the EIM_ACCOUNT interface table into the specified base tables in the database.
This chapter follows these steps to import data. read “Using the Interface Tables” on page 182. including finding out which columns are mandatory. This chapter provides the information for this example in the following order. Edit the EIM configuration file. For more information. and run the EIM import process. ■ Account data to be loaded into the EIM_ACCOUNT interface table For information about how to load an interface table. Run EIM.ifb configuration file. export. including: ■ ■ ■ ■ Specific data and file attachments that EIM can process The names of the interface tables The target base tables mapped to the interface tables Any secondary tables associated with the target tables
182
Developing and Deploying Siebel Business Applications Version 8. read “To run an EIM process using the GUI” on page 187. you need to complete the following steps. read “Editing the Configuration File” on page 185. ■ Configuration file To view the contents of the IFB file that used to customize the behavior of the EIM process.Using EIM to Load Data Into the Test Environment ■ Using the Interface Tables
Process Overview
For any EIM process (whether it be import.0
. For more information. prepare the NRECimp. merge. read “A Sample Configuration File” on page 185. read “Checking the Results of the Data Import” on page 189. or delete).
1 2 3 4
Load the interface tables. For more information.

find EIM_ACCOUNT. expand the EIM Interface Table object. The EIM Interface Tables window appears in the Object List Editor. find the interface table you plan to load. In the Object Explorer.0
18 3
.
To use Siebel Tools to determine which columns are required 1
In the Object Explorer. select EIM Interface Table Column (a child object of EIM Interface Table). activate the EIM Interface Tables object types. NOTE: If the EIM Interface Tables object type is not visible.
Developing and Deploying Siebel Business Applications Version 8.
2 3
In the EIM Tables window. However. and then under the Object Explorer tab. for some columns interface tables are required: they cannot be left NULL. The EIM Interface Table Columns window appears in which the columns of the current table are displayed. For the current example. You can find out which columns are required either through Siebel Tools or by referring to Siebel Enterprise Integration Manager Administration Guide.Using EIM to Load Data Into the Test Environment ■ Using the Interface Tables
Determining Which Columns Are Required
To some extent. choose View > Options. you can decide which columns from your source table to load into an interface table.

For example. and NAME columns are required because they are not marked Nullable. Some columns in the interface tables are part of a user key sequence. The columns marked Nullable are not required.0
. IF_ROW_STAT.
184
Developing and Deploying Siebel Business Applications Version 8.Using EIM to Load Data Into the Test Environment ■ Using the Interface Tables
4
In the Interface Table Columns window. As EIM loads each row. use your database-software-specific load utility. read the documentation for your database software. look at which columns have the Nullable property checked.
Loading the Interface Tables
To load data into an interface table. such as one of the load utilities available for DB2. The user key sequence is the set of columns (called user key columns) whose values uniquely identify a row.
NOTE: For your convenience. right-click and choose Columns Displayed to change the column order on this view so that the Nullable property appears next to the Name property. it checks whether the interface table already contains that row’s user key sequence. as shown in the preceding figure. as shown in the following figure. the IF_ROW_BATCH_NUM. For information. thus preventing the import of duplicate rows. Make sure you load the required columns.

is shown here. This example uses the configuration file NRECimp. In this example.ifb.ZIPCODE. NOTE: In a Unicode environment. */ [Siebel Interface Manager] LOGIN USER = "SADMIN" LOGIN PASSWORD = "SADMIN" RUN PROCESS = Import Accounts /* These are generic process parameters. The default configuration file. S_ADDR_ORG. read Siebel Enterprise Integration Manager Administration Guide. S_PARTY ONLY BASE COLUMNS = S_ORG_EXT. The EIM configuration file is an ASCII text file of extension type IFB that resides in the admin directory under the Siebel Server directory.CITY.ADDR. The following parameter sections describe the required header section and generic process section parameters. NRECimp. /* These are header parameters. This example features the import process. the EIM configuration file must be saved as a Unicode text file. For more information about the EIM configuration file.LOC. S_ADDR_ORG. Read the Siebel Enterprise Integration Manager Administration Guide for the following topics. Before initiating an EIM process. ■ ■ ■ Other process and header parameters Alternative sources from which EIM accepts parameter values The process for defining multiple processes in the configuration file
A Sample Configuration File
The sample configuration file in this section shows the entries that are necessary only for the operations in the particular import EIM example for this chapter.0
18 5
. provides the data used in the process if no other configuration file is specified.ifb.OU_ID. S_ORG_EXT.
Developing and Deploying Siebel Business Applications Version 8. Following the header section. S_ADDR_ORG.ifb.NAME. */ [Import Accounts] TYPE = IMPORT TABLE = EIM_ACCOUNT ONLY BASE TABLES = S_ORG_EXT. Some process section parameters are generic to all EIM processes. read Siebel Enterprise Integration Manager Administration Guide.Using EIM to Load Data Into the Test Environment ■ Editing the Configuration File
Editing the Configuration File
EIM reads a special configuration file that specifies the EIM process to perform and the appropriate parameters. The text of the sample configuration file. Other process section parameters are specific to a particular EIM process.PARTY_UID. you must edit the contents of the EIM configuration file to define the process to be performed. S_ADDR_ORG. For more information. S_ADDR_ORG.STATE. default. EIM sets the process locale as specified in the configuration file at start up. S_PARTY. there must be at least one process section with its associated parameters. The configuration file begins with a header section used to specify global parameters that apply to the process sections defined later in the file. S_ADDR_ORG.

read “A Sample Configuration File” on page 185. Table 11 shows only those header parameters featured in the NRECimp.STATE. S_ADDR_ORG. The process section is generic to all EIM processes. S_ADDR_ORG.MERGE. IMPORT for NREC ’s import example. read the Siebel Enterprise Integration Manager Administration Guide. S_ADDR_ORG. For the list of the values assigned to each of the header parameters.ADDR.
Table 11. Only process these tables. EIM_ACCOUNT for NREC.NAME. S_ADDR_ORG.0
.ifb.
Required Header Section Parameters Description Database employee login (SADMIN for NREC) Database password (SADMIN for NREC) Initial or main process section to run (Import Accounts for NREC) Header section must use this reserved name
Command USERNAME PASSWORD PROCESS [Siebel Interface Manager]
Process Parameter Section
A parameter in the process section only applies to the particular process specified and overrides any corresponding value in the header section for the specific process. S_ORG_EXT. */
Header Parameter Section
This section describes the header parameters that you need to specify in the configuration file to properly configure EIM for an import process.OU_ID. For parameters specific to the import process.
Process Section Parameters Generic to All EIM Processes Description Only process these columns.CITY.PARTY_TYPE_CD /* There are no process-specific parameters required in this example.ZIPCODE for NREC. S_ORG_EXT.
Table 12.SHELL. S_ADDR_ORG. Table 12 describes the parameters that NREC used in the process section of NREC’s configuration file.
Command ONLY BASE COLUMNS
ONLY BASE TABLES TABLE TYPE
186
Developing and Deploying Siebel Business Applications Version 8. Interface (IF) table for process. S_ORG_EXT. S_PARTY for NREC.Using EIM to Load Data Into the Test Environment ■ Editing the Configuration File
S_PARTY.DELETE. There are both generic and specific process parameters.LOC. IMPORT.EXPORT. NRECimp.ifb. S_ADDR_ORG.

type FALSE. In the Component Requests form. Otherwise. you need to again extract the database for each mobile client. Do not change this value to TRUE until after you import the initial data. In the System Preference Value field. add or change any component parameters for the EIM process and save the record.
Developing and Deploying Siebel Business Applications Version 8.
Figure 41 on page 189 shows an example of setting parameters in the Component Request Parameters list. In the Component/Job field. add a new record.
5 6
Complete the remaining fields in the Component Requests form and save the record. To synchronize them again. “Implementing Siebel Remote. read Chapter 18. For more information on synchronization. the server database and mobile client databases will not be synchronized after the import. Click outside the row to save changes. read Siebel System Administration Guide. and run database initialization on each client.
You can also change the transaction logging preference by changing the LOG TRANSACTIONS parameter in the EIM configuration file. click the select button.
To disable transaction logging 1 2 3 4
Navigate to the System Preferences screen. read Siebel Enterprise Integration Manager Administration Guide. CAUTION: Do not disable Docking Transaction Logging if you have active mobile clients. Click the Component Requests view tab.
To run an EIM process using the GUI 1 2 3 4
Navigate to Administration . Select Docking: Transaction Logging. it is a good idea to disable transaction logging to improve EIM performance.Server Configuration > Enterprises > Parameters. In the Component Request Parameters list. For information on defining component jobs.
Running EIM
This section describes how to start an import process from the Siebel Client. first define the component job. To use a component job based on EIM for your component request.0
18 7
.” and Siebel Remote and Replication Manager Administration Guide.Using EIM to Load Data Into the Test Environment ■ Disabling Logging Before Initial Loads
Disabling Logging Before Initial Loads
Before performing an initial load through EIM. Disabling transaction logging consists of disabling the Docking: Transaction Logging system preference. select the Enterprise Integration Mgr component. For information about starting the import process from the command line. and in the Component/Jobs window.

click the Select button.
Batch number
Required
Batch number
0
Process
Required
Process name of the EIM process you want to run 1 8 1
not applicable 0 0 not applicable
Error Flags SQL Trace Flags Trace Flags
Optional Optional Optional
7
In the Component Requests form. Continue to make other selections in the Job Parameters window by repeating Step a through Step d for the required and optional selections listed in the following table. Required or Optional Required
Selection Configuration file
Value Name of the EIM configuration file
Default default.Using EIM to Load Data Into the Test Environment ■ Running EIM
a b c d e f
In the Component Request Parameters list. The possible selections. In the Name field. Otherwise. some steps may not roll back correctly. and default values appear in the following table.ifb
Comments You can use the Uniform Naming Convention (UNC) filename when specifying the EIM configuration file if you have read permission to the path. You need to identify at least a batch number. select an item from the list and click OK.
188
Developing and Deploying Siebel Business Applications Version 8. In the Value field. values required. and then click Submit Request. and configuration file for the task.0
. When the EIM process is running. click the menu button. do not stop or pause the task. add a new record. process name. defined in the EIM configuration file. If the batch number component parameter is set to 0. type the appropriate value for that list selection and click Save. The initial process to be run. the batch number in the EIM configuration file (if any) is used. In the Job Parameters window.
CAUTION: EIM is a multistep process.

0
18 9
.Using EIM to Load Data Into the Test Environment ■ Checking the Results of the Data Import
Figure 41 shows an example of running an EIM process as described.
Developing and Deploying Siebel Business Applications Version 8. where task# is the Task Number for the EIM process that you ran. NREC’s EIM log files are located in the siebel_srvr_root\log\server directory. Click outside the row to save changes. type TRUE.
Figure 41. In addition. Select Docking: Transaction Logging. For more information.
Checking the Results of the Data Import
Your EIM log file contains comprehensive status and diagnostic information about the import process. the default. Running an EIM Process
To reactivate Docking Transaction Logging 1 2 3 4
Navigate to the System Preferences screen.
To review your import process
■ View the EIM log file for the corresponding task number. read Siebel Enterprise Integration Manager Administration Guide. you can check the status of each row EIM tried to import by using the IF_ROW_STAT column. The log file name is Eim_task#.trc. In the System Preference Value field.

Using EIM to Load Data Into the Test Environment ■ Checking the Results of the Data Import
190
Developing and Deploying Siebel Business Applications Version 8.0
.

” The tasks in this chapter are performed in the administration views of the Siebel Web client or dedicated Web client. The tasks in this chapter do not cover Access Groups and Catalogs.14 Required Application Administration Tasks
This chapter describes how NREC completed the general setup tasks in the Test environment. and large numbers of transactions to route. there is the potential for error. This chapter includes the following topics: ■ ■ ■ ■ ■ Logging On as the Siebel Administrator Defining Views on page 192 Defining Company Structure on page 193 Setting Up Users on page 199 Registering Partners and Creating Partner Organizations on page 202
NOTE: Generally. which control access to master data. Although you can perform these tasks against your local database and synchronize. always perform administration tasks against the server database. Assume NREC accessed the views by logging on to the Partner Manger application. you can follow along using an application logged on to the Sample database. You can use SADMIN and SADMIN to log in to the Siebel Sample database to complete the tasks in this chapter. such as Call Center. the tasks for setting them up are not covered in this chapter.
Developing and Deploying Siebel Business Applications Version 8. read Chapter 3. Although the tasks in this chapter are written from the perspective of an NREC employee setting up the application in the test environment. read Siebel Applications Administration Guide and Siebel Security Guide. you must log in to your Siebel application using the administrator user name and password assigned by your database administrator. The login screen appears. For more information about setting up Access Groups and Catalogs. For an overview of NREC’s installation process. including data conflicts. The default values are SADMIN and SADMIN. performance problems resulting from a large local database.0
19 1
. Go to the URL for your application.
Logging On as the Siebel Administrator
To perform the tasks in this chapter. Because NREC did not use Access Groups or Catalogs in their implementation. The same views are accessible through other employee applications.
To log in as an administrator to a server data source 1 2
Open your Web browser. “Installing Siebel Applications. This chapter assumes a successful installation of Siebel products in the Test environment.

For the new views to appear in the user interface you need to register them in the application. read “Modifying the Screen Bar and View Bar Colors” on page 163.
To register new views 1 2
From the application-level menu.
192
Developing and Deploying Siebel Business Applications Version 8.Required Application Administration Tasks ■ Defining Views
3 4
Enter SADMIN in the User ID and Password fields. A view record requires modification only if its name is changed. choose Site Map > Administration . For more information about tab images. To return the user interface to the original look and feel. new views for the NREC example. Logging in as SADMIN provides access to all screens and views mentioned in this guide. Siebel Partner Manager opens. Use Administration . Even then. log in to Siebel Partner Manager. Add records for the new views. “Modifying the Look and Feel of the Web Client. However. You must do this before you can associate views with responsibilities.Application > Views to register new views. Select Sample as the data source.0
. now you need to register them in the test environment. a preferable approach is to not assign it to any responsibilities. NOTE: If you modified tabs as described in Chapter 10.Appraisals House Detail . you need to replace the original images. you registered the views in your local development environment. NOTE: Turn off any of the forecast views that you do not intend to use based on your organization’s forecasting configuration decision. displaying data from the Sample database.
2 3
Enter SADMIN and SADMIN as the user name and password.” the images for the off state may appear in your employee application. You did this during the development cycle. The only time a view may need to be deleted is if it no longer existed or if you did not want anyone to have access to it. For the NREC example.Renovations
NOTE: You generally do not need to modify or delete records for registered views.
Defining Views
Often developers add views during the configuration stage of the implementation process. to unit test the new views (read “Testing Changes” on page 50). For example.Application > Views.
To log in as an administrator to the sample data source 1
Open the Mobile Web Client on your local machine. are:
■ ■ ■
House Detail View House Detail . Click OK.

NOTE: Changing your company structure—such as positions and divisions—can cause routers to reevaluate visibility for every object related to the objects that have changed. such as when two people share a single job. or access. read Siebel Applications Administration Guide.
Developing and Deploying Siebel Business Applications Version 8. record addresses.
Understanding Access to Data
How you define your company’s structure in your Siebel application affects the records and views to which users have visibility. There is a many-to-many relationship between a person and that person’s positions.
Understanding Company Structure
Defining your company’s structure involves setting up the following entities: ■ Organizations and organization skills. and maintain default currencies. This can affect performance. an individual could hold one or more positions—sales representative for the X territory definition and sales manager for the XYZ region. positions. Positions represent specific job slots. positions. and responsibilities. responsibilities. They can represent internal or external groups of users—for example. For example. Conversely.
■ ■ ■
For more information about setting up company structures. more than one person may be assigned to a single position. Responsibilities control the screens and views a user can access. internal divisions or partners. positions determine which records users can access. Positions and position skills. divisions. There are several relationships between organizations.0
19 3
.Required Application Administration Tasks ■ Defining Company Structure
Defining Company Structure
The first step in setting up your Siebel application is to define your company’s structure. and people. Divisions are used to group positions. Divisions belong to organizations but do not affect visibility. Organizations represent the broad divisions of your company. This includes defining organizations. For more information. each user is then assigned one or more responsibilities. read Siebel Remote and Replication Manager Administration Guide. Responsibilities determine which views users can access. Organizations are used to control access to data. Divisions. In addition to having one or more positions. Responsibilities. Positions determine which record users can access.

194
Developing and Deploying Siebel Business Applications Version 8. For more information on organizations and company structure. read Siebel Applications Administration Guide and Siebel Security Guide. However.
To set up an organization 1
From the application-level menu. if the user changed position. and so on—NREC uses Siebel Partner Manager to set up partners and promote them to organizations with NREC as the parent organization. contacts.
Setting Up Organizations and Organization Skills
Setting up organizations is an optional step in an implementation. you automatically have everything assigned to a default organization. Initially NREC creates the NREC organization. Because NREC is using Partner Portal. opportunities. responsibilities.Required Application Administration Tasks ■ Defining Company Structure
In a situation in which a user is associated with one responsibility and multiple positions. that user has the same set of views regardless of which position that user logged on with. Again. that user would access different data.Group > Organizations. and so on) that pertains to this position. Some data records are unavailable depending on what organization a user’s position belongs to. read Siebel Applications Administration Guide.) For more information on organizations and access to data. The Organizations view appears. Read “Registering Partners and Creating Partner Organizations” on page 202. (Users can also be given more visibility within their organization by receiving access to certain views. but the data in the views has. If the user changes to the sales manager position. choose Site Map > Administration . This structure lets NREC to logically group these different user groups and partition data accordingly. Having one organization is like having no organization. it sets up one parent organization called NREC and then a child organization for each of its partner real estate agencies.0
. If you do not set up additional organizations. the position the user is logged on as does not have any other positions reporting to it so the user does not get other data. There is no effect on visibility and data access. Even though the user still has the My Team’s Accounts view. Then after the rest of the company structure is set up—positions. the My Team’s Accounts view now shows the user information for the positions reporting to that user if the user is the primary on the account. NOTE: A user can change positions while logged in by choosing View > User Preferences > Change Position and choosing a different position in the list. Having organizations adds another level of visibility. A user who is logged on as a sales representative can access only data (accounts. the views have not changed.

Required Application Administration Tasks ■ Defining Company Structure
2
Add a new record. In the Internal Divisions list. For example.
3
Review the values defined for the division.0
19 5
. choose Site Map > Administration . Using the word organization in the name provides a visual clue for users. For example. query for NREC.
Developing and Deploying Siebel Business Applications Version 8.
Setting Up Divisions
Divisions belong to organizations and are used to record addresses and to maintain default currencies. you must have at least one division set up. the NREC division was created when you created the NREC Organization.
Partner Flag
FALSE
NOTE: Organizations cannot be deleted.Group > Internal Divisions. Indicates whether the organization represents an external enterprise. but their country of operation and currency are defined by their division. To implement Siebel Business Applications. read Siebel Partner Relationship Management Administration Guide.
To review the division created for your organization 1 2
From the application-level menu. The Internal Divisions list appears. Field Name Partner Manager Position Value NREC Organization SADMIN Description Unique name for the organization. For more information. User reporting structures are defined by their parent position. query for the organization you created in “Setting Up Organizations and Organization Skills” on page 194. Some fields are listed in the following table. Used for Partner Portal to represent the person in the organization who manages the relationship with partners. A division is automatically created when you create an organization.

the CEO position probably does not report to a higher level. For example. Positions represent a job slot in your organization.Group > Positions. start at the top of the organization chart and work your way down. Define positions in each level of your company’s division hierarchy.
196
Developing and Deploying Siebel Business Applications Version 8. Because you choose parent positions as you create new positions.Required Application Administration Tasks ■ Defining Company Structure
Setting Up Positions and Position Skills
To log in to the Siebel application an employee has to have a position. As you enter your company’s positions.
To create positions 1
From the application-level menu. refer to your company’s organization chart to determine reporting relationships (positions and parent positions). There is always one position that does not have a parent position.0
. Positions determine which records users with a particular position can access. choose Site Map > Administration . The Positions view appears.

A position can only have one organization.0
19 7
. Most fields in the Position list are filled in automatically from the Employee record of the active employee. read Siebel Applications Administration Guide. For more information. but not all organizations. The employee can then get one organization’s data at a time. add a new record for each of the positions to define. For example. Required. If you have not set up employees. you add the employees listed in the last column. then you must create a position for each organization and assign the employee to each position. by choosing View > User Preferences > Change Position. Later. Select an organization for the position. It has no effect on visibility. Position Territory The name of the position.
Developing and Deploying Siebel Business Applications Version 8. Allows a position to be associated to a territory for use by the Assignment Manager module.
Position Type
The following table lists sample positions for the NREC example. For more information. Informational field that indicates the type of position. you can associate them with positions later. If you want a user to have visibility to some organizations.Required Application Administration Tasks ■ Defining Company Structure
2
In the Positions list. read Siebel Assignment Manager Administration Guide. Position Administrator CEO Information Technology Manager Marketing Associate Partner Manager Real Estate Agent 1 Real Estate Agent 2 Sales Manager Parent Position Information Technology Manager not applicable CEO Sales Manager Sales Manager Sales Manager Sales Manager CEO Employee Sandy Bolivar Pat Bosch Chris Brown Terry Picardo Dale Abizaid Dana Castro Alex Grey Lee Smith
Most fields in the Position applet get filled in automatically from the Employee record of the active employee. Field Billing Product Compensable Organization Comments Used for Professional Services. the Start Date field shows the start date of the employee marked Active for the position. as described in the section “Setting Up an Employee in Your Siebel Application” on page 200. Used for incentive compensation. Some fields are described in the following table.

therefore. In the Assignment Skills list. Grant access to the System Preferences view to only a select group of administrators. partner manager.
To define a responsibility. to your Siebel application’s information and functions. and so on. Click the Assignment Skills tab.Required Application Administration Tasks ■ Defining Company Structure
To set up position skills 1
From the application-level menu. and so on. The sales manager responsibility might have access to the same screens as the sales representative. you might create responsibilities for NREC CEO. Save the record. Select a skill in the Item field. Accounts. For example. Activities. You may prefer to copy the sample responsibilities that ship with your Siebel application and then customize them for your purposes. do not give end users access to the System Preferences view. NOTE: You cannot edit sample responsibilities. sales manager. field sales representatives.Applications screen. For example. such as Opportunities. Views. the Siebel Administrator responsibility allows access to all views. click the position to which to add skills. The CEO responsibility might have access to all views except applications administration. System preferences control server logic and processing. Master Forecasts.Group > Positions. You can do this using the License Keys view in the Administration . add a new record. The Positions view appears. The work performed using these screens has far-reaching implications for the entire application. disable the Siebel License Key view in the user’s responsibility. plus additional views. if desired. Therefore. Skills are added using Siebel Tools.
2 3 4 5
In the Positions list. Define responsibilities that correspond to the major job functions in your organization. Mobile Clients. Skills must exist before you can add them.
Defining Responsibilities
Responsibilities determine which views users can access. Responsibilities. Defining responsibilities lets you limit user access to views and.0
. Do not add Administration .
198
Developing and Deploying Siebel Business Applications Version 8. ■ ■ ■ In the NREC example The Real Estate Agent responsibility might have a select set of views in Siebel Sales. and Territories screens.
6 7
Add comments. To hide the license key view. limit access to the Employees. Contacts. you must specify which views are available to that responsibility.Applications screens to responsibilities associated with end users. You may want to hide the license key view to discourage unauthorized users from attempting to change license keys. choose Site Map > Administration . Likewise.

NOTE: You cannot edit the sample responsibilities.
4
Add any other desired views to the responsibility.Application > Responsibilities. so they can be assigned responsibilities. you may want to configure new views in Siebel Tools that restrict the visibility to responsibilities as a way to delegate administration of responsibilities. the Responsibility view shows all responsibilities. If you implement an external authentication application. but the users are not.
■ ■ ■
House Detail View House Detail . For the NREC example.
2
Select a responsibility to copy.0
19 9
. Now NREC must add these views to the responsibilities that need to have access to them. your Siebel application. each user may have an individual database account.
Developing and Deploying Siebel Business Applications Version 8. add the following views. You must copy them before you can modify them. read Configuring Siebel Business Applications. NOTE: Add all new views to the administrator responsibility. Without responsibilities.
Now you must set up your users. The Responsibility view appears. you must configure user authentication including associating users with database accounts. However. For more information on configuring views. Enter a new description for the responsibility so that you can later identify its function.
To copy an existing responsibility 1
From the application-level menu. choose Site Map > Administration . regardless of organization. By default. a user cannot use the Siebel application. Select an organization for the responsibility. because the people with this responsibility typically help troubleshoot the Siebel application. you must define users in your database server.Required Application Administration Tasks ■ Setting Up Users
NREC created new views during the development cycle and then registered the views in the application.
3
Click the menu button and then choose Copy Record. Depending on your user authentication environment. and your authentication environment.Renovations
5 6 7
Enter a new name for the responsibility.
Setting Up Users
Before users can access Siebel data. Your database administrator creates database accounts and optionally encrypts their passwords. The views for the existing responsibility are copied. or accounts may be shared by multiple users.Appraisals House Detail . such as NREC Partner Real Estate Agent.

For more information about setting up users. read Siebel Applications Administration Guide. you can set up these database users as Siebel application users. Customers for customer applications to whom your company may grant some data access. Includes employees.
Setting Up Database Users
Before you can set up someone as a Siebel application user. and territories to a user Remove all positions connected to a user
This task can be done by an administrator in your organization or an administrator at a partner organization whose responsibility allows them access to the view. you are able to: ■ ■ ■ Add or delete a user Add multiple positions. For more information. partners. Persons.Required Application Administration Tasks ■ Setting Up Users
For the current example. For more information about setting up user authentication. Individual internal users.
200
Developing and Deploying Siebel Business Applications Version 8. read “Registering Partners and Creating Partner Organizations” on page 202. Individual users in partner companies to whom your company may grant access to some of its data. As the Siebel application administrator. and contacts. users.
■
■
Setting Up an Employee in Your Siebel Application
After users have a database account. Internal and external users with login privileges. that person must have a database account user name. Work with your database administrator to set up developers as database users in the SSE_ROLE group. responsibilities.
Types of Users
Siebel Business Applications recognize several types of users: ■ ■ Employees. read Siebel Security Guide. Persons may or may not have login privileges. The exact steps for adding users and placing them in this role group depend on the database software your organization is using. A user does not need a position to access views. Users. Add the database accounts on the appropriate database and add these accounts to the group SSE_ROLE.0
. Partners. Employees typically have login privileges. To access views a partner needs a position. organizations. assume NREC is setting up each user with an individual database account and is not using an external authentication application.

you want to set up employee records. Using this process you can assign user responsibilities at the same time as you enter other user information.
2 3 4
Add a new record. Positions and their employees are defined for NREC in the section “Setting Up Positions and Position Skills” on page 196. read Siebel Security Guide. Field User ID Password Comments Enter the user ID for this employee in uppercase letters for compatibility across databases.
To add an employee 1
From the application-level menu. Associating responsibilities with users is described in the section “Associating Responsibilities with a User. users. Applicable only when using LDAP or Microsoft Active Directory for login authentication. However. or you may continue to work from the Employee view to change or add associations between users and their responsibilities. Otherwise. choose Site Map > Administration . you may work directly from the Responsibility view. Select at least one responsibility.
Associating Responsibilities with a User
When you are first implementing your Siebel application. you assign them to users as described in “Setting Up Users” on page 199. Some fields are described in the following table. and persons. The user’s responsibilities. you also need to set up partners. The user’s position.Required Application Administration Tasks ■ Setting Up Users
Initially.
Developing and Deploying Siebel Business Applications Version 8.”
Position Responsibility
5
Repeat these steps for each employee you need to add. The procedures for setting up other types of users are similar to the procedures for setting up employees.User > Employees. The Employees view appears. Complete the additional fields. it is not editable. After your initial implementation. you define responsibilities. as described in “Defining Responsibilities” on page 198. For more information about parameter setups to make the field editable when using LDAP or Microsoft Active Directory.0
20 1
. You can also add organizations and positions. After you have defined responsibilities.

Registering Partners and Promoting Them to Organizations
NREC registers each partner and then converts it to an organization within the NREC company structure. choose Site Map > Administration . Additionally. This section uses one partner. and employees. The Approved Partners view appears. responsibilities. For example. choose Site Map > Administration .Application > Responsibilities. as an example. and then click Add.
3
Save the record.Partner > Approved Partners.
2
In the Approved Partners list. including positions.
To register a partner and then promote it to an organization 1
From the application-level menu.
Registering Partners and Creating Partner Organizations
This section covers how NREC sets up partners in their test environment to resemble its business model. read Siebel Partner Relationship Management Administration Guide.
202
Developing and Deploying Siebel Business Applications Version 8. click New to enter a new record representing the partner. NREC will create an organization for each of its partner real estate agencies.
2 3 4 5
Select a responsibility to assign to a user. enter San Francisco Real Estate. Select one or more employees from the Add Employees dialog box. For detailed information on managing partners. The record is displayed in the Partners list. A Partner form appears. San Francisco Real Estate. Select the User list applet.Required Application Administration Tasks ■ Registering Partners and Creating Partner Organizations
To associate a user with a responsibility 1
From the application-level menu. The added employees now have access to the views listed in the Views applet. The Responsibility view appears.0
. NREC will set up the company structure for each partner. Click the menu button and then choose Edit > Add New Record.

In the Partners form. Responsibilities. which automatically promotes the partner to an organization.
To create positions for a registered partner 1 2
From the Show drop-down list. For example. and user assignments for the partner. and User Assignments
Now that you have created a registered partner.Required Application Administration Tasks ■ Registering Partners and Creating Partner Organizations
4
Click the Register button. Enter responsibilities for the partner organization. The partner is moved to the Registered partners list and an organization is created for the partner as a child of the parent organization—NREC. responsibilities. San Francisco Real Estate.
Developing and Deploying Siebel Business Applications Version 8.
3
Enter new records using the following views:
■ ■ ■
Positions. Responsibilities. query for the partner you created in the previous procedure. A form appears where you can select the Organization flag.0
20 3
. you can add the positions.
5
Select the Organization flag and enter NREC as the parent organization. Enter employee records for the partner organization. Enter positions for the partner organization.
Creating Positions. choose Registered Partners. User Assignments.

15 Assignment Manager
In previous chapters, you used Siebel Tools to configure the business logic of NREC’s Partner Portal application. In addition to Siebel Tools, there are other mechanisms t to configure business logic as well. These include modules such as Siebel Business Process Designer, Siebel Personalization, and Assignment Manager. These modules are administered at run time using views in the Siebel Web Client. You can modify business logic without having to recompile the Siebel SRF file. This chapter describes how NREC used Assignment Manager to implement business rules. Subsequent chapters cover Business Process Designer and Personalization. Use Assignment Manager to create business rules that automatically assign entities such as opportunities, service requests, or activities to the appropriate individuals. For example, NREC wants to automatically assign opportunities to employees at partner real estate agencies. When an opportunity is entered into the application, it contains the ZIP Code where the customer is interested in buying property. Assignment Manager uses this attribute to automatically assign the opportunity to a real estate agent located within that ZIP Code. After assignment rules are defined and made active, they are automatically triggered whenever a new opportunity is created. This chapter includes the following topics: ■ ■ ■ ■ ■ ■ Configuring Territory Assignment Components Creating Assignment Rules Based on Territories on page 206 Specifying Assignment Criteria and Values for Rules on page 207 Adding Positions for Each Assignment Rule on page 208 Releasing the Assignment Rules on page 208 Activating the Rules on page 209

Configuring Territory Assignment Components
NREC’s assignment rules use the ZIP Code attribute on the opportunity to determine how to assign the opportunity. This is a custom attribute that you added to the opportunity business component in “Adding Fields to the Opportunity Business Component” on page 112. Because this is a custom attribute, NREC needs to add a new assignment criteria using Siebel Tools before being able to create assignment rules. This section summarizes the high-level tasks necessary to create the assignment criteria. For detailed information about configuring assignment attributes, read Siebel Assignment Manager Administration Guide. The tasks to create the Opportunity ZIP Code assignment criteria are: ■ Create a new Workflow Policy Column

Developing and Deploying Siebel Business Applications Version 8.0

20 5

Assignment Manager ■ Creating Assignment Rules Based on Territories

■ ■ ■

Define a new Workflow Policy Component Column as a child record of the existing Opportunity Workflow Policy Component Create a new Assignment Attribute and Assignment Attribute Column Create a new Assignment Criteria and Assignment Criteria Attributes

NOTE: Defining assignment criteria is only necessary when the predefined assignment criteria do not meet your organization’s business needs. The tasks are summarized here to give you an idea of the underlying configuration that supports the subsequent sections of this chapter.

Creating Assignment Rules Based on Territories
The first step is to create assignment rules based on territories. For example, three of NREC’s territories are San Francisco, Peninsula, and East Bay. Each of these territories is served by a partner real estate agency. Each real estate agency is associated with a set of ZIP Codes, which you will define as criteria values in the next procedure. ■ ■ ■ San Francisco: 94101, 94102, 94103 Peninsula: 94301, 94401, 94010 East Bay: 94701, 94602, 94580

For the NREC example, you need to create an assignment rule for each territory listed above. The following procedures use San Francisco as an example.

To create assignment rules based on territories 1 2 3
From the application-level menu, choose Site Map > Administration - Assignment > Assignment Rules List. In the Assignment Rules list, click New. Enter a new record using the values as shown in the following table. Field Name Object Rule Group Minimum Score Assignee Filter Example Value San Francisco Opportunity Default Rule Group 0 All Above Minimum Although NREC is not using scoring, you must enter a value here. Use all assignees with an assignment score greater than or equal to the assignment rule’s minimum score. For a description of other methods read Siebel Assignment Manager Administration Guide. Description Unique name for the rule The object to be assigned

Specifying Assignment Criteria and Values for Rules
After defining assignment rules for each territory, you need to define the assignment criteria and criteria values. ■ Assignment criteria. Criteria used to determine which candidates qualify to receive the assignment. In the NREC example, the criteria compares the attributes of an opportunity and the attributes of a partner employee. Partner employees that have appropriate attributes qualify for the assignment. Criteria values. Specific values or range of values for a given criterion. Criteria values are used for comparison. In the NREC example, the values for the assignment criteria are the ZIP Codes that fall within a particular territory.

■

To specify territory assignment criteria and values 1 2
Navigate to the Assignment Rule View and select the assignment rule for San Francisco that you created in the previous section. Drill down on the Assignment Rule name (San Francisco). The Assignment Rule appears in the top form applet and Criteria list is displayed below it.

3

Add a new record in the Criteria list, as shown in the following table. Value for NREC Example Prospect ZIP Code

Field Rule Criterion

Description Defines the type of criteria to be used. In this case, the NREC developer needed to create the assignment criteria, because the attribute being used is a custom attribute defined by NREC. For information about defining assignment criteria, read Siebel Assignment Manager Administration Guide. Method used to match objects to candidates. For example, Compare to object compares criteria values to object attributes. Method used to match criteria values and candidates. Determines whether the criteria is required to qualify. Candidates that satisfy this criteria have this score added to their total score.

Comparison Method

Compare to object

Inclusion Required Score

Include Always 0

Developing and Deploying Siebel Business Applications Version 8.0

20 7

Assignment Manager ■ Adding Positions for Each Assignment Rule

4

In the Values List applet (located below the Criteria List applet), add new records for each of the ZIP Codes included in this assignment rule. For example, for the San Francisco territory assignment rule, you enter records for:
■ ■ ■ ■

94101 94102 94103 And so on

Adding Positions for Each Assignment Rule
Just as each rule has criteria that specify when the rule takes effect, each rule also has a list of positions, employees, or organizations that specifies the candidates for the assignment. In the NREC example, the assignment is based on positions. Each assignment rule is associated with the positions at the respective partner real estate agency. For example, the positions at the San Francisco Real Estate Agency are associated to the assignment rule for the San Francisco territory.

To add positions to an assignment rule 1 2 3 4
Navigate to the Assignment Rule view, and then select the assignment rule for San Francisco. Click the Positions view tab. Click the menu button and then choose New Record. The Add Positions dialog box appears. Select the Positions for the partner real estate agency to associate with this rule. In the current example, these are the positions for the San Francisco Real Estate Agency:
■ ■ ■

Releasing the Assignment Rules
After you have created and defined assignment rules, you must release them to instruct Assignment Manager to use these rules. NOTE: This procedure releases all assignment rules. Do not release assignment rules while associated server tasks are running.

208

Developing and Deploying Siebel Business Applications Version 8.0

Assignment Manager ■ Activating the Rules

To release assignment rules 1 2
Navigate to the Assignment Rules view, and then select the rule for San Francisco. Click Release. Assignment rules are released to Assignment Manager for use.

Activating the Rules
To activate Assignment Manager rules, you must start several Siebel Server components. However, it is best to start the components just once—after you have created your rules in both Assignment Manager and Business Process Designer. For this reason, instructions on starting the components appear only at the end of the Business Process Designer chapter, in “Activating the Rules” on page 218. For more information about Assignment Manager, read the Siebel Assignment Manager Administration Guide.

This includes tasks such as: ■ ■ ■ ■ Setting up your Siebel Server machine to interface to different messaging applications that Siebel Communications Server supports Configuring and administer the Siebel Communications Server components you need. you used one way— writing assignment rules using Assignment Manager. In the previous chapter.
Configuring Siebel Communications Server
To send email using Siebel Business Process Designer. NREC plans to use Siebel Business Process Designer to send an email notification to partner real estate agents when an opportunity has been assigned to them. The email is based on a simple template. This chapter introduces another way to customize your application—using Business Process Designer to automate business processes. A workflow process defines the steps necessary to send the email. including the Communications Outbound Manager server component Configuring Siebel Communications Server communications drivers and profiles Configuring additional recipient groups for your communications. For example. This chapter describes the tasks required to set up this business rule. based on Siebel business objects and business components
For detailed instructions on performing these configuration tasks. read Siebel Communications Server Administration Guide. A workflow policy triggers the process when it detects that an opportunity has been assigned. you must successfully configure your email communications application and configure Siebel Communications Server. including: ■ ■ ■ ■ “Creating an Email Template” on page 212 “Creating a Workflow Process” on page 213 “Creating a Workflow Policy” on page 217 “Activating the Rules” on page 218
The work in this chapter is done using the administration screens in NREC’s test environment.16 Siebel Business Process Designer
There are many ways to customize a Siebel application.0
21 1
. and informs them that they have a new opportunity in their queue.
Developing and Deploying Siebel Business Applications Version 8.

The template discussed in this section is an advanced template. and for replies in Siebel eMail Response.
To create an email template 1
From the application-level menu. An email message sent from the Siebel application uses an email template. Siebel field names are substituted with field values from database records. and Send Page.0
. similar to how a form letter uses a template.Siebel Business Process Designer ■ Creating an Email Template
Creating an Email Template
Before you can set up a workflow process to send an email message. you must first configure an email template. Some template elements are replaced in the final message text. The All Templates view appears. Simple templates are used for commands such as Send Email. enter a new record using the values as shown in the following table. Send Fax. Use the Administration . For example. such as the request triggered by a workflow process. There are two kinds of email templates: simple and advanced. choose Site Map > Administration .Communications screen to create email templates.
212
Developing and Deploying Siebel Business Applications Version 8. Field Name Channel Type Value NREC Email template Email
3
Click the Advanced view tab. Send Wireless Message.
2
In the Templates list. Advanced templates are used for outbound communication requests.Communications > All Templates.

In general. read Siebel Communications Server Administration Guide. Send Email business service. or other types of steps. Field Delivery Profile Value Default SMTP Profile Comments Created for the Internet SMTP/POP3 Servers communications driver. The profile must exist before you create the template. decisions. for an email template. enter a new record using the values as shown in the following table. The recipient group you specify here only determines which substitution fields are available for the template text. In the current example. Default subject line for the email. Thank you. Text to appear in the body of the template. A new opportunity has been assigned to you. End. The subject line can also include substitution fields.
Creating a Workflow Process
A workflow process defines the series of actions you want to occur in the workflow.0
21 3
.
Developing and Deploying Siebel Business Applications Version 8. which can be Start steps. invocations of business services methods. Predefined business services are available to use for performing actions such as sending email. After the workflow process is triggered. The email template is now available to use in the workflow process. ■ ■ ■ Start. Each workflow process must end with an End step. In this profile. it performs the specified actions. define the communications sender using the From Address parameter override. Each workflow process must begin with a start step.
To create the workflow process you use the Workflow Process features in Siebel Tools. The term in brackets is a substitution. subprocesses. and about communications drivers and profiles. The actual recipients are determined in the context in which the template is used. a workflow process consists of one or more process steps. the steps are simple. NREC
Public Template Text
For detailed information about email templates and fields.
Recipient Group
Opportunity Sales Team Members
Subject
New Opportunity in Queue TRUE Dear [Full Name]. Determines whether the template is available to all users.Siebel Business Process Designer ■ Creating a Workflow Process
4
In the Advanced form.

click Workflow Process.
Project
NREC Configuration
4
Right-click on the record and choose Edit Workflow Process. For the Workflow Process object.
a b c 2 3
Choose View > Options. Enter a new record with the values as shown in the following table.Siebel Business Process Designer ■ Creating a Workflow Process
Using Workflow Process Features in Siebel Tools
Figure 42 shows the Workflow Process Designer with the steps for the current example. A Workflow Process palette and workspace appear. Workflow Process Designer View with Flowchart of Current Example
To create a workflow process in Siebel Tools 1
Set Siebel Tools to display all objects within the Workflow Process hierarchy. Field Name Business object Value NREC New Opportunity Notification Opportunity Comments Unique name that identifies the process. select every object in its hierarchy and then click OK. Click the Object Explorer tab.
Figure 42.0
.
214
Developing and Deploying Siebel Business Applications Version 8.
In the Object Explorer. Business object is Opportunity because the goal is to trigger an action based on changes to the Opportunity record. The pick list contains only those business objects that have a primary business component defined.

Developing and Deploying Siebel Business Applications Version 8.0
21 5
. In the current example. Right-click and choose Show Input Arguments. Step Start Business Service End Name Start: NREC New Opp Email Business Service: Send Email End: NREC New Opp Email
8
For the Business Service step. edit the name for each step as shown in the following table. make these additional settings as shown in the following table.Siebel Business Process Designer ■ Creating a Workflow Process
5
Drag appropriate icons from the palette to the flowcharting workspace.
7
In the WF Steps window. a pink rectangle represents a business service.
6
Drag connectors from the palette to the flowcharting workspace to connect the steps of the process. For information about the different types of steps. Notice that different shapes and colors are used to represent different types of steps. Field Business Service Business Service Method Value Outbound Communications Manager CreateRequest
9
In the workspace. select the Business Service step. read Siebel Business Process Framework: Workflow Guide. The Input Arguments window appears below the workspace. as shown in the following illustration.

Siebel Business Process Designer ■ Creating a Workflow Process
10 In the Input Arguments window. This checks the syntax for validity. 13 Click Deploy (the button is located between the window title “Workflow Processes” and the field
headings). read Siebel Business Process Framework: Workflow Guide.
11 In the Object Explorer. read the following section.Business Process list) to make sure the NREC New Opportunity Notification workflow process is listed and has a status of Active.
Now you must create a policy that calls this workflow process.
Table 13.
4
Check the Active Workflow Processes list (below the Administration .
To deploy a workflow process 1 2 3
Log in to the client software as an administrator. and changes the status of the process to Active. The action in this example is to invoke the Account Status Change process.0
. add the records as shown in the following table.Business Process > Workflow Deployment and query for the workflow you just deployed. It also changes the status of the previous active version to Outdated. the next task is to deploy it in the Siebel application. click Activate. When picking
an Input Argument using the Business Service Method Arguments window.” After the workflow has a status of Completed. click Workflow Process to redisplay the list of workflows. 12 Select the NREC New Opportunity Notification workflow process. Navigate to Administration . For instructions on defining the action and conditions.”
216
Developing and Deploying Siebel Business Applications Version 8. registers run-time events if used.
Field Values for Input Arguments Type Literal Literal Literal Process Property Value NREC Email Message Opportunity Sales Team NREC Request Object Id Property Name
Input Argument PackageNameList RecipientGroup RequestName SourceIdList
For a detailed description of the arguments required for predefined business services. The status changes from “In Progress” to “Completed. “Creating a Workflow Policy. search on the Name field. With the workflow process selected. A Workflow policy consists of a condition and an action.

the condition is when an opportunity is assigned by Assignment Manager. add a new record to specify what actions the policy triggers. This value is the name of the process you created as described in “Creating a Workflow Process” on page 213. Field Name Program Workflow Object Value NREC Opportunity Notification Run Workflow Process Opportunity Comment The name of the action can be any name meaningful to you. When this occurs the workflow policy invokes the workflow process defined in “Creating a Workflow Process” on page 213. the action is to run a workflow process.
Creating a Policy Action
Workflow policy actions define the events that you want to occur when the conditions of your Workflow policy are met. you can define the conditions under which the action occurs. In the Actions list.
3
In the Arguments list.
Creating a Policy Condition
Now that you have defined the event that you want to occur as a Policy Action.Siebel Business Process Designer ■ Creating a Workflow Policy
Creating a Workflow Policy
Workflow policies define the conditions under which a workflow process is invoked. the required fields and their values are shown in the following table.
Developing and Deploying Siebel Business Applications Version 8. The workflow process must be active for it to appear in the drop-down list for the Value field. add records for the necessary arguments. You do this by defining a Policy Condition. In this example. In the NREC example. Name of the object associated with the workflow policy.0
21 7
.Business Process > Actions. Argument Argument Value Value ProcessName NREC New Opportunity Notification Comment Because you previously specified Run Workflow Process. ProcessName is the only item in the pick list.
To create a policy action 1 2
Navigate to Administration . the required fields and their values are shown in the following table. In the current example. This value specifies that the policy triggers a workflow process. In the current example.

In the Policies list.0
. you must create it.
In the Conditions list. enter the record as shown in the following table. Sequence of the Actions. Because this group does not currently exist. Field Action Sequence Value NREC Opportunity Notification 10 Comments This is the name of the Workflow Policy Action you created in “Creating a Policy Action” on page 217. complete the fields shown in the following table. ■ ■ Generate Triggers Workflow Monitor
218
Developing and Deploying Siebel Business Applications Version 8. Specify NREC in the Name field. For the current example.Siebel Business Process Designer ■ Activating the Rules
To create a policy condition 1 2
Navigate to Administration . click New. enter a new record.
Activating the Rules
To activate rules—whether they are Assignment Manager rules or Workflow rules—you must run the following Siebel Server components. Click OK.
Workflow Object Group
Choose this value because the action is based on changes to an Account field. Click Save. In the Workflow Groups dialog box.Business Process > Policies. enter the condition as shown in the following table. Condition Field Position ID Operation IS ADDED
4
In the Actions list. Field Name Value NREC Opportunity Notification Opportunity NREC Comment This name can be any name that is meaningful to you.
1 2 3 4 5 3
Click the select button in the Group field.

Select Generate Triggers from the Component Job list.SQL Comment This filename identifies the SQL script that needs to be run. For information about running Server Manager using the command line interface.
To generate triggers using the GUI 1 2 3
Navigate to Administration . Name Trigger File Name Value TRIGGER. To view changes to the state. In the Component Requests view. or command line mode. Setting this parameter to TRUE causes the SQL script to be run automatically. This is required for Oracle and IBM DB2.
Developing and Deploying Siebel Business Applications Version 8. Password for the table owner. click New. and its contents get created as a result of generating triggers. The file is created in the siebel_srvr_root directory during installation.Siebel Business Process Designer ■ Activating the Rules
Running Generate Triggers
Use the Generate Trigger (GenTrig) component on the Siebel Server to create database triggers. The Workflow Policies module of Siebel Business Process Designer uses these database triggers to identify which records may match policy conditions. Click the Component Request form applet menu. select Tasks. read Siebel System Administration Guide. the Status field contains either Success or Error. refresh the screen by clicking Run Query from the applet menu. read Siebel System Administration Guide. Click the Task Info Log view tab. The Generate Triggers component needs to be rerun whenever new policies are created or deleted. View log details by doing the following:
a b c
Click the Screen Enterprise Operation.
EXEC Table Owner Password
TRUE Your Password
5 6 7 8
Enter your Privileged User name and password. You can run the Generate Triggers component from either the Server Manager graphical user interface.0
21 9
. The following procedure is for the GUI. Upon completion. This creates a new line entry but does not start the task. In the Show field.
4
Click New in the Component Job Parameter list and define the parameters as shown in the following table.Server Management > Enterprises.
For more information about administering server component parameters. then select Submit Request.

The alias can not contain blank spaces. In the lower Component Definitions list. A new record appears. Enter the name of the Workflow Policy Group for the requests the component will process.Server Configuration > Enterprises. choose the Default Tasks parameter. Set the Value to 1.
4 5
Optional. perform a query for the component definition. choose Enable Component Definition.
To create a Workflow Monitor Agent component definition 1 2
Navigate to Administration .
3
From the upper Component Definitions list menu. You may make additional changes to the component parameters.
To set parameters and activate a Workflow Monitor Agent component definition 1 2 3
In the upper Component Definitions list. To view the definition. Field Name Component Type Component Group Alias Value NREC’s WorkMon WorkMon NREC Workflow Component Group NRECWorkMon Description Name of the component. From the upper Component Definitions list menu.
4
Complete the fields as shown in the following table. The definition state changes from Creating to Active. read Siebel Business Process Framework: Workflow Guide. Alias for the component. choose Save Record.Siebel Business Process Designer ■ Activating the Rules
Starting Workflow Monitor Agent
You must start two Workflow Monitor Agent tasks: one for Assignment Manager and the other for Workflow policies.
5
From the upper Component Definitions list menu. Click the Component Definitions tab. choose New Record. and stop when the Siebel server shuts down. Worfkow Monitor Agent component type. For a description of Workflow Monitor Agent parameters. choose the Group Name parameter. The Enterprise Configuration view appears. Select an existing component group. This sets the component to start when the Siebel server starts. you must perform a query. In the lower Component Definitions list.0
. The component definition is saved. Two Component Definitions lists appear.
220
Developing and Deploying Siebel Business Applications Version 8.

To create a rule set 1 2
In a Siebel employee application. The tasks in this chapter are performed using administration views available in the Siebel Web Client. When a partner real estate agent logs in to NREC’s application. You create one rule set to contain the business rules for the NREC example. The Rule Sets view appears. Add a new record to the Rule Sets list using the values as shown in the following table. the agent can access only the houses in the House Detail view that are in the same ZIP Code as is defined on the user’s profile.Personalization > Rule Sets. The filter is based on the ZIP Code value of the house record and the user’s Postal Code profile attribute. Siebel Personalization provides you with another way to customize the business logic of your application without having to work in Siebel Tools and recompile an SRF file.17 Personalization
This chapter describes the steps for using Siebel Personalization to create a simple business rule that filters NREC’s list of houses. This chapter includes the following topics: ■ ■ ■ ■ ■ Creating Rule Sets Associating Rule Sets with Applets on page 224 Creating Rules on page 224 Using the Expression Designer on page 225 Testing on page 227
Creating Rule Sets
Rule sets are collections of the business rules that define how content is displayed. Field Name Active Value NREC House Filter TRUE
Developing and Deploying Siebel Business Applications Version 8. Like Siebel Workflow and Siebel Assignment Manager.0
22 3
. NOTE: ZIP Code is a field that you added to the Internal Products business component in “Configuring the House Detail View” on page 87. navigate to Administration .

the applets to which the Personalization rule applies are the Product Form Applet and the Product List Applet. Choose the order in which the rule sets are evaluated. they can access only the houses for sale in their area. navigate to Administration .
Creating Rules
Personalization rules control how content is targeted to users. These are the applets to which the business rules for the rule set apply. Field Name Sequence Start Date Value NREC House Filter 1 Leave blank Description This is the rule set you created in “Creating Rule Sets” on page 223. The date after which the conditional expression is not evaluated.0
. the conditional expression is evaluated continuously after the Start Date. The date when the conditional expression starts to be evaluated. In the Rule Sets list. NREC is using Personalization to filter the list of houses for sale based on a user’s ZIP Code. If both Start and End Date are blank. If Start Date is blank. enter a new record for the Product List Applet.
2 3
In the Applets list.
To associate a rule set with an applet 1
In a Siebel employee application. The logic expressed in Siebel Query Language is: [Zip Code] = GetProfileAttr(‘Me.Postal Code’) NOTE: ZIP Code is a field that you added to the Internal Products business component in “Configuring the Internal Product Business Component” on page 92. the expression specifies that when displaying records from the Internal Product business component only show those records that have a ZIP Code field that matches the user’s Postal Code attribute. For the NREC example. In this case. The Applets view appears.Org. you write an Expression personalization rule. If End Date is blank. the conditional expression is always evaluated. or Invoke Method. the conditional expression is evaluated continuously or until the End Date is reached. Expression rules use Siebel Query Language to set the parameters that control the content displayed to users. add a new record as shown in the following table.Personalization > Applets. There are three types of business rules: Business Service.
End Date
Leave blank
4
Repeat Step 1 through Step 3 to associate the Product Form Applet with the NREC House Filter.
224
Developing and Deploying Siebel Business Applications Version 8. Expression.Personalization ■ Associating Rule Sets with Applets
Associating Rule Sets with Applets
Rule sets are associated with one or more applets. When users view the list of houses for sale. In this case.

navigate to Administration .Org. Required. read “Using the Expression Designer” on page 225. read Siebel Personalization Administration Guide.
To create a rule 1 2 3
In a Siebel employee application. choose the NREC House Filter rule set that you created as described in “Creating Rule Sets” on page 223. This procedure guides you through the steps for creating the Include Expression defined in Step 3 on page 225.Personalization ■ Using the Expression Designer
For more information about other types of personalization rules and Siebel Query Language.0
22 5
. enter a new record using the values as shown in the following table. This procedure is an alternative to typing the expression directly into the Include Expression field. Field Name Sequence Value NREC House Filter 1 Description Choose a name that suggests the purpose of the rule.
Using the Expression Designer
Use the Expression Designer to write personalization rules without having to learn Siebel Query Language.Post al Code’)
NOTE: You can type the expression directly into the Include Expression field or you can click the select button to invoke the Expression Designer.
Rule Type Active Include Expression
Expressions TRUE [ZIP Code] = GetProfileAttr(‘Me. Evaluates inclusion and exclusion expressions directly. In the Rule Sets list. For instructions on using the Expression designer to enter the Include Expression for this example.
Developing and Deploying Siebel Business Applications Version 8. Enter numbers in this field to set the order in which the rules are evaluated. The Expression Designer provides you with a drag-and-drop interface for writing complex expressions. Used with the Expressions rule type. It provides you with a drag-and-drop interface and helps you validate syntax of the expression. Check the box to use the rule. An expression that sets parameters to include content.Personalization > Rule Sets. In the Rules list.

and then click Add Element. <All> from Subcategories. Click = in the Quick bar. and Zip Code from Elements.0
. Me.
2
Choose Business Component Fields from Categories. The Expression box displays the completed rule as shown in the following illustration. The Expression box displays [ZIP Code]=. The Expression Designer appears as shown in the following illustration. The Expression box displays [ZIP Code].
3 4
Place the cursor after [ZIP Code] in the Expression box.Postal. and then click Add Element.Org. Show as String from Subcategories.Code from Elements.
226
Developing and Deploying Siebel Business Applications Version 8. Choose Me Profile Attributes from Categories.
5 6
Place the cursor after =.Personalization ■ Using the Expression Designer
To write a personalization rule using the Personalization Business Rules Designer 1
Click the select button in the Include Expression field.

enter the command string for the Mobile Web Client.Personalization ■ Testing
[ZIP Code] = GetProfileAttr(‘Me. navigate to Administration . NOTE: For the current example. This is done in the Test view under Administration .cfg” /d <data_source> where:
■
<Siebel_install_dir> is the full path to the client installation directory
Developing and Deploying Siebel Business Applications Version 8.
3
In the Test Application field. use the House Detail view in your configured application to enter a few house records. Only records with that ZIP Code appear. You may have to add the data source using the /d switch. The Expression Designer closes and the expression is displayed in the Include Expression field of the Applet Rules More Info form. This is the user name and password of the user to use to test the personalization rules.
To test personalization rules 1
In a Siebel employee application.Org. For information about the House Detail View. Be sure to enter records with several different ZIP Codes.
Testing
Personalization rules can be tested in a staging environment before being used in the production environment. C:\<Siebel_install_dir>\BIN\siebel.
2
Enter a Primary User Login and Primary User Password.Personalization.Postal Code’)
7
Click Save to validate the rule. and then copy and paste the command string from the Target field into the Test Application field. to test NREC’s personalization rule.0
22 7
. choose Properties.exe /c “C:\<Siebel_install_dir>\bin\ENU\ <config_file>. NOTE: You can right-click your program icon. You will define one of these values as a profile attribute when you test.Personalization > Test. The Test view appears. use SADMIN and SADMIN. read “Configuring the House Detail View” on page 87. For example.

Org.
4
Click Load.
228
Developing and Deploying Siebel Business Applications Version 8. uagent. or ServerDataSrc
For example: C:\Program Files\Siebel\7. The persistent user profile attributes of the primary user are loaded in the Primary User Attributes list with a Me. Person-related attributes have the value Person in the Source field. For example.
7 8
Navigate to the House Detail view and test the results. A new instance of the specified application opens.Personalization ■ Testing
■ ■
<config_file> is the application configuration file. click Save in the test view. Only records that have a ZIP Code value of 94121 appear. To save the test setup. the Test Mode dialog box appears after you complete Step 6 with instructions about how to launch a new instance of the application. read Siebel Personalization Administration Guide. When testing using the Siebel Web Client.Postal Code primary user attribute and enter a value. enter 94121. http:// <machine_name>/eChannel. For the current example.cfg" /d Sample NOTE: You can also enter the URL for a Siebel Web Client. For example.7\client\BIN\ENU\scw. prefix.
5
Select the Me.exe /c "C:\Program Files\Siebel\7. Sample.
6
Click Test.7\client\BIN\siebel. for example.0
. Organization-related attributes have the value Organization. a new instance of Siebel Partner Portal opens.cfg for Siebel Call Center and siebel for Siebel Sales <data_source> is the database to which to connect: Local. For more information.

This process is known as synchronization. Siebel Server.18 Implementing Siebel Remote
This chapter begins by explaining how National Real Estate Clearinghouse (NREC) uses Siebel Remote. these transactions are uploaded from the mobile Web client to the server during synchronization. In a similar manner. to detail the Siebel Remote scenario. Siebel Remote Client software tracks the changes as synchronization transactions. these transactions are downloaded from the server to the laptop. when Chris connects to the Siebel Remote server through a dial-up networking connection. As Chris Strong enters and updates information in the local database on the laptop. the chapter outlines and briefly describes the tasks to set up a new Siebel Remote User. and outlining the tasks to set up the Siebel Remote server. transactions occurring on the server that are applicable to Chris are tracked. Siebel Remote supports mobile computing by allowing field personnel to share current information with virtual teams of other mobile and connected users across the organization. NREC is using Siebel Remote so that its employees can connect to a Siebel Server with their laptop computers and exchange updated data and files. the mobile Web client is a laptop computer used by a field sales or service representative. Subsequently. During synchronization. Chris Strong is a mobile user. Siebel Remote Hardware Architecture
Developing and Deploying Siebel Business Applications Version 8. Users can access their data locally. Next. Figure 43 illustrates the main elements of the Siebel Remote architecture.0
22 9
.
Figure 43. or File System. A mobile Web client can download a portion of the Siebel database and the Siebel File System to a laptop. This chapter uses Chris Strong. without being connected directly to the Database Server. illustrating the hardware architecture. Typically. a real estate agent with NREC. Then the chapter describes the process for synchronizing a mobile Web client.

For details. Setting up a new Siebel Remote user entails the following tasks. For details. For details. Enable network connectivity.
1 2 3 4 5 6 7 8
Create a mobile Web client user account and privileges.
NOTE: For information about advanced topics. For details. read Siebel Remote and Replication Manager Administration Guide. For details. read Siebel Security Guide and Siebel Remote and Replication Manager Administration Guide. Set synchronization preferences. Register a mobile Web client. Set up mobile Web client hardware and software. read “Establishing Autodial Preferences” on page 231. Establish autodial preferences. ■ ■ ■ ■ Setting Siebel Remote System Preferences Disabling Local Access to All Views Starting Siebel Remote Server Components Generating a New Database Template
For detailed information on these and other Siebel Remote administration tasks. For details. The Siebel Remote server provides an interim storage area for data required to synchronize mobile databases with the Siebel database server. read “Setting Up Mobile Client Hardware and Software” on page 231.
230
Developing and Deploying Siebel Business Applications Version 8. Initialize a mobile Web client local database. txnroute. such as authentication or conflict detection and resolution. Run database extract for a mobile Web client. read “Setting Siebel Remote Preferences” on page 232.
Setting Up a New Siebel Remote User
Setting up a mobile Web client involves certain tasks for both the Siebel Remote server and the mobile Web client. read “Initializing a Mobile Web Client Local Database” on page 235. read “Creating a Mobile Web Client User Account and Privileges” on page 231. For details. read “Running Database Extract for a Mobile Web Client” on page 234.Implementing Siebel Remote ■ Setting Up the Siebel Remote Server
Setting Up the Siebel Remote Server
The Siebel Remote server runs the Siebel Remote components (such as txnproc.0
. The administrator must repeat each of these steps for each mobile client. An administrator at NREC completed the entire process of setting up each mobile client. read “Registering a Mobile Client” on page 232. For details. Setting up the Siebel Remote server in preparation for setting up Siebel Remote users includes the following tasks. NREC decided not to rely on end users to complete the configuration because the administrator could be more thorough and accurate in completing each task. and others) and manages synchronization sessions with mobile Web clients. read “Enabling Network Connectivity” on page 231.

This step may include: ■ ■ Configuring users. From the Siebel Remote Preferences dialog box.
Establishing Autodial Preferences
A mobile client user using Microsoft dial-up networking can configure Siebel Remote to automatically to establish a connection with the Siebel Remote server when the user initiates a synchronization session. For more information about this topic. Click OK. modems. Installing disk drives.
Setting Up Mobile Client Hardware and Software
Install the necessary hardware and software on the mobile Web client.
NOTE: You must define your phone book entries before synchronizing.Implementing Siebel Remote ■ Setting Up a New Siebel Remote User
Creating a Mobile Web Client User Account and Privileges
NREC chose not to use authentication for mobile Web clients. click Setup. you need to create accounts for each client depending on the authentication method. it is also the default configuration. NREC did not need to create any accounts or passwords for these. memory cards. Because it is the easiest and most popular configuration. read Siebel Remote and Replication Manager Administration Guide. and then Synchronize or close the dialog box. Therefore.
Enabling Network Connectivity
Install the necessary hardware and software on the mobile Web client so the mobile Web client can exchange files with the Siebel Remote server. click the Connection pick list and choose the appropriate connection. For more information about network connectivity. This step may include choosing communication settings and installing networking cards.0
23 1
. read Siebel Installation Guide for Microsoft Windows. In the Siebel Remote Synchronize dialog box.
For more information. If you want to authenticate mobile Web clients. select File > Synchronize > Database.
Developing and Deploying Siebel Business Applications Version 8. and software.
To establish autodial preferences 1 2 3 4
From the application-level menu. and operating system software. read Siebel Installation Guide for Microsoft Windows.

Setting Synchronization Options
The Siebel Remote client reads configuration parameters in the Siebel configuration file (default is siebel. configuration information is read from the CFG file of that particular application. then configuration information is read from the uagent. that is. if Siebel Call Center is used. periods.cfg in the client bin directory with default values for each configuration parameter. choose Site Map > Administration . using File > Synchronize > Database. It assumes the Siebel Administrator has previously set up Chris Strong as an employee in the Siebel application. This view helps mobile Web clients resolve data merge conflicts on their local databases by showing conflict information after synchronization.cfg.0
. It can contain only Roman. If your deployment does not use Replication Manager.cfg) to specify the location of the Siebel Server. CAUTION: The mobile Web client name and the User ID must be entered in uppercase letters and be eight characters or less. For more details about synchronization parameters and enabling encryption for synchronization networking. read Siebel Remote and Replication Manager Administration Guide. read Siebel Applications Administration Guide. click the menu button and choose New Record.
232
Developing and Deploying Siebel Business Applications Version 8. It cannot include spaces. Siebel Remote uses the mobile Web client name to create inbox and outbox directories on the Siebel Server. then the appropriate node is HQ. When Chris Strong and other NREC mobile users perform synchronization within the application. you must set the values for the configuration parameters. or other invalid characters ( / \ : * ? “ < >|) as in the DOS file naming schema.
To register a new mobile Web client on a parent node 1 2
From the application-level menu. The Siebel installation utility creates a siebel. In the New Mobile Client form. NOTE: It is important to make sure mobile users have the Client Status view in their responsibilities. there are no tasks for setting remote preferences. In the Parent Server list. For additional detail regarding the setting up of employees.Implementing Siebel Remote ■ Setting Up a New Siebel Remote User
Setting Siebel Remote Preferences
NREC is using the default settings for the Siebel Remote parameters established during installation in the client configuration file.
Registering a Mobile Client
This section describes how to register a mobile Web client. alphanumeric. For example. Before using Siebel Remote. and the _ or characters.
3 4
In the Mobile Clients list. enter Chris Strong in the Mobile Client field.Remote > Mobile Clients. A good practice is to use the mobile Web client User ID (next step) as the mobile Web client name. Thus. choose the appropriate parent node.

is one of the following:
■ ■ ■ ■
Sales Representative Minimal Data Analyst Sales Manager
The corresponding Responsibility with the Routing Model suffix relates to the data routing model assigned in Step 6 above. Catalog Category.par_name and EIM_NODE. The App Server Name field is not populated until the Database Extract is run for the mobile user. The Sync Password field is used by the Synchronization Manager if the authentication method in the Siebel Server Component Parameters is set to Siebel. For more information about language preferences. click the select button and choose the Sales Representative routing model and click Pick.
9
Navigate to Administration . The union of the routing rules determines whether a record is routed to a mobile Web client. Although these columns are not required for EIM. Literature. click the select button and choose the User ID for Chris Strong and click OK. these columns are populated by default. and choose the corresponding Responsibility with the Routing Model suffix.0
23 3
. Using a language preference the mobile user can download data in a preferred language.
6
In the Routing Model field. This helps optimize the size of the local databases. Set the password in this field and give it to the mobile user. Product. records without an HQ node as the parent node do not appear in the Mobile Clients view. read Siebel Remote and Replication Manager Administration Guide. click the select button. For more information about corresponding routing models and how these help optimize the size of local databases. they are required for Siebel Remote. When you enter mobile users using the Mobile Clients view. for the following dock objects that contain Translation Tables: LOV. or languages.
8
Complete the remaining fields as appropriate. This is required because Chris Strong’s data routing model. NOTE: Each mobile user is associated with one Routing Model.
Developing and Deploying Siebel Business Applications Version 8. Catalog. read Siebel Remote and Replication Manager Administration Guide and the release notes documentation for your application.Applications > Responsibilities > Responsibilities list.Implementing Siebel Remote ■ Setting Up a New Siebel Remote User
5
In the User ID field.par_node_type_cd. The parent node is stored in the following two columns: EIM_NODE. The User ID is used to access Chris Strong’s local database during initialization and synchronization. A Routing Model includes a set of routing rules. At the time the mobile Web client record is created (S_NODE) the APP_SERVER_NAME field is NULL. and choose English as the preferred language for Chris Strong.
7
In the Language(s) field. NOTE: If you use EIM to load mobile user records. read Siebel Remote and Replication Manager Administration Guide. Sales Representative. For more information on data routing models.

In the Add Users Selection dialog box. choose Submit request. Do not modify the contents of this directory under any circumstances. The following example shows a portion of the server directory tree after you run Database Extract for Chris Strong. The required parameter for Database Extract is Client Name.
To run a database extract for a mobile Web client 1 2 3 4
From the application-level menu. Click the Component Jobs tab. choose Site Map > Administration . and may affect the outcome of the database extract. the name of Chris Strong’s mobile Web client.
Running Database Extract for a Mobile Web Client
The database extract process retrieves data visible to Chris Strong from the server database. NOTE: The installation program also places a directory named txnproc in the docking directory within the Siebel server root directory. The value for the Client Name parameter is CSTRONG. and click New.
Server Directory Tree After Running Database Extract
The Database Extract program creates the appropriate directories for Chris Strong on the Remote server. add a new record.
5
From the Component Jobs menu. Before running a database extract for Chris Strong.Implementing Siebel Remote ■ Setting Up a New Siebel Remote User
a b
In the Users list. siebel docking cstrong
234
Developing and Deploying Siebel Business Applications Version 8. It creates compressed files that contain data to be loaded into the local database when Chris initializes the laptop.0
. In the Component Job Parameters list. For more information on positions. you must make sure that your organization’s reporting hierarchies are updated and that Chris has a valid position in your organization’s hierarchy. The resulting information is used by the application’s routing rules.
The mobile client database is extracted. click New and add the necessary parameters. It retrieves data according to routing rules that define the level of access to information for Chris Strong. read Siebel Applications Administration Guide. select the mobile user and click OK. This may take a few minutes. choose Database Extract from the pick list. In the Component/Job field.Server > Enterprise Operations.

Implementing Siebel Remote ■ Setting Up a New Siebel Remote User

inbox outbox txnproc For more information about this topic, read “Sample Directory Tree After Running Database Extract” on page 66.

Initializing a Mobile Web Client Local Database
The volume of information that must be downloaded from the Siebel Remote server to initialize a mobile Web client’s database is usually substantial. Establish a LAN (rather than a modem or WAN) connection between the server and the mobile Web client for this process. Alternatively, the local database can be initialized from a CD-ROM or other media—if compressed files have been copied into the folder specified as FileSystem parameter. For more information about extracting to a CD, read Siebel Remote and Replication Manager Administration Guide. NOTE: To initialize a mobile Web client database, the TableOwner parameter in the CFG file must be set to Siebel (the default).

To initialize the mobile Web client database 1 2
Establish a connection between the Siebel Remote server and Chris Strong’s laptop. In the mobile Web client’s Siebel program group, click the Siebel Remote icon. NOTE: Verify that the icon is pointing to the appropriate CFG file. The default is siebel.cfg.

3

In the Siebel Remote Parameters dialog box, enter the information as shown in the following table. Field Client Name User Name Password Entry CSTRONG (registered Siebel client name). CSTRONG (login name). CSTRONG (If an authenticator password was assigned, enter that instead of CSTRONG).

4 5

Click Continue. Monitor the process for errors.

To initialize the mobile client database during login
■ Log in to the local database when starting the application. When Siebel Business Applications cannot find a local database, it attempts to initialize the local database. Follow the prompts.

Developing and Deploying Siebel Business Applications Version 8.0

23 5

Implementing Siebel Remote ■ Synchronizing a Mobile Web Client

After the initialization completes, Chris Strong’s laptop is ready for use in the field. Chris Strong needs to resynchronize with the Siebel Remote Server on a frequent basis. Instructions for this process are included in the next section, “Synchronizing a Mobile Web Client” on page 236. There is an auto synchronization option to help maintain the frequency of synchronization.

Synchronizing a Mobile Web Client
This section describes the processes for synchronizing a mobile Web client.

Routing and Merging
On the Siebel Remote server, the Transaction Router and Transaction Merger components continuously route and apply transactions for mobile clients. Figure 44 illustrates the processes that occur when a mobile client is synchronized.

How Changes Are Propagated To and From a Mobile Web Client
Between synchronization sessions, the Siebel Remote server prepares transactions applied to the database server by both mobile and connected users. Siebel Server components write the transactions to a separate directory for each mobile user, such as Chris Strong. These transactions, combined with items from the file system, are downloaded to Chris during the next synchronization session. Items from the file system include updated, published, or requested marketing literature, correspondence templates, and other types of file attachments. A similar process occurs on Chris’s laptop as well, although without the server component.

Process Flow for Changes by Connected Users
This section describes the process flow for downloading changes on the server database to local databases, such as Chris’s. The flow begins from the time a connected user creates a new opportunity until it appears in Chris’s local database. This specific process flow includes an example of a telesales representative in a Call Center. The telesales representative talks to potential customers responding to a new NREC advertising campaign. The telesales representative decides to create a new opportunity record for one of the more promising responses. The figure below illustrates this flow and includes the following groups of steps.

1

The telesales representative creates a new opportunity record—a transaction saved in the opportunities table on the server database. A copy is saved to the master transaction log.

Developing and Deploying Siebel Business Applications Version 8.0

23 7

Implementing Siebel Remote ■ Synchronizing a Mobile Web Client

2

A mobile user invokes a synchronization session from the laptop. The mobile user can use the Siebel client while the Siebel Remote client applies the changes to the local database, as shown in Figure 45.

Figure 45. Process Flow for Changes by Connected Users CAUTION: Users must never directly modify the local transaction log. The Siebel Remote synchronization client automatically purges the local transaction log table. For more information about process flow for changes by connected users, read Siebel Remote and Replication Manager Administration Guide.

Process Flow for Changes Made by Mobile Users
Mobile Web clients, such as Chris, use a local database to store data for user access. The local database contains Siebel Business Applications tables that store user data. The local database also contains a local transaction log to store transactions created by the mobile user. Siebel Remote forwards these transactions to the Siebel Remote server when the client synchronizes. This section provides a description of each phase of the process flow, from the time when Chris modifies the new opportunity until the time when the modifications appear in the Server database. For this example, assume that Chris is meeting with the potential new client, represented by the opportunity record entered by the telesales representative in the previous section. The figure below illustrates this flow and includes the following groups of steps.

238

Developing and Deploying Siebel Business Applications Version 8.0

Implementing Siebel Remote ■ Synchronizing a Mobile Web Client

1 2 3 4

As a result of the meeting, Chris makes changes to the Opportunity record in the local database. Chris enters these changes immediately after the meeting while working offline. The modified opportunity record is saved to the Opportunities table in Chris’s local database. The transaction record is saved to the Local Transaction log. Chris synchronizes the laptop. The Siebel Remote client extracts pending transactions from the Local Transaction log into transaction files (.dx). The client then places these DX files in the outbox directory on Chris’s laptop. Siebel Remote connects to the server and the DX file is sent to the server and inserted in the database as shown in Figure 46.

Synchronizing a Mobile Web Client Machine
Chris must synchronize frequently to obtain and view possible updates in the server database. Also, there may be updates to the store of documentation, marketing literature, and sales brochures in the file system.

image files. rather than copying this user data from test to production. after having completed an EIM import. as updates may have continued to be made to the data in your legacy application.” Modified files. responsibilities. However. “Migrating to the Test Environment. contacts. such as employees. such as accounts. The procedure is the same as the one you followed in moving configurations from development to test. and cascading style sheets. specifically Assignment Manager rules and Workflow processes and policies. Use the Repository Migration Utility to move the latest Tools configuration from your test environment to your production environment.0
24 1
. Therefore.19 Deploying the Application
This chapter covers the steps that NREC took to migrate its data and application from the test to production environments. “Migrating to the Test Environment. such as SRF files. and so on. For more information about EIM imports. and Personalization rules and expressions. The data you must move includes the following: ■ Tools configurations.” Transactional data. Many of the tasks in this section were covered in previous chapters. including schema changes. read Chapter 13. Web templates. you are ready to move data from the test environment to the production environment. this snapshot may by now be out-of-date. You have a snapshot of this data in your test environment. You must copy any changes you made to Web templates and related files.
Developing and Deploying Siebel Business Applications Version 8. as described in Chapter 12. You must copy this information from either your test environment or your legacy application to your production environment. Setup data. do another EIM import from your legacy application—but this time directly into your production environment.
■
■
■
■
This chapter gives instructions for the last two items—migrating setup data and program data from test to production. opportunities. and so on. Program data. This chapter includes the following topics: ■ ■ Migrating Data from the Test Environment to Production Rolling Out to End Users on page 244
Migrating Data from the Test Environment to Production
After completing your testing. “Using EIM to Load Data Into the Test Environment” and Siebel Enterprise Integration Manager Administration Guide. positions. You must copy this information from your test environment to your production environment. Refer to the instructions in Chapter 12.

■ ■ ■
EIM_ASGN_GRP EIM_ASGN_WL EIM_ASG_GRPDTL
For more information about EIM. read Siebel Enterprise Integration Manager Administration Guide. For example. Select the process or processes you want to export. using the following interface tables. choose Export Workflow. For information about using EIM. Because the setup data in your test environment may be obsolete by the time you are ready to move into production. read Siebel Enterprise Integration Manager Administration Guide.
Moving Assignment Manager Data
You can use EIM to move your Assignment Manager data. positions.
To export a process 1 2 3 4
Log in to the application in the test environment. specifically Assignment Manager. press and hold the CTRL key while selecting the processes.0
. To select more than one process. it is a good idea to move the data into the production server directly from your legacy application. Moving each of the two types of data requires you to follow a different procedure.Business Process > Workflow Processes > All Processes. Navigate to Administration . Workflow and Personalization data from the test environment (where you created it) to the Production environment. responsibilities.
Moving Program Data
You must move program data. use the EIM_EMPLOYEE interface table to import employee data from your legacy application into the production server. From the Processes list menu.
Moving Workflow Data
Moving Workflow data consists of moving data about workflow processes and moving data about workflow policies and groups. Setup data includes information about employees. as described in this section. using EIM for the import.
To move Assignment Manager data
■ Use EIM. The XML workflow process definition appears.Deploying the Application ■ Migrating Data from the Test Environment to Production
Moving Setup Data
You must move setup data into your production environment.
242
Developing and Deploying Siebel Business Applications Version 8. and so on.

NOTE: When exporting a process containing subprocesses. events. events. read Siebel Enterprise Integration Manager Administration Guide. Click Open.
Moving Personalization Data
Personalization rules. Subprocesses are not exported automatically. file name and the XML file name extension. and actions are exported in one XML file. The File Download window appears.0
24 3
. Select a path and file name of the process to import.
To export personalization data as an XML file 1 2
Navigate to any Administration . and then click Save. Enter the file path. If you selected more than one process to export.
To move workflow policies and groups
■ Use EIM.Deploying the Application ■ Migrating Data from the Test Environment to Production
5 6
From the XML dialog box menu. The process imports with a status of In Progress. and then choose XML Export.
Developing and Deploying Siebel Business Applications Version 8. using the following interface tables:
■ ■ ■
EIM_WFM_GROUP EIM_WFM_RULE EIM_WFM_ACTION
For more information about EIM. Click the menu button.Personalization view. choose File > Save As. the newly imported process definition’s version number increments by one. and actions can be exported as an XML file for later importation into another Siebel environment.
To import a process definition 1 2 3 4 5
Log in to the application in the production environment. The process or processes are exported. for example Views.
Exporting Personalization Data as an XML File Personalization data rules. choose Import Workflow. the processes are saved to one XML file. Navigate to Administration . From the applet menu. you must also export the subprocesses.Business Process > Workflow Processes > All Processes. NOTE: If a process definition of the same name exists in the target environment.

A dialog box appears.
4
Save the XML file. Click the menu button. This section follows the NREC example to show how NREC rolled out the application to end users. and then click OK. and then click OK. Choose a file. a message displays how many records had conflicts and were inserted. Click Submit. you need only tell users the URLs to use to log in to for each application.ooo. The default file name is personalization. and skipped. the applications for Web Client users reside on the server. Therefore. events. A dialog box appears prompting you for a file name.Deploying the Application ■ Rolling Out to End Users
3
Click the Save This File To Disk option button. The personalization data is imported. A dialog box appears prompting you specify a file name and storage location.0
. migrating data provides the production server with the latest data. The next logical step in the deployment is to roll out the applications to users.xml. This process can take several minutes.
Rolling Out to End Users
As described in “Migrating Data from the Test Environment to Production” on page 241. and actions can be imported from an XML file generated by a previous export.
To import personalization data from an XML file 1 2
Navigate to any Administration .
244
Developing and Deploying Siebel Business Applications Version 8. for example Views. as long as the client machines have a Web browser.Personalization view. When the process is finished.
Rolling Out to Siebel Web Client Users
With the exception of the Web browser.
3 4 5
Click Browse. updated. and then choose XML Import.
Importing Personalization Data Personalization rules.

You can distribute the program through any other file distribution mechanism. After the Siebel Packager utility assembles the software into a single. This initial installation serves as a model for other installations.
■ ■ ■
Select Custom during client installation and be sure to select the Packager Utility option.
Developing and Deploying Siebel Business Applications Version 8. NREC chose network distribution. because receiving Siebel Anywhere kits requires the Siebel client to be already installed on the user’s machine. CD-ROM. and Web template files. You can use it only for upgrades. as specified when running the Siebel Packager utility) for the installer that it creates. However. the Siebel Packager utility reproduces this model installation exactly. you can distribute this installer to your users. For example.Deploying the Application ■ Rolling Out to End Users
Rolling Out to Mobile and Dedicated Web Client Users
The Siebel Packager utility creates custom software installation packages for distribution to end users. which may be performed by running the Siebel Packager utility against the initial installation.
NOTE: Be sure to customize this model Siebel client installation so that it is identical to how you intend to package it. This installer contains the Siebel Mobile and Dedicated Client executables and your custom configuration. You can copy the customized software package onto CD-ROMs for distribution to end users.
■ ■
Preparing to Use Siebel Packager Utility
You must complete the procedures in this section before using the Siebel Packager utility. The Siebel Packager utility uses the files from this client installation (or another client installation. self-extracting file. When creating the custom installer.
2
Copy any changed files to the appropriate directories under siebel_clnt_root. such as email or FTP. or under the root directory of another installation that you use to create the custom installation package. However.
To prepare to use the Siebel Packager utility 1
Make sure the Siebel Packager utility has been installed on a client machine in your Production environment. as described in “Making Your Customized Installer Available to End Users” on page 248. You can use Siebel Anywhere to distribute and execute the installation automatically for both dedicated and mobile users. The rest of this chapter refers to the root-level directory of the client installation as siebel_clnt_root. The installer creates a Siebel environment on the end users’ machines that duplicates the environment on the administrator’s client machine. Other methods.0
24 5
. Such files may include custom repository (SRF) or configuration (CFG) files. you cannot use Oracle’s Siebel Anywhere for an initial rollout. For more information. Siebel Packager packages can also be distributed in the following ways: ■ Siebel Anywhere. read Siebel Anywhere Administration Guide.

ini file.
Component BIN
FONTS LOCAL LOCALE
246
Developing and Deploying Siebel Business Applications Version 8. This file is largely self-documented to help you in customizing it.prf. including the required DLL files. located in the siebel_clnt_root\local directory.ini file used by the standard Siebel client installer prompts the user for parameters— not usually the desired behavior for an end-user installation.cfg file with your customized configuration file. and the session file.
Software Installed in the Test Environment Description Siebel Executable Files (Binaries) located in the \siebel_clnt_root\bin directory. Of the different installable components that make up a Siebel application.
Table 14. Do not omit this module when creating a package. directory. Location of the local database.0
.
4
Create a custom siebel. siebel. Contains font files. NREC chose to package the ones described in Table 14. read Siebel Installation Guide for Microsoft Windows. If you need more information. located in the siebel_clnt_root\fonts directory. configuration files.
Preparing Siebel Components for Packaging
You can use the Siebel Packager utility to package the Siebel client installation software.ini file customized to your environment.ini file controls the following behavior of the installer that the Siebel Packager utility creates:
■ ■ ■
Whether or not the Siebel client installation program checks that the appropriate versions of third-party software have been installed on the client machine Whether or not the data sources that the Siebel application relies on are installed and how they are configured Which installation dialog boxes users are presented at run time and which installation parameters they can specify
The siebel. During the packaging process. located in the siebel_clnt_root\locale. The siebel. Language-specific files.Deploying the Application ■ Rolling Out to End Users
3
Make sure that you have sufficient free disk space on the client on which the Siebel Packager utility is installed. and the Siebel executable. Local databases are unique to individual users and must not be packaged. user. You may want to replace the siebel. Create a siebel.ini file located in the \siebel_client\packager\temp\package_name directory using a standard text editor. Include every file in this directory in your self-extracting installer. plus two times the disk space required by the third-party software you are packaging. the Siebel Packager utility temporarily requires three times the amount of disk space required by the Siebel client software you are packaging. Make your changes to the siebel.ses. except the user preferences file.

Component MSGTEMPL Objects
PUBLIC SQLTEMPL WEBTEMPL
For information about other types of files that can be packaged. located in the siebel_clnt_root\msgtempl directory. The utility displays progress information while it executes. Click OK at the Choose Setup Language screen. click Start. choose Packager from the Modules list and click Remove and then Click Next. You do not want to include Packager itself as a module. Contains Web templates. it would require an installation of BASE as well as each additional language pack. located in the siebel_clnt_root\webtempl directory. Leave the default values in the remaining fields.
a b c 4
Enter a Package Name. located in the siebel_clnt_root\public directory. Object Configuration Template Files (Configured Objects) located in the siebel_clnt_root\objects directory— the precompiled SRF file to distribute to end users. including BASE.S.Directory Definition dialog box appears. Contains SQL scripts used by the Siebel Web Client. For example.
5
In the Packaging window.
In the Module Definition dialog box.
Running the Siebel Packager Utility
The Siebel Packager wizard guides you through the windows to help you create the custom client installer. if NREC were planning a multilingual roll out.Deploying the Application ■ Rolling Out to End Users
Table 14. NREC is deploying a single-language version of their application. Step 1 of 4 . For example.
Software Installed in the Test Environment Description Message files used by the client.7 > Packager. choose Programs > Siebel Client 7. read Siebel Installation Guide for Microsoft Windows.
To create the BASE package 1 2
From the Windows Start menu.
3
Create the BASE package. The objects directory must contain at least one SRF file before you start the Siebel Packager utility. NREC Package. English).0
24 7
. Click Next. You need a separate installer for each language component. This requires two separate installers—one for BASE and one for ENU (U. Contains HTML.
Developing and Deploying Siebel Business Applications Version 8. JavaScript and image files for Siebel Web Client. The Siebel Client Packager. Both packages must use the same package name. located in the siebel_clnt_root\sqltempl directory.

Click Next. For instructions about other distribution methods.
4 5 6
Click Start to begin creating the package.
To create the language package 1 2
Go to start > Programs > Siebel Client 7. For more information about creating Base and Language Packages.S. and then click Next to continue. choose ENU for U. As described earlier. In the Self-extracting Archive dialog box.” A silent install is one that does not display any windows or dialog boxes to the user. make your customized installer available to end users. and click OK at the Choose Setup Language dialog box. read Siebel Installation Guide for Microsoft Windows.ini file can be edited by clicking on the Edit siebel. The Packaging dialog box appears. click Exit to finish. English). Send an email to users explaining how to copy and extract the package from this location. In the Self-extracting Archive dialog box.
To distribute a self-extracting installer over a LAN (if you created a self-extracting archive) 1 2
Put the self-extracting installer (packager_name. NREC Package). click OK and then Next. When the Siebel Packager utility is complete. click Exit to finish.ini file in the Siebel Packager utility. Because NREC chose to distribute the installer using network distribution.exe) in a network-accessible directory.Deploying the Application ■ Rolling Out to End Users
6 7
When the utility is complete. click on Remove to remove it.7 > Packager. you can distribute your customized installation program to end users in a number of ways.0
. Enter a Package Name (for example.
The Module Definition dialog box appears. click OK. In the Directory Definition screen:
a b c d
Choose <LANGUAGE> in the Language Packs list (for example. and about editing the siebel. Make sure that all users have access to this directory. read Siebel Installation Guide for Microsoft Windows.ini file need to be modified so that the installation on the end-user machines is “silent.
248
Developing and Deploying Siebel Business Applications Version 8. this section describes that distribution method.
NOTE: The parameters used in the siebel.
3
Choose Packager from the Modules list.
Making Your Customized Installer Available to End Users
After you have tested your customizations and are satisfied with the client installer you have created. Leave the default values in the remaining fields.ini file. The siebel. and then click Next. Consider telling users how to FTP the self-extracting archive to their machines and install it from there.

After or during this rollout. Send an email to users to tell them how to install the package from this location.
Developing and Deploying Siebel Business Applications Version 8.Deploying the Application ■ Rolling Out to End Users
To distribute an installer over a LAN (if you did not create a self-extracting archive) 1 2
Put the package directory in a network-accessible location to which all users have access.0
24 9
. you are ready to provide user training on the applications.

Deploying the Application ■ Rolling Out to End Users
250
Developing and Deploying Siebel Business Applications Version 8.0
.