Sabre Native API to Replace Emulator API

by Molly Jones

The new Sabre Red Workspace (SRW) features a highly configurable agent workspace, opening the door for developers to design customized travel solutions for their customers. Launching on April 3rd, the Sabre Red Workspace Developer Toolkit will be a step-by-step, comprehensive toolkit for developers looking to create solutions for the new Sabre Red Workspace. One of these tools, the Native API, provides an upgraded bridge solution that will enable developers to design custom Sabre Red Workspace applications using their own technology.

Before, external applications were integrated into SRW through the Emulator API, which was based on a library file (.dll). With the launch of the Sabre Red Workspace Developer Toolkit, the Emulator API will be sunset and replaced with the Native API, which uses Java Message Service queues (ActiveMQ) to enable interactive, message-based communications between external applications and the new Sabre Red Workspace.

Since the Native API is only accessible through the Sabre Red Workspace Developer Toolkit, developers must become Red App certified providers to integrate their own solutions into the new Sabre Red Workspace.

To become a Red App certified provider, go to www.sabreredappcentre.com to access and fill out the proper forms (About>For Providers>Apply). Everyone is required to submit a proposal. To do so, log in to the Sabre Red App Center, to to my Red Apps, and follow the instructions to submit a proposal.

In order to build an application for use in the new Sabre Red Workspace using your own platform, you have to create a bridge plug-in for the application to work. This involves two parallel development processes:

Build the Bridge

Using the Native API and documentation found in the Sabre Red Workspace Developer Toolkit, create a simple Red App, using Java and the Eclipse IDE. This Red App will consist of a few configuration files that will open the channels of communication between your application and the new Sabre Red Workspace, seamlessly integrating your solution into the workspace.

Build Your App

The Native API solution supports open-platform development, so you can use .Net, Python, Perl, or any other coding language you like and its corresponding IDE to build your application.

Once the application is completed, use the bridge application you created using the Native API to plug your application into the new Sabre Red Workspace. Please note, you must plug your app into the bridge application you created in order for it to work, so ensure your customers download the bridge and receive your application. The bridge built with the Native API will be on the Red App Centre, so you can direct your customers there to access it. However, you must distribute your application solution to customers yourself. Once your customers have both applications, your solution will be seamlessly integrated alongside all the other exciting functionalities the new Sabre Red Workspace has to offer.

Confused? Don’t be! Simply follow the four steps below, and you are well on your way to integrating your next big innovation into the new Sabre Red Workspace.

  1. Head to sabreredappcentre.com to fill out the form & submit a proposal to become a Red App Provider.
  2. Log into Sabre Dev Studio to access the Sabre Red Workspace Developer Toolkit.
  3. Use the Eclipse IDE + the Sabre Red Workspace Developer Toolkit to create a bridge to plug your application into the new Sabre Red Workspace.
  4. Send your customers both the link to your bridge (in the Red App Centre) and your application (distribute on your own), and your app will be integrated with the new Sabre Red Workspace!

About Molly Jones

Molly Jones is a Sr. Product Marketing Manager for the new Sabre Red Workspace. As part of Sabre’s New Graduate Leadership Program, she has also worked in Sabre’s Supplier Commerce, Global Accounts, and Global Operations divisions. She graduated from Rice University with a BA in English and Cognitive Science in 2015.

Leave a Reply

Your email address will not be published. Required fields are marked *