The path to a directory for logging.
Setting LogDirectory will instruct the adapter to log the details of each transmission to unique files in the specified directory. For each request processed, the adapter will log the original EDI data, the complete text of the outgoing request and the incoming response.
The adapter will write multiple log file for each transmission, with separate extensions for each type of data:
|Status (.log)||Contains information on applied security options and pass/fail status of transmission|
|Request (.req)||Contains the outgoing request, after security options have been applied|
|Payload (.dat)||Contains log of unsecured payload prior to transmission|
|AS1 Message (.as3)||Raw AS3 messages created or downloaded by the adapter.|
|MDN Receipt (.as3-mdn)||MDN receipts created or downloaded by the adapter.|
|Error (.err)||This is only written in an error is encountered, containing the error.|
LogDirectory supports several macros that can be used to specify a unique directory path. If the path specified does not already exist, the adapter will attempt to create the directory. The following macros are supported:
|%MessageID%||The MessageID of the AS3 transmission, after it is generated.|
|%OriginalMessageID%||In MDN Receipts, the MessageID of the transmission that the receipt is for. You can use this to pair asynchronous MDN receipt logs with their transmissions|
|%date:format%||%Format% is a platform-specific date/time formatting string. For example: yyyy-MM-dd-HH-mm-ss-tttt|
The filenames will be chosen automatically by the adapter. Each filename will be the system time, in the format YYYY-MM-DD-HH-MM-SS-MMMM, with extensions "-2", "-3", used in case files of those names already exist.
If logs cannot be written an exception will be thrown.