User Guide : Map Connectors : Source and Target Map Connectors : Data Junction Log File
Share this page             
Data Junction Log File
The Data Junction Log File connector gives you the ability to read the log file generated by the Map Editor. A script file created in the Content Extractor Editor is used for the source file structure. The log file information can then be written to a specified target file or table.
This connector is also called Integration Log File.
If you are interested in parsing log files that contain process errors and messages, see Process and Transformation LogFile Parser. With this connector, there are more available schema data types, and the ability to parse process logs as well as logs for transformations.
Connector-Specific Notes
Data Junction Log File is not available as a target connector.
Property Options
Allows you to specify the byte order of Unicode (wide) characters. The default is Auto and is determined by the architecture of your computer. The list box options are Auto (default), Little Endian, and Big Endian. Little Endian byte order is generally used by Intel machines and DEC Alphas and places the least significant portion of a byte value in the left portion of the memory used to store the value. Big Endian byte order is used by IBM 370 computers, Motorola microprocessors and most RISC-based systems and stores the values in the same order as the binary representation.
Type the program variable.
The script file used for the source structure. The default file is djwinlog.djp.
Select the type of encoding used with source and target files. The default encoding is OEM.
Shift-JIS encoding is meaningful only in Japanese operating systems.
If your source data file starts with characters that need to be excluded from the transformation, set the StartOffset option to specify at which byte of the file to begin. The default value is zero. The correct value may be determined by using the Hex Browser.
Note:  This property is set in number of bytes, not characters.