Ensure that Integrations Using OCI Actions Continue to Run Successfully

If you call Oracle Cloud Infrastructure with the OCI Object Storage action, OCI Function action, or any of the OCI AI service actions from integrations, you must perform tasks to ensure that these integrations continue to run successfully in the secondary instance.

Create Minor Version Integrations (Recommended)

This recommended approach is a combination of pre-failover and post-failover tasks. For example, assume you use an OCI Object Storage action in an integration. To account for a disaster recovery failover, perform the following integration tasks:
  1. Create a minor version of the integration on the primary instance.
  2. Initiate a failover.
  3. Update the minor version of the integration in the secondary instance to reflect the new endpoint URI.
  4. Save and activate the minor version.

    When the initial primary instance again becomes active, you activate the major version of the integration on that instance. See Object Storage Native Action in Oracle-Managed Disaster Recovery.

You can follow a similar minor integration creation approach if using an OCI Function action or any of the OCI AI services in your integrations.

Manually Reconfigure OCI Actions Used in Integrations

If you don't want to create a minor integration version, you must manually reconfigure your calls after failover to point to the secondary instance.

  • OCI Object Storage action and OCI Function action. See Call Category in Using Integrations in Oracle Integration 3.

  • Any of the OCI AI services. See OCI AI Services Category in Using Integrations in Oracle Integration 3.