CDE 44 Administrator Guide

8/6/2019 CDE 44 Administrator Guide

http://slidepdf.com/reader/full/cde-44-administrator-guide 1/100

Complex Data ExchangeAdministrator Guide

Informatica Complex Data Exchange™(Version 4.4)



Complex Data Exchange Administrator GuideVersion 4.4 August 2007

Copyright © 2001–2007 Informatica Corporation. All rights reserved.

This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containingrestrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may bereproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. ThisSoftware is protected by U.S. Patent Numbers and other Patents Pending.

Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and asprovided 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 software and documentation is subject to change without notice. Informatica Corporation does not warrant that this software ordocumentation is error free.

Informatica, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, InformaticaData Quality, Informatica Data Explorer, Informatica Complex Data Exchange and Informatica On Demand Data Replicator are trademarks or registeredtrademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be tradenames 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 © Sun Microsystems. Allrights reserved. Copyright 1985-2003 Adobe Systems Inc. All rights reserved. Copyright 1996-2004 Glyph & Cog, LLC. All rights reserved.

This product includes software developed by Boost (http://www.boost.org/). Permissions and limitations regarding this software are subject to terms available athttp://www.boost.org/LICENSE_1_0.txt.

This product includes software developed by Mozilla (http://www.mozilla.org/). Your right to use such materials is set forth in the GNU Lesser General PublicLicense Agreement, which may be found at http://www.gnu.org/licenses/lgpl.html. The Mozilla 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 particularpurpose.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/) which is licensed under the Apache License, Version 2.0(the “License”). You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing,software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express orimplied. See the License for the specific language governing permissions and limitations under the License.

This product includes software developed by SourceForge (http://sourceforge.net/projects/mpxj/). Your right to use such materials is set forth in the GNU LesserGeneral Public License Agreement, which may be found at http://www.gnu.org/licenses/lgpl.html. The SourceForge 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 fitnessfor a particular purpose.

This product includes Curl software which is Copyright 1996-2007, Daniel Stenberg, <[email protected]>. All Rights Reserved. Permissions and limitationsregarding this software are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission to use, copy, modify, and distribute this software forany purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

This product includes ICU software which is Copyright (c) 1995-2003 International Business Machines Corporation and others. All rights reserved. Permissionsand limitations regarding this software are subject to terms available at http://www-306.ibm.com/software/globalization/icu/license.jsp

This product includes OSSP UUID software which is Copyright (c) 2002 Ralf S. Engelschall, Copyright (c) 2002 The OSSP Project Copyright (c) 2002 Cable& Wireless Deutschland. Permissions and limitations regarding this software are subject to terms available at http://www.opensource.org/licenses/mit-license.php.

This product includes Eclipse software which is Copyright (c) 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding thissoftware are subject to terms available at http://www.eclipse.org/org/documents/epl-v10.php

libstdc++ is distributed with this product subject to the terms related to the code set forth at http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/license.html.

DISCLAIMER: Informatica Corporation provides this documentation “as is” without warranty of any kind, either express or implied, including, but not limitedto, the implied warranties of non-infringement, merchantability, or use for a particular purpose. The information provided in this documentation may includetechnical inaccuracies or typographical errors. Informatica could make improvements and/or changes in the products described in this documentation at any time without notice.

Part Number: CDE-ADM-44000-0001



ii i

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xDocument Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Other Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiVisiting Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . . xiVisiting the Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiVisiting the Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . . xi

Obtaining Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiOnline Conversion Agent Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Chapter 1: Overvi ew. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Essential Administrative Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Installing Complex Data Exchange on Windows . . . . . . . . . . . . . . . . . . . 2

Installing Complex Data Exchange on UNIX . . . . . . . . . . . . . . . . . . . . . . 2Testing the Complex Data Exchange Installation . . . . . . . . . . . . . . . . . . . 2Running Data Transformations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Configuring Complex Data Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Upgrading Existing Data Transformations . . . . . . . . . . . . . . . . . . . . . . . . 3Using ODBC Database Support Features . . . . . . . . . . . . . . . . . . . . . . . . . 3Deploying Complex Data Exchange in an Organization . . . . . . . . . . . . . . 3

Complex Data Exchange Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2: System Requi rements . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Supported Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8UNIX-Type Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Java Runtime Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Windows System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

JRE Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Solaris System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Solaris 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Solaris 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

http://-/?-

http://-/?-



iv Table of Contents

Solaris 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Confirming Packages and Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12


AIX System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 AIX 5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 AIX 5.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Confirming Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15


Linux System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17SUSE Linux 9 and Red Hat Linux EL3 on x86 . . . . . . . . . . . . . . . . . . . . 17SUSE Linux 9 and Red Hat Linux EL4 on x86-64 . . . . . . . . . . . . . . . . .17Confirming Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

HP-UX System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

HP-UX 11.23 on PA-RISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18HP-UX 11.23 on ia64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Confirming Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Third-Party Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Microsoft Office Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20PDF and COBOL Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 3: Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Upgrading from a Previous Version . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Running the Setup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Post-Setup Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Installing a License File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Loading Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Configuring In-Process or Out-of-Process Invocation . . . . . . . . . . . . . . . 26Configuring ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Testing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Uninstalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28



v

Chapter 4: Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Loading the Environment Variables on UNIX Platforms . . . . . . . . . . . . . . . . 31

Loading from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Loading Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31UNIX Environment Variable Reference . . . . . . . . . . . . . . . . . . . . . . . . . 32Example of Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Windows Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Chapter 5: Testing and Troubleshoot ing . . . . . . . . . . . . . . . . . . . . . . .35

Complex Data Exchange Engine Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Document Processor Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Installation Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

UNIX Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Java Heap and Stack Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Preventing Core-File Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40LDR_CNTRL Environment Variable on AIX . . . . . . . . . . . . . . . . . . . . 40LD_PRELOAD Environment Variable on HP-UX . . . . . . . . . . . . . . . . . 40Memory Allocation on HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Emulators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Asian Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Chapter 6: Runni ng Data Transformations . . . . . . . . . . . . . . . . . . . . .43

Designing and Configuring Data Transformations . . . . . . . . . . . . . . . . . . . . 44Deploying Complex Data Exchange Services . . . . . . . . . . . . . . . . . . . . . . . . 45

Repository Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Deploying on the Studio Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Deploying on Another Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Re-Deploying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Running Complex Data Exchange Services . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 7: Runni ng In-Process or Out-of-Process . . . . . . . . . . . . . . .49

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Relative Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Determining whether to Run In-Process or Out-of-Process . . . . . . . . . . . 50

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52



vi Table of Contents

Chapter 8: Configuration Edi tor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Using the Configuration Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Backing Up the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Assigning the Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Missing Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Saving the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58Directory Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Copying the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Multiple Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Creating Multiple Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60Selecting the Configuration at Runtime . . . . . . . . . . . . . . . . . . . . . . . . . 60Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Multiple JREs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Running Multiple Configurations Concurrently . . . . . . . . . . . . . . . . . . . 61

Chapter 9: Upgrading Complex Data Exch ange Projects . . . . . . . . . .63

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 When Is Upgrading Necessary? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Upgrading an Individual Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Upgrading a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65Syntax Conversion Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Version Support on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Version Support on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Before Running the Tool: Organize Your Projects . . . . . . . . . . . . . . . . . .66Running the Syntax Conversion Tool . . . . . . . . . . . . . . . . . . . . . . . . . . 67Running from the Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Upgrade Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70New and Modified Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Modified Namespace for Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70Unsupported File and Directory Names . . . . . . . . . . . . . . . . . . . . . . . . . 70

XSD Schemas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

Chapter 10: Using Complex Data Exchange with ODBC . . . . . . . . . .73Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74



Table of Contents vii

Installing and Configuring an ODBC Manager on UNIX . . . . . . . . . . . . . . . 75Installing an ODBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Defining DSNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Using a DSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Chapter 11: Administ ration and Deployment Policies . . . . . . . . . . . . 77

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Studio Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Engine Runtime Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Standard Windows User Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Multiple Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Copying the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Deploying Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Running on a Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Sizing Guidelines for SAP XI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Backup Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Production Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Development Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Failure Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

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

http://-/?-

http://-/?-



viii Table of Contents



ix

Preface

Welcome to Informatica Complex Data Exchange, the leading software for automatingcomplex data transformations in high-performance, transaction-intensive applications and

service oriented architectures. Complex Data Exchange enables organizations to define,deploy, and reuse data transformations without writing code. You can use Complex DataExchange to transform any data format to any data format, whether the data is structured orunstructured, and whether it exists in an XML, text, or binary representation.

Complex Data Exchange Studio is a visual design environment for data transformations.Complex Data Exchange Engine is the runtime environment for transformation services. TheComplex Data Exchange libraries provide predefined transformations supporting industry standard data formats.

Complex Data Exchange is fully integrated with Informatica PowerCenter and withnumerous external systems. PowerCenter applications use the Complex Data Transformationto activate Complex Data Exchange services and perform data transformations.



x Preface

About This Book

The Complex Data Exchange Administrator Guide is written for system administrators andusers who are responsible for installing the Complex Data Exchange software and maintaining

or configuring its operation. It contains instructions and information regarding both Windows and UNIX-type platforms.

Document ConventionsThis 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 anoperating system command. This is generic text that should bereplaced 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 overwriteor 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 torun a task.



Preface xi

Other Informatica Resources

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

♦ Informatica Customer Portal♦ Informatica web site♦ Informatica Knowledge Base♦ Informatica Global Customer Support

Visiting Informatica Customer Portal

As an Informatica customer, you may 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 theInformatica user community.

Visiting the Informatica Web Site

You may access the Informatica corporate web site at http://www.informatica.com. The sitecontains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includesimportant information about technical support, training and education, and implementationservices.

Visiting the Informatica Knowledge Base

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

Obtaining Customer SupportThere are many ways to access Informatica Global Customer Support. You may contact aCustomer Support Center by using the telephone numbers listed the following table, you cansend email, or you can use the WebSupport Service.

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

♦ [email protected] for technical inquiries♦ [email protected] for general customer service requests



xii Preface

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

No r th A mer i ca / S ou t h A m er i ca Eu r op e / M id dl e Eas t / A f ri c a A s ia / A us t ral i a

Informatica Corporation Headquarters100 Cardinal WayRedwood City, California94063United States

Toll Free877 463 2435

Standard RateUnited States: 650 385 5800

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

Toll Free00 800 4632 4357

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

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

Toll FreeAustralia: 00 11 800 4632 4357Singapore: 001 800 4632 4357

Standard RateIndia: +91 80 4112 5738



1

Chapter 1

Overview

This chapter includes the following topics:

♦ Essential Administrative Tasks, 2♦ Complex Data Exchange Modules, 4♦ Terminology, 5



2 Chapter 1: Overview

Essential Administrative Tasks

This book explains how to administer the Complex Data Exchange data transformationsoftware. It covers subjects such as installing and configuring Complex Data Exchange,

diagnosing and solving system problems, and administering Complex Data Exchange on anetwork.

The following paragraphs outline some of the essential administrative tasks.

Installing Complex Data Exchange on WindowsFor information about installing Complex Data Exchange on Microsoft Windows systems,

read the following chapters:♦ “System Requirements” on page 7♦ “Installation” on page 21

Installing Complex Data Exchange on UNIXComplex Data Exchange runs on UNIX-type operating systems such as Solaris, AIX, HP-UX,

and Linux. For the installation and required configuration instructions, read:♦ “System Requirements” on page 7♦ “Installation” on page 21♦ “Environment Variables” on page 29

Testing the Complex Data Exchange Installation

To confirm that Complex Data Exchange is correctly installed, see:♦ “Testing and Troubleshooting” on page 35

Running Data TransformationsIf you are a system administrator who is responsible for Complex Data Exchange operations,you should be aware of the ways in which users may run data transformations and services in

Complex Data Exchange. For an overview, see:♦ “Running Data Transformations” on page 43

Configuring Complex Data Exchange After you have installed Complex Data Exchange, you can edit the configuration, forexample, to:

♦ Invoke Complex Data Exchange either in-process or out-of-process of its callingapplication



Essential Administrative Tasks 3

♦ Change the locations where Complex Data Exchange stores deployed services or error logs♦ Change the Java Runtime Environment (JRE) that Complex Data Exchange uses♦ Adjust performance parameters

For these subjects, see:

♦ “Running In-Process or Out-of-Process” on page 49♦ “Configuration Editor” on page 55

Upgrading Existing Data TransformationsIf you have upgraded from a previous Complex Data Exchange version, you must alsoupgrade the data transformation projects and services that you run in Complex DataExchange. For more information, see:♦ “Upgrading Complex Data Exchange Projects” on page 63

Using ODBC Database Support FeaturesIf you plan to use the Complex Data Exchange ODBC database support features, read:

♦ “Using Complex Data Exchange with ODBC” on page 73

Deploying Complex Data Exchange in an OrganizationIf you are deploying Complex Data Exchange to multiple computers throughout anorganization, you need to:

♦ Install Complex Data Exchange on multiple workstations and servers♦ Implement security policies♦ Replicate the Complex Data Exchange services on multiple servers♦ Back up the Complex Data Exchange configurations, projects, services, and data

For these subjects, see:

♦ “Administration and Deployment Policies” on page 77




Complex Data Exchange Modules

This book describes the installation and administration of the following Complex DataExchange modules:

In addition to the above modules, there are optional integration agents that interfaceComplex Data Exchange with third-party software systems. For information about installingand administering these agents, see the manual for each agent.

ModuleRequired/Optional

Description

Complex Data ExchangeEngine

Required The runtime module that executes Complex Data Exchange datatransformations. This module is required in all Complex Data Exchangeinstallations.Complex Data Exchange Engine runs on both Windows and UNIX-typeplatforms.

Complex Data ExchangeStudio

Optional The design and configuration environment where you can create anddeploy data transformations.Complex Data Exchange Studio is hosted within Eclipse on Windowsplatforms. The Eclipse setup is included in the Complex Data Exchangeinstallation package.

Document Processors Optional A set of components that perform global processing operations ondocuments, such as transforming their file formats.All the document processors run on Windows platforms, and most of themrun on UNIX-type platforms.

Libraries Optional Libraries of predefined Complex Data Exchange data transformations,which you can use with industry messaging standards such as EDI,ACORD, HL7, HIPAA, and SWIFT. Each library contains parsers,serializers, and XSD schemas for the appropriate messaging standard.You can install the libraries on Windows platforms. You can use ComplexData Exc hange Studio to import the library components to your projects,and deploy the projects to Windows or UNIX-type platforms.

Online Documentation Optional An online help library, containing all the Complex Data Exchangedocumentation.You can install the documentation on Windows platforms. For use on UNIX-type platforms, you can use the PDF versions of the documents.



Terminology 5

Terminology

In the course of installing and administering the Complex Data Exchange software, you arelikely to encounter the following terms. These terms are explained in detail in other manuals,

such as Getting Started with Complex Data Exchange . The following are brief definitions.

Term Definit ion

Data transformation The conversion of data from one structure or format to another, possiblyaccompanied by modification of the data values.

Project A collection of files and resources that are necessary to define and execute adata transformation. Each project is stored in a directory.

Complex Data Exchange service A data transformation that is available to be executed in Complex DataExchange Engine.

Complex Data Exchange repository The location where Complex Data Exchange services are stored.

Deploy Copy a project to the Complex Data Exchange repository, thereby making itavailable as a Complex Data Exchange service.

JRE Java Runtime Environment, required to install and run Complex DataExchange. Also known as JVM, Java Virtual Machine.






7

Chapter 2

System Requirements


♦ Supported Systems, 8♦ Windows System Requirements, 10♦ Solaris System Requirements, 11♦ AIX System Requirements, 14♦ Linux System Requirements, 17♦ HP-UX System Requirements, 18♦ Third-Party Applications, 20



8 Chapter 2: System Requirements

Supported Systems

You can install and run Complex Data Exchange on the following operating systems.

Microsoft WindowsOn Microsoft Windows, you can install all Complex Data Exchange modules such asComplex Data Exchange Engine, Complex Data Exchange Studio, the document processors,and the libraries.

Hardware Requirements

The minimum RAM requirement is 128 MB. For a system running production ComplexData Exchange services, we recommend at least 512 MB of RAM and a CPU speed of at least1 GHz.

UNIX-Type SystemsOn UNIX-type operating systems, you can install Complex Data Exchange Engine and thedocument processors. Complex Data Exchange supports the following UNIX-type systems:

♦ Sun Solaris♦ IBM AIX ♦ Linux♦ Hewlett-Packard HP-UX

The following Complex Data Exchange features are not available on UNIX:

♦ The COM API, which requires the Microsoft Windows COM architecture♦ Custom COM components, such as ExternalCOMPreProcessor or ExternalCOMAction

♦ Document processors that require Microsoft Office applications on the same computer,such as ExcelToHtml , ExcelToTxt , PowerpointToHtml , WordToHtml , WordToTxt , and

WordToRtf

The Java document processors for Microsoft Office documents, such asExcelToXml , WordToXml , and XmlToExcel , do not require the Office applications and operate on UNIX.

Hardware RequirementsThe minimum RAM requirement is 256 MB. For a system running production ComplexData Exchange services, we recommend at least 512 MB of RAM and a CPU speed of at least1 GHz.

Recommended Configuration

On UNIX-type operating systems, do not limit the data size and the stack size. To determine whether there is currently a limitation, run the following command:



Supported Systems 9

♦ For AIX, HP, and Solaris: ulimit –a

♦ For Linux: limit

If you process very large documents using Complex Data Exchange, try adjusting systemparameters such as the memory size and the file size.

Java Runtime Environment A Java 2 Runtime Environment (JRE) is required. By default, the Complex Data Exchangesetup installs a JRE on your computer.

Optionally, you can use another JRE version, which you install independently on thecomputer. For the supported JRE versions, see the specific requirements for your operatingsystem.

After you install Complex Data Exchange, it is possible to change the selected JRE. Forexample, you can change from a client JRE to a server JRE. For more information, see“Configuration Editor” on page 55 and “UNIX Environment Variable Reference” onpage 32.

JRE for Use with Java API

If you use the Complex Data Exchange Java API to activate a Complex Data Exchangeservice, any Java components of the service run on the JRE that is used by the external Javaapplication.

For consistency of operation, this should be the same JRE as the one that you configured within Complex Data Exchange. In any event, it must be a JRE version that Complex DataExchange supports.

For more information, see “Running In-Process or Out-of-Process” on page 49.



10 Chapter 2 : Sys tem Requi rements

Windows System Requirements

You can install Complex Data Exchange on a system conforming to the followingrequirements:

♦ Microsoft Windows 2000 SP4, XP Professional SP2, or 2003 Server SP1 (32-bit or 64-bitedition).

Complex Data Exchange Studio is not currently supported on the 64-bit edition of Windows.

♦ Microsoft Internet Explorer, version 6.0 or higher.♦ For Complex Data Exchange Studio: Microsoft .NET Framework, version 2.0. If you do

not have this version installed on your computer, the Complex Data Exchange setupprogram installs it automatically.

JRE VersionComplex Data Exchange requires a Sun Java 2 Runtime Environment, version 1.5.0. You canuse the JRE that is installed with Complex Data Exchange, or you can download a JRE fromhttp://www.sun.com .

The JRE does not need to be defined in your PATH environment variable. In rare instances, theComplex Data Exchange Java document processors might require that the JRE be defined inthe PATH for proper operation.

Disk SpaceThe Complex Data Exchange Engine and Studio software require approximately 200 MB of disk space.

To install the optional Complex Data Exchange libraries, reserve additional space. For moreinformation, see Complex Data Exchange Libraries .

http://www.sun.com/

http://www.sun.com/



Solaris System Requirements 11

Solaris System Requirements

Complex Data Exchange is supported on Sun Solaris on the SPARC platform.

Solaris 8 You can run Complex Data Exchange on Solaris 8 2/04, on the SPARC platform. Thefollowing packages and patches must be installed:

Solaris 9

You can run Complex Data Exchange on Solaris 9 4/03, on the SPARC platform. Thefollowing packages and patches must be installed:

Package Minimum Version

SUNWcsl 11.8.0,REV=2000.01.08.18.12

SUNWlibC 5.8,REV=99.06.09

SUNWlibms 5.8,REV=1999.10.21

SUNWuiu8 1.5,REV=1999.12.03.14.40

Patch Minimum Version

108434 17

108435 17

108993 36

109147 28

109384 07

110815 01

111327 05

111562 02

111721 04

113261 02


SUNWcsl 11.9.0,REV=2002.04.06.15.27

SUNWlibC 5.9,REV=2002.03.18


SUNWuiu8 1.5,REV=2002.02.02.16.55




Solaris 10 You can run Complex Data Exchange on Solaris 10, also known as SunOS 5.10, on theSPARC platform. The following packages and patches must be installed:


111711 12

111712 12

111722 04

112233 12

112839 08

112874 31

112963 25

113029 06

113319 22

113896 06


SUNWcsl 11.10.0,REV=2005.01.21.15.53

SUNWcslr 11.10.0,REV=2005.01.21.15.53

SUNWcsr 11.10.0,REV=2005.01.21.15.53

SUNWlibC 5.10,REV=2004.12.22


SUNWlibmsr 5.10,REV=2004.11.23

SUNWuiu8 1.5,REV=2004.11.24.10.12


118833 36

118918 24

119042 10

119254 38

119578 30

119963 08

120068 03

120753 05



Solaris System Requirements 13

Confirming Packages and PatchesTo confirm that a required package has been installed, run the following command:

pkginfo -l package_name

For example, to determine whether the SUNWcsl package is installed, run the command:pkginfo -l SUNWcsl

To confirm that a required patch has been installed, run the command:

showrev -p | grep patch_number

For example:

showrev -p | grep 111711

The commands display whether a package or patch is installed, and its version number.

JRE VersionComplex Data Exchange requires a Sun Java 2 Runtime Environment, version 1.5.0. You canuse the JRE that is installed with Complex Data Exchange, or you can download a JRE fromhttp://www.sun.com .

Disk Space A full Complex Data Exchange installation on Solaris requires approximately 160 MB of disk space.

120900 04

121133 02

121683 05

122032 04


AIX S t R i t

http://www.sun.com/

http://www.sun.com/




AIX System Requirements

Complex Data Exchange is supported on IBM AIX.

AIX 5.2 You can run Complex Data Exchange on AIX 5.2 with maintenance level 3. The followingpackages must be installed:

AIX 5.3 You can run Complex Data Exchange on AIX 5.3 with maintenance level 0. The followingpackages must be installed:

On some AIX 5.3 computers, the Complex Data Exchange setup fails to run unless youconfigure the LDR_CNTRLenvironment variable. If the setup fails to start, configure thevariable as follows.

To conf igure the LDR_CNTRL var iab le :

1 . Determine the existing value of theLDR_CNTRLvariable, if any. To do this, enter thefollowing command:

echo $LDR_CNTRL

Save the result, if it is not empty.

2 . If you use the sh , ksh , or bash shell, add the following lines to.profile :LDR_CNTRL=NOKTRL

export LDR_CNTRL

Package Version PTF

bos.rte.bind_cmds 5.2.0.30 ML 3

bos.rte.libc 5.2.0.30 ML 3

bos.rte.libpthreads 5.2.0.30 ML 3

xlC.rte 6.0.0.0 ML 3

Package Version PTF

bos.rte.bind_cmds 5.3.0.10 ML 0

bos.rte.libc 5.3.0.10 ML 0

bos.rte.libpthreads 5.3.0.10 ML 0

xlC.rte 6.0.0.0 ML 0

If the result of step 1 was not empty you must append it to the NOKTRLvalue Substitute



AIX System Requirements 15

If the result of step 1 was not empty, you must append it to the NOKTRLvalue. Substitutethe following syntax including the quotation marks:

LDR_CNTRL="NOKTRLresult_of_step_1 "

export LDR_CNTRL

3. If you use the csh or tcsh shell, add the following line to your~/.cshrc or ~/.tcshrc file:

setenv LDR_CNTRL NOKTRL

If the result of step 1 was not empty, substitute the following syntax including thequotation marks:

setenv LDR_CNTRL " NOKTRL result_of_step_1 "

4. To ensure that the environment variable takes effect, log out and log back in.

Confirming Packages

To d e t e r m i n e w h i c h m a i n t e n a n c e l e v e l i s i n s t a l le d :

Run the following command:oslevel -r

To v e r i f y t h a t a r e q u i r e d p a c k a g e i s i n s t a l l e d :

1 . Run the following command, which opens the system management console:smitty

2. Select the options Software Installation and Maintenance > List Software and RelatedInformation > List Installed Software and Related Information > List Installed Software.

The package name should be displayed in the list.3. To confirm the version number of a package, run the following command:

lslpp -l | grep package_name

For example, to determine whether the xlC package is installed, run the command:lslpp -l | grep xlC

The version number appears.

JRE VersionComplex Data Exchange requires a Java 2 Runtime Environment, version 1.5.0. You can usethe JRE that is installed with Complex Data Exchange, or you can download a JRE fromhttp://www.ibm.com .

Disk Space

http://www.ibm.com/

http://www.ibm.com/




Disk Space A full Complex Data Exchange installation on AIX requires approximately 190 MB of disk space. The setup requires that you have at least this amount of free space in thetemp directory. To verify the free space, run the following command:

df -k

Linux System Requirements



Linux System Requirements 17

Linux System Requirements

Complex Data Exchange is supported on SUSE and Red Hat versions of Linux.

SUSE Linux 9 and Red Hat Linux EL3 on x86 You can run Complex Data Exchange on SUSE Linux version 9 and on Red Hat Linuxversion EL3, on an Intel x86 or compatible platform. The following packages must beinstalled:

Complex Data Exchange requires a Sun Java 2 Runtime Environment, version 1.5.0. You canuse the JRE that is installed with Complex Data Exchange, or you can download a JRE fromhttp://www.sun.com .

SUSE Linux 9 and Red Hat Linux EL4 on x86-64 You can run Complex Data Exchange on SUSE Linux version 9 and on Red Hat Linuxversion EL4, on x86-64 platforms such as AMD Opteron.

Complex Data Exchange requires an IBM Java 2 Runtime Environment, version 1.5.0. Youcan use the JRE that is installed with Complex Data Exchange, or you can download a JREfrom http://www.ibm.com .

Confirming PackagesTo determine whether a required package is installed, run the following command:

rpm -qa | grep package_name

For example, to determine whether the glibc package is installed, run the command:

rpm -qa | grep glibc

The version number of the package appears.

Disk Space A full Complex Data Exchange installation on Linux requires approximately 150 MB of disk space.

Package Version Minimum Revision

glibc 2.3.2 11.9

libgcc 3.2.2 5

libstdc++ 3.2.2 5

compat-glibc 7.x-2.2.4.32.5.i386.rpm

compat-libstdc++ 7.3-2.96.122.i386.rpm

HP-UX System Requirements

http://www.sun.com/

http://www.ibm.com/

http://www.ibm.com/

http://www.sun.com/




HP UX System Requirements

Complex Data Exchange is supported on Hewlett-Packard HP-UX.

HP-UX 11.23 on PA-RISC You can run Complex Data Exchange on HP-UX 11.23, also known as version B.11.23 9000/800, on the PA-RISC architecture. The following patches must be installed:

Complex Data Exchange requires an HP Java 2 Runtime Environment, version 1.5.0, and the Java “-AA” add-on. You can use the JRE that is installed with Complex Data Exchange, oryou can download a JRE fromhttp://www.hp.com .

HP-UX 11.23 on ia64 You can run Complex Data Exchange on HP-UX 11.23, also known as version B.11.23 9000/

800, on the ia64 architecture (Intel Itanium). The following patches must be installed:


BUNDLE11i B.11.23.0409.3

FEATURE11i B.11.23.0505.022eHPUXBaseOS B.11.23

HWEnable11i B.11.23.0505.022b

PHCO_32489

PHKL_31500

PHKL_33312

PHSS_32502

PHSS_33263

PHSS_33349

QPKAPPS B.11.23.0505.022

QPKBASE B.11.23.0505.022


PHCO_35524 1.0

PHCO_35997 1.0

PHKL_35029 1.0

PHKL_36244 1.0

PHSS_33350 1.0


http://www.hp.com/

http://www.hp.com/



HP-UX System Requirements 19

Complex Data Exchange requires an HP Java 2 Runtime Environment, version 1.5.0. You canuse the JRE that is installed with Complex Data Exchange, or you can download a JRE from

http://www.hp.com .

Confirming Bundles

To c o n f i r m t h a t t h e r e q u i r e d b u n d l e s h a ve b e e n i n s t a l l e d :

Run the following command:/usr/sbin/swlist

Disk Space A full Complex Data Exchange installation on HP-UX requires approximately 280 MB of disk space.

PHSS_34043 1.0

PHSS_34859 1.0

PHSS_35165 1.0

PHSS_35528 1.0

PHSS_35535 1.0

PHSS_36336 1.0


Third-Party Applications

http://www.hp.com/

http://www.hp.com/




y pp

You can use Complex Data Exchange with documents that are generated by a large number of third-party applications. The following applications are among those that are currently

supported.

Microsoft Office ApplicationsTo help you parse Microsoft Office documents, such as Word, Excel, or PowerPoint files,Complex Data Exchange offers several document processors, which convert Microsoft Officedocuments to a format such as text, HTML, RTF, or XML. Office versions 97 and higher aresupported.

The text, HTML, and RTF processors run on Microsoft Windows platforms where the Officeapplications are installed.

The XML processors do not require the Office application. They run on both Windows andUNIX-type platforms.

For more information, see “Document Processors” in theComplex Data Exchange Studio User Guide .

PDF and COBOL SupportComplex Data Exchange contains built-in support for the Adobe Acrobat (PDF) format andfor COBOL data formats. You do not need to install any Acrobat or COBOL software toprocess these file types.

For more information about the PDF support, see “Document Processors” in the Complex Data Exchange Studio User Guide . For more information on COBOL support, see Processing

COBOL Data in Complex Data Exchange .



21

Chapter 3

Installation


♦ Overview, 22♦ Running the Setup Wizard, 23♦ Post-Setup Steps, 26♦ Uninstalling, 28

Overview



22 Chapter 3: Installation

This chapter explains how to install Complex Data Exchange on your computer. It coversinstallation on both Windows and UNIX-type platforms.

Upgrading from a Previous Version

From Version 3.x or Earlier When upgrading from Complex Data Exchange version 3.2 or earlier, you must uninstall theexisting version before installing the new version.

From Version 4.x When upgrading from an earlier Complex Data Exchange 4 release, or if you are installing aComplex Data Exchange service pack, you do not need to uninstall before installing the new version.

Before starting the upgrade, shut down all applications that use Complex Data Exchange.Otherwise, the setup cannot replace certain files, and the upgrade might fail.

Upgrading Multiple ComputersUpgrade all Complex Data Exchange computers and components in your organization at thesame time. This avoids version conflicts between projects that you develop on one computerand run on another computer.

Upgrading Projects

You can upgrade existing Complex Data Exchange projects and run them in the new version.For more information, see “Upgrading Complex Data Exchange Projects” on page 63.

Installing Multiple Complex Data Exchange VersionsIn Windows, it is not possible to install multiple versions or copies of Complex DataExchange on the same computer.

On UNIX-type systems, it is possible to install multiple versions or copies in differentdirectories, provided that you start each copy with the appropriate environment variables. Formore information, see “Environment Variables” on page 29.

Running the Setup Wizard



Running the Setup Wizard 23

To install the Complex Data Exchange software, you should run the setup wizard. In someComplex Data Exchange versions, the sequence of the wizard pages might differ slightly fromthe sequence described here.

To r u n t h e S e t u p w i z ar d :

1 . Open the setup wizard.♦ On Windows: Log on as a user with administrative privileges for the local computer,

and double-click the Setup.exe file.♦ On UNIX in graphical mode: Execute the appropriate setup file for your operating

system, for example:./Setup_Aix.bin

♦ On UNIX in console mode: If you cannot view the graphical setup interface, forexample, if you are working from a remote location, add the-console switch to thecommand../Setup_Aix.bin -console

2. You are prompted to select the language of the setup wizard.

This option also sets the default language of the Complex Data Exchange user interface.On Windows, it sets the language of the online documentation. Following installation,you can change the user-interface language in the Complex Data ExchangeConfiguration Editor.

On Windows: if you plan to change the language in the Configuration Editor, you mustselect a non-English language for the setup. If you select English, some of the servicesrequired for other languages might not be installed.

3. Follow the on-screen instructions to start the setup and accept the Complex DataExchange license.

4. On the Install Path page, select the directory path where the setup should install theComplex Data Exchange software.♦ On Windows: The default path is c:\Program Files\Informatica\

ComplexDataExchange .♦

On UNIX: The default path is /opt/Informatica/ComplexDataExchange .Throughout this book, we refer to the directory path that you select as<INSTALL_DIR> .

5 . You are prompted to select the Complex Data Exchange components to install. There areoptions for components such as:




opt o s o co po e ts suc as:

For more information about the modules, see “Complex Data Exchange Modules” on

page 4.6 . On the Java Path page, select the Java Runtime Environment that you will use with

Complex Data Exchange. The default is a JRE that the setup installs in the ComplexData Exchange directory. Optionally, you can browse to another supported JRE, which isalready installed on your computer.♦ On Windows: The default JRE path is <INSTALL_DIR>\jre1.4 .♦ On UNIX: The default JRE path is <INSTALL_DIR>/jre1.4/jre .

Following installation, it is possible to change the path and use a different JRE. On Windows, you can edit the JRE path in the Complex Data Exchange ConfigurationEditor. On UNIX, you must edit the environment variables file. For more information,see “Configuration Editor” on page 55 and “UNIX Environment Variable Reference” onpage 32.

7 . On the next page, you are prompted for the Service Repository Path Selection. This is thestorage location for data transformations that are deployed as Complex Data Exchange

services. The default is<INSTALL_DIR>\ServiceDB . You can change the repository location following installation. For more information, see“Configuration Editor” on page 55.

8 . On the Log Path page, select the location where Complex Data Exchange Engine shouldstore its log files. The log path is also known as the reports path.♦ On Windows: The default is c:\Documents and Settings\<USER>\Application

Data\Informatica\ComplexDataExchange\CMReports , where <USER> is your username.

♦ On UNIX: The default is <INSTALL_DIR>/CMReports .

You can change the log path following installation. For more information, see“Configuration Editor” on page 55.

9 . On Windows: If you selected the option to install the Eclipse DevelopmentEnvironment, the wizard displays an Eclipse Configuration page. Select one of the

following options:

Component Explanation

Engine Installs Complex Data Exchange Engine.

Studio On Windows only: Installs Complex Data Exchange Studio, which is hostedwithin the Eclipse environment.

Document Processors Installs the document processors package.

Libraries On Windows only: Installs the Complex Data Exchange project libraries.

♦ Install a standalone copy of Eclipse 3.2. If you select this option, the setup installs anew copy of Eclipse, which is independent of any other copies of Eclipse that may exist



Running the Setup Wizard 25

py p p y p p yon the computer.

♦ Optionally, if Eclipse 3.2 is already installed on the computer, you can choose to runComplex Data Exchange Studio in it. Enter the directory path of the eclipse.exe file,

for example,c:\eclipse212\eclipse . This option is convenient if you already useEclipse for other purposes, and you wish to store Complex Data Exchange projects inyour existing Eclipse workspace.

10 . On the Summary page, review the setup options. Click Install to complete theinstallation.

11 . If you are running an upgrade setup from a previous Complex Data Exchange 4 release,the setup prompts you to upgrade existing Complex Data Exchange services. For moreinformation, see “Upgrading Complex Data Exchange Projects” on page 63.

12 . Depending on your operating system and applications, you must perform some post-setup steps. For more information, see“Post-Setup Steps” on page 26.

Post-Setup Steps




After you complete the setup, review the following information and perform the requiredsteps.

Installing a License FileIf your copy of Complex Data Exchange was purchased as part of Informatica PowerCenter,then the Informatica PowerCenter licensing mechanism applies to Complex Data Exchange.

If you purchased a standalone copy of Complex Data Exchange, you must install a validlicense file before you can run Complex Data Exchange services on the computer. ContactInformatica to obtain a Complex Data Exchange license file,CDELicense.cfg . You can useComplex Data Exchange Studio without installing a license file.

To i n s t a l l a l i c e n s e f i l e :

1 . Log on as a user with administrative privileges or as a user with write permission for theComplex Data Exchange installation directory.

2 . Copy the CDELicense.cfg file to the Complex Data Exchange installation directory.♦

On Windows: The default installation directory isc:\Program Files\Informatica\

ComplexDataExchange .♦ On UNIX: The default directory is /opt/Informatica/ComplexDataExchange .

To v e r i f y t h e v a l i d i t y o f t h e l i c e n s e f i l e :

1 . Open a command prompt.

2 . Enter the command:

CM_console -v

The system displays information such as the location and validity of the license file.Note: Itemfield ContentMaster license files are not valid for Complex Data Exchange. If youare upgrading from ContentMaster, contact Informatica for a new license file.

Loading Environment Variables

On UNIX: When the setup is complete, you must configure the system to load the ComplexData Exchange environment variables. For more information, see“Environment Variables”on page 29.

Configuring In-Process or Out-of-Process Invocation You can configure Complex Data Exchange Engine to run either in-process or out-of-process.This is especially important if you have a 32-bit Complex Data Exchange version, and youplan to activate it from 64-bit applications. For more information, see“Running In-Process orOut-of-Process” on page 49.

Configuring ODBCIf you plan to use the ODBC database support features of Complex Data Exchange you



Post-Setup Steps 27

If you plan to use the ODBC database support features of Complex Data Exchange, youmight need to configure an ODBC driver. For more information, see “Using Complex DataExchange with ODBC” on page 73.

Testing the InstallationTest the installation and confirm that Complex Data Exchange operates properly. For moreinformation, see “Testing and Troubleshooting” on page 35.

Uninstalling




To u n i n s t a l l Co m p l e x D a t a Ex c h a n g e :

1 . Close Complex Data Exchange Studio and all processes that activate Complex Data

Exchange Engine.2 . If you are uninstalling prior to a version upgrade, back up the Complex Data Exchange

repository, by default, <INSTALL_DIR>/ServiceDB . If necessary, you can restore theservices after the upgrade.

3 . Run the uninstall program.♦ On Windows: Open the Add or Remove Programs option of the Windows Control

Panel. Select the option to remove Complex Data Exchange.♦ On UNIX in graphical mode: Execute the uninstaller file, for example:

<INSTALL_DIR>/uninstall/_uninstMaster/uninstaller_AIX.bin

♦ On UNIX in console mode: Add the -console switch to the above command.<INSTALL_DIR>/uninstall/_uninstMaster/uninstaller_AIX.bin -console

4 . When the uninstallation is complete, you can delete <INSTALL_DIR> and any filesremaining in it.

5 . On UNIX: Remove the configuration that loads the Complex Data Exchangeenvironment variables. For more information, see“Environment Variables” on page 29.Then log out and log in, to ensure that the configuration changes take effect.



29

Chapter 4

Environment Variables


♦ Overview, 30

♦ Loading the Environment Variables on UNIX Platforms, 31♦ Windows Environment Variables, 34

Overview



30 Chapter 4: Envi ronment Variab les

The Complex Data Exchange setup assigns several environment variables, which point to theinstallation directory and to other locations that the system needs.

On UNIX-type platforms, you must configure the system to load the environment variables.Until you do this, you cannot run Complex Data Exchange.

On Windows platforms, the loading is automatic. There are no required configuration stepsfor environment variables.

Loading the Environment Variables on UNIX Platforms



Loading the Environment Variables on UNIX Platforms 31

On UNIX-type platforms, the Complex Data Exchange setup creates an environmentvariables file. You must load the file before you can test or use Complex Data Exchange. Youcan do this in either of the following ways:

♦ Manually, from the command line.♦ Automatically, by inserting the appropriate command in your profile or in a script file.

Loading from the Command LineIf you prefer not to load the environment variables automatically, you can load themmanually from the command line. You must do this each time you log in, before you useComplex Data Exchange.

♦ If you use the sh , ksh , or bash shell, the command is:. /<INSTALL_DIR>/setEnv.sh

♦ If you use the csh or tcsh shell, the command is:source /<INSTALL_DIR>/setEnv.csh

For <INSTALL_DIR> , you should substitute your installation path.

Loading AutomaticallyTo configure your system to load the environment variables file automatically when you login:

♦ If you use the sh , ksh , or bash shell, insert the following line in your.profile file.. /<INSTALL_DIR>/setEnv.sh

♦ If you use the csh or tcsh shell, insert the following line in your.login file.source /<INSTALL_DIR>/setEnv.csh

After you edit the file, log out and log in, so that your configuration changes will take effect.

Alternatively, you can execute the appropriate command line from a script file.

Environment Variable File when Running Out-of-ProcessIf you configure Complex Data Exchange to run out-of-process, the Complex Data ExchangeServer accesses<INSTALL_DIR>/setEnv.sh to obtain the environment variable settings.Confirm that the settings are correct in that file, regardless of the shell that you use or theenvironment-variable file that you load. For more information, see“Running In-Process orOut-of-Process” on page 49.

UNIX Environment Variable ReferenceOn UNIX-type platforms, Complex Data Exchange uses the following environment variables.




Example of Environment VariablesThe following is an example of the environment variables file (setEnv.csh ) on an AIX system. The variable names and values differ slightly on other UNIX-type operating systems.## Complex Data Exchange Environment settings

setenv IFCMPath /opt/Informatica/ComplexDataExchange

setenv CMJAVA_PATH /opt/Informatica/ComplexDataExchange/jre1.4/jre/bin/classic:

/opt/Informatica/ComplexDataExchange/jre1.4/jre/bin

# Prepend Complex Data Exchange to the PATH

if ( ! $?PATH ) then

setenv PATH ""

endif

setenv PATH "${IFCMPath}/bin:${PATH}"

# Add CM & java path to LIBPATH

if ( ! $?LIBPATH ) then

setenv LIBPATH ""

endif

setenv LIBPATH "${IFCMPath}/bin:${CMJAVA_PATH}:${LIBPATH}"

# Update IFCONTENTMASTER_HOME.

Environment VariableRequired/Optional

Purpose of the Variable

PATH Required The environment variables file adds <INSTALL_DIR>/bin to thepaths.Note: In rare instances, the Complex Data Exchange Java documentprocessors require that the JRE be added to the path.

- On AIX: LIBPATH- On Solaris and Linux:

LD_LIBRARY_PATH- On HP-UX: SHLIB_PATH

and LD_LIBRARY_PATH

Required The environment variables file adds the installation directory(<INSTALL_DIR> ) to the library path.It also adds the JVM directory of the JRE and its parent directory to thepath, for example, <INSTALL_DIR>/jre1.4/lib/sparc/server

and <INSTALL_DIR>/jre1.4/lib/sparc . You can edit this valueto use another compatible JRE.

CLASSPATH Required The environment variables file adds <INSTALL_DIR>/api/lib/CM_JavaAPI.jar to the Java class path.

IFCONTENTMASTER_HOME Required The environment variables file creates this variable, which points to theComplex Data Exchange installation directory ( <INSTALL_DIR> ).

IFConfigLocation4 Optional The path of the Complex Data Exchange configuration file. For more

information, see “Multiple Configurations” on page 60 .

setenv IFCONTENTMASTER_HOME "${IFCMPath}"

# Prepend CM path CLASSPATH



Loading the Environment Variables on UNIX Platforms 33

if ( ! $?CLASSPATH ) then

setenv CLASSPATH ""

endifsetenv CLASSPATH "${IFCMPath}/api/lib/CM_JavaAPI.jar:.:${CLASSPATH}"

Windows Environment Variables

On Windows the Complex Data Exchange setup creates or modifies the following




On Windows, the Complex Data Exchange setup creates or modifies the followingenvironment variables. This information is for reference only. You do not need to perform any special steps to configure or load the variables.

Environment VariableRequired/Optional

Purpose of the Variable

Path Required The setup adds <INSTALL_DIR>\bin to the path.Note: In rare instances, the Complex Data Exchange Java documentprocessors require that the JRE be added to the path.

CLASSPATH Required The setup adds <INSTALL_DIR>\api\lib\CM_JavaAPI.jar to

the path.IFCONTENTMASTER_HOME Required The setup creates this environment variable, which points to the

Complex Data Exchange installation directory ( <INSTALL_DIR> ).

IFConfigLocation4 Optional The path of the Complex Data Exchange configuration file. For moreinformation, see “Multiple Configurations” on page 60 .



35

Chapter 5

Testing and

TroubleshootingThis chapter includes the following topics:

♦ Complex Data Exchange Engine Test, 36

♦ Document Processor Test, 37♦ Installation Troubleshooting, 38

Complex Data Exchange Engine Test

After you install the software perform a quick test to verify that Complex Data Exchange



36 Chapter 5: Test ing and Troubleshooting

After you install the software, perform a quick test to verify that Complex Data ExchangeEngine operates correctly.

Following the test procedure, we provide some troubleshooting hints that might help you if the test fails or if you experience any other difficulty with the installation.

To t e s t t h e E n g i n e i n s t a l l a t i o n :

1 . Open a command prompt.

2 . Enter the CM_console command, without any parameters.

3 . CM_console should display a usage message such as the following:Usage:

CM_console Service name [Additional options]

...

4 . In the directory <INSTALL_DIR>\setupTests , there is a sample Complex Data Exchangeproject called testCME . Copy the entire testCME directory to the Complex DataExchange repository, which you defined during the setup. By default, the repository

directory is <INSTALL_DIR>\ServiceDB .This makes testCME available as a Complex Data Exchange service.

5 . Enter the following command, which executestestCME .CM_console testCME

The service performs a simple data transformation on an HL7 source document. Thefollowing result should be displayed:

<Result>Test Succeeded</Result>

Document Processor Test

If you installed the document processors, you can test the installation by running a service



Document Processor Test 37

y p , y y gcalled testCMDP . The service converts an Excel spreadsheet file to XML. It uses theExcelToXml document processor to perform an initial conversion stage.

To t e s t t h e d o c u m e n t p r o c e s s o r i n s t a l l at i o n :

1 . In the directory <INSTALL_DIR>\setupTests , there is a sample Complex Data Exchangeproject called testCMDP . Copy the entire testCMDP directory to the Complex DataExchange repository.

2. Run the command:CM_console testCMDP

3. The command should display the following output:<Report>

<Name>John Doe</Name>

<Age>29</Age>

<Sex>Male</Sex>

<Report><Q Year="2000" Q="1">5</Q>

<Q Year="2000" Q="2">6</Q>

<Q Year="2000" Q="3">7</Q>

<Q Year="2000" Q="4">3</Q>

<Q Year="2001" Q="1">5</Q>

<Q Year="2001" Q="2">8</Q><Q Year="2001" Q="3">3</Q>

<Q Year="2001" Q="4">3</Q>

<Q Year="2002" Q="1">3</Q>

<Q Year="2002" Q="2">4</Q>

<Q Year="2002" Q="3">2</Q>

<Q Year="2002" Q="4">8</Q></Report>

</Report>

Installation Troubleshooting

If you experience difficulty installing or running Complex Data Exchange, check the




y p y g g p gfollowing points.

UNIX Environment VariablesOn a UNIX-type platform, if the installation tests fail, the system is probably not settingsome or all of the environment variables that Complex Data Exchange requires.

To r e s o l v e a n e n v i r o n m e n t v a r i a b l e p r o b l e m :

1 . Confirm that you have followed the instructions to load the environment variables. Open

the setEnv.sh or setEnv.csh file and verify its contents.For more information, see “Environment Variables” on page 29.

2 . If you load the environment variables from your profile:

Log out and log in to the computer, and try the CM_console command again. If the teststill fails, your system is probably configured not to load the profile during startup. Try the following steps to solve the problem.

♦ If you use the sh or ksh shell within the Common Desktop Environment, edit the file~/.dtprofile and uncomment the following line:DTSOURCEPROFILE=true

♦ If you use the bash shell, edit your ~/.bashrc file and add the following line:. ./.profile

3 . If you configure Complex Data Exchange to run out-of-process, the Complex DataExchange server accesses<INSTALL_DIR>/setEnv.sh to obtain the environment variablesettings. Confirm that the settings are correct in that file.

4 . Log out and log in, and try the tests again.

If the tests still do not succeed, contact your system administrator or Informatica GlobalCustomer Support.

Log Files

Complex Data Exchange generates several log f iles, which are useful for troubleshootingpurposes.

Installation LogsThe setup creates a set of logs in the<INSTALL_DIR>\Inst_logs directory. You can examinethe logs for any error messages.

Complex Data Exchange Studio LogBy default, Complex Data Exchange Studio keeps a log of its operations.

To enable or disable the log and to set the log location, click Window > Preferences on the



Installation Troubleshooting 39

Complex Data Exchange Studio menu. On the left side of the window, select Complex DataExchange. On the right side, set the logging options.

Complex Data Exchange Studio Event Logs When Complex Data Exchange Studio runs a data transformation, it saves an event log calledEvents.cme in the Results directory of the project. The log appears in the Events view.

For more information, see the “Running and Testing Projects” in the Complex Data Exchange Studio User Guide .

Complex Data Exchange Engine Event LogsIf a failure occurs in a Complex Data Exchange service, the Engine creates an event log. Youcan view the log by dragging the*.cme file to the Events view of the Studio.

For more information, see “Event Logs” in theComplex Data Exchange Engine Developer Guide .

Java Heap and Stack SizeIf a Java component of Complex Data Exchange, such as a document processor that uses Java,fails to process very large documents or displays out-of-memory errors, the problem might bean inadequate Java heap size or stack size.

To s e t t h e J a v a h e a p s i z e :

1 .Open the Complex Data Exchange Configuration Editor.

2. On the left side of the window, expand the tree to display:CM Configuration/CM Engine/JVM init parameters

3. Right-click the JVM init parameters node and add an InitParam .

4. Assign a value of InitParam such as -Xmx512M, where 512 is the heap size in megabytes.

You should define the JVM init parameters only if needed. Setting a large Java heap size

increases the Complex Data Exchange memory requirement. You can pass additional parameters to the Java Virtual Machine by adding multipleInitParam lines. Enter each parameter on a separate line.

To control the Java stack size, see the JRE documentation.

Preventing Core-File Generation When processing very large inputs, a Java out-of-memory condition might cause ComplexData Exchange Engine to shut down unexpectedly and generate a core file. This has been

b d i IBM JRE i i g AIX l tf




observed in IBM JRE versions running on AIX platforms.

To prevent the core-file generation, start Java with the-Xdisablejavadump flag.

LDR_CNTRL Environment Variable on AIXOn some AIX 5.3 computers, the Complex Data Exchange setup fails to run unless youconfigure the LDR_CNTRLenvironment variable. For more information, see“AIX SystemRequirements” on page 14.

LD_PRELOAD Environment Variable on HP-UXOn HP-UX systems, you might need to set the LD_PRELOADenvironment variable to runcertain types of Complex Data Exchange applications. Specifically, you need to set theenvironment variable if:

♦ The Complex Data Exchange service is configured with a Java document processor, suchas:−

ExcelToDataXml− ExcelToTextML

− ExcelToXml

− PowerpointToTextML

− WordToTextML

− WordToXml

− XmlToExcel♦ You activate the Complex Data Exchange service in the process of a C++ application, such

as:− The CM_console command− An application that calls the Complex Data Exchange C++ API

For more information, see “Running In-Process or Out-of-Process” on page 49.

Under these circumstances, you should setLD_PRELOADto point to the libjvm shared objectof the JRE.

ExamplesOn an HP-UX PA-RISC platform, the libjvm object is calledlibjvm.sl . Enter a commandsuch as:

setenv LD_PRELOAD "<INSTALL_DIR>/jre1.4/lib/PA_RISC2.0/server/libjvm.sl"

On an HP-UX ia64 platform, the object is called libjvm.so . The corresponding command is:

setenv LD_PRELOAD "<INSTALL_DIR>/jre1.4/lib/IA64N/server/libjvm.so"

The above examples are for 32-bit Complex Data Exchange versions, and they point to 32-bit JREs. If you run a 64-bit version, LD_PRELOADshould point to a 64-bit JRE. The twoexamples become:



Installation Troubleshooting 41

examples become:

setenv LD_PRELOAD "<INSTALL_DIR>/jre1.4/lib/PA_RISC2.0W/server/libjvm.sl"

setenv LD_PRELOAD "<INSTALL_DIR>/jre1.4/lib/IA64W/server/libjvm.so"

IncompatibilitiesThe LD_PRELOADsetting is incompatible with applications that call the Complex DataExchange Java API or that runtcsh scripts. Before you run such applications, you must unsetthe environment variable:

unsetenv LD_PRELOAD

If you frequently run both C++ and Java applications in the same HP-UX environment, youcan configure them to run in different shells. In the shell that you use for the C++ application,you can add the LD_PRELOADsetting to the profile.

Alternatively, you can create two shell scripts, which set or unset theLD_PRELOADvariable.C++ applications should run the script that sets LD_PRELOAD, before they activate ComplexData Exchange Engine. Java applications should run the script that unsetsLD_PRELOAD, before

activating Complex Data Exchange Engine.

Memory Allocation on HP-UXBy default, HP-UX systems allocate virtual memory to a process in four 1-GB quadrants, asfollows:

♦ Q1: main executable code and data♦

Q2: main executable heap and stack ♦ Q3: shared modules code and data♦ Q4: shared modules code and stack

When processing very large inputs, you can modify the allocation to provide more memory for Complex Data Exchange Engine. One way to do this is by running thechatr utility. Formore information, refer to the HP-UX documentation.

Emulators You should install and run Complex Data Exchange on native operating systems. Running onemulators is not supported.

For example, do not run Complex Data Exchange for HP-UX PA-RISC on an HP-UX ia64machine with a PA-RISC emulator.

Asian FontsThe Complex Data Exchange Studio views sometimes fail to display Asian fonts correctly under Windows 2000. To correct the problem, open the Window > Preferences command,select the Workbench/Fonts node and set the font for each view




select the Workbench/Fonts node, and set the font for each view.



43

Chapter 6

Running Data

TransformationsThis chapter includes the following topics:

♦ Designing and Configuring Data Transformations, 44♦

Deploying Complex Data Exchange Services, 45♦ Running Complex Data Exchange Services, 47

Designing and Configuring Data Transformations

Complex Data Exchange users can design, configure, and test data transformations by usingComplex Data Exchange Studio on a Windows platform. Among the possible transformation



44 Chapter 6: Running Data Transformations

Complex Data Exchange Studio on a Windows platform. Among the possible transformationcomponents are:

♦ Parsers. Convert any data format to XML.♦ Serializers.Convert XML to any format.♦ Mappers. Convert XML to another XML vocabulary or schema.♦ Transformers. Modify the data in any format.

For more information and instructions on using Complex Data Exchange Studio, see thefollowing documents:

♦ Getting Started with Complex Data Exchange —provides basic instructions and tutorialexercises for using the entire Complex Data Exchange system

♦ Complex Data Exchange Studio User Guide —explains how the data transformations operateand how to configure them

♦ Using Complex Data Exchange Studio in Eclipse —explains how to use the Complex DataExchange Studio user interface, which is hosted in the Eclipse development environment

Deploying Complex Data Exchange Services

To run a data transformation in Complex Data Exchange Engine, a user must first deploy it asa Complex Data Exchange service. The deployment procedure copies the Studio project to a



Deploying Complex Data Exchange Services 45

p g p y p p p jrepository, where it is available to run in Complex Data Exchange Engine. For moreinformation, see “Deploying Complex Data Exchange Services” in theComplex DataExchange Studio User Guide .

Repository LocationOn both Windows and UNIX, the default repository location is <INSTALL_DIR>\ServiceDB .

To deploy a project, a user must have write permission for the repository. You can change the

repository location by setting theBase Path parameter in the Configuration Editor.

Deploying on the Studio Computer You can deploy a Complex Data Exchange service to the repository on a Windows computer where Complex Data Exchange Studio is installed.

To d e p l o y a C o m p l ex D at a E x c h a n g e s e r v i c e t o t h e S t u d i o c o m p u t e r :

1 . Configure the data transformation in Complex Data Exchange Studio.

2. On the menu, click Project > Deploy.

Deploying on Another Computer You can deploy a Complex Data Exchange service to the repository on another computer,such as a UNIX-type platform.

To d e p l o y a C o m p l e x D a t a Ex c h a n g e s e r v i c e t o a U N I X -t y p e p l a t f o r m :

1 . Deploy the service on the Complex Data Exchange Studio computer, as described above.

2. Copy the deployed project directory from the repository on the Studio computer to therepository on the remote computer.

3. Complex Data Exchange Engine determines whether any services have been revised by

periodically examining the timestamp of a file calledupdate.txt . By default, thetimestamp is examined every thirty seconds.

The update.txt file exists in the repository root directory which is, by default, theServiceDB directory. The content of the file can be empty.

If this is the first time that you have deployed a service to the remote repository,update.txt might not exist. If the file is missing, copy it from the local repository.

If update.txt exists, you should update its timestamp as follows.♦ On Windows: Open update.txt in Notepad and save it.

♦ On UNIX: Open a command prompt, change to the repository directory, and enterthe following command.touch update.txt

l




Re-Deploying After deploying a Complex Data Exchange service, if you edit the data transformation in theStudio, you must deploy the service again.

Running Complex Data Exchange Services

You can run Complex Data Exchange services by any of the following methods:

♦ By using the CM console command-line interface



Running Complex Data Exchange Services 47

By using the CM_console command line interface.

♦ By programming an application that calls one of the Complex Data Exchange APIs.♦ By using the HTTP protocol to access the Complex Data Exchange CGI interface.♦ By using a Complex Data Exchange integration agent, which runs in a third-party

application.

For more information, see the Complex Data Exchange Engine Developer Guide .






49

Chapter 7

Running In-Process or

Out-of-ProcessThis chapter includes the following topics:

♦ Overview, 50♦

Configuration, 52

Overview

You can configure Complex Data Exchange Engine to run either in the process of the callingapplication or out-of-process.



50 Chapter 7: Running In-Process or Out-of-Process

Out-of-process invocation requires the use of Complex Data Exchange Server. For moreinformation, see the Complex Data Exchange Engine Developer Guide .

This option has no effect on Complex Data Exchange Studio or on theCM_console command, which always run data transformations in-process.

Relative AdvantagesRunning out-of-process has the following advantages:

♦ It allows 64-bit processes to activate 32-bit versions of Complex Data Exchange Engine.♦ An Engine failure is less likely to disrupt the calling application.♦ It can help prevent binary collisions with other modules that run in the process of the

calling application.

In-process invocation has the following advantages:

♦ Running in-process might give faster performance than out-of-process.♦ Some of the APIs are available only when running out-of-process. Out-of-process

invocation is currently supported by the Java API.

Determining whether to Run In-Process or Out-of-ProcessConsult the following table to determine whether you need to run in-process or out-of-process.

The first and second columns of the table list the available Complex Data Exchange versions.The third and fourth columns list the invocation methods, such as calling from a 32-bit Javaprocess or a 64-bit Java process.

PlatformComplex DataExchange Versio n

If You Call Complex DataExchange from a 32-bitProcess, You can Choose


Windows 32-bit In-process or out-of-process Out-of-processSolaris 32-bit In-process or out-of-process Out-of-process

64-bit Out-of-process In-process or out-of-process

AIX 32-bit In-process or out-of-process Out-of-process

64-bit Out-of-process In-process or out-of-process

SUSE Linux 9 or Red

Hat Linux EL3 on x86

32-bit In-process or out-of-process

SUSE Linux 9 or RedHat Linux EL4 on x86-64

64-bit In-process or out-of-process

PlatformComplex DataExchange Versio n





Overview 51

Determining Your Complex Data Exchange VersionIf you are not sure whether you have a 32-bit or 64-bit Complex Data Exchange version, opena command prompt and run the command:

CM_console -v

Among other information, the command displays a package identifier, which is a code thatuniquely identifies your Complex Data Exchange version. The code contains the substring32 or 64 .

HP-UX 64-bit Out-of-process In-process or out-of-process

Configuration

To s e l e c t i n - p r o c e s s o r o u t -o f -p r o c e s s i n v o c a t i o n :

1 . Open the Complex Data Exchange Configuration Editor.




♦

On Windows: On the Start menu, click All Programs > Informatica > Complex DataExchange > Configuration.♦ On UNIX: Enter the following command:

<INSTALL_DIR>/CMConfig

2 . In the left pane, expand the tree to display the following node:CM Configuration/CM Engine

3 . In the right pane, edit the following setting. If the setting is not displayed, right-click theCM Engine node and add it.

4 . Edit the settings under the following node:CM Configuration/CM Engine/CM Server

These settings have an effect only if you have setInvocation = Server . If the settingsare not displayed, right-click theCM Server node and add them.

Sett ing Explanation

Invocation Select the value InProc for in-process invocation.Select Server for out-of-process invocation. This causes the Engine request to be routedvia Complex Data Exchange Server. For each client process that submits requests, theServer starts an independent Engine process.

SettingRequired/Optional

Explanation

Server Path Required onUNIX

The path to the CM_Server.sh shared object. Set its value to:<INSTALL_DIR>/bin/cm_server.shYou should also confirm that cm_server.sh has executepermission. You can do this by running the command:chmod a+x <INSTALL_DIR>/bin/cm_server.shThe Server Path setting is unnecessary on Windows platforms.You can leave it blank.

Thread pool size Optional The maximum number of Engine threads that can run client

requests concurrently per process. If the number of client requestsexceeds the number of available threads, the Server queues therequests until a thread is available. The default is 4.

Thread Stack Size Optional The stack size, in kilobytes, that the Server allocates to eachthread. The default is 1024.

Init Engine Optional If the value of this parameter is OnDemand , the Server starts theEngine when the client application first issues a request. If thevalue is OnStartup , the Server starts the Engine when the clientapplication is loaded The default is OnDemand

SettingRequired/Optional

Explanation



Configuration 53

5 . If you run out-of-process, confirm that the environment variables settings are correct inthe setEnv.sh file. For more information, see“Environment Variable File when RunningOut-of-Process” on page 31.

application is loaded. The default is OnDemand .

Number of retriesRestart timeout

Optional If a client process receives no response from the Server, it attemptsa Server restart. These parameters control the restart behavior:The Number of retries is the maximum number of permittedrestarts, and the Restart timeout is the time interval inseconds. If the number of required restarts exceeds the specifiedvalue, within the time interval, the client process ceases all further attempts.The default values are Number of retries = 4 and Restarttimeout = 900 . This means that if the client process needs torestart the server more than 4 times in 900 seconds, it ceases theattempts.This behavior is regardless of the number of successful requestsduring the timeout period. In the above example, if the clientprocess successfully communicates with the server 100 timesduring the 900-second interval, but it fails 5 times, it ceases further attempts.The behavior is per client process. If there are multiple clientprocesses, then each of them is permitted 4 restarts during the

timeout interval.The restarts refer only to the communication between the clientprocess and the Server. If the Engine returns an error response, for example, due to invalid input data, the Server reports the error status to the client, but the Server does not require a restart.




Chapter 8



55

C apte 8

Configuration Editor


♦ Using the Configuration Editor, 56♦ Configuration Settings, 58♦ Copying the Configuration File, 59♦ Multiple Configurations, 60

Using the Configuration Editor

Complex Data Exchange has a Configuration Editor, which lets you edit the parameters of aComplex Data Exchange installation.

Usually, you need to use the Configuration Editor only in the following circumstances:



56 Chapter 8 : Configura tion Edi tor

y y g y g

♦ If you need to change one of the directory locations that you configured during the setup,such as the JRE location or the repository location.

♦ If instructed in the Complex Data Exchange documentation or by Informatica GlobalCustomer Support.

To open the Configuration Editor:

♦ On Windows: On the Start menu, open Informatica > Complex Data Exchange >Configuration.

♦ On UNIX in graphical mode: Enter the following command:<INSTALL_DIR>/CMConfig

The Configuration Editor is not supported in a UNIX console mode.

Some of the Configuration Editor settings are available in all Complex Data Exchangeinstallations. Some additional settings vary depending on the Complex Data Exchange

version and on the optional components that you have installed.

Backing Up the Configuration FileThe Configuration Editor saves the configuration in an XML file. By default, the file is<INSTALL_DIR/CMConfig.xml> .

Before you edit the configuration, save a backup copy of CMConfig.xml . In the event of aproblem, you can restore the backup.

The file <INSTALL_DIR>/CMConfig.bak is a backup of the original<INSTALL_DIR/CMConfig.xml> , which the setup program created when you installed Complex DataExchange. RestoringCMConfig.bak returns Complex Data Exchange to its originalconfiguration.

Assigning the Settings

The editor has an Explorer-type window. On the left side, expand the tree and select thedesired setting. On the right side, double-click to assign a setting value.

Some settings require that you type a value, whereas others offer a drop-down list or a browseoption. If a setting has a gray background, it has a read-only value that cannot be edited.

Some settings accept a table of values. You can right-click to add or remove table rows.

Missing SettingsIf a setting is not displayed, Complex Data Exchange uses its default value. To display thesetting and edit its value, right-click its parent node and click the Add option.

Saving the Configuration File



Using the Configuration Editor 57

Click the Save icon to save the edited settings. If you forget to save, the Configuration Editordisplays a reminder when you exit.

Configuration Settings

The following are the most common configuration settings that you might need to edit. Youcan assign these settings when you run the Complex Data Exchange setup. If necessary, youcan change the settings afterwards in the Configuration Editor.




There are many additional settings, which are described in the relevant locations throughoutthe Complex Data Exchange documentation.

Directory Locations When you ran the Complex Data Exchange setup, you were prompted for the directory locations of the Complex Data Exchange repository, log files, and JRE. If necessary, you canalter the locations by editing the following parameters:

Parameter Explanation

CM Configuration/

Directory services/

File system/Base Path

The Complex Data Exchange repository location, where Complex DataExchange services are stored.

CM Configuration/

CM Engine/

JVM Location

On Windows:The JRE location, for example:<INSTALL_DIR>/jre1.4/bin/clientIf you edit the path, do not uninstall the previous JRE version until you savethe new setting and exit the Configuration Editor. This is important becausethe Configuration Editor itself requires a JRE.On UNIX:This parameter is not available in the Configuration Editor onUNIX-type platforms. For more information about setting the JRE on UNIX,see “UNIX Environment Variable Reference” on page 32 .

CM Configuration/

General/

Reports directory

The log path, also called the reports path, where Complex Data Exchangesaves event logs and certain other types of reports.

CM Configuration/

CM Engine/

Invocation

CM Configuration/

CM Engine/

CM Server

These settings control whether Complex Data Exchange Engine runs in-process or out-of-process. For more information, see “Running In-Processor Out-of-Process” on page 49 .

Copying the Configuration File

You can copy a configuration file between identical computers, running the same operatingsystem and the same version of the software. This is a convenient way, for example, to ensurethat a set of identical servers all use the same Complex Data Exchange configuration.

N A id i b id i l h fi i i h b



Copying the Configuration File 59

Note: Avoid copying between non-identical systems, as the configurations might beincompatible. For example, the configuration file on a Windows system contains theJVMLocation parameter. On a UNIX-type system, this parameter must not exist. If it does,Complex Data Exchange does not run correctly.

Multiple Configurations

You can create multiple Complex Data Exchange configurations. At runtime, you can select which configuration Complex Data Exchange Engine should use.

You might do this, for example, if you wish to use different Complex Data Exchangeit i f diff t t f i Y t fig ti th t h diff t




repositories for different types of services. You can create configurations that have differentvalues of the repository location setting.

Creating Multiple Configurations You can create multiple configurations by editing and copying the default configuration file.

To c r e a t e m u l t i p l e c o n f i g u r a t i o n f i l e s :

1 . Make a backup copy of the default configuration file,<INSTALL_DIR/CMConfig.xml> . Atthe end of the procedure, you will restore the backup.

2 . Use the Configuration Editor to edit the original copy of CMConfig.xml . Save your edits.

3 . Copy the edited CMConfig.xml to another location or another filename.

4 . Repeat steps 2 and 3, creating additional versions of the configuration file. In this way,

you can define as many configurations as you need.5 . Restore the backup that you created in step 1.

This ensures that the default configuration remains as before.

Selecting the Configuration at Runtime You can set the configuration file that Complex Data Exchange Engine should use in any of

the following ways:♦ Define an environment variable calledIFConfigLocation4 . The value of the variable must

be the path of a valid configuration file, for example:c:\MyIFConfigLocation4\CMConfig1.xml

♦ On UNIX only: Store the configuration file under the name CMConfig.xml , in the user'shome directory.

♦ Use the default configuration file,<INSTALL_DIR>/CMConfig.xml .

When Complex Data Exchange Engine starts, it searches these locations in sequence. It usesthe first configuration file that it finds.

Example 1 You want to run two applications with different configuration files. Each application shouldset the value of IFConfigLocation4 before it starts Complex Data Exchange Engine.

Example 2Two users want to run Complex Data Exchange Engine with different configurations, on thesame UNIX-type platform. Store their respective configuration files in their home directories.Both files must have the name CMConfig.xml .

Alternatively, store aCMConfig.xml file in the home directory of one of the users. The otheruser uses the default configuration file <INSTALL DIR>/CMConfig xml



Multiple Configurations 61

user uses the default configuration file,<INSTALL_DIR>/CMConfig.xml .

Multiple JREsOn Windows platforms, the JVM Location parameter of the configuration file defines the

JRE that Complex Data Exchange should use. By using multiple configuration files, you canswitch JREs.

On UNIX-type systems, the configuration file does not contain aJVM Location parameter.To switch JREs, you must load a different environment variables file. For information, see“Environment Variables” on page 29.

Running Multiple Configurations ConcurrentlyComplex Data Exchange Engine loads the configuration file and the environment variables

when it starts. After it starts, changing the configuration file or the environment variables has

no effect.This means that two applications can use different configurations concurrently. Eachapplication uses the configuration that was in affect when its instance of Complex DataExchange Engine started.




Chapter 9



63

Upgrading Complex Data

Exchange ProjectsThis chapter includes the following topics:

♦ Overview, 64♦ Upgrading an Individual Project, 65♦ Syntax Conversion Tool, 66♦ Upgrade Issues, 70

Overview

If you are upgrading from a previous Complex Data Exchange release, you can upgrade yourexisting projects and your deployed Complex Data Exchange services to the current release.

The upgrade of projects from Complex Data Exchange version 3.1 or higher is automatic. You can upgrade an individual project by opening or importing it in Complex Data Exchange



64 Chapter 9: Upgrading Complex Data Exchange Projects

pg p j y p g p g p gStudio, or you can run a syntax conversion tool that upgrades all your projects or servicestogether.

Note: If you run an upgrade setup from a previous Complex Data Exchange 4 release, thesetup prompts you to upgrade your existing services. In other cases, perform the upgradeyourself, after you complete the setup.

When Is Upgrading Necessary?Upgrading is necessary when the syntax version of Complex Data Exchange Engine haschanged.

To determine the syntax version, open a command prompt and run the following command:

CM_console -v

TerminologyIn Complex Data Exchange 3.x and 4, certain terms are used in slightly different ways. Toprevent confusion, we use the Complex Data Exchange 4 terminology throughout theupgrade instructions, unless otherwise stated.

The following table presents the corresponding terms.

Complex DataExchange 4 Complex Data Exchange3.x Description

Project Workspace A directory containing a data transformation configuration: aCMW file, o ne or more TGP script files, etc.

Workspace No corresponding term The default parent directory, where Complex Data ExchangeStudio 4 stores projects.

Deploy Publish Make a project available as a service.

Repository Services database location The parent directory where Complex Data Exchange services arestored.

Upgrading an Individual Project

On a Windows computer, you can upgrade an individual project by opening or importing itin Complex Data Exchange Studio.

Perform the import by clicking File > Import. In the Import window, select the option toimport an Existing Complex Data Exchange Project into Workspace.



Upgrading an Individual Project 65

p g p g j pComplex Data Exchange Studio prompts you to upgrade the project if necessary. The upgradeis fully automatic.

Following the upgrade, test the project and confirm that it runs correctly.

Upgrading a Service You can upgrade the development copy of a project and re-deploy it as a Complex DataExchange service.

To do this, open or import the development copy in Complex Data Exchange Studio. Test theproject, and re-deploy it as a service.

Syntax Conversion Tool

You can use the Complex Data Exchange syntax conversion tool to upgrade multiple projectsand services quickly, in an automated operation. You can also use it to upgrade global TGPscript files, which are stored in the Complex Data ExchangeautoInclude\user directory.

Before the upgrade, the tool creates an automatic backup of your existing projects and files. Itl fil d d h i d I f h




creates a log file and reports any upgrade errors that it detects. In case of an error, restore thebackup, correct the problem, and run the tool again.

Version Support on WindowsOn Windows, the syntax conversion tool can upgrade projects or services from Complex DataExchange 3.1 and higher.

Version Support on UNIXOn UNIX-type platforms, the tool can upgrade services from earlier Complex Data Exchange4 releases.

To u p g r a d e C o m p l e x D a t a E x c h a n g e 3 . x s e r v i c e s :

1. Run the tool on a copy of the project or service directories on a Windows computer.2. Re-deploy the services to the UNIX computer.

Before Running the Tool: Organize Your ProjectsThe tool operates on projects or services that are stored in a single parent directory. It canoperate on:

♦ A Complex Data Exchange Studio version 4 workspace♦ A Complex Data Exchange repository ♦ Any other directory that contains Complex Data Exchange Studio projects or services

Within the parent directory, the projects must be at the top level of nesting, for example:

Parent Directory

Project1

Project2

Project3

...

If your projects are not currently stored in a single parent directory, you can re-organize thembefore running the tool. Alternatively, you can run the tool separately on the individualparent directories.

The tool also operates on the Complex Data ExchangeautoInclude\user directory, whichcontains global TGP script files.

Running the Syntax Conversion Tool

To r u n t h e s y n t a x c o n v e r s i on t o o l :1 T th t l



Syntax Conversion Tool 67

1 . To open the tool:♦ On Windows: In the Complex Data Exchange folder on the Start menu, click Syntax

Conversion Tool.♦ On UNIX: Run the following command:

<INSTALL_DIR>/bin/CM_DBConverter.sh

The tool is a window with several tabs, where you can configure the upgrade.

2. At the bottom of the window, specify whether you are upgrading from version 3.x or 4.x.

On UNIX: Only 4.x is supported.

3. On the Services tab, set the following options:

4. If you have any TGP files in theautoInclude\user directory, set the following optionson the AutoInclude tab:

5. Set the following options on the Result Files tab:

6. Click the Start button.

The tool reports its progress and results.

Option Explanation

Source Location The parent directory containing the old projects, or the repository containing the oldservices.

Target Location The parent directory where the tool should store the new projects, or the repository for thenew services. If the target is the same as the source, the original files are overwritten.

Option Explanation

Source Location The old autoInclude\user directory.

Target Location The new autoInclude\user directory.

Option ExplanationBackup Location A location where the tool should back up your existing projects, prior to upgrade.

Error Location A location where the tool should store any projects that it cannot upgrade due to an error.

Log Location A location for the upgrade log.

7 . You can repeat steps 3, 5, and 6 on any additional parent directories that contain projectsor services. For example, you can upgrade a Complex Data Exchange Studio workspace

where you store development projects, in addition to a repository where you storedeployed services.

The AutoInclude options should be blank on the repeat runs. The AutoInclude files werealready upgraded on the first run and do not need to be upgraded again.

8 . If the tool reports any errors, review the log to determine their cause, correct them, and




p y , g , ,run the tool again.

9 . If you have upgraded services, use the Configuration Editor to change the repository location to the new location. If you have upgraded development projects, use the File >Import command to open the projects in Complex Data Exchange Studio.

1 0. Test the projects and services to confirm that they work correctly and that their behavior

has not changed. For more information about the issues that might arise, see“UpgradeIssues” on page 70.

Running from the Command LineOptionally, you can run the syntax conversion tool from the command line, withoutdisplaying the graphical user interface.

To r u n t h e s y n t a x c o n v e r s i o n t o o l fr o m t h e c o m m a n d l i n e :

1 . Open a command prompt, and change to the Complex Data Exchange bin directory.

2 . Run the following command:♦ On Windows: CM_DBConverter.bat <switches>

♦ On UNIX: CM_DBConverter.sh –console <switches>

The <switches> are listed in the following table.

SwitchRequired/Optional

Description

-v Required Version from which you are upgrading (3 or 4). On UNIX, only 4 is supported.

-s Required Path of the source directory, containing projects or services.

-d Optional Path of the target directory. If you omit this switch, the tool overwrites the existingdirectory.

-si Optional Path of the source autoInclude\user directory. If you omit this switch, the tooldoes not upgrade global TGP files.

-di Optional Path of the target autoInclude\user directory. If you omit this switch, the tooloverwrites the existing directory.

-l Optional Path of the upgrade log file. The default is <INSTALL_DIR>\SyntaxConversionLog.txt .

-b Optional Path of the backup directory, where the tool backs up the original projects or servicesprior to the upgrade. The default is the value of the -s switch concatenated with thesuffix _OLD_Backup.

-e Optional Path of the error directory, where the tool stores any projects or services that itcannot upgrade due to an error. The default is the value of the -s switchconcatenatedwith thesuffix OLD Failure

SwitchRequired/Optional

Description



Syntax Conversion Tool 69

Following each switch, leave a space and type the value. If a path contains spaces, youmust enclose it in quotation marks. For example, the Windows command

CM_DBConverter.bat -v 4 -s "c:\Program Files\Informatica\ComplexDataExchange\ServiceDB"

upgrades version 4 services in the default repository location.3. The tool notifies you when the upgrade is complete. If there were errors, it prompts you

to examine the log file.

4. If you are upgrading services, use the Configuration Editor to change the repository location to the target that you specified.

concatenated with the suffix _OLD_Failure .

Upgrade Issues

The automatic upgrade successfully upgrades nearly all the features that existed in previousComplex Data Exchange versions. Nonetheless, it is important that you test the datatransformation following the upgrade. If you find that an upgraded project does not operate

correctly, you can edit its configuration in Complex Data Exchange Studio.The following paragraphs discuss some upgrade issues that you might encounter.




g p g p pg y g

New and Modified ComponentsIn version 4, some of the Complex Data Exchange components that you can use in datatransformations have been revised, renamed, or replaced by new components. When youupgrade a project, Complex Data Exchange inserts the new components automatically.

For more information on some components that have been modified, see the documentWhat's New in Complex Data Exchange . In most cases, the modifications do not change thebehavior of upgraded projects.

You might find that an upgraded project containing the Locator component behaves slightly differently from the original version 3.2 project, where theLocator component did not exist,and the analogous functionality was implemented in a different way.

In projects upgraded from version 4.0.4 and earlier, the behavior of theEnsureCondition andCalculateValue actions might change slightly due to the introduction of a new JavaScriptprocessor. For more information on the supported JavaScript syntax, see theEnsureCondition action in the Complex Data Exchange Studio User Guide .

Modified Namespace for VariablesStarting in version 4.0.6, the namespace for variables has been changed to www.Local-

Project.com/Variables . If you upgrade a project from version 4.0.5 or earlier, the Schemaview and the project properties display both the old empty namespace and the new namespacethat contains your variables. This has no effect on the operation of your project.

Unsupported File and Directory NamesIn Complex Data Exchange 4, the names of project files and directories may contain Englishletters (A-Z, a-z), numerals (0-9), spaces, and the following symbols:

# % & + , - . = @ [ ] _ { }

If a version 3.x project does not conform with this convention, the project might fail toupgrade. If this occurs, change the names in version 3.x before running the tool.

XSD SchemasIn Complex Data Exchange 3.1, the XML schema was defined in the TGP files of the project.Starting in Complex Data Exchange 3.2, the XML schema is an XSD file.

When you upgrade a version 3.1 project to version 4, Complex Data Exchange Studio createsan XSD schema automatically. Review the schema and confirm that it meets your needs. Youcan edit the schema or create your own schema, as required.

For more information, see “Data Holders” in the Complex Data Exchange Studio User Guide .



Upgrade Issues 71




Chapter 10



73

Using Complex Data

Exchange with ODBCThis chapter includes the following topics:

♦ Overview, 74♦ Installing and Configuring an ODBC Manager on UNIX, 75♦ Defining DSNs, 76

Overview

Complex Data Exchange offers ODBC connectivity features that allow it to interact withdatabase systems. For more information about the capabilities, see theODBCLookup transformer and the ODBCAction action in the Complex Data Exchange Studio User Guide .

On Windows platforms, Complex Data Exchange uses the built-in Microsoft ODBCmanager. On UNIX-type platforms, you must configure an ODBC manager before you can

th ODBC f t



74 Chapter 10: Using Complex Data Exchange with ODBC

use the ODBC features.

On both Windows and UNIX, you might need to install an ODBC driver. You should defineone or more DSNs, which Complex Data Exchange uses to connect to the database.

Installing and Configuring an ODBC Manager on UNIX

On UNIX-type platforms, you must install an ODBC manager that supports the ODBC 3.0 API. You can use an open-source ODBC manager or one that you obtain from your UNIX ordatabase vendor.

You should add the directory location of the ODBC manager to your LIBPATH orLD_LIBRARY_PATH environment variable.



Installing and Configuring an ODBC Manager on UNIX 75

To c o n f i g u r e t h e O D B C m a n a g e r i n C o m p l e x D a t a E x c h a n g e :

1 . Open the Complex Data Exchange Configuration Editor.

2. In the left pane, select the CM Engine node.

3.In the right-pane, right-click and click Add > ODBC Manager Shared Library Path.This adds a new parameter calledODBC manager shared library path to the display.

4. Set the value of the parameter to the location of the ODBC manager shared object, forexample:

/usr/local/odbc/libODBCMgr.so

Installing an ODBC Driver An ODBC driver for your database system must be installed on the computer. The drivermight be supplied with the database system, or you can obtain it from your platform ordatabase vendor.

TroubleshootingIf an incorrect ODBC manager version is installed, Complex Data Exchange might display the following error when it tries to run a service that uses ODBC:

Function not found in ODBC API

If an ODBC driver is not installed, Complex Data Exchange might display the followingerror:

Failed to load ODBC API

Defining DSNs

You should define one or more DSNs, which Complex Data Exchange can use to connect tothe required databases.

♦ On Windows: Use the Control Panel > Administrative Tools > Data Sources option to

define and test DSNs.♦ On UNIX: Use the utilities provided with your ODBC manager to define and test DSNs.



76 Chapter 10: Using Complex Data Exchange with ODBC

Using a DSNTo connect to a database, configure a Complex Data Exchange data transformation with acomponent such as ODBCLookup or ODBCAction . In the db_connection property of thecomponent, specify the DSN that you defined above.

Chapter 11



77

Administration and

Deployment PoliciesThis chapter includes the following topics:

♦ Overview, 78♦ Security, 79♦ Multiple Servers, 81♦ Failure Handling, 84

Overview

If you are administering Complex Data Exchange in a large organization, you need toestablish policies and methods for:

♦ Deploying the Complex Data Exchange software throughout the organization♦ Security and user permissions♦ Deploying Complex Data Exchange services and configurations in multiple-server

i



78 Chapter 11: Administration and Deployment Policies

environments♦ Backup requirements♦ Failure handling

This chapter discusses the key issues and describes some approaches for implementing the

policies.

Security

Below, we list the typical permissions that are required by users who install and use ComplexData Exchange Studio and Engine. Of course, there might be exceptions to the list, andadditional permissions might be required, depending on the Complex Data Exchangeapplications that your organization runs.

Studio Permissions



Security 79

Users who configure data transformations in Complex Data Exchange Studio typically musthave the following permissions:

♦ Read and write permission for the Eclipse workspace location. By default, the location isMy Documents\Informatica\ComplexDataExchange\4.0\workspace .

♦ Read and execute permission for the Complex Data Exchange installation directory <INSTALL_DIR> and for all its subdirectories.

♦ Read and write permission for the Complex Data Exchange repository, where they willdeploy Complex Data Exchange services. By default, the repository is<INSTALL_DIR>\ServiceDB .

♦ Read and write permission for the log location. By default, the location isc:\Documentsand Settings\<USER>\Application Data\Informatica\ComplexDataExchange\

CMReports .

Engine Runtime PermissionsThe user accounts under which applications run Complex Data Exchange Engine must havethe following permissions:

♦ Read and execute permission for the Complex Data Exchange installation directory

<INSTALL_DIR> and for its subdirectories.♦ Read permission for the Complex Data Exchange repository.♦ Read and write permission for the Complex Data Exchange log path, or for any other

location where you configure Complex Data Exchange applications to store error logs.

Standard Windows User CategoriesFor convenience, we list below the capabilities of two standard Windows user types:administrators and limited users. You can choose these user types when you register users inthe Windows Control Panel.

Administrators Windows users who have administrative privileges can perform all Complex Data Exchangeoperations.

Limited UsersTypically, limited users do not have write permission for the Complex Data Exchangeprogram directory and are subject to the following restrictions:

♦ They cannot install or uninstall the Complex Data Exchange software.♦ They cannot install a Complex Data Exchange license file.♦ They cannot deploy services to the default Complex Data Exchange repository. You can

relax this restriction by moving the repository to another directory, where the users have write permission. For more information, see“Configuration Editor” on page 55.




p g p g♦ They cannot add custom components such as document processors or transformers.♦ They can view the settings in the Configuration Editor, but they cannot change the setting

values.

Multiple Servers

For enhanced performance, you can install Complex Data Exchange on multiple Windows orUNIX servers. The following discussion assumes that you use a load balancing module toconnect to multiple, identically configured servers.

Copying the Configuration FileCopy the configuration file, by default,<INSTALL DIR>\CMConfig.xml , from one server to



Multiple Servers 81

Copy the configuration file, by default, INSTALL_DIR \CMConfig.xml , from one server toother, identical servers. This ensures that all the servers have the same Complex DataExchange repository path, reports path, operation parameters, etc.

For more information, see “Copying the Configuration File” on page 59.

Deploying ServicesThe servers should share the same Complex Data Exchange services. There are two ways toimplement this:

♦ Shared file system. Store a single copy of the Complex Data Exchange repository on ashared disk. Configure all the servers to access the shared repository.

♦ Replicated file system. Configure each server with i ts own Complex Data Exchange

repository. Use an automatic file deployment tool to mirror the Complex Data Exchangerepository from a source location to the individual servers.

If you use the second approach, you must replicate or touch the fileupdate.txt , which existsin the repository directory. The timestamp of this file notifies Complex Data ExchangeEngine when the last service update was performed. For more information, see“DeployingComplex Data Exchange Services” on page 45.

Running on a Cluster ServerIf you install Complex Data Exchange on a cluster server, you must either replicate theComplex Data Exchange repository among the cluster nodes, or you must locate therepository on a shared disk.

Installing on Microsoft Cluster ServerThe following procedure illustrates how to install Complex Data Exchange on MicrosoftCluster Server on Windows XP. For Windows 2000, the procedure is similar with minorvariations.

To i n s t a l l C o m p l e x D a t a E x c h a n g e o n a c l u s t e r s e r v e r :

1 . Run the Complex Data Exchange setup on the active node.

2. When you are prompted for the repository location, assign a path on the quorum disk.

3. Make the other node active, and repeat steps 1-2.

Be sure to assign an identical path to the installation folder and to the repository locationon both nodes.

4 . On each node, open the Complex Data Exchange Configuration Editor and edit theCMConfig/General/Reports Directory setting, which is the location where ComplexData Exchange Engine stores log files. The settings on both nodes must point to the samefolder on the quorum disk.

5 . If your Complex Data Exchange system requires a license file, install a copy of the file oneach node. For more information, see“Installing a License File” on page 26.




Backup Requirements

You should make regular backups of several Complex Data Exchange directories and files.

Production EnvironmentIn a production environment where you run Complex Data Exchange Engine, back up thefollowing locations:

♦ The Complex Data Exchange configuration file By default the file is<INSTALL DIR>\



Backup Requirements 83

♦ The Complex Data Exchange configuration file. By default, the file is<INSTALL_DIR>\CMConfig.xml . For more information, see “Configuration Editor” on page 55.

♦ The Complex Data Exchange repository. By default, this is<INSTALL_DIR>\ServiceDB . You should confirm the location by checking the value of the following parameter in theComplex Data Exchange Configuration Editor:

CM Configuration/Directory services/File system/Base Path

♦ The <INSTALL_DIR>\autoInclude\user directory, which stores custom globalcomponents.

If you use identical configurations on multiple servers, you need to back up only a single copy of these items.

In the event of a server failure, you can install Complex Data Exchange in the same location

as on the failed server and restore the backup.

Development EnvironmentBack up the Complex Data Exchange Studio workspaces of the developers in yourorganization. By default, the workspace location of each user is:

My Documents\Informatica\ComplexDataExchange\4.0\workspace

In addition, back up the locations that are listed above for the production environment.

Failure Handling

If a Complex Data Exchange service fails to execute successfully, it returns a failure status tothe calling application. It is the responsibility of the calling application to handle the error.

For example, the application can transmit failed input data to a failure queue. The application

can package related inputs in a transaction to ensure that important data is not lost.In the event of a failure, Complex Data Exchange Engine generates an event log. For moreinformation about viewing and interpreting the log, see “Event Logs” in theComplex Data

h i l G id d “R i d T i P j ” i h C l




Exchange Engine Developer Guide and “Running and Testing Projects” in the Complex DataExchange Studio User Guide .

Index



85

A AIX IBM 8autoInclude

upgrading 66

Bbackup requirements

services and data 83

CCLASSPATH

environment variable 32,34CMReports

setting log location 58COBOL

system requirements 20Configuration Editor 56

using 56configuration file

backing up 56configuration files

multiple 60core dump

preventing 40

Ddatabase connectivity ODBC 74default location

repository 24document

processors 4DSNs

defining 76

EEclipse

installing 4emulators

not supported 41Engine

for running data transformations 4

environment variablestroubleshooting UNIX 38UNIX 32

environment variables fileloading on UNIX 31using multiple 61

event logsremote support interface 39setting location 58

Excelsystem requirements 20

Ffailure handling

administrative approaches 84filenames

effect on upgrade 70fonts

displaying Asian 42

changing on Windows 58default 24

JVMinitialization parameters 39

LLD_LIBRARY_PATH

environment variable 32LDR_CNTRL

AIX environment variable 14

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-



86 Index

displaying Asian 42

Hheap size

Java 39Hewlett-Packard

HP-UX 8HP-UX

Hewlett-Packard 8

IIBM

AIX 8IFConfigLocation4

environment variable 32,34IFCONTENTMASTER_HOME

environment variable 32,34install path

default 23INSTALL_DIR

installation directory 23Installation

instructions 22invocation

in- or out-of-process 50

J Java

heap and stack size 39 JRE system requirement 9 JVM initialization parameters 39preventing core dump 40

JRE JVM initialization parameters 39

JRE path

changing on UNIX 32

AIX environment variable 14LIBPATH

environment variable 32libraries

predefined data transformations 4

license fileconfirming validity 26installing 26

limited usersrestrictions 80

Linuxoperating system 8

load balancingmultiple servers 81

log fileslocation of 38

log pathdefault 24setting location 58

MMicrosoft Office

system requirements 20

Nnamespace

variables 70

OODBC

configuring 74installing driver 75installing manager on UNIX 75using 76

operating systems

supported 8

out-of-processinvocation 50

PPATH

environment variable 32Path

environment variable 34PDF


sixty-four bit processesactivating 50

sizing guidelinesmultiple servers 82

SolarisSun 8

stack size

Java 39SunSolaris 8

syntax conversion tooldi j t 66

http://-/?-

http://-/?-



Index 87

y qpermissions

required for users 79policies

administration 78

PowerPointsystem requirements 20processors

document 4project

definition 5projects

upgrading 66upgrading from previous version 64

Rremote support interface

event logs 39reports path

default 24setting location 58

repository pathdefault 24setting location 58

Sschemas

upgrading 70

serversmultiple 81services

deploying 45upgrading 66

setup wizard 23

SHLIB_PATHenvironment variable 32

upgrading projects 66system requirements

AIX 14HP-UX 18

JRE 9Linux 17Solaris 11

Windows 10

Ttemp directory

free space requirement 16

troubleshootinginstallation 38UNIX environment variables 38

Uuninstalling

software 28

unsupported featureson UNIX systems 8

upgradingmodified components 70multiple computers 22projects 64services and projects 66

userspermissions 79

Windows user types 79

Vvariables

namespace 70

W Word


http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-



88 Index