Oracle Integration for Oracle SaaS
Oracle Integration for Oracle SaaS, a streamlined version of Oracle Integration, gives you the features and benefits of Oracle Integration with a focus on SaaS. You can create Oracle Integration for Oracle SaaS instances in any Oracle data region if you created a new Oracle Cloud account on or after February 11, 2020.
Here are the key differences between Oracle Integration for Oracle SaaS and Oracle Integration:
- Purpose-built for connecting and extending Oracle SaaS. Specifically, every integration you create must have an endpoint in an Oracle Cloud SaaS application, every Visual Builder application you create must use at least one business object or API call from an Oracle Cloud SaaS application, and every process application you create must include at least one business object or API call from an Oracle Cloud SaaS application.
- Flexibility for hourly bursting. Oracle Integration for Oracle SaaS is offered as a monthly subscription in packs of one million messages per month, which keeps costs predictable even when you have unpredictable hourly volumes. Usage is reported monthly instead of hourly.
- Reuse of message packs across instances. Oracle Integration for Oracle SaaS users can apply their message packs across instances. The following example describes this usage. Assume you perform the following tasks:
- Buy five message packs, each consisting of one million messages.
- Create three separate instances for development, test, and production.
- Assign one message pack to all three instances.
- Keep the two remaining message packs in a savings pool for future use.
If the load on the production instance increases, assign one message pack from the savings pool to the production instance. The production instance now consists of two message packs of one million messages each. You decide later to assign the remaining message pack to a new pre-production instance. If you delete the pre-production instance in three months, you can return the message pack from that instance to the savings pool for re-assignment to an existing instance. Or, you can provision a new instance to which you assign that message pack.
- Provisioning. Creating an instance for Oracle Integration for Oracle SaaS is slightly different from creating an instance for Oracle Integration, and Bring Your Own License (BYOL) is not available in Oracle Integration for Oracle SaaS. Differences in provisioning are noted in Create an Oracle Integration Instance.