Logging

Travelport Booking Feed supports the following types of logging:

All logging files are saved into the logs directory of the Travelport Booking Feed application. By default, this directory is located in \Program Files\Galileo International\Travelport Booking Feed\logs.

In addition to the error queue, there are also additional logging capabilities within the client application.

Error Logging

When a non-critical error is encountered, the Travelport Booking Feed Client Adapter application retries to send a message three times before logging the message as an error and trying a new message. Non-critical errors are usually associated with a condition that may resolve itself in a short amount of time.

For example, if the database becomes temporarily unavailable because of a lock or pause condition, the application is unable to commit a transaction to the database. Because these conditions are usually temporary, by waiting for a few seconds and retrying the message, the application may be able to commit the message and continue.

When a critical error message is detected, the message is immediately moved to the agency error queue. The Travelport Booking Feed application automatically shuts down after three consecutive critical errors. A critical error usually occurs when the application detects that the message is corrupt.

Host XML Logging

The Client Adapter can be configured to exclusively log XML data and bypass the agency data database for receiving data. Host XML logging is managed through the Travelport Booking Feed Client Configuration panel.

The file names for these logs are directly associated with the transaction ID for the message. For example, if the last transaction was assigned a transaction ID of “1”, the XML file is saved as Msg1.xml. The transaction ID for a message a message can be identified in the command line console window. As each message is processed, the transaction ID of the message displays as ID = ##.

In addition to the XML logging, the application keeps a copy of the last message sent to the adapter, and the last bad message sent to the adapter. These files are respectively named LastMsg.xml and LastBadMsg.xml.

Note: The Host XML logging option should not be turned on unless there are problems, as there is no automatic cleanup of these logs, and the computer can eventually run out of disk space. The log files can be manually deleted from this directory at any time.

JDBC Logging for Database Failures

The JDBC message logging creates a file in the log whenever a database update fails. This file, JDBC.txt, contains a running log of all database commands that fail. JDBC message logging is managed through the Travelport Booking Feed Client Configuration panel.

Logging for Client Adapter Console Output

The wrapper.log file is always created to capture the output the Travelport Booking Feed application sends to the Client Adapter console. This file is very important when running the Travelport Booking Feed as a service because no console window displays. Wrapper.log contains all output from the application that would normally be displayed to the console. This file can be opened with Notepad or any other text editing program.

When wrapper.log reaches 1 MB, it automatically rolls into a new file, called wrapper1.log. Log data rolls up to three files; after the third file reaches 1 MB, the output then rolls back into Wrapper.log, and the file naming sequence restarts.