Install and Configure Oracle Integration for Disaster Recovery

You can select to enable disaster recovery when provisioning an Oracle Integration instance. This action installs a primary instance in one region and a secondary instance in another region.

  1. Sign in to the Oracle Cloud Infrastructure Console and note your selected region. See Sign In to the Oracle Cloud Infrastructure Console in Provisioning and Administering Oracle Integration 3.
  2. Open the navigation menu and click Developer Services. Under Application Integration, click Integration.
  3. From the Compartment list, click through the hierarchy of compartments and select the one in which to create the instance. You may need to expand the + icon to find the compartment to use. Compartments can contain other compartments.
    Pick a Compartment list expanded to display a hierarchy of compartments

    The page is refreshed to show any existing instances in that compartment.
  4. Click Create instance.
  5. Enter the following details.
    Field Description

    Display Name

    Enter the display name for the instance.
    Edition

    Select from the following supported editions for disaster recovery.

    • Enterprise
    • Healthcare

    Note: If you select the Standard edition, an error is displayed when you click Create.

    See Oracle Integration Editions in Provisioning and Administering Oracle Integration 3 to see what's licensed in each supported edition.

    Shape

    Only the Production shape is available for disaster recovery instances.

    Note: The Development shape is not supported.

    License Type

    Select the license type. See Choose a License Type in Provisioning and Administering Oracle Integration 3.

    Message Packs

    Enter the message pack number. See Choose a Message Pack Number in Provisioning and Administering Oracle Integration 3.

    The Use advanced options link appears at the bottom of the Create instance page.

  6. Click Use advanced options and select the Disaster recovery tab.
  7. Select the Enable disaster recovery toggle.
    A message is displayed.
    The failover instance will be located in the region_name region. It will remain in standby until you start the failover process.
. Some features including Process Automation, Visual Builder, custom endpoints, and private endpoints won't be available in this instance.


    The Create instance dialog is shown. The Message packs field is shown. this is the Hide advanced options link, which is selected. Below this are tabs for Network access, Disaster recovery (which is selected), and Tags. Below this is the Enable disaster recovery toggle, which is selected. A message is shown. The message is displayed above this image. Below this are Create and Cancel buttons.

    Note:

    Do not select to configure the options under the Network access tab. This feature is not supported in disaster recovery-enabled environments.
  8. Click Create.

    The Work requests section shows installation progress. As installation progresses, the % Complete value changes.


    The Work requests section shows a table with rows for Operation, Status, % Complete, Accepted, and Started.

    Note:

    Creation of the primary and secondary instances can take time to complete due to DNS configuration.
  9. Click Create integration instance to view details about installation progress. When creation of the primary and secondary instances in different regions completes successfully, the Finished field is updated. You do not receive a popup message when installation completes.


    The Work request details page is shown. Below this, the Create integration instance section is shown. The Work request information tab is selected, with labels shown for Percent complete, OCID, Accepted, Started, and Finished. a box labeled WR appears on the left with the words Work requests label in progress below it. Below this is the Resources section, with links for Log message and Error messages. To the right is the Log messages section, which consists of a table with columns for Message and Accepted.

    The installed primary instance includes a green circle with the label ACTIVE. The word Primary appears below the instance name to indicate that this is the primary instance.


    The Integration instance details page is shown. A green circle labeled OIC is shown as Active on the left. The instance name has a label of Primary. Below this are tabs for Service console, Edit, Failover, Move, and Add tags, and a More Actions drop-down list. Below this, the tab for Integration instance information is shown. Labels are shown for Created, Updated, Version, Consumption model, Edition, OCID, Service console URL, Shape, License type, Message packs, File Server, and Disaster recovery.

  10. Under Resources in the left navigation pane, click Disaster recovery.

    The Disaster recovery option is shown as being selected from the Resources section.

  11. Click the secondary instance.

    The details page for the secondary instance in the other region is displayed.
    • The word _Recovery is appended to the end of the secondary instance name. The _Recovery word always appears as part of this instance name, even when the secondary instance becomes the primary instance after a failover.
    • The word Secondary appears below the instance name. When you fail over from the initial instance to the secondary instance, Secondary is replaced with Primary.
    • A status of STANDBY appears below the circle labeled OIC.
    • The Start failover button is enabled for use. This is the only life cycle action that can be performed from the secondary instance.


    The Integration instance details page is shown. A brown circle labeled OIC is shown as Standby on the left. The instance name has a label of Secondary. Below this are tabs for Service console, Edit, Failover, Move, and Add tags. Only Failover is enabled for selection. All other tabs are disabled. Below this, the tab for Integration instance information is shown. Labels are shown for Created, Updated, Version, Consumption model, Edition, OCID, Service console URL, Shape, License type, Message packs, File Server, and Disaster recovery.

  12. Start designing integrations in your primary instance. As soon as you start, the synchronization of design-time metadata begins between the primary and secondary instances in near real time. This reduces the chance for data loss when a failover is required.