Name and path of the output file directory. Enter the directory name in this field. By default, the Integration Service writes output files to the directory $PMTargetFileDir.

If you enter a full directory and file name in the Output Filename field, clear this field. External loader sessions may fail if you use double spaces in the path for the output file.

Name of the output file. 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. External loader sessions may fail if you use double spaces in the path for the output file.

Name and path of the reject file directory. By default, the Integration Service writes all reject files to the directory $PMBadFileDir.

If you enter a full directory and file name in the Reject Filename field, clear this field.

Name of the reject file. Enter the file name, or file name and directory. The Integration Service appends information in this field to that entered in the Reject File Directory field. 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.

By default, the Integration Service names the reject file after the target instance name:

target_name

.bad.

You can also enter a reject file session parameter to represent the reject file or the reject file and directory. Name all reject file parameters $BadFile

Name

.

Definition of flat file properties. When you use an external loader, you must define the flat file properties by clicking the Set File Properties link.

For Oracle external loaders, the target flat file can be fixed-width or delimited.

For Sybase IQ external loaders, the target flat file can be fixed-width or delimited.

For Teradata external loaders, the target flat file must be fixed-width or delimited.

For IBM DB2 external loaders, the target flat file must be delimited.