Session Properties Reference

By PenchalaRaju.Yanamala This appendix contains a listing of settings in the session properties. These settings are grouped by the following tabs: General Tab Properties Tab Mapping Tab (Transformations View) Mapping Tab (Partitions View) Components Tab Metadata Extensions Tab

Table A-1. General Tab General Tab Options Rename Description You can enter a new name for the session task with the Rename button. Description You can enter a description for the session task in the Description field. Mapping name Name of the mapping associated with the session task. Resources You can associate an object with an available resource. Fail Parent if This Task Fails* Fails the parent worklet or workflow if this task fails. Fail Parent if This Task Does Fails the parent worklet or workflow if this task does Not Run* not run. Disable This Task* Disables the task. Treat the Input Links as AND Runs the task when all or one of the input link

or OR* conditions evaluate to True. *Appears only in the Workflow Designer. Properties Tab On the Properties tab, you can configure the following settings: General Options. General Options settings allow you to configure session log file name, session log file directory, parameter file name and other general session settings. For more information, see General Options Settings. Performance. The Performance settings allow you to increase memory size, collect performance details, and set configuration parameters. For more information, see Performance Settings. General Options Settings You can configure General Options settings on the Properties tab. You can enter session log file name, session log file directory, and other general session settings.

Table A-2. Properties Tab - General Options Settings General Options Settings Write Backward Compatible Session Log File Session Log File Name Description Select to write session log to a file.

By default, the Integration Service uses the session name for the log file name: s_mapping name.log. For a debug session, it uses DebugSession_mapping name.log.

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. You can also use the $PMSessionLogFile session parameter to represent the name of the session log or the name and location of the session log. Session Log File Designates a location for the session log file. By default, the Directory 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 Designates the name and directory for the parameter file. Use Name 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 postsession functions, as if running the full session. The Integration Service writes data to relational targets, but rolls back the data when the session completes. For all other target types, such as flat file and SAP BW, the Integration Service does not write data to the targets. Enter the number of source rows you want to test in the Number of Rows to Test field. You cannot perform a test load on sessions that use XML sources. Note: You can perform a test load when you configure a session for normal mode. If you configure the session for bulk mode, the session fails. Number of Rows Enter the number of source rows you want the Integration to Test Service to test load. The Integration Service reads the number you configure for the test load. You cannot perform a test load when you run a session against a mapping that contains XML sources. $Source Enter the database connection you want the Integration Service Connection Value to use for the $Source connection variable. You can select a relational or application connection object, or you can use the $DBConnectionName or $AppConnectionName session parameter if you want to define the connection value in a parameter file. Use the $Source variable in Lookup and Stored Procedure transformations to specify the database location for the lookup table or stored procedure. If you use $Source in a Lookup or

Stored Procedure transformation, you can specify the database location in the $Source Connection Value field to ensure the Integration Service uses the correct database connection to run the session. If you use $Source in a mapping, but do not specify a database connection in one of these fields, the Integration Service determines which database connection to use when it runs the session. If it cannot determine the database connection, it fails the session. $Target Enter the database connection you want the Integration Service Connection Value to use for the $Target connection variable. You can select a relational or application connection object, or you can use the $DBConnectionName or $AppConnectionName session parameter if you want to define the connection value in a parameter file. Use the $Target variable in Lookup and Stored Procedure transformations to specify the database location for the lookup table or stored procedure. If you use $Target in a Lookup or Stored Procedure transformation, you can specify the database location in the $Target Connection Value field to ensure the Integration Service uses the correct database connection to run the session. If you use $Target in a mapping, but do not specify a database connection in one of these fields, the Integration Service determines which database connection to use when it runs the session. If it cannot determine the database connection, it fails the session. Treat Source Indicates how the Integration Service treats all source rows. If Rows As the mapping for the session contains an Update Strategy transformation or a Multigroup External Procedure 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 targetbased, 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 By default, this option is enabled and the Integration Service of File 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 The Integration Service rolls back the transaction at the next Transactions on commit point when it encounters a non-fatal writer error. Errors

Recovery Strategy

When a session is fails, the Integration Service suspends the workflow if the workflow is configured to suspend on task error. If the session recovery strategy is resume from the last checkpoint or restart, you can recover the workflow. The Integration Service recovers the session and continues the workflow if the session succeeds. If the session fails, the workflow becomes suspended again. You can also recover the session or recover the workflow from the session when you configure the session to resume from last checkpoint or restart. When you configure a Session task, you can 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. *Tip: When you bulk load to Microsoft SQL Server or Oracle targets, define a large commit interval. Microsoft SQL Server and Oracle start a new bulk load transaction after each commit. Increasing the commit interval reduces the number of bulk load transactions and increases performance. Performance Settings

Table A-3. Properties Tab - Performance Settings Performance Settings DTM Buffer Size Description

Amount of memory allocated to the session from the DTM process. By default, the Integration Service determines the DTM buffer size at run time. The Workflow Manager allocates a minimum of 12 MB for DTM buffer memory. You can specify auto or a numeric value. If you enter 2000, the Integration Service interprets the number as 2000 bytes. Append KB, MB, or GB to the value to specify other units. For example, you can specify 512MB. Increase the DTM buffer size in the following circumstances: A session contains large amounts of character data and you -configure it to run in Unicode mode. Increase the DTM buffer size to 24MB. -A session contains n partitions. Increase the DTM buffer size to at least n times the value for the session with one partition. A source contains a large binary object with a precision larger than -the allocated DTM buffer size. Increase the DTM buffer size so that the session does not fail. Collect Collects performance details when the session runs. Use the Performance Data Workflow Monitor to view performance details while the session runs. Write Writes performance details for the session to the PowerCenter Performance Data repository. Write performance details to the repository to view to Repository performance details for previous session runs. Use the Workflow Monitor to view performance details for previous session runs.

Incremental Aggregation Reinitialize Aggregate Cache

Select Incremental Aggregation option if you want the Integration Service to perform incremental aggregation. Select Reinitialize Aggregate Cache option if the session is an incremental aggregation session and you want to overwrite existing aggregate files. After a single session run, to return to a normal incremental aggregation session run, you must clear this option. Enable High When selected, the Integration Service processes the Decimal Precision datatype to a precision of 28. If a session does not use the Decimal datatype, leave this setting clear. Session Retry On Select this option if you want the Integration Service to retry Deadlock target writes on deadlock. You can only use Session Retry on Deadlock for sessions configured for normal load. This option is disabled for bulk mode. You can configure the Integration Service to set the number of deadlock retries and the deadlock sleep time period. Pushdown Use pushdown optimization to push transformation logic to the Optimization source or target database. The Integration Service analyzes the transformation logic, mapping, and session configuration to determine the transformation logic it can push to the database. At run time, the Integration Service executes any SQL statement generated against the source or target tables, and it processes any transformation logic that it cannot push to the database. Select one of the following values: -None. The Integration Service does not push any transformation logic to the database. -To Source. The Integration Service pushes as much transformation logic as possible to the source database. -To Target. The Integration Service pushes as much transformation logic as possible to the target database. Full. The Integration Service pushes as much transformation -logic as possible to both the source database and target database. $$PushdownConfig. The $$PushdownConfig mapping -parameter allows you to run the same session with different pushdown optimization configurations at different times. Default is None. Allow Temporary Select to allow the Integration Service to create temporary View for views in the database when it pushes the session to the Pushdown database. The Integration Service must create a view in the database if the session contains an SQL override, a filtered lookup, or an unconnected lookup. Allow Temporary Select to allow the Integration Service to create temporary Sequence for sequence objects in the database. The Integration Service Pushdown must create a sequence object in the database if the session contains a Sequence Generator transformation. Session Sort Specify a sort order for the session. The session properties Order display all sort orders associated with the Integration Service code page. When the Integration Service runs in Unicode mode, it sorts character data in the session using the selected sort order. When the Integration Service runs in ASCII mode, it

ignores this setting and uses a binary sort order to sort character data. Mapping Tab (Transformations View) In the Transformations view of the Mapping tab, you can configure settings for connections, sources, targets, and transformations. You can configure the following nodes: Connections Sources Targets Transformations Connections Node The Connections node displays the source, target, lookup, stored procedure, FTP, external loader, and queue connections. You can choose connection types and connection values. You can also edit connection object values. Figure A-4 shows the Connections settings on the Mapping tab:

Table A-4. Mapping Tab - Connections Settings Connections Node Settings Type Description Enter the connection type for relational and non-relational sources and targets based on the value you choose in the Type column. You can choose a connection object based on the

Partitions Value Sources Node

connection type: -Application -Queue -External Loader -FTP -None Displays the partitions if the session is partitioned. Enter a source and target connection based on the value you choose in the Type column.

The Sources node lists the sources used in the session and displays their settings. If you want to view and configure the settings of a specific source, select the source from the list. You can configure the following settings: Readers. The Readers settings displays the reader the Integration Service uses with each source instance. For more information, see Readers Settings. Connections. The Connections settings lets you configure connections for the sources. For more information, see Connections Settings. Properties. The Properties settings lets you configure the source properties. For more information, see Properties Settings. Readers Settings You can view the reader the Integration Service uses with each source instance. The Workflow Manager specifies the necessary reader for each source instance. For relations sources the reader is Relational Reader and for file sources it is File Reader.

Table A-6. Mapping Tab - Sources Node - Properties Settings (Relational Sources) Relational Description Source Options Owner Name Specifies the table owner name.

Source Table Specifies the source table name. Enter a table name, or enter a Name parameter or variable to define the source table name in a parameter file. You can use mapping parameters, mapping variables, session parameters, workflow variables, or worklet variables. If you override the source table name here, and you override the source table name using an SQL query, the Integration Service uses the source table name defined in the SQL query. User Defined Specifies the condition used to join data from multiple sources Join represented in the same Source Qualifier transformation. Tracing Level Specifies the amount of detail included in the session log when you run a session containing this transformation. You can view the value of this attribute when you click Show all properties. Select Distinct Selects unique rows. Pre SQL Pre-session SQL commands to run against the source database before the Integration Service reads the source. Post SQL Post-session SQL commands to run against the source database after the Integration Service writes to the target. Sql Query Defines a custom query that replaces the default query the Integration Service uses to read data from sources represented in this Source Qualifier. A custom query overrides entries for a custom join or a source filter. Source Filter Specifies the filter condition the Integration Service applies when querying records. Table A-7 describes the Properties settings on the Mapping tab for file sources: Table A-7. Mapping Tab - Sources Node - Properties Settings (File Sources) File Source Description Options Source File Enter the directory name in this field. By default, the Integration Directory Service looks in the service process variable directory, $PMSourceFileDir, for file sources. If you specify both the directory and file name in the Source Filename field, clear this field. The Integration Service concatenates this field with the Source Filename field when it runs the session. You can also use the $InputFileName session parameter to specify the file directory. Source Enter the file name, or file name and path. Optionally use the Filename $InputFileName session parameter for the file name. The Integration Service concatenates this field with the Source File Directory field when it runs the session. For example, if you have “C:\data\” in the Source File Directory field, then enter “filename.dat” in the Source Filename field. When the Integration Service begins the session, it looks for “C:\data\filename.dat”. By default, the Workflow Manager enters the file name configured in the source definition. Source You can configure multiple file sources using a file list. Filetype Indicates whether the source file contains the source data, or a list of files with the same file properties. Select Direct if the source file contains the source data. Select Indirect if the source file contains a

Set File Properties Datetime Displays the datetime format for datetime fields. Format* Thousand Displays the thousand separator for numeric fields. Separator* Decimal Displays the decimal separator for numeric fields. Separator* *You can view the value of this attribute when you click Show all properties. This attribute is read-only. For more information, see the PowerCenter Designer Guide. Setting File Properties for Sources Configure flat file properties by clicking the Set File Properties link in the Sources node. You can define properties for both fixed-width and delimited flat file sources. You can configure flat file properties for non-reusable sessions in the Workflow Designer and for reusable sessions in the Task Developer.

list of files. When you select Indirect, the Integration Service finds the file list then reads each listed file when it executes the session. You can configure the file properties.

Table A-8. Fixed-Width Properties for File Sources Fixed-Width Properties Options Null Character: Description

Indicates the character representing a null value in the file. This

Text/Binary Repeat Null Character

Code Page Number of Initial Rows to Skip

Number of Bytes to Skip Between Records

Strip Trailing Blanks Line Sequential File Format

can be any valid character in the file code page, or any binary value from 0 to 255. If selected, the Integration Service reads repeat NULL characters in a single field as a single NULL value. If you do not select this option, the Integration Service reads a single null character at the beginning of a field as a null field. Important: For multibyte code pages, specify a single-byte null character if you use repeating non-binary null characters. This ensures that repeating null characters fit into the column. Select the code page of the fixed-width file. The default setting is the client code page. Integration Service skips the specified number of rows before reading the file. Use this to skip header rows. One row may contain multiple rows. If you select the Line Sequential File Format option, the Integration Service ignores this option. You can enter any integer from zero to 2147483647. Integration Service skips the specified number of bytes between records. For example, you have an ASCII file on Windows with one record on each line, and a carriage return and line feed appear at the end of each line. If you want the Integration Service to skip these two single-byte characters, enter 2. If you have an ASCII file on UNIX with one record for each line, ending in a carriage return, skip the single character by entering 1. If selected, the Integration Service strips trailing blank spaces from records before passing them to the Source Qualifier transformation. Select this option if the file uses a carriage return at the end of each record, shortening the final column.

Configuring Delimited File Properties for Sources To edit the delimited properties, select Delimited in the Flat Files dialog box and click the Advanced button. The Delimited File Properties dialog box appears.

Table A-9. Delimited Properties for File Sources Delimited File Properties Options Delimiters Description

Character used to separate columns of data in the source file. Delimiters can be either printable or single-byte unprintable characters, and must be different from the escape character and the quote character (if selected). To enter a single-byte unprintable character, click the Browse button to the right of this field. In the Delimiters dialog box, select an unprintable character from the Insert Delimiter list and click Add. You cannot select unprintable multibyte characters as delimiters. The delimiter must be in the same code page as the flat file code page. Optional Quotes Select None, Single, or Double. If you select a quote character, the Integration Service ignores delimiter characters within the quote characters. Therefore, the Integration Service uses quote characters to escape the delimiter. For example, a source file uses a comma as a delimiter and contains the following row: 342-3849, ‘Smith, Jenna’, ‘Rockville, MD’, 6. If you select the optional single quote character, the Integration Service ignores the commas within the quotes and reads the row as four fields. If you do not select the optional single quote, the Integration Service reads six separate fields. When the Integration Service reads two optional quote characters within a quoted string, it treats them as one quote character. For example, the Integration Service reads the following quoted string as I’m going tomorrow:

2353, ‘I’’m going tomorrow.’, MD Additionally, if you select an optional quote character, the Integration Service only reads a string as a quoted string if the quote character is the first character of the field. Note: You can improve session performance if the source file does not contain quotes or escape characters. Code Page Select the code page of the delimited file. The default setting is the client code page. Row Delimiter Specify a line break character. Select from the list or enter a character. Preface an octal code with a backslash (\). To use a single character, enter the character. The Integration Service uses only the first character when the entry is not preceded by a backslash. The character must be a single-byte character, and no other character in the code page can contain that byte. Default is line-feed, \012 LF (\n). Escape Character immediately preceding a delimiter character Character embedded in an unquoted string, or immediately preceding the quote character in a quoted string. When you specify an escape character, the Integration Service reads the delimiter character as a regular character (called escaping the delimiter or quote character). Note: You can improve session performance for mappings containing Sequence Generator transformations if the source file does not contain quotes or escape characters. Remove Escape This option is selected by default. Clear this option to include the Character From escape character in the output string. Data Treat By default, the Integration Service reads pairs of delimiters as a Consecutive null value. If selected, the Integration Service reads any number Delimiters as of consecutive delimiter characters as one. One For example, a source file uses a comma as the delimiter character and contains the following record: 56, , , Jane Doe. By default, the Integration Service reads that record as four columns separated by three delimiters: 56, NULL, NULL, Jane Doe. If you select this option, the Integration Service reads the record as two columns separated by one delimiter: 56, Jane Doe. Number of Initial Integration Service skips the specified number of rows before Rows to Skip reading the file. Use this to skip title or header rows in the file. Targets Node The Targets node lists the used in the session and displays their settings. If you want to view and configure the settings of a specific target, select the target from the list. You can configure the following settings: Writers. The Writers settings displays the writer the Integration Service uses with each target instance. For more information, see Writers Settings. Connections. The Connections settings lets you configure connections for the targets. For more information, see Connections Settings. Properties. The Properties settings lets you configure the target properties. For more information, see Properties Settings.

Writers Settings You can view and configure the writer the Integration Service uses with each target instance. The Workflow Manager specifies the necessary writer for each target instance. For relational targets the writer is Relational Writer and for file targets it is File Writer.

Table A-12. Mapping Tab - Targets Node - Properties Settings (Relational) Target Property Target Load Type Description You can choose Normal or Bulk. If you select Normal, the Integration Service loads targets normally. If you select Normal and the Microsoft SQL Server target

Insert

Update (as Update)

Update (as Insert)

Update (else Insert)

Delete Truncate Table Reject File Directory

Reject Filename

Rejected Truncated/Overflowed Rows* Update Override*

name includes spaces, configure the following connection environment SQL in the connection object: SET QUOTED_IDENTIFIER ON You can select Bulk when you load to IBM DB2, Sybase, Oracle, or Microsoft SQL Server. If you select Bulk for an IBM DB2, Sybase, Oracle, or Microsoft SQL Server target, the Integration Service invokes the bulk API with default settings, bypassing database logging. If you select 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. If selected, the Integration Service inserts all rows flagged for insert. By default, this option is selected. If selected, the Integration Service updates all rows flagged for update. By default, this option is selected. If selected, the Integration Service inserts all rows flagged for update. By default, this option is not selected. If selected, the Integration Service updates rows flagged for update if it they exist in the target, then inserts any remaining rows marked for insert. If selected, the Integration Service deletes all rows flagged for delete. If selected, the Integration Service truncates the target before loading. 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 $BadFileName session parameter to specify the file directory. 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 $BadFileName 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. Instructs the Integration Service to write the truncated and overflowed rows to the reject file. Override the default UPDATE statement.

Table Name Prefix Pre SQL

Specify the owner of the target tables. You can enter pre-session SQL commands for a target instance in a mapping to execute commands against the target database before the Integration Service reads the source. Post SQL Enter post-session SQL commands to execute commands against the target database after the Integration Service writes to the target. Target Table Name Specifies the target table name. Enter a table name, or enter a parameter or variable to define the target table name in a parameter file. You can use mapping parameters, mapping variables, session parameters, workflow variables, or worklet variables. *You can view the value of this attribute when you click Show all properties. This attribute is read-only. For more information, see the PowerCenter Designer Guide. Properties Settings for Flat File Targets

Table A-13. Mapping Tab - Targets Node - File Properties Settings Target Property Merge Partitioned Files Description 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. Enter the directory name in this field. By default, the Integration Service writes the merged file in the service process variable

Merge File Directory

Merge File Name Output File Directory

Output Filename

Reject File Directory

Reject Filename

Set File Properties Datetime Format* Thousand

directory, $PMTargetFileDir. If you enter a full directory and file name in the Merge File Name field, clear this field. Name of the merge file. Default is target_name.out. This property is required if you select Merge Partitioned Files. 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 $OutputFileName session parameter to specify the file directory. 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 $OutputFileName session parameter for the file name. The Integration Service concatenates this field with the Output File Directory field when it runs the session. Note: 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. 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 $BadFileName session parameter to specify the file directory. 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 $BadFileName 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. You can configure the file properties. Displays the datetime format selected for datetime fields. Displays the thousand separator for numeric fields.

Separator* Decimal Displays the decimal separator for numeric fields. Separator* *You can view the value of this attribute when you click Show all properties. This attribute is read-only. For more information, see the PowerCenter Designer Guide. Setting File Properties for Targets Click the Set File Properties button on the Mapping tab to configure flat file properties. You can define flat file properties for both fixed-width and delimited flat file targets. You can configure flat file properties for non-reusable sessions in the Workflow Designer and for reusable sessions in the Task Developer.

Table A-14. Fixed-Width Properties for File Targets Fixed-Width Properties Options Null Character Description

Repeat Null Character

Code Page

Enter the character you want the Integration Service to use to represent null values. You can enter any valid character in the file code page. Select this option to indicate a null value by repeating the null character to fill the field. If you do not select this option, the Integration Service enters a single null character at the beginning of the field to represent a null value. Select the code page of the fixed-width file. The default setting is the client code page.

Configuring Delimited Properties for Targets To edit the delimited properties, select Delimited in the Flat Files dialog box and click the Advanced button. The Delimited File Properties dialog box appears.

Mapping Tab (Partitions View)

In the Partitions view of the Mapping tab, you can configure partitions. You can configure partitions for non-reusable sessions in the Workflow Designer and for reusable sessions in the Task Developer. The following nodes are available in the Partitions view: Partition Properties. For more information, see Partition Properties Node. KeyRange. For more information, see KeyRange Node. HashKeys. For more information, see HashKeys Node. Partition Points. For more information, see Partition Points Node. Non-Partition Points. For more information, see Non-Partition Points Node. Partition Properties Node

Table A-18. Components Tab Components Tab Option Task Description Tasks you can perform in the Components tab. You can configure pre- or post-session shell commands, success or failure email messages, and variable assignments in the Components tab. Select None if you do not want to configure commands and emails in the Components tab. For pre- and post-session commands, select Reusable to call an existing reusable Command task as the pre- or post-session shell command. Select Non-Reusable to create pre- or postsession shell commands for this session task. For success or failure emails, select Reusable to call an existing Email task as the success or failure email. Select Non-Reusable to create email messages for this session task. Use to configure commands, emails, or variable assignments.

Type

Value

Table A-19 describes the tasks available in the Components tab: Table A-19. Components Tab Tasks Components Tab Description Tasks Pre-Session Command Shell commands that the Integration Service performs at the beginning of a session. Post-Session Success Shell commands that the Integration Service performs Command after the session completes successfully.

Post-Session Failure Command On Success Email

Shell commands that the Integration Service performs after the session if the session fails. Integration Service sends On Success email message if the session completes successfully. On Failure Email Integration Service sends On Failure email message if the session fails. Pre-session variable Assign values to mapping parameters, mapping assignment variables, and session parameters before a session runs. This field is editable for non-reusable sessions. Post-session on Assign values to parent workflow and worklet variables success variable after a session completes successfully. This field is assignment editable for non-reusable sessions. Post-session on failure Assign values to parent workflow and worklet variables variable assignment after a session fails. This field is editable for non-reusable sessions. Reusable Pre- or Post-Session Commands Select Reusable in the Type field if you want to select an existing Command task as the pre- or post-session shell command. The Command Object Browser appears when you click the Open button in the Value field.

Table A-25 describes the configuration options for the Metadata Extensions tab: Table A-25. Metadata Extensions Tab Metadata Extensions Tab Description

Options Extension Name Datatype Value

Precision Reusable

Description

Name of the metadata extension. Metadata extension names must be unique in a domain. Datatype: numeric (integer), string, boolean, or XML. Value of the metadata extension. For a numeric metadata extension, the value must be an integer. For a boolean metadata extension, choose true or false. For a string or XML metadata extension, click the button in the Value field to enter a value of more than one line. The Workflow Manager does not validate XML syntax. Maximum length for string or XML metadata extensions. Select to make the metadata extension apply to all objects of this type (reusable). Clear to make the metadata extension apply to this object only (non-reusable). Description of the metadata extension.

Sign up to vote on this title
UsefulNot useful