Table of Contents

Search

  1. Preface
  2. Workflow Manager
  3. Workflows and Worklets
  4. Sessions
  5. Session Configuration Object
  6. Tasks
  7. Sources
  8. Targets
  9. Connection Objects
  10. Validation
  11. Scheduling and Running Workflows
  12. Sending Email
  13. Workflow Monitor
  14. Workflow Monitor Details
  15. Session and Workflow Logs
  16. Session Properties Reference
  17. Workflow Properties Reference

General Options Settings

General Options Settings

The following table describes the General Options settings on the Properties tab:
General Options Settings
Description
Write Backward Compatible Session Log File
Writes the session log to a file.
Session Log File Name
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.
Session Log File 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.
Parameter File Name
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.
Enable Test Load
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.
Number of Rows to Test
Enter the number of source rows you want the Integration Service to test load.
$Source Connection Value
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.
$Target Connection Value
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.
Treat Source Rows As
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.
Commit Type
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.
Commit Interval
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.
Commit On End of File
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.
Rollback Transactions on Errors
The Integration Service rolls back the transaction at the next commit point when it encounters a non-fatal writer error.
Recovery Strategy
Choose one of the following recovery strategies:
  • Resume from the last checkpoint. The Integration Service saves the session state of operation and maintains target recovery tables.
  • Restart. The Integration Service runs the session again when it recovers the workflow.
  • Fail session and continue the workflow. The Integration Service cannot recover the session, but it continues the workflow. This is the default session recovery strategy.
Java Classpath
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.