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. POWERCENTERHELP
  17. Session Properties Reference
  18. Workflow Properties Reference

Targets Node

Targets Node

The Targets node lists the mapping targets and displays the settings. To view and configure the settings of a specific target, select the target from the list. You can configure the following settings:
  • Writers.
    Displays the writer that the Integration Service uses with each target instance. For relational targets, you can choose a relational writer or a file writer. Choose a file writer to use an external loader. After you override a relational target to use a file writer, define the file properties for the target. Click Set File Properties and choose the target to define.
  • Connections.
    Displays the target connections. You can choose connection types and connection values. You can also edit connection object values.
  • Properties.
    Displays different properties for different target types. For relational targets, you can override properties that you configured in the Mapping Designer. You can also configure the following session properties for relational targets:
    Relational Target Property
    Description
    Target Load Type
    You can choose Normal or Bulk.
    If you select Normal, the Integration Service loads targets normally.
    You can choose Bulk when you load to DB2, Sybase, Oracle, or Microsoft SQL Server. If you specify Bulk for other database types, the Integration Service reverts to a normal load. Loading in bulk mode can improve session performance, but limits the ability to recover because no database logging occurs.
    Choose Normal mode if the mapping contains an Update Strategy transformation.
    If you choose Normal and the Microsoft SQL Server target name includes spaces, configure the following connection environment SQL in the connection object:
    SET QUOTED_IDENTIFIER ON
    Insert
    The Integration Service inserts all rows flagged for insert.
    Update (as Update)
    The Integration Service updates all rows flagged for update.
    Update (as Insert)
    The Integration Service inserts all rows flagged for update.
    Update (else Insert)
    The Integration Service updates rows flagged for update if they exist in the target, and inserts remaining rows marked for insert.
    Delete
    The Integration Service deletes all rows flagged for delete.
    Truncate Table
    The Integration Service truncates the target before loading.
    Reject File Directory
    Reject-file directory name. By default, the Integration Service writes all reject files to the service process variable directory, $PMBadFileDir.
    If you specify both the directory and file name in the Reject Filename field, clear this field. The Integration Service concatenates this field with the Reject Filename field when it runs the session.
    You can also use the $BadFile
    Name
    session parameter to specify the file directory.
    Reject Filename
    File name or file name and path for the reject file. By default, the Integration Service names the reject file after the target instance name:
    target_name
    .bad. Optionally, use the $BadFile
    Name
    session parameter for the file name.
    The Integration Service concatenates this field with the Reject File Directory field when it runs the session. For example, if you have “C:\reject_file\” in the Reject File Directory field, and enter “filename.bad” in the Reject Filename field, the Integration Service writes rejected rows to C:\reject_file\filename.bad.
    For file targets, you can override properties that you configured in the Target Designer. You can also configure the following session properties for file targets:
    File Target Property
    Description
    Merge Partitioned Files
    When selected, the Integration Service merges the partitioned target files into one file when the session completes, and then deletes the individual output files. If the Integration Service fails to create the merged file, it does not delete the individual output files.
    You cannot merge files if the session uses FTP, an external loader, or a message queue.
    Merge File Directory
    Enter the directory name in this field. By default, the Integration Service writes the merged file in the service process variable directory, $PMTargetFileDir.
    If you enter a full directory and file name in the Merge File Name field, clear this field.
    Merge File Name
    Name of the merge file. Default is
    target_name
    .out. This property is required if you select Merge Partitioned Files.
    Create Directory if Not Exists
    Creates the target directory if it does not exist.
    Output File Directory
    Enter the directory name in this field. By default, the Integration Service writes output files in the service process variable directory, $PMTargetFileDir.
    If you specify both the directory and file name in the Output Filename field, clear this field. The Integration Service concatenates this field with the Output Filename field when it runs the session.
    You can also use the $OutputFile
    Name
    session parameter to specify the file directory.
    Output Filename
    Enter the file name, or file name and path. By default, the Workflow Manager names the target file based on the target definition used in the mapping:
    target_name
    .out.
    If the target definition contains a slash character, the Workflow Manager replaces the slash character with an underscore.
    When you use an external loader to load to an Oracle database, you must specify a file extension. If you do not specify a file extension, the Oracle loader cannot find the flat file and the Integration Service fails the session.
    Enter the file name, or file name and path. Optionally use the $OutputFile
    Name
    session parameter for the file name.
    The Integration Service concatenates this field with the Output File Directory field when it runs the session.
    If you specify an absolute path file name when using FTP, the Integration Service ignores the Default Remote Directory specified in the FTP connection. When you specify an absolute path file name, do not use single or double quotes.
    Reject File Directory
    Enter the directory name in this field. By default, the Integration Service writes all reject files to the service process variable directory, $PMBadFileDir.
    If you specify both the directory and file name in the Reject Filename field, clear this field. The Integration Service concatenates this field with the Reject Filename field when it runs the session.
    You can also use the $BadFile
    Name
    session parameter to specify the file directory.
    Reject Filename
    Enter the file name, or file name and path. By default, the Integration Service names the reject file after the target instance name:
    target_name
    .bad. Optionally use the $BadFile
    Name
    session parameter for the file name.
    The Integration Service concatenates this field with the Reject File Directory field when it runs the session. For example, if you have “C:\reject_file\” in the Reject File Directory field, and enter “filename.bad” in the Reject Filename field, the Integration Service writes rejected rows to C:\reject_file\filename.bad.