Architecture Workflow
Data Flow
There are three major components to the Travelport Booking Feed product:
- The Apollo or Galileo GDS.
- The Travelport UNIX environment, which stores ticket data and booking file change information.
- The Client Adapter in the customer environment, which receives and processes the data.
The following diagram shows an example of the processing flow for Travelport Booking Feed data.
Data Collection.After Travelport Booking Feed is activated, all initial reservations and subsequent updates to fare, ticketing, and itinerary on the Galileo or Apollo systems are included in the data source. After Travelport activates Travelport Booking Feed, the data feed begins immediately.
General PNR data, such as itinerary segments, passenger name, and ticketing remarks, is collected in a structured format from the CRS at end transact when the PNR/Booking File is completed.
Note:There is no retroactive data download and/or database update. Existing PNRs/Booking Files are not downloaded until a change is made to the PNR/Booking File itself.
Data Conversion.The data is then passed to the Travelport Booking Feed application, where it is sent to an XML translator, which converts the data to XML format. The data is then passed to the agency configuration file, which determines the appropriate customer queue for the data.
Queuing.Each Travelport Booking Feed customer is assigned to one or more data queues. Data is sent to the “owning” pseudo city’s customer queue. However, data for each pseudo city can map into a single data queue or multiple “associated” queues.
Positive Acknowledgement.Travelport Booking Feed assures delivery of data within the defined threshold limit. Delivery to the agency database, or to an exclusive XML file, is retried until a positive acknowledgement has been returned from the client indicating the data has been saved successfully.
Client Adapter.Data is then received by the agency’s Client Adapter, which is networked by either a VPN connection or an SSL connection.
The Travelport Booking Feed Client Adapter can be initiated as needed, or installed as a service that launches automatically when a Travelport Booking Feed-designated computer is started. Whenever possible, it is recommended to leave Client Adapter to run continuously; therefore, the service is the recommended option.
The service option is especially convenient for customers with computers dedicated to the Travelport Booking Feed application. The service also gives us customers the ability to integrate other programs/applications with Travelport Booking Feed to create start/stop jobs.
Data Storage.After data is sent through the Client Adapter, it is stored in a SQL database. A command line console for the Client Adapter is available to capture the output from Travelport Booking Feed to the database.
As of the 2.05 release, customers also have the option to turn off database storage and log data directly to an XML file.
Note:The command line console is not available when the Client Adapter is installed as a service. However, the output data is available as a log.
July 2013