Tracing properties
The Gateway Server provides tracing options, which can be used to help identify error
conditions.
| Keyword | Values/Example | Description |
|---|---|---|
| trace | true or false | Controls the use of low-level tracing. The value must be specified in lower case. It is recommended for this be left to false, which is the default. |
| fileLevelTimings | true or false | When set to true, the Gateway generates a comma separated value file, .csv, containing the times in milliseconds it took to complete the different processing stages of the transmission. The file is generated in the directory where Gateway was started from and is named GwyFileLevelTimings_SERVERNAME_SERVERPORT.csv. This file is not cleaned up at end of day and is appended to if it already exists. It can be opened with Microsoft Excel. |
| itemLevelTimings | true or false | When set to true, the Gateway generates a comma separated value file, .csv, containing the times in milliseconds which it took to complete the processing of each transaction in the transmission. The file is generated in the directory where Gateway was started from and is named nnnnnnn_ItemTimes.csv Where nnnnnnn is the name of the incoming transmission processed by the Gateway. This file is not cleaned up at end of day. It can be opened with Microsoft Excel. |
| cleanupLevelTimings | true or false | When set to true, the Gateway generates a comma separated value file, CSV
containing the times in milliseconds it took to complete the end of day process. The file is generated in the
directory where Gateway was started from and is named:
|
| timingFilePath | ..\\timer | Directory to hold all timing files (transmission level, transaction level and cleanup level timing files). |
When active, the trace records are written to the log files.