Informatica Admin

Data Transformation Project Upgrading

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

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.

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.
2.
Test the project.
3.
Re-deploy the project.For more information, see the Data Transformation Studio

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 Before Running the Tool Organize Your Projects.  2. Review and correct file names and directory names. For more information, see Unsupported File and Directory Names.  3. Copy Data Transformation 3.x services on Linux and UNIX computers to a Windows computer. For more information, see Version Support on UNIX.

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:

Workspace_Parent_Directory Project1 Project2 Project3 … or:

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.

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.

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 Action
Windows Click Start > All Programs > Informatica > Data Transformation > Syntax Conversion Tool
LinuxUNIX 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

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

Option Description
Source Location The workspace containing the old projects or the repository containing the old services.
Target Location 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 Description
Source Location The old autoInclude/user directory.
Target Location The new autoInclude/user directory.
5.
On the Result Files tab, set the following options:

Option Description
Backup Location The location where the tool backs up your existing projects prior to upgrade.
Error Location The location where the tool should store any projects that it cannot upgrade due to an error.
Log Location 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,

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>
LinuxUNIX ./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.
-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-sswitch 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-sswitch 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.1.0\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.
Advertisements

Tagged: , , , , ,

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: