Move an Instance
There are several ways to move Oracle Integration instances.
Move an Instance to a Different Compartment
You can move an Oracle Integration instance to a different compartment.
If you instead want to move an instance to a different region, see Move an Instance to a Different Region or Stripe.
Note
Moving an instance to another compartment doesn't affect runtime or design-time access to the Oracle Integration instance. However, it can potentially change who has access to the instance in the Oracle Cloud Console. For example, if User A has permission to manage items only to Compartment 1, and you move the instance to Compartment 2, User A will lose access to the instance. Before moving an instance to a new compartment, make sure that all users that need access to the instance will still be able to access the instance after the move.
Moving an instance to another compartment doesn't affect runtime or design-time access to the Oracle Integration instance. However, it can potentially change who has access to the instance in the Oracle Cloud Console. For example, if User A has permission to manage items only to Compartment 1, and you move the instance to Compartment 2, User A will lose access to the instance. Before moving an instance to a new compartment, make sure that all users that need access to the instance will still be able to access the instance after the move.
To move an Oracle Integration instance to a different compartment:
- You can move an instance from the list of Oracle Integration instances or while viewing the instance's details:
- To move an instance from the Integration instances page (the list of Oracle Integration instances), to the right of the instance you want to move, click
, then click Move.
- To move an instance from the instance details page, while viewing the instance you want to move, click Actions, then click Move.
- To move an instance from the Integration instances page (the list of Oracle Integration instances), to the right of the instance you want to move, click
Move an Instance to a Different Region or Stripe
To move an Oracle Integration instance to a different region or stripe, create an instance in the new region or stripe, then export the design-time metadata from your old instance and import it into the new instance.
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.
- If you are moving an instance (not just cloning an instance), where the new instance replaces the old instance, you must delete the old instance so that only the new instance is used going forward. Both instances can't be active at the same time.
Here's a high-level overview of best practices for moving your instance to a different region.
| Best practice | Associated documentation |
|---|---|
| Make sure your existing Oracle Integration instance uses a custom endpoint and that all clients are using the custom endpoint. | Configure a Custom Endpoint for an Instance |
| Back up your Oracle Cloud Infrastructure (OCI) logs. Audit and activity stream data isn't copied when cloning design-time metadata. | Scenario: Archiving Logs to Object Storage in the OCI documentation |
| Create a new instance in the new region or stripe. | Create an Oracle Integration Instance Note: The new instance must be empty for the next task. |
| Export design-time metadata from the old instance and import it into the new instance. | Clone the Design-Time Metadata of an Entire Service Instance in Using Integrations in Oracle Integration 3 |
| Configure a custom endpoint for the new instance with the same host name you used for your old instance, but do not update the DNS Canonical Name (CNAME) until you verify that the new instance is working properly. | Configure a Custom Endpoint for an Instance |
| Make sure user access, connectivity, and additional features are configured on the new instance as they were on the old instance. | Use the post-upgrade instructions as an example of areas to check: Summary of Post-Upgrade Tasks |
| Complete your organization's verification tasks on the new instance, such as performing integration load testing. However, do not start polling or schedules to avoid duplicate processing. | N/A |
| When you've finished verifying the new instance and all non-polling integrations are activated, switch the custom endpoint CNAME to point to the new Oracle Integration instance hostname. | Post-Configuration Tasks for an Oracle-Managed Custom Endpoint |
| Deactivate all polling integrations and stop the schedules in the old instance. | Deactivate an Integration and Start and Pause an Integration Schedule in Using Integrations in Oracle Integration 3 |
| Activate the polling integrations and start the schedules in the new instance. | Activate an Integration and Start and Pause an Integration Schedule in Using Integrations in Oracle Integration 3 |
| Delete the old instance. | Delete an Instance |
| If you're 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. | N/A |