Queueing

Each Travelport Booking Feed customer is assigned to one or more data queues. Each queue can hold up to a maximum of 50,000 messages, and is assigned a unique Queue ID. However, individual queues can receive data from more than one Pseudo City.

Data can be downloaded to the same secure customer data queue from various locations (pseudo cities). The pseudo city must be activated for each location.

Queue Ownership

Data is sent to the “owning” pseudo city’s customer queue. In most cases, the owner of a booking is the pseudo city to which an Apollo or Galileo subscriber is either initialized or emulated.

Even if a branch or service bureau location is set up for Travelport Booking Feed, if either of these type locations modifies a booking, the data continues to be sent to the owning pseudo city. If “Change of Ownership” is invoked on a PNR/Booking File, subsequent data is sent to the new PNR/Booking File owner’s customer queue. If the new PNR/Booking File owner is not turned onto Travelport Booking Feed, no data is be sent to either the previous owner or the new owner.

Travelport Booking Feed Queue IDs

Before a customer’s data can be logged, a unique data queue must be assigned for that customer in a customer configuration file. The customer data queue consists of:

The three- or four-character Pseudo City Code (PCC) of the agency where the data is gathered.

A three-character code uses an underscore (_) for the fourth character. IDs are case sensitive and must be in upper-case letters.

The CRS code (for example, 1G for Galileo or 1V for Apollo).
A system-generated four-digit ending.

For example:

A four-character PCC would be assigned a Queue ID such as: 79YW1G3848.
A three-character PCC would be assigned a Queue ID such as: EK4_1G4982.

Corporate IDs and Multiple Queues

For Travelport Booking Feed version 2.08.02 and later, the customer’s Corporate IDs can be used to accommodate multiple queues assigned to a PCC. For example, two Corporate IDs, IBM001USABC and IBM001USXYZ, can be assigned to PCC EK4. Events associated with each of these IDs are then routed to the appropriate Corporate ID-specific queue: EK4_1G4982_ABC and EK4_1G4982_XYZ, respectively.

This functionality is optional, and must be provisioned for the customer by Travelport. A single “default” queue per PCC remains for use by customers who do not opt into this functionality, or if a Corporate ID is not sent or is not recognized by the GDS. Using multiple queues requires a creating a separate Client Adapter for each queue.

Error Queue IDs

An Error Queue is also configured and assigned for each customer. The Error Queue consists of:

The three- or four-character PCC of the agency where the data is gathered.

A three-character uses an underscore (_) for the fourth character. IDs are case sensitive and must be in upper case letters.

The CRS code (i.e., 1G for Galileo or 1V for Apollo)
The word ERROR in upper case.

For example:

A four-character PCC would be assigned an Error Queue ID such as: 79YW1GERROR.
A three-character PCC would be assigned an Error Queue ID such as: EK4_1GERROR.

Queue Threshold Policies and Guidelines

Travelport Booking Feed queues are not infinitely sized; therefore, the adapter software must be run regularly to drain the data. If a queue reaches threshold limits, action will be taken by Travelport to ensure that system stability is maintained.

Threshold Policies

The following policies are enacted when a queue reaches the threshold:

If a customer’s queue reaches a threshold of 25,000 backed up messages, automated email notifications are sent to the agency support contact. These emails are sent once an hour until the threshold is under 25,000 messages.
If customer’s queue reaches a threshold of 50,000 backed up messages, Travelport Booking Feed will discard any new data. After it is discarded, the data will not be available.

Note: To ensure that threshold messages can be received, please provide a current, working email address for an appropriate contact to your Travelport Representative.

Determining the Number of Queues Required

When ordering Travelport Booking Feed, customers should consider the following concerns to determine the number of queues that will be required:

How often queues will be drained of data.
The number of Pseudo Cities that will log data to that queue. It is highly recommended to limit the number of PCCs assigned to a Queue ID.
The volume of transactions. Note that transactions are defined not only as segments and tickets, but also changes to PNRs/Booking Files because Travelport Booking Feed also transmits this data as queue items.

The following guidelines should be considered carefully to help determine the number of Queue IDs required:

Single Branch Agent	=	Single Branch Agent
Multi-Branch Agent (less than 10 PCCs)	=	1 Queue ID
Multi-Branch Agent (10–20 PCCs)	=	1 Queue ID, unless each PCC is likely to produce over 1,000 segments per day.
Multi-Branch Agent (20+ PCCs)	=	At least 1 Queue ID per 20 PCCs

Note: This information is offered as a guideline only. It should be noted that the true measure of capacity is the number of transactions that the customer will create. For customers with exceptionally high transaction volume, it is possible that a limit of one Queue ID per one PCC will be needed.

Multiple Queues for Associated Locations

Data can be sent to multiple customer queues. For example, a large travel agency may have different locations in which data is needed to produce comprehensive management reports. One location may be responsible for monitoring booking quotas, while another location may be responsible for ensuring compliance to the company travel policy. With Travelport Booking Feed, both of these locations can have the same data they both need to do their jobs.

Additional recipient locations are assigned in the agency configuration file as associated locations. Only authorized Travelport personnel can view and/or modify the agency configuration file. Each associated location must also have a unique Queue ID setup to receive data.

Associated locations do not need to load the Travelport Booking Feed application. However, they do need a working database and valid Queue ID.