1. Implementation Guide
  2. Introduction
  3. Technical Assumptions

Technical Assumptions

This accelerator operates under the following technical assumptions:

  • The Oracle Hospitality Adapter must be used to fetch OPERA Cloud business events.

    • The polling interval range is between 5 seconds and 600 seconds.

    • The trigger is a single-threaded execution.

  • OPERA de-queues the business events after fetching them.
  • External Systems expect the payload in JSON format.
  • The maximum business events per fetch is 20 messages with a payload size up to 10 MB.

    • The Accelerator is configured to handle a payload size of 5 MB.

  • Sequence business events per the following:

    • Business Event creation timestamp

    • Business Event Id

  • For each external system, you must clone the recipe with the external system details.

  • Tracing and tracking is disabled for all integrations.

  • Once activated, accelerator integrations must not be deactivated at any point during the runtime flow.

  • Accelerator integrations should not be run manually unless otherwise specified.

Parent topic: Introduction