Table of Contents

Search

  1. Preface
  2. Informatica Developer
  3. The Model Repository
  4. Searches in Informatica Developer
  5. Connections
  6. Physical Data Objects
  7. Flat File Data Objects
  8. Logical View of Data
  9. Viewing Data
  10. Application Deployment
  11. Application Patch Deployment
  12. Application Patch Deployment Example
  13. Continuous Integration and Continuous Delivery (CI/CD)
  14. Object Import and Export
  15. Appendix A: Data Type Reference
  16. Appendix B: Keyboard Shortcuts
  17. Appendix C: Connection Properties

Developer Tool Guide

Developer Tool Guide

Run-time: Write Properties

Run-time: Write Properties

The Developer tool displays run-time properties for flat file targets in the
Run-time: Write section
in the
Advanced
view. The Data Integration Service uses this information when it writes data to a flat file.
The following table describes the write properties that you configure for flat file data objects:
Property
Description
Append if exists
Appends the output data to the target files and reject files.
If you do not select this option, the Data Integration Service truncates the target file and reject file before writing data to them. If the files do not exist, the Data Integration Service creates them.
Default is disabled.
Create directory if not exists
Creates the target directory if it does not exist.
Default is disabled.
Header options
Creates a header row in the file target. You can choose the following options:
  • No header. Does not create a header row in the flat file target.
  • Output field names. Creates a header row in the file target with the output port names .
  • Use header command output. Uses the command in the Header Command field to generate a header row. For example, you can use a command to add the date to a header row for the file target.
Default is no header.
Header command
Command used to generate the header row in the file target.
Footer command
Command used to generate the footer row in the file target.
Output type
Type of target for the mapping. Select File to write the target data to a flat file. Select Command to output data to a command.
Command
Command used to process the target data.
On UNIX, use any valid UNIX command or shell script. For example, use the following command to generate a compressed file from the target data on UNIX:
compress -c - > MyTargetFiles/MyCompressedFile.Z
On Windows, use any valid DOS command or batch file. The flat file writer sends the data to the command instead of a flat file target. For example, use
cmd
as the target command on Windows to avoid staging data in the file system and to avoid any security breaches.
You can improve mapping performance by pushing transformation tasks to the command instead of the Data Integration Service. You can also use a command to sort or to compress target data.
Merge command
Merge command used to process merge data for all target partitions. The Data Integration Service must use a concurrent merge type for a command to process merge data. The command might not maintain the order of the target data.
Output file directory
Output directory for the flat file target. The machine that hosts Informatica services must be able to access this directory.
Enter multiple directories separated by semicolons to increase performance when multiple partitions write to the flat file target.
Default is the TargetDir system parameter.
Output file name
File name of the flat file target.
If multiple partitions write to the flat file target and you choose not to merge target data, each partition writes to a separate output file named
<output_file_name><partition_number>.out
.
Merge type
Type of merge that the Data Integration Service performs on the data for partitioned targets. If the Data Integration Service does not create partitions for the target, it ignores this value.
Select one of the following options:
  • No merge. The Data Integration Service concurrently writes the target output to a separate file for each partition.
  • Sequential. The Data Integration Service creates an output file for each partition and then merges them into a single merge file at the end of the mapping.
  • File list. The Data Integration Service creates a target file for each partition and creates a file list that contains the paths of the individual files.
  • Concurrent. The Data Integration Service concurrently writes the data for all target partitions to the merge file. Because the Data Integration Service writes to the merge file concurrently for all partitions, the sort order of the data in the merge file might not be sequential.
Merge file directory
Directory for the merge file for all target partitions. The machine that hosts Informatica services must be able to access this directory.
Default is the TargetDir system parameter.
Merge file name
Name of the merge file for all target partitions. Default is the output file name.
Connection type
The type of connection. Select from the following options:
  • None. The target file does not require a connection. The target file location is specified by the output file directory.
  • Hadoop File System. The target file is in HDFS.
Default is None.

0 COMMENTS

We’d like to hear from you!