powerexchange for siebel user guide documentation/1/pwx_… · siebel enterprise applications is an...

User Guide

Informatica® PowerExchange forSiebel(Version 8.5.1.0.0)

Informatica PowerExchange for Siebel User Guide Version 8.5.1.0.0 July 2008

Copyright (c) 2006–2008 Informatica Corporation. All rights reserved.

This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software is protected by U.S. Patent Numbers 6,208,990; 6,044,374; 6,014,670; 6,032,158; 5,794,246; 6,339,775, 6,850,947; 6,895,471, 7,254,590, and other U.S. Patents Pending.

Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.

The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing.

Informatica, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica Complex Data Exchange and Informatica On Demand Data Replicator are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners.

DISCLAIMER: Informatica Corporation provides this documentation “as is” without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice.

Part Number: PWX-SUG-85100-0001

Table of Contents

List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiInformatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Informatica Global Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Chapter 1: Understanding PowerExchange for Siebel . . . . . . . . . . . . . 1Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Understanding Siebel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Siebel Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Siebel Datatypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Siebel Object Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Application Object Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

PowerCenter Integration with Siebel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Understanding Siebel Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Siebel Business Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Siebel Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Siebel Business Service Transformations . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2: Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . 11Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Installing and Configuring PowerExchange for Siebel . . . . . . . . . . . . . . . 12

Before You Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Upgrading PowerExchange for Siebel . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Installing PowerExchange for Siebel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Installing the Client Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Installing the Repository Component . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Installing the Integration Service Component . . . . . . . . . . . . . . . . . . . . 15

iii

Registering the Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Configuring Java Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Copying Siebel API Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configuring Access to Siebel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Accessing Siebel Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Accessing Siebel Application Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Uninstalling PowerExchange for Siebel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Uninstalling from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Uninstalling from UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Cleaning Up the Siebel Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 3: Siebel Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Working with Siebel Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Generating Key Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Working with Calculated Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Filtering Siebel Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Importing a Siebel Source Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Steps to Import a Siebel Business Component . . . . . . . . . . . . . . . . . . . . 36

Updating Siebel Source Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Reimporting a Siebel Source Definition . . . . . . . . . . . . . . . . . . . . . . . . . 38

Editing a Siebel Source Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Chapter 4: Application Source Qualifier for Siebel Sources . . . . . . . 39Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

The Source Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

The Sort Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

View Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 5: Siebel Targets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Working with Siebel Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Generating Key Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Configuring the Update Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Importing a Siebel Target Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Steps to Import a Siebel Target Definition . . . . . . . . . . . . . . . . . . . . . . . 55

iv Table of Contents

Updating Siebel Target Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Reimporting a Siebel Target Definition . . . . . . . . . . . . . . . . . . . . . . . . . 58

Editing a Siebel Target Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58


Chapter 6: Siebel Business Service Transformation . . . . . . . . . . . . . 61Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Siebel Business Service Transformation Components . . . . . . . . . . . . . . . . . . 63

Metadata Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Siebel Business Service Transformation Groups and Ports . . . . . . . . . . . . . . . 64

Using a Siebel Business Service Transformation in a Mapping . . . . . . . . . . . . 65

Working with Integration Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Working with Hierarchy Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Working with Strings, Numbers, and Dates . . . . . . . . . . . . . . . . . . . . . . 68

Creating a Siebel Business Service Transformation . . . . . . . . . . . . . . . . . . . . 70

Chapter 7: Processing Siebel Calculated Expressions . . . . . . . . . . . 73Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Processing Siebel Business Component Expressions . . . . . . . . . . . . . . . . . . . 75

Processing Siebel Business Component Calculated Expressions . . . . . . . . 75

Processing Siebel Business Component Nested Calculated Expressions . . 76

Processing Siebel Business Component Lookup Expressions . . . . . . . . . . 76

Working with the Siebel Business Component Mapplet . . . . . . . . . . . . . . . . 77

Using an Input Transformation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Using an Expression Transformation . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Using a Lookup Transformation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Using an Output Transformation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Creating the Siebel Business Component Mapplet . . . . . . . . . . . . . . . . . . . . 82

Steps to Create a Siebel Business Component Mapplet . . . . . . . . . . . . . . 83

Chapter 8: Siebel Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Configuring Application Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Configuring Session for a Siebel Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Cache Directory and Cache Size for a Siebel Target . . . . . . . . . . . . . . . . 88


Table of Contents v

Appendix A: Siebel ODBC Sources . . . . . . . . . . . . . . . . . . . . . . . . . . 91Importing Siebel Sources Through ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Importing Siebel Business Components . . . . . . . . . . . . . . . . . . . . . . . . . 92

Importing Siebel Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Filtering Siebel Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Viewing Attribute Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Steps to Import Siebel Source Definitions . . . . . . . . . . . . . . . . . . . . . . . 94

Updating Column Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Application Source Qualifier for Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Understanding the Default Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Joining Source Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Custom Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Creating Key Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Creating and Configuring an Application Source Qualifier . . . . . . . . . . . . . . 99

Connecting Siebel Source Definitions in a Mapping . . . . . . . . . . . . . . . . 99

Configuring Sessions for Siebel Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Configuring Session for a Lookup Transformation . . . . . . . . . . . . . . . . 100

Partitioning Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Siebel Datatype Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Appendix B: Siebel Datatype Reference . . . . . . . . . . . . . . . . . . . . . 103Siebel and Transformation Datatypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Appendix C: Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Designer Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

SEBL Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

SiebelCT Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

SiebelRdr Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

SiebelWrt Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Appendix D: Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

vi Table of Contents

List of Figures

Figure 1-1. Siebel Object Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Figure 1-2. Designer Integration with Siebel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Figure 1-3. Integration Service and Siebel Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Figure 3-1. The Import from Siebel Wizard for a Source Definition . . . . . . . . . . . . . . . . . . . . 35

Figure 5-1. The Import from Siebel Wizard for a Target Definition . . . . . . . . . . . . . . . . . . . . 55

Figure 6-1. Siebel Business Service Transformation Groups . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Figure 7-1. Lookup Transformation in a Siebel Business Component Mapplet . . . . . . . . . . . . 81

List of Figures vii

viii List of Figures

List of Tables

Table 1-1. Source, Target, and Siebel Business Service Transformation . . . . . . . . . . . . . . . . . . . 4

Table 2-1. Java Properties for the Integration Service Process . . . . . . . . . . . . . . . . . . . . . . . . . 18

Table 3-1. Details Imported for a Business Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Table 5-1. Key Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Table 5-2. Update Strategy Field Valid Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Table 6-1. Input and Output Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Table 7-1. Lookup Transformations in the Siebel Business Component Mapplet . . . . . . . . . . . 80

Table 8-1. Session Level Properties for Targets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Table A-1. Siebel Details in a Business Component Source Definition. . . . . . . . . . . . . . . . . . . 92

Table A-2. Siebel System Fields and Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Table A-3. Siebel Details in a Table Source Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Table A-4. Siebel Field and Column Datatypes for Siebel Source Definitions . . . . . . . . . . . . . 101

Table A-5. Siebel and Transformation Datatypes for Siebel Sources. . . . . . . . . . . . . . . . . . . . 102

Table B-1. Siebel and Transformation Datatypes for Siebel Source and Target Definitions . . . 104

Table B-2. Siebel and Transformation Datatypes for Siebel Business Service Methods . . . . . . 105

List of Tables ix

x List of Tables

Preface

The Informatica PowerExchange for Siebel User Guide provides information about extracting data from a Siebel source and loading data into a Siebel target. The User Guide is written for database administrators and developers who are responsible for extracting data from Siebel and loading data to Siebel. This book assumes you have knowledge of Siebel and PowerCenter.

xi

Informatica Resources

Informatica Customer PortalAs an Informatica customer, you can access the Informatica Customer Portal site at http://my.informatica.com. The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica Knowledge Base, Informatica Documentation Center, and access to the Informatica user community.

Informatica Web SiteYou can access the Informatica corporate web site at http://www.informatica.com. The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services.

Informatica Knowledge BaseAs an Informatica customer, you can access the Informatica Knowledge Base at http://my.informatica.com. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips.

Informatica Global Customer SupportThere are many ways to access Informatica Global Customer Support. You can contact a Customer Support Center through telephone, email, or the WebSupport Service.

Use the following email addresses to contact Informatica Global Customer Support:

♦ [email protected] for technical inquiries

♦ [email protected] for general customer service requests

WebSupport requires a user name and password. You can request a user name and password at http://my.informatica.com.

xii Preface

http://www.informatica.com




Use the following telephone numbers to contact Informatica Global Customer Support:

North America / South America Europe / Middle East / Africa Asia / Australia

Informatica Corporation Headquarters100 Cardinal WayRedwood City, California 94063United States

Toll Free +1 877 463 2435

Standard RateBrazil: +55 11 3523 7761Mexico: +52 55 1168 9763United States: +1 650 385 5800

Informatica Software Ltd.6 Waltham ParkWaltham Road, White WalthamMaidenhead, BerkshireSL6 3TNUnited Kingdom

Toll Free 00 800 4632 4357

Standard RateBelgium: +32 15 281 702France: +33 1 41 38 92 26Germany: +49 1805 702 702Netherlands: +31 306 022 797United Kingdom: +44 1628 511 445

Informatica Business Solutions Pvt. Ltd.Diamond DistrictTower B, 3rd Floor150 Airport RoadBangalore 560 008India

Toll Free Australia: 1 800 151 830Singapore: 001 800 4632 4357

Standard RateIndia: +91 80 4112 5738

Preface xiii

xiv Preface

C h a p t e r 1

Understanding PowerExchange for Siebel

This chapter includes the following topics:

♦ Overview, 2

♦ Understanding Siebel, 3

♦ PowerCenter Integration with Siebel, 7

♦ Understanding Siebel Metadata, 9

1

OverviewPowerExchange for Siebel extracts data from Siebel using business components and tables as sources. It loads data directly into Siebel using business components as targets. PowerExchange for Siebel integrates with Siebel through the Siebel business services and Siebel business components.

The Integration Service uses ODBC or the Java Data Bean API to extract data from Siebel sources. The Integration Service uses the Java Data Bean API to load data into the Siebel business components or other targets. The Integration Service maintains data integrity while reading data and writing data to Siebel by maintaining relationships among Siebel business components.

Extract data from business components through ODBC or the Java Data Bean API. You can Extract data from tables through ODBC. Extract data from multi-group business components through the Java Data Bean API.

To extract data from Siebel calculated fields through ODBC, you need to create mapplets. You can use the Java Data Bean API to extract data from calculated fields directly.

You can invoke Siebel business services from the PowerCenter environment through the Java Data Bean API. A Siebel business service is a Siebel object used to implement reusable business logic. Siebel business services are executed within the application object manager.

2 Chapter 1: Understanding PowerExchange for Siebel

Understanding SiebelSiebel Enterprise Applications is an integrated suite of enterprise marketing, sales, customer service, and call center management applications. Siebel Enterprise Applications is based on client/server architecture. It can use any of the major relational databases for data storage on the server.

Siebel Enterprise Applications is based on the Siebel Object Model. The Siebel Object Model consists of object layers, which contain object definitions. Siebel business components exist in the Business Objects Layer, and Siebel tables exist in the Data Objects Layer. The Designer imports Siebel metadata from the Business Objects Layer and the Data Objects Layer to create source definitions.

A Siebel business component is a logical entity that combines columns from base tables, extension tables, and joined tables into a single structure. Siebel tables have columns and indexes that directly correspond to the columns and indexes of physical database tables in the underlying database.

Siebel Security When you extract data from a Siebel source through ODBC, you can extract data without compromising the existing Siebel security. The PowerCenter Client and the Integration Service require a database user name and password to read Siebel metadata tables and the application tables. Although you can use the table owner names as the database user name, you can keep Siebel metadata and the application data secure by creating database user names with read-only permission.

Siebel Enterprise Applications does not maintain user names and passwords. It passes the user name and password to the database for validation. The database user name is associated with permissions in Siebel Enterprise Applications. However, Siebel Enterprise Applications does not use a separate user name and password. You can use the Siebel Enterprise Applications user name and password if the user has the required permissions. For more information about accessing Siebel data and application data, see “Configuring Access to Siebel” on page 20.

Siebel DatatypesSiebel Enterprise Applications uses field and column datatypes to identify the type of data exchanged between Siebel and the underlying database. Siebel business components have field datatypes and Siebel tables have column datatypes. PowerExchange for Siebel uses Siebel datatypes when you import metadata from the Siebel system. Siebel datatypes correspond to the native datatypes of the underlying database.

Siebel Object ModelThe object definitions in Siebel Enterprise Applications exist in the following architectural layers in addition to the database system:

Understanding Siebel 3

♦ User Interface Objects Layer. Consists of user interface object definitions. The object definitions describe the interface with which the user interacts in the Siebel Enterprise Applications. When the Integration Service reads data from Siebel through ODBC, the Integration Service extracts the hierarchy of user interface objects, such as applications, screens, and views. When the Integration Service reads data from Siebel through the Java Data Bean API, the Integration Service extracts the hierarchy of user interface objects, such as business objects and business components. The Designer displays the hierarchy to select source definitions, but it does not store this information in the repository.

♦ Business Objects Layer. Consists of business object definitions that are built on data object definitions, such as business components, services, links, multi-value links, joins, and fields. When the Integration Service writes data to Siebel, it extracts business components and their properties from the Business Objects Layer.

♦ Data Objects Layer. Consists of data object definitions that correspond to the data structures in the underlying database, such as Siebel tables and columns. This layer is independent of the underlying DBMS. The Designer extracts metadata of Siebel tables and their properties from the Data Objects Layer.

Table 1-1 lists source, target, Siebel Business Service transformation, the corresponding objects in Siebel, and connectivity layers in the Siebel Object model:

For more information about the Siebel Object Model, see the Siebel documentation.

Table 1-1. Source, Target, and Siebel Business Service Transformation

Siebel Object Siebel Object Model Layer Connectivity

Source Siebel Business Component

Business Objects Layer

Java Data Bean API

Siebel Business Component


ODBC

Table Data Objects Layer ODBC

Target Siebel Business Component


Java Data Bean API

Siebel Business Service Transformation

Business Service Method


Java Data Bean API


Figure 1-1 shows the Siebel Object Model:

Application Object ManagerAn application object manager manages all the Siebel objects in a Siebel application. An application object manager can either be a user-defined component or a predefined component.

Figure 1-1. Siebel Object Model

Business Component**

Link**

Join**

Join Specification**Field**

Business Object*

Application*

Screen*

View*

Column***Table***

User Interface Objects Layer


Data Objects Layer

RDBMS

Multi value Link**

*PowerExchange for Siebel extracts this hierarchy from Siebel Enterprise Applications.**PowerExchange for Siebel extracts these object definitions when it extracts business component metadata.***PowerExchange for Siebel extracts these object definitions when it extracts Siebel metadata tables.****The Integration Service extracts application data from these tables and columns when you run a session.

Table**** Column****

Key:= Object Type= 1 to 1 relationship= 1 to many relationship

Understanding Siebel 5

The following table describes sample predefined components in a Siebel application:

You can use the Siebel srvrmgr utility or a Siebel application to view the application object manager for the current Siebel installation.

To use the Siebel srvrmgr utility to view application object manager:

1. Use the Siebel srvrmgr utility to connect to the Siebel gateway server.

2. Enter the following command at the prompt:

list comps

A list of active application object managers appears. Use one of the active application object managers to connect to Siebel.

To use a Siebel application to view application object manager:

1. Log in to the Siebel application.

2. Click Navigate > Site Map.

-or-

Click the Site Map button.

The Site Map displays all the screens alphabetically in columns. Each screen name is a hyperlink.

3. Click the Administration - Server Configuration hyperlink.

4. Click Servers > Components.

A list of application object managers appears. Use one of the application object managers to connect to Siebel.

Predefined Component Description

SMObjMgr_<lang> Marketing object manager, where <lang> specifies the language for which the language pack is installed on the Siebel server.

SSEObjMgr_<lang> Sales object manager, where <lang> specifies the language for which the language pack is installed on the Siebel server.

SCCObjMgr_<lang> Call Center object manager, where <lang> specifies the language for which the language pack is installed on the Siebel server.


PowerCenter Integration with SiebelImport Siebel metadata into PowerCenter as source definitions and use it in mappings. Run sessions to extract and load Siebel data and invoke Siebel business services. When you import a source or a target definition, the Designer connects to the Siebel application to import metadata.

Figure 1-2 shows Designer integration with Siebel:

The Integration Service connects to the Business Objects Layer through the Java Data Bean API. The Integration Service connects to the Data Objects Layer through ODBC.

The Integration Service connects to an application object manager to extract data from Siebel sources and load data into Siebel targets, or to invoke business services. An application object manager hosts the Business Objects Layer and the Data Objects Layer. The application object manager handles connection requests to the Siebel server.

Figure 1-2. Designer Integration with Siebel

Siebel Applications

Siebel Target Definition


PowerCenter Designer


Java Data Bean API

Siebel Source Definition

ODBC

Data Objects Layer

Java Data Bean API

PowerCenter Integration with Siebel 7

Figure 1-3 shows how the Integration Service integrates with Siebel to extract and load data:

Figure 1-3. Integration Service and Siebel Integration

Integration Service

Workflow

Siebel Session

Siebel Connection

The Integration Service reads and writes data based on session and application connection.

The Integration Service uses Java Data Bean API and ODBC to connect to Siebel Enterprise Applications.

Java Data Bean API ODBC

User Interface Objects Layer


Data Objects Layer


Understanding Siebel MetadataSource definitions represent metadata for business components and tables. Target definitions represent metadata for business components. You can import a Siebel business service method as a transformation.

In Siebel Enterprise Applications, business components correspond to Siebel tables and Siebel tables correspond to the physical database tables in the underlying database. You can import Siebel tables and business components as source definitions. You can import Siebel business components as target definitions.

Siebel Business ComponentsBusiness components on the Business Objects Layer correspond to the tables on the Data Objects Layer. When you import a Siebel business component as a source definition, the Designer imports the metadata from the business components on the Business Objects Layer and the associated Siebel tables on the Data Objects Layer.

When you import a Siebel business component as a source definition, the Designer imports the following business component properties:

♦ Field. Displays the name of the field. The Designer displays the following attributes and their values for each field:

− Calculated value expression. Displays the expression of a field if it is calculated.

− Physical table name. Displays the name of the underlying database table.

− Physical column name. Displays the name of the underlying database column name.

− Multi value link. Displays the name of the multi value link that the field refers to.

− Join name. Displays the alias for the join that the field refers to, if it is a join field.

♦ Base table name. Displays the name of the base table for the business component.

♦ Search specification. Displays the search criteria used by Siebel Enterprise Applications to retrieve a subset of records. You cannot edit this information.

♦ Sort specification. Displays the search criteria used by Siebel Enterprise Applications to sort the records retrieved in the specified order. You cannot edit this information.

When you run a session, the Integration Service extracts the application data from the physical database tables in the underlying database.

When you import a Siebel business component as a source or target definition through the Java Data Bean API, the Designer extracts the metadata from the business components on the Business Objects Layer. When you import a Siebel business component as a target definition, the Designer imports the following business component properties:

♦ Business component name. Displays the name of the business component.

♦ Business object name. Displays the business object name for the business component.

♦ Field. Displays the name of the field.

Understanding Siebel Metadata 9

When you run a session, the Integration Service reads and loads data into the business components on the Business Objects Layer.

Siebel TablesSiebel tables correspond to the physical database tables in the underlying database. When you import a Siebel table as a source, the Designer imports the metadata from the Siebel table on the Data Objects Layer. When you run a session, the Integration Service extracts the application data from the physical database tables in the underlying database.

When you import Siebel table source definitions, the Designer imports all types of Siebel tables except for the Dictionary, Repository, and Interface tables.

Siebel Business Service TransformationsYou can import a Siebel business service method as a transformation. Siebel business services exist in the Business Objects Layer. You can use a Siebel Business Service transformation to invoke Siebel business service methods that implement business logic within an application object manager.


C h a p t e r 2

Installation and Configuration


♦ Overview, 12

♦ Installing PowerExchange for Siebel, 14

♦ Registering the Plug-in, 17

♦ Configuring Java Properties, 18

♦ Copying Siebel API Libraries, 19

♦ Configuring Access to Siebel, 20

♦ Uninstalling PowerExchange for Siebel, 22

♦ Troubleshooting, 24

11

OverviewThis chapter provides information about upgrading, installing, and uninstalling PowerExchange for Siebel.

PrerequisitesBefore you install or upgrade PowerExchange for Siebel, complete the following tasks:

♦ Install or upgrade PowerCenter. For more information about the PowerCenter versions that PowerExchange for Siebel is compatible with, see the PowerExchange for Siebel Release Notes.

♦ Verify that you have read and write permissions on the following directories:

<PowerCenter Installation Directory>\server

<PowerCenter Installation Directory>\client

The installer must be able to add and overwrite files in these directories.

Installing and Configuring PowerExchange for SiebelTo install and configure PowerExchange for Siebel, complete the following steps:

1. Install the components. Install the Client, Repository, and Integration Service components to access Siebel. For more information, see “Installing PowerExchange for Siebel” on page 14.

2. Register the plug-in. Register the plug-in with the repository. For more information, see “Registering the Plug-in” on page 17.

3. Configure Java properties. Configure Java properties in the Administration Console for each Integration Service process that runs Siebel sessions. For more information, see “Configuring Java Properties” on page 18.

4. Copy Siebel API libraries. Copy the Siebel API libraries to the PowerCenter Client machine and PowerCenter Services machine. For more information, see “Copying Siebel API Libraries” on page 19.

5. Configure access to Siebel. This step is applicable only if you import Siebel sources through ODBC. To access Siebel data, configure access to Siebel metadata and application data. For more information, see “Configuring Access to Siebel” on page 20.

Note: After you install and configure PowerExchange for Siebel, create a User DSN through ODBC data source on the PowerCenter Client machine to import Siebel source definitions. Configure the User DSN to connect to the underlying database for the Siebel system. For example, if the Siebel system resides on an Oracle database, configure the data source to connect to the Oracle database.

After you install and configure PowerExchange for Siebel, you can create connections to access Siebel. Create connection objects in the Workflow Manager so that the Integration Service can connect to Siebel at run time.

12 Chapter 2: Installation and Configuration

Before You UpgradeBefore you upgrade PowerExchange for Siebel, uninstall the previous version. When you uninstall PowerExchange for Siebel, you do not need to unregister the plug-in.

Upgrading PowerExchange for SiebelWhen you upgrade PowerExchange for Siebel, complete the following tasks:

1. Install PowerExchange for Siebel. When you install PowerExchange for Siebel, you install the PowerExchange for Siebel Client and Services components. For more information, see “Installing PowerExchange for Siebel” on page 14.

2. Upgrade the plug-in registration. Register the PowerExchange for Siebel plug-in, to update the existing plug-in registration. For more information, see “Registering the Plug-in” on page 17.

3. Copy Siebel libraries. Copy the Siebel API libraries to the PowerCenter Client machine and PowerCenter Services machine. For more information, see “Copying Siebel API Libraries” on page 19.

4. Configure access to Siebel. This step is applicable only if you import Siebel sources through ODBC. For more information, see “Configuring Access to Siebel” on page 20.

Overview 13

Installing PowerExchange for Siebel

When you install PowerExchange for Siebel, you install components that allow PowerCenter to access Siebel. Install the following components:

♦ Client component. Allows you to import definitions, create mappings, and create connection objects using the PowerCenter Client.

♦ Repository component. Allows the Repository Service to store and access the Siebel metadata in the repository.

♦ Integration Service component. Allows the Integration Service to run Siebel sessions.

Install these components on the machines that you want to access Siebel.

Installing the Client ComponentInstall the Client component on each PowerCenter Client machine where you want to create or access Siebel metadata.

To install the Client component:

1. Run setup.exe from the installation package.

2. Choose the Client component.

3. Click Next.

4. Enter your name and organization name.

5. Select the directory where the PowerCenter Client executables are located.

By default, these are in the following location:

<PowerCenter Installation Directory>\client\bin

6. Click Next to begin the installation.

7. Click OK when the installation is complete.

Installing the Repository ComponentInstall the Repository Service component on each node configured to run a Repository Service process. If the Repository Service is configured to run on primary and backup nodes, install the Repository component on each node configured to run the Repository Service process.

Step 1. InstallStep 1. Upgrade


To install the Repository component on Windows:


2. Choose the Repository component.

3. Click Next.


5. Select the directory to store the plug-in.

By default, the plug-ins are stored in the following location:

<PowerCenter Installation Directory>\server\bin\Plugin



To install the Repository component on UNIX:

1. Copy the Repo.tar file to the machine.

2. Enter tar -xvf Repo.tar command at the prompt to untar the file.

3. Go to the Installer directory.

4. Enter ./install at the prompt.

5. Enter the absolute path to store the plug-in:

<PowerCenter Installation Directory>/server/bin/Plugin

The Repository component is installed.

Installing the Integration Service ComponentIf the Integration Service is configured to run on primary and backup nodes, install the Integration Service component on each node configured to run the Integration Service process.

If the Integration Service is configured to run on a grid, install the Integration Service component on each node configured to run on the grid. If you cannot install the Integration Service component on each node in the grid, create a resource in the domain and assign it to each node where you installed the Integration Service Component. When you create a session, configure the session to use the resource.

For example, create a custom resource called Siebel. When you create a session, you can require the session to use the resource Siebel. The Load Balancer will only dispatch the session to nodes where the Integration Service component is installed.

For more information about resources, see the PowerCenter Administrator Guide.

Installing PowerExchange for Siebel 15

To install the Integration Service component on Windows:


2. Choose the Server component.

3. Click Next.


5. Select the directory where the PowerCenter Services executables are located.

By default, these are in the following location:

<PowerCenter Installation Directory>\server\bin\



To install the Integration Service component on UNIX:

1. Copy the Server.tar file to the machine.

2. Enter tar -xvf Server.tar command at the prompt to untar the file.

3. Go to the Installer directory.


5. Enter the absolute path to the executables:

<PowerCenter Installation Directory/server/bin/

The Integration Service component is installed.


Registering the Plug-in

After you install PowerExchange for Siebel, register the plug-in with the repository. A plug-in is an XML file that defines the functionality of PowerExchange for Siebel. To register the plug-in, the repository must be running in exclusive mode. Use the Administration Console or the pmrep RegisterPlugin command to register the plug-in. The plug-in file for PowerExchange for Siebel is pmsiebel.xml. When you install the Repository component, the installer copies pmsiebel.xml to the following directory:


For more information about using the Administration Console to register a plug-in, see the PowerCenter Administrator Guide.

For more information about the pmrep RegisterPlugin command, see the PowerCenter Command Line Reference.

Note: If you do not have the correct privileges to register the plug-in, contact the user who manages the Repository Service.


Registering the Plug-in 17

Configuring Java Properties

Configure Java properties in the Administration Console for each Integration Service process that runs Siebel sessions.

Table 2-1 describes the Java properties you configure:

For more information about configuring the Integration Service, see the PowerCenter Administrator Guide.

Step 3. Install

Table 2-1. Java Properties for the Integration Service Process

Property Description

Java SDK Classpath You can set the CLASSPATH to any JAR files that you need to run a session that require java components. The Integration Service appends the values you set to the system CLASSPATH.

Java SDK Minimum Memory Minimum amount of memory the Java SDK uses during a session. If the session fails due to a lack of memory, you can increase this value.Default is 32 MB.

Java SDK Maximum Memory Maximum amount of memory the Java SDK uses during a session. If the session fails due to a lack of memory, you can increase this value. Default is 64 MB.


Copying Siebel API Libraries

Copy the Siebel API libraries from the machine where Siebel is installed to the PowerCenter Client machine, and to the machines where the Repository Service and Integration Service processes run.

To copy the Siebel API libraries:

1. Locate the Siebel.jar and SiebelJI_enu.jar files in the following directory:

<Siebel Installation Directory>\siebsrvr\CLASSES

2. Copy the files to the following directory on the PowerCenter Client machine:

<PowerCenter Installation Directory>\client\bin\javalib

3. Copy the files to the following directory on the PowerCenter Services machine:

<PowerCenter Installation Directory>\server\bin\javalib


Copying Siebel API Libraries 19

Configuring Access to Siebel

To import Siebel data through ODBC, configure access to Siebel metadata and Siebel application data. Create users to access metadata and application data. You can create a single user or separate users.

Accessing Siebel MetadataTo import Siebel metadata, create a database user and grant the user SELECT permission for the following Siebel metadata tables:

♦ S_APPLICATION

♦ S_APP_VER

♦ S_BOCOMP

♦ S_BUSCOMP

♦ S_BUSOBJ

♦ S_COLUMN

♦ S_EMPLOYEE

♦ S_EMP_POSTN

♦ S_FIELD

♦ S_JOIN

♦ S_JOIN_SPEC

♦ S_LINK

♦ S_MVLINK

♦ S_PER_RESP

♦ S_SCREEN

♦ S_SCREEN_VIEW

♦ S_SCR_MENU_ITEM

♦ S_TABLE

♦ S_VIEW

For more information about providing access to the Siebel metadata tables, see Informatica Knowledge Base article 21267.

Accessing Siebel Application DataTo import Siebel application data, create a database user and grant the user SELECT permission for the underlying tables containing application data. Use this database user name



https://my-prod.informatica.com/srm2/kb/documentLink.do?cmd=displayKC&docType=kc&externalId=21267

https://my-prod.informatica.com/srm2/kb/documentLink.do?cmd=displayKC&docType=kc&externalId=21267

when you configure the application connection to connect to a Siebel source in the Workflow Manager.

Configuring Access to Siebel 21

Uninstalling PowerExchange for SiebelTo uninstall PowerExchange for Siebel, uninstall it from each machine where you installed the Client, Repository, or Integration Service components.

Uninstalling from WindowsTo uninstall PowerExchange for Siebel from Windows, use the Windows Add/Remove Programs.

Uninstalling from UNIXYou can uninstall the PowerExchange for Siebel Repository and Integration Service components from UNIX.

To uninstall the Repository component from UNIX:


2. Enter the absolute path to the installation directory.

By default, the Repository component is installed in the following location:


3. When the installer prompts you to overwrite the existing installation or uninstall the Repository component, choose to uninstall the Repository component.

To uninstall the Integration Service component from UNIX:


2. Enter the absolute path to the installation directory.

By default, the Integration Service component is installed in the following location:

<PowerCenter Installation Directory>/server/bin/

3. When the installer prompts you to overwrite the existing installation or uninstall the Integration Service component, choose to uninstall the Integration Service component.

Cleaning Up the Siebel EnvironmentWhen you uninstall PowerExchange for Siebel, optionally remove the Siebel API libraries from the PowerCenter Client machine and PowerCenter Services machine to clean up the Siebel system.

To remove the Siebel API libraries from the PowerCenter Client machine:

Remove the Siebel.jar and SiebelJI_enu.jar files from the following directory:

<PowerCenter Installation Directory>\client\bin\javalib


To remove the Siebel API libraries from the PowerCenter Services machine:

Remove the Siebel.jar and SiebelJI_enu.jar files from the following directory:


Uninstalling PowerExchange for Siebel 23

TroubleshootingImporting PowerCenter 8.1.1 Siebel mappings into PowerCenter 8.5.1 without upgrading the PowerCenter 8.1.1 repository leads to the following error:Invalid Database Type: PowerCenterConnectforSiebel for target: <target name>, or the Database Type is not installed in this repository.

-or-

Invalid Database Type: PowerCenterConnectforSiebel for source: <source name>, or the Database Type is not installed in this repository.

Upgrade the PowerCenter 8.1.1 repository.


C h a p t e r 3

Siebel Sources


♦ Overview, 26

♦ Working with Siebel Sources, 27

♦ Generating Key Values, 30

♦ Working with Calculated Fields, 33

♦ Filtering Siebel Sources, 34

♦ Importing a Siebel Source Definition, 35

♦ Updating Siebel Source Definitions, 38

25

OverviewSiebel source definitions represent Siebel metadata. You can import Siebel source definitions through the Java Data Bean API. When you import a Siebel source definition through the Java Data Bean API, the Designer extracts the metadata from the business components on the Business Objects Layer.

Use the Import from Siebel Wizard to import Siebel business components. When you import a Siebel source definition, the Designer displays business objects for the active application object manager. You can select a business object and then a business component to import from the list of business components.

Note: You can also import Siebel source definitions through ODBC. For more information, see “Importing Siebel Sources Through ODBC” on page 92.

26 Chapter 3: Siebel Sources

Working with Siebel SourcesA Siebel business component can contain single-value and multi-value fields. A single-value field can store one value at a time and a multi-value field can store more than one value at a time. A multi-value field has an associated multi-value link attribute that corresponds to the destination business component for this field.

A multi-value source contains groups for single-value and multi-value fields. All the single-value fields are part of a single group. The multi-value fields with the same multi-value link are part of the same group. The group containing the single-value fields is the parent group for all the groups in that source. The other groups are child groups of the parent group.

Consider the Account business component with the following fields and groups:

An account name can be associated with multiple addresses. Therefore, each Account row can have multiple rows with Street Address and City columns. Multiple rows are stored as data of the CUT Address business component. An account name can be associated with multiple positions. Therefore, each Account row can have multiple rows with Position and Position ID columns. Multiple rows are stored as data of the Position business component.

Fields Field Name Multi-value Link Group Destination Business

Component

Single-value Account n/a Account n/a

Account Number

n/a Account n/a

Multi-value Street Address

Business Address

Business_Address

CUT Address

City Business Address

Business_Address

CUT Address

Position Position Position Position

Position ID Position Position Position

Working with Siebel Sources 27

The following figure shows the Account business component containing Position with a multi-value link attribute Position:

The Account source definition contains a group for Name and Account Number, a group for Position and Position ID, and the other group for City and Street Address.

Multi-value Link, Position


The following figure shows the Account source definition with the parent group Account, and the child groups, Business_Address and Position:

Business_Address Child Group

Position Child Group

Account Parent Group

Working with Siebel Sources 29

Generating Key ValuesWhen you import a multi-group Siebel source definition, the Designer creates a key relationship between each group in the source definition and its parent group. For more information about key relationships, see “Generating Key Values” on page 51.

Note: When you create mappings with the primary key-foreign key relationship, the Designer might not create the relationship for the tables. You need to manually set the primary key relationship in the foreign key table.

The following table lists the primary and foreign keys created for the groups in the Account source definition:

For a multi-group source, the Integration Service uses row ID as the group primary key of each group. The values for the group foreign keys are taken from the list of values for the group primary keys in the parent group.

The following table shows sample rows contained in the Account group:

The following table shows sample rows contained in the Business_Address child group:

Group Primary Key Foreign Key

Account GPK__Account n/a

Business_Address GPK__Business_Address GFK__Account__Business_Address

Position GPK__Position GFK__Account__Position

GPK__Account Name Account_Number

1 James Brown 101

2 John Martin 102

GPK__Business_Address

GFK__Account__Business_Address City Street Address

A 1 Los Angeles

63 Ranch Ave

B 1 Frankfort 3090 Stevens Creek Blvd

C 2 Dallas 181 Curtner Ave

D 2 San Diego

760 Camino Real


The following table shows sample rows contained in the Position child group:

In this example, each source represents a group in the source definition. To maintain key relationships when you connect mapping objects, connect source columns in the groups to the corresponding group in the flat file target definitions.

The following table lists column relationships between groups in the Account source definition and flat file target definitions:

GPK__Position GFK__Account__Position Position Position ID

E 1 Account Manager A1

F 1 Business Analyst B1

G 2 Consultant C1

H 2 Financial Adviser C2

Source Group Name Source Column Name Target Name Target Column

Name

Account GPK__Account Account_rdr1 GPK

Account Name Account_rdr1 Name

Account Account_Number Account_rdr1 Account_Number

Position GPK__Position Position_Account_rdr GPK

Position GFK__Account__Position Position_Account_rdr GFK

Position Position Position_Account_rdr Position

Position Position_ID Position_Account_rdr Position_ID

Business_Address GPK__Business_Address Business_Add_Account_rdr GPK

Business_Address GFK__Account__Business_Address Business_Add_Account_rdr GFK

Business_Address City Business_Add_Account_rdr City

Business_Address Street_Address Business_Add_Account_rdr Street_Address

Generating Key Values 31

The following mapping shows a Siebel source definition, an Application Source Qualifier, and flat file target definitions:

The Integration Service extracts the following rows from the Account source definition:

[Account (1, “James Brown”, “101”, Address (A, 1, Los Angeles, 63 Ranch Ave), Address (B, 1, Frankfort, 3090 Stevens Creek Blvd), Position (E, 1, Account Manager, A1), Position (F, 1, Business Analyst, B1)]

[Account (2, “John Martin”, “102”, Address (C, 2, Dallas, 181 Curtner Ave), Address (D, 2, San Diego, 760 Camino Real), Position (G, 2, Consultant, C1), Position (H, 2, Finance Adviser, C2)]

The following table lists the rows that the Integration Service inserts into flat file targets:

Flat File Target Name Inserted Rows

Account_rdr1 [1, James Brown, 101][2, John Martin, 102]

Position_Account_rdr [E, 1, Account Manager, A1][F, 1, Business Analyst, B1][G, 2, Consultant, C1][H, 2, Finance Adviser, C2]

Business_Add_account_rdr [A, 1, Los Angeles, 63 Ranch Ave][B, 1, Frankfort, 3090 Stevens Creek Blvd][C, 2, Dallas, 181 Curtner Ave][D, 2, San Diego, 760 Camino Real]


Working with Calculated FieldsUse PowerExchange for Siebel to extract data from calculated fields. A calculated field is a Siebel field that derives its value from other fields. You can calculate the value of the calculated fields by applying a formula. For example, in the Quote business component, the calculated field, Account Bill To City State ENU, is used across multiple business components. To calculate the value of the calculated field, the following formula is used:

IIf ([Account Bill To City] IS NULL, [Account Bill To State], IIf ([Account Bill To State] IS NULL, [Account Bill To City], [Account Bill To City] + “,” + [Account Bill To State]))

When the Integration Service reads data from the Account Bill To City State ENU field, the Integration Service calculates the value of the calculated field before it passes the data to other transformations.

Working with Calculated Fields 33

Filtering Siebel SourcesWhen you import Siebel source definitions, you can view business objects and business components that match the condition.

You can filter business objects and business components by name. Use the following guidelines when you enter a filter condition:

♦ Use AND or OR operators to enter more than one filter criterion.

♦ Use a question mark (?) as wildcard character for a single character and an asterisk (*) as wildcard character for multiple characters.

♦ If the filter condition contains special characters, enclose the filter condition in single quotes. Special characters include =, >, <, (, ), ,, ~, “, ‘, and [.

♦ If the filter condition contains a single double quote or single quote, the quote must be doubled. For example, to search for a business component, FINS AG Agent's Designation or FINS AG Agent’s Name, enter the following filter condition:

‘FINS*’’*’

♦ Enter date values in the mm/dd/yyyy format.

If you apply a filter on business components without selecting a business object, the wizard shows the business objects containing the business components that match the filter criterion. If you apply a filter on business components after selecting a business object, the wizard shows the business components that match the filter criterion in that business object.

After retrieving the names of business objects, select the business object for which you want to view the business components. To filter business components, select Business Component from the Based On list, enter the filter criteria in the Value, and click Load Objects.

To change the filter condition, enter the modified condition, and click Load Objects.


Importing a Siebel Source DefinitionWhen you connect to Siebel, the wizard lists a hierarchy of business objects and business components.

Figure 3-1 shows the business objects and business components listed in the wizard page:

Table 3-1 describes the details imported by the Designer when you import a business component as a source definition:

Figure 3-1. The Import from Siebel Wizard for a Source Definition

Table 3-1. Details Imported for a Business Component

Source Definition Field Description

Source Table Business component name.

Column Name The Designer displays the following attributes for each field:- Field Name- Datatype- Length/Precision- Scale- Description - Calculated- Multi-value- Multi-value link- Comments

Business Object

Business Component

Importing a Siebel Source Definition 35

Steps to Import a Siebel Business ComponentUse the following procedure to import business components through the Java Data Bean API.

To import a Siebel source definition through the Java Data Bean API:

1. In the Source Analyzer, click Sources > Import Siebel Business Components.

The wizard appears.

2. Enter the following parameters:

3. Click Connect to connect to Siebel.

4. If the connection is successful, click Next.

5. Click Load Objects if you want to load all the business objects for the active application object manager.

6. Optionally, enter a filter condition to view business objects and business components that meet the condition. For more information about filtering Siebel sources, see “Filtering Siebel Sources” on page 34.

7. Select a business object and drill down through the selected business object to select the business component you want to import. After you select a business component, the details area displays information about the business component.

Note: You can also import custom business components.

8. Click Next.

Connection Parameter Description

Protocol Protocol used to connect to Siebel. The format for the protocol is siebel[[.transport][.[encryption][.[compression]]]]. The parameters in the protocol format are:- transport. Enter http or TCPIP. Default is TCPIP.- encryption. Enter NONE or RSA. Default is NONE.- compression. Enter NONE or zlib. Default is zlib.

Siebel Server Host Siebel server host name.

SCBroker Port Siebel Connection Broker port number.

Enterprise Server Siebel Enterprise Server name.

Application Object Manager Siebel application business object manager. For more information, see “Application Object Manager” on page 5.

User Name Siebel user name to connect to Siebel.

Password Password for user.

Encoding Encoding used for communication between the Designer and the Siebel server. By default, the Designer uses the UTF-8 encoding.

Note: For more information about the connection parameters, contact your Siebel system administrator.


9. Enter a name for the source in the Source Name field if you want to change the name of the source.

10. Click Import.

The wizard shows the fields and number of groups that the Designer created, and the number of groups and fields that the Designer failed to create.

Note: The Designer replaces special characters in the group and field names with an underscore (_). Special characters include space, ., ,, /, “, +, =, ~, `, !, %, ^, (, ), [, ], {, }, :, ;, ?, <, >, &, @, *, and |.

11. Click Import Another Source to import another source.

12. Repeat steps 5 to 10 to import another source definition.

13. Click Finish.

Importing a Siebel Source Definition 37

Updating Siebel Source DefinitionsManually edit the definition to configure the properties that you cannot import or to make minor changes to the definition.

You can update a Siebel source definition to change the name, datatype, precision, keytype, and business name for a column.

Note: If the changes are significant, you can reimport the definition. This overwrites or renames the existing source definition.

Reimporting a Siebel Source DefinitionComplete the steps to reimport a Siebel definition. You can retain the following information in the definition being replaced:

♦ Primary key-foreign key relationships

♦ Source definition description

♦ Column or port description

For more information about reimporting a source definition, see “Steps to Import a Siebel Business Component” on page 36.

Editing a Siebel Source DefinitionOn the Columns tab, edit the precision and key type for fields in the source definition.


C h a p t e r 4

Application Source Qualifier for Siebel Sources


♦ Overview, 40

♦ The Source Filter, 41

♦ The Sort Filter, 43

♦ View Mode, 44

39

OverviewIn the Application Source Qualifier for the sources that are imported through the Java Data Bean API, you can perform the following tasks:

♦ Filter data. Use the source filter to retrieve the rows from a business component that satisfy a criterion.

♦ Sort data. Use the sort filter to sort data and to ensure that the Integration Service reads source data in a specific order from a business component.

♦ View data through view mode. View mode defines the visibility type for a business component.

Note: For information about the Application Source Qualifier for the sources imported through ODBC, see “Application Source Qualifier for Sources” on page 97.

40 Chapter 4: Application Source Qualifier for Siebel Sources

The Source FilterUse the source filter to retrieve rows from a business component that satisfy a condition. Use the following guidelines when you enter a filter condition:

♦ Use AND or OR operators to enter more than one filter criterion.

♦ Use a question mark (?) as wildcard character for a single character and an asterisk (*) as wildcard character for multiple characters.

♦ If the filter condition contains special characters, enclose the filter condition in single quotes. Special characters include =, >, <, (, ), ,, ~, “, ‘, and [.

♦ If the filter condition contains a single double quote or single quote, the quote must be doubled.

♦ Enter date values in the mm/dd/yyyy format.

You can also enter a filter condition that retrieves data from a parent group and a child group. For example, you can retrieve the accounts for which status is Active from the Account business component. You can also retrieve addresses of the Active accounts which have Country as U.S. from the Business_Address group. The Business_Address group is the child group of the Account group.

To compare a single-value field with multiple values, specify these values in a mapping parameter file. The mapping parameter file contains a mapping parameter. For example, to retrieve data from the Business_Address group about the persons who stay either in U.S., U.K., or India, declare the mapping variable in the Mapping Designer. Enter the name of the mapping variable preceded by $$ in the filter condition. For more information about mapping parameters and mapping variables, see the PowerCenter Designer Guide.

Note: Use the syntax provided by the Java Data Bean API to enter a filter condition.

To enter a filter condition:

1. In the Mapping Designer, double-click the Application Source Qualifier.

2. Click the Siebel Properties tab.

3. Click the Browse button by the Source Filter field.

The Source Filter 41

The Search Builder dialog box appears.

4. Select the group to be filtered.

5. Select a field from the Field list.

Multi-value field names in the Field list are the same as in the destination business component. To view the corresponding field names in the source definition, double-click the source definition in the Source Analyzer, and click the Attributes tab. The Value column shows the field names as present in source definition.

6. Select the operator from the Operator list.

7. Enter the value for the selected field in Value.

Enter date values in the mm/dd/yyyy format.

8. Optionally, enter the mapping variable name in the Value field to compare the selected field with multiple values. The values are stored in the mapping parameter file.

Provide the name and path for the mapping parameter file at the session level.

9. Click Add to Filter to add the filter condition to the filter expression.

10. For multiple filter conditions, follow steps 4 to 7, and click AND into Filter or OR into Filter.

To add parentheses to a complex filter expression, click the Add buttons.

11. Click OK.

The filter condition appears in the Application Source Qualifier.


The Sort FilterUse the sort filter to retrieve data from a business component in a specific order. You can specify the sort condition for each group in a multi-group source. For example, you can retrieve data from the Business_Address group sorted by the City field. City is a multi-value field in the Account business component. Therefore, a row in the Account business component can have corresponding multiple rows in the CUT Address business component. The sort filter sorts the cities for a row in the Account business component and then across the rows in CUT Address.

To enter a sort condition:

1. In the Mapping Designer, double-click the Application Source Qualifier.

2. Click the Siebel Properties tab.

3. Click the Browse button by the Sort Filter field.

The Sort Builder dialog box appears.

4. Select the group to be sorted.

The Field list displays all the fields that correspond to the multi-value fields in the multi-value source for the selected group.

5. Select a field by which you want to sort the data.

Multi-value field names in the Field list are the same as in the destination business component. To view the corresponding field names in the source definition, double-click the source definition in the Source Analyzer, and click the Attributes tab. The Value column shows the field names as present in source definition.

6. Select the sorting order from the Type list.

7. Click Add to Filter to add the sort condition to the sort expression.

8. Click OK. The sort condition appears in the Sort Filter in the Application Source Qualifier.

The Sort Filter 43

View ModeView mode determines the number of rows extracted by the Integration Service from a business component. You can specify the following values for view mode:

♦ SalesRep. Displays rows according to the following access control mechanisms used by a business component:

− Single position. You can associate a single position with individual data. The Integration Service extracts the rows that are owned by the user position.

− Sales team. You can associate multiple positions, in the form of a team, with data. The Integration Service extracts the rows that are owned by the users whose sales team contains the user position.

To view the rows for this view mode, the business component must have a view mode with an owner type of Position.

♦ Manager. Displays rows for a user and the rows which can be accessed by the users who report to the user. The rows displayed depend on the access control mechanism. For the single position access control, the Integration Service extracts the rows associated directly with the active position of the user and the rows associated with subordinate positions.

For the sales team access control, the Integration Service extracts the row for which the active position of the user is the primary position on the team or a subordinate position is the primary member on the team.

The Integration service does not display any data if a user position has no subordinate positions. To view the rows for this view mode, the business component must have a view mode with an owner type of Position. This view mode is used by managers.

♦ Personal. Displays the rows to which you have direct access. To view the rows, the business component must have a view mode with an owner type of Person. For example, you can view the rows for which you have permissions. This is the default view mode.

♦ All. Displays the rows for an organization that have a valid owner. For example, an administrator can view all the accounts in the Account business component.

♦ Organization. Displays rows for the organization to which a valid owner has been assigned and the position of the user is associated with the organization. This view mode is applicable to the single organization or multiple organization access control. For example, an executive can view the accounts of all the organizations in the Account business component.

♦ Group. Displays rows either in the current category or in the first level child categories of a category to which the user has access. The Integration Service extracts the rows in the first level category if the user accesses the catalog.

♦ Category. Displays a flat list of rows in categories across every catalog that a user can access.

♦ SubOrganization. Displays rows depending on the type of access control. For the single organization access control, the Integration Service extracts the rows associated directly with the active position of the user or the descendant organization of the user. For the multiple organization access control, the Integration Service extracts the rows for which


the active organization of the user or a descendant organization is the primary organization.

When a Siebel user selects a view mode and the rows are not available for the selected view mode, the Integration Service writes a message to the session log for the view mode.

The following table lists the hierarchy in a sample organization:

In this hierarchy, Emma, Alan, and Shane are Siebel users in the organization. Alan reports to Emma, and Shane reports to Alan. Every Siebel user has created two rows for the Service Request business component.

When a Siebel user uses the Personal view mode to read data from the Service Request business component, two rows are extracted that are created by the Siebel user.

When a Siebel user uses the Manager view mode for reading data, the data for the Siebel user and subordinates is extracted. For example, if Emma uses the Manager view mode, the rows created by Emma, Alan, and Shane are extracted. If Alan uses the Manager view mode, the rows created by Alan and Shane are extracted.

When a Siebel user uses the Organization view mode, the rows created by the Siebel user and the other Siebel users in the organization are extracted because all Siebel users belong to the same organization. For example, if Shane uses the Organization view mode, the rows created by Shane, Alan, and Emma are extracted.

User Name Designation Manager SubordinatesRows created for the Service Request Business Component

Emma VP - Service None Alan, Shane 2

Alan Service Manager Emma Shane 2

Shane Service Representative Alan None 2

View Mode 45

C h a p t e r 5

Siebel Targets


♦ Overview, 48

♦ Working with Siebel Targets, 49

♦ Generating Key Values, 51

♦ Configuring the Update Strategy, 52

♦ Importing a Siebel Target Definition, 55

♦ Updating Siebel Target Definitions, 58


47

OverviewSiebel target definitions represent the metadata for a Siebel business component. Use the Import from Siebel Wizard to import the Siebel target definitions. When you connect to Siebel, the wizard lists Siebel business objects. You can expand a business object to list the business components it contains.

When you select a business component to import, the details area of the wizard displays information such as the field names, datatypes, precision, and scale. The details area does not display the details for business objects.

When you import a business component that contains multi-value links corresponding to the fields from other business components, the Designer imports all the fields as one target definition.

48 Chapter 5: Siebel Targets

Working with Siebel TargetsA Siebel business component can contain single-value and multi-value fields. A single-value field can store one value at a time and a multi-value field can store more than one value at a time. A multi-value field has an associated multi-value link attribute that corresponds to the destination Siebel business component for this field.

A multi-value target contains groups for single-value and multi-value fields. All the single-value fields are part of a single group. The multi-value fields with the same multi-value link are part of the same group. The group containing the single-value fields is the parent group for all the groups in that target. The other groups are child groups of the parent group.

Consider the Account business component with the following fields and groups:

Each Account row can have multiple rows with Street Address and City columns. A name can be associated with multiple addresses. Multiple rows are stored as data of the CUT Address business component.

Fields Name Multi-Value Link Group Destination Business

Component

Single-Value Name n/a Account n/a

ID n/a Account n/a

Multi-Value Street Address

Business Address

Business_Address

CUT Address

City Business Address

Business_Address

CUT Address

Working with Siebel Targets 49

The following figure shows the Account business component containing City with a multi-value link attribute, Business Address:

Account contains a group for Name and ID and the other group for City and Street Address.

Multi-value Link Attribute


Generating Key ValuesWhen you import a Siebel target definition, the Designer creates a key relationship between each group in the target definition and its parent group. Each key uses the following naming convention:

GPK__<group_name>

GFK__<parentgroup_name>__<group_name>

Table 5-1 describes the key naming conventions:

For the Account business component, the Designer generates primary keys, GPK__Account and GPK__Business_Address. It generates the GFK__Account__Business_Address foreign key for the child group.

Provide the values for the GPK and GFK fields in the source that define the relationship between the parent group and child group rows. Choose values for the GFK field from the GPK field in the parent group.

Note: When you create mappings with the primary key-foreign key relationship, the Designer might not create the relationship for the tables. You need to manually set the primary key relationship in the foreign key table.

Table 5-1. Key Naming Conventions

Key Name Component Description

GPK|GFK Type of key. The key name begins with GPK when it is a primary key. The key name begins with GFK when it is a foreign key.

group_name Name of the group to which the key belongs.

parentgroup_name Name of the parent group with which you have established primary key relationship.

Generating Key Values 51

Configuring the Update StrategyEach group in the target business component contains a field that determines the update strategy for the group. Configure this field in the mapping to specify the operation that you need to perform on the rows. You can perform INSERT, UPDATE, and DELETE operations on rows. The default operation is INSERT.

Table 5-2 lists the valid values for the update strategy field:

If you specify an invalid value for this field, the Integration Service treats it as INSERT.

Note: The Integration Service ignores the value of the Treat Source Rows As property at the session level.

The naming convention for the update strategy field is Update_Strategy_<group_name>. The Account group contains the Update_Strategy_Account field and the Business_Address group contains the Update_Strategy_Business_Address field.

The following table shows the rows contained in the source definition Account_Src:

The following table shows the rows contained in the source definition Business_Add_Src:

Table 5-2. Update Strategy Field Valid Values

Operation Value

INSERT 0

UPDATE AS UPDATE 1

DELETE 2

UPDATE ELSE INSERT 3

GPK__AccountUpdate_Strategy_Account

Name ID

1 0 James Brown 101

2 0 John Martin 102


GFK__Account_Business_Address

Update_Strategy_Business_Address

City Street Address

A 1 0 Los Angeles 63 Ranch Ave

B 1 0 Frankfort 3090 Stevens Creek Blvd


In this example, each source represents a group in the target definition. To maintain key relationships when you connect mapping objects, connect source columns to the corresponding group in the target definition.

The following table lists the column relationships between the source definitions and the groups in the Account target definition:

The following figure shows the Account business component with a multi-valued field:

C 2 0 Dallas 181 Curtner Ave

D 2 0 San Diego 760 Camino Real

Source Name Source Column Name Account Target Group Name Target Column Name

Account_Src GPK__Account Account GPK__Account

Account_Src Name Account Name

Account_Src ID Account ID

Business_Addr_Src GPK__Business_Address Business_Address GPK__Business_Address

Business_Addr_Src GFK__Account__Business_ Address

Business_Address GFK__Account__Business_Address

Business_Addr_Src City Business_Address City

Business_Addr_Src Street_Address Business_Address Street_Address


GFK__Account_Business_Address

Update_Strategy_Business_Address

City Street Address

Configuring the Update Strategy 53

The Integration Service inserts the following rows into the target business component:

[Account (“James Brown”, “101”, Address (Los Angeles, 63 Ranch Ave), Address (Frankfort, 3090 Stevens Creek Blvd)]

[Account (“John Martin”, “102”, Address (Dallas, 181 Curtner Ave), Address (San Diego, 760 Camino Real)]


Importing a Siebel Target DefinitionWhen you connect to Siebel, the wizard lists a hierarchy of business objects and business components.

Figure 5-1 shows a sample page from the wizard:

Steps to Import a Siebel Target DefinitionUse the following procedure to import Siebel target definitions.

To import Siebel target definitions:

1. In the Target Designer, click Target > Import from Siebel.

The wizard appears.

Figure 5-1. The Import from Siebel Wizard for a Target Definition

Details Area

SiebelBusiness ObjectSiebelBusiness Component

Importing a Siebel Target Definition 55

2. Enter the following information:

3. Click Connect to connect to Siebel.

4. If the connection is successful, click Next.

5. Click Load Objects if you want to load all the business objects for the active application object manager.

6. Optionally, enter a filter to view business objects and business components that meet the condition. For more information about filtering Siebel sources, see “Filtering Siebel Sources” on page 34.

7. Select a business object and drill down to select the business component you want to import. After you select a business component, the details area displays the information about the business component.

Note: You can also import custom business components. When you import a Siebel business component as a target definition, the Designer imports all the fields except the calculated and read-only fields.

8. Click Next.

9. Enter a name for the source in the Target Name field if you want to change the name of the target.

10. Click Import.

The wizard shows the fields and number of groups that the Designer created, and the number of groups and fields that the Designer failed to create.






Application Object Manager Siebel Application Business Object Manager. For more information about the Siebel Application Object Manager, see “Application Object Manager” on page 5.

User Name Siebel user name to connect to Siebel.


Encoding Encoding used for communication between the Designer and the Siebel Server. By default, the Designer uses the UTF-8 encoding.

Note: For more information about the connection parameters, contact your Siebel system administrator.


Note: The Designer replaces special characters in the group and field names with an underscore (_). Special characters include space, ., ,, /, “, +, =, ~, `, !, %, ^, (, ), [, ], {, }, :, ;, ?, <, >, &, @, *, and |.

11. Click Import Another Target to import another target.

12. Repeat steps 5 to 10 to import another target definition.

13. Click Finish.

Importing a Siebel Target Definition 57

Updating Siebel Target DefinitionsManually edit the definition to configure properties that you cannot import or to make minor changes to the definition.

You can update a Siebel target definition to configure column attributes such as precision and keytype.

Note: If the changes are significant, you can reimport the definition. This overwrites or renames the existing target definition. You can retain existing primary key-foreign key relationships and descriptions in the target definition being replaced.

Reimporting a Siebel Target DefinitionComplete the steps to reimport a Siebel target definition. You can retain the following information in the definition being replaced:

♦ Primary key-foreign key relationships

♦ Target definition description

♦ Column or port description

For more information about reimporting a target definition, see “Steps to Import a Siebel Target Definition” on page 55.

Editing a Siebel Target DefinitionOn the Columns tab, edit the precision and key type for fields in the business component. When you set the key type of columns as PRIMARY KEY, the Integration Service uses these columns to search the rows in the Siebel business components. You cannot modify the datatype of a column.


TroubleshootingThe Import from Siebel option is not enabled in the Designer.Verify that the Siebel license is assigned to the Repository Service.

Troubleshooting 59

C h a p t e r 6



♦ Overview, 62

♦ Siebel Business Service Transformation Components, 63

♦ Siebel Business Service Transformation Groups and Ports, 64

♦ Using a Siebel Business Service Transformation in a Mapping, 65

♦ Creating a Siebel Business Service Transformation, 70

61

Overview

A Siebel Business Service transformation is a passive transformation that you can use to invoke business service methods. Use Siebel business services to move data and convert data formats between Siebel and external applications. For example, the Authentication business service is a Siebel business service that takes credentials of users as the input and generates the user name and role of the user as output.

Business service methods transfer data between Siebel and external applications. You can use a Siebel Business Service transformation to perform complex calculations or specialized functions.

When you run a session with a Siebel Business Service transformation, the Integration Service connects to a Siebel server and invokes the business service method.

Use the Import from Siebel Wizard to create a Siebel Business Service transformation. When you connect to Siebel, the wizard displays the metadata for the business services. In the wizard, select a Siebel business service method to generate Siebel Business Service transformation. In addition to the primitive datatypes such as Number, Date, and String, business methods also take integration objects and hierarchy objects as arguments.

The following figure shows the business service methods, business services, and details about the business service method in the details area:

Transformation type:PassiveConnected

Business Service Method

Siebel Business Service

Details Area

62 Chapter 6: Siebel Business Service Transformation

Siebel Business Service Transformation ComponentsA Siebel Business Service transformation contains the following tabs:

♦ Transformation. Enter a name and description for the Siebel Business Service transformation.

♦ Ports. View and edit port information on the Ports tab. For more information about ports, see “Siebel Business Service Transformation Groups and Ports” on page 64.

♦ Properties. View the properties on the Properties tab. Configure the tracing level property for the Siebel Business Service transformation.

♦ Metadata Extensions. The Designer provides vendor-defined metadata extensions that extend metadata stored in the repository. You cannot create user-defined metadata extensions. For more information about Siebel Business Service metadata extensions, see “Metadata Extensions” on page 63.

♦ Initialization Properties. The Siebel Business Service transformation does not use initialization properties. The Integration Service retrieves initialization information from a vendor-defined metadata extension.

♦ Port Attribute Definitions. The Siebel Business Service transformation does not use port attributes.

Metadata ExtensionsA Siebel Business Service transformation provides the following vendor-defined metadata extensions:

♦ BusinessServiceMethodName. Refers to the name of the business service method represented by the transformation.

♦ BusinessServiceName. Refers to the name of the business service to which the business service method belongs.

The Designer sets the values of metadata extensions. You cannot edit these values.

Siebel Business Service Transformation Components 63

Siebel Business Service Transformation Groups and Ports

A Siebel Business Service transformation has input and output groups. The naming convention for the input group is <Business Service name>_In. The naming convention for the output group is <Business Service name>_Out. Siebel Business Service transformation can have multiple input and output ports. The input arguments of a business service method correspond to the input ports, and the output arguments correspond to the output ports.

Figure 6-1 shows the input and output groups for a Siebel Business Service transformation:

Note: If a business service method does not have any input or output port, a dummy port is added to the input or output group.

Figure 6-1. Siebel Business Service Transformation Groups

Output Group

Input Group


Using a Siebel Business Service Transformation in a Mapping

A Siebel Business Service transformation can have the following types of input and output arguments:

♦ Integration object. Provides a logical representation of external application data or Siebel data that corresponds to an external application.

♦ Hierarchy object. Represents hierarchical Siebel data stored in a property set. Property sets are in memory representations of Siebel application data.

♦ Date, String, or Number. Date, String, and Number are primitive datatypes.

Table 6-1 describes the input and output ports of a Siebel Business Service transformation:

Working with Integration ObjectsWhen a Siebel Business Service transformation invokes a method that takes an integration object as an argument, you can use an XML Generator transformation to generate the XML string.

Each integration object has an XSD generated by the Designer. The XSD is stored in the <PowerCenter Installation Directory>\client\bin directory. The format for the XSD file name is <IntegrationObjectName>.xsd. The data you provide as input to a Siebel Business

Table 6-1. Input and Output Ports

Input Argument Output Argument Description

Integration object Date, String, or Number

An integration object is passed as an XML string to a Siebel Business Service transformation. You can directly pass the XML string to the Siebel Business Service transformation or use an XML Generator transformation to generate the integration object as an XML string.

Date, String, or Number

Integration object An integration object is generated as an XML string by the Siebel Business Service transformation. Use an XML Parser transformation to parse the XML string generated by the Siebel Business Service transformation.

Integration object Integration object You can directly pass the XML string to the Siebel Business Service transformation or use an XML Generator transformation to generate the integration object as an XML string. Use an XML Parser transformation to parse the XML string generated by Siebel Business Service transformation.

Hierarchy object Date, String, or Number

A hierarchy object is directly passed as an XML string to a Siebel Business Service transformation.

Date, String, or Number

Hierarchy object A hierarchy object is generated as an XML string by a Siebel Business Service transformation.

Hierarchy object Hierarchy object A hierarchy object is directly passed as an XML string to a Siebel Business Service transformation. A hierarchy object is generated as an XML string by the Siebel Business Service transformation.

Using a Siebel Business Service Transformation in a Mapping 65

transformation must comply with the XSD. The XML Generator transformation converts the source data to a format compliant with the XSD. The output of the XML Generator transformation is input for the Siebel Business Service transformation. For more information about creating an XML Generator transformation, see the PowerCenter XML Guide.

When a business service method returns an integration object as an output, you can parse the output XML according to the target database using an XML Parser transformation. The Designer generates XSD for the integration object. The XML Parser transformation consumes the XSD and parses the output XML according to the target database. For example, if you want to insert data into an Oracle table, you can parse the XML output to a format that complies with the Oracle table.

Example of Integration Object as InputA business service method can take an integration object as the input. Consider a business case where you want to load data from a flat file source into a Quote business component. You can use the Siebel Quote business service to invoke a method called Insert. The Insert method takes the integration object SiebelMessage as an input argument and adds a record to the underlying business component called Quote. The addition of a record is based on the input SiebelMessage, which is an XML string. To generate the XML string, use the XML Generator transformation.

The following figure shows a mapping that includes the Siebel_Quote_Insert Business Service transformation:

The sample mapping includes the Siebel_Quote_Insert Business Service transformation. To insert a Quote record, provide input values for Name, Id, QuoteNumber, QuoteType, and Description from the source. The XML Generator transformation uses the input values to create an integration object in the XML format. Use Quote Interface.xsd to create the XML Generator transformation that generates the XML string in the format required by the Insert method. Pass the output of the XML Generator transformation to the Siebel_Quote_Insert Business Service transformation.


Example of Integration Object as OutputA business service method can also generate an integration object as an output. Consider a case where you want to query the details of an account. You can use the Siebel Account business service to invoke a method called QuerybyId. QuerybyId accepts the primaryRowId of an account as an input and generates the integration object in an XML string format as the output. You can use an XML Parser transformation to parse the output XML string into a format compliant with the target.

The following figure shows a Siebel Business Service transformation, Siebel_Account_QueryById, in a mapping that invokes the business service method called QuerybyId:

The mapping includes the Siebel_Account_QueryById Business Service transformation. To get the account details, provide the primaryRowId of an account from the source. The Siebel_Account_QueryById transformation passes the account details as an integration object, in an XML string format, to the SiebelMessage port. Use the Account Interface.xsd to create an XML Parser transformation. Pass the output of the Siebel_Account_QueryById transformation to the XML Parser transformation, which parses the XML string in the format required by the target.

Working with Hierarchy ObjectsA business service method can take a hierarchy object as the input. A business service method can also generate a hierarchy object as an output. The hierarchy object is represented as an XML string.

Example of Hierarchy Object as InputYou need to generate a hierarchy object as an XML string to pass it as an input argument to a Siebel business service method.


The following figure shows a sample mapping that uses a hierarchy object as the input:

The sample mapping shows a XML_Converter_HierToDoc transformation. This transformation takes a hierarchy object as the input and converts it into an XML document. The hierarchy object is passed as an XML string from the source to the XML_Converter_HierToDoc transformation. This transformation converts the input hierarchy object into an XML document and generates the document as an XML string.

Example of Hierarchy Object as OutputA Siebel Business Service transformation generates a hierarchy object as an XML string.

The following figure shows a sample mapping that generates hierarchy object as an output:

The sample mapping uses XML_Converter_DocToHier transformation that takes an XML document as an input and converts the input into the hierarchy object. The XML document is passed as an input to the XML_Converter_DocToHier transformation. This transformation converts the input XML document to the hierarchy object and generates the hierarchy object as an output.

Working with Strings, Numbers, and DatesWhen a business service method takes a string, number, or date as an input argument, you can pass the input directly to a Siebel Business Service transformation.

For example, you can use a Siebel Business Service transformation, Authentication_Business_Service, to extract the role and Siebel user name of a Siebel user. This Siebel Business Service transformation accepts the user name, credentials, and password as inputs. This transformation provides the role and Siebel user name of the Siebel user as the output.


The following table lists the column relationships between the source definition, Authentication_Business_Service, and the target definition:

The following figure shows a mapping with the Authentication_Business_Service Business Service transformation:

The Integration Service inserts the following sample row into the target definition:

Allen, Jon Rane

Allen is the role assigned to the Siebel user, and Jon Rane is the Siebel user name of a user.

Source Column Name Business Service Transformation Column Name Target Column Name

GetPrivateCredentials GetPrivateCredentials

Password Password

User_Name User_Name

Role Role

Siebel_User_Name Siebel_User_Name


Creating a Siebel Business Service TransformationCreate a Siebel Business Service transformation in the Transformation Developer or the Mapping Designer.

To create a Siebel Business Service transformation:

1. Open the Transformation Developer.

-or-

Open the Mapping Designer.

2. Click Transformation > Create.

3. Select Siebel Business Service transformation.

4. Enter a name for the transformation.

5. Click Create.

The wizard appears.

6. Enter the following parameters:

7. Click Next.

The wizard displays a list of business services and the corresponding methods.

8. Select a business service to view the list of supported methods.


Protocol Protocol used to connect to Siebel. The format for the protocol is siebel[[.transport][.[encryption][.[compression]]]]. The parameters in the protocol format are:- transport. Enter http or TCPIP. Default is TCPIP.- encryption. Enter NONE or RSA. Default is NONE.- compression. It can accept two values: NONE or zlib. Default is zlib.




Application Object Manager Siebel Application Business Object Manager. For more information about Siebel Application Object Manager, see “Application Object Manager” on page 5.

User Name User name to connect to Siebel.


Encoding Code page used for communication between the Designer and the Siebel Server. By default, Java Data Bean API uses the UTF-8 encoding.

Note: For more information about connection parameters, contact your Siebel system administrator.


9. Select a method that you want to import.

When you select a method, you can view information about its input and output arguments in the details area.

10. Click Finish to import the selected method as a transformation.

11. Click Done.

Creating a Siebel Business Service Transformation 71

C h a p t e r 7

Processing Siebel Calculated Expressions


♦ Overview, 74

♦ Processing Siebel Business Component Expressions, 75

♦ Working with the Siebel Business Component Mapplet, 77

♦ Creating the Siebel Business Component Mapplet, 82

73

OverviewUse PowerExchange for Siebel to extract data from the Siebel business component fields that contain calculated expressions. A calculated expression is a Siebel expression that calculates the value of a field in a business component based on the value of other fields in the business component.

For example, the Explorer_Label field in the Account business component uses the following Siebel calculated expression to calculate its value from the CSN, Name, and Location fields:

[CSN] + “ - “ + [Name] + “, “ + [Location]

When the Integration Service reads data from the Explorer_Label field, it calculates the value of the calculated expression before it passes the data to other transformations in the mapping.

To calculate the value of Siebel calculated expressions in a mapping, create a mapplet for the Siebel business component. The Siebel business component mapplet converts Siebel calculated expressions in the business component to the PowerCenter transformation language that the Integration Service uses to process the calculated expressions.

74 Chapter 7: Processing Siebel Calculated Expressions

Processing Siebel Business Component ExpressionsYou can create a Siebel business component mapplet to process the following Siebel business component expressions:

♦ Siebel business component calculated expressions

♦ Siebel business component nested calculated expressions

♦ Siebel business component lookup expressions

Processing Siebel Business Component Calculated ExpressionsThe Siebel business component mapplet uses an Expression transformation to process calculated expressions. The mapplet converts calculated expressions into the PowerCenter transformation language and processes the value of the expression. It then passes the value of the expression to other transformations or targets in the mapping. For more information about using an Expression transformation in a Siebel business component mapplet, see “Using an Expression Transformation” on page 78.

The Siebel business component mapplet processes calculated expressions that are supported by the PowerCenter transformation language. When a Siebel business component source contains a port with a Siebel expression that the transformation language does not support, the Siebel business component mapplet produces a NULL output for the port. For example, you want to process the Functional_Currency_Code field, which contains an expression Currency (). The transformation language does not support the expression Currency (). The mapplet produces a NULL output value for the Functional_Currency_Code field.

For more information about Siebel expressions supported by the PowerCenter transformation language, see “Using an Expression Transformation” on page 78.

When a Siebel business component source contains fields with names that use special characters such as a slash (/), the Siebel business component mapplet replaces the special character with an underscore (_). The Designer does not recognize special characters in the Siebel business component source. When you link the ports in the Application Source Qualifier for a Siebel business component to the corresponding ports in the Siebel business component mapplet, the ports that contain special characters do not get linked to the corresponding ports in the Siebel business component mapplet. You need to manually connect the ports with special characters.

The Siebel business component mapplet requires that a business component field with a calculated expression have the same datatype as its calculated expression. When the datatype of a Siebel business component field differs from the datatype of its calculated expression, the Siebel business component mapplet interprets the field as NULL. For example, the Time Sheet business component contains the Period_End_Date_String field, which uses the Text datatype. The Period_End_Date_String field contains the following calculated expression:

Period_End_Date

Processing Siebel Business Component Expressions 75

Period_End_Date is a field of the Date datatype in the Time Sheet business component. Since the datatypes of the Period_End_Date_String field and its calculated expression are incompatible, the Integration Service interprets the Period_End_Date_String field as NULL.

The Siebel business component mapplet does not interpret predefault field syntax. If a Siebel business component field contains an expression with predefault field syntax, the Expression transformation of the Siebel business component mapplet interprets the expression as a calculated expression. The Expression transformation evaluates the field as NULL.

Processing Siebel Business Component Nested Calculated Expressions

The Siebel business component mapplet can process nested calculated expressions in the Siebel business component source. A field with a nested calculated expression references the value of another field in the same business component that contains a calculated expression.

For example, the Deal_Size field in the Opportunity business component contains a calculated expression that references the calculated expressions in the Users_Score and Budget_Amt_Score fields. The Integration Service processes the calculated expressions in the Users_Score and Budget_Amt_Score fields. It uses the values from the Users_Score and Budget_Amt_Score fields to process the calculated expression in the Deal_Size field.

For more information about nested Siebel calculated expressions, see “Using an Expression Transformation” on page 78.

Processing Siebel Business Component Lookup ExpressionsWhen a business component field contains a lookup expression, the Siebel business component mapplet includes a Lookup transformation to process the expression.

For more information about the Lookup transformation in the Siebel business component mapping, see “Using a Lookup Transformation” on page 80.


Working with the Siebel Business Component MappletThe Create Mapplet for Siebel Calculated Fields Wizard creates a mapplet that contains the following transformations:

♦ Input transformation. Receives data from a business component source definition.

♦ Expression transformation. Interprets the Siebel calculated expressions to the PowerCenter transformation language.

♦ Lookup transformation. Unconnected transformation when the business component contains a field with a lookup expression.

♦ Output transformation. Passes the interpreted calculated values to the mapping.

Using an Input TransformationAn Input transformation contains ports that receive data from a Siebel business component source definition. The Input transformation includes ports for the fields that the Expression transformation uses to process calculated expressions.

When you connect the Application Source Qualifier for a Siebel business component source to the Input transformation, link the ports that the mapplet needs to calculate the values of fields with calculated expressions. The Input transformation does not contain input ports for Siebel business component fields with calculated expressions. Do not link Siebel business component fields with calculated expressions to the mapplet.

For example, create a Siebel business component mapplet to process the State___Calc field in the Employee business component. The field contains the following calculated expression:

IIf ([Share_Address_Flag] = “Y”, [State], ‘’)

Share_Address_Flag and State are fields in the Employee business component. To interpret the calculated expression in the State___Calc field, link the Share_Address_Flag and State fields from the Siebel business component source definition to the Input transformation. The Input transformation passes the data from these fields to the Expression transformation.

Working with the Siebel Business Component Mapplet 77

The following figure shows a mapplet that processes the State___Calc field for which the Share_Address_Flag and State fields are inputs:

The mapplet has the following functionality:

♦ The Input transformation passes Siebel business component fields required to process Siebel calculated expressions to the Expression transformation.

♦ The mapplet passes the output values of a calculated expression through the Output transformation to other transformations or targets in the mapping.

Using an Expression TransformationThe Expression transformation receives data from the Input transformation and converts Siebel expressions to the PowerCenter transformation language.

The following table describes the Siebel expressions you can interpret using the Siebel business component mapplet:

For example, the Overdue field in the Action business component contains the following Siebel calculated expression:

[Done] IS NULL AND [Start_Date] < Today ()

Siebel Expression Transformation Language Expression

IIf (testExpr, expr1, expr2) IIF (testExpr, expr1, expr2)

IfNull (expr1, expr2) IIF (ISNULL (expr1), expr2, expr1)

Lookup (type, val) :LKP.Look_up (type, val)

LookupValue (type, lang_ind_code) :LKP.LookupValue (type, lang_ind_code)

LookupName (type, val) :LKP.LookupName (type, val)

Timestamp () SYSDATE

Today () TRUNC (SYSDATE, ‘DD’)

Siebel business component fields

Output values of a calculated expression


Done and Start_Date are fields in the Action business component. To interpret the Siebel calculated expression, the Expression transformation converts the Siebel expression to the following PowerCenter transformation language expression:

ISNULL (Done) AND Start_Date < TRUNC (SYSDATE,’DD’)

The Expression transformation calculates the value of the expression and passes the data to the Output transformation.

When a Siebel business component contains a Siebel lookup expression, the Expression transformation converts the expression to an equivalent :LKP expression in the PowerCenter transformation language. It passes the expression to a Lookup transformation which makes the lookup query on the S_LST_OF_VAL table. For more information about using the Lookup transformations in a Siebel business component mapplet, see “Using a Lookup Transformation” on page 80.

For example, the HW_Percent_Score field in the Opportunity business component contains the following Siebel lookup expression:

Lookup (“HW_PERCENT”, [HW Percent])

When you create the Siebel business component mapplet, the Expression transformation converts the Siebel lookup expression into the following :LKP expression:

:LKP.Look_up (‘HW_PERCENT’, HW_Percent)

‘HW_PERCENT’ is the type and HW_Percent is the value of the lookup expression. The mapplet includes a specific Lookup transformation based on the :LKP expression to make a lookup query on the Siebel underlying database. For information about viewing a Siebel calculated expression, see “Viewing Attribute Values” on page 94.

When a Siebel business component contains a nested calculated expression, the Expression transformation calculates the values of all expressions that make up the nested expression. For example, the Line Total field in the Forecast_Quote_Item Siebel business component contains the following nested calculated expression:

[Item_Price] * [Quantity]

The Expression transformation processes the calculated expressions in the Item_Price and Quantity fields. It uses the values from the Item_Price and Quantity fields to calculate the value of the Line_Total field.

When the Expression transformation processes a nested calculated expression, it uses variable ports to store the values of the calculated fields referenced by the calculated expression.

For more information about Siebel calculated expressions, see the Siebel documentation. For more information about PowerCenter transformation language expressions, see the PowerCenter Transformation Language Reference.

Configuring the Expression TransformationWhen the Expression transformation cannot interpret a particular Siebel expression, you can configure the ports in the Expression transformation to return more meaningful data instead


of a NULL output. For example, the Full_Name field in the Opportunity business component contains the following Siebel expression:

Language ()

Since the PowerCenter transformation language does not support the calculated expression Language (), the Expression transformation produces the NULL output for the field. You can edit the expression to return strings, such as “Not Available” or “Cannot be determined” by modifying the expression for the port. For more information about using the Expression transformation, see the PowerCenter Transformation Guide.

Using a Lookup TransformationA Siebel business component mapplet includes an unconnected Lookup transformation when the business component contains a lookup expression. The Create Mapplet for Siebel Calculated Fields Wizard creates a Lookup transformation in the mapplet based on the type of :LKP expression in the Expression transformation. The Lookup transformation name in the Siebel business component mapplet corresponds to the PowerCenter :LKP expressions it processes.

A Lookup transformation in a Siebel business component mapplet receives input from the results of a :LKP expression in the Expression transformation. It uses the input values to make a lookup query on the S_LST_OF_VAL table in the Siebel underlying database. Depending on the type of lookup expression, the Lookup transformation returns a specific column from the S_LST_OF_VAL table. Siebel systems use the S_LST_OF_VAL table for lookup functions.

Table 7-1 describes the Lookup transformation in the Siebel business component mapplet:

For example, the HW Percent Score field in the Opportunity business component contains a Siebel lookup expression. When you create a mapplet for the Opportunity business component, the mapplet contains the transformation Look_up. The transformation Look_up contains the TYPE_IN and VAL_IN ports that receive input from the Expression transformation to process the following lookup expression:

:LKP.Look_up (‘HW_PERCENT’, HW_Percent)

‘HW_PERCENT’ is the TYPE_IN value and HW_Percent is the VAL_IN value. The transformation Look_up uses the following lookup condition to query the S_LST_OF_VAL table in the Siebel underlying database:

TYPE = <TYPE_IN> AND VAL = <VAL_IN>

Table 7-1. Lookup Transformations in the Siebel Business Component Mapplet

PowerCenter Lookup Transformation Name Transformation Language Expression Column Returned by

Lookup Transformation

Look_up :LKP.Look_up (type, val) ORDER_BY

LookupValue :LKP.LookupValue (type, lang_ind_code) VAL

LookupName :LKP.LookupName (type, val) NAME


Since the HW Percent Score field contains the Siebel expression Lookup, the transformation Look_up returns a value from the ORDER BY column in the S_LST_OF_VAL table. The Lookup transformation passes the results of the lookup query to the Expression transformation.

Figure 7-1 shows the Lookup transformation ports in a Siebel business component mapplet:

In the mapplet, the Lookup transformation receives input from the Expression transformation, and passes the result of the lookup query to the Expression transformation.

When the Siebel business component mapplet includes a Lookup transformation, specify the location of the S_LST_OF_VAL table. Specify the location of the table in the Location information attribute on the Properties tab. You can specify either the connection value that you use to connect to the Siebel system or the $Source variable. If you specify the $Source variable, configure the $Source connection value in the Workflow Manager.

Using an Output TransformationAn Output transformation receives data from the Expression transformation and sends it to downstream transformations or targets in the mapping. You can manually connect ports from the Output transformation to a target or another transformation in a Siebel business component mapping. You can also link the Output transformation ports to a target or a transformation.

Figure 7-1. Lookup Transformation in a Siebel Business Component Mapplet

Input values Result of the lookup query


Creating the Siebel Business Component MappletCreate the Siebel business component mapplet in the Mapplet Designer. Create a mapplet for each business component source you want to use in the mapping. After you create the mapplet, link the Siebel business component source definition to the mapplet. You must connect the business component fields that are included in the Siebel calculated expressions you want to process.

For example, you want to extract data from the Account business component. The Account business component contains a field called DUNS Intcode, which uses the following Siebel calculated expression:

IIf ([Country] = ”USA”, ”1”, ”2”)

To interpret the calculated expression, create a Siebel business component mapplet for the Account business component. Create a mapping with the Account business component as source and add the Account business component mapplet to the mapping. Connect the Country port from the Application Source Qualifier of the Account business component source to the corresponding port in the Account business component mapplet. The mapplet processes the calculated expression and passes it to the target.

The following figure shows a mapping that contains a mapplet to process the calculated expression in the DUNS Intcode field:

The mapping has the following functionality:

1. The Application Source Qualifier passes data from the Country field into the Account business component mapplet.

2. The Account business component mapplet processes the calculated expression in the DUNS Intcode field using input values from the Country field.

3. The mapplet passes writes data to the relational target Account.


Steps to Create a Siebel Business Component Mapplet

To create a mapplet for a Siebel business component source with calculated expressions:

1. In the Mapplet Designer, click Mapplets > Create Mapplet for Siebel Calculated Fields.

The Create Mapplet for Siebel Calculated Fields Wizard appears.

2. Select the Siebel business components for which you want to create mapplets, and click Next.

3. Optionally, to edit the default mapplet name and description, enter name in the Mapplet Name field and a description in the Mapplet Comment field.

-or-

Click the down arrow in the Mapplet Name field to open the Edit Mapplet dialog box, and edit the mapplet name and description.

4. Click Finish.

Creating the Siebel Business Component Mapplet 83

The mapplet appears in the Mapplet Designer.

For more information about working with mapplets, see the PowerCenter Designer Guide.


C h a p t e r 8

Siebel Sessions


♦ Configuring Application Connections, 86

♦ Configuring Session for a Siebel Target, 88


85

Configuring Application ConnectionsConfigure an application connection, before the Integration Service extracts data from Siebel sources and loads data into Siebel targets.

When you configure an application connection, you specify the connection attributes to connect to a Siebel source, target, or a Siebel Business Service transformation.

Use the following procedure to configure connections for objects:

♦ Sources imported through the Java Data Bean API

♦ Targets

♦ Business Service transformations

To configure an application connection:

1. In the Workflow Manager, click Connections > Application.

The Application Connection Browser dialog box appears.

2. Click New.

3. Select Siebel Connection from the list.

4. Click OK.

The Connection Object Definition dialog box appears.

5. Enter the following information in the connection object:



User Name User name to connect to Siebel.

Password Password for the user name.



Enterprise Server Enterprise Server name.

Application Object Manager

Siebel application business object manager. For more information, see “Application Object Manager” on page 5.

Encoding Encoding used for communication between the Integration Service and the Siebel Server. By default, the Integration Service uses the UTF-8 encoding.

Note: For more information about connection parameters, contact your Siebel system administrator.

86 Chapter 8: Siebel Sessions

For information about configuring application connections for sources that are imported through ODBC, see “Configuring Sessions for Siebel Sources” on page 100.

Configuring Application Connections 87

Configuring Session for a Siebel TargetTable 8-1 describes the properties for Siebel targets that you can configure while configuring a Siebel session:

Cache Directory and Cache Size for a Siebel TargetThe Integration Service uses a data cache to store Siebel target data. When the session completes, the Integration Service releases cache memory and deletes the cache files. You might find cache files in the cache directory if the session does not complete successfully. The cache includes a primary key and a foreign key index cache for each target group and one data cache for all groups.

The default cache size to store Siebel target data is 10 MB. The minimum value for cache size is 80 KB. You can set the cache size equal to 20 percent of the available memory for the system.

Table 8-1. Session Level Properties for Targets

Session Property Description

Duplicate Parent Row Handling

Choose one of the following values to indicate how the Integration Service handles duplicate parent rows: - First Row. The Integration Service passes the first row to the target. The Integration Service rejects

rows with the same primary key that it processes after this row. - Last Row. The Integration Service passes the last duplicate row to the target. The Integration Service

rejects rows with the same primary key that it processes before this row. - Error. The Integration Service passes the first row to the target. Rows that follow with duplicate

primary keys increment the error count. The session fails when the error count exceeds the error threshold.

Orphan Row Handling

Choose one of the following values to indicate how the Integration Service handles orphan rows: - Ignore. The Integration Service ignores orphan rows. - Error. The Integration Service treats orphan rows as error. Error count is incremented for each such

row. The session fails when the error count exceeds the error threshold.

Cache Directory

The directory used to cache the Siebel target data. The default cache directory is $PMCacheDir, which is a service variable that represents the directory where the Integration Service stores cache files by default.

Cache Size The maximum buffer size to cache the Siebel target data used by the Integration Service before loading the data into target.


TroubleshootingA Siebel session might time out when you are loading bulk data by creating multiple partitionsAsk your Siebel Administrator to create the siebel.properties file and set higher values for the following connection parameters in this file:

♦ siebel.conmgr.sesstimeout. The number of seconds the Siebel Server will wait before disconnecting an idle client session. Its value must be a positive integer. Default is 2700 seconds.

♦ siebel.conmgr.poolsize. For each object manager process, a pool of open connections is maintained and shared by all the users of that process. This parameter specifies the maximum number of connections that will be stored in the pool. Its value must be a positive integer less than 500. Other values are ignored. Default is 2.

Copy the siebel.properties file to the following directory:


Troubleshooting 89

A p p e n d i x A

Siebel ODBC Sources

This appendix includes the following topics:

♦ Importing Siebel Sources Through ODBC, 92

♦ Application Source Qualifier for Sources, 97

♦ Joining Source Data, 98

♦ Creating and Configuring an Application Source Qualifier, 99

♦ Configuring Sessions for Siebel Sources, 100

♦ Siebel Datatype Reference, 101

91

Importing Siebel Sources Through ODBCYou can import business components and tables as Siebel source definitions through ODBC. Import Siebel source definitions rather than creating them manually in the Source Analyzer. When you import a Siebel source definition, the Designer imports Siebel metadata that is not configurable in the Source Analyzer.

When you import a business component and all of the business components and Siebel tables associated with it, the Designer does not display these relationships in the workspace. However, the Integration Service uses these relationships in a session. The Integration Service reads the metadata from the business component and the associated business components and Siebel tables. It reads the data from the physical database tables associated with the Siebel tables.

After you import a Siebel business component or table, the Navigator displays sources by the Siebel business component or table name by default.

Tip: Click Tools > Options to display business names for sources.

Importing Siebel Business ComponentsUse the Designer to import Siebel business component source definitions. To import a business component, select a business component from the selection list on the Business Components tab.

You can also drill down through the Siebel hierarchy to select a business component from the selection list on the Applications tab.

Table A-1 describes the fields that the Designer imports when you import a business component as a source:

Table A-1. Siebel Details in a Business Component Source Definition


Field Name* Siebel field name.

Attribute* Designer displays the following attributes for each field:- Calculated value expression- Physical table name- Physical column name- Multi value link- Join name

Value* Value used by Siebel Enterprise Applications, which corresponds to the value in the underlying database.

Base Table Name Base table name of the business component.

Search Specification Filter condition used by Siebel Enterprise Applications to retrieve a subset of records. You cannot edit this information.

92 Appendix A: Siebel ODBC Sources

When you import a business component, the Designer imports Siebel system fields. These fields represent the system columns in the underlying base table.

Table A-2 lists the system fields that the Designer imports for every business component:

Importing Siebel TablesUse the Designer to import Siebel table source definitions. To import a Siebel table, select a Siebel table from the selection list.

When you import a table as a source definition, the Designer imports the details of the Siebel table.

Table A-3 describes the Siebel table details:

You can import all types of Siebel table source definitions into the repository except for the following types:

♦ Dictionary

Sort Specification Filter condition used by Siebel Enterprise Applications to implement a sort order. You cannot edit this information.

*These fields appear on the Attributes tab of the source definition when opened in the Source Analyzer.

Table A-2. Siebel System Fields and Columns

System Field Name System Column Name

ID ROW_ID

Created CREATED

Created By CREATED_BY

Updated LAST_UPD

Updated By LAST_UPD_BY

Table A-3. Siebel Details in a Table Source Definition


Source Table Table name.

Business Name Siebel business name.

Owner Name User name for the table.

Table Type Source subtype.

Description Information pertaining to a Siebel table.

Base Table Name Base table name for extension tables.

Table A-1. Siebel Details in a Business Component Source Definition


Importing Siebel Sources Through ODBC 93

♦ Repository

♦ Interface

♦ Virtual

♦ Enterprise Application Integration (EAI) Adapter tables

Filtering Siebel Sources When you import Siebel source definitions, you can enter a filter condition to limit the number of business components and tables that appear in the Import Siebel Metadata dialog box.

You can apply filters based on the table name, business name, or business component name. You cannot filter business components on the Applications tab because they are organized according to the Siebel Enterprise Applications hierarchy.

Use the following guidelines when you enter a filter condition:

♦ You can enter one or more filter criterion at a time.

♦ Use commas to separate filter criterion.

♦ Use an underscore (_) or the percent symbol (%) as wildcard characters. Use an underscore to represent a single character. Use the percent symbol to represent multiple characters.

♦ To change a filter condition, enter the modified condition and reconnect to the database.

Viewing Attribute ValuesYou can view attribute values on the Attributes tab of a business component in the Source Analyzer. To view the entire value of an attribute, double-click the Value field next to the attribute. For more information about attributes and their values, see “Siebel Business Components” on page 9.

Steps to Import Siebel Source Definitions

To import a Siebel source definition:

1. In the Source Analyzer, click Sources > Import From Siebel.

The Import Siebel Metadata dialog box appears.

2. Select the Siebel ODBC connection, and enter the database user name and password to connect to the underlying database. Since this user name is not the owner of the Siebel system tables, you must also enter the table owner name.

Note: Enter the database user name created when you configured access to Siebel metadata. For more information about configuring access to Siebel metadata, see “Accessing Siebel Metadata” on page 20.

3. Optionally, enter a filter criterion and specify how to apply the filter.

4. Click Connect.


5. Select the Applications, Business Components, or Tables tab.

6. Open the folders for the objects you want to import.

7. Select the objects, and click Add to Import List.

You can add both business components and tables to the import list.

8. To display the objects on the Import List, click View Import List.

To remove an object from the list, select it and click Delete.

Note: If you import a business component that does not have a base table or has inconsistent metadata in the Siebel repository, the Designer does not display the business component in the Import List.

9. To close the Import List, click Close.

10. To import all listed Siebel objects, click OK.

Updating Column StatisticsWhen you add a Siebel business component to the Import List and the Siebel source database contains outdated column distribution statistics, it can take longer than a minute. The statistics determine the index to be used when SQL queries are executed. Updating the statistics can shorten the time taken to add a business component to the Import List.

To update the column distribution statistics, run a query against the Siebel source database. If you save the query output to a file and delete the headers, you can run the file as an SQL script against the Siebel source database.

To update the column distribution statistics on Oracle:

1. Run the following query:

SELECT ‘analyze table’, name, ‘compute statistics’

FROM S_TABLE

WHERE type = ‘Repository’;

2. After you successfully run the query in step 1, run the following query:

SELECT ‘analyze index’, name, ‘compute statistics’

FROM S_INDEX

Importing Siebel Sources Through ODBC 95

WHERE tbl_id in (select row_id from s_table where type = ‘Repository’);

3. Save the query output to a file.

4. Delete the headers in the file that contains the query output.

5. Run the file as an SQL script against the Siebel source database.

To update the column distribution statistics on IBM DB2:

1. Run the following query:

SELECT ‘runstats on table’, ‘SIEBEL.’||NAME, ‘and indexes all’

FROM S_TABLE

WHERE TYPE = ‘Repository’;

2. Save the query output to a file.

3. Delete the headers in the file that contains the query output.

4. Run the file as an SQL script against the Siebel source database.


Application Source Qualifier for Sources In the Application Source Qualifier, you can perform the following tasks:

♦ Create a custom extract query. Create an extract override for Siebel tables to replace the default query.

♦ Specify sorted ports. Sort source data by the number of ports you enter.

♦ Select distinct values from the source. Retrieve distinct source rows.

♦ Join data from the same Siebel system. Join two or more Siebel tables with key relationships by connecting them to one Application Source Qualifier. For more information, see “Joining Source Data” on page 98.

♦ Filter data. Use a source filter to remove source rows that you do not need in the data flow. When you enter a source filter for a business component, use the following syntax:

SiebelBusinessComponentName.SiebelFieldName

Understanding the Default QueryFor business components, the Designer creates the default query based on the multi-value link and join relationships of the fields you select. If you select the base fields in a business component, the Designer includes the base table in the FROM clause of the default query. If you select all of the fields in a business component, the Designer creates the default query based on the multi-value link and join relationships of all of the fields.

Depending on the fields and join conditions you select from a business component, the Integration Service can generate less, the same, or more rows of data than the base table.

Based on the fields and join conditions you select from a business component, the Integration Service can generate duplicate rows of data. Use the Select Distinct option to avoid creating duplicate rows.

You can use extract override to override a default query. Use SQL syntax supported by the underlying database for the Siebel system to override a default query. Use physical database table names for Siebel tables in an extract override. Every column name must be qualified by the name of the table, view, or synonym in which it appears. For example, if you want to include the EMPLOYEE_ID column from the EMPLOYEES table, enter EMPLOYEES.EMPLOYEE_ID.

Application Source Qualifier for Sources 97

Joining Source DataWhen you join related tables, the Integration Service joins the tables based on the related keys in each table.

The default join is an inner equijoin that uses the following syntax in the WHERE clause:

Source1.column_name = Source2.column_name

The columns in the default join must have the following properties:

♦ A primary key-foreign key relationship

♦ Matching datatypes

When you connect multiple Siebel table source definitions, the Designer joins them based on logical relationships between connected and associated sources.

The Designer can create a default join for Siebel table source definitions if the tables are related. Siebel tables are related if there is a primary key-foreign key relationship in the Source Analyzer.

Custom JoinsTo override the default join, you can enter the contents of the WHERE clause that specifies the join in the custom query.

You can override the default join under the following circumstances:

♦ Columns do not have a primary key-foreign key relationship.

♦ You want to specify a different type of join, such as an outer join.

Creating Key RelationshipsYou can join tables if the tables have primary key-foreign key relationships. However, you can create primary key-foreign key relationships in the Source Analyzer by linking matching columns in different tables. These columns do not have to be keys, but they must be included in the index for each table.

If you join multiple foreign keys from one table to a single primary key in another table, use a Lookup transformation instead of an Application Source Qualifier transformation to join these tables. Otherwise, the Integration Service might not read the correct number of rows.

Join OverridesUse the following syntax for Siebel business components if you use a source filter in the join override:


For Siebel business components and tables, double-click the column names that appear in the Ports window to avoid typing the name of every column.


Creating and Configuring an Application Source Qualifier

By default, the Designer creates an Application Source Qualifier when you add a Siebel source to a mapping. If you configure the Designer to create a source definition without an Application Source Qualifier, you can create the Application Source Qualifier manually. You must then manually connect the Application Source Qualifier with a source definition in the mapping.

After you create an Application Source Qualifier, you can set several configuration options.

Connecting Siebel Source Definitions in a MappingWhen you connect Siebel source definitions to an Application Source Qualifier transformation in a mapping, use the following guidelines:

♦ You can connect a Siebel business component source definition to an Application Source Qualifier transformation.

♦ You can join a Siebel table source definition with one or many related Siebel table source definitions using one Application Source Qualifier transformation.

♦ You cannot join a Siebel business component source definition with any other source definition using an Application Source Qualifier transformation.

Creating and Configuring an Application Source Qualifier 99

Configuring Sessions for Siebel SourcesConfigure an application connection before the Integration Service extracts data from Siebel sources. The application connection is a database connection to the Siebel underlying database. The application type for a Siebel source and Lookup transformation is Siebel.

For more information about configuring Siebel application connections, see the PowerCenter Workflow Administration Guide.

You cannot use a connection variable for an application connection.

When you configure an application connection, you specify the connection attributes to connect to a Siebel source.

Note: When you configure an application connection for a source, use the same user name and password that you created to access Siebel application data. Enter the owner name as the source table name prefix to access application data.

Configuring Session for a Lookup TransformationWhen you create a Siebel session with a Lookup transformation, you must specify an application connection for the Integration Service to connect to the Siebel underlying database and access the S_LST_OF_VAL table.

Partitioning DataTo extract a large amount of source data, you can partition the sources to improve session performance. By default, the Workflow Manager sets the partition type to pass-through for Siebel sources. You can also specify key range partitioning for Siebel sources.

Use the following guidelines when you create partitions for Siebel sources:

♦ When you create a key for a Siebel business component, the Integration Service uses the following syntax:


♦ When you use a source filter in a join override or a Siebel business component, use the following syntax for Siebel business components:



Siebel Datatype ReferencePowerCenter uses the following datatypes in Siebel mappings when you import source definitions through ODBC:

♦ Siebel native datatypes. Siebel datatypes appear in Siebel definitions. Siebel Enterprise Applications has field and column datatypes.

− Field datatypes. Siebel business components have field datatypes. Siebel field datatypes correspond to the Siebel column datatypes in the Siebel system.

− Column datatypes. Siebel tables have column datatypes. These datatypes describe the type of data exchanged between the Siebel system and the underlying database.

♦ Transformation datatypes. Set of datatypes that appear in the transformations. They are internal datatypes based on ANSI SQL-92 generic datatypes, which the Integration Service uses to move data across platforms. They appear in all the transformations in a mapping.

For information about the datatypes when you import source definitions through the Java Data Bean API, see “Siebel and Transformation Datatypes” on page 104.

When the Integration Service reads source data, it converts the native datatypes to the comparable transformation datatypes before transforming the data. When the Integration Service writes to a target, it converts the transformation datatypes to the comparable native datatypes. For more information about datatypes, see the PowerCenter Designer Guide.

When you import a Siebel definition, the Designer connects to the Siebel data source to import metadata. Siebel metadata describes datatypes, precision, and scale of columns. As a result, the Designer displays Siebel definitions with Siebel datatypes.

Table A-4 lists Siebel field and column datatypes compatible with the Integration Service:

Table A-4. Siebel Field and Column Datatypes for Siebel Source Definitions

Siebel Field Datatype (Business Components) Siebel Column Datatype (Tables)

DTYPE_BOOL Char (length 1)

DTYPE_CURRENCY Number

DTYPE_DATE Date

DTYPE_DATETIME Date/Time

DTYPE_ID Varchar (length 15)

DTYPE_INTEGER Number

DTYPE_NOTE Long

DTYPE_NUMBER Number

DTYPE_PHONE Varchar (length 40)

DTYPE_TEXT Varchar

DTYPE_TIME Time

Siebel Datatype Reference 101

For example, you import a source definition through ODBC, and the source definition has a Siebel DTYPE_NOTE column. If the Siebel system resides on an Oracle database server, data in that column is saved in the physical table as the Oracle Long native datatype. The Integration Service queries the physical table and extracts data from that column as the Long datatype. The Integration Service then converts the Oracle Long datatype to a Text transformation datatype for data transformation.

Table A-5 lists the Siebel datatypes and corresponding transformation datatypes for Siebel source definitions compatible with PowerCenter:

Table A-5. Siebel and Transformation Datatypes for Siebel Sources

Siebel Field Datatype (Business Components) Transformation Datatype Range and Description

DTYPE_BOOL String 1 to 65,535 characters.Fixed-length or varying-length string.

DTYPE_CURRENCY Decimal Precision 15. Double-precision floating-point numeric value.

DTYPE_DATE Date/Time Jan 1, 1753 to Dec 31, 1999 AD (precision to the second).

DTYPE_DATETIME Date/Time Jan 1, 1753 to Dec 31, 1999 AD (precision to the second).

DTYPE_ID String 1 to 65,535 characters.Fixed-length or varying-length string.

DTYPE_INTEGER Integer Precision 10, scale 0 to 28.Integer value.

DTYPE_NOTE Text 1 to 65,535 characters.Fixed-length or varying-length string.

DTYPE_NUMBER Decimal Precision 1 to 28.Scale of 0 to 28.

DTYPE_PHONE String 1 to 65,535 characters.Fixed-length or varying-length string.

DTYPE_TEXT Text 1 to 65,535 characters.Fixed-length or varying-length string.

DTYPE_TIME Date/Time Jan 1, 1753 to Dec 31, 1999 AD (precision to the second).

DTYPE_CHAR* String 1 character.

DTYPE_VARCHAR* String 1 to 65,535 characters.Fixed-length or varying-length string.

*DTYPE_CHAR and DTYPE_VARCHAR are not Siebel datatypes. The Designer uses these datatypes to import Siebel tables that have Char and Varchar column datatypes.


A p p e n d i x B

Siebel Datatype Reference

This appendix includes the following topic:

♦ Siebel and Transformation Datatypes, 104

103

Siebel and Transformation DatatypesPowerCenter uses the following datatypes in Siebel mappings when you import source definitions through Java Data Bean API:

♦ Siebel native datatypes. Siebel datatypes appear in Siebel definitions in a mapping.

♦ Transformation datatypes. Set of datatypes that appear in the transformations. They are internal datatypes based on ANSI SQL-92 generic datatypes, which the Integration Service uses to move data across platforms. They appear in all transformations in a mapping.

When the Integration Service reads source data, it converts the native datatypes to the comparable transformation datatypes before transforming the data. When the Integration Service writes to a target, it converts the transformation datatypes to the comparable native datatypes. For more information about datatypes, see the PowerCenter Designer Guide.

Table B-1 lists the Siebel and corresponding transformation datatypes for Siebel business service methods compatible with PowerCenter:

Table B-1. Siebel and Transformation Datatypes for Siebel Source and Target Definitions


DTYPE_BOOL String 1 to 65,535 characters.Fixed-length or varying-length string.

DTYPE_CURRENCY Decimal Precision 15.Double-precision floating-point numeric value.

DTYPE_DATE Date/Time Jan 1, 1753 to Dec 31, 1999 AD (precision to nanosecond)

DTYPE_DATETIME Date/Time Jan 1, 1753 to Dec 31, 1999 AD (precision to nanosecond)

DTYPE_ID String 1 to 65,535 characters.Fixed-length or varying-length string.

DTYPE_INTEGER Integer Precision 10, scale 0 to 28.Integer value.

DTYPE_NOTE Text 1 to 65,535 characters.Fixed-length or varying-length string.

DTYPE_NUMBER Decimal Precision 1 to 28.Scale 0 to 28.

DTYPE_PHONE String 1 to 65,535 characters.Fixed-length or varying-length string.

DTYPE_TEXT* Text 1 to 65,535 characters.Fixed-length or varying-length string.

DTYPE_TIME Date/Time Jan 1, 1753 to Dec 31, 1999 AD (precision to nanosecond)

104 Appendix B: Siebel Datatype Reference

Table B-2 lists the Siebel and corresponding transformation datatypes for Siebel business service methods compatible with PowerCenter:

DTYPE_UTCDATETIME Date/Time Jan 1, 1753 to Dec 31, 1999 AD (precision to nanosecond.

*PowerExchange for Siebel stores integration objects and hierarchy objects in DTYPE_TEXT in the PowerCenter repository.

Table B-2. Siebel and Transformation Datatypes for Siebel Business Service Methods

Siebel Field Datatype (Business Service Methods)

Transformation Datatype Range and Description

String String 1 to 65,535 characters.Fixed-length or varying-length string.

Date Date/Time Jan 1, 1753 to Dec 31, 1999 AD (precision to nanosecond)

Number Integer Precision 10, scale 0 to 28.Integer value.

Integration object String 1 to 65,535 characters.Fixed-length or varying-length string.

Hierarchy object String 1 to 65,535 characters.Fixed-length or varying-length string.

Table B-1. Siebel and Transformation Datatypes for Siebel Source and Target Definitions


Siebel and Transformation Datatypes 105

106 Appendix B: Siebel Datatype Reference

A p p e n d i x C

Error Messages

This appendix includes the following topics:

♦ Designer Messages, 108

♦ SEBL Codes, 113

♦ SiebelCT Codes, 116

♦ SiebelRdr Codes, 117

♦ SiebelWrt Codes, 120

107

Designer MessagesThe Designer displays error messages in message boxes and in the output window. This section lists messages alphabetically.

application source qualifier <application source qualifier name> has business component and other sources.Cause: The listed application source qualifier is connected to a Siebel business

component source definition and other source definitions. A Siebel business component cannot be joined with other Siebel sources.

Action: Use a separate application source qualifier for each Siebel source definition.

application source qualifier <application source qualifier name> has filter clause which uses one or more fields that were not selected.Cause: The listed application source qualifier has a filter clause that uses one or more

fields not selected from the business component.

Action: In the filter clause, use the fields from the business component.

application source qualifier <application source qualifier name> has join override clause which uses one or more fields that were not selected.Cause: The listed application source qualifier has a join override clause that uses one

or more fields not selected from the business component.

Action: In the join override clause, use the fields from the business component.

application source qualifier <application source qualifier name> has more than one business component attached.Cause: The listed application source qualifier is associated with or connected to more

than one Siebel business component source definition. Associate or connect one business component source definition to a single application source qualifier.

Action: Disconnect one of the business component source definitions from the application source qualifier, or remove one of the associated business component source definitions from the mapping.

-or-

To use more than one business component in a single mapping, create an application source qualifier for each business component. Use a Joiner transformation to join two related business components.

108 Appendix C: Error Messages

application source qualifier <application source qualifier name> has one or more calculated fields projected out. NULL data would be produced for such fields. Generate a mapplet for this business component before using calculated fields.Cause: An application source qualifier contains one or more fields with calculated

expressions connected to a target or another transformation. You cannot connect Siebel business component fields with calculated expressions from an application source qualifier to a target or another transformation.

Action: Disconnect any ports that connect fields with calculated expressions from the application source qualifier to the target or transformation. Generate a Siebel business component mapplet to interpret the calculated expressions in the business component. Connect the fields with calculated expressions from the application source qualifier to the Siebel business component mapplet.

application source qualifier <application source qualifier name> has partitions with key names that use one or more fields that were not selected.Cause: The listed application source qualifier has partitions with key names that use

one or more fields not selected from the business component.

Action: For key names in partitions, use the fields from the business component.

application source qualifier <application source qualifier name> sources are not related.Cause: You tried to connect or associate two unrelated table source definitions in the

listed application source qualifier. Connect or associate related table source definitions in an application source qualifier.

Action: Disconnect one of the unrelated sources. Or, remove one of the associated source definitions.

Check the specified connection parameters.Cause: The connection parameters except user name, password, and protocol are

incorrect.

Action: Verify all the connection parameters.

Error! Cannot find Siebel metadata from source <source name>.Cause: In the Import from Siebel dialog box, database user name entered does not

have SELECT permission on the Siebel metadata tables.

Action: Use a different user name or have the Siebel administrator grant the user the necessary permissions. For more information about the permissions necessary to import source definitions, see “Configuring Access to Siebel” on page 20.

-or-

Cause: You tried to import a non-Siebel object in the Import from Siebel dialog box.

Action: Import Siebel sources with the Import from Siebel dialog box.

Designer Messages 109

Error! This version of Siebel source <source name> is not supported!Cause: You tried to import a Siebel source definition from a version of Siebel that is

not supported by this version of PowerExchange for Siebel.

Action: Import source definitions or extract source data from supported versions of Siebel.

Failed to connect to Siebel server.Cause: The Siebel server is down or Siebel services have stopped.

Action: Check the network connection and restart the Siebel services.

Failed to get the repository object.Cause: PowerExchange for Siebel failed to get the repository objects.

Action: Verify that you are connected to the repository and restart the Designer.

Failed to load jvm.dll. Verify that INFA_HOME is correctly set and it contains the Java directory. Cause: The INFA_HOME environment variable is not set to the <PowerCenter

Installation Directory>.

-or-

<PowerCenter Installation Directory> does not contain the Java directory.

Action: Set the INFA_HOME environment variable to the <PowerCenter Installation Directory>.

Failed to load the Siebel .jar files.Cause: PowerCenter could not find the Siebel .jar files at the required location.

Action: Copy the Siebel .jar files to the INFA_HOME\client\bin\javalib directory and restart the Designer.

Failed to log on to Siebel database server.Cause: The Designer was unable to access the Siebel system database server. The

network or the database server might not be running properly.

Action: Verify that the network and database are running before trying again.

Invalid filter value.Cause: The value specified in a search filter condition is incorrect.

Action: Verify the value specified in the Value field. For more information about the search filter condition, see “Filtering Siebel Sources” on page 34.


Invalid mapping. At least one field in the parent group needs to be linked. Cause: A field from one of the child groups is linked. However, no field in the parent

group is linked.

Action: Link at least one field in the parent group. Validate the mapping.

Invalid Siebel Metadata: Siebel Join <Join name> used by one or more projected fields is not found in the repository.Cause: The listed Siebel Join does not exist or is not found in the Siebel system.

Action: Disconnect transformations and targets from any application source qualifier port that uses the listed Siebel Join. You can view the fields that use the listed Join on the Attributes tab of a business component in the Source Analyzer.

Invalid Siebel Metadata: Siebel Link <Link name> used by one or more projected fields is not found in the repository.Cause: The listed Siebel link does not exist or is not found in the Siebel system.

Action: Disconnect transformations and targets from any application source qualifier port that uses the listed Siebel link. Query the database underlying the Siebel system for the multi-value links that use the listed destination link. You can view the fields that use these multi-value links on the Attributes tab of a business component in the Source Analyzer.

Invalid Siebel Metadata: There is no physical column name for non-calculated field <field name>.Cause: A port is created in the Siebel business component that is not based on a

database column.

Action: Disconnect transformations and targets from any application source qualifier port that uses the listed port.

-or-

Delete the listed Siebel business component port from the source definition.

Search specification contains unsupported terms.Cause: The search specification contains expressions using PositionID, RepositoryID,

LoginID, IfNull, Iif, or GetProfileAttr.

Action: A Siebel search specification does not allow expression using PositionID, RepositoryID, IfNull, Iif, or GetProfileAttr. Modify the search specification.

Search specification is invalid.Cause: The field names in the search specification are not enclosed in parentheses.

Action: Enclose all field names in the search specification in parentheses.

Designer Messages 111

Search specification contains non-projected fields. The search specification will not be processed.Cause: The search specification has a field that is part of the source but is not

connected in the mapping to an output port.

Action: Project the fields that are part of the search specification.

Search specification contains calculated fields. The search specification will not be processed.Cause: The search specification includes calculated fields.

Action: Remove the calculated fields from the search specification. The search specification cannot include calculated fields.

Unable to find license key for PowerExchange for Siebel. Cause: License key is not available or it has expired.

Action: Contact Informatica Global Customer Support to get a valid license key.

Unable to import a Siebel source definition. Cause: Internal error.

Action: Contact your Siebel system administrator.

Unable to launch the PowerExchange for Siebel UI because the INFA_HOME environment variable is not set. Cause: The INFA_HOME environment variable is not set.

Action: Set the INFA_HOME environment variable to <PowerCenter Installation Directory> and restart the Designer.

Unable to load the default resource DLL, Siebel0409.dllCause: The Designer could not find the Siebel0409.dll in the <PowerCenter

Installation Directory>\client\bin directory.

Action: Reinstall PowerExchange for Siebel.

Warning: application source qualifier transformation <application source qualifier name> has a larger number of sorted ports than projected output ports. Ignoring number of sorted ports.Cause: In the application source qualifier, the Number of Sorted Ports option on the

Properties tab has a higher value than the number of connected output ports.

Action: In the application source qualifier, use a lower value for the Sorted Ports option or increase the number of connected output ports.


SEBL CodesSEBL_30005 Not all sources are related in application source qualifier <application source

qualifier name>.Cause: You tried to connect or associate two unrelated table source definitions in the

listed application source qualifier. Connect or associate related table source definitions in an application source qualifier.

Action: Disconnect one of the unrelated table source definitions.

-or-

Remove one of the associated source definitions.

SEBL_30006 Unknown error occurred in application source qualifier <application source qualifier name>.

Cause: Internal error.

Action: Contact Informatica Global Customer Support.

SEBL_30008 application source qualifier <application source qualifier name> has projected port with no inbound link.

Cause: In the listed application source qualifier, the output port is linked. However, the corresponding input port is not linked.

Action: Link the necessary input port, or disconnect the linked output port.

SEBL_30009 SQL Error <SQL statement>.Cause: Internal error. The Integration Service encountered an error in the listed SQL

statement.


SEBL_30011 application source qualifier <application source qualifier name> has invalid user-defined query <query> with character error at <number> location.

Cause: You entered a query containing characters that are not valid in the application connection code page.

Action: Edit the query so that all characters are valid in the application connection code page.

SEBL_30012 application source qualifier <application source qualifier name> has invalid filter clause <filter> with character error at <number> location.

Cause: A filter condition is entered containing characters that are not valid in the application connection code page.

Action: Edit the filter condition so that all the characters are valid in the application connection code page.

SEBL Codes 113

SEBL_30013 application source qualifier <application source qualifier name> has invalid join and/or filter override <join override> with character error at <number> location.

Cause: You entered a join condition or source filter condition that contain characters that are not valid in the application connection code page.

Action: Edit the join or filter conditions, or both so that all the characters are valid in the application connection code page.

SEBL_30014 application source qualifier <application source qualifier name> has more than one business component attached.

Cause: The listed application source qualifier is associated with or connected to more than one Siebel business component source definition. Associate or connect one business component source definition to a single application source qualifier.

Action: Disconnect one of the business component source definitions from the application source qualifier.

-or-

Remove one of the associated business component source definitions.

-or-

To use more than one business component in a single mapping, create an application source qualifier for each business component you want to use. Use a Joiner transformation to join two related business components.

SEBL_30015 application source qualifier <application source qualifier name> has business component and other sources.

Cause: The listed application source qualifier is connected to a business component source definition and other source definitions. You cannot join a business component with other Siebel sources.

Action: Use a separate application source qualifier for each Siebel source definition.

SEBL_30019 application source qualifier <application source qualifier name> has filter clause which uses one or more fields that were not selected.

Cause: The listed application source qualifier has a filter clause that uses one or more fields not selected from the business component.

Action: In the filter clause, use the fields from the business component.

SEBL_30020 application source qualifier <application source qualifier name> has join override clause which uses one or more fields that were not selected.

Cause: The listed application source qualifier has a join override clause that uses one or more fields not selected from the business component.

Action: In the join override clause, use the fields from the business component.


SEBL_30022 application source qualifier <application source qualifier name> has partitions with key names that use one or more fields that were not selected.

Cause: The listed application source qualifier has partitions with key names that use one or more fields. However, these key names are not selected from the business component.

Action: For key names in partitions, use the fields from the business component.

SEBL_30023 One or more fields used to partition source(s) of application source qualifier <application source qualifier name> have been deleted.

Cause: You defined a partition key for a port in the application source qualifier that you deleted.

Action: Edit the session to remove the partition key from the application source qualifier. Save the partition information in the session and run it again.

SEBL Codes 115

SiebelCT CodesSiebelCT_2003 Failed to invoke business method <Method Name>Cause: An error occurred while invoking a Siebel business service method.

Action: Contact your Siebel administrator for support.

SiebelCT_2004 Mandatory input port <port name> is not connected.Cause: A required input transformation port is not connected in the mapping.

Action: Link the required input port in the mapping.

SiebelCT_2005 Data truncation occurred for the transformation port <port name>.Cause: The precision defined for the transformation port is less than the precision of

the data received.

Action: Redefine the precision of the transformation port to match that of the data received.


SiebelRdr CodesSiebelRdr_1012 Failed to connect to server <siebel server name>. Check the connection

parameters.Cause: This error occurs when a parameter in the application connection is incorrect.

Action: Verify that the parameters you have specified are correct.

SiebelRdr_1020 The Integration Service failed to create the business component <business component name> used by business object <business object name>.

Cause: The business component is inactive.

-or-

The business component and the business object containing the business component are not linked in the repository.


SiebelRdr_1021 Invalid sort filter condition specified for the business component <business component>.

Cause: The sort filter condition is invalid.

Action: Verify that the sort filter condition is valid.

SiebelRdr_1022 Invalid search filter condition specified for the business component <business component name>.

Cause: The search filter condition is invalid.

Action: Verify that the search filter condition is valid.

SiebelRdr_1028 The Integration Service failed to initialize the partition driver.Cause: Internal error.


SiebelRdr_1029 Incorrect value specified in the sort filter condition.Cause: The value specified in the Value field in a sort filter condition is incorrect.

Action: Verify that the value in the Value field is correct.

SiebelRdr_1030 The Integration Service failed to deinitialize partition driver.Cause: Internal error.


SiebelRdr_1031 The Integration Service could not extract data from the business component <business component name>.


SiebelRdr Codes 117


SiebelRdr_1032 The Integration Service failed to set data in PowerCenter buffer.Cause: Internal error.


SiebelRdr_1033 The Integration Service received abort/stop request from the Data Transformation Manager (DTM) process. Terminating session.



SiebelRdr_1034 An error occurred while clearing the search or sort filter applied on a business component <business component name>.



SiebelRdr_1035 The Integration Service failed to retrieve the business component for the multi-valued field <multi-valued field name>.



SiebelRdr_1036 The Integration Service failed to create the business object <business object name>.



SiebelRdr_1037 An error occurred while executing a query on the business component <business component name>.



SiebelRdr_1038 An error occurred while setting the view mode for the business component <business component name>.



SiebelRdr_1040 The Integration Service failed to extract the first row from the business component <business component name>.




SiebelRdr_1041 The Integration Service failed to extract the value of the field <field name> of the business component <business component name>.



SiebelRdr_1042 The Integration Service failed to extract a row after the first row from the business component <business component name>.



SiebelRdr_3000 Failed to find the PowerExchange for Siebel license key.Cause: A valid license key for PowerExchange for Siebel was not found.

Action: Add a valid license key through the PowerCenter Administration console.

SiebelRdr_3008 <Exception>.Cause: An exception occurred when the Integration tried to read data from Siebel.


SiebelRdr_3009 <Error>.Cause: Internal error.


SiebelRdr Codes 119

SiebelWrt CodesSiebelWrt_1000 PowerExchange for Siebel is not enabled on PowerCenter or the license is

expired. Contact Informatica Global Customer Support.Cause: A valid license key for PowerExchange for Siebel was not found.

Action: Add a valid license key through the PowerCenter Administration console. If the problem persists, contact Informatica Global Customer Support.

SiebelWrt_1008 <Exception>Cause: An exception occurred while writing data to Siebel.


SiebelWrt_1009 <Error>Cause: Internal error.


SiebelWrt_1012 Failed to connect to server <Siebel server name>. Reason: <reason>.Cause: This error occurs when a parameter in the application connection is incorrect.

Action: Ensure that the parameters you have specified are correct.

SiebelWrt_1041 Error threshold value <threshold> reached. Terminating data load.Cause: The Integration Service reached the error threshold specified in the session

properties.

Action: Eliminate the errors in your data or increase the error threshold.

SiebelWrt_1054 <Primary key field> cannot be NULL. Cause: The value of a primary key field is NULL.

Action: Specify a non-NULL value for the primary key.

SiebelWrt_1055 <Foreign key field> cannot be NULL.Cause: The value of a foreign key field is NULL.

Action: Specify a non-NULL value for the foreign key field.

SiebelWrt_1060 The Integration Service could not create hierarchy.Cause: Internal error.



A p p e n d i x D

Glossary

This appendix includes the following topic:

♦ Glossary of Terms, 122

121

Glossary of Terms

application object managerA Siebel component that manages all the Siebel objects in a Siebel application. The application object manager also hosts the Business Objects Layer and the Data Objects Layer.

business componentA logical entity that combines columns from base tables, extension tables, and joined tables into a single structure.

calculated expressionA Siebel expression that calculates the value of a field in a business component based on the value of other fields in the business component.

integration objectA logical representation of external application data or Siebel data that corresponds to an external application.

multi-valued fieldA field that can store more than one value at a time.

Siebel business serviceA Siebel object used to implement reusable business logic that can be executed within the Object Manager.

Siebel Business Service transformation A passive transformation that you can use to invoke business service methods. The business service methods transfer or convert data between Siebel applications and external applications.

single-value fieldA field that can store one value at a time.

Siebel Object ModelRepresents Siebel object architecture, which includes a set of object definitions that are grouped into different layers depending on the functionality and characteristics of objects.

122 Appendix D: Glossary

I n d e x

Aapplication connection

configuring for PowerExchange for Siebel 86application object manager

viewing for Siebel 5Application Source Qualifier

configuring, ODBC sources 99creating, ODBC sources 99

C Siebel calculated expressions

See Siebel calculated expressionscalculated fields

Siebel sources 33components

Siebel Business Service transformation 63configuring

update strategy 52connection attributes

password 86user name 86

custom joinsjoining source data 98

Ddatatypes

PowerExchange for Siebel 104Siebel 3

default querydescription 97

Eerror messages

Integration Service 113PowerCenter Designer 108PowerExchange for Siebel client 108SEBL codes 113

Expression transformationconfiguring 79

Ffilters

Siebel sources, Java Data Bean API 34Siebel sources, ODBC 94

Ggroups

Siebel Business Service transformation 64

123

Iimporting

business component, Java Data Bean API 36installing

PowerExchange for Siebel 14Integration Service

error messages 113

JJava components

See also PowerCenter Administrator Guideconfiguring for Siebel 18

joinscustom 98default 98

Kkey relationship

generating 51key values

generating, Siebel sources 30keys

See also PowerCenter Transformation Guidecreating for joins 98joining multiple foreign keys 98

LLookup transformation

See also PowerCenter Transformation Guideusing 98

Mmapping examples

Siebel Business Service transformation 65mapplet for Siebel calculated fields

creating 83mapplets

creating 82multi-value fields

Siebel sources 27Siebel targets 49

OODBC

importing sources 97ODBC sources

Application Source Qualifier, configuring 99Application Source Qualifier, creating 99creating key relationships, tables 98filtering 94

outer joinSee also PowerCenter Transformation Guideoverview 98

Ppassive transformation

Siebel Business Service 122plug-ins

See also PowerCenter Administrator GuideSee also PowerCenter Command Line Referenceregistering PowerExchange for Siebel 17updating the registration 17

PowerExchange for Siebel clienterror messages 108

prerequisitesPowerExchange for Siebel 12

Ssearch specification

property 92Siebel

calculated expressions 78, 82cleaning the environment 22datatypes 3Lookup expression 76, 79

Siebel API librariesregistering for PowerExchange for Siebel 19

Siebel architectureSiebel Enterprise Applications 3

Siebel base tabledescription 9

Siebel business componentsimporting 9

Siebel Business Service transformationcomponents 63creating 70groups 64mapping example 65working with 61

124 Index

Siebel calculated expressionsIfNull 78IIf 78Lookup 78LookupExpr 78LookupValue 78mapplets 82nested expression 76, 79Timestamp 78Today 78

Siebel default queryoverview 97

Siebel Enterprise ApplicationsSiebel architecture 3

Siebel fieldcalculated expressions 74description 9

Siebel mappingsconnecting sources 99

Siebel mappletsExpression transformation 78Input transformation 77Lookup Transformation 80

Siebel Object Modelillustration 5

Siebel securityoverview 3

Siebel source definitionsconnecting in a mapping 99creating 55editing 38importing 9overview 2, 12, 26reimporting 38

Siebel source filtersdescription, importing through ODBC 97tables during import 94

Siebel tablesimporting sources 10

Siebel target definitionsediting 58importing 55reimporting 58troubleshooting 59working with 49

sort filter, session-level 43sort specification

property 93sorted ports

description 97

source filter, session-levelworking with 41

Ttables

creating key relationships, ODBC sources 98transformation groups

Siebel Business Service transformation 64transformations

Expression 78Lookup 80mapplets 77

Uuninstalling

PowerExchange for Siebel 22Siebel, cleaning 22

update strategyconfiguring 52

upgradingPowerExchange for Siebel pre-upgrade tasks 13PowerExchange for Siebel upgrade tasks 13

Vview mode

working with 44

125 Index

126 Index

NOTICESThis Informatica product (the “Software”) includes certain drivers (the “DataDirect Drivers”) from DataDirect Technologies, an operating company of Progress Software Corporation (“DataDirect”) which are subject to the following terms and conditions:

1. THE DATADIRECT DRIVERS ARE PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.

powerexchange for siebel user guide documentation/1/pwx_… · siebel enterprise applications is an...

Documents