Key Considerations

Consider the following important information before you start implementing the DR solution:

• The scheduled parameters in the integrations may not be the latest in the secondary instance because this depends on how often you update them. Hence, you must frequently update integrations with scheduled parameters in the secondary Oracle Integration instance. See Automate Scheduled Parameters Updates.
• If a connectivity agent is required, you must provision and configure separate connectivity agents for the primary and secondary Oracle Integration instances.
• When the primary instance is active, you must stop or deactivate scheduled flows and integrations with polling triggers in the secondary instance. After a failover, activate these artifacts in the secondary instance.
• The monitoring data (message history) is not replicated. You can use the OCI Logging service to extract the message history in your data lake or warehouse to have a global view.
• Ensure that your source applications and end users use the custom endpoint to access the Oracle Integration instance. Your administrators must use the respective original instance hostnames to manage the instances.
• When a failover to the secondary instance is required, you must manually change the routing by updating the DNS record at your DNS provider. Here are some additional points to note about the failover process:
  • It's quick and simple for non-scheduled and non-polling integration flows.
  • Scheduled flows and integrations with polling triggers require special handling.