About Communications with Sabre Web Services
Sabre Web Services are programmatic methods for accessing structured responses from the Sabre GDS for host commands. Sabre Web Services use two ways of communications: SOAP and REST. SOAP use the XML document style for communicating with the host system together with Sabre XML Specifications. Sabre XML Specifications are an extension of the Open Travel specification. They are specifically tailored to meet the needs of Sabre and Sabre's clients. REST use JSON document style for communicating with the host system.
The com.sabre.edge.cf.sws.SWS service (sometimes informally referred to as the "SWS service" in this documentation suite) gives Red Apps the ability to communicate with Sabre Web Services to access host commands as structured XML content.
The com.sabre.edge.cf.rest2sg.Rest2Sg service (sometimes informally referred to as the "Rest2Sg service" in this documentation suite) gives Red Apps the ability to communicate with Sabre Web Services to access host commands as structured JSON content.
Red Apps have two approaches to communicate with Sabre Web Services:
-
Send a single service call
-
Send multiple calls to Sabre Web Services, and use the locking service
When a Red App uses the locking service together with multiple calls to the SWS service, other Red Apps in Sabre Red 360 are prevented from making Web Services requests. Requests are also prevented from being sent to the host.
A Red App releases the lock when it is done making service calls, which lets other Red Apps communicate with Sabre Web Services and the Sabre host. If a Red App does not release the lock, the lock times out.
com.sabre.edge.cf.sws.SWS Service
The com.sabre.edge.cf.sws.SWS service lets Red Apps gain access to Sabre Web Services from Sabre Red 360. The SWS service handles session management and connectivity with Sabre Web Services on behalf of a Red App.
The SWS service expects the Document object (encapsulated XML) as a request and returns the same format to the Red App, however, this service does not parse the XML. You can either parse the XML manually or use some type of binding.
To use SWS Service, you need to obtain the following for each Web service that you want your Red App to consume:
-
Action code for the request
-
XML format for the request and response
-
Data elements and attributes in the request and response payloads
If communications failures occur between a Red App and the gateway to Sabre Web Services, the Red App request times out automatically after 60 seconds, and SRWRuntime returns an error to the Red App.
Constraint
The com.sabre.edge.cf.sws.SWS service manages sessions between Sabre Red 360 and a Red App for synchronization with the Sabre GDS PNR work area. However, some Sabre Web Services preserve a state that is not shared with this work area. The workflows for these Web Services must be completed through Sabre Web Services. Workflows cannot be completed through the Sabre host or Sabre emulator.
Example That Uses the Air Availability Web Service
A Red App requests air availability with the Sabre Web Services OTA_AirAvailLLSRQ service. The Red App must use either the ShortSellLLSRQ Short Sell Web Service or the OTA_AirBookLLSRQ Book Air Web Service to sell or book the transaction. The Red App cannot execute the selling or booking transaction through the Sabre host or Sabre emulator. After the Red App requests either the Short Sell or Air Book Web service, the sold segment is synchronized with the Sabre GDS PNR work area.
If you need more specific information about Sabre Web Services, contact your Sabre account manager.
com.sabre.edge.cf.rest2sg.Rest2Sg Service
The com.sabre.edge.cf.rest2sg.Rest2Sg service lets Red Apps gain access to Sabre Web Services from Sabre Red 360. The Rest2Sg service handles session management and connectivity with Sabre Web Services on behalf of a Red App.
The Rest2Sg service expects the JSON string as a request and returns the same format to the Red App, however, this service does not parse the JSON.
To use Rest2Sg Services, you need to obtain the following for each Web service that you want your Red App to consume:
-
Action code for the request
-
JSON format for the request and response
-
Data elements and attributes in the request and response payloads
If communications failures occur between a Red App and the gateway to Sabre Web Services, the Red App request times out automatically after 60 seconds, and SRWRuntime returns an error to the Red App.
Sabre System Special Characters
Use the DisplaySpecialCharacters Java class to include Sabre system special characters. For more information, see Sabre System Special Characters.