Travel: Sabre Integration
The primary Integration flow is as follows:
A person comes in and completes full registration on the Lenos site, providing air preferences information.
The Travel Agency then uses this Confirmation Number and the preference details and creates a ticketed PNR reservation for the Registrant. The agency will program the Campaign Id and Registrant Confirmation Number (individual identifier) in Sabre.
Lenos is subscribed to the Sabre ENS API, and it allows us to receive automatic notification of any PNR changes for the client.
Sabre Event Notification services sends notification to Lenos that the Travel itinerary was Created or Updated.
The Lenos ENS listener picks up the PNRID of this Registrant, looks up the Travel information and creates/updates the Itinerary for the Registrant into the Lenos system.
The Clients can look at the travel reports in real-time.
Process Flow for Using Event Notification Services
Customers must register with Sabre Dev Studio and get access to ENS and other Sabre API assets.
ENS sends the notifications to the receiving Lenos URL (subscriber) called the Event Sync, immediately after the Events occur. When an Event is triggered that matches the parameters that were specified in a subscription, the Event Sync application receives the notification in structured XML format via the IP address or URL in the subscription. If the Event does not match the specified parameter, the Event Sync Source does not send the notification to the Event Sync.
The process for Setting up and using ENS has the following general parts:
Register for ENS.
Your Sabre account representative registers with your organization. During registration, you provide your account representative with some specific information about the Event topics which interest you, and some subscription parameters.
The PCC you want to use for registration and subscription purposes.
A Lenos Event Sync URL to register with ENS.
A range of parameters for ‘PNR change’ Event topics - you provide the related PCCs and the configuration you want.
Subscribe to Event topics by creating subscriptions and establishing subscription parameters. Please note subscriptions must be updated/tested in Certification first.
After you register, you complete the subscription process. You create subscriptions by using a Web- based subscription management GUI.
Every subscription must have a start and end date and the URL address of the Lenos Event Sync where the notifications will be delivered.
2. Test Lenos Event Sync application in the Certification environment.
Deployment to the Production environment will only occur once ENS has confirmed successful testing.
3. Receive Event notifications.
After you create your subscriptions, Events that meet your criteria are pushed in XML format to the Lenos URL. The Lenos Event Sync application parses the content, picks the PNRID and processes t further to create/update Travel Itinerary. The Events continue to get pushed to the Listener URL until the expiration date is met, or you modify or cancel the subscription.
4. Manage subscriptions on a regular basis.
Subscription management is ongoing. After creating your subscriptions, you manage them whenever it is necessary. Management includes activities such as modifying the Event parameters, renewing subscription dates, creating new subscriptions with different parameters, and canceling subscriptions (sometimes referred to as unsubscribing). You can also obtain a list of your current subscriptions.
