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 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.