Informatica B2B Data Transformation (Version 9.5.1) Administrator Guide

Transcription

1 Informatica B2B Data Transformation (Version 9.5.1) Administrator Guide

2 Informatica B2B Data Transformation Administrator Guide Version June 2012 Copyright (c) Informatica. 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 may be protected by U.S. and/or international Patents 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 (a) and (a) (1995), DFARS (1)(ii) (OCT 1988), FAR (a) (1995), FAR , or FAR (ALT III), as applicable. The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing. Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica On Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and Informatica Master Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners. Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights reserved. Copyright Sun Microsystems. All rights reserved. Copyright RSA Security Inc. All Rights Reserved. Copyright Ordinal Technology Corp. All rights reserved.copyright Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright Meta Integration Technology, Inc. All rights reserved. Copyright Intalio. All rights reserved. Copyright Oracle. All rights reserved. Copyright Adobe Systems Incorporated. All rights reserved. Copyright DataArt, Inc. All rights reserved. Copyright ComponentSource. All rights reserved. Copyright Microsoft Corporation. All rights reserved. Copyright Rogue Wave Software, Inc. All rights reserved. Copyright Teradata Corporation. All rights reserved. Copyright Yahoo! Inc. All rights reserved. Copyright Glyph & Cog, LLC. All rights reserved. Copyright Thinkmap, Inc. All rights reserved. Copyright Clearpace Software Limited. All rights reserved. Copyright Information Builders, Inc. All rights reserved. Copyright OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. Copyright Cleo Communications, Inc. All rights reserved. Copyright International Organization for Standardization All rights reserved. Copyright ej-technologies GmbH. All rights reserved. Copyright Jaspersoft Corporation. All rights reserved. Copyright is International Business Machines Corporation. All rights reserved. Copyright yworks GmbH. All rights reserved. Copyright Daniel Veillard. All rights reserved. Copyright Unicode, Inc. This product includes software developed by the Apache Software Foundation ( and other software which is licensed under the Apache License, Version 2.0 (the "License"). You may obtain a copy of the License at 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 which was developed by Mozilla ( software copyright The JBoss Group, LLC, all rights reserved; software copyright by Bruno Lowagie and Paulo Soares and other software which is licensed under the GNU Lesser General Public License Agreement, which may be found at The 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. The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine, and Vanderbilt University, Copyright ( ) , all rights reserved. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and redistribution of this software is subject to terms available at and This product includes Curl software which is Copyright , Daniel Stenberg, <daniel@haxx.se>. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at 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. The product includes software copyright ( ) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at The product includes software copyright , The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this software are subject to terms available at This product includes software copyright Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at This product includes OSSP UUID software which is Copyright 2002 Ralf S. Engelschall, Copyright 2002 The OSSP Project Copyright 2002 Cable & Wireless Deutschland. Permissions and limitations regarding this software are subject to terms available at This product includes software developed by Boost ( or under the Boost software license. Permissions and limitations regarding this software are subject to terms available at This product includes software copyright University of Cambridge. Permissions and limitations regarding this software are subject to terms available at This product includes software copyright 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at This product includes software licensed under the terms at license.html, license.html, licenseagreement; license.html; nanoxml.sourceforge.net/orig/copyright.html; and

3 This product includes software licensed under the Academic Free License ( the Common Development and Distribution License ( the Common Public License ( the Sun Binary Code License Agreement Supplemental License Terms, the BSD License ( the MIT License ( and the Artistic License ( This product includes software copyright Joe WaInes, XStream Committers. All rights reserved. Permissions and limitations regarding this software are subject to terms available at This product includes software developed by the Indiana University Extreme! Lab. For further information please visit This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775; 6,640,226; 6,789,096; 6,820,077; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,243,110, 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422, 7,720,842; 7,721,270; and 7,774,791, international Patents and other Patents Pending. DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of noninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice. NOTICES This Informatica product (the Software ) includes certain drivers (the DataDirect Drivers ) from DataDirect Technologies, an operating company of Progress Software Corporation ( DataDirect ) which are subject to the following terms and conditions: 1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. 2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS. Part Number: DT-ADM

4 Table of Contents Preface.... ii Informatica Resources.... ii Informatica Customer Portal.... ii Informatica Documentation.... ii Informatica Web Site.... ii Informatica How-To Library.... ii Informatica Knowledge Base.... iii Informatica Multimedia Knowledge Base.... iii Informatica Global Customer Support.... iii Chapter 1: System Administration System Administration Overview Data Transformation System Architecture Backup Policies Design Environment Backup Policies Production Environment Backup Policies Data Transformation Directory Locations User Permissions for Data Transformation Production Environment User Permissions for Data Transformation Design Environment Administrator Task List Chapter 2: Data Transformation Project Upgrading Data Transformation Project Upgrading Overview When to Upgrade Projects Upgrade Terminology Upgrading a Project Upgrading a Service Syntax Conversion Tool Pre-Upgrade Tasks Running the Syntax Conversion Tool Running the Syntax Conversion Tool from the Command Line Project Upgrade Troubleshooting New and Modified Components Modified Namespace for Variables XML Schemas Index Table of Contents i

5 Preface The Data Transformation Administrator Guide is written for system administrators and users who are responsible for installing the Data Transformation software and maintaining or configuring its operation. It contains instructions and information for Linux, UNIX, and Windows platforms. Informatica Resources Informatica Customer Portal As an Informatica customer, you can access the Informatica Customer Portal site at The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica How-To Library, the Informatica Knowledge Base, the Informatica Multimedia Knowledge Base, Informatica Product Documentation, and access to the Informatica user community. Informatica Documentation The Informatica Documentation team takes every effort to create accurate, usable documentation. If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through at We will use your feedback to improve our documentation. Let us know if we can contact you regarding your comments. The Documentation team updates documentation as needed. To get the latest documentation for your product, navigate to Product Documentation from Informatica Web Site You can access the Informatica corporate web site at The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services. Informatica How-To Library As an Informatica customer, you can access the Informatica How-To Library at The How-To Library is a collection of resources to help you learn more about Informatica products and features. It includes articles and interactive demonstrations that provide solutions to common problems, compare features and behaviors, and guide you through performing specific real-world tasks. ii

6 Informatica Knowledge Base As an Informatica customer, you can access the Informatica Knowledge Base at Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips. If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team through at Informatica Multimedia Knowledge Base As an Informatica customer, you can access the Informatica Multimedia Knowledge Base at The Multimedia Knowledge Base is a collection of instructional multimedia files that help you learn about common concepts and guide you through performing specific tasks. If you have questions, comments, or ideas about the Multimedia Knowledge Base, contact the Informatica Knowledge Base team through at KB_Feedback@informatica.com. Informatica Global Customer Support You can contact a Customer Support Center by telephone or through the Online Support. Online Support requires a user name and password. You can request a user name and password at Use the following telephone numbers to contact Informatica Global Customer Support: North America / South America Europe / Middle East / Africa Asia / Australia Toll Free Brazil: Mexico: North America: Toll Free France: Germany: Italy: Netherlands: Portugal: Spain: Switzerland: United Kingdom: Toll Free Australia: New Zealand: Standard Rate India: Standard Rate Belgium: France: Germany: Netherlands: United Kingdom: Preface iii

7 iv

8 C H A P T E R 1 System Administration This chapter includes the following topics: System Administration Overview, 1 Backup Policies, 2 Data Transformation Directory Locations, 3 User Permissions for Data Transformation Production Environment, 4 User Permissions for Data Transformation Design Environment, 5 Administrator Task List, 5 System Administration Overview The Data Transformation system consists of a design environment for designers and a production environment where applications run transformation services. For more information, see Data Transformation System Architecture on page 1. The system administrator must regularly back up essential files for the operation of Data Transformation. For more information, see Backup Policies on page 2. The files required for designing and running transformation projects and services are located in certain directories, which are determined at the time of installation. For more information, see Data Transformation Directory Locations on page 3. Human users who use the Studio and application users that access services each must have the correct permissions. For more information, see User Permissions for Data Transformation Production Environment on page 4 and User Permissions for Data Transformation Design Environment on page 5. For more information about the responsibilities of the system administrator, see Administrator Task List on page 5. Data Transformation System Architecture The Data Transformation network contains the following units: Design environment. One or more Windows computers on which the Data Transformation Studio is installed for use by designers. The design environment includes the following additional components: - Data Transformation Engine. Tests transformation projects. - Document processors. Convert documents from binary formats to formats that the Data Transformation Engine can read. 1

9 - Online documentation. Data Transformation product documentation. On the design environment, you can install optional libraries of predefined transformations for use with industry messaging standards. For more information, see the Data Transformation Libraries Guide. Production environment. One or more Linux, UNIX, or Windows computers. Multiple production environments can be configured as a cluster if they are of the same type. The production environment contains the following components: - Data Transformation Engine. Runs transformation services for applications. - Document processors. Convert documents from binary formats to formats that the Data Transformation Engine can read. Backup Policies Make regular backups of Data Transformation directories and files on both the production environment and the design environment. Design Environment Backup Policies On the Data Transformation Studio computer (design environment) of each developer in your organization, back up the following items: The Eclipse workspace directory. The Data Transformation configuration file (CMConfig.xml). The Data Transformation license file (CDELicense.cfg). The repository directory. The two directories that hold custom global components. For more information about the locations of these items, see Data Transformation Directory Locations on page 3. Production Environment Backup Policies On the Data Transformation production environment computers in your organization, back up the following items: The Data Transformation configuration file (CMConfig.xml). The Data Transformation license file (CDELicense.cfg). The repository directory. The two directories that hold custom global components. For more information about the locations of these items, see Data Transformation Directory Locations on page 3. If you use identical configurations on multiple servers in a cluster, you need to back up only a single copy of these items. 2 Chapter 1: System Administration

10 Data Transformation Directory Locations The following table describes directories that are used by Data Transformation: Location <INSTALL_DIR> <INSTALL_DIR>/DataTransformation/ <INSTALL_DIR>/DataTransformation/bin/ <INSTALL_DIR>/DataTransformation/ServiceDB Description The directory where Data Transformation is installed. The user chooses this directory at the time of installation. The default is: - Windows. c:\informatica\ Linux and UNIX (root user). /root/informatica/ Linux and UNIX (other user). /home/<user_name>/ Informatica/9.5.0 The Data Transformation home directory, which contains the following files: - CMConfig.xml - CMConfig.xsd - CDELicense.cfg - setenv.sh (Linux and UNIX) - setenv.csh (Linux and UNIX) This value is stored in the IFCONTENTMASTER_HOME environment variable. Data Transformation executables. Repository where transformation services are stored. This value is stored in CMConfig.xml and can be changed using the configuration editor or a text editor. <INSTALL_DIR>/DataTransformation/CMReports <INSTALL_DIR>/DataTransformation/CMUserLogs <INSTALL_DIR>/DataTransformation/autoInclude/user <INSTALL_DIR>/DataTransformation/externLibs/user <INSTALL_DIR>\clients\java\bin <INSTALL_DIR>/java/bin <INSTALL_DIR>\clients\java\jre\bin\client <INSTALL_DIR>/java/jre/bin/client <INSTALL_DIR>/java/jre/lib/<processor> Engine and Studio logs. This value is stored in CMConfig.xml and can be changed using the configuration editor or a text editor. Application logs and user logs. This value is stored in CMConfig.xml and can be changed using the configuration editor or a text editor. The directory that holds custom global components (TGP files). The directory that holds custom global components (DLL and JAR files). Java home directory (design environment). Java home directory (production environment). JRE directory (design environment). JRE directory (production environment). JRE directories (Linux and UNIX only). These values are stored in environment variables. Data Transformation Directory Locations 3

11 Location Description <INSTALL_DIR>/java/jre/lib/<processor>/server C:\Users\<USER_NAME>\My Documents\Informatica \DataTransformation\950\workspace Eclipse workspace directory where projects are stored on the Studio computer. This location can be changed in the Studio using Eclipse commands. There is also an optional, user-defined directory for diagnostic logs for the Server component that calls the Engine out of process. This path is stored in CMConfig.xml and can be changed using the configuration editor or a text editor. Run the following command to determine the installation directory: CM_console -v The installation directory appears after Configuration file: and before /DataTransformation/. For more information about environment variables and the configuration editor, see the Data Transformation Installation and Configuration Guide. For more information about the Studio, see the Data Transformation Studio User Guide. User Permissions for Data Transformation Production Environment Windows administrator users have all permissions that are required for the Data Transformation production environment. The following table describes the permissions required for Linux and UNIX users and Windows limited users to run the Engine in the production environment: Directory Installation directory Installation directory Repository Engine and Studio logs Engine and Studio logs Application logs and user logs Application logs and user logs Permissions Read Execute Read Read Write Read Write For more information about the locations of these directories, see Data Transformation Directory Locations on page 3. 4 Chapter 1: System Administration

12 User Permissions for Data Transformation Design Environment Windows administrator users have all permissions that are required for the Data Transformation design environment. The following table describes the permissions that limited users require to design and test projects: Directory Installation directory Installation directory Repository Repository Eclipse location Eclipse location Engine and Studio logs Engine and Studio logs Permissions Read Execute Read Write Read Write Read Write To deploy projects to the repository on a remote computer, the limited user must have read and write permissions for the repository on that machine. The following tasks require administrator permissions: Installing and uninstalling Data Transformation Installing libraries Changing Data Transformation configuration settings For more information about the locations of these directories, see Data Transformation Directory Locations on page 3. Administrator Task List The Data Transformation system administrator is responsible for the following tasks: Manage user permissions. For more information, see User Permissions for Data Transformation Design Environment on page 5 and User Permissions for Data Transformation Production Environment on page 4. Define a backup policy. For more information, see Backup Policies on page 2. Upgrade projects. For more information, see Data Transformation Project Upgrading Overview on page 6. Install, upgrade, configure, and uninstall Data Transformation. For more information, see the Data Transformation Installation and Configuration Guide. Install libraries. For more information, see the Data Transformation Libraries Guide. Deploy projects. For more information, see the Data Transformation Studio User Guide. User Permissions for Data Transformation Design Environment 5

13 C H A P T E R 2 Data Transformation Project Upgrading This chapter includes the following topics: Data Transformation Project Upgrading Overview, 6 Syntax Conversion Tool, 8 Project Upgrade Troubleshooting, 11 Data Transformation Project Upgrading Overview If you are upgrading from a previous Data Transformation release, you can upgrade your existing Studio projects and your deployed Data Transformation services to the current release. The upgrade from Data Transformation version 3.2 or higher is automated. Individual project. Import it into Data Transformation Studio or open it. Multiple projects. Use the syntax conversion tool. When to Upgrade Projects You must upgrade projects when the syntax version changes for the Data Transformation Engine. The current version is To determine the syntax version, open a command prompt and run the following command: CM_console -v The syntax version appears. Upgrade Terminology Data Transformation version 3.x used certain terms that have been superseded. 6

14 The following table describes the corresponding terms. Current term Term Used in Data Transformation 3.x Description Project Workspace A directory on the Studio computer containing a transformation configuration: a CMW file, one or more TGP script files, and other related files. Workspace No corresponding term The parent directory on the Studio computer where Data Transformation Studio stores projects. Deploy Publish Make a project available as a service. Repository Services database location The parent directory on the Studio computer and in the production environment where Data Transformation services are stored. Note: This information is relevant for upgrading projects from Data Transformation 3.x to the current version. Upgrading a Project On a Windows computer where the design environment is installed, you can upgrade an individual project by importing it into Data Transformation Studio. 1. Click File > Import. The Import dialog box appears. 2. Under the Data Transformation folder, select Import Data Transformation Project into Workspace, and then click Next. The Import Data Transformation Project dialog box appears. 3. Click Browse to select the directory that contains the project you want to upgrade, and then click Next. The Enter Project Name page appears. 4. Enter the name of the project as it will be displayed in the Data Transformation Explorer view, and then click Next. The Import Files page appears. 5. Click Finish. The project is imported and upgraded. 6. Test the project. Upgrading a Service You can upgrade the development copy of a project and re-deploy it as a Data Transformation service. 1. Open or import the project in Data Transformation Studio. For more information, see Upgrading a Project on page Test the project. 3. Re-deploy the project. For more information, see the Data Transformation Studio User Guide. Data Transformation Project Upgrading Overview 7

15 Syntax Conversion Tool The Data Transformation syntax conversion tool upgrades multiple projects and services simultaneously in one operation. It also upgrades global TGP script files, which are stored in the autoinclude/user directory. Before the upgrade, the syntax conversion tool backs up existing projects and files. During the upgrade operation, it creates a log file that includes all errors detected. In case of an error, restore the backup, correct the problem, and run the tool again. Pre-Upgrade Tasks Before you run the syntax conversion tool to upgrade your projects and services, perform the following tasks: 1. Organize the projects and services correctly. For more information, see Organize Projects and Services on page Review and correct file names and directory names. For more information, see File and Directory Names from Data Transformation 3.x on page Copy Data Transformation 3.x services on Linux and UNIX computers to a Windows computer. For more information, see Syntax Conversion for Data Transformation 3.x on Linux or UNIX on page 9. Organize Projects and Services The syntax conversion tool operates on a single parent directory that contains projects or services. It can operate on the following directories: A Data Transformation Studio workspace on the design environment computer. A Data Transformation repository on the production environment computer or the design environment computer. Any other directory that contains Data Transformation Studio projects or services. The Data Transformation autoinclude/user directory, which contains global TGP script files. The project and service subdirectories must be at the top level of nesting under the parent directory, for example: or: Workspace_Parent_Directory Project1 Project2 Project3... Repository_Parent_Directory Service1 Service2 Service3... Tip: Move the files to a temporary directory before running the syntax conversion tool. File and Directory Names from Data Transformation 3.x In the current Data Transformation version, the names of project files and directories can contain only 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 you have projects from Data Transformation 3.x, change the file names and directory names to conform with the current naming convention. 8 Chapter 2: Data Transformation Project Upgrading

16 Syntax Conversion for Data Transformation 3.x on Linux or UNIX The syntax conversion tool only runs on Windows platforms. 1. Copy the service directories to a Windows computer. 2. Run the syntax conversion tool on the Windows copy of the service directories. 3. Re-deploy the services to the Linux or UNIX computer. For more information, see the Data Transformation Studio User Guide. Running the Syntax Conversion Tool Run the syntax conversion tool on either of the following workspace and repository directories: The single parent directory that contains all projects or services. Individual parent directories, each containing a logical group of projects or services. 1. Open the syntax conversion tool by performing one of the following actions: System Windows Linux UNIX Action Click Start > All Programs > Informatica > Data Transformation > Syntax Conversion Tool Run the following command: <INSTALL_DIR>/DataTransformation/bin/CM_DBConverter.sh The Syntax Conversion Tool window appears. 2. At the bottom of the window, select the version from which you are upgrading, such as 4.x. On Linux or UNIX: The syntax conversion tool operates on Data Transformation version 4.x or later. For more information about upgrading from version 3.x, see Syntax Conversion for Data Transformation 3.x on Linux or UNIX on page On the Services tab, set the following options: Option Source Location Target Location Description The workspace containing the old projects or the repository containing the old services. The workspace for 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 Source Location Target Location Description The old autoinclude/user directory. The new autoinclude/user directory. 5. On the Result Files tab, set the following options: Option Backup Location Description The location where the tool backs up your existing projects prior to upgrade. Syntax Conversion Tool 9

17 Option Error Location Log Location Description The location where the tool should store any projects that it cannot upgrade due to an error. The location for the upgrade log. 6. Click Start. The tool converts the projects and reports its progress and results. 7. Repeat steps 3, 5, and 6 on all Data Transformation Studio workspace parent directories that contain projects and repository parent directories that contain services. The AutoInclude options should be blank on the repeat runs. The AutoInclude files are 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. Test the projects and services to confirm that they work correctly. For more information about issues that might arise, see Project Upgrade Troubleshooting on page 11. Running the Syntax Conversion Tool from the Command Line To run the syntax conversion tool from the command line: 1. Open a command prompt, and then change to the <INSTALL_DIR>/DataTransformation/bin/ directory. 2. Run the following command: Option Description Windows CM_DBConverter.bat <switches> Linux UNIX./CM_DBConverter.sh console <switches> where the <switches> are as described in the following table. Switch Required/ Optional Description -v Required Major version from which you are upgrading, such as 4. On Linux and UNIX, upgrading is supported only from version 4 or later. -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. 10 Chapter 2: Data Transformation Project Upgrading

18 Switch Required/ Optional Description -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. After each switch, leave a space and type the value. If a path contains spaces, you must enclose it in quotation marks. For example, the following Windows command upgrades version 4 services in the default repository location: CM_DBConverter.bat -v 4 -s "c:\informatica\9.5.1\datatransformation\servicedb" 3. The tool notifies you when the upgrade is complete. If there are 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. For more information, see the Data Transformation Studio User Guide. Project Upgrade Troubleshooting Important: You must test the transformation following the upgrade to ensure that it performs according to its design. If an upgraded project does not operate correctly, you can edit its configuration in Data Transformation Studio. New and Modified Components If a Data Transformation component has been revised, renamed, or replaced by a new component, the upgrade installs the new component. For more information about components that have been modified, see the Data Transformation Release Guide. In most cases, the modifications do not change the behavior of upgraded projects. An upgraded project containing the Locator component might behave slightly differently from an 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 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 about the JavaScript support in these actions, see the Data Transformation Studio User Guide. For more information about behavior changes, see the Release Notes supplied with the new Data Transformation version. Modified Namespace for Variables Starting in version 4.0.6, the namespace for variables was changed to If you upgrade a project from version or earlier, the Schema view and the project properties display both the old empty namespace and the new namespace that contains your variables. This does not affect the operation of your project. Project Upgrade Troubleshooting 11

19 XML Schemas In Data Transformation 3.1, the XML schema was defined in the TGP files of the project. In Data Transformation 3.2 and later, the XML schema is an XSD file. When you upgrade a version 3.1 project, Data Transformation Studio creates an XSD schema file. Review the schema and confirm that it meets your needs. You can edit the schema or create your own schema. For more information about schemas, see the Data Transformation Studio User Guide. 12 Chapter 2: Data Transformation Project Upgrading

20 I N D E X A administration overview 1 task list 5 architecture system 1 B backup policies design environment 2 production environment 2 C CalculateValue action troubleshooting 11 configuration file location 3 custom global components location of directories 3 upgrading with syntax conversion tool 8 D Data Transformation 3.1 on Linux or UNIX syntax conversion patch 9 deploy defined 6 design environment defined 1 permissions 5 directory locations 3 troubleshooting names 8 E Eclipse workspace directory location 3 EnsureCondition action troubleshooting 11 environment, design defined 1 environment, production defined 1 F file and directory names troubleshooting 8 folder locations 3 G global components, custom location of directories 3 upgrading with syntax conversion tool 8 global TGP script files upgrading with syntax conversion tool 8 H home directory location 3 I installation directory location 3 J Java home directory location 3 JRE directory location 3 L license file location 3 Locator component troubleshooting 11 log directory location 3 P permissions design environment 5 production environment 4 Windows users 5 13

21 production environment defined 1 permissions 4 project defined 6 upgrade procedure 7 upgrade task list 8 upgrade troubleshooting 11 upgrade, running the syntax conversion tool 9 upgrade, running the syntax conversion tool from the command line 10 upgrading from previous version 6 upgrading with syntax conversion tool 8 projects directory location 3 when to upgrade 6 publish defined 6 R repository defined 6 directory location 3 S script files, global TGP upgrading with syntax conversion tool 8 service upgrade procedure 7 upgrading with syntax conversion tool 8 services database defined 6 studio permissions 5 syntax conversion tool running 9 running from the command line 10 upgrading projects and services 8 system architecture 1 TGP script files, global upgrading with syntax conversion tool 8 troubleshooting CalculateValue action 11 EnsureCondition action 11 file and directory names 8 Locator component 11 new and modified Data Transformation components 11 project upgrading 11 variable namespace 11 U upgrade terminology 6 upgrading overview, projects 6 procedure 7 running the syntax conversion tool 9 running the syntax conversion tool from the command line 10 schemas 12 services and projects with syntax conversion tool 8 task list 8 troubleshooting 11 when 6 user permissions 5 V variable namespace troubleshooting 11 W workspace defined 6 directory location 3 T task list administration 5 14 Index