Move an Oracle Integration Instance to a Different Region
You can move your Oracle Integration instance to a different region.
If you instead want to move your instance to a different compartment, see Move an Instance to a Different Compartment.
Note
You can't move an Oracle Integration instance from one tenancy to another, even if the tenancies are both within the same region, but you can export/import integrations across tenancies with appropriate permissions for object storage or explicit transfer of the export file.
You can't move an Oracle Integration instance from one tenancy to another, even if the tenancies are both within the same region, but you can export/import integrations across tenancies with appropriate permissions for object storage or explicit transfer of the export file.
If you are considering this type of move, here are some best practices to ensure the move is smooth.
- Use a custom endpoint for your Oracle Integration instances. See Configure a Custom Endpoint for an Instance. Ensure all clients are using the new custom endpoint.
- Export and import design-time metadata to move the existing configuration to the new instance in the new region. See Clone the Design-Time Metadata of an Entire Service Instance in Using Integrations in Oracle Integration 3.
- Do as much verification in the new region as possible. However, do not start polling or schedules to avoid duplicate processing.
- Configure the same custom endpoint for the new instance, but do not update the DNS Canonical Name (CNAME) at this time.
- When all verification in the new region is complete and all non-polling integrations are activated, switch the custom endpoint CNAME to point to the new Oracle Integration instance hostname.
- Deactivate the polling integrations and stop the schedules in the old instance.
- Activate the polling integrations and start the schedules in the new instance.
- If using File Server, a load balancer is probably required in each region and hostname. The load balancer performs port mapping because there is no guarantee that the File Server port number matches across instances. This is a great opportunity to use a standard SFTP port for external clients, along with a hostname. Once the load balancer is set up in each region and verified to be working, you can switch the hostname to the new region load balancer when you are ready to move traffic to the new File Server.
- These best practices can be used to move to a new stripe. However, both instances cannot be active at the same time and the original instance must be deleted.