Gasboy SiteOmat Maintenance Manual - Manual (Page 194)

190
SiteOmat Setup and Maintenance Manual – MDE 4817G
Then for each new authorized transaction it shows the authorization lines, when transaction is
competed it displays the TX lines, for example:
[2009-02-05 10:51:35.506 00023265] O:OrPT T8012107672337245
[2009-02-05 10:51:38.266 00023264] APS: 8012107672337245
atg=200000004||0|-1 P1 N2 L99999999.00 Tm
[2009-02-05 10:51:44.340 00023262] TX 8012107672337245 P1 N2 Q2.12 S4.24
[2009-02-05 10:51:51.506 00023265] O:OrPT T8012107672337245
[2009-02-05 10:52:32.645 00023264] APS: 0000000000000003517 atg=0|41|0|-1
P1 N2 L99999999.00 Tm
[2009-02-05 10:52:46.533 00023262] TX XXXXXXXXXXXXXXX3517 P1 N2 Q6.91
S13.82
8-4.4. BOS Log Files
This section describes the different types of log files that appear on the BOS. The name of the log
file appears in the header of each section.
All log files appears in the folder c:\orpak\BOS\bin\log.
8-4.4.1. BOS_REMOTE_HO.log
Records all out bound and in bound traffic of BOS with a remote head office – similar to
WEB_COMM but in this case we are a client for HO.
8-4.4.2. Database Logs (DATA.log, META_DATA.log, LANG.log)
For each database used by the system, there exists a log file that records all queries run on that
particular database. It can be considered as a sort of journal of activity on that database.
The database log files include both SELECT queries, as well as queries that modify the database in
some way.
Note that the database log files are primarily intended for use by development.
8-4.4.3. Web Server Access Logs (WebAccessxxxx.log)
For each attempt to establish a SiteOmat session with a name and password, an entry is written to
this log by the web server.
The port number is included in the name of the log file.
8-4.4.4. Web Server Communications Logs (WebCommxxxx.log)
This log file contains all HTTP requests made to the web server.
SOAP requests originating on the FCC are also logged to this file.
The port number is included in the name of the log file.