Prerequisites
The following technical requirements are necessary to support a Travelport Booking Feed implementation. See the Installation section for more details.
Hardware Prerequisites
The recommended/minimum hardware requirements to run Travelport Booking Feed 10.1 are:
Recommended Hardware
- 1 GB RAM (32-bit) or 2 GB RAM (64-bit)
- 1 GB of hard disk space (32-bit) or 2 GB (64-bit)
- 1 GHZ or faster 32-bit (x86) or 64-bit (x64) processor -- Communications: Internet via secure SSL or dedicated VPN.
Note: The Travelport Booking Feed Client Adapter can be configured to exclusively log XML data and bypass the client database for receiving data. In this implementation, the XML data logs must be manually deleted. Therefore, the hard drive must allow for enough space to capture the anticipated amount of logs accumulate between purges.
See Host XML Logging for details.
Software Prerequisites
Each user is required to purchase and install the following software in support of Travelport Booking Feed.
Operating System
Any version of Microsoft® Windows 7 ® and above is supported. Windows XP is not supported by Travelport Booking Feed.
Recommended Databases
For customers who choose to use a database to receive Travelport Booking Feed data, the following databases are recommended:
- Microsoft® SQL Server®
- Sybase® Adaptive Server®
Recent versions of both Microsoft SQL Server and Sybase Adaptive Server have worked successfully with Travelport Booking Feed to date, although not all versions have been formally certified. Contact your representative if you encounter difficulties with using Travelport Booking Feed in conjunction with a specific version of these products.
If you do not have either of these databases, you can download trial versions from www.microsoft.com or www.sybase.com.
Reporting Software
For customers who want to produce ready-made reports for management teams, it is recommended that an application, such as Crystal Reports, is used with the database.
Travelport Booking Feed Installation Components
The following Travelport Booking Feed installation components are required:
- Travelport Booking Feed 10.1 Adapter, including Java version 1.7.0_21 (32-bit).
This application serves as the interface between the Galileo® or Apollo® GDS system and the customer’s local database.
- A SQL database server, if the database implementation of Travelport Booking Feed will be used. Travelport Booking Feed database supports current versions in line with Microsoft support.
The currently supported database servers are Microsoft® SQL Server® and Sybase® Adaptive Server®. Setup scripts are also included for the client database for both Adaptive Server and SQL Server. These setup scripts can be installed with the adapter or manually installed, as preferred.
See the Installation section for more details.
Connectivity
SSL-based connectivity is the standard method to access Travelport Booking Feed. However, if a site currently has a direct IP subscriber line to Galileo or Apollo, or already has Travelport’s SSL client installed for an application, no other connectivity is required.
The following connectivity options are supported with this version of Travelport Booking Feed:
- SSL connection (Recommended)
If SSL is being used for connectivity, customer must also have Port 443 open to gdssl-atl.galileo.com. Refer to the SSL Installation Guide for further details. A copy of the guide is available at http://support.galileo.com/aps.
- Existing unmanaged VPN connection.
- Directly connected lease line.
Contact your Travelport representative to discuss connectivity options suitable for your environment.
Connection Speed
A high-speed connection, such as DSL or Broadband, is required. A dial-up connection is not supported, as even low-volume customers may experience difficulties such as backed up queues that lead to a potential loss of data.
Note: The Travelport Booking Feed product is not a query/reply (synchronous) architecture whereby clients initiate a request and receive a real-time response. Instead, Travelport Booking Feed uses a workflow (asynchronous) architecture in which data volume represents a combination of all available data for Travelport Booking Feed-designated transactions at a given time. Therefore, an individual agency’s response time can be affected by the aggregate volume of transactions.
Queues
A Queue ID for each customer queue will be assigned by Travelport. Additional connectivity permissions will be required, depending on the type of connection.
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. To accommodate separate queues, a Client Adapter must be installed for each queue. See Creating Separate Queues for details.
Firewall Settings
If Travelport Booking Feed is used through a direct connection, i.e., a leased line rather than a VPN connection, the following firewall settings must be adhered to:
- If the market runs its own network, they must also ensure that they open Port 1415 on their firewall.
- If SSL is being used for connectivity, the customer must also have Port 443 open to gdssl-atl.galileo.com.
- Refer to the PDF SSL Installation Guide for further details.