Event archiving

It is possible to archive all events/transactions through toolkit.

Archiving is enabled through the Toolkit configuration page (toolkit.properties). A value of true enables archiving:

Archive_Logs=true

A value of false or the property missing will disable archiving.

When archiving is enabled a directory named archive is created in the External Cache. Each event is logged as a timestamped directory within the archive directory.

There are two kinds of events - test client and simulator and the formats are different.

Test client event example:

2017_01_13_08_19_50_032/
    log.xml

The directory name is a stylized version of the time stamp. The file log.xml is the normal log created by the test client. It contains the request and response messages, endpoint, test name etc.

Simulator event example:

2017_01_13_08_19_50_628/
    date.ser
    ip.txt
    log.txt
    request_body.bin
    request_body.txt
    request_hdr.txt
    response_body.txt
    response_hdr.txt

Most of the filenames are obvious. ip.txt is the IP address of the client that sent the message to the simulator. log.txt is the message validator output.

According to the HTTP standard the body of an HTTP message is a byte stream and the message header has to be decoded to know its encoding. The file request_body.bin contains the raw byte stream. For convenience it is also save with the default utf-8 encoding as request_body.txt. HTTP header are required to be plain ASCII.