1 Features and Technical Overview

Oracle Hospitality OPERA Cloud Business Events Resequencer Technical Accelerator provides a way to ensure that business events entering the system are processed in a specific order. It leverages the Oracle Integration and the FIFO Accelerator to enforce a strict processing order.

High Level Architecture

Figure 1-1 Re-sequencing of OPERA Business Events Prior to Partner Systems Delivery

OPERA Cloud Business Events

Any transaction inside OPERA Cloud is considered a business event (BE). Once a transactional change occurs inside OPERA Cloud, the business event is captured and queued inside the outbound queuing system after the message is transformed. The messages are then moved to the Event Hub in Oracle Hospitality Integration Platform (OHIP).

OPERA Cloud PMS users must manually configure business events so they are transmitted to the appropriate External System.

Developers can use the OPERA Cloud Integration Processor API resources in OHIP that expose the functionality to fetch business events. This is a real-time API optimized for integrations. The following operations retrieve business events for one or multiple hotels:

• /int/v1/externalSystem/extSystemCode/businessEvents

• /int/v1/externalSystem/extSystemCode/hotels/hotelId/businessEvents

The Oracle Integration Cloud (OIC) Hospitality Adapter can fetch business events from OPERA Cloud PMS at scheduled intervals as defined by the Developer in FIFO manner. In the adapter UI wizard, you can configure the intervals at which event data must be fetched.

OPERA Cloud requires business events to send messages to an external system and users must configure business events based to what the external systems can accommodate. Unique business events and data elements are defined for each external system/module combination. When an action is carried out in OPERA that involves the data element, a business event is triggered and it becomes a message to the external system. Business events are de-queued from OPERA Cloud once they are fetched using OHIP APIs. Business Events received using OHIP APIs from OPERA Cloud are sorted and sequenced, and the message header (date) contains a timestamp for when the events were fetched.

Fetching Business Events

To fetch business events that will be executed by Hospitality Technical Accelerator:

• Business events are captured from OHIP using the OIC Hospitality Adapter (Trigger Role).

• The following OHIP APIs are used to fetch business events:

  • Fetch just for given Hotel ID (default) — /int/v1/externalSystem/{extSystemCode}/hotels/{hotelId}/businessEvents

  • Fetch for all Hotel IDs of the tenant associated to the External System ID — /int/v1/externalSystem/{extSystemCode}/businessEvents

• Using the OIC Hospitality Adapter, users can select to fetch all business events related to one particular external system id or fetch business events related to one hotel id that corresponds to an external system id.

• A maximum of 20 business events can be fetched in a poll.

• The polling interval lies between 5 seconds to 600 seconds.

• Multiple OIC instances fetch the business events.

This Technical Accelerator has a set of OIC integrations that address the re-sequencing of OPERA Cloud Business Events to the original sequence per a sorting logic. New business events from OPERA Cloud for a hotel or multiple hotels within a hotel chain are pulled using Oracle Hospitality Integration Platform (OHIP) APIs and Oracle Hospitality Adapter via integrations that re-sequence these business events in an Oracle Autonomous Transaction Processing (ATP) (to be provisioned separately). The re-sequence uses the business event timestamp and business event id to ensure the sequence of business events is accurate and delivered in a FIFO fashion to the target external system.