Writes the session log to a file.

Enter a file name, a file name and directory, or use the $PMSessionLogFile session parameter. The Integration Service appends information in this field to that entered in the Session Log File Directory field. For example, if you have “C:\session_logs\” in the Session Log File Directory File field and then enter “logname.txt” in the Session Log File field, the Integration Service writes the logname.txt to the C:\session_logs\ directory.

Location for the session log file. By default, the Integration Service writes the log file in the service process variable directory, $PMSessionLogDir.

If you enter a full directory and file name in the Session Log File Name field, clear this field.

The name and directory for the parameter file. Use the parameter file to define session parameters and override values of mapping parameters and variables.

You can enter a workflow or worklet variable as the session parameter file name if you configure a workflow to run concurrently, and you want to use different parameter files for the sessions in each workflow run instance.

You can configure the Integration Service to perform a test load.

With a test load, the Integration Service reads and transforms data without writing to targets. The Integration Service generates all session files and performs all pre- and post-session functions, as if running the full session.

Enter the number of source rows you want to test in the Number of Rows to Test field.

Enter the number of source rows you want the Integration Service to test load.

The database connection you want the Integration Service to use for the $Source connection variable. You can select a relational or application connection object, or you can use the $DBConnection

Name

or $AppConnection

Name

session parameter if you want to define the connection value in a parameter file.

The database connection you want the Integration Service to use for the $Target connection variable. You can select a relational or application connection object, or you can use the $DBConnection

Name

or $AppConnection

Name

session parameter if you want to define the connection value in a parameter file.

Indicates how the Integration Service treats all source rows. If the mapping for the session contains an Update Strategy transformation or a Custom transformation configured to set the update strategy, the default option is Data Driven.

When you select Data Driven and you load to either a Microsoft SQL Server or Oracle database, you must use a normal load. If you bulk load, the Integration Service fails the session.

Determines if the Integration Service uses a source- or target-based, or user-defined commit. You can choose source- or target-based commit if the mapping has no Transaction Control transformation or only ineffective Transaction Control transformations. By default, the Integration Service performs a target-based commit.

A user-defined commit is enabled by default if the mapping has effective Transaction Control transformations.

In conjunction with the selected commit interval type, indicates the number of rows. By default, the Integration Service uses a commit interval of 10,000 rows.

This option is not available for user-defined commit.

By default, this option is enabled and the Integration Service performs a commit at the end of the file. Clear this option if you want to roll back open transactions.

This option is enabled by default for a target-based commit. You cannot disable it.

The Integration Service rolls back the transaction at the next commit point when it encounters a non-fatal writer error.

Choose one of the following recovery strategies:

If you enter a Java Classpath in this field, the Java Classpath is added to the beginning of the system classpath when the Integration Service runs the session. Use this option if you use third-party Java packages, built-in Java packages, or custom Java packages in a Java transformation.

You can use service process variables to define the classpath. For example, you can use $PMRootDir to define a classpath within the $PMRootDir folder.