4. Database and Log Source

Contents

• Database and Log Source
  • Log Source
  • Data Model Issues
  • Databases

4.1. Log Source

4.1.1. Location

As of today, the location of the Amadeus back-end products’ log files varies from one to another. This leads to the needs of converging all theses files into a common location for the easier automatic processing, which can be done using the team’s Stats Generator. It needs following the instruction in the documents provided in the link above in order to generate the logs in the right locations.

The files generated will be supposed to be located in the PPP_STAT directory of the pppdelde account.

4.1.2. Format

While each log file is a delimiter-separated text file whose contents are varied from one source to another, their format however has to follow the same form.

\[key1|value1|key2|value2|...key_n|value_n|\]

Where key and value might be missing (in this latter case simply a blank will be showed, while in the first case both will be absent).

For example,

ADD|2012/04/11|ATT|00:00:00|AMM|obeap433|APN|ATC|AOI|SAOB2216H|
ADD|2012/04/11|ATT|00:00:04|AMM|obeap432|APN|ATC|AOI||
ADD|2012/04/11|ATT|00:00:04|AMM|obeap432|AOI|SAOB6H|

where we can see in the second line there is no value for the key AOI while there’s nothing at all for the APN key. Still the 3-letter key is not very human readable, we therefore have to map them to some more meaning words. One solution is to have this configuration file to instruct how to map the keyword with its readable name.

**Config File for ATC**

DD|Date|ATT|Time|AMM|Server|APN|Product|ATY|Query_Type|AQM|Query_Name|AST|Status|ACM|Canned_message_number|...

meaning the ATC log file will have these key: DD, ATT, AMM...and the DD key attribute will bear the name of Date while ATT means Time and so on...

The files after being processed will look something like this, being separated by the ‘’ character while having no string wrapping character.

BLB_size\Canned_message_number\16_31\Time\PSP_Error\
\339\\00:00:00\\
0\0\\00:00:04\NO VALID FARE/RULE COMBINATIONS FOR PRICING\

Equivalent csv table

header:“BLB_size”	Canned_message_number	16_31	Time	PSP_Error
widths:10	10	10	20	30
[blank]	339	[blank]	00:00:00	6
0	0	[blank]	00:00:04	NO VALID FARE/RULE COMBINATIONS FOR PRICING

4.2. Data Model Issues

There are several issues with the data currently employed.

• The first one is we only know an airline via its 2-letter IATA code and sometimes and we will have a conflict as it’s not a unique identifier for airline carriers.
• There are data with psp_error but the code error still indication 0
• There are unparsable string, with the ” character in it.

4.3. Databases

4.3.1. Connection

MySQL Server
* server: 172.16.132.101
* port: 3415
* databases: stats

One might need to contact the admin team in order to get the account needed to access this database server.

4.3.2. Schema