Release Guide

Back Next

Mapping Tasks

Effective in version 10.0, Informatica has the following new features for Mapping tasks:

Mapping task log file directory: You can configure the directory where the Data Integration Service writes the Mapping task log. By default, the Data Integration Service writes the Mapping task log file in the directory defined by the system parameter, LogDir. The default location is disLogs/mappingtask. You can configure a different directory for the Mapping task log file in the Mapping task
Advanced
properties. You can parameterize the log file directory.

Mapping task log file name: You can configure a file name for the Mapping task log file. The Data Integration Service appends the file name to the information in the Masking Task Log File Directory field. It appends the log file name to a UID and time stamp or to a mapping run number, based on how you choose to save the log file. You can parameterize the log file name. Configure the log file name in the Mapping task
Advanced
properties.

Mapping task log save type: You can save the Mapping task log file by timestamp or by the number of mapping task runs. The suffix of the mapping task log file name reflects the option you select. You can configure how many log files to save.

Java classpath: You can enter the classpath to add to the beginning of the system classpath when the Data Integration Service runs the mapping task. Enter a Java classpath in the
Advanced
properties if you use third-party Java packages, built-in Java packages, or custom Java packages in a Java transformation.

Mapping task parameter usage: Effective in version 10.0, you can view which objects in a mapping use a specific parameter. Select a parameter on the Mapping task
Input
tab, and click
Parameter Usage
.

Custom properties: You can define custom properties for a Mapping task and configure the property values. You can also parameterize a custom property.

For more information, see the

Informatica 10.0 Developer Workflow Guide