Execu/Tech Systems, Inc.
Knowledgebase
Search:
850-747-0581 Email Website
Contents
 
:
IndexBookmarkPrint This Article

Home > Interfaces > OTA / HTNG > OTA / HTNG Logs

 The log files for the OTA / HTNG interface can help you determine what happened if you experience any problems.

To reduce clutter and disk usage, standard logs are limited to the most recent 250 messages. Each message will produce 4 log files, detailed below in the "Log File Locations" section.

If you need more detailed logs of the XML request and response messages, use the "Test Logs (Everything)" option. This is covered at the end of this page.
 

Log File Viewer (ETHTNGLovViewer.exe)

This is new and probably has bugs. Please email support if you find one.

Because the interface has several logs with different types of data (XML, Plain Text, etc.) they are difficult to read and make sense of. This log viewer should help you decode the riddle wrapped in the mystery inside the enigma of the log files. 

This application is located in the PMS software folder. If you can't find it, you can download it by CLICKING HERE. Extract the contents to the PMS software folder.



After you open the log file viewer you'll see that all the fields are blank. You'll need to click the Read Logs button at the top left. Click it ONLY ONCE!. The status bar at the bottom will let you know when it's finished reading the log files and if any were found, you should see a list of reservation records. 

If a name or confirmation number is missing, that means it was either missing from the log file (names are not sent with cancellation records) or the log file wasn't found.

Double - Click the record on the left to see the details from each of the four log files. They are shown in the order in which they are processed. If a log file is missing, you'll see an Internet Explorer type message telling you the file can't be found in the appropriate window.

Request From CRS is the XML message received from the CRS (TravelClick, Synxis, etc.).
Request To PMS the interface parses the XML and submits the appropriate data to the PMS.
Response From PMS the PMS processes the request and returns a response. If there is an error, it's returned, otherwise it returns the PMS confirmation number followed by the letter "S" for "SUCCESS"
Response To CRS the interface formats an XML response to send back to the CRS. This log lacks some of the login credentials required to submit a standalone response. The interface adds these credentials after the log is created.
If the response log file is found, you can resend it. This may be helpful if the CRS didn't receive a response to a request. If resending is available you will see the green button. Click it once and the response message will be resent within a few seconds.


Log File Locations

Logs for the OTA / HTNG interface are saved in the Request (RQFiles) and Response (RSFiles) folders.

These are the locations of the different logs.
RQFiles\Log    XML messages posted from the CRS to the PMS interface. 
RQFiles\Log\ToPMS    Messages posted to the PMS by the interface. 
RQFiles\Log\FromPMS    Message posted back to the interface by the PMS. 
RSFiles\Log    XML messages posted back to the CRS from the interface. 
SyncLog.txt is also in this folder and contains the results of the inventory, rate and restriction messages


All logs are saved as text files and the file name is yyyyMMddHHmmssff.txt where:

yyyy  =  The year as a four-digit number. 
MM  =  The month, from 01 through 12. 
dd  =  The day of the month, from 01 through 31. 
HH  =  The hour, using a 24-hour clock from 00 to 23. 
mm  =  The minute, from 00 through 59. 
ss  =  The second, from 00 through 59. 
ff  =  The hundredths of a second, from 00 through 99. 

ToPMS Log Codes

These are the codes sent in the messages to the PMS.

TY  =  Type of message (NEW, MOD, CNX) 
CN  =  OTA Reservation Confirmation Number 
AD =  Advance Deposit 
NL  =  Last Name 
NF  =  First Name 
NM  =  Middle Name 
NT  =  Name Title (Mr, Mrs, Dr) 
NS  =  Name Suffix 
MN =  More Names 
A1  =  Address line 1 
A2  =  Address line 2 
A3  =  Address City 
A4  =  Address State 
A5  =  Address Zip Code 
A6  =  Address Country 
AT =  Telephone 
T1  =  Travel Agent - IATA Number ProfileType = 4 
T2  =  Travel Agent - Name 
T3  =  Travel Agent - Address Line 1 
T4  =  Travel Agent - Address Line 2
T5  =  Travel Agent - City 
T6  =  Travel Agent - State 
T7  =  Travel Agent - ZIP 
T8  =  Travel Agent - Country 
T9  =  Travel Agent - Phone 
TA  =  Transport Arrival = Method, ID(flight), Time 
TD  =  Transport Departure = Method, ID(flight), Time 
C1  =  Company - Code ProfileType = 3 
C2  =  Company - Name 
C3  =  Company - Address Line 1 
C4  =  Company - Address Line 2 
C5  =  Company - City 
C6  =  Company - State 
C7  =  Company - Zip 
C8  =  Company - Country 
C9  =  Company - Phone 
C10   =  Company - Contact Salutation 
C11   =  Company - Contact Name 
G1  =  Group - Code   'ProfileType = 6 
G2  =  Group - Coordinator Name 
G3  =  Group - Coordinator Name 
G4  =  Group - Phone 
G5  =  Group - City 
G6  =  Group - State 
G7  =  Group - Zip 
G8  =  Group - Email
G9  =  Group - Company name 
CE  =  Email Address 
BD  =  Arrival Date 
NN   =  Number Nights 
NA  =  Guest Adult Count 
NC  =  Guest Child Count 
R1  =  Room Type 
RC  =  Rate Code 
P1  =  Rate 
S1  =  Service Description 
S2  =  Service Code 
S3  =  Service Cost 
CR  =  Credit Card Number 
CX  =  Credit Card Expiration Date 
CY  =  Credit Card Payment Code (Type of card) 
BS  =  Source of Business 
MS  =  Market Segment Code 
PD  =  Guest Profile ID from CRS 
CM  =  Reservation Comment 

FromPMS

The messages received from the PMS are very simple.

  • The first 10 characters are the PMS Confirmation Number. 

  • The 11th character is a result code. This is what it means:
C  =  Reservation already cancelled in PMS 
D  =  Reservation already exists. Duplicate 
L  =  Reservation locked by PMS User and unable to update 
N  =  Reservation not found 
S  =  Success. No problems 
(Missing)  =  The PMS was unable to respond within 10 minutes and the reservation may not have been updated. 


Test Logs (Everything)

This test option will produce a log of the XML request and response. This is very helpful when troubleshooting specific problems. You can see the message sent by Execu/Tech and the response received by the CRS.
   If your version of ETHTNG-Sender doesn't have these options, contact Execu/Tech support to update.
  • On the computer running the interface, stop the scheduled task for ETHTNG-Sender.

  • Locate the interface application, ETHTNG-Sender.exe, usually found in the same folder as the PMS software. 

  • Run it.

  • Click "Pause" 


  • Click the "Testing" tab. 
 

Follow the instructions after this image of the interface window to create and view the log.



  1. Change the Start and End dates to the dates being tested. If no specific date range is being tested, set it to cover just a few days to avoid a long test duration and long test log.

  2. Select "Resend All (not just changes)".

  3. Select "Test Logs (Everything)".

  4. For "Message to send?" select the message type you're troubleshooting.

  5. Click "Send Sync".
    Wait for it to finish. You'll know it's finished with you see "Waiting for next message." displayed above the blank XML message display box.

  6. Click "Save / Display Log". This will save the file "TestLog.txt" in the "RSFiles\Log" folder and then open it in Notepad for you to view, copy, save to another location, etc.
     

  7. When you're finished testing, be sure to close this instance of the interface and restart the scheduled task.




Article ID
 ota___htng_logs
Views
 7378
Last Modified
 11/30/2021 9:15 AM