powercenter connect for tibco 8.1.1 user guide documentation/1/pcco… · powercenter connect for...

User Guide

Informatica PowerCenter Connect

for TIBCO

(Version 8.1.1)

Informatica PowerCenter Connect for TIBCO User GuideVersion 8.1.1September 2006

Copyright © 2002-2006 Informatica Corporation.All rights reserved. Printed in the USA.

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.

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 document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Informatica Corporation does not warrant that this documentation is error free.

Informatica, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerMart, SuperGlue, Metadata Manager, Informatica Data Quality and Informatica Data Explorer 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.

Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies, 1999-2002. All rights reserved. Copyright © Sun Microsystems. All Rights Reserved. Copyright © RSA Security Inc. All Rights Reserved. Copyright © Ordinal Technology Corp. All Rights Reserved.

Informatica PowerCenter products contain ACE (TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University and University of California, Irvine, Copyright (c) 1993-2002, all rights reserved.

Portions of this software contain copyrighted material from The JBoss Group, LLC. Your right to use such materials is set forth in the GNU Lesser General Public License Agreement, which may be found at http://www.opensource.org/licenses/lgpl-license.php. The JBoss materials are provided free of charge by Informatica, “as-is”, without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose.

Portions of this software contain copyrighted material from Meta Integration Technology, Inc. Meta Integration® is a registered trademark of Meta Integration Technology, Inc.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/). The Apache Software is Copyright (c) 1999-2005 The Apache Software Foundation. All rights reserved.

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit and redistribution of this software is subject to terms available at http://www.openssl.org. Copyright 1998-2003 The OpenSSL Project. All Rights Reserved.

The zlib library included with this software is Copyright (c) 1995-2003 Jean-loup Gailly and Mark Adler.

The Curl license provided with this Software is Copyright 1996-2004, Daniel Stenberg, <[email protected]>. All Rights Reserved.

The PCRE library included with this software is Copyright (c) 1997-2001 University of Cambridge Regular expression support is provided by the PCRE library package, which is open source software, written by Philip Hazel. The source for this library may be found at ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre.

InstallAnywhere is Copyright 2005 Zero G Software, Inc. All Rights Reserved.

Portions of the Software are Copyright (c) 1998-2005 The OpenLDAP Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted only as authorized by the OpenLDAP Public License, available at http://www.openldap.org/software/release/license.html.

This Software may be protected by U.S. and international Patents and Patents Pending.

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. The information provided in this documentation may include technical inaccuracies or typographical errors. Informatica could make improvements and/or changes in the products described in this documentation at any time without notice.

Table of Contents

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

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

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Other Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Visiting Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Visiting the Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Visiting the Informatica Developer Network . . . . . . . . . . . . . . . . . . . . xiii

Visiting the Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . xiii

Obtaining Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Chapter 1: Understanding PowerCenter Connect for TIBCO . . . . . . . . 1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

PowerCenter and TIBCO Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

PowerCenter Designer Integration with TIB/Repository . . . . . . . . . . . . . . 3

Integration Service and TIBCO Integration . . . . . . . . . . . . . . . . . . . . . . . 6

Understanding Secure Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2: Configuring PowerCenter Connect for TIBCO . . . . . . . . . . 9

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Step 1. Set the Path to TIBCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Setting the Path to TIBCO on Windows . . . . . . . . . . . . . . . . . . . . . . . . 12

Setting the Path to TIBCO on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Step 2. Rename PowerCenter Connect for TIBCO Libraries . . . . . . . . . . . . . 13

Renaming PowerCenter Connect for TIBCO Libraries on Windows . . . . 13

Renaming PowerCenter Connect for TIBCO Libraries on Solaris . . . . . . 13

Renaming PowerCenter Connect for TIBCO Libraries on HP-UX . . . . . 13

Step 3. Install the infaMetadata Adapter Instance . . . . . . . . . . . . . . . . . . . . . 14

Table of Contents iii

Chapter 3: TIBCO Source and Target Concepts . . . . . . . . . . . . . . . . . 17

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Source and Target Metadata Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Source and Target Definitions Based on TIB/Repository Metadata . . . . . 19

TIBCO Metadata Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Nested Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Source and Target Definitions with Separate Columns for Nested Message Data Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Source and Target Definitions with Collapsed Nested Messages . . . . . . . . 24

Chapter 4: Working with TIBCO Sources . . . . . . . . . . . . . . . . . . . . . . 25

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Importing a TIBCO Source Definition from TIB/Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Creating a TIBCO Source Definition Manually . . . . . . . . . . . . . . . . . . . . . . 31

Editing a TIBCO Source Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Working with the TIBCO Source Group . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Editing the TIBCO Metadata Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Editing the TIBCO Source Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Creating the Application Multi-Group Source Qualifier . . . . . . . . . . . . . . . . 40

Transformation Datatypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Creating the Application Multi-Group Source Qualifier Transformation . 40

Chapter 5: Working with TIBCO Targets . . . . . . . . . . . . . . . . . . . . . . . 41

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Specifying SendSubject in a TIBCO Target Definition . . . . . . . . . . . . . . 42

Defining a Target from a TIBCO Source Definition . . . . . . . . . . . . . . . . . . . 43

Defining a TIBCO Target from a Relational or Flat File Source Definition . . 44

Importing a TIBCO Target Definition from TIB/Repository . . . . . . . . . . . . . 47

Creating a TIBCO Target Definition Manually . . . . . . . . . . . . . . . . . . . . . . 50

Editing a TIBCO Target Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Working with the TIBCO Target Group . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Editing the TIBCO Metadata Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Editing the TIBCO Target Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Chapter 6: Creating and Configuring TIBCO Workflows . . . . . . . . . .57

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

iv Table of Contents

Working with TIBCO Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

TIBCO Event Queue Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Configuring Session Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Configuring Certified Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Message Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Pipeline Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Configuring a Session with a TIBCO Mapping . . . . . . . . . . . . . . . . . . . . . . 68

Scheduling Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Running Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Appendix A: TIBCO Datatype Reference . . . . . . . . . . . . . . . . . . . . . . 77

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

TIBCO and Transformation Datatypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

TIB/Rendezvous Datatypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

TIB/Adapter SDK Datatypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Table of Contents v

vi Table of Contents

List of Figures

Figure 1-1. PowerCenter and TIBCO Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Figure 1-2. PowerCenter Designer and TIB/Repository Integration . . . . . . . . . . . . . . . . . . . . . 4

Figure 1-3. TIB/Repository Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Figure 1-4. Integration Service and TIBCO Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Figure 2-1. Import TIBCO Metadata Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Figure 3-1. TIBCO Source and Target Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Figure 3-2. TIB/Repository Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Figure 3-3. Target Definition Based on a TIB/Repository Instance . . . . . . . . . . . . . . . . . . . . . 20

Figure 3-4. TIBCO Metadata Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Figure 3-5. TIBCO Target Definition Map Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Figure 3-6. Source Definition with Separate Columns for Nested Message Data Fields . . . . . . 23

Figure 3-7. TIBCO Source Definition with a Collapsed Nested Message . . . . . . . . . . . . . . . . 24

Figure 4-1. TIBCO Source Definition and Application Multi-Group Source Qualifier . . . . . . 40

Figure 5-1. TIBCO Target Definition Created from a TIBCO Source Definition . . . . . . . . . . 43

Figure 5-2. TIBCO Target Definition Created from a Flat File Source Definition . . . . . . . . . . 43

Figure 5-3. TIBCO Target Definition Created from a Flat File Source Definition . . . . . . . . . . 44

Figure 5-4. TIBCO Target Definition with Nested Message Data Fields . . . . . . . . . . . . . . . . . 45

Figure 6-1. Session Conditions in the Session Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Figure 6-2. TIBCO Application Connection Configured for Certified Messages . . . . . . . . . . . 64

Figure 6-3. Target Properties for Writing Certified Messages . . . . . . . . . . . . . . . . . . . . . . . . . 66

List of Figures vii

viii List of Figures

List of Tables

Table 1-1. TIBCO Message Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Table 2-1. TIBCO ActiveEnterprise Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Table 6-1. TIBCO Event Queue Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Table 6-2. Partition Types for Partition Points in TIBCO Mappings. . . . . . . . . . . . . . . . . . . . 67

Table A-1. TIB/Rendezvous and Transformation Datatypes . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Table A-2. TIB/Adapter SDK and Transformation Datatypes . . . . . . . . . . . . . . . . . . . . . . . . . 81

List of Tables ix

x List of Tables

Preface

Welcome to PowerCenter Connect, Informatica’s family of packaged software products that helps you extract data and metadata from ERP and other third-party applications.

PowerCenter Connect for TIBCO is a natural extension to PowerCenter’s open architecture, which supports data extraction from a wide variety of operational data sources. PowerCenter Connect for TIBCO lets you directly extract data from TIBCO messages, transform the data according to your business rules, and load data into TIBCO messages or data warehouses.

xi

About This Book

The Informatica PowerCenter Connect for TIBCO User Guide provides information to build TIBCO mappings, extract data from webMethods messages, and load data into TIBCO messages. It is written for the database administrators and developers who are responsible for extracting data from TIBCO messages and loading data into TIBCO messages.

This book assumes you have knowledge of relational database concepts and database engines, PowerCenter, and TIBCO. You must also be familiar with the interface requirements for other supporting applications. For additional information about related TIBCO issues, refer to the TIBCO documentation.

The material in this book is also available online.

Document Conventions

This guide uses the following formatting conventions:

If you see… It means…

italicized text The word or set of words are especially emphasized.

boldfaced text Emphasized subjects.

italicized monospaced text This is the variable name for a value you enter as part of an

operating system command. This is generic text that should be

replaced with user-supplied values.

Note: The following paragraph provides additional facts.

Tip: The following paragraph provides suggested uses.

Warning: The following paragraph notes situations where you can overwrite

or corrupt data, unless you follow the specified procedure.

monospaced text This is a code example.

bold monospaced text This is an operating system command you enter from a prompt to

run a task.

xii Preface

Other Informatica Resources

In addition to the product manuals, Informatica provides these other resources:

♦ Informatica Customer Portal

♦ Informatica web site

♦ Informatica Developer Network

♦ Informatica Knowledge Base

♦ Informatica Technical Support

Visiting Informatica Customer Portal

As 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.

Visiting the Informatica Web Site

You 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.

Visiting the Informatica Developer Network

You can access the Informatica Developer Network at http://devnet.informatica.com. The Informatica Developer Network is a web-based forum for third-party software developers. The site contains information about how to create, market, and support customer-oriented add-on solutions based on interoperability interfaces for Informatica products.

Visiting the Informatica Knowledge Base

As 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.

Obtaining Technical Support

There are many ways to access Informatica Technical Support. You can contact a Technical Support Center by using the telephone numbers listed the following table, you can send email, or you can use the WebSupport Service.

Preface xiii

Use the following email addresses to contact Informatica Technical 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.

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

Informatica Corporation Headquarters

100 Cardinal Way

Redwood City, California

94063

United States

Toll Free

877 463 2435

Standard Rate

United States: 650 385 5800

Informatica Software Ltd.

6 Waltham Park

Waltham Road, White Waltham

Maidenhead, Berkshire

SL6 3TN

United Kingdom

Toll Free

00 800 4632 4357

Standard Rate

Belgium: +32 15 281 702

France: +33 1 41 38 92 26

Germany: +49 1805 702 702

Netherlands: +31 306 022 797

United Kingdom: +44 1628 511 445

Informatica Business Solutions Pvt. Ltd.

Diamond District

Tower B, 3rd Floor

150 Airport Road

Bangalore 560 008

India

Toll Free

Australia: 00 11 800 4632 4357

Singapore: 001 800 4632 4357

Standard Rate

India: +91 80 4112 5738

xiv Preface

C h a p t e r 1

Understanding PowerCenter

Connect for TIBCO

This chapter includes the following topics:

♦ Overview, 2

♦ PowerCenter and TIBCO Integration, 3

♦ Understanding Secure Connections, 7

1

Overview

PowerCenter Connect for TIBCO integrates with components of TIBCO ActiveEnterprise to extract data from TIBCO sources and write data to TIBCO targets. With PowerCenter Connect for TIBCO, you can define TIBCO sources and targets in the PowerCenter Designer by importing message metadata from a TIB/Repository instance. Use the TIBCO source and target definitions in a mapping to read messages from TIBCO sources and write messages to TIBCO targets.

The Integration Service can read and write TIBCO messages in TIB/Rendezvous or AE format during a PowerCenter workflow. When the Integration Service reads TIBCO source messages, it receives messages with a particular message subject from a TIBCO daemon. When the Integration Service writes TIBCO target messages, it writes the messages through a TIBCO daemon. The Integration Service writes the TIBCO target messages with the message subject as the address. The TIBCO daemon transmits the messages across a local or wide area network. Target listeners subscribe to TIBCO target messages based on the message subject.

With PowerCenter Connect for TIBCO, the Integration Service can read and write certified TIBCO messages. When you run a workflow to read certified messages from TIBCO sources, the Integration Service sends confirmation to the TIBCO source for each certified message it receives. If the PowerCenter session aborts or fails and then restarts, the Integration Service can still receive certified messages that the TIBCO daemon sent while the session was stopped for a certain time period. When you run a workflow to write certified messages to TIBCO targets, the Integration Service expects confirmation from the TIBCO targets for each certified message it sends. If the Integration Service does not receive confirmation from the TIBCO targets, the TIBCO daemon can resend the certified message for a specified period of time or until it receives confirmation.

This chapter provides an overview of the integration of PowerCenter and TIBCO. For more information about TIBCO, see the TIBCO documentation.

2 Chapter 1: Understanding PowerCenter Connect for TIBCO

PowerCenter and TIBCO Integration

PowerCenter Connect for TIBCO lets you read messages from TIBCO and write messages to TIBCO in TIB/Rendezvous or AE format. To read and write messages in TIB/Rendezvous and AE format, create mappings with TIBCO source and target definitions. Use the PowerCenter Designer to define the metadata for TIBCO sources and targets. You can also use the PowerCenter Designer to connect to a TIB/Repository instance to import source and target metadata. When you run a workflow, the Integration Service connects to the TIBCO daemon to read and write TIBCO messages.

Figure 1-1 shows PowerCenter integration with TIBCO to create TIBCO mappings and run TIBCO workflows:

PowerCenter Designer Integration with TIB/Repository

The PowerCenter Designer connects to a TIB/Repository instance to import metadata for TIBCO source and target definitions. Before you connect to a TIB/Repository instance through the PowerCenter Designer, you install an adapter instance in TIB/Designer.

TIB/Designer is a graphical user interface that lets you define an adapter instance. You use the adapter instance to start a TIB/Repository session to access a TIB/Repository instance. Each adapter instance lets you connect to one TIB/Repository instance.

When you want to connect to a TIB/Repository instance to import TIBCO source or target metadata, you specify an adapter instance in the PowerCenter Designer. The adapter instance starts a TIB/Repository session. During the TIB/Repository session, the PowerCenter Designer accesses a TIB/Repository instance to import TIBCO source or target metadata.

Figure 1-1. PowerCenter and TIBCO Integration

Designer

Integration

Service

PowerCenter

TIB/Repository TIB/Repository stores metadata for TIBCO

messages.

The PowerCenter Designer defines TIBCO

mappings. It can connect to TIB/Repository to

fetch metadata for TIBCO source and target

definitions.

The TIBCO daemon broadcasts TIBCO messages

to the network and retrieves TIBCO messages

from the network.

The Integration Service reads and writes TIBCO

messages during a PowerCenter workflow.

TIBCO Daemon

PowerCenter and TIBCO Integration 3

Figure 1-2 shows how the PowerCenter Designer imports metadata from a TIB/Repository instance to define TIBCO sources and targets:

To import TIBCO metadata from a TIB/Repository instance, you can connect to the TIB/Repository instance from the PowerCenter Designer with a user-defined adapter instance. Or, you can connect to the TIB/Repository instance with an adapter instance that Informatica provides with PowerCenter Connect for TIBCO. For more information about the infaMetadata adapter instance, see “Step 3. Install the infaMetadata Adapter Instance” on page 14.

TIBCO Messages

TIBCO messages are hierarchically structured messages that consist of message header fields and message data fields. TIB/Rendezvous messages have up to five header fields and any number of data fields. AE messages have up to four header fields and any number of data fields. Header fields contain the message address and information to deliver certified messages. Data fields contain message data.

Table 1-1 shows the message fields of a TIBCO message:

Figure 1-2. PowerCenter Designer and TIB/Repository Integration

Table 1-1. TIBCO Message Fields

Message FieldHeader/ Body

Description

Send Subject Header Address of the message.

Reply Subject Header Optional return address for identifying the message sender.

Time Limit Header Time period during which certified messages can be retained for delivery. Only TIB/Rendezvous messages can contain a Time Limit header field.

Sender Name Header Name of the transport used for delivering certified messages.

Sequence Number Header Sequence number of the certified message.

Data Fields Body Contain the message data. Data fields can also contain nested messages.

The PowerCenter Designer uses an adapter

instance to start a TIB/Repository session with

a TIB/Repository instance to import source and

target metadata.

TIBCO source and targets definitions represent

metadata for TIBCO messages.

TIB/Repository

TIBCO

Source

Definition

TIBCO

Target

Definition

PowerCenter Designer

Adapter Instance


Data fields can contain nested messages. Nested messages are TIBCO messages embedded in the data fields of another TIBCO message. Nested messages consist only of data fields. They do not have their own address or certified message delivery information. A message can have an unlimited number of nested messages.

The following example shows a TIBCO message:

[2001-08-08 15:37:47]: subject=cm.nt1, message={NESTED1={PRICE=70.000000 WHOLESALE_COST=30.000000} NESTED2={ITEM_ID=5378.000000 ITEM_NAME=Divers Knife and Sheath} ITEM_DESC=Tools}

Subject is a header field. NESTED1, NESTED2, and ITEM_DESC are data fields. The data fields NESTED1 and NESTED2 are nested messages. PRICE and WHOLESALE_COST are the nested message data fields in NESTED1. ITEM_ID and ITEM_NAME are the nested message data fields in NESTED2.

TIB/Repository

TIB/Repository is a hierarchical repository that stores metadata for TIBCO message data fields in repository instances. A single TIB/Repository can have many repository instances. Repository instances store TIBCO message metadata as classes. Each class contains a set of attributes that define data fields in a TIBCO message. The attributes contain name and datatype information for the data fields in a TIBCO message.

TIB/Repository can also store metadata for nested messages. When a TIB/Repository instance contains a nested message, it stores the nested message as an attribute of a class in the hierarchy. The attribute receives the datatype CLASS. The nested message is also a class.

Figure 1-3 shows the structure of a TIB/Repository instance:

When the PowerCenter Designer imports class metadata from a TIB/Repository instance to define TIBCO sources and targets, it imports the class metadata as a group. It uses the class name as the name of the group. The PowerCenter Designer imports the data fields in the class

Figure 1-3. TIB/Repository Instance

Class Representing Nested

Message Metadata

Classes

Attributes Datatypes

Nested Message

Nested Message

Attribute & Datatype

PowerCenter and TIBCO Integration 5

as columns in the source and target definitions. If the class contains metadata for a nested message, the PowerCenter Designer also imports the nested message metadata.

For example, the PowerCenter Designer imports the class ORDER, which contains the nested message PRICE. When the PowerCenter Designer imports PRICE, it also imports the metadata for the nested message fields in the class PRICE.

For more information about importing TIBCO source and target definitions, see “Source and Target Definitions Based on TIB/Repository Metadata” on page 19.

Integration Service and TIBCO Integration

During a workflow, the Integration Service connects to a TIBCO daemon to read source messages or write target messages in TIB/Rendezvous or AE format. When the Integration Service reads or writes TIBCO messages, it connects to the TIBCO daemon through TIB/Rendezvous. When the Integration Service reads or writes messages in AE format, it connects to the TIBCO daemon through TIB/Adapter SDK.

Figure 1-4 shows how PowerCenter connects to TIBCO during a session to read and write messages:

When you configure a PowerCenter workflow to read messages from a TIBCO daemon or write messages through a TIBCO daemon, use a TIBCO application connection to connect to the TIBCO daemon. Specify a subject for the source and target messages in the TIBCO application connection attributes. The Integration Service reads source messages that contain the subject in the TIBCO application connection. It also sends target messages with the subject in the TIBCO application connection. For more information about entering a TIBCO daemon and a subject in a TIBCO application connection, see “Managing Connection Objects” in the PowerCenter Workflow Administration Guide.

Figure 1-4. Integration Service and TIBCO Integration

The Integration Service reads and writes TIBCO

messages based on workflow and TIBCO

application connection configurations.

The Integration Service connects to the TIBCO

daemon through TIB/Rendezvous to read and

write TIBCO messages.

The Integration Service connects to the TIBCO

daemon through TIB/Adapter SDK to read and

write AE messages.

WorkflowTIBCO

Application

Connection

Workflow Manager

TIBCO Session

Integration Service

TIB/Rendezvous TIB/Adapter SDK

TIBCO Daemon


Understanding Secure Connections

The Integration Service can read TIBCO Rendezvous messages from a secure daemon and write TIBCO Rendezvous messages to a secure daemon during a session. TIBCO Rendezvous uses Secure Sockets Layer to enable secure client communication over non-secure networks.

TIBCO Rendezvous supports two secure daemons:

♦ rvsd. The TIBCO Rendezvous secure communications daemon. It is the background process that supports all Rendezvous communications. The daemon process starts automatically when needed, runs continuously, and might exit after a period of inactivity.

♦ rvsrd. The TIBCO Rendezvous secure routing daemon. It delivers messages to programs on computers within a single network.

TIBCO Rendezvous supports two modes of communication through its secure daemons:

♦ Non-secure TCP connections

♦ SSL Connections, allowing secure client communication over non-secure networks

Each secure daemon instance authorizes a set of trusted users. The secure daemon allows a client transport to connect, only if the client presents valid identification as an authorized user.

For more information about secure daemons, see the TIBCO Rendezvous documentation. You can configure a TIB/Rendezvous application connection to enable SSL for TIB/Rendezvous application connection. For information, see “Managing Connection Objects” in the PowerCenter Workflow Administration Guide.

Understanding Secure Connections 7

C h a p t e r 2

Configuring PowerCenter

Connect for TIBCO


♦ Overview, 10

♦ Step 1. Set the Path to TIBCO, 12

♦ Step 2. Rename PowerCenter Connect for TIBCO Libraries, 13

♦ Step 3. Install the infaMetadata Adapter Instance, 14

9

Overview

PowerCenter Connect for TIBCO requires configuration on the Integration Service and PowerCenter Client. You must also install and configure components of TIBCO ActiveEnterprise. The administrators for each of these systems should perform the installation and configuration tasks for their respective systems.

To configure PowerCenter Connect for TIBCO, complete the following steps:

1. Set the path to the TIBCO installation directory. For more information, see “Step 1. Set the Path to TIBCO” on page 12.

2. Rename PowerCenter Connect for TIBCO libraries. For more information, see “Step 2. Rename PowerCenter Connect for TIBCO Libraries” on page 13.

3. Install the infaMetadata adapter instance (optional). When you want to import TIBCO source and target metadata from a TIB/Repository instance, install an adapter instance for the TIB/Repository instance through TIB/Designer. For more information, see “Step 3. Install the infaMetadata Adapter Instance” on page 14.

Before You Begin

Before configuring PowerCenter Connect for TIBCO, install PowerCenter. You must also install and configure components of TIBCO ActiveEnterprise.

Table 2-1 describes the TIBCO ActiveEnterprise products you must install and configure:

Table 2-1. TIBCO ActiveEnterprise Products

TIBCO

ActiveEnterprise

Product

Required/ Optional

Description

TIB/Rendezvous Required Install and configure TIB/Rendezvous on the machine running the Integration

Service. To import TIBCO source and target definitions from a TIB/Repository

instance, you must also install and configure TIB/Rendezvous on the machine

hosting the PowerCenter Client.

TIB/Adapter SDK Optional Install and configure TIB/Adapter SDK on the machine hosting the PowerCenter

Client to import TIBCO source and target definitions from a TIB/Repository

instance.

To read source messages and write target messages in AE format, you must

also install and configure TIB/Adapter SDK on the machine hosting the

PowerCenter Client.

10 Chapter 2: Configuring PowerCenter Connect for TIBCO

For more information about installing and configuring TIBCO ActiveEnterprise products, see the TIBCO documentation.

TIB/Repository Optional Install and configure TIB/Repository in the same local area network as the

machine hosting the PowerCenter Client to import TIBCO source and target

definitions from a TIB/Repository instance.

TIB/Designer Optional Install and configure TIB/Designer on the machine hosting the PowerCenter

Client to import TIBCO source and target definitions from a TIB/Repository

instance with the infaMetadata adapter instance.

If you want to import TIBCO source and target definitions from a TIB/Repository

instance with a user-defined adapter instance, you can install TIB/Designer on

any machine to define the adapter instance.

Table 2-1. TIBCO ActiveEnterprise Products

TIBCO

ActiveEnterprise

Product

Required/ Optional

Description

Overview 11

Step 1. Set the Path to TIBCO

Set the path to the TIBCO installation directory on the machine running the Integration Service.

Setting the Path to TIBCO on Windows

Set the path to the following TIBCO directories from the Control Panel or the command line:

♦ <TIBCO_HOME>\tra\5.2\bin

♦ <TIBCO_HOME>\tpcl\5.2\bin

♦ <TIBCO_HOME>\tibrv\bin

For example, to set the path to <TIBCO_HOME>\tra\5.2\bin, enter the following text:

;d:\<TIBCO>\tra\5.2\bin

Setting the Path to TIBCO on UNIX

Set the path to the following TIBCO directories on UNIX:

♦ <TIBCO_HOME>/tra/5.2/lib

♦ <TIBCO_HOME>/tpcl/5.2/lib

♦ <TIBCO_HOME>/tibrv/lib

Add the directories to the library path based on the operating system.

Use the following guidelines for a UNIX shell:

For example:

setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$TIBCO/tibrv/lib

Operating System Path Variable

Solaris LD_LIBRARY_PATH

HP-UX SHLIB_PATH

UNIX Shell Description

C shell setenv <path> $<path>:$<TIBCO directory>

Bourne shell <path>=$<path>:$<TIBCO directory>; export <path>


Step 2. Rename PowerCenter Connect for TIBCO

Libraries

Rename PowerCenter Connect for TIBCO libraries on the machine running the Integration Service and the machine hosting the PowerCenter Client.

Renaming PowerCenter Connect for TIBCO Libraries on Windows

In the <Informatica>\client\bin directory, rename the following library:

In the <Informatica>\server\bin directory, rename the following library:

Renaming PowerCenter Connect for TIBCO Libraries on Solaris

In the <Informatica>/server/bin directory, rename the following libraries:

Renaming PowerCenter Connect for TIBCO Libraries on HP-UX

In the <Informatica>/server/bin directory, rename the following libraries:

Library Name Rename to...

pmtibsdkad520.dll pmtibsdkad.dll


pmtibsdkdrv520.dll pmtibsdkdrv.dll


pmtibsdkhelper520.so pmtibsdkhelper.so

libpmtibsdkdrv520.so libpmtibsdkdrv.so


pmtibsdkhelper520.sl pmtibsdkhelper.sl

libpmtibsdkdrv520.sl libpmtibsdkdrv.sl

Step 2. Rename PowerCenter Connect for TIBCO Libraries 13

Step 3. Install the infaMetadata Adapter Instance

When you want to import TIBCO source and target metadata from a TIB/Repository instance, and you do not have a user-defined adapter instance, install the infaMetadata adapter instance in TIB/Designer.

Note: If you want to define TIBCO sources manually, you can skip this step. Also, if you want to define TIBCO targets manually or based on other source definitions, you can skip this step.

The infaMetadata adapter instance is the infaMetadataImport.xml file. When you install PowerCenter Connect for TIBCO, the infaMetadataImport.xml file installs in the PowerCenter Connect for TIBCO Client directory. Install the adapter instance for each TIB/Repository instance from which you want to import TIBCO source and target metadata in the PowerCenter Designer.

The default name of the infaMetadata adapter instance is infaMetadataAdapter/infaMetadataInstance/infaMetadata. The default load URL is /tibco/public/class/ae. When you install the adapter instance in TIB/Designer, you must manually define the default load URL.

Once you install the adapter instance, you can change the default load URL name. For example, you can rename the adapter instance to infaMetadataAdapter. You can also add other URLs to allow PowerCenter to search for repository classes in other locations. For example, if you want PowerCenter to also search for repository classes under the directory /tibco/public/class/ae/test, you can add this URL to Load Metadata URL.

Note: When you install the infaMetadata adapter instance, you should not configure TIB/Repository sessions for the adapter instance in TIB/Designer. If you configure TIB/Repository sessions for the infaMetadata adapter instance, the PowerCenter Designer may not be able to connect to a TIB/Repository instance to import source or target metadata.

When you use the TIBCO adapter instance to connect to a TIB/Repository instance to import TIBCO source or target metadata, the infaMetadata adapter instance name appears in the Application Name field in the Import TIBCO Metadata dialog box. Also, the configuration URL for the adapter instance appears in the Configuration URL field in the Import TIBCO Metadata dialog box.


Figure 2-1 shows the Import TIBCO Metadata dialog box:

To install the infaMetadata adapter instance in TIB/Designer:

1. Open an existing project in TIB/Designer.

2. Select the repository instance in which you want to install the infaMetadata adapter instance.

3. Click Project > Import Resources from File, Folder, URL.

The Import Resource or File dialog box appears.

4. From the Format list, select Repository XML or Adapter AEXML.

5. Click Browse to locate infaMetadataImport.xml in the PowerCenter Client\samples directory and click Open.

6. Click OK.

7. After TIB/Designer installs the infaMetadata adapter instance, click OK.

8. Expand the infaMetadataAdapterInstance folder, and drill down to Advanced > Metadata URLs.

9. Click Resources > Add Resource > Adapter Resources > Load URL.

10. On the Configuration tab, click Browse Resources.

11. Expand a project, and drill down to AESchemas > ae, and click OK.

Figure 2-1. Import TIBCO Metadata Dialog Box

Application Name:

Name of the adapter

instance

Configuration URL

Step 3. Install the infaMetadata Adapter Instance 15

12. After you install the infaMetadata adapter instance and add the load URL, optionally modify the adapter instance name.

13. Optionally, add URLs to the Load URL field.

14. Repeat steps 2 to 13 for each repository instance you want to import TIBCO source and target metadata from.


C h a p t e r 3

TIBCO Source and Target

Concepts


♦ Overview, 18

♦ Source and Target Metadata Hierarchy, 19

♦ Nested Messages, 23

17

Overview

TIBCO source and target definitions represent metadata for TIBCO messages. When the Integration Service extracts messages from a TIBCO source during a workflow, it reads messages based on the message format defined in the source definition. When the Integration Service writes messages to a TIBCO target during a workflow, it writes messages based on the message format defined in the target definition.

Similar to the structure of TIBCO messages, the metadata in TIBCO source and target definitions is hierarchically structured. The highest node of the hierarchy in a source or target definition is a group. The columns in the source and target definitions belong to the group. TIBCO source and target definitions can represent metadata for nested messages. Nested message metadata appears as part of the group in the source or target definition.

The PowerCenter Designer represents the hierarchical group format of TIBCO source and target definitions in a TIBCO metadata tree. The PowerCenter Designer defines a metadata tree for each TIBCO source and target definition.

18 Chapter 3: TIBCO Source and Target Concepts

Source and Target Metadata Hierarchy

TIBCO source and target definitions represent metadata in a group. The group contains the message metadata for TIBCO messages, which appears as columns in the source or target definition. The group can contain metadata for messages data fields. It can also contain nested message metadata and message header metadata. Each source and target definition contains one group.

Figure 3-1 shows an example of a TIBCO source and target definition:

In this example, PRICE is the name of the group in the source and target definitions. The source and target represent metadata for a TIBCO message with one header field, SendSubject, and three data fields, PRICE, WHOLESALE_COST, and SALE_PRICE. It also represents metadata for a nested message with the data fields ITEM_ID, ITEM_NAME, and ITEM_DESC.

Note: You can determine which fields in a TIBCO source or target definition are nested messages by viewing the TIBCO metadata tree or map value for the source or target definition. For more information about TIBCO metadata trees and map values, see “TIBCO Metadata Tree” on page 21.

When you use the PRICE source and target definitions in a mapping and run a workflow, the Integration Service reads messages in the format of the group PRICE and writes messages in the format of the group PRICE. For example, the following TIBCO message contains the hierarchical format defined in the source and target definitions in Figure 3-1:

[2002-20-03 12:22:45]: subject=cm.nt1, message={PRICE=70.000000 WHOLESALE_COST=30.000000 SALE_PRICE=60.000000 ITEM={ITEM_ID=5378.000000 ITEM_NAME=Divers Knife and Sheath ITEM_DESC=Tools}}

Source and Target Definitions Based on TIB/Repository Metadata

The PowerCenter Designer can create a TIBCO source or target definition based on metadata from a TIB/Repository instance. When a source or target definition is based on TIB/Repository metadata, it represents class and attribute metadata from the TIB/Repository instance. The imported class becomes the group in the source or target definition. The class

Figure 3-1. TIBCO Source and Target Definitions

Group Name Group Name

Message

Header Field

Metadata Message Data

Field Metadata

TIBCO Target DefinitionTIBCO Source Definition

Source and Target Metadata Hierarchy 19

name becomes the name of the group. The attributes of the class become columns in the source or target definition. Their datatype in the TIB/Repository instance remains their datatype in the source or target definition. When an attribute is also a class representing nested message metadata, it appears in the source or target definition as a subgroup of the class to which it belongs in the TIB/Repository instance.

Figure 3-2 shows an example of a TIB/Repository instance:

For more information about classes, attributes, and datatypes in a TIB/Repository instance, see “TIB/Repository” on page 5.

Figure 3-3 shows a target definition based on the TIB/Repository instance in Figure 3-2:

In this example, ORDERS is the name of the group in the target definition. It derives from the name of the class ORDERS in the TIB/Repository instance. The attributes ITEM_ID and ITEM_DESC from the class ORDERS appear as columns in the target definition. The attribute PRICE is also a class and thereby a nested message. The attributes from the class PRICE appear as columns in the source definition. The class PRICE may appear as a column in the source or target definition when it represents nested message metadata in binary format. For more information about representing nested message metadata in binary format, see “Source and Target Definitions with Collapsed Nested Messages” on page 24.

For more information about importing source definitions from a TIB/Repository instance, see “Importing a TIBCO Source Definition from TIB/Repository” on page 27. For more

Figure 3-2. TIB/Repository Instance

Figure 3-3. Target Definition Based on a TIB/Repository Instance

Classes

Attributes Datatypes

Nested Message

Metadata

Nested Message

Attribute & Datatype

Class Representing Nested

Message Metadata

The group name derives from a class

in the TIB/Repository instance.

The columns derive from attributes in

the TIB/Repository instance.


information about importing target definitions from a TIB/Repository instance, see “Importing a TIBCO Target Definition from TIB/Repository” on page 47.

TIBCO Metadata Tree

You can view the structure of TIBCO source and target metadata from the Metadata Tree Editor in the PowerCenter Designer. TIBCO metadata trees show the hierarchical structure of TIBCO source and target metadata. The source or target group is the highest node in a metadata tree. Under the group, the metadata tree stores fields and other group nodes, which are subgroups. The fields represent metadata for message data fields. The subgroups represent metadata for nested messages. Subgroups can also contain nodes for data fields. These represent nested message data fields. Each source and target definition has its own metadata tree.

Figure 3-4 shows a TIBCO metadata tree based on the source and target definitions in Figure 3-1 on page 19:

You can update the TIBCO metadata tree when you edit a TIBCO source or target definition. For more information about editing the TIBCO metadata tree for a source definition, see “Editing the TIBCO Metadata Tree” on page 35. For more information about editing the TIBCO metadata tree for a target definition, see “Editing the TIBCO Metadata Tree” on page 54.

Map Values

Each node in the TIBCO metadata tree has a map value. The map value shows the relationship of a column to the group in the hierarchy. It shows which columns in a source or target definition represent metadata for message header fields or message data fields. It also shows which columns in a source or target definition represent metadata for nested message fields.

Figure 3-4. TIBCO Metadata Tree

Group Name: Highest

Node in the Metadata Tree

Message Data Fields

Subgroup Name: Group for

Nested Message Metadata

Map Value for the Column

WHOLESALE_COST

Source and Target Metadata Hierarchy 21

The map value for each column that represents message header metadata begins with “MSG_HEADER.” The column name follows. For example, in Figure 3-5, the map value for the column representing message header metadata is MSG_HEADER\SendSubject.

The group name in the TIBCO metadata tree is the highest node in the map value for columns representing message data fields. For example, the highest node for the columns representing message metadata in Figure 3-5 is PRICE. PRICE is also the name of the group in the target definition.

The subgroup name follows the group name in the map value for fields that belong to the subgroup. These fields represent metadata for nested messages. For example, ITEM in Figure 3-5 is a subgroup in the TIBCO metadata tree. When a source or target definition contains metadata for a collapsed nested message, the subgroup name is also the column name.

The lowest node in the map value is a field or group name from the TIBCO metadata tree. When the map value represents a collapsed message, the lowest node represents a group name. When the map value represents fields of the group or a subgroup, the lowest node represents a field name in the TIBCO metadata tree.

In Figure 3-5, the columns PRICE, WHOLESALE_COST, and SALE_PRICE represent metadata for data fields in a TIBCO message. They represent data fields under the group PRICE in the TIBCO metadata tree. The columns ITEM_ID, ITEM_NAME, and ITEM_DESC in Figure 3-5 represent metadata for nested message data fields. They belong to the subgroup ITEM in the TIBCO metadata tree.

The map value appears in the TIBCO metadata tree. It also displays on the Attributes tab of the Edit Tables dialog box for the source or target definition.

Figure 3-5 shows the map values of the columns in the target definition in Figure 3-1 on page 19:

Figure 3-5. TIBCO Target Definition Map Values

Group Name: Highest

Node in the Map Value

Column Name: Lowest

Node in the Map Value

Map Values

Subgroup Name: Identifies

Nested Messages

Message Header

Map Value


Nested Messages

TIBCO source and target definitions represent nested message metadata in one of the following ways:

♦ Source and target definitions can contain separate columns for nested message data fields.

♦ Source and target definitions can collapse the nested message data fields into a binary column.

When you create a TIBCO source or target definition, you determine whether it should contain separate columns for each nested message data field or whether you want it to contain a collapsed binary field. For more information about defining a TIBCO source, see “Working with TIBCO Sources” on page 25. For more information about defining a TIBCO target, see “Working with TIBCO Targets” on page 41.

Source and Target Definitions with Separate Columns for Nested Message Data Fields

When a TIBCO source or target definition represents nested message metadata as separate columns, each nested message data field receives its own column in the source or target definition with the appropriate TIBCO datatype. During a session, the Integration Service can extract data from or write data to each nested message field in a TIBCO message. It can also transform the data in any of the data fields of the nested message.

For example, a source definition contains a nested message with the fields ITEM_ID, ITEM_NAME, and ITEM_DESC. During a session, the Integration Service can read data from TIBCO message fields of the same name and transform the data in any of the data fields. For more information about TIBCO datatypes in PowerCenter, see “TIBCO and Transformation Datatypes” on page 79.

Figure 3-6 shows a source definition with nested message data fields as separate columns:

You can view the hierarchical structure of the nested message metadata in the TIBCO metadata tree. For more information about the TIBCO metadata tree, see “TIBCO Metadata Tree” on page 21.

Figure 3-6. Source Definition with Separate Columns for Nested Message Data Fields

Nested Message Data Fields

Nested Messages 23

Source and Target Definitions with Collapsed Nested Messages

When a TIBCO source or target definition represents nested message metadata as binary data in a single column, the Integration Service processes the data as a single, binary block. In the source or target definition, the column representing the nested message metadata receives the name of the data field that contains the nested message. It also receives the datatype msg. The msg datatype is a TIBCO datatype that represents the nested message data fields from a TIBCO message. For more information about TIBCO datatypes in PowerCenter, see “TIBCO and Transformation Datatypes” on page 79.

For example, you create a TIBCO source definition based on message metadata from a TIBCO message with the following structure:

[2002-20-03 12:22:45]: subject=cm.nt1, message={ORDER_ID=726 QUANTITY=250 DISCOUNT=10.000000 ITEM_CLASS={ITEM_ID=5378.000000 ITEM_NAME=Divers Knife and Sheath ITEM_DESC=Tools}}

When the PowerCenter Designer represents the nested message metadata as a binary column, the column receives the name ITEM_CLASS. This is because ITEM_CLASS is the data field in the TIBCO message that contains the nested message data fields. In the source definition, the column representing the nested message receives the datatype msg.

Figure 3-7 shows a source definition with a nested message represented as a binary column:

Although the source definition represents the nested message metadata as a binary column, you can view the metadata for the individual fields of the nested message in the TIBCO metadata tree. For example, if the nested message data fields are ITEM_ID, ITEM_NAME, and ITEM_DESC, the TIBCO metadata tree contains the fields under the subgroup ITEM_CLASS. For more information about the TIBCO metadata tree, see “TIBCO Metadata Tree” on page 21.

Note: When you include TIBCO source or target definitions in a mapping, and you include the mapping in a session with a TIB/Adapter SDK application connection, the TIBCO source and target definitions in the mapping must represent nested message metadata with separate columns for the nested message data fields.

Figure 3-7. TIBCO Source Definition with a Collapsed Nested Message

Collapsed Nested Message


C h a p t e r 4

Working with TIBCO Sources


♦ Overview, 26

♦ Importing a TIBCO Source Definition from TIB/Repository, 27

♦ Creating a TIBCO Source Definition Manually, 31

♦ Editing a TIBCO Source Definition, 32

♦ Working with the TIBCO Source Group, 35

♦ Creating the Application Multi-Group Source Qualifier, 40

25

Overview

You create a TIBCO source definition in the Source Analyzer. When you create a TIBCO source definition, the PowerCenter Designer displays a table with message fields and TIBCO-specific datatypes. When the Integration Service extracts data from the TIBCO source, it converts the data based on the datatypes in the Application Multi-Group Source Qualifier transformation associated with the source.

You can create a TIBCO source definition in the following ways:

♦ Import a source definition from a TIB/Repository instance.

♦ Create a source definition manually.

When you create a TIBCO source definition, you can manually add message header fields to the source definition. If you import a source definition from TIB/Repository, you can add header fields during import.

When you create a TIBCO source definition for reading TIB/Rendezvous messages, you can include the following header fields: SendSubject, ReplySubject, Sequence, SenderName, and TimeLimit.

When you create a TIBCO source definition for reading AE messages, you can include the following header fields: SendSubject, ReplySubject, Sequence, and SenderName.

After you create a TIBCO source definition, you can edit the source definition to reflect changes in source messages. When you edit the source definition, you can also use the TIBCO Group Wizard to edit the TIBCO metadata tree for the source definition and add or remove columns from the source. If you create a source definition manually, you must edit the metadata tree from the TIBCO Group Wizard to define the group and columns in the source definition. For more information about editing source definitions, see “Editing a TIBCO Source Definition” on page 32. For more information about using the TIBCO Group Wizard, see “Working with the TIBCO Source Group” on page 35.

26 Chapter 4: Working with TIBCO Sources

Importing a TIBCO Source Definition from TIB/Repository

You can connect to TIB/Repository to import a source definition from a TIB/Repository instance. To connect to a TIB/Repository instance, enter a URL for the TIB/Repository instance in the Import TIBCO Metadata dialog box.

When you import a source definition from a TIB/Repository instance, you must also enter an application name and configuration URL. The application name is the name of the adapter instance that starts the TIB/Repository session with the TIB/Repository instance. The configuration URL is the URL for the adapter instance. Use a user-defined application name and configuration URL to connect to a TIB/Repository instance. Or, use the application name and configuration URL that Informatica provides with PowerCenter Connect for TIBCO. For more information about the TIBCO adapter instance that Informatica provides with PowerCenter Connect for TIBCO, see “Step 3. Install the infaMetadata Adapter Instance” on page 14.

When you connect to a TIB/Repository instance, the PowerCenter Designer displays the class definitions and attributes in the TIB/Repository instance. The PowerCenter Designer might not display some classes for the following reasons:

♦ Classes or fields have user-defined or invalid datatypes.

♦ Classes or fields contain a carrot (^), backslash (\), space, or period.

♦ Classes or fields have the same name as another class or field.

♦ Classes or fields are longer than 80 characters.

When the PowerCenter Designer cannot display a class, the Output window lists the class and the reason it does not display. For example, a TIB/Repository instance contains the class CLASS\ITEM. When you connect to the TIB/Repository instance, the PowerCenter Designer does not display the class CLASS\ITEM because of the character “\”. The PowerCenter Designer displays the following message:

Class ‘CLASS\ITEM’ is rejected. The character ‘\’ is not allowed.

For more information about importing a source definition from TIB/Repository, see “Source and Target Definitions Based on TIB/Repository Metadata” on page 19.

Importing a TIBCO Source Definition from TIB/Repository 27

To import a source definition from a TIB/Repository instance:

1. In the Source Analyzer, click Sources > Import from TIBCO Repository.

The Import TIBCO Metadata dialog box appears.

2. In the Import TIBCO Metadata window, enter a Repository URL for a TIB/Repository instance.

Use tibrc@<repository name> as the repository URL. For example, if the repository name is OrderRepo, enter tibrc@OrderRepo.

3. Optionally, enter a filter to view select classes from the TIB/Repository instance.

Enter a particular class name. Or, enter a filter condition with the wildcard character, %, to display classes that meet the filter condition. Use the following filter syntax when entering a wildcard character:

♦ Enter the filter condition as a prefix. For example, enter A% to display all classes that begin with “A.”

♦ Enter the filter condition as a suffix. For example, enter %s to display all classes that end with “s.”

♦ Enter the filter condition as a substring. For example, enter %d% to display all classes that contain a “d.”

Note: Class names are case sensitive.

To display all classes, leave the filter blank.


4. Click “Retrieve top-level metadata only” to only view classes from the TIB/Repository instance that do not represent nested message metadata.

When you only view top-level metadata, you cannot import a class that represents nested message metadata as a group in the source definition. For more information about nested messages in a TIB/Repository instance, see “TIB/Repository” on page 5 and “Source and Target Definitions Based on TIB/Repository Metadata” on page 19.

5. Click Connect.

The PowerCenter Designer displays a list of classes in the TIB/Repository instance.

Importing a TIBCO Source Definition from TIB/Repository 29

6. Use the Add button to select the class you want to import.

The PowerCenter Designer adds the class and its attributes to the Objects to import pane. If any of the attributes represent a class that contains nested message metadata, the PowerCenter Designer adds them to the Objects to import pane as well. Only classes display in the Objects to import pane.

Tip: If you selected a class that you do not want to import, you can remove the class from the Objects to import pane by selecting the class and clicking the Remove button.

7. Click the Collapse Class box to the right of the class name to collapse a class into a single column in the source definition.

When you collapse a class into one column, you create a column in the source definition with the datatype msg. If you do not collapse the class, each data field of the class appears as a separate column in the source definition. For more information about including nested messages in a TIBCO source definition, see “Nested Messages” on page 23.

8. Enter a name for the source definition in the Source name field.

9. To add header fields to the source definition, click Create default header fields.

For more information about header fields in a TIBCO message, see “TIBCO Messages” on page 4.

Tip: You can also add header field metadata to the source definition in the TIBCO Group Wizard when you edit the source definition. For more information about using the TIBCO Group Wizard, see “Working with the TIBCO Source Group” on page 35.

10. Click Import.

Add Button

Remove Button

Collapse Class Box


Creating a TIBCO Source Definition Manually

When you manually create a source definition in the PowerCenter Designer, you define the structure of the TIBCO source without importing source metadata from a TIB/Repository instance. After creating the source definition, you add source metadata by creating a group in the source definition.

To manually create a source definition:

1. In the Source Analyzer, click Sources > Create.

The Create Source dialog box appears.

2. Enter a name for the source definition.

3. Enter a name in the Database Name field.

4. From Database Type, select TIBCO.

5. Click Create.

An empty TIBCO source definition appears in the Source Analyzer.

To add another source definition, enter a new source name. Click Create.

6. Click Done.

Note: After creating the TIBCO source definition, you need to add a group to the source definition. For more information about adding a group to a source definition, see “Working with the TIBCO Source Group” on page 35.

Creating a TIBCO Source Definition Manually 31

Editing a TIBCO Source Definition

You can edit a TIBCO source definition to reflect changes in the source messages. You can also modify the name and description of the source definition. You can modify the name and description of the source definition or column names and precision from the Edit Tables dialog box. To add or remove columns from the source definition, use the TIBCO Group Wizard. For more information about editing groups in a source definition, see “Working with the TIBCO Source Group” on page 35.

Note: If you import the source definition from a TIB/Repository instance, and you want to edit the source definition to reflect changes to the metadata in the TIB/Repository instance, you might find it easier to reimport the source definition if changes to the TIB/Repository instance are significant.

To edit a TIBCO source definition:

1. In the Source Analyzer, double-click the title bar of the source definition.

The Edit Tables dialog box appears.

2. On the Table tab, optionally edit the following settings:

Table Settings Edit Description

Select table Yes Displays the source definition you are editing. To choose a different source definition

to edit, select it from the list.

Rename button Yes Edit the name of the source definition and enter a business name. For more

information about business names, see the PowerCenter Designer Guide.

Business name No Not applicable for TIBCO source definitions.


3. Click the Columns tab.

4. Edit the following settings:

Owner name Yes Not applicable for TIBCO source definitions.

Description Yes Optional description of source definition. Character limit is 2000 bytes/K, where K is

the maximum number of bytes for each character in the PowerCenter repository code

page. Enter links to business documentation.

Database type No Database type is TIBCO.

Column Settings Edit Description

Select Table Yes Displays the source definition you are editing. To choose a different source

definition to edit, select it from the list.

Column Name Yes To change the name of a column, click the column name you want to edit and enter

a new column name. When you change a column name, the TIBCO metadata tree

does not reflect the change.

Datatype No To change the datatype for a column, edit the datatype in the Columns and Keys

window in the TIBCO Group Wizard. For more information about editing datatypes

in the TIBCO Group Wizard, see “Editing the TIBCO Source Group” on page 37.

Precision Yes To change the precision, click the precision for the column you want to edit, and

enter a new value for precision. When you change the precision for a column, the

TIBCO metadata tree does not reflect the change.

Scale No Displays scale.

Not Null No Not applicable for TIBCO source definitions.


Invokes the TIBCO

Group Wizard

Editing a TIBCO Source Definition 33

5. If you want to edit the source group or the TIBCO metadata tree, click the Edit group button to invoke the TIBCO Group Wizard.

For more information about editing groups, see “Working with the TIBCO Source Group” on page 35.


Working with the TIBCO Source Group

You can edit the group in a TIBCO source definition to reflect changes in TIBCO message formats. Use the TIBCO Group Wizard to modify the group. The TIBCO Group Wizard lets you change the group name, update the TIBCO metadata tree, and edit the columns in the source definition.

Editing the TIBCO Metadata Tree

Edit the TIBCO metadata tree when you want to add, remove, or modify classes and fields. When you modify the metadata tree, use the updated tree to add columns to the group in the TIBCO source definition.

To edit the TIBCO metadata tree:

1. Open the Edit Tables window for the source or target definition you want to edit.


3. Click the Edit Group button to invoke the TIBCO Group Wizard.

4. Click Next.

Create Group ButtonEdit Group Button

Delete Group Button

Working with the TIBCO Source Group 35

The Columns and Keys window appears.

5. Click the Edit Metadata Tree button.

The Metadata Tree Editor appears.

Edit Metadata

Tree Button

Add Group Button

Remove Field Button

Add Field Button

Remove Group Button


6. Edit the metadata tree.

Use the Metadata Tree Editor to complete the following tasks:

7. Click OK when you are finished editing the metadata tree.

Editing the TIBCO Source Group

You can edit the group in a TIBCO source definition to add, remove, or modify columns. For example, you can change a column name or change the order in which columns appear in the source definition.

Note: When you want to add columns to a group, you must first add the column to the TIBCO metadata tree.

Task Description

Add a group Click the Add Group button to add a group. If the source or target definition already contains

a group, any group you add represents nested message metadata. If the source or target

definition does not already contain a group, any group you add will be the group name for

the source or target definition.

Remove a group Click the Remove Group button to remove a group that represents nested message

metadata. You cannot remove a group when the group is a column in the source or target

definition or when fields from the group are columns in the source or target definition.

Edit a group name Right-click the group name to edit it. You cannot rename a group when the group is a

column in the source or target definition or when fields from the group are columns in the

source or target definition.

Edit the precision

of a group

Click a group name and enter a new value for precision in the Prec field. When you edit the

precision for a group that exists the source or target definition, the new value for the

precision does not reflect in the source or target definition.

To change the precision of a group in the source or target definition, change the precision on

the Columns and Keys page of the Edit Group Wizard or on the Columns tab of the Edit

Tables dialog box.

Add a field Click the Add Field button to add a field to a group.

Edit a field name Click the field name to edit it. You cannot rename a field when the field is a column in the

source or target definition.

Remove a field Click the Remove Field button to remove a field from a group. You cannot rename a field

when the field is a column in the source or target definition.

Edit the datatype

and precision of a

field

Click the field and enter a new datatype or precision in the Datatype and Prec fields. When

you edit the precision or datatype of a field that is a column in the source or target definition,

the new value for the precision does not reflect in the source or target definition.

To change the precision or datatype of a field in the source or target definition, change the

precision on the Columns and Keys page of the Edit Group Wizard or on the Columns tab of

the Edit Tables dialog box.


To edit the TIBCO source group:

1. Open the Edit Tables dialog box for the source definition you want to edit.



The TIBCO Group Wizard appears.

4. Optionally, edit the following settings:

Tip: If you add header fields to the source definition and you later want to remove them, you must delete them from the Columns and Keys window in the Group Wizard.

5. Click Next.

Settings Description

Enter a name for this group Enter a name for the group.

Description Enter a description of the group.

Default Headers Select any header fields you want to add to the source definition. For more

information about header fields, see “TIBCO Messages” on page 4.


The Columns and Key window appears.

6. Edit the group in the source definition:

♦ To add a new column to the source definition, select a field from the TIBCO metadata tree and click the Add button.

♦ To add a collapsed nested message to the source definition, select the group name and click the Add button.

♦ To remove a column from the source definition, click the Delete button.

♦ To change the order of columns in the source definition, use the up and down arrows.

Note: If you add a group or field with spaces, a backslash, tab, carriage return, new line, or period, the PowerCenter Designer replaces the characters with underscores.

7. Edit the columns in the group:

8. Click Finish.

Settings Edit Description

Column Name Yes Click the column name you want to edit and enter a new column name. When you

change a column name, the TIBCO metadata tree does not reflect the change.

Not Null No Not applicable for TIBCO source definitions.

Datatype Yes Click the datatype for the column you want to edit, and select a new datatype from the

list. When you change the datatype for a column, the TIBCO metadata tree does not

reflect the change.

Precision Yes Click the precision for the column you want to edit, and enter a new value for precision.

When you change the precision for a column, the TIBCO metadata tree does not reflect

the change.


Delete Button

Move column up or down.

Add Button


Creating the Application Multi-Group Source Qualifier

An Application Multi-Group Source Qualifier determines how the Integration Service reads data from the TIBCO source. During a session, the Integration Service reads messages from the TIBCO daemon based on the connected ports and transformation properties.

When you use a TIBCO source definition in a mapping, the PowerCenter Designer includes a predefined Application Multi-Group Source Qualifier with the source definition. You cannot edit the Application Multi-Group Source Qualifier. To extract data from multiple TIBCO sources, use an Application Multi-Group Source Qualifier for each source definition in the mapping.

Figure 4-1 shows a TIBCO source definition connected to an Application Multi-Group Source Qualifier:

Transformation Datatypes

The transformation datatypes in the Application Multi-Group Source Qualifier are internal datatypes based on ANSI SQL-92 generic datatypes, which PowerCenter uses to move data across platforms. When the Integration Service reads data from a TIBCO source, it converts the data from its native datatype to the transformation datatype. When you run a session, the Integration Service performs transformations based on the transformation datatypes. When writing data to a target, the Integration Service converts the data based on the native datatypes in the target definition.

The transformation datatype for all ports in the Application Multi-Group Source Qualifier are predefined. You cannot change the datatype for any of the fields in the Application Multi-Group Source Qualifier. For more information about transformation datatypes, see “TIBCO and Transformation Datatypes” on page 79.

Creating the Application Multi-Group Source Qualifier

Transformation

By default, the PowerCenter Designer creates an Application Multi-Group Source Qualifier when you add a TIBCO source definition to a mapping. If you configure the PowerCenter Designer to manually create a source qualifier when you add a source definition to a mapping, you must manually connect an Application Multi-Group Source Qualifier to a TIBCO source definition.

Figure 4-1. TIBCO Source Definition and Application Multi-Group Source Qualifier


C h a p t e r 5

Working with TIBCO Targets


♦ Overview, 42

♦ Defining a Target from a TIBCO Source Definition, 43

♦ Defining a TIBCO Target from a Relational or Flat File Source Definition, 44

♦ Importing a TIBCO Target Definition from TIB/Repository, 47

♦ Creating a TIBCO Target Definition Manually, 50

♦ Editing a TIBCO Target Definition, 51

♦ Working with the TIBCO Target Group, 54

41

Overview

You create a TIBCO target definition in the Target Designer in the PowerCenter Designer. When you create a TIBCO target definition, the PowerCenter Designer displays a table with message fields and TIBCO-specific datatypes. The target you define represents the message structure of the TIBCO messages you want to write to the TIBCO daemon during a PowerCenter session.

You can create a TIBCO target definition in the following ways:

♦ Create a target from a TIBCO source definition.

♦ Create a target from a relational or flat file source definition.

♦ Import a target definition from a TIB/Repository instance.

♦ Create a target definition manually.

When you create a TIBCO target definition, you can manually add message header fields to the target definition. If you import a target definition from a TIB/Repository instance, you can add the header fields during import.

When you create a TIBCO target definition for writing TIB/Rendezvous messages, you can include the following header fields: SendSubject, ReplySubject, and TimeLimit. When you create a TIBCO target definition for writing AE messages, you can include the SendSubject and ReplySubject header fields.

After you create a TIBCO target definition, you can edit the target definition to reflect changes in target messages. When you edit the target definition, you can also use the TIBCO Group Wizard to edit the TIBCO metadata tree for the target definition and add or remove columns from the target. If you create a target definition manually, you must edit the metadata tree from the TIBCO Group Wizard to define the group and columns in the target definition. For more information about editing target definitions, see “Editing a TIBCO Target Definition” on page 51. For more information about using the TIBCO Group Wizard, see “Working with the TIBCO Target Group” on page 54.

Specifying SendSubject in a TIBCO Target Definition

When you include SendSubject as a column in a TIBCO target definition, the values the Integration Service passes to the SendSubject field overwrite the default subject name in the TIBCO application connection. This lets you send TIBCO target messages with different subjects. For example, during a workflow, if a TIBCO target message contains the value infa.subj.1 for SendSubject, the Integration Service writes the message to the TIBCO daemon with the subject infa.subj.1. Likewise, during the workflow, if a TIBCO target message contains the value infa.subj.2 for SendSubject, the Integration Service writes the message to the TIBCO daemon with the subject infa.subj.2. If the value for SendSubject in a TIBCO target message is null, the Integration Service writes the message using the default subject in the TIBCO application connection. For more information about configuring a subject in a TIBCO application connection, see “Managing Connection Objects” in the PowerCenter Workflow Administration Guide.

42 Chapter 5: Working with TIBCO Targets

Defining a Target from a TIBCO Source Definition

If you create a TIBCO target definition from a TIBCO source definition, the PowerCenter Designer creates a target definition similar to the source definition. The target definition contains the same TIBCO metadata tree. It also contains the header fields SendSubject, ReplySubject, and TimeLimit if they are columns in the source definition.

Figure 5-1 shows a TIBCO target definition created from a TIBCO source definition:

If the source definition contains a nested message, the target definition you create from the source definition contains the same nested message. If the nested message in the source definition is collapsed, the target definition contains the same collapsed nested message. If the nested message fields appear as columns in the source definition, they also become columns in the target definition.

Figure 5-2 shows a TIBCO target definition from a TIBCO source definition with a collapsed nested message:

Create a TIBCO target definition from a TIBCO source definition by dragging a TIBCO source definition to the Target Designer workspace.

Figure 5-1. TIBCO Target Definition Created from a TIBCO Source Definition

Figure 5-2. TIBCO Target Definition Created from a Flat File Source Definition

TIBCO Target DefinitionTIBCO Source Definition

TIBCO Source Definition TIBCO Target Definition

Collapsed Nested

Message

Collapsed Nested

Message

Defining a Target from a TIBCO Source Definition 43

Defining a TIBCO Target from a Relational or Flat File

Source Definition

When you create a TIBCO target definition from a relational or flat file source definition, the PowerCenter Designer creates a group for the target definition. The group name is the name of the source definition. The columns in the source definition become columns in the target definition. The PowerCenter Designer also creates a TIBCO metadata tree for the target definition.

Figure 5-3 shows a TIBCO target definition created from a flat file source definition:

In this example, all of the columns from the flat file source definition appear in the TIBCO target definition. The name of the source definition, ORDER_INFO, is the group name in the target definition. The datatypes in the target definition are TIBCO-specific datatypes.

You can define TIBCO targets with nested messages from a relational or flat file source definition. Since relational and flat file source definitions do not have hierarchical structures, you need to use multiple source definitions to create a TIBCO target definition with nested messages. When you define the target, you select one source definition as the group for the target definition. You select another source definition as a subgroup of the first group.

For example, you create a TIBCO target definition from a flat file source definition called ORDER_INFO. The target definition has the following fields: CUSTOMER_ID, CUSTOMER_NAME, ITEM, and PURCHASE_DATE. You want the TIBCO target messages to also include a nested message. A flat file source definition called PRICE contains the columns WHOLESALE_PRICE, RETAIL_PRICE, and DISCOUNT. Add the source definition PRICE as a subgroup of the target group ORDER_INFO. PRICE becomes the name of the subgroup. The columns WHOLESALE_PRICE, RETAIL_PRICE, and DISCOUNT become fields in the subgroup PRICE, which represents nested message metadata in the TIBCO target definition.

Figure 5-3. TIBCO Target Definition Created from a Flat File Source Definition

Source Definition Name

Target Group

Name


Figure 5-4 shows a TIBCO target definition created from two flat file source definitions:

You can also define a nested message manually from the TIBCO Metadata Tree Editor, and add the nested metadata to the target in the TIBCO Group Wizard. For more information about editing the TIBCO metadata tree and using the TIBCO Group Wizard, see “Working with the TIBCO Source Group” on page 35.

To create a TIBCO target definition from a relational or flat file source definition:

1. In the Target Designer, click Target > Import TIBCO.

The Import TIBCO Target dialog box appears.

2. Select Import from Other Sources.

The TIBCO Import dialog box appears.

3. Enter a name for the target definition in the Target name field.

4. To add header fields to the target definition, click Create default header fields.

5. Select the source definition you want to import, and click the Add button.

The source definition you add becomes the group for the TIBCO target definition.

Figure 5-4. TIBCO Target Definition with Nested Message Data Fields

Nested Message

Fields

Add Button

Remove Button

Collapse Class Box

Group Name for the

Target Definition

Defining a TIBCO Target from a Relational or Flat File Source Definition 45

6. Under a group in the Selected Sources column, optionally add a subgroup by clicking the group name, and adding a source from the Select Sources column.

The new subgroup becomes nested message metadata for the target definition.

7. Optionally, click the Collapse Class box for any group in the Selected Sources column.

If you select the Collapse Class box, the fields in the group appear as a binary column in the target definition.

8. Click OK.

The Integration Service displays the TIBCO target definition in the Target Designer.

Subgroup Name for

the Target Definition


Importing a TIBCO Target Definition from TIB/Repository

You can connect to TIB/Repository to import a target definition from a TIB/Repository instance. To connect to a TIB/Repository instance, enter a URL for the TIB/Repository instance in the Import TIBCO Metadata dialog box.

When you import a target definition from a TIB/Repository instance, you must also enter an application name and configuration URL. The application name is the name of the adapter instance that starts the TIB/Repository session with the TIB/Repository instance. The configuration URL is the URL for the adapter instance. Use a user-defined application name and configuration URL to connect to a TIB/Repository instance. Or, use the application name and configuration URL that Informatica provides with PowerCenter Connect for TIBCO. For more information about the TIBCO adapter instance that Informatica provides with PowerCenter Connect for TIBCO, see “Step 3. Install the infaMetadata Adapter Instance” on page 14.

When you connect to a TIB/Repository instance, the PowerCenter Designer displays the classes and attributes in the TIB/Repository instance. The PowerCenter Designer might not display some classes for the following reasons:

♦ Classes or fields have user-defined or invalid datatypes.

♦ Classes or fields contain a carrot (^), backslash (\), space, or period.

♦ Classes or fields have the same name as another class or field.

♦ Classes or fields are longer than 80 characters.

When the PowerCenter Designer cannot display a class, the Output window lists the class and the reason it does not display. For example, a TIB/Repository instance contains the class CLASS\ITEM. When you connect to the TIB/Repository instance, the PowerCenter Designer does not display the class CLASS\ITEM because of the character “\”. The PowerCenter Designer displays the following message:

Class ‘CLASS\ITEM’ is rejected. The character ‘\’ is not allowed.

For more information about importing a target definition from a TIB/Repository instance, see “Source and Target Definitions Based on TIB/Repository Metadata” on page 19.

To import a target definition from a TIB/Repository instance:

1. In the Target Designer, click Target > Import TIBCO.

2. Select Import from TIBCO Repository.

3. In the Import TIBCO Metadata window, enter a Repository URL for a TIB/Repository instance.

Use tibrc@<repository name> as the repository URL. For example, if the repository name is OrderRepo, enter tibrc@OrderRepo.

4. Optionally, enter a filter to only view select classes from the TIB/Repository instance.

Importing a TIBCO Target Definition from TIB/Repository 47

Enter a particular class name. Or, enter a filter condition with the wildcard character, %, to display classes that meet the filter condition. Use the following filter syntax when entering a wildcard character:

♦ Enter the filter condition as a prefix. For example, enter A% to display all classes that begin with “A.”

♦ Enter the filter condition as a suffix. For example, enter %s to display all classes that end with “s.”

♦ Enter the filter condition as a substring. For example, enter %d% to display all classes that contain a “d.”

Note: Class names are case sensitive.

To display all classes, leave the filter blank.

5. Click Retrieve top-level metadata only to view classes from the TIB/Repository instance that do not represent nested message metadata.

When you only view top-level metadata, you cannot import a class that represents nested message metadata as a group in the target definition. For more information about nested messages in a TIB/Repository instance, see “TIB/Repository” on page 5 and “Source and Target Definitions Based on TIB/Repository Metadata” on page 19.

6. Click Connect.

The PowerCenter Designer displays a list of classes in the TIB/Repository instance.


7. Use the Add button to select the class you want to import.

The PowerCenter Designer adds the class and its attributes to the Objects to import pane. If any of the attributes represent a class that contains nested message metadata, the PowerCenter Designer adds them to the Objects to import pane as well. Only classes display in the Objects to import pane.

Tip: If you selected a class that you do not want to import, you can remove a class from the Objects to import pane by selecting the class and clicking the Remove button.

8. Click the Collapse Class box to the right of the class name to collapse a class into a single column in the target definition.

When you collapse a class into one column, you create a column in the target definition with the datatype msg. If you do not collapse the class, each data field of the class appears as a separate column in the target definition. For more information about including nested messages in a TIBCO target definition, see “Nested Messages” on page 23.

9. Enter a name for the target definition in the Target name field.

10. To add header fields to the target definition, click Create default header fields.

Tip: You can also add header field metadata to the target definition in the TIBCO Group Wizard when you edit the target definition.

For more information about header fields in a TIBCO message, see “TIBCO Messages” on page 4. For more information about using the TIBCO Group Wizard, see “Working with the TIBCO Target Group” on page 54.

11. Click Import.

Add Button

Remove Button

Collapse Class Box

Importing a TIBCO Target Definition from TIB/Repository 49

Creating a TIBCO Target Definition Manually

When you manually create a target definition in the PowerCenter Designer, you define the structure of the TIBCO target without importing metadata from a TIB/Repository instance. After creating the target definition, you add target metadata by creating a group in the target definition. For more information about adding a group to a target definition, see “Working with the TIBCO Target Group” on page 54.

To manually create a target definition:

1. In the Target Designer, click Targets > Create.

The Create Target Table dialog box appears.

2. Enter a name for the target definition.

3. From Database Type, select TIBCO.

4. Click Create.

An empty TIBCO target definition appears in the Target Designer.

To add another target definition, enter a new target name. Click Create.

5. Click Done.


Editing a TIBCO Target Definition

You can edit a TIBCO target definition to add or modify columns to reflect changes in the target messages. You can also modify the name and description of the target definition. You can modify the name and description of the target definition or column names and precision from the Edit Tables dialog box. To add or remove columns from the target definition, use the TIBCO Group Wizard.

For more information about editing groups in a target definition, see “Working with the TIBCO Target Group” on page 54.

Note: If you import the target definition from a TIB/Repository instance, and you want to edit the target definition to reflect changes to the metadata in the TIB/Repository instance, you might find it easier to reimport the target definition if changes to the TIB/Repository instance are significant.

To edit a TIBCO target definition:

1. In the Target Designer, double-click the title bar of the target definition.

The Edit Tables dialog box appears.

2. On the Table tab, optionally edit the following settings:


Select table Yes Displays the target definition you are editing. To choose a different target definition to

edit, select it from the list.

Rename button Yes Edit the name of the target definition and enter a business name. For more

information about business names, see the PowerCenter Designer Guide.

Editing a TIBCO Target Definition 51


4. Edit the following settings:

Business name No Not applicable to TIBCO target definitions.

Constraints No Not applicable to TIBCO target definitions. Any entry is ignored.

Creation options No Not applicable to TIBCO target definitions. Any entry is ignored.

Description Yes Optional description of target definition. Character limit is 2000 bytes/K, where K is

the maximum number of bytes for each character in the PowerCenter repository code

page. Enter links to business documentation.

Database type No Database type is TIBCO.

Edit keywords Yes Add keywords to the target definition. Use the keywords to perform searches in the

Repository Manager.


Select Table Yes Displays the target definition you are editing. To chose a different target definition to

edit, select it from the list.

Column Name Yes To change the name of a column, click the column name you want to edit and enter

a new column name. When you change a column name, the TIBCO metadata tree

does not reflect the change.

Datatype No Displays datatype. To change the datatype for a column, edit the datatype in the

Columns and Keys window in the TIBCO Group Wizard. For more information about

editing datatypes in the TIBCO Group Wizard, see “Editing the TIBCO Target

Group” on page 54.


Create Group Button

Edit Group Button

Delete Group Button


5. If you want to edit the target group or the TIBCO metadata tree, click the Edit group button to invoke the TIBCO Group Wizard.

For more information about editing groups, see “Working with the TIBCO Target Group” on page 54.

Precision Yes To change the precision, click the precision for the column you want to edit, and

enter a new value for precision. When you change the precision for a column, the

TIBCO metadata tree does not reflect the change.


Not Null Yes Indicates whether the column can be blank or not. To change the not null status,

select or clear the not null status for the column you want to edit.


Editing a TIBCO Target Definition 53

Working with the TIBCO Target Group

You can edit the group in a TIBCO target definition to reflect changes in TIBCO message formats. Use the TIBCO Group Wizard to modify the group. The TIBCO Group Wizard lets you change the group name, update the TIBCO metadata tree, and edit the columns in the target definition.

Editing the TIBCO Metadata Tree

Edit the TIBCO metadata tree when you want to add, remove, or modify classes and fields. When you modify the metadata tree, use the updated tree to add columns to the group in the TIBCO target definition. For more information about editing the TIBCO metadata tree, see “Editing the TIBCO Metadata Tree” on page 35.

Editing the TIBCO Target Group

You can edit the group in a TIBCO target definition to add, remove, or modify columns. For example, you can change a column name or change the order in which columns appear in the target definition. When you want to add columns to a group, you must first add the column to the TIBCO metadata tree.

To edit the TIBCO target group:

1. Open the Edit Tables dialog box for the target definition you want to edit.



The TIBCO Group Wizard appears.


4. Optionally, edit the following settings:

Tip: If you add header fields to the target definition and you later want to remove them, you must delete them from the Columns and Keys window in the Group Wizard.

5. Click Next.

The Columns and Key window appears.

6. Edit the group in the target definition:

♦ To add a new column to the target definition, select a field from the TIBCO metadata tree and click the Add button. When you want to add nested message metadata, you can only represent the nested message metadata in one of two ways. The nested message metadata can be collapsed. Or, the metadata for the data fields can have separate columns in the target definition.

♦ To add a collapsed nested message to the target definition, select the group name and click the Add button.

♦ To remove a column from the target definition, click the Delete button.

♦ To change the order of columns in the target definition, use the up and down arrows.

Note: If you add a group or field with spaces, a backslash, tab, carriage return, new line, or a period to the target definition, the PowerCenter Designer replaces the characters with underscores.

Settings Description

Enter a name for this group Enter a name for the group.

Description Enter a description of the group.

Default Headers Select any header fields you want to add to the target definition. For more

information about header fields, see “TIBCO Messages” on page 4.

Delete Button

Move Column up or Down

Add Button

Working with the TIBCO Target Group 55

7. Edit the columns in the group.

8. Click Finish.

Settings Edit Description

Column Name Yes Click the column name you want to edit and enter a new column name. When you

change a column name, the TIBCO metadata tree does not reflect the change.

Not Null Yes Indicates whether the column can be blank or not. To change the not null status, select

or clear the not null status for the column you want to edit.

Datatype Yes Click the datatype for the column you want to edit, and select a new datatype from the

list. When you change the datatype for a column, the TIBCO metadata tree does not

reflect the change.

Precision Yes Click the precision for the column you want to edit, and enter a new value for precision.

When you change the precision for a column, the TIBCO metadata tree does not reflect

the change.



C h a p t e r 6

Creating and Configuring

TIBCO Workflows


♦ Overview, 58

♦ Working with TIBCO Workflows, 59

♦ Configuring a Session with a TIBCO Mapping, 68

♦ Scheduling Workflows, 74

♦ Running Workflows, 75

♦ Troubleshooting, 76

57

Overview

After you create mappings in the PowerCenter Designer, you can create a session and use the session in a workflow to extract, transform, and load data. You can create sessions and workflows in the Workflow Manager.

Before configuring a TIBCO workflow, you must complete the following tasks:

♦ Configure an Integration Service. Configure an Integration Service to run TIBCO workflows. For more information about configuring an Integration Service, see the PowerCenter Administrator Guide.

♦ Configure source and target connections. Configure the connections necessary to read data from the source and write data to the target. For example, to extract data from a TIBCO source, the Integration Service requires an application connection. For more information about configuring queue connections, see “Managing Connection Objects” in the PowerCenter Workflow Administration Guide.

You cannot use a connection variable for an application connection. For more information about connection variables, see the PowerCenter Workflow Administration Guide.

58 Chapter 6: Creating and Configuring TIBCO Workflows

Working with TIBCO Workflows

When you configure a TIBCO workflow, you define the session and scheduler properties that determine how the Integration Service reads messages from a TIBCO source or writes messages to a TIBCO target. You can configure the following TIBCO workflow properties:

♦ TIBCO event queue information. Set TIBCO event queue information for a TIBCO session in a workflow. For more information, see “TIBCO Event Queue Information” on page 59.

♦ Session conditions. Set session conditions for a TIBCO session. For more information, see “Configuring Session Conditions” on page 60.

♦ Real-time data extraction. Configure a TIBCO session with the Real-time Flush Latency session condition to extract data in real time. For more information, see “Real-time Flush Latency” on page 62.

♦ Certified messages. Configure a TIBCO session to read and write certified messages. For more information, see “Configuring Certified Messages” on page 63.

♦ Message recovery. Enable recovery for a TIBCO session. For more information, see “Message Recovery” on page 66.

♦ Pipeline partitioning. Set partitions in a pipeline for a TIBCO session. For more information, see “Pipeline Partitioning” on page 67.

TIBCO Event Queue Information

When you configure a TIBCO session, you must enter an event queue in the session properties. The Integration Service uses an event queue to organize events. For example, the Integration Service uses an event queue when it receives messages.

In the session properties, you can select the default event queue. Or, you can enter an event queue name and queue parameters. The default event queue holds all event information. It can also contain an unlimited number of events and does not discard events. Event queues you create can hold specific event information. You can configure an event queue in the session properties to hold a certain number of events and to discard events when the queue is full.

Table 6-1 describes the queue parameters you can configure in the session properties when you do not want to use the default event queue:

Table 6-1. TIBCO Event Queue Parameters

Queue ParameterRequired/ Optional

Description

Queue Name Optional Name for the event queue.

Queue Maximum

Event Limit

Required Maximum number of events the event queue can contain. Default is unlimited.

Working with TIBCO Workflows 59

For example, you enter a queue name in the session properties and configure 5,000 as the queue maximum event parameter. You set the queue limit policy to discard the first event in the queue and the queue discard amount to discard 100 events. When the queue reaches 5,000 events, the Integration Service discards the first 100 events in the queue.

Configuring Session Conditions

When you configure a TIBCO session in a workflow, you can set values for session conditions. You set the session conditions from the Properties settings on the Mapping tab in the session properties.

You can define the following session conditions:

♦ Idle Time

♦ Message Count

♦ Reader Time Limit

♦ Real-time Flush Latency

The Idle Time, Message Count, and Reader Time Limit session conditions control when the Integration Service stops reading from the TIBCO daemon. The Real-time Flush Latency session condition controls when the Integration Service commits messages to the target for real-time data extraction during the session.

Queue Limit Policy Required Policy for discarding events when the event queue reaches the queue

maximum event limit.

Queue Discard

Amount

Required Number of events TIBCO discards from the event queue when the queue

reaches the maximum number of events.

Table 6-1. TIBCO Event Queue Parameters

Queue ParameterRequired/ Optional

Description


Figure 6-1 shows the Properties settings on the Mapping tab in the session properties where you set session conditions:

When you enter values for multiple session conditions, the Integration Service stops reading from the TIBCO daemon when the first session condition is met. For example, if you set the Idle Time value to 10 seconds and the Message Count value to 100 messages, the Integration Service stops reading from the TIBCO daemon after 10 seconds or after reading 100 messages, whichever comes first.

Idle Time

Use the Idle Time session condition to indicate how long the Integration Service waits when no messages arrive before it stops reading from the TIBCO daemon. Enter an Idle Time value in seconds in the session properties. For example, if you enter 30 for Idle Time, the Integration Service waits 30 seconds after reading from the TIBCO daemon. If no new messages arrive through the TIBCO daemon within 30 seconds, the Integration Service stops reading from the daemon.

Message Count

Use the Message Count session condition to control the number of messages the Integration Service reads from the TIBCO daemon before stopping. Enter a Message Count value in the session properties. For example, when you enter 100 for Message Count, the Integration Service reads 100 messages from the TIBCO daemon.

Figure 6-1. Session Conditions in the Session Properties

Session

Conditions


Reader Time Limit

Use the Reader Time Limit session condition to read messages from the TIBCO daemon for a set period of time. When you use the Reader Time Limit session condition, the Integration Service reads messages from the TIBCO daemon for the time period you enter. Enter a Reader Time Limit value in seconds in the session properties. For example, if you enter 10 for Reader Time Limit, the Integration Service stops reading from the TIBCO daemon after 10 seconds.

Real-time Flush Latency

Use the Real-time Flush Latency session condition in a session with a TIBCO source in the mapping to run the session in real time. When you use the Real-time Flush Latency session condition, the Integration Service commits TIBCO source messages to the target at the end of a specified maximum latency period.

For example, if the value for Real-time Flush Latency is 5, the Integration Service commits all messages read from the source five seconds after the first message enters the source. The lower you set the interval, the faster the Integration Service commits messages to the target.

Note: When you enter a low Real-time Flush Latency interval, the session might consume more system resources.

When you use the Real-time Flush Latency session condition to run a session in real time, complete the following steps:

1. If the pipeline contains an XML target definition, select Append to Document for the On Commit option from the Properties tab of the target definition.

2. Configure the session for source-based commits in the session properties.

3. When you configure the session to use source-based commits and add partitions to the pipeline, you must specify pass-through partitioning at each partition point.

4. Configure a real-time session to run as a continuous workflow. For more information about scheduling a workflow, see “Scheduling Workflows” on page 74.

When the Integration Service runs the session, it begins to read messages from the source. Once messages enter the source, the Real-time Flush Latency interval begins. At the end of each five second Real-time Flush Latency interval, the Integration Service commits all messages read from the source.

When you set the Real-time Flush Latency session condition and configure the session to use source-based commits, the Integration Service commits messages to the target using the source-based commit interval and the Real-time Flush Latency interval.

For example, you use 5 seconds as the Real-time Flush Latency session condition and you set the source-based commit interval to 1,000 messages. The Integration Service commits messages to the target at two points: after reading 1,000 messages from the source and after each five second Real-time Flush Latency interval.

If you configure the session to use target-based commits, the Integration Service runs the session using source-based commits. Also, it only commits messages to the target based on the


Real-time Flush Latency interval. It does not commit messages to the target based on the commit interval. For more information about commit types and intervals, see the PowerCenter Workflow Administration Guide.

When you use the Real-time Flush Latency session condition, the following limitations apply:

♦ The pipeline cannot contain Transaction Control transformations.

♦ The pipeline cannot contain Custom transformations with the Generate Transaction option selected. You select the Generate Transaction option on the Properties tab of the Edit Transformations dialog box.

♦ The pipeline cannot contain transformations with the All Input option selected for the Transformation Scope property. You select a value for the Transformation Scope property on the Properties tab of the Edit Transformations dialog box.

♦ The pipeline cannot contain any transformation that has row transformation scope and receives input from multiple transaction control points.

♦ The mapping cannot contain a flat file target definition.

♦ The session cannot contain partition types other than pass-through at all partition points.

♦ The Integration Service ignores the Real-time Flush Latency session condition when you run a session in debug mode.

♦ If the mapping contains a relational target, the Target Load Type attribute in the Properties settings on the Mapping tab (Targets node) in the session properties should be Normal.

Configuring Certified Messages

The Integration Service can read certified messages from TIBCO sources and write certified messages to TIBCO targets.

Reading Certified Messages from TIBCO Sources

When you run a workflow to read certified messages from TIBCO sources, the Integration Service sends confirmation to the TIBCO source for each certified message it receives. If the PowerCenter session aborts or fails and then restarts, the Integration Service can still receive certified messages that the TIBCO daemon sent while the session was stopped for a certain time period.

Note: You can configure the TIBCO application to allow the TIBCO daemon to resend unconfirmed certified messages to PowerCenter for a certain time period. The higher the time period you set, the longer the TIBCO daemon can resend unconfirmed certified messages to PowerCenter. You must also set a file-based ledger in TIBCO to retain certified messaging information, which enables the TIBCO daemon to resend unconfirmed certified messages to PowerCenter. For more information about configuring TIBCO to send certified messages, see the TIBCO documentation.

When you configure a session to read certified messages from a TIBCO source, select a TIBCO application connection value that is configured to receive certified messages.


If you select a TIB/Adapter SDK application connection, verify that the adapter instance associated with the application connection is configured for certified messages. You can view the adapter instance properties in TIB/Designer. For more information about configuring an adapter instance, consult the TIBCO documentation.

If you select a TIB/Rendezvous application connection, you can view the application connection attributes to verify that the application connection is configured for certified messages.

When you configure a TIBCO application connection to read certified messages, you can select Request Old and enter a file-based ledger for the Ledger File attribute if you want the TIBCO daemon to resend unconfirmed messages to PowerCenter. When you select Request Old, the Integration Service asks the TIBCO daemon to resend unconfirmed messages. When you configure a file-based ledger, you ensure that the Integration Service retains information about certified messages, including information about certified message senders and the number of messages the PowerCenter has received.

Figure 6-2 shows a TIBCO application connection configured for reading certified messages:

For more information about configuring TIBCO application connections for certified messages, see “Managing Connection Objects” in the PowerCenter Workflow Administration Guide.

Writing Certified Messages to TIBCO Targets

When you run a workflow to write certified messages to TIBCO targets, the Integration Service expects confirmation from the TIBCO targets for each certified message it sends. If the Integration Service does not receive confirmation from the TIBCO targets, the TIBCO

Figure 6-2. TIBCO Application Connection Configured for Certified Messages

Required Attributes for Certified

Messages

Optional Attributes for

Certified Messages


daemon can resend the certified message for a specified period of time or until it receives confirmation.

When you create a session to write certified messages to TIBCO targets, configure the following session properties:

♦ Select an application connection value configured to send certified messages for each TIBCO target.

♦ Configure a time limit during which the TIBCO daemon attempts to send certified target messages.

♦ Optionally, enter pre-registered listeners that want to receive certified target messages.

If you select a TIB/Adapter SDK application connection, verify that the adapter instance associated with the application connection is configured for certified messages. You can view the adapter instance properties in TIB/Designer. For more information about configuring an adapter instance, consult the TIBCO documentation.

If you select a TIB/Rendezvous application connection, you can view the application connection attributes to verify that the application connection is configured for certified messages. When you configure a TIBCO application connection for certified messages, enter a file-based ledger if you want the TIBCO daemon to be able to resend unconfirmed certified messages.

For an example of a TIBCO application connection configured for certified messages, see Figure 6-2 on page 64. For more information about configuring TIBCO application connections for sending certified messages, see “Managing Connection Objects” in the PowerCenter Workflow Administration Guide.

From the Properties settings on the Targets node of the session properties, enter a value for Time Limit during which the TIBCO daemon can resend undelivered certified target messages. When the time limit expires, the TIBCO daemon no longer resends unconfirmed certified messages.

From the Properties settings on the Targets node of the session properties, enter pre-registered listeners. When you enter pre-registered listeners, the pre-registered subscribers receive all TIBCO target messages during the session run as certified messages.


Figure 6-3 shows the session properties where you enter a time limit for resending unconfirmed certified target messages and pre-registered listeners:

For more information about configuring a time limit and pre-registered listeners for certified messages, see “Configuring a Session with a TIBCO Mapping” on page 68.

Message Recovery

You can configure message recovery for sessions that fail when reading messages from a TIBCO source. When you enable message recovery, the Integration Service stores all messages it reads from the TIBCO source in a cache before processing the messages for the target. If the session fails, run the session in recovery mode to recover the messages the Integration Service could not process during in the previous session run.

During the recovery session, the Integration Service reads the messages from the cache. After the Integration Service reads the messages from the cache and processes them for the target, the recovery session ends.

The Integration Service removes messages from the cache after the Real-time Flush Latency period expires. It also empties the cache at the end of the session. If the session fails after the Integration Service commits messages to the target but before it removes the messages from the cache, targets may receive duplicate rows during the next session run.

Figure 6-3. Target Properties for Writing Certified Messages

Target Session

Properties for

Certified

Messages


To enable session recovery, complete the following tasks:

1. Select a recovery strategy in the session properties.

2. Specify a recovery cache folder in the session properties at each partition point.

If you change the mapping or the session properties and then restart the session, the Integration Service creates a new cache file and then runs the session. This can result in data loss during the session run.

For more information about message recovery, see “Real-time Processing” in the Workflow Administration Guide.

Pipeline Partitioning

You can increase the number of partitions in a pipeline to improve session performance. Increasing the number of partitions allows the Integration Service to create multiple connections to sources and targets and process partitions of data concurrently. While processing TIBCO messages, the Integration Service may process messages out of sequence due to the varying rates at which the partitions process data.

When you create a session in a workflow, the Workflow Manager validates each pipeline in the mapping for partitioning. You can specify multiple partitions in a pipeline if the Integration Service can maintain data consistency when it processes the partitioned data.

Table 6-2 describes the partition types for partition points in TIBCO mappings:

For more information about partitioning and a list of all partitioning restrictions, see the PowerCenter Workflow Administration Guide.

Specifying Partitions and a Recovery Cache Folder

When you specify partitions for a TIBCO mapping in a session, and you configure the Recovery Cache Folder attribute in the session properties, enter a cache folder on a different physical drive for each reader partition in the pipeline for better performance.

Table 6-2. Partition Types for Partition Points in TIBCO Mappings

Partition Point Partition Type

Application Multi-Group Source Qualifier for TIBCO sources Pass-through

TIBCO target All


Configuring a Session with a TIBCO Mapping

When you configure a session using a TIBCO source or target, you need to set the following session properties:

♦ Connection type for Application Multi-Group Source Qualifiers for TIBCO sources

♦ TIBCO event queue information

♦ Connection type for TIBCO targets

You can also configure the session with the following properties:

♦ Commit type and interval

♦ Message recovery

♦ Session conditions

♦ Certified messages for TIBCO targets

♦ Pipeline partitioning

To configure session properties for a TIBCO session:

1. In the Task Developer, double-click a TIBCO session to open the session properties.

2. From the Connections settings on the Mapping tab, select a TIBCO application connection value for Application Multi-Group Source Qualifiers connected to TIBCO source definitions.


If the TIBCO source definition represents metadata for messages in TIB/Rendezvous format, select a TIB/Rendezvous application connection. If the TIBCO source definition represents metadata for messages in AE format, select a TIB/Adapter SDK application connection.

Tip: To read certified messages from TIBCO sources, select TIBCO application connections that are configured for certified messages. For more information about reading certified messages from TIBCO sources, see “Reading Certified Messages from TIBCO Sources” on page 63.

3. From the Connections settings on the Targets node, select a TIBCO application connection value for each TIBCO target definition.

If the TIBCO target definition represents metadata for messages in TIB/Rendezvous format, select a TIB/Rendezvous application connection. If the TIBCO target definition represents metadata for messages in AE format, select a TIB/Adapter SDK application connection.

Tip: To write certified messages to TIBCO targets, select a TIBCO application connections that are configured for certified messages. For more information about writing certified messages to TIBCO targets, see “Writing Certified Messages to TIBCO Targets” on page 64.

4. From the General Options on the Properties tab, verify that the Treat Source Rows As attribute is set to Insert.

5. Select Source as the commit type to extract data in real time.

Commit

Type

Commit

Interval

Recovery

Strategy

Configuring a Session with a TIBCO Mapping 69

6. Optionally edit the commit interval.

7. Select a recovery strategy.

To enable message recovery, select Resume from Last Checkpoint.

If you enable message recovery, you can configure a value for the recovery cache folder from the Properties settings of the Mapping tab (Sources node). Or, use the default cache folder $PMCacheDir\.

8. If you are configuring session properties for a TIBCO source definition, click the Properties settings on the Mapping tab (Sources node). Otherwise, go to step 12.


9. If you do not want to use the default event queue, clear the Use Default Queue option and enter the following queue information:

10. Optionally, edit the values for the Idle Time, Message Count, Reader Time Limit, and/or Real-time Flush Latency session conditions.

The Workflow Manager assigns the following default values to the session conditions:

For more information about session conditions, see “Configuring Session Conditions” on page 60.

11. If you enabled message recovery, you can enter a value for the recovery cache folder. Or, use the default cache folder $PMCacheDir\.

AttributeRequired/ Optional

Description

Queue Name Required Name of the event queue. Enter a queue name if you do not use the default

queue.

Queue Limit

Policy

Optional Select one of the following policies as the queue limit policy:

- NONE. Select when you do not want to remove any events from the event

queue when the queue reaches the maximum event limit. NONE is the

default queue limit policy.

- FIRST. Select when you want to remove the first event in the event queue

when the queue reaches the maximum event limit.

- LAST. Select when you want to remove the last event in the event queue

when the event queue reaches the maximum event limit.

- NEW. Select when you want to remove the newest event in the event queue

when the event queue reaches the maximum event limit.

Queue Maximum

Event Limit

Optional Enter a number for the queue maximum event limit to set the maximum

number of events a queue can contain. Default is 0. If set to 0, the queue does

not use a maximum event limit.

Queue Discard

Amount

Optional Enter a number for the queue discard amount to discard events when the

queue reaches the maximum number of events. Default is 0. If set to 0, the

queue does not discard any events when the queue maximum event is

reached.

If you select NEW as the queue limit policy, you must set the queue discard

amount to one.

Session ConditionDefault

ValueDescription

Idle Time -1 TIBCO daemon can remain idle for an infinite period of time before the

PowerCenter session ends.

Message Count -1 Integration Service can read an infinite number of messages before the

session ends.

Reader Time Limit 0 Integration Service can read source messages from the TIBCO daemon

for an infinite period of time.

Real-time Flush Latency 0 Integration Service does not run the session in real time.


12. If you are configuring session properties for a TIBCO target definition, click the Properties settings on the Mapping Tab (Targets node). Otherwise, go to step 14.

13. Enter the following properties:

Properties Required/ Optional

Description

Reply Subject Optional Identifies PowerCenter as the message sender. If the target definition contains a

reply subject, it overrides the reply subject in the session properties. If you enter

an invalid reply subject, the session fails.

Send Interval Required Minimum amount of time in milliseconds the Integration Service waits between

each message when writing messages to the target. For example, if you set the

send interval to 2, the Integration Service waits at least two milliseconds before

writing messages to the target. Default is 1.

If you set the send interval to 0, the Integration Service writes all messages to the

target simultaneously. If the subscriber is inactive, and you set the send interval

to 0, the session may fail.


14. Click OK to exit the session properties.

Time Limit Optional Time period in seconds during which the Integration Service retains certified

target messages. It retains the messages while waiting for a confirmation

message from subscribers. When the time limit expires, the Integration Service

discards all unconfirmed messages. Default is 0. This means that the Integration

Service retains target messages for an infinite period of time.

Pre-registered

Listeners

Optional Enter any pre-registered listeners to which you want the Integration Service to

send certified target messages during a session run.

When you enter multiple pre-registered listeners, separate the listeners using a

semicolon. All pre-registered listeners use the same subject for TIBCO target

messages during the workflow.

Note: Use only pre-registered listener names that do not contain a semicolon. If

you enter a pre-registered listener name that contains a semicolon, the

Integration Service interprets the pre-registered listener name as two distinct

listeners. For example, you enter listener;1 as a pre-registered listener name.

The Integration Service interprets the pre-registered listener name as two

listeners: listener and 1.

If the mapping contains more than one TIBCO target and two or more targets use

the same pre-registered listener, verify that both targets also use the same

TIBCO application connection.

For more information about entering pre-registered listeners, see “Configuring

Certified Messages” on page 63.

Properties Required/ Optional

Description


Scheduling Workflows

Before you run a session in a workflow, configure and schedule the workflow. You can schedule a workflow to run continuously, run at a given time or interval, or you can manually start a workflow. The Integration Service runs scheduled workflows through the duration of the schedule, unless the workflow fails.

To run a continuous workflow, select Run continuously when you edit the scheduler for the workflow. A continuous workflow starts as soon as the Integration Service initializes. When the workflow stops, it restarts immediately. For more information about scheduling workflows, see the PowerCenter Workflow Administration Guide.


Running Workflows

When you run TIBCO sessions in a workflow, avoid running concurrent sessions that use the same CmName. You set a CmName when you configure TIBCO application connections for reading or writing certified messages during a workflow. When you configure TIBCO sessions, you may configure more than one session with the same application connection for reading or writing certified messages. If you include sessions in a workflow with the same TIBCO application connection, and these sessions run concurrently, CmName conflicts may occur.

Running Workflows 75

Troubleshooting

I ran a session with a TIBCO target in the mapping. I configured the session with a value of 0

for the Send Interval. After writing 200,000 messages, the session failed.

When you run a session to write messages to a TIBCO target, the Integration Service might send messages faster than the TIBCO target can receive them. This might cause the system to run out of memory.

These are the possible workarounds:

♦ Configure the application connection for the TIBCO target to use a file-based ledger. For more information about configuring a file-based ledger, see “Managing Connection Objects” in the PowerCenter Workflow Administration Guide.

♦ Verify that the pre-registered listeners you specified in the session properties are running.

♦ Set the Send Interval on the Targets node of the session properties to 1 or higher.

I ran a session configured for writing certified messages to TIBCO targets. The session

failed to respond.

You may have multiple sessions configured to use the same TIBCO application connection that contains a value for the Ledger File attribute. However, the sessions are configured with different pre-registered listeners. Make sure that sessions using the same TIBCO application connection use the same pre-registered listeners.

I ran a session configured for writing certified messages to TIBCO targets. Before the next

session, I removed pre-registered listeners from the session properties. The session failed

to respond.

When you want to remove one or more pre-registered listeners between session runs, you must also delete the ledger file. Once you remove the pre-registered listeners and the ledger file, you can restart the session.


A p p e n d i x A

TIBCO Datatype

Reference

This appendix includes the following topics:

♦ Overview, 78

♦ TIBCO and Transformation Datatypes, 79

77

Overview

PowerCenter uses the following datatypes in TIBCO mappings:

♦ TIBCO datatypes. TIBCO datatypes appear in TIBCO source and target definitions. PowerCenter supports TIB/Adapter SDK and TIB/Rendezvous datatypes. TIB/Adapter SDK and TIB/Rendezvous datatypes display identically in PowerCenter.

♦ Transformation datatypes. Transformation datatypes are generic datatypes that PowerCenter uses during the transformation process. They appear in all transformations in a mapping.

78 Appendix A: TIBCO Datatype Reference

TIBCO and Transformation Datatypes

When the Integration Service reads data from a TIBCO source, it converts the data in the message header and message data fields to transformation datatypes used in the Application Multi-Group Source Qualifier transformation. When writing data to a TIBCO target, the Integration Service converts the data based on the native datatypes in the target message. The Integration Service converts TIBCO data with TIB/Rendezvous and TIB/Adapter SDK datatypes.

TIB/Rendezvous Datatypes

When the Integration Service reads TIB/Rendezvous messages from a TIBCO source, it converts the TIB/Rendezvous datatypes to transformation datatypes. When it writes TIB/Rendezvous messages to a TIBCO target, it converts the transformation datatypes to TIB/Rendezvous datatypes.

Table A-1 lists the TIB/Rendezvous datatypes that PowerCenter supports, the TIB/Rendezvous datatypes as they appear in PowerCenter, and the corresponding transformation datatypes:

Table A-1. TIB/Rendezvous and Transformation Datatypes

TIB/Rendezvous

Datatype

Range and

Description

TIBCO

Datatype in

the Designer

Transformation

DatatypeRange and Description

TIBRVMSG_MSG Composite

of fields

msg Binary 1 to 104,857,600 bytes You can pass binary data from a

source to a target, but you cannot

perform transformations on binary

data.

Used for collapsed classes.

TIBRVMSG_DATETIME datetime Date/Time Jan 1, 1753 to Dec 31, 9999 AD.

Combined date/time value, with

precision to the second.

TIBRVMSG_STRING ISO 8859-1

character

string

(also called

Latin-1)

string String Unicode mode: (precision + 1) * 2.

ASCII mode: precision + 1.

1 to 104,857,600 characters Fixed-length or varying-length

string.

TIBRVMSG_BOOL T or F bool String Precision of 1.

TIBRVMSG_OPAQUE binary Binary 1 to 104,857,600 bytes You can pass binary data from a



data.

TIBRVMSG_I8 8-bit integer int8 Small Integer Precision of 5 and scale of 0. Integer value.

TIBCO and Transformation Datatypes 79

Unsupported TIB/Rendezvous Datatypes

PowerCenter Connect for TIBCO does not support TIB/Rendezvous array datatypes. For more information about TIB/Rendezvous datatypes, see the TIBCO documentation.

TIBRVMSG_I16 16-bit

integer

int16 Small Integer Precision of 5 and scale of 0. Integer value.

TIBRVMSG_I32 32-bit

integer

int32 Integer Precision of 10 and scale of 0. Integer value.

TIBRVMSG_I64 64-bit

integer

int64 Decimal Precision 1 to 28 digits, scale 0 to

28.

TIBRVMSG_U8 8-bit

unsigned

integer

uint8 Small Integer Precision of 5 and scale of 0. Integer value.

TIBRVMSG_U16 16-bit

unsigned

integer

uint16 Integer Precision of 10 and scale of 0. Integer value.

TIBRVMSG_U32 32-bit

unsigned

integer

uint32 Decimal Precision 1 to 28 digits, scale 0 to

28.

TIBRVMSG_U64 64-bit

unsigned

integer

uint64 Decimal Precision 1 to 28 digits, scale 0 to

28.

TIBRVMSG_F32 32-bit

floating point

real32 Double Precision of 15 digits.

Double-precision floating-point

numeric value.

TIBRVMSG_F64 64-bit

floating point

real64 Double Precision 1 to 28 digits, scale 0 to

28.

TIBRVMSG_IPADDR32 4-byte IP

address

ipaddr32 String Unicode mode: (precision + 1) * 2.



string.

TIBRVMSG_IPPORT16 2-byte IP

port

ipport16 String Unicode mode: (precision + 1) * 2.



string.

TIBRVMSG_XML XML data xml Binary 1 to 104,857,600 bytes You can pass binary data from a



data.

TIB/Rendezvous

Datatype

Range and

Description

TIBCO

Datatype in

the Designer

Transformation



Truncation of TIB/Rendezvous Datatype TIBVMSG_XML

When you run a session with a TIBCO target that contains an XML datatype and the data is truncated, the session discards that row on truncation. Also, the Integration Service writes a warning message to the session log and increments the error count. The session fails only when the error count reaches the threshold. You can define the error count threshold in the session properties.

TIB/Adapter SDK Datatypes

PowerCenter uses TIB/Adapter SDK datatypes when reading and writing TIBCO messages and when importing source or target metadata from a TIB/Repository instance. When the Integration Service reads TIBCO messages in AE format from a TIBCO source, it converts the TIB/Rendezvous datatypes to transformation datatypes. When it writes TIBCO messages in AE format to a TIBCO target, it converts the transformation datatypes to TIB/Rendezvous datatypes.

TIB/Repository uses TIB/Adapter SDK datatypes for TIBCO message metadata stored in TIB/Repository instances. When you import source or target metadata from a TIB/Repository instance, the PowerCenter Designer displays the datatypes for the metadata in PowerCenter-specific format.

Table A-2 lists the TIB/Adapter SDK datatypes that PowerCenter supports, the TIB/Adapter SDK datatypes as they appear in PowerCenter, and the corresponding transformation datatypes:

Table A-2. TIB/Adapter SDK and Transformation Datatypes

TIB/Adapter SDK

Datatype

Range and

Description

TIBCO

Datatype in

the Designer

Transformation


dateTime datetime Date/Time Jan 1, 1753 to Dec 31, 9999 AD.

Combined date/time value, with

precision to the second.

string ISO 8859-1

character

string

(also called

Latin-1)

string String Unicode mode: (precision + 1) * 2.


1 to 104,857,600 characters Fixed-length or varying-length string.

boolean T or F bool String Precision of 1.

binary binary Binary 1 to 104,857,600 bytes You can pass binary data from a source

to a target, but you cannot perform

transformations on binary data.

i1 8-bit integer int8 Small Integer Precision of 5 and scale of 0. Integer value.

i2 16-bit

integer

int16 Small Integer Precision of 5 and scale of 0. Integer value.


Unsupported TIB/Adapter SDK Datatypes

PowerCenter Connect for TIBCO does not support the following TIB/Adapter SDK datatypes:

♦ any

♦ char.n

♦ date

♦ fixed.p.s

♦ interval

♦ sequence

♦ time

♦ union

♦ void

For more information about TIB/Adapter SDK datatypes, see the TIBCO documentation.

i4 32-bit

integer

int32 Integer Precision of 10 and scale of 0. Integer value.

i8 64-bit

integer

int64 Decimal Precision 1 to 28 digits, scale 0 to 28.

ui1 8-bit

unsigned

integer

uint8 Small Integer Precision of 5 and scale of 0. Integer value.

ui2 16-bit

unsigned

integer

uint16 Integer Precision of 10 and scale of 0. Integer value.

ui4 32-bit

unsigned

integer

uint32 Decimal Precision 1 to 28 digits, scale 0 to 28.

ui8 64-bit

unsigned

integer

uint64 Decimal Precision 1 to 28 digits, scale 0 to 28.

r4 32-bit

floating point

real32 Double Precision of 15 digits Double-precision floating-point numeric

value.

r8 64-bit

floating point

real64 Double Precision of 15 digits Double-precision floating-point numeric

value.

TIB/Adapter SDK

Datatype

Range and

Description

TIBCO

Datatype in

the Designer

Transformation



TIB/Adapter SDK Datatype Conversion

PowerCenter workflows with TIB/Adapter SDK application connections do not convert data between compatible datatypes. When you run a session to write messages to a TIBCO target with a TIB/adapter SDK application connection, and the transformation datatype for a field is not identical to the datatype in the target field, the Integration Service loads a null value for the field. This is because TIB/Adapter SDK datatypes cannot convert between compatible datatypes.

To ensure that the Integration Service writes the correct data to the target, verify that the datatypes in the target definition are identical to the transformation datatypes in the transformation that precedes the target in the mapping.


I n d e x

Aadapter instance (TIBCO)

editing the TIBCO adapter instance 14installing 14

application connections (TIBCO)See also PowerCenter Workflow Administration Guideselecting to read certified messages 69selecting to write certified messages 69

Application Multi-Group Source Qualifier (TIBCO)creating 40description 40

Ccertified messages (TIBCO)

reading certified messages 63troubleshooting 76writing certified messages 64

CmName (TIBCO)conflicts 75

code pages (TIBCO)supported 2

continuous workflows (TIBCO)description 74

Ddatatypes (TIBCO)

Application Multi-Group Source Qualifier 40TIB/Adapter SDK datatypes 81TIB/Rendezvous datatypes 79TIBCO 78TIBVMSG_XML 81transformation 78, 79unsupported TIB/Adapter SDK datatypes 82unsupported TIB/Rendezvous datatypes 80

Ggroups (TIBCO)

description 19editing a TIBCO source group 37editing a TIBCO target group 54editing the TIBCO metadata tree 35working with 35, 54

IIdle Time (TIBCO)

configuring 71description 61

infaMetadata adapter instance (TIBCO)See adapter instance

85

installing (TIBCO)TIBCO installation and configuration steps 10

Integration Service (TIBCO)See also PowerCenter Administrator Guideconfiguring 58

Mmap value (TIBCO)

description 21Message Count (TIBCO)


message recovery (TIBCO)See also PowerCenter Workflow Administration Guideconfiguringdescription 66recovery cache folder 67

Nnested messages (TIBCO)

collapsing 24description 5in source and target definitions 23maintaining separate columns 23TIB/Adapter SDK application connections 24

Ppipeline partitioning (TIBCO)

description 67specifying partitions and a file cache folder 67

PowerCenter (TIBCO)integration with TIBCO 3

pre-registered listeners (TIBCO)configuring for certified messages 73

RReader Time Limit (TIBCO)


Real-time Flush Latency (TIBCO)configuring 71configuring continuous workflows 74configuring source-based commit 69description 62

real-time sessions (TIBCO)configuring source-based commit 62defined 62Real-time Flush Latency session condition 62

recovery (TIBCO)See message recovery

recovery cache folder (TIBCO)for message recovery 67

SSecure daemons (TIBCO)

Rendezvous secure communications daemon 7Rendezvous secure routing daemon 7

Send Interval session property (TIBCO)troubleshooting 76

session conditions (TIBCO)description 60entering 60Idle Time 61Message Count 61Reader Time Limit 62Real-time Flush Latency 62

session recovery (TIBCO)specifying partitions and a file cache folder 67

sources and targets (TIBCO)installing the TIBCO adapter instance 14

subject (TIBCO)overwriting default subject in TIBCO targets 42

TTIB/Adapter SDK 4.1.2 (TIBCO)

installing and configuring 10TIB/Adapter SDK application connections (TIBCO)

nested messages 24TIB/AdapterAdministrator (TIBCO)

installing and configuring 11installing the infaMetadata adapter instance 14

TIB/Designer (TIBCO)installing and configuring 11installing the infaMetadata adapter instance 14

TIB/Rendezvous (TIBCO)installing and configuring 10integration with PowerCenter 6

TIB/Repository (TIBCO)description 5importing a TIBCO source definition 27importing a TIBCO target definition 47installing and configuring 11

86 Index

TIBCO (TIBCO)integration with PowerCenter 3products 10

TIBCO adapter instance (TIBCO)description 14

TIBCO daemon (TIBCO)description 6

TIBCO event queue (TIBCO)configuring 71description 59

TIBCO libraries (TIBCO)renaming 13

TIBCO messages (TIBCO)description 4message fields 4nested messages 5

TIBCO metadata tree (TIBCO)description 21editing 35map values 21

TIBCO source definition (TIBCO)creating manually 31editing 32editing a group 37importing from TIB/Repository 19nested messages 23overview 18, 26TIB/Repository 27working with a group 35, 54

TIBCO target definition (TIBCO)creating from a relational or flat file source definition

44creating from a TIBCO source 43creating manually 50editing 51editing a group 54importing from TIB/Repository 19nested messages 23overview 42working with a group 35, 54

TIBVMSG_XML datatype (TIBCO)truncating 81

Time Limit (TIBCO)configuring to send certified messages 64, 73

troubleshooting (TIBCO)workflows 76

Wworkflows (TIBCO)

CmName conflicts 75

configuring sessions in a workflow 68overview 58running 75scheduling 74

Index 87

88 Index

powercenter connect for tibco 8.1.1 user guide documentation/1/pcco… · powercenter connect for...

Documents