Sabre Cruise Web Services Developer Guide August 2009 © 2009, Sabre Inc. All rights reserved. This documentation is the confidential and proprietary intellectual property of Sabre Inc. Any unauthorized use, reproduction, preparation of derivative works, performance, or display of this document, or software represented by this document, without the express written permission of Sabre Inc. is strictly prohibited. Sabre and the Sabre logo design are trademarks and/or service marks of an affiliate of Sabre Inc. All other trademarks, service marks, and trade names are owned by their respective companies. TABLE OF CONTENTS Introduction to Sabre Web Services ........................................................................................................... 5 Web Services .............................................................................................................................................. 5 XML ..................................................................................................................................................... 6 SOAP .................................................................................................................................................... 6 WSDL ................................................................................................................................................... 6 About Sabre Web Services ......................................................................................................................... 7 Integrated Computer Environment ............................................................................................................ 8 Cruise Web Service .....................................................................................................................................10 Transaction Organization .........................................................................................................................13 Cruise Request .....................................................................................................................................13 Cruise Response ...................................................................................................................................15 Text Substitution - Forcing fully translated advisories .............................................................................20 Related Fields in the Cruise Web Services API: ..................................................................................20 ErrorLevel ............................................................................................................................................20 What do we expect from the Web Service consumer? .........................................................................23 Domain Tables .............................................................................................................................................24 Table Organization ...................................................................................................................................25 Domain Table Types .................................................................................................................................26 Type Definition Tables ........................................................................................................................26 Global Tables .......................................................................................................................................26 Vendor Specific Tables ........................................................................................................................26 Constants tables ...................................................................................................................................27 List of Domain Tables ...............................................................................................................................27 Message Rules ..............................................................................................................................................30 Global Rules .............................................................................................................................................30 Vendor Rules .............................................................................................................................................30 Booking Process ...........................................................................................................................................34 Sabre and Customer Responsibilities ........................................................................................................38 Sabre’s Responsibilities ............................................................................................................................38 Client Responsibilities ..............................................................................................................................39 Documentation .............................................................................................................................................40 Certification Environment ..........................................................................................................................41 Appendix A - Connect and test Cruise Web Services ...............................................................................42 Appendix B – Error reporting ....................................................................................................................49 Error Types ...............................................................................................................................................49 Soap Faults ...............................................................................................................................................49 Errors encapsulated within the Advisory object .......................................................................................53 Errors encapsulated within Cruise Error Object .....................................................................................56 Recommended Error Handling .................................................................................................................58 Appendix C - Cruise Webservice WSDLS ................................................................................................59 Appendix D - Support .................................................................................................................................61 Sabre Cruise Web Service Introduction to Sabre Web Services Introduction to Sabre Web Services Sabre Web Services make it possible for organizations, such as agencies, suppliers, and trading partners, to integrate their business processes and applications with systems and data centers within Sabre Holdings, such as the Sabre system. This is accomplished by sending and receiving XML messages over the Internet. This section introduces you to the Web services technology, and the features and benefits of Sabre Web Services. It also discusses the standards and specifications that Sabre Web Services are designed to meet, including the Sabre XML specification. Web Services A service is a discrete unit of data or content that either consists of business logic or host command input and output. A service is exposed via a common access infrastructure. Exposing a service makes the data or functionality in a system or application available to other organizations through a common interface. When the common interface is Web-based or Internet- based, the service is called a Web service. A Web service is a software system that uses XML to define the format and data in messages. The messages are sent over the Internet. A definition of a Web service, taken from Sun Microsystems, follows. It is based on sending XML documents. A Web service accepts a request, performs its function based on the request, and returns a response. The request and response can be part of the same operation, or they can occur separately, in which case the consumer does not need to wait for a response. Both the request and the response usually take the form of XML, a portable data-interchange format, and are delivered over a wire protocol, such as HTTP. A Web Service functions like this: A client application calls a Web service by sending an XML message as a request, and the Web service infrastructure returns an XML response to the client. Because all communication is formatted with XML, a Web service is not tied to any particular operating system, programming language, or platform Web services are programmatic interfaces for application-to-application communication via the Internet. The W3C has a definition of Web services that incorporates WSDL: A Web service is a software system designed to support interoperable machine-to- machine interaction over a network. It has an interface described in a machine processable format (specifically WSDL). Other systems interact with the Web service in a pg. 5 Sabre Cruise Web Service Introduction to Sabre Web Services manner prescribed by its description using SOAP-messages, typically conveyed using HTTP with an XML serialization in conjunction with other Web-related standards. All Sabre Web Services can be consumed using a combination of either XML/SOAP or WSDL/SOAP. Consuming a service means that a client sends a request