CDE 44 Administrator Guide

Complex Data Exchange
Administrator Guide
Informatica Complex Data Exchange™

(Version 4.4)
Complex Data Exchange Administrator Guide
Version 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 containing
restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be
reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This
Software is protected by U.S. Patent Numbers 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 as
provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR
52.227-14 (ALT III), as applicable.
The information in this software and documentation is subject to change without notice. Informatica Corporation does not warrant that this software or
documentation is error free.
Informatica, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica
Data Quality, Informatica Data Explorer, Informatica Complex Data Exchange and Informatica On Demand Data Replicator are trademarks or registered
trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade
names or trademarks of their respective owners.
Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright © Sun Microsystems. All
rights 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 at
http://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 Public
License 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 particular
purpose.
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 or
implied. 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 Lesser
General 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 fitness
for a particular purpose.
This product includes Curl software which is Copyright 1996-2007, Daniel Stenberg, <daniel@haxx.se>. All Rights Reserved. Permissions and limitations
regarding this software are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission to use, copy, modify, and distribute this software for
any 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. Permissions
and 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 this
software 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 limited
to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. The information provided in this documentation may include
technical inaccuracies or typographical errors. Informatica could make improvements and/or changes in the products described in this documentation at any
time without notice.
Part Number: CDE-ADM-44000-0001

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Other Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Visiting Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Visiting the Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Visiting the Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . . xi
Obtaining Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Online Conversion Agent Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Chapter 1: Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Essential Administrative Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Installing Complex Data Exchange on Windows . . . . . . . . . . . . . . . . . . . 2
Installing Complex Data Exchange on UNIX . . . . . . . . . . . . . . . . . . . . . . 2
Testing the Complex Data Exchange Installation . . . . . . . . . . . . . . . . . . . 2
Running Data Transformations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Configuring Complex Data Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Upgrading Existing Data Transformations . . . . . . . . . . . . . . . . . . . . . . . . 3
Using ODBC Database Support Features . . . . . . . . . . . . . . . . . . . . . . . . . 3
Deploying Complex Data Exchange in an Organization . . . . . . . . . . . . . . 3
Complex Data Exchange Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Chapter 2: System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Supported Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
UNIX-Type Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Windows System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
JRE Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Solaris System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Solaris 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Solaris 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
iii
Solaris 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Confirming Packages and Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
JRE Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
AIX System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
AIX 5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
AIX 5.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Confirming Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
JRE Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Linux System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
SUSE Linux 9 and Red Hat Linux EL3 on x86 . . . . . . . . . . . . . . . . . . . . 17
SUSE Linux 9 and Red Hat Linux EL4 on x86-64 . . . . . . . . . . . . . . . . . 17
Confirming Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
HP-UX System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
HP-UX 11.23 on PA-RISC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
HP-UX 11.23 on ia64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Confirming Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Third-Party Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Microsoft Office Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
PDF and COBOL Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Chapter 3: Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Upgrading from a Previous Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Running the Setup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Post-Setup Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Installing a License File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Loading Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Configuring In-Process or Out-of-Process Invocation . . . . . . . . . . . . . . . 26
Configuring ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Testing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Uninstalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
iv Table of Contents
Chapter 4: Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Loading the Environment Variables on UNIX Platforms . . . . . . . . . . . . . . . . 31
Loading from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Loading Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
UNIX Environment Variable Reference . . . . . . . . . . . . . . . . . . . . . . . . . 32
Example of Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Windows Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Chapter 5: Testing and Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . 35

Complex Data Exchange Engine Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Document Processor Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Installation Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
UNIX Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Java Heap and Stack Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Preventing Core-File Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
LDR_CNTRL Environment Variable on AIX . . . . . . . . . . . . . . . . . . . . 40
LD_PRELOAD Environment Variable on HP-UX . . . . . . . . . . . . . . . . . 40
Memory Allocation on HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Emulators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Asian Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Chapter 6: Running Data Transformations . . . . . . . . . . . . . . . . . . . . . 43

Designing and Configuring Data Transformations . . . . . . . . . . . . . . . . . . . . 44
Deploying Complex Data Exchange Services . . . . . . . . . . . . . . . . . . . . . . . . 45
Repository Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Deploying on the Studio Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Deploying on Another Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Re-Deploying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Running Complex Data Exchange Services . . . . . . . . . . . . . . . . . . . . . . . . . 47
Chapter 7: Running In-Process or Out-of-Process. . . . . . . . . . . . . . . 49

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Relative Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Determining whether to Run In-Process or Out-of-Process . . . . . . . . . . . 50
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
v
Chapter 8: Configuration Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Using the Configuration Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Backing Up the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Assigning the Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Missing Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Saving the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Directory Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Copying the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Multiple Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Creating Multiple Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Selecting the Configuration at Runtime . . . . . . . . . . . . . . . . . . . . . . . . . 60
Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Multiple JREs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Running Multiple Configurations Concurrently . . . . . . . . . . . . . . . . . . . 61
Chapter 9: Upgrading Complex Data Exchange Projects . . . . . . . . . . 63

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
When Is Upgrading Necessary? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Upgrading an Individual Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Upgrading a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Syntax Conversion Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Version Support on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Version Support on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Before Running the Tool: Organize Your Projects . . . . . . . . . . . . . . . . . . 66
Running the Syntax Conversion Tool . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Running from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Upgrade Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
New and Modified Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Modified Namespace for Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Unsupported File and Directory Names . . . . . . . . . . . . . . . . . . . . . . . . . 70
XSD Schemas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Chapter 10: Using Complex Data Exchange with ODBC . . . . . . . . . . 73

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
vi Table of Contents
Installing and Configuring an ODBC Manager on UNIX . . . . . . . . . . . . . . . 75
Installing an ODBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Defining DSNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Using a DSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Chapter 11: Administration and Deployment Policies . . . . . . . . . . . . 77

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Studio Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Engine Runtime Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Standard Windows User Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Multiple Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Copying the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Deploying Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Running on a Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Sizing Guidelines for SAP XI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Backup Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Production Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Development Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Failure Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Table of Contents vii

viii Table of Contents
Preface
Welcome to Informatica Complex Data Exchange, the leading software for automating
complex 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 Data
Exchange to transform any data format to any data format, whether the data is structured or
unstructured, 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. The
Complex Data Exchange libraries provide predefined transformations supporting industry
standard data formats.
Complex Data Exchange is fully integrated with Informatica PowerCenter and with
numerous external systems. PowerCenter applications use the Complex Data Transformation
to activate Complex Data Exchange services and perform data transformations.
ix
About This Book
The Complex Data Exchange Administrator Guide is written for system administrators and
users 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 Conventions
This guide uses the following formatting conventions:
If you see… It means…
italicized text The word or set of words are especially emphasized.
boldfaced text Emphasized subjects.
italicized monospaced text This is the variable name for a value you enter as part of an
operating system command. This is generic text that should be
replaced with user-supplied values.
Note: The following paragraph provides additional facts.
Tip: The following paragraph provides suggested uses.
Warning: The following paragraph notes situations where you can overwrite
or corrupt data, unless you follow the specified procedure.
monospaced text This is a code example.
bold monospaced text This is an operating system command you enter from a prompt to
run a task.
x Preface
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 the
Informatica user community.
Visiting the Informatica Web Site

You may access the Informatica corporate web site at http://www.informatica.com. The site
contains information about Informatica, its background, upcoming events, and sales offices.
You will also find product and partner information. The services area of the site includes
important information about technical support, training and education, and implementation
services.
Visiting the Informatica 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 known
technical issues about Informatica products. You may also find answers to frequently asked
questions, technical white papers, and technical tips.
Obtaining Customer Support

There are many ways to access Informatica Global Customer Support. You may contact a
Customer Support Center by using the telephone numbers listed the following table, you can
send email, or you can use the WebSupport Service.
Use the following email addresses to contact Informatica Global Customer Support:
♦ support@informatica.com for technical inquiries
♦ support_admin@informatica.com for general customer service requests
Preface xi
WebSupport requires a user name and password. You can request a user name and password at
http://my.informatica.com.
North America / South America Europe / Middle East / Africa Asia / Australia
Informatica Corporation Informatica Software Ltd. Informatica Business Solutions

Headquarters 6 Waltham Park Pvt. Ltd.
100 Cardinal Way Waltham Road, White Waltham Diamond District
Redwood City, California Maidenhead, Berkshire Tower B, 3rd Floor
94063 SL6 3TN 150 Airport Road
United States United Kingdom Bangalore 560 008
India
Toll Free Toll Free Toll Free

877 463 2435 00 800 4632 4357 Australia: 00 11 800 4632 4357
Singapore: 001 800 4632 4357
Standard Rate Standard Rate Standard Rate

United States: 650 385 5800 Belgium: +32 15 281 702 India: +91 80 4112 5738
France: +33 1 41 38 92 26
Germany: +49 1805 702 702
Netherlands: +31 306 022 797
United Kingdom: +44 1628 511 445
xii Preface
Chapter 1
Overview
This chapter includes the following topics:

♦ Essential Administrative Tasks, 2
♦ Complex Data Exchange Modules, 4
♦ Terminology, 5
1
Essential Administrative Tasks
This book explains how to administer the Complex Data Exchange data transformation
software. It covers subjects such as installing and configuring Complex Data Exchange,
diagnosing and solving system problems, and administering Complex Data Exchange on a
network.
The following paragraphs outline some of the essential administrative tasks.
Installing Complex Data Exchange on Windows

For 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 UNIX

Complex 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 Transformations

If 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, for
example, to:
♦ Invoke Complex Data Exchange either in-process or out-of-process of its calling
application
2 Chapter 1: Overview
♦ 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 Transformations

If you have upgraded from a previous Complex Data Exchange version, you must also
upgrade the data transformation projects and services that you run in Complex Data
Exchange. For more information, see:
♦ “Upgrading Complex Data Exchange Projects” on page 63
Using ODBC Database Support Features

If 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 Organization

If you are deploying Complex Data Exchange to multiple computers throughout an
organization, 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
Essential Administrative Tasks 3

Complex Data Exchange Modules
This book describes the installation and administration of the following Complex Data
Exchange modules:
Required/
Module Description
Optional
Complex Data Exchange Required The runtime module that executes Complex Data Exchange data
Engine transformations. This module is required in all Complex Data Exchange
installations.
Complex Data Exchange Engine runs on both Windows and UNIX-type
platforms.
Complex Data Exchange Optional The design and configuration environment where you can create and
Studio deploy data transformations.
Complex Data Exchange Studio is hosted within Eclipse on Windows
platforms. The Eclipse setup is included in the Complex Data Exchange
installation package.
Document Processors Optional A set of components that perform global processing operations on
documents, such as transforming their file formats.
All the document processors run on Windows platforms, and most of them
run 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 Complex
Data Exchange 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 Exchange
documentation.
You can install the documentation on Windows platforms. For use on UNIX-
type platforms, you can use the PDF versions of the documents.
In addition to the above modules, there are optional integration agents that interface
Complex Data Exchange with third-party software systems. For information about installing
and administering these agents, see the manual for each agent.
Terminology
In the course of installing and administering the Complex Data Exchange software, you are
likely 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 Definition
Data transformation The conversion of data from one structure or format to another, possibly
accompanied by modification of the data values.
Project A collection of files and resources that are necessary to define and execute a
data transformation. Each project is stored in a directory.
Complex Data Exchange service A data transformation that is available to be executed in Complex Data
Exchange 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 it
available as a Complex Data Exchange service.
JRE Java Runtime Environment, required to install and run Complex Data
Exchange. Also known as JVM, Java Virtual Machine.
Terminology 5
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
7
Supported Systems
You can install and run Complex Data Exchange on the following operating systems.
Microsoft Windows
On Microsoft Windows, you can install all Complex Data Exchange modules such as
Complex 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 Complex
Data Exchange services, we recommend at least 512 MB of RAM and a CPU speed of at least
1 GHz.
UNIX-Type Systems
On UNIX-type operating systems, you can install Complex Data Exchange Engine and the
document 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 as ExcelToXml,
WordToXml, and XmlToExcel, do not require the Office applications and operate on UNIX.
Hardware Requirements
The minimum RAM requirement is 256 MB. For a system running production Complex
Data Exchange services, we recommend at least 512 MB of RAM and a CPU speed of at least
1 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:
8 Chapter 2: System Requirements

♦ For AIX, HP, and Solaris: ulimit –a
♦ For Linux: limit
If you process very large documents using Complex Data Exchange, try adjusting system
parameters 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 Exchange
setup installs a JRE on your computer.
Optionally, you can use another JRE version, which you install independently on the
computer. For the supported JRE versions, see the specific requirements for your operating
system.
After you install Complex Data Exchange, it is possible to change the selected JRE. For
example, 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” on
page 32.
JRE for Use with Java API

If you use the Complex Data Exchange Java API to activate a Complex Data Exchange
service, any Java components of the service run on the JRE that is used by the external Java
application.
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 Data
Exchange supports.
For more information, see “Running In-Process or Out-of-Process” on page 49.
Supported Systems 9
Windows System Requirements
You can install Complex Data Exchange on a system conforming to the following
requirements:
♦ Microsoft Windows 2000 SP4, XP Professional SP2, or 2003 Server SP1 (32-bit or 64-bit
edition).
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 setup
program installs it automatically.
JRE Version
Complex Data Exchange requires a Sun Java 2 Runtime Environment, version 1.5.0. You can
use the JRE that is installed with Complex Data Exchange, or you can download a JRE from
http://www.sun.com.
The JRE does not need to be defined in your PATH environment variable. In rare instances, the
Complex Data Exchange Java document processors might require that the JRE be defined in
the PATH for proper operation.
Disk Space
The 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 more
information, see Complex Data Exchange Libraries.

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. The
following 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
Solaris 9
You can run Complex Data Exchange on Solaris 9 4/03, on the SPARC platform. The
following packages and patches must be installed:
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 System Requirements 11

111711 12
111712 12
111722 04
112233 12
112839 08
112874 31
112963 25
113029 06
113319 22
113896 06
Solaris 10
You can run Complex Data Exchange on Solaris 10, also known as SunOS 5.10, on the
SPARC platform. The following packages and patches must be installed:
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

120900 04
121133 02
121683 05
122032 04
Confirming Packages and Patches

To 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 Version
http://www.sun.com.
Disk Space
A full Complex Data Exchange installation on Solaris requires approximately 160 MB of disk
space.
Solaris System Requirements 13

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 following
packages must be installed:
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
AIX 5.3
You can run Complex Data Exchange on AIX 5.3 with maintenance level 0. The following
packages must be installed:
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
On some AIX 5.3 computers, the Complex Data Exchange setup fails to run unless you
configure the LDR_CNTRL environment variable. If the setup fails to start, configure the
variable as follows.
To configure the LDR_CNTRL variable:
1. Determine the existing value of the LDR_CNTRL variable, if any. To do this, enter the
following 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

If the result of step 1 was not empty, you must append it to the NOKTRL value. Substitute
the following syntax including the quotation marks:
LDR_CNTRL="NOKTRL result_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 the
quotation 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 determine which maintenance level is installed:
X Run the following command:

oslevel -r
To verify that a required package is installed:
1. Run the following command, which opens the system management console:
smitty
2. Select the options Software Installation and Maintenance > List Software and Related
Information > 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 Version
Complex Data Exchange requires a Java 2 Runtime Environment, version 1.5.0. You can use
the JRE that is installed with Complex Data Exchange, or you can download a JRE from
http://www.ibm.com.
AIX System Requirements 15

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 the temp
directory. To verify the free space, run the following command:
df -k

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 Linux
version EL3, on an Intel x86 or compatible platform. The following packages must be
installed:
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
http://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 Linux
version EL4, on x86-64 platforms such as AMD Opteron.
Complex Data Exchange requires an IBM Java 2 Runtime Environment, version 1.5.0. You
can use the JRE that is installed with Complex Data Exchange, or you can download a JRE
from http://www.ibm.com.
Confirming Packages
To 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.
Linux System Requirements 17

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:
BUNDLE11i B.11.23.0409.3
FEATURE11i B.11.23.0505.022e
HPUXBaseOS 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
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, or
you can download a JRE from http://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:
PHCO_35524 1.0
PHCO_35997 1.0
PHKL_35029 1.0
PHKL_36244 1.0
PHSS_33350 1.0

PHSS_34043 1.0
PHSS_34859 1.0
PHSS_35165 1.0
PHSS_35528 1.0
PHSS_35535 1.0
PHSS_36336 1.0
Complex Data Exchange requires an HP Java 2 Runtime Environment, version 1.5.0. You can
http://www.hp.com.
Confirming Bundles
To confirm that the required bundles have been installed:
X 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.
HP-UX System Requirements 19

Third-Party Applications
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 Applications

To help you parse Microsoft Office documents, such as Word, Excel, or PowerPoint files,
Complex Data Exchange offers several document processors, which convert Microsoft Office
documents to a format such as text, HTML, RTF, or XML. Office versions 97 and higher are
supported.
The text, HTML, and RTF processors run on Microsoft Windows platforms where the Office
applications are installed.
The XML processors do not require the Office application. They run on both Windows and
UNIX-type platforms.
For more information, see “Document Processors” in the Complex Data Exchange Studio User
Guide.
PDF and COBOL Support

Complex Data Exchange contains built-in support for the Adobe Acrobat (PDF) format and
for COBOL data formats. You do not need to install any Acrobat or COBOL software to
process 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.

Chapter 3
Installation

♦ Overview, 22
♦ Running the Setup Wizard, 23
♦ Post-Setup Steps, 26
♦ Uninstalling, 28
21
Overview
This chapter explains how to install Complex Data Exchange on your computer. It covers
installation 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 the
existing 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 a
Complex 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 Computers

Upgrade all Complex Data Exchange computers and components in your organization at the
same time. This avoids version conflicts between projects that you develop on one computer
and 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 Versions

In Windows, it is not possible to install multiple versions or copies of Complex Data
Exchange on the same computer.
On UNIX-type systems, it is possible to install multiple versions or copies in different
directories, provided that you start each copy with the appropriate environment variables. For
more information, see “Environment Variables” on page 29.
22 Chapter 3: Installation
Running the Setup Wizard
To install the Complex Data Exchange software, you should run the setup wizard. In some
Complex Data Exchange versions, the sequence of the wizard pages might differ slightly from
the sequence described here.
To run the Setup wizard:
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, for
example, if you are working from a remote location, add the -console switch to the
command.
./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 Exchange
Configuration Editor.
On Windows: if you plan to change the language in the Configuration Editor, you must
select a non-English language for the setup. If you select English, some of the services
required for other languages might not be installed.
3. Follow the on-screen instructions to start the setup and accept the Complex Data
Exchange license.
4. On the Install Path page, select the directory path where the setup should install the
Complex 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>.
Running the Setup Wizard 23

5. You are prompted to select the Complex Data Exchange components to install. There are
options for components such as:
Component Explanation
Engine Installs Complex Data Exchange Engine.
Studio On Windows only: Installs Complex Data Exchange Studio, which is hosted
within the Eclipse environment.
Document Processors Installs the document processors package.
Libraries On Windows only: Installs the Complex Data Exchange project libraries.
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 Complex
Data Exchange directory. Optionally, you can browse to another supported JRE, which is
already 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 Configuration
Editor. On UNIX, you must edit the environment variables file. For more information,
see “Configuration Editor” on page 55 and “UNIX Environment Variable Reference” on
page 32.
7. On the next page, you are prompted for the Service Repository Path Selection. This is the
storage 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 should
store 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 user
name.
♦ 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 Development
Environment, the wizard displays an Eclipse Configuration page. Select one of the
following options:
♦ Install a standalone copy of Eclipse 3.2. If you select this option, the setup installs a
new copy of Eclipse, which is independent of any other copies of Eclipse that may exist
on the computer.
♦ Optionally, if Eclipse 3.2 is already installed on the computer, you can choose to run
Complex 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 use
Eclipse for other purposes, and you wish to store Complex Data Exchange projects in
your existing Eclipse workspace.
10. On the Summary page, review the setup options. Click Install to complete the
installation.
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 more
information, 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.
Running the Setup Wizard 25

Post-Setup Steps
After you complete the setup, review the following information and perform the required
steps.
Installing a License File

If 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 valid
license file before you can run Complex Data Exchange services on the computer. Contact
Informatica to obtain a Complex Data Exchange license file, CDELicense.cfg. You can use
Complex Data Exchange Studio without installing a license file.
To install a license file:
1. Log on as a user with administrative privileges or as a user with write permission for the
Complex Data Exchange installation directory.
2. Copy the CDELicense.cfg file to the Complex Data Exchange installation directory.
♦ On Windows: The default installation directory is c:\Program Files\Informatica\
ComplexDataExchange.
♦ On UNIX: The default directory is /opt/Informatica/ComplexDataExchange.
To verify the validity of the license file:
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 you
are 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 Complex
Data 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 you
plan to activate it from 64-bit applications. For more information, see “Running In-Process or
Out-of-Process” on page 49.
Configuring ODBC
If you plan to use the ODBC database support features of Complex Data Exchange, you
might need to configure an ODBC driver. For more information, see “Using Complex Data
Exchange with ODBC” on page 73.
Testing the Installation

Test the installation and confirm that Complex Data Exchange operates properly. For more
information, see “Testing and Troubleshooting” on page 35.
Post-Setup Steps 27
Uninstalling
To uninstall Complex Data Exchange:
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 the
services 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 files
remaining in it.
5. On UNIX: Remove the configuration that loads the Complex Data Exchange
environment variables. For more information, see “Environment Variables” on page 29.
Then log out and log in, to ensure that the configuration changes take effect.
Chapter 4
Environment Variables

♦ Overview, 30
♦ Loading the Environment Variables on UNIX Platforms, 31
♦ Windows Environment Variables, 34
29
Overview
The Complex Data Exchange setup assigns several environment variables, which point to the
installation 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 steps
for environment variables.
30 Chapter 4: Environment Variables

Loading the Environment Variables on UNIX Platforms
On UNIX-type platforms, the Complex Data Exchange setup creates an environment
variables file. You must load the file before you can test or use Complex Data Exchange. You
can 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 Line

If you prefer not to load the environment variables automatically, you can load them
manually from the command line. You must do this each time you log in, before you use
Complex 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 Automatically
To configure your system to load the environment variables file automatically when you log
in:
♦ 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-Process

If you configure Complex Data Exchange to run out-of-process, the Complex Data Exchange
Server 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 the
environment-variable file that you load. For more information, see “Running In-Process or
Loading the Environment Variables on UNIX Platforms 31

UNIX Environment Variable Reference
On UNIX-type platforms, Complex Data Exchange uses the following environment variables.
Required/
Environment Variable Purpose of the Variable
Optional
PATH Required The environment variables file adds <INSTALL_DIR>/bin to the

paths.
Note: In rare instances, the Complex Data Exchange Java document
processors require that the JRE be added to the path.
- On AIX: LIBPATH Required The environment variables file adds the installation directory
- On Solaris and Linux: (<INSTALL_DIR>) to the library path.
LD_LIBRARY_PATH It also adds the JVM directory of the JRE and its parent directory to the
- On HP-UX: SHLIB_PATH path, for example, <INSTALL_DIR>/jre1.4/lib/sparc/server
and LD_LIBRARY_PATH and <INSTALL_DIR>/jre1.4/lib/sparc. You can edit this value
to 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 the
Complex 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.
Example of Environment Variables

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

setenv IFCONTENTMASTER_HOME "${IFCMPath}"
# Prepend CM path CLASSPATH

if ( ! $?CLASSPATH ) then
setenv CLASSPATH ""
endif
setenv CLASSPATH "${IFCMPath}/api/lib/CM_JavaAPI.jar:.:${CLASSPATH}"
Loading the Environment Variables on UNIX Platforms 33

Windows Environment Variables
On Windows, the Complex Data Exchange setup creates or modifies the following
environment variables. This information is for reference only. You do not need to perform any
special steps to configure or load the variables.
Required/
Environment Variable Purpose of the Variable
Optional
Path Required The setup adds <INSTALL_DIR>\bin to the path.

Note: In rare instances, the Complex Data Exchange Java document
processors 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 more
information, see “Multiple Configurations” on page 60.

Chapter 5
Testing and
Troubleshooting
♦ Complex Data Exchange Engine Test, 36
♦ Document Processor Test, 37
♦ Installation Troubleshooting, 38
35
Complex Data Exchange Engine Test
After you install the software, perform a quick test to verify that Complex Data Exchange
Engine 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 test the Engine installation:
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 Exchange

project called testCME. Copy the entire testCME directory to the Complex Data
Exchange 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 executes testCME.
CM_console testCME
The service performs a simple data transformation on an HL7 source document. The
following result should be displayed:
<Result>Test Succeeded</Result>
36 Chapter 5: Testing and Troubleshooting

Document Processor Test
If you installed the document processors, you can test the installation by running a service
called testCMDP. The service converts an Excel spreadsheet file to XML. It uses the
ExcelToXml document processor to perform an initial conversion stage.
To test the document processor installation:
1. In the directory <INSTALL_DIR>\setupTests, there is a sample Complex Data Exchange

project called testCMDP. Copy the entire testCMDP directory to the Complex Data
Exchange 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>
Document Processor Test 37

Installation Troubleshooting
If you experience difficulty installing or running Complex Data Exchange, check the
following points.
UNIX Environment Variables

On a UNIX-type platform, if the installation tests fail, the system is probably not setting
some or all of the environment variables that Complex Data Exchange requires.
To resolve an environment variable problem:
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 test
still 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 Data
Exchange server accesses <INSTALL_DIR>/setEnv.sh to obtain the environment variable
settings. 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 Global
Customer Support.
Log Files
Complex Data Exchange generates several log files, which are useful for troubleshooting
purposes.
Installation Logs
The setup creates a set of logs in the <INSTALL_DIR>\Inst_logs directory. You can examine
the logs for any error messages.

Complex Data Exchange Studio Log
By 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
Complex Data Exchange Studio menu. On the left side of the window, select Complex Data
Exchange. 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 called
Events.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 Logs

If a failure occurs in a Complex Data Exchange service, the Engine creates an event log. You
can view the log by dragging the *.cme file to the Events view of the Studio.
For more information, see “Event Logs” in the Complex Data Exchange Engine Developer
Guide.
Java Heap and Stack Size

If 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 be
an inadequate Java heap size or stack size.
To set the Java heap size:
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 multiple
InitParam lines. Enter each parameter on a separate line.
To control the Java stack size, see the JRE documentation.
Installation Troubleshooting 39
Preventing Core-File Generation
When processing very large inputs, a Java out-of-memory condition might cause Complex
Data Exchange Engine to shut down unexpectedly and generate a core file. This has been
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 AIX

On some AIX 5.3 computers, the Complex Data Exchange setup fails to run unless you
configure the LDR_CNTRL environment variable. For more information, see “AIX System
Requirements” on page 14.
LD_PRELOAD Environment Variable on HP-UX

On HP-UX systems, you might need to set the LD_PRELOAD environment variable to run
certain types of Complex Data Exchange applications. Specifically, you need to set the
environment variable if:
♦ The Complex Data Exchange service is configured with a Java document processor, such
as:
− 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 set LD_PRELOAD to point to the libjvm shared object
of the JRE.
Examples
On an HP-UX PA-RISC platform, the libjvm object is called libjvm.sl. Enter a command
such 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_PRELOAD should point to a 64-bit JRE. The two
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"
Incompatibilities
The LD_PRELOAD setting is incompatible with applications that call the Complex Data
Exchange Java API or that run tcsh scripts. Before you run such applications, you must unset
the environment variable:
unsetenv LD_PRELOAD
If you frequently run both C++ and Java applications in the same HP-UX environment, you
can configure them to run in different shells. In the shell that you use for the C++ application,
you can add the LD_PRELOAD setting to the profile.
Alternatively, you can create two shell scripts, which set or unset the LD_PRELOAD variable.
C++ applications should run the script that sets LD_PRELOAD, before they activate Complex
Data Exchange Engine. Java applications should run the script that unsets LD_PRELOAD, before
activating Complex Data Exchange Engine.
Memory Allocation on HP-UX

By default, HP-UX systems allocate virtual memory to a process in four 1-GB quadrants, as
follows:
♦ 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 the chatr utility. For
more information, refer to the HP-UX documentation.
Emulators
You should install and run Complex Data Exchange on native operating systems. Running on
emulators is not supported.
For example, do not run Complex Data Exchange for HP-UX PA-RISC on an HP-UX ia64
machine with a PA-RISC emulator.
Installation Troubleshooting 41
Asian Fonts
The 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.

Chapter 6
Running Data
Transformations
♦ Designing and Configuring Data Transformations, 44
♦ Deploying Complex Data Exchange Services, 45
♦ Running Complex Data Exchange Services, 47
43
Designing and Configuring Data Transformations
Complex Data Exchange users can design, configure, and test data transformations by using
Complex Data Exchange Studio on a Windows platform. Among the possible transformation
components 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 the
following documents:
♦ Getting Started with Complex Data Exchange—provides basic instructions and tutorial
exercises for using the entire Complex Data Exchange system
♦ Complex Data Exchange Studio User Guide—explains how the data transformations operate
and how to configure them
♦ Using Complex Data Exchange Studio in Eclipse—explains how to use the Complex Data
Exchange Studio user interface, which is hosted in the Eclipse development environment
44 Chapter 6: Running Data Transformations

Deploying Complex Data Exchange Services
To run a data transformation in Complex Data Exchange Engine, a user must first deploy it as
a Complex Data Exchange service. The deployment procedure copies the Studio project to a
repository, where it is available to run in Complex Data Exchange Engine. For more
information, see “Deploying Complex Data Exchange Services” in the Complex Data
Exchange Studio User Guide.
Repository Location
On 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 the Base 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 deploy a Complex Data Exchange service to the Studio computer:
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 deploy a Complex Data Exchange service to a UNIX-type platform:
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 the
repository on the remote computer.
3. Complex Data Exchange Engine determines whether any services have been revised by
periodically examining the timestamp of a file called update.txt. By default, the
timestamp is examined every thirty seconds.
The update.txt file exists in the repository root directory which is, by default, the
ServiceDB 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.
Deploying Complex Data Exchange Services 45

♦ On UNIX: Open a command prompt, change to the repository directory, and enter
the following command.
touch update.txt
Re-Deploying
After deploying a Complex Data Exchange service, if you edit the data transformation in the
Studio, 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.
♦ 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.
Running Complex Data Exchange Services 47

Chapter 7
Running In-Process or
Out-of-Process
♦ Overview, 50
♦ Configuration, 52
49
Overview
You can configure Complex Data Exchange Engine to run either in the process of the calling
application or out-of-process.
Out-of-process invocation requires the use of Complex Data Exchange Server. For more
information, see the Complex Data Exchange Engine Developer Guide.
This option has no effect on Complex Data Exchange Studio or on the CM_console
command, which always run data transformations in-process.
Relative Advantages
Running 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-Process

Consult 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 Java
process or a 64-bit Java process.
If You Call Complex Data If You Call Complex Data

Complex Data
Platform Exchange from a 32-bit Exchange from a 64-bit
Exchange Version
Process, You can Choose Process, You can Choose
Windows 32-bit In-process or out-of-process Out-of-process
Solaris 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 32-bit In-process or out-of-process

Hat Linux EL3 on x86
50 Chapter 7: Running In-Process or Out-of-Process

If You Call Complex Data If You Call Complex Data
Complex Data
Platform Exchange from a 32-bit Exchange from a 64-bit
Exchange Version
Process, You can Choose Process, You can Choose
SUSE Linux 9 or Red 64-bit In-process or out-of-process

Hat Linux EL4 on x86-64
HP-UX 64-bit Out-of-process In-process or out-of-process
Determining Your Complex Data Exchange Version

If you are not sure whether you have a 32-bit or 64-bit Complex Data Exchange version, open
a command prompt and run the command:
CM_console -v
Among other information, the command displays a package identifier, which is a code that
uniquely identifies your Complex Data Exchange version. The code contains the substring 32
or 64.
Overview 51
Configuration
To select in-process or out-of-process invocation:

♦ On Windows: On the Start menu, click All Programs > Informatica > Complex Data
Exchange > 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 the
CM Engine node and add it.
Setting Explanation
Invocation Select the value InProc for in-process invocation.

Select Server for out-of-process invocation. This causes the Engine request to be routed
via Complex Data Exchange Server. For each client process that submits requests, the
Server starts an independent Engine process.
4. Edit the settings under the following node:

CM Configuration/CM Engine/CM Server
These settings have an effect only if you have set Invocation = Server. If the settings
are not displayed, right-click the CM Server node and add them.
Required/
Setting Explanation
Optional
Server Path Required on The path to the CM_Server.sh shared object. Set its value to:
UNIX <INSTALL_DIR>/bin/cm_server.sh
You should also confirm that cm_server.sh has execute
permission. You can do this by running the command:
chmod a+x <INSTALL_DIR>/bin/cm_server.sh
The 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 requests
exceeds the number of available threads, the Server queues the
requests until a thread is available. The default is 4.
Thread Stack Size Optional The stack size, in kilobytes, that the Server allocates to each
thread. The default is 1024.

Required/
Setting Explanation
Optional
Init Engine Optional If the value of this parameter is OnDemand, the Server starts the
Engine when the client application first issues a request. If the
value is OnStartup, the Server starts the Engine when the client
application is loaded. The default is OnDemand.
Number of retries Optional If a client process receives no response from the Server, it attempts
Restart timeout a Server restart. These parameters control the restart behavior:
The Number of retries is the maximum number of permitted
restarts, and the Restart timeout is the time interval in
seconds. If the number of required restarts exceeds the specified
value, within the time interval, the client process ceases all further
attempts.
The default values are Number of retries = 4 and Restart
timeout = 900. This means that if the client process needs to
restart the server more than 4 times in 900 seconds, it ceases the
attempts.
This behavior is regardless of the number of successful requests
during the timeout period. In the above example, if the client
process successfully communicates with the server 100 times
during the 900-second interval, but it fails 5 times, it ceases further
attempts.
The behavior is per client process. If there are multiple client
processes, then each of them is permitted 4 restarts during the
timeout interval.
The restarts refer only to the communication between the client
process 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.
5. If you run out-of-process, confirm that the environment variables settings are correct in
the setEnv.sh file. For more information, see “Environment Variable File when Running
Configuration 53
Chapter 8
Configuration Editor

♦ Using the Configuration Editor, 56
♦ Configuration Settings, 58
♦ Copying the Configuration File, 59
♦ Multiple Configurations, 60
55
Using the Configuration Editor
Complex Data Exchange has a Configuration Editor, which lets you edit the parameters of a
Complex Data Exchange installation.
Usually, you need to use the Configuration Editor only in the following circumstances:
♦ 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 Global
Customer 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 Exchange
installations. Some additional settings vary depending on the Complex Data Exchange
version and on the optional components that you have installed.
Backing Up the Configuration File

The 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 a
problem, 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 Data
Exchange. Restoring CMConfig.bak returns Complex Data Exchange to its original
configuration.
Assigning the Settings

The editor has an Explorer-type window. On the left side, expand the tree and select the
desired 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 browse
option. 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.
56 Chapter 8: Configuration Editor

Missing Settings
If a setting is not displayed, Complex Data Exchange uses its default value. To display the
setting and edit its value, right-click its parent node and click the Add option.
Saving the Configuration File

Click the Save icon to save the edited settings. If you forget to save, the Configuration Editor
displays a reminder when you exit.
Using the Configuration Editor 57

Configuration Settings
The following are the most common configuration settings that you might need to edit. You
can assign these settings when you run the Complex Data Exchange setup. If necessary, you
can change the settings afterwards in the Configuration Editor.
There are many additional settings, which are described in the relevant locations throughout
the 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 can
alter the locations by editing the following parameters:
Parameter Explanation
CM Configuration/ The Complex Data Exchange repository location, where Complex Data
Directory services/ Exchange services are stored.
File system/Base Path
CM Configuration/ On Windows: The JRE location, for example:

CM Engine/ <INSTALL_DIR>/jre1.4/bin/client
JVM Location If you edit the path, do not uninstall the previous JRE version until you save
the new setting and exit the Configuration Editor. This is important because
the Configuration Editor itself requires a JRE.
On UNIX: This parameter is not available in the Configuration Editor on
UNIX-type platforms. For more information about setting the JRE on UNIX,
see “UNIX Environment Variable Reference” on page 32.
CM Configuration/ The log path, also called the reports path, where Complex Data Exchange
General/ saves event logs and certain other types of reports.
Reports directory
CM Configuration/ These settings control whether Complex Data Exchange Engine runs in-
CM Engine/ process or out-of-process. For more information, see “Running In-Process
Invocation
or Out-of-Process” on page 49.
CM Configuration/
CM Engine/
CM Server

Copying the Configuration File
You can copy a configuration file between identical computers, running the same operating
system and the same version of the software. This is a convenient way, for example, to ensure
that a set of identical servers all use the same Complex Data Exchange configuration.
Note: Avoid copying between non-identical systems, as the configurations might be
incompatible. For example, the configuration file on a Windows system contains the JVM
Location parameter. On a UNIX-type system, this parameter must not exist. If it does,
Complex Data Exchange does not run correctly.
Copying the Configuration File 59

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 Exchange
repositories for different types of services. You can create configurations that have different
values of the repository location setting.
Creating Multiple Configurations

You can create multiple configurations by editing and copying the default configuration file.
To create multiple configuration files:
1. Make a backup copy of the default configuration file, <INSTALL_DIR/CMConfig.xml>. At

the 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 called IFConfigLocation4. 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's
home directory.
♦ Use the default configuration file, <INSTALL_DIR>/CMConfig.xml.
When Complex Data Exchange Engine starts, it searches these locations in sequence. It uses
the first configuration file that it finds.
Example 1
You want to run two applications with different configuration files. Each application should
set the value of IFConfigLocation4 before it starts Complex Data Exchange Engine.

Example 2
Two users want to run Complex Data Exchange Engine with different configurations, on the
same UNIX-type platform. Store their respective configuration files in their home directories.
Both files must have the name CMConfig.xml.
Alternatively, store a CMConfig.xml file in the home directory of one of the users. The other
user uses the default configuration file, <INSTALL_DIR>/CMConfig.xml.
Multiple JREs
On 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 can
switch JREs.
On UNIX-type systems, the configuration file does not contain a JVM Location parameter.
To switch JREs, you must load a different environment variables file. For information, see
“Environment Variables” on page 29.
Running Multiple Configurations Concurrently

Complex 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. Each
application uses the configuration that was in affect when its instance of Complex Data
Exchange Engine started.
Multiple Configurations 61
Chapter 9
Upgrading Complex Data

Exchange Projects
♦ Overview, 64
♦ Upgrading an Individual Project, 65
♦ Syntax Conversion Tool, 66
♦ Upgrade Issues, 70
63
Overview
If you are upgrading from a previous Complex Data Exchange release, you can upgrade your
existing 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
Studio, or you can run a syntax conversion tool that upgrades all your projects or services
together.
Note: If you run an upgrade setup from a previous Complex Data Exchange 4 release, the
setup prompts you to upgrade your existing services. In other cases, perform the upgrade
yourself, after you complete the setup.
When Is Upgrading Necessary?

Upgrading is necessary when the syntax version of Complex Data Exchange Engine has
changed.
To determine the syntax version, open a command prompt and run the following command:
CM_console -v
Terminology
In Complex Data Exchange 3.x and 4, certain terms are used in slightly different ways. To
prevent confusion, we use the Complex Data Exchange 4 terminology throughout the
upgrade instructions, unless otherwise stated.
The following table presents the corresponding terms.
Complex Data Complex Data Exchange

Description
Exchange 4 3.x
Project Workspace A directory containing a data transformation configuration: a

CMW file, one or more TGP script files, etc.
Workspace No corresponding term The default parent directory, where Complex Data Exchange
Studio 4 stores projects.
Deploy Publish Make a project available as a service.
Repository Services database location The parent directory where Complex Data Exchange services are
stored.
64 Chapter 9: Upgrading Complex Data Exchange Projects

Upgrading an Individual Project
On a Windows computer, you can upgrade an individual project by opening or importing it
in Complex Data Exchange Studio.
Perform the import by clicking File > Import. In the Import window, select the option to
import an Existing Complex Data Exchange Project into Workspace.
Complex Data Exchange Studio prompts you to upgrade the project if necessary. The upgrade
is 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 Data
Exchange service.
To do this, open or import the development copy in Complex Data Exchange Studio. Test the
project, and re-deploy it as a service.
Upgrading an Individual Project 65

Syntax Conversion Tool
You can use the Complex Data Exchange syntax conversion tool to upgrade multiple projects
and services quickly, in an automated operation. You can also use it to upgrade global TGP
script files, which are stored in the Complex Data Exchange autoInclude\user directory.
Before the upgrade, the tool creates an automatic backup of your existing projects and files. It
creates a log file and reports any upgrade errors that it detects. In case of an error, restore the
backup, correct the problem, and run the tool again.
Version Support on Windows

On Windows, the syntax conversion tool can upgrade projects or services from Complex Data
Exchange 3.1 and higher.
Version Support on UNIX

On UNIX-type platforms, the tool can upgrade services from earlier Complex Data Exchange
4 releases.
To upgrade Complex Data Exchange 3.x services:
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 Projects

The tool operates on projects or services that are stored in a single parent directory. It can
operate 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 them
before running the tool. Alternatively, you can run the tool separately on the individual
parent directories.

The tool also operates on the Complex Data Exchange autoInclude\user directory, which
contains global TGP script files.
Running the Syntax Conversion Tool
To run the syntax conversion tool:
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:
Option Explanation
Source Location The parent directory containing the old projects, or the repository containing the old
services.
Target Location The parent directory where the tool should store the new projects, or the repository for the
new services. If the target is the same as the source, the original files are overwritten.
4. If you have any TGP files in the autoInclude\user directory, set the following options
on the AutoInclude tab:
Option Explanation
Source Location The old autoInclude\user directory.
Target Location The new autoInclude\user directory.
5. Set the following options on the Result Files tab:
Option Explanation
Backup 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.
6. Click the Start button.

The tool reports its progress and results.
Syntax Conversion Tool 67

7. You can repeat steps 3, 5, and 6 on any additional parent directories that contain projects
or services. For example, you can upgrade a Complex Data Exchange Studio workspace
where you store development projects, in addition to a repository where you store
deployed services.
The AutoInclude options should be blank on the repeat runs. The AutoInclude files were
already 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
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.
10. 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 “Upgrade
Issues” on page 70.
Running from the Command Line

Optionally, you can run the syntax conversion tool from the command line, without
displaying the graphical user interface.
To run the syntax conversion tool from the command line:
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.
Required/
Switch Description
Optional
-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 existing
directory.
-si Optional Path of the source autoInclude\user directory. If you omit this switch, the tool
does not upgrade global TGP files.
-di Optional Path of the target autoInclude\user directory. If you omit this switch, the tool
overwrites the existing directory.
-l Optional Path of the upgrade log file. The default is <INSTALL_DIR>\

SyntaxConversionLog.txt.

Required/
Switch Description
Optional
-b Optional Path of the backup directory, where the tool backs up the original projects or services
prior to the upgrade. The default is the value of the -s switch concatenated with the
suffix _OLD_Backup.
-e Optional Path of the error directory, where the tool stores any projects or services that it
cannot upgrade due to an error. The default is the value of the -s switch
concatenated with the suffix _OLD_Failure.
Following each switch, leave a space and type the value. If a path contains spaces, you
must 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.
Syntax Conversion Tool 69

Upgrade Issues
The automatic upgrade successfully upgrades nearly all the features that existed in previous
Complex Data Exchange versions. Nonetheless, it is important that you test the data
transformation 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.
New and Modified Components

In version 4, some of the Complex Data Exchange components that you can use in data
transformations have been revised, renamed, or replaced by new components. When you
upgrade a project, Complex Data Exchange inserts the new components automatically.
For more information on some components that have been modified, see the document
What's New in Complex Data Exchange. In most cases, the modifications do not change the
behavior 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 the Locator 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 the EnsureCondition and
CalculateValue actions might change slightly due to the introduction of a new JavaScript
processor. For more information on the supported JavaScript syntax, see the
EnsureCondition action in the Complex Data Exchange Studio User Guide.
Modified Namespace for Variables

Starting 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 Schema
view and the project properties display both the old empty namespace and the new namespace
that contains your variables. This has no effect on the operation of your project.
Unsupported File and Directory Names

In Complex Data Exchange 4, the names of project files and directories may contain English
letters (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 to
upgrade. If this occurs, change the names in version 3.x before running the tool.
XSD Schemas
In 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 creates
an XSD schema automatically. Review the schema and confirm that it meets your needs. You
can 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
Using Complex Data

Exchange with ODBC
♦ Overview, 74
♦ Installing and Configuring an ODBC Manager on UNIX, 75
♦ Defining DSNs, 76
73
Overview
Complex Data Exchange offers ODBC connectivity features that allow it to interact with
database systems. For more information about the capabilities, see the ODBCLookup
transformer and the ODBCAction action in the Complex Data Exchange Studio User Guide.
On Windows platforms, Complex Data Exchange uses the built-in Microsoft ODBC
manager. On UNIX-type platforms, you must configure an ODBC manager before you can
use the ODBC features.
On both Windows and UNIX, you might need to install an ODBC driver. You should define
one or more DSNs, which Complex Data Exchange uses to connect to the database.
74 Chapter 10: Using Complex Data Exchange with ODBC

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 or
database vendor.
You should add the directory location of the ODBC manager to your LIBPATH or
LD_LIBRARY_PATH environment variable.
To configure the ODBC manager in Complex Data Exchange:

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 called ODBC manager shared library path to the display.
4. Set the value of the parameter to the location of the ODBC manager shared object, for
example:
/usr/local/odbc/libODBCMgr.so
Installing an ODBC Driver

An ODBC driver for your database system must be installed on the computer. The driver
might be supplied with the database system, or you can obtain it from your platform or
database vendor.
Troubleshooting
If 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 following
error:
Failed to load ODBC API
Installing and Configuring an ODBC Manager on UNIX 75

Defining DSNs
You should define one or more DSNs, which Complex Data Exchange can use to connect to
the 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.
Using a DSN
To connect to a database, configure a Complex Data Exchange data transformation with a
component such as ODBCLookup or ODBCAction. In the db_connection property of the
component, specify the DSN that you defined above.
76 Chapter 10: Using Complex Data Exchange with ODBC

Chapter 11
Administration and
Deployment Policies
♦ Overview, 78
♦ Security, 79
♦ Multiple Servers, 81
♦ Failure Handling, 84
77
Overview
If you are administering Complex Data Exchange in a large organization, you need to
establish 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
environments
♦ Backup requirements
♦ Failure handling
This chapter discusses the key issues and describes some approaches for implementing the
policies.
78 Chapter 11: Administration and Deployment Policies

Security
Below, we list the typical permissions that are required by users who install and use Complex
Data Exchange Studio and Engine. Of course, there might be exceptions to the list, and
additional permissions might be required, depending on the Complex Data Exchange
applications that your organization runs.
Studio Permissions
Users who configure data transformations in Complex Data Exchange Studio typically must
have the following permissions:
♦ Read and write permission for the Eclipse workspace location. By default, the location is
My 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 will
deploy Complex Data Exchange services. By default, the repository is <INSTALL_DIR>\
ServiceDB.
♦ Read and write permission for the log location. By default, the location is c:\Documents
and Settings\<USER>\Application Data\Informatica\ComplexDataExchange\
CMReports.
Engine Runtime Permissions

The user accounts under which applications run Complex Data Exchange Engine must have
the 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 Categories

For 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 in
the Windows Control Panel.
Administrators
Windows users who have administrative privileges can perform all Complex Data Exchange
operations.
Security 79
Limited Users
Typically, limited users do not have write permission for the Complex Data Exchange
program 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.
♦ 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 or
UNIX servers. The following discussion assumes that you use a load balancing module to
connect to multiple, identically configured servers.
Copying the Configuration File

Copy the configuration file, by default, <INSTALL_DIR>\CMConfig.xml, from one server to
other, identical servers. This ensures that all the servers have the same Complex Data
Exchange repository path, reports path, operation parameters, etc.
For more information, see “Copying the Configuration File” on page 59.
Deploying Services
The servers should share the same Complex Data Exchange services. There are two ways to
implement this:
♦ Shared file system. Store a single copy of the Complex Data Exchange repository on a
shared disk. Configure all the servers to access the shared repository.
♦ Replicated file system. Configure each server with its own Complex Data Exchange
repository. Use an automatic file deployment tool to mirror the Complex Data Exchange
repository from a source location to the individual servers.
If you use the second approach, you must replicate or touch the file update.txt, which exists
in the repository directory. The timestamp of this file notifies Complex Data Exchange
Engine when the last service update was performed. For more information, see “Deploying
Complex Data Exchange Services” on page 45.
Running on a Cluster Server

If you install Complex Data Exchange on a cluster server, you must either replicate the
Complex Data Exchange repository among the cluster nodes, or you must locate the
repository on a shared disk.
Installing on Microsoft Cluster Server

The following procedure illustrates how to install Complex Data Exchange on Microsoft
Cluster Server on Windows XP. For Windows 2000, the procedure is similar with minor
variations.
To install Complex Data Exchange on a cluster server:
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.
Multiple Servers 81
Be sure to assign an identical path to the installation folder and to the repository location
on both nodes.
4. On each node, open the Complex Data Exchange Configuration Editor and edit the
CMConfig/General/Reports Directory setting, which is the location where Complex
Data Exchange Engine stores log files. The settings on both nodes must point to the same
folder on the quorum disk.
5. If your Complex Data Exchange system requires a license file, install a copy of the file on
each 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 Environment
In a production environment where you run Complex Data Exchange Engine, back up the
following locations:
♦ 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 the
Complex Data Exchange Configuration Editor:
CM Configuration/Directory services/File system/Base Path
♦ The <INSTALL_DIR>\autoInclude\user directory, which stores custom global

components.
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 Environment
Back up the Complex Data Exchange Studio workspaces of the developers in your
organization. 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.
Backup Requirements 83
Failure Handling
If a Complex Data Exchange service fails to execute successfully, it returns a failure status to
the 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 more
information about viewing and interpreting the log, see “Event Logs” in the Complex Data
Exchange Engine Developer Guide and “Running and Testing Projects” in the Complex Data
Exchange Studio User Guide.

Index
A D
AIX database connectivity
IBM 8 ODBC 74
autoInclude default location
upgrading 66 repository 24
document
processors 4
B DSNs
defining 76
backup requirements
services and data 83
E
C Eclipse
installing 4
CLASSPATH
emulators
environment variable 32, 34
not supported 41
CMReports
Engine
setting log location 58
for running data transformations 4
COBOL
environment variables
system requirements 20
troubleshooting UNIX 38
Configuration Editor 56
UNIX 32
using 56
environment variables file
configuration file
loading on UNIX 31
backing up 56
using multiple 61
configuration files
event logs
multiple 60
remote support interface 39
core dump
setting location 58
preventing 40
85
Excel changing on Windows 58
system requirements 20 default 24
JVM
initialization parameters 39
F
failure handling
administrative approaches 84
L
filenames LD_LIBRARY_PATH
effect on upgrade 70 environment variable 32
fonts LDR_CNTRL
displaying Asian 42 AIX environment variable 14
LIBPATH
environment variable 32
H libraries
predefined data transformations 4
heap size
license file
Java 39
confirming validity 26
Hewlett-Packard
installing 26
HP-UX 8
limited users
HP-UX
restrictions 80
Hewlett-Packard 8
Linux
operating system 8
I load balancing
multiple servers 81
IBM log files
AIX 8 location of 38
IFConfigLocation4 log path
environment variable 32, 34 default 24
IFCONTENTMASTER_HOME setting location 58
environment variable 32, 34
install path
default 23 M
INSTALL_DIR
Microsoft Office
installation directory 23
Installation
instructions 22
invocation
in- or out-of-process 50
N
namespace
variables 70
J
Java
heap and stack size 39
O
JRE system requirement 9 ODBC
JVM initialization parameters 39 configuring 74
preventing core dump 40 installing driver 75
JRE installing manager on UNIX 75
JVM initialization parameters 39 using 76
JRE path operating systems
changing on UNIX 32 supported 8
86 Index
out-of-process sixty-four bit processes
invocation 50 activating 50
sizing guidelines
multiple servers 82
P Solaris
Sun 8
PATH
stack size
Java 39
Path
Sun
Solaris 8
PDF
syntax conversion tool
upgrading projects 66
permissions
system requirements
required for users 79
AIX 14
policies
HP-UX 18
administration 78
JRE 9
PowerPoint
Linux 17
Solaris 11
processors
Windows 10
document 4
project
definition 5
projects
T
upgrading 66 temp directory
upgrading from previous version 64 free space requirement 16
troubleshooting
installation 38
R UNIX environment variables 38
remote support interface
event logs 39
reports path
U
default 24 uninstalling
setting location 58 software 28
repository path unsupported features
default 24 on UNIX systems 8
setting location 58 upgrading
modified components 70
multiple computers 22
S projects 64
services and projects 66
schemas
users
upgrading 70
permissions 79
servers
Windows user types 79
multiple 81
services
deploying 45
upgrading 66
V
setup variables
wizard 23 namespace 70
SHLIB_PATH
Index 87
W
Word
88 Index

CDE 44 Administrator Guide

Cargado por

Información del documento

Descripción original:

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

CDE 44 Administrator Guide

Cargado por

Copyright:

Formatos disponibles

Complex Data Exchange

Informatica Complex Data Exchange™

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

Part Number: CDE-ADM-44000-0001

Chapter 2: System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 5: Testing and Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 6: Running Data Transformations . . . . . . . . . . . . . . . . . . . . . 43

Chapter 7: Running In-Process or Out-of-Process. . . . . . . . . . . . . . . 49

Chapter 9: Upgrading Complex Data Exchange Projects . . . . . . . . . . 63

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

Chapter 11: Administration and Deployment Policies . . . . . . . . . . . . 77

Table of Contents vii

If you see… It means…

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

boldfaced text Emphasized subjects.

Note: The following paragraph provides additional facts.

Tip: The following paragraph provides suggested uses.

monospaced text This is a code example.

Visiting Informatica Customer Portal

Visiting the Informatica Web Site

Visiting the Informatica Knowledge Base

Obtaining Customer Support

Informatica Corporation Informatica Software Ltd. Informatica Business Solutions

Toll Free Toll Free Toll Free

Standard Rate Standard Rate Standard Rate

This chapter includes the following topics:

Installing Complex Data Exchange on Windows

Installing Complex Data Exchange on UNIX

Testing the Complex Data Exchange Installation

Running Data Transformations

Configuring Complex Data Exchange

Upgrading Existing Data Transformations

Using ODBC Database Support Features

Deploying Complex Data Exchange in an Organization

Essential Administrative Tasks 3

Libraries Optional Libraries of predefined Complex Data Exchange data transformations,

This chapter includes the following topics:

8 Chapter 2: System Requirements

Java Runtime Environment

JRE for Use with Java API

10 Chapter 2: System Requirements

Package Minimum Version

Patch Minimum Version

Package Minimum Version

Solaris System Requirements 11

Package Minimum Version

Patch Minimum Version

12 Chapter 2: System Requirements

Confirming Packages and Patches

Solaris System Requirements 13

Package Version PTF

Package Version PTF

To configure the LDR_CNTRL variable:

Save the result, if it is not empty.

14 Chapter 2: System Requirements

To determine which maintenance level is installed:

X Run the following command:

To verify that a required package is installed:

The version number appears.

AIX System Requirements 15

16 Chapter 2: System Requirements

SUSE Linux 9 and Red Hat Linux EL3 on x86

Package Version Minimum Revision