text
stringlengths 65
20k
|
---|
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.Chapter 3 Key Considerations 3-2When 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.Prerequisites Ensure that all prerequisites for the Integrations DR solution are met before you begin the configuration process.Before you begin the DR configuration process for Integrations, you must: Provision a second Oracle Integration instance in a different OCI region with at least one message pack.However, to ensure that the secondary instance handles the usual volume, provision it with the same number of message packs as your primary instance.Provision an OCI Object Storage bucket for metadata migration.Obtain a custom hostname (in a domain of your choice) and an SSL certificate for it.Set Up the Disaster Recovery Solution for Integrations Perform the following one-time configuration tasks to set up the disaster recovery solution for the Integrations feature.As part of the configuration, you can also set up an OCI DNS zone if necessary.Overview of configuration tasks: 1.Create two Oracle Integration instances in two different OCI regions; for example, one in Ashburn and another in Phoenix. |
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.Chapter 3 Key Considerations 3-2When 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.Prerequisites Ensure that all prerequisites for the Integrations DR solution are met before you begin the configuration process.Before you begin the DR configuration process for Integrations, you must: Provision a second Oracle Integration instance in a different OCI region with at least one message pack.However, to ensure that the secondary instance handles the usual volume, provision it with the same number of message packs as your primary instance.Provision an OCI Object Storage bucket for metadata migration.Obtain a custom hostname (in a domain of your choice) and an SSL certificate for it.Set Up the Disaster Recovery Solution for Integrations Perform the following one-time configuration tasks to set up the disaster recovery solution for the Integrations feature.As part of the configuration, you can also set up an OCI DNS zone if necessary.Overview of configuration tasks: 1.Create two Oracle Integration instances in two different OCI regions; for example, one in Ashburn and another in Phoenix.See Creating an Oracle Integration Instance in Provisioning and Administering Oracle Integration Generation 2 . |
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.Chapter 3 Key Considerations 3-2When 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.Prerequisites Ensure that all prerequisites for the Integrations DR solution are met before you begin the configuration process.Before you begin the DR configuration process for Integrations, you must: Provision a second Oracle Integration instance in a different OCI region with at least one message pack.However, to ensure that the secondary instance handles the usual volume, provision it with the same number of message packs as your primary instance.Provision an OCI Object Storage bucket for metadata migration.Obtain a custom hostname (in a domain of your choice) and an SSL certificate for it.Set Up the Disaster Recovery Solution for Integrations Perform the following one-time configuration tasks to set up the disaster recovery solution for the Integrations feature.As part of the configuration, you can also set up an OCI DNS zone if necessary.Overview of configuration tasks: 1.Create two Oracle Integration instances in two different OCI regions; for example, one in Ashburn and another in Phoenix.See Creating an Oracle Integration Instance in Provisioning and Administering Oracle Integration Generation 2 .2.You can do one of the following: Register a custom hostname in your own DNS. |
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.Chapter 3 Key Considerations 3-2When 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.Prerequisites Ensure that all prerequisites for the Integrations DR solution are met before you begin the configuration process.Before you begin the DR configuration process for Integrations, you must: Provision a second Oracle Integration instance in a different OCI region with at least one message pack.However, to ensure that the secondary instance handles the usual volume, provision it with the same number of message packs as your primary instance.Provision an OCI Object Storage bucket for metadata migration.Obtain a custom hostname (in a domain of your choice) and an SSL certificate for it.Set Up the Disaster Recovery Solution for Integrations Perform the following one-time configuration tasks to set up the disaster recovery solution for the Integrations feature.As part of the configuration, you can also set up an OCI DNS zone if necessary.Overview of configuration tasks: 1.Create two Oracle Integration instances in two different OCI regions; for example, one in Ashburn and another in Phoenix.See Creating an Oracle Integration Instance in Provisioning and Administering Oracle Integration Generation 2 .2.You can do one of the following: Register a custom hostname in your own DNS.Use OCI DNS zone. |
Your administrators must use the respective original instance hostnames to manage the instances.Chapter 3 Key Considerations 3-2When 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.Prerequisites Ensure that all prerequisites for the Integrations DR solution are met before you begin the configuration process.Before you begin the DR configuration process for Integrations, you must: Provision a second Oracle Integration instance in a different OCI region with at least one message pack.However, to ensure that the secondary instance handles the usual volume, provision it with the same number of message packs as your primary instance.Provision an OCI Object Storage bucket for metadata migration.Obtain a custom hostname (in a domain of your choice) and an SSL certificate for it.Set Up the Disaster Recovery Solution for Integrations Perform the following one-time configuration tasks to set up the disaster recovery solution for the Integrations feature.As part of the configuration, you can also set up an OCI DNS zone if necessary.Overview of configuration tasks: 1.Create two Oracle Integration instances in two different OCI regions; for example, one in Ashburn and another in Phoenix.See Creating an Oracle Integration Instance in Provisioning and Administering Oracle Integration Generation 2 .2.You can do one of the following: Register a custom hostname in your own DNS.Use OCI DNS zone.Create an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname. |
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.Prerequisites Ensure that all prerequisites for the Integrations DR solution are met before you begin the configuration process.Before you begin the DR configuration process for Integrations, you must: Provision a second Oracle Integration instance in a different OCI region with at least one message pack.However, to ensure that the secondary instance handles the usual volume, provision it with the same number of message packs as your primary instance.Provision an OCI Object Storage bucket for metadata migration.Obtain a custom hostname (in a domain of your choice) and an SSL certificate for it.Set Up the Disaster Recovery Solution for Integrations Perform the following one-time configuration tasks to set up the disaster recovery solution for the Integrations feature.As part of the configuration, you can also set up an OCI DNS zone if necessary.Overview of configuration tasks: 1.Create two Oracle Integration instances in two different OCI regions; for example, one in Ashburn and another in Phoenix.See Creating an Oracle Integration Instance in Provisioning and Administering Oracle Integration Generation 2 .2.You can do one of the following: Register a custom hostname in your own DNS.Use OCI DNS zone.Create an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.See Use an OCI DNS Management Zone . |
Scheduled flows and integrations with polling triggers require special handling.Prerequisites Ensure that all prerequisites for the Integrations DR solution are met before you begin the configuration process.Before you begin the DR configuration process for Integrations, you must: Provision a second Oracle Integration instance in a different OCI region with at least one message pack.However, to ensure that the secondary instance handles the usual volume, provision it with the same number of message packs as your primary instance.Provision an OCI Object Storage bucket for metadata migration.Obtain a custom hostname (in a domain of your choice) and an SSL certificate for it.Set Up the Disaster Recovery Solution for Integrations Perform the following one-time configuration tasks to set up the disaster recovery solution for the Integrations feature.As part of the configuration, you can also set up an OCI DNS zone if necessary.Overview of configuration tasks: 1.Create two Oracle Integration instances in two different OCI regions; for example, one in Ashburn and another in Phoenix.See Creating an Oracle Integration Instance in Provisioning and Administering Oracle Integration Generation 2 .2.You can do one of the following: Register a custom hostname in your own DNS.Use OCI DNS zone.Create an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.See Use an OCI DNS Management Zone .3.Configure a common custom endpoint for both primary and secondary Oracle Integration instances. |
Prerequisites Ensure that all prerequisites for the Integrations DR solution are met before you begin the configuration process.Before you begin the DR configuration process for Integrations, you must: Provision a second Oracle Integration instance in a different OCI region with at least one message pack.However, to ensure that the secondary instance handles the usual volume, provision it with the same number of message packs as your primary instance.Provision an OCI Object Storage bucket for metadata migration.Obtain a custom hostname (in a domain of your choice) and an SSL certificate for it.Set Up the Disaster Recovery Solution for Integrations Perform the following one-time configuration tasks to set up the disaster recovery solution for the Integrations feature.As part of the configuration, you can also set up an OCI DNS zone if necessary.Overview of configuration tasks: 1.Create two Oracle Integration instances in two different OCI regions; for example, one in Ashburn and another in Phoenix.See Creating an Oracle Integration Instance in Provisioning and Administering Oracle Integration Generation 2 .2.You can do one of the following: Register a custom hostname in your own DNS.Use OCI DNS zone.Create an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.See Use an OCI DNS Management Zone .3.Configure a common custom endpoint for both primary and secondary Oracle Integration instances.Note: If you are using a connectivity agent, you must provision a dedicated connectivity agent for each Oracle Integration instance and use the original instance hostnames in the agents configurations. |
Before you begin the DR configuration process for Integrations, you must: Provision a second Oracle Integration instance in a different OCI region with at least one message pack.However, to ensure that the secondary instance handles the usual volume, provision it with the same number of message packs as your primary instance.Provision an OCI Object Storage bucket for metadata migration.Obtain a custom hostname (in a domain of your choice) and an SSL certificate for it.Set Up the Disaster Recovery Solution for Integrations Perform the following one-time configuration tasks to set up the disaster recovery solution for the Integrations feature.As part of the configuration, you can also set up an OCI DNS zone if necessary.Overview of configuration tasks: 1.Create two Oracle Integration instances in two different OCI regions; for example, one in Ashburn and another in Phoenix.See Creating an Oracle Integration Instance in Provisioning and Administering Oracle Integration Generation 2 .2.You can do one of the following: Register a custom hostname in your own DNS.Use OCI DNS zone.Create an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.See Use an OCI DNS Management Zone .3.Configure a common custom endpoint for both primary and secondary Oracle Integration instances.Note: If you are using a connectivity agent, you must provision a dedicated connectivity agent for each Oracle Integration instance and use the original instance hostnames in the agents configurations.See Configure a Custom Endpoint . |
However, to ensure that the secondary instance handles the usual volume, provision it with the same number of message packs as your primary instance.Provision an OCI Object Storage bucket for metadata migration.Obtain a custom hostname (in a domain of your choice) and an SSL certificate for it.Set Up the Disaster Recovery Solution for Integrations Perform the following one-time configuration tasks to set up the disaster recovery solution for the Integrations feature.As part of the configuration, you can also set up an OCI DNS zone if necessary.Overview of configuration tasks: 1.Create two Oracle Integration instances in two different OCI regions; for example, one in Ashburn and another in Phoenix.See Creating an Oracle Integration Instance in Provisioning and Administering Oracle Integration Generation 2 .2.You can do one of the following: Register a custom hostname in your own DNS.Use OCI DNS zone.Create an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.See Use an OCI DNS Management Zone .3.Configure a common custom endpoint for both primary and secondary Oracle Integration instances.Note: If you are using a connectivity agent, you must provision a dedicated connectivity agent for each Oracle Integration instance and use the original instance hostnames in the agents configurations.See Configure a Custom Endpoint .4.Use REST APIs or the Oracle Integration UI to migrate the metadata from the primary to secondary instance for the first time. |
Provision an OCI Object Storage bucket for metadata migration.Obtain a custom hostname (in a domain of your choice) and an SSL certificate for it.Set Up the Disaster Recovery Solution for Integrations Perform the following one-time configuration tasks to set up the disaster recovery solution for the Integrations feature.As part of the configuration, you can also set up an OCI DNS zone if necessary.Overview of configuration tasks: 1.Create two Oracle Integration instances in two different OCI regions; for example, one in Ashburn and another in Phoenix.See Creating an Oracle Integration Instance in Provisioning and Administering Oracle Integration Generation 2 .2.You can do one of the following: Register a custom hostname in your own DNS.Use OCI DNS zone.Create an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.See Use an OCI DNS Management Zone .3.Configure a common custom endpoint for both primary and secondary Oracle Integration instances.Note: If you are using a connectivity agent, you must provision a dedicated connectivity agent for each Oracle Integration instance and use the original instance hostnames in the agents configurations.See Configure a Custom Endpoint .4.Use REST APIs or the Oracle Integration UI to migrate the metadata from the primary to secondary instance for the first time.See Migrate Metadata from the Primary Instance .Chapter 3 Prerequisites 3-3Once you have configured the DR environment by executing these tasks, verify your system end-to-end. |
Obtain a custom hostname (in a domain of your choice) and an SSL certificate for it.Set Up the Disaster Recovery Solution for Integrations Perform the following one-time configuration tasks to set up the disaster recovery solution for the Integrations feature.As part of the configuration, you can also set up an OCI DNS zone if necessary.Overview of configuration tasks: 1.Create two Oracle Integration instances in two different OCI regions; for example, one in Ashburn and another in Phoenix.See Creating an Oracle Integration Instance in Provisioning and Administering Oracle Integration Generation 2 .2.You can do one of the following: Register a custom hostname in your own DNS.Use OCI DNS zone.Create an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.See Use an OCI DNS Management Zone .3.Configure a common custom endpoint for both primary and secondary Oracle Integration instances.Note: If you are using a connectivity agent, you must provision a dedicated connectivity agent for each Oracle Integration instance and use the original instance hostnames in the agents configurations.See Configure a Custom Endpoint .4.Use REST APIs or the Oracle Integration UI to migrate the metadata from the primary to secondary instance for the first time.See Migrate Metadata from the Primary Instance .Chapter 3 Prerequisites 3-3Once you have configured the DR environment by executing these tasks, verify your system end-to-end.Access the custom endpoint and navigate through the Oracle Cloud Infrastructure Console. |
Set Up the Disaster Recovery Solution for Integrations Perform the following one-time configuration tasks to set up the disaster recovery solution for the Integrations feature.As part of the configuration, you can also set up an OCI DNS zone if necessary.Overview of configuration tasks: 1.Create two Oracle Integration instances in two different OCI regions; for example, one in Ashburn and another in Phoenix.See Creating an Oracle Integration Instance in Provisioning and Administering Oracle Integration Generation 2 .2.You can do one of the following: Register a custom hostname in your own DNS.Use OCI DNS zone.Create an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.See Use an OCI DNS Management Zone .3.Configure a common custom endpoint for both primary and secondary Oracle Integration instances.Note: If you are using a connectivity agent, you must provision a dedicated connectivity agent for each Oracle Integration instance and use the original instance hostnames in the agents configurations.See Configure a Custom Endpoint .4.Use REST APIs or the Oracle Integration UI to migrate the metadata from the primary to secondary instance for the first time.See Migrate Metadata from the Primary Instance .Chapter 3 Prerequisites 3-3Once you have configured the DR environment by executing these tasks, verify your system end-to-end.Access the custom endpoint and navigate through the Oracle Cloud Infrastructure Console.Configure a Custom Endpoint This procedure allows applications and users to access the same URL. |
As part of the configuration, you can also set up an OCI DNS zone if necessary.Overview of configuration tasks: 1.Create two Oracle Integration instances in two different OCI regions; for example, one in Ashburn and another in Phoenix.See Creating an Oracle Integration Instance in Provisioning and Administering Oracle Integration Generation 2 .2.You can do one of the following: Register a custom hostname in your own DNS.Use OCI DNS zone.Create an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.See Use an OCI DNS Management Zone .3.Configure a common custom endpoint for both primary and secondary Oracle Integration instances.Note: If you are using a connectivity agent, you must provision a dedicated connectivity agent for each Oracle Integration instance and use the original instance hostnames in the agents configurations.See Configure a Custom Endpoint .4.Use REST APIs or the Oracle Integration UI to migrate the metadata from the primary to secondary instance for the first time.See Migrate Metadata from the Primary Instance .Chapter 3 Prerequisites 3-3Once you have configured the DR environment by executing these tasks, verify your system end-to-end.Access the custom endpoint and navigate through the Oracle Cloud Infrastructure Console.Configure a Custom Endpoint This procedure allows applications and users to access the same URL.Configure a common custom endpoint for your Oracle Integration instances, so that applications and users can access Oracle Integration with the same URL regardless of which instance is active in the background. |
Overview of configuration tasks: 1.Create two Oracle Integration instances in two different OCI regions; for example, one in Ashburn and another in Phoenix.See Creating an Oracle Integration Instance in Provisioning and Administering Oracle Integration Generation 2 .2.You can do one of the following: Register a custom hostname in your own DNS.Use OCI DNS zone.Create an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.See Use an OCI DNS Management Zone .3.Configure a common custom endpoint for both primary and secondary Oracle Integration instances.Note: If you are using a connectivity agent, you must provision a dedicated connectivity agent for each Oracle Integration instance and use the original instance hostnames in the agents configurations.See Configure a Custom Endpoint .4.Use REST APIs or the Oracle Integration UI to migrate the metadata from the primary to secondary instance for the first time.See Migrate Metadata from the Primary Instance .Chapter 3 Prerequisites 3-3Once you have configured the DR environment by executing these tasks, verify your system end-to-end.Access the custom endpoint and navigate through the Oracle Cloud Infrastructure Console.Configure a Custom Endpoint This procedure allows applications and users to access the same URL.Configure a common custom endpoint for your Oracle Integration instances, so that applications and users can access Oracle Integration with the same URL regardless of which instance is active in the background.To configure a custom endpoint: 1.Choose a custom hostname for your instances and register it with a DNS provider. |
See Creating an Oracle Integration Instance in Provisioning and Administering Oracle Integration Generation 2 .2.You can do one of the following: Register a custom hostname in your own DNS.Use OCI DNS zone.Create an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.See Use an OCI DNS Management Zone .3.Configure a common custom endpoint for both primary and secondary Oracle Integration instances.Note: If you are using a connectivity agent, you must provision a dedicated connectivity agent for each Oracle Integration instance and use the original instance hostnames in the agents configurations.See Configure a Custom Endpoint .4.Use REST APIs or the Oracle Integration UI to migrate the metadata from the primary to secondary instance for the first time.See Migrate Metadata from the Primary Instance .Chapter 3 Prerequisites 3-3Once you have configured the DR environment by executing these tasks, verify your system end-to-end.Access the custom endpoint and navigate through the Oracle Cloud Infrastructure Console.Configure a Custom Endpoint This procedure allows applications and users to access the same URL.Configure a common custom endpoint for your Oracle Integration instances, so that applications and users can access Oracle Integration with the same URL regardless of which instance is active in the background.To configure a custom endpoint: 1.Choose a custom hostname for your instances and register it with a DNS provider.2.Obtain an SSL certificate from a certificate authority (CA) for your hostname. |
2.You can do one of the following: Register a custom hostname in your own DNS.Use OCI DNS zone.Create an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.See Use an OCI DNS Management Zone .3.Configure a common custom endpoint for both primary and secondary Oracle Integration instances.Note: If you are using a connectivity agent, you must provision a dedicated connectivity agent for each Oracle Integration instance and use the original instance hostnames in the agents configurations.See Configure a Custom Endpoint .4.Use REST APIs or the Oracle Integration UI to migrate the metadata from the primary to secondary instance for the first time.See Migrate Metadata from the Primary Instance .Chapter 3 Prerequisites 3-3Once you have configured the DR environment by executing these tasks, verify your system end-to-end.Access the custom endpoint and navigate through the Oracle Cloud Infrastructure Console.Configure a Custom Endpoint This procedure allows applications and users to access the same URL.Configure a common custom endpoint for your Oracle Integration instances, so that applications and users can access Oracle Integration with the same URL regardless of which instance is active in the background.To configure a custom endpoint: 1.Choose a custom hostname for your instances and register it with a DNS provider.2.Obtain an SSL certificate from a certificate authority (CA) for your hostname.Note: If you use a hostname certificate whose certificate authority (CA) is not in the Oracle Integration trust store, you must also upload the certificate to your Oracle Integration instance. |
Use OCI DNS zone.Create an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.See Use an OCI DNS Management Zone .3.Configure a common custom endpoint for both primary and secondary Oracle Integration instances.Note: If you are using a connectivity agent, you must provision a dedicated connectivity agent for each Oracle Integration instance and use the original instance hostnames in the agents configurations.See Configure a Custom Endpoint .4.Use REST APIs or the Oracle Integration UI to migrate the metadata from the primary to secondary instance for the first time.See Migrate Metadata from the Primary Instance .Chapter 3 Prerequisites 3-3Once you have configured the DR environment by executing these tasks, verify your system end-to-end.Access the custom endpoint and navigate through the Oracle Cloud Infrastructure Console.Configure a Custom Endpoint This procedure allows applications and users to access the same URL.Configure a common custom endpoint for your Oracle Integration instances, so that applications and users can access Oracle Integration with the same URL regardless of which instance is active in the background.To configure a custom endpoint: 1.Choose a custom hostname for your instances and register it with a DNS provider.2.Obtain an SSL certificate from a certificate authority (CA) for your hostname.Note: If you use a hostname certificate whose certificate authority (CA) is not in the Oracle Integration trust store, you must also upload the certificate to your Oracle Integration instance.See Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 for the full list of tasks. |
Create an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.See Use an OCI DNS Management Zone .3.Configure a common custom endpoint for both primary and secondary Oracle Integration instances.Note: If you are using a connectivity agent, you must provision a dedicated connectivity agent for each Oracle Integration instance and use the original instance hostnames in the agents configurations.See Configure a Custom Endpoint .4.Use REST APIs or the Oracle Integration UI to migrate the metadata from the primary to secondary instance for the first time.See Migrate Metadata from the Primary Instance .Chapter 3 Prerequisites 3-3Once you have configured the DR environment by executing these tasks, verify your system end-to-end.Access the custom endpoint and navigate through the Oracle Cloud Infrastructure Console.Configure a Custom Endpoint This procedure allows applications and users to access the same URL.Configure a common custom endpoint for your Oracle Integration instances, so that applications and users can access Oracle Integration with the same URL regardless of which instance is active in the background.To configure a custom endpoint: 1.Choose a custom hostname for your instances and register it with a DNS provider.2.Obtain an SSL certificate from a certificate authority (CA) for your hostname.Note: If you use a hostname certificate whose certificate authority (CA) is not in the Oracle Integration trust store, you must also upload the certificate to your Oracle Integration instance.See Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 for the full list of tasks.Use an OCI DNS Management Zone Configure DNS records and for your Oracle Integration instances. |
See Use an OCI DNS Management Zone .3.Configure a common custom endpoint for both primary and secondary Oracle Integration instances.Note: If you are using a connectivity agent, you must provision a dedicated connectivity agent for each Oracle Integration instance and use the original instance hostnames in the agents configurations.See Configure a Custom Endpoint .4.Use REST APIs or the Oracle Integration UI to migrate the metadata from the primary to secondary instance for the first time.See Migrate Metadata from the Primary Instance .Chapter 3 Prerequisites 3-3Once you have configured the DR environment by executing these tasks, verify your system end-to-end.Access the custom endpoint and navigate through the Oracle Cloud Infrastructure Console.Configure a Custom Endpoint This procedure allows applications and users to access the same URL.Configure a common custom endpoint for your Oracle Integration instances, so that applications and users can access Oracle Integration with the same URL regardless of which instance is active in the background.To configure a custom endpoint: 1.Choose a custom hostname for your instances and register it with a DNS provider.2.Obtain an SSL certificate from a certificate authority (CA) for your hostname.Note: If you use a hostname certificate whose certificate authority (CA) is not in the Oracle Integration trust store, you must also upload the certificate to your Oracle Integration instance.See Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 for the full list of tasks.Use an OCI DNS Management Zone Configure DNS records and for your Oracle Integration instances.You can use an OCI DNS zone to manage DNS records and provide hostname resolution for your Oracle Integration instances. |
3.Configure a common custom endpoint for both primary and secondary Oracle Integration instances.Note: If you are using a connectivity agent, you must provision a dedicated connectivity agent for each Oracle Integration instance and use the original instance hostnames in the agents configurations.See Configure a Custom Endpoint .4.Use REST APIs or the Oracle Integration UI to migrate the metadata from the primary to secondary instance for the first time.See Migrate Metadata from the Primary Instance .Chapter 3 Prerequisites 3-3Once you have configured the DR environment by executing these tasks, verify your system end-to-end.Access the custom endpoint and navigate through the Oracle Cloud Infrastructure Console.Configure a Custom Endpoint This procedure allows applications and users to access the same URL.Configure a common custom endpoint for your Oracle Integration instances, so that applications and users can access Oracle Integration with the same URL regardless of which instance is active in the background.To configure a custom endpoint: 1.Choose a custom hostname for your instances and register it with a DNS provider.2.Obtain an SSL certificate from a certificate authority (CA) for your hostname.Note: If you use a hostname certificate whose certificate authority (CA) is not in the Oracle Integration trust store, you must also upload the certificate to your Oracle Integration instance.See Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 for the full list of tasks.Use an OCI DNS Management Zone Configure DNS records and for your Oracle Integration instances.You can use an OCI DNS zone to manage DNS records and provide hostname resolution for your Oracle Integration instances.1.After you've acquired a domain (or a sub-domain) for your Oracle Integration instance, add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API. |
Note: If you are using a connectivity agent, you must provision a dedicated connectivity agent for each Oracle Integration instance and use the original instance hostnames in the agents configurations.See Configure a Custom Endpoint .4.Use REST APIs or the Oracle Integration UI to migrate the metadata from the primary to secondary instance for the first time.See Migrate Metadata from the Primary Instance .Chapter 3 Prerequisites 3-3Once you have configured the DR environment by executing these tasks, verify your system end-to-end.Access the custom endpoint and navigate through the Oracle Cloud Infrastructure Console.Configure a Custom Endpoint This procedure allows applications and users to access the same URL.Configure a common custom endpoint for your Oracle Integration instances, so that applications and users can access Oracle Integration with the same URL regardless of which instance is active in the background.To configure a custom endpoint: 1.Choose a custom hostname for your instances and register it with a DNS provider.2.Obtain an SSL certificate from a certificate authority (CA) for your hostname.Note: If you use a hostname certificate whose certificate authority (CA) is not in the Oracle Integration trust store, you must also upload the certificate to your Oracle Integration instance.See Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 for the full list of tasks.Use an OCI DNS Management Zone Configure DNS records and for your Oracle Integration instances.You can use an OCI DNS zone to manage DNS records and provide hostname resolution for your Oracle Integration instances.1.After you've acquired a domain (or a sub-domain) for your Oracle Integration instance, add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.For details on creating an OCI DNS zone and adding a record to it, see Managing DNS Service Zones . |
See Configure a Custom Endpoint .4.Use REST APIs or the Oracle Integration UI to migrate the metadata from the primary to secondary instance for the first time.See Migrate Metadata from the Primary Instance .Chapter 3 Prerequisites 3-3Once you have configured the DR environment by executing these tasks, verify your system end-to-end.Access the custom endpoint and navigate through the Oracle Cloud Infrastructure Console.Configure a Custom Endpoint This procedure allows applications and users to access the same URL.Configure a common custom endpoint for your Oracle Integration instances, so that applications and users can access Oracle Integration with the same URL regardless of which instance is active in the background.To configure a custom endpoint: 1.Choose a custom hostname for your instances and register it with a DNS provider.2.Obtain an SSL certificate from a certificate authority (CA) for your hostname.Note: If you use a hostname certificate whose certificate authority (CA) is not in the Oracle Integration trust store, you must also upload the certificate to your Oracle Integration instance.See Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 for the full list of tasks.Use an OCI DNS Management Zone Configure DNS records and for your Oracle Integration instances.You can use an OCI DNS zone to manage DNS records and provide hostname resolution for your Oracle Integration instances.1.After you've acquired a domain (or a sub-domain) for your Oracle Integration instance, add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.For details on creating an OCI DNS zone and adding a record to it, see Managing DNS Service Zones .The following image shows a sample DNS zone created for the domain named archdevpro.com . |
4.Use REST APIs or the Oracle Integration UI to migrate the metadata from the primary to secondary instance for the first time.See Migrate Metadata from the Primary Instance .Chapter 3 Prerequisites 3-3Once you have configured the DR environment by executing these tasks, verify your system end-to-end.Access the custom endpoint and navigate through the Oracle Cloud Infrastructure Console.Configure a Custom Endpoint This procedure allows applications and users to access the same URL.Configure a common custom endpoint for your Oracle Integration instances, so that applications and users can access Oracle Integration with the same URL regardless of which instance is active in the background.To configure a custom endpoint: 1.Choose a custom hostname for your instances and register it with a DNS provider.2.Obtain an SSL certificate from a certificate authority (CA) for your hostname.Note: If you use a hostname certificate whose certificate authority (CA) is not in the Oracle Integration trust store, you must also upload the certificate to your Oracle Integration instance.See Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 for the full list of tasks.Use an OCI DNS Management Zone Configure DNS records and for your Oracle Integration instances.You can use an OCI DNS zone to manage DNS records and provide hostname resolution for your Oracle Integration instances.1.After you've acquired a domain (or a sub-domain) for your Oracle Integration instance, add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.For details on creating an OCI DNS zone and adding a record to it, see Managing DNS Service Zones .The following image shows a sample DNS zone created for the domain named archdevpro.com .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-42.In the zone, add the Oracle Integration custom hostname as a CNAME record. |
See Migrate Metadata from the Primary Instance .Chapter 3 Prerequisites 3-3Once you have configured the DR environment by executing these tasks, verify your system end-to-end.Access the custom endpoint and navigate through the Oracle Cloud Infrastructure Console.Configure a Custom Endpoint This procedure allows applications and users to access the same URL.Configure a common custom endpoint for your Oracle Integration instances, so that applications and users can access Oracle Integration with the same URL regardless of which instance is active in the background.To configure a custom endpoint: 1.Choose a custom hostname for your instances and register it with a DNS provider.2.Obtain an SSL certificate from a certificate authority (CA) for your hostname.Note: If you use a hostname certificate whose certificate authority (CA) is not in the Oracle Integration trust store, you must also upload the certificate to your Oracle Integration instance.See Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 for the full list of tasks.Use an OCI DNS Management Zone Configure DNS records and for your Oracle Integration instances.You can use an OCI DNS zone to manage DNS records and provide hostname resolution for your Oracle Integration instances.1.After you've acquired a domain (or a sub-domain) for your Oracle Integration instance, add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.For details on creating an OCI DNS zone and adding a record to it, see Managing DNS Service Zones .The following image shows a sample DNS zone created for the domain named archdevpro.com .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-42.In the zone, add the Oracle Integration custom hostname as a CNAME record.3.After you've successfully published the above changes, update your domain to use the OCI DNS nameservers. |
Access the custom endpoint and navigate through the Oracle Cloud Infrastructure Console.Configure a Custom Endpoint This procedure allows applications and users to access the same URL.Configure a common custom endpoint for your Oracle Integration instances, so that applications and users can access Oracle Integration with the same URL regardless of which instance is active in the background.To configure a custom endpoint: 1.Choose a custom hostname for your instances and register it with a DNS provider.2.Obtain an SSL certificate from a certificate authority (CA) for your hostname.Note: If you use a hostname certificate whose certificate authority (CA) is not in the Oracle Integration trust store, you must also upload the certificate to your Oracle Integration instance.See Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 for the full list of tasks.Use an OCI DNS Management Zone Configure DNS records and for your Oracle Integration instances.You can use an OCI DNS zone to manage DNS records and provide hostname resolution for your Oracle Integration instances.1.After you've acquired a domain (or a sub-domain) for your Oracle Integration instance, add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.For details on creating an OCI DNS zone and adding a record to it, see Managing DNS Service Zones .The following image shows a sample DNS zone created for the domain named archdevpro.com .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-42.In the zone, add the Oracle Integration custom hostname as a CNAME record.3.After you've successfully published the above changes, update your domain to use the OCI DNS nameservers.Migrate Metadata from the Primary Instance Export the metadata from the primary instance to the standby instance. |
Configure a Custom Endpoint This procedure allows applications and users to access the same URL.Configure a common custom endpoint for your Oracle Integration instances, so that applications and users can access Oracle Integration with the same URL regardless of which instance is active in the background.To configure a custom endpoint: 1.Choose a custom hostname for your instances and register it with a DNS provider.2.Obtain an SSL certificate from a certificate authority (CA) for your hostname.Note: If you use a hostname certificate whose certificate authority (CA) is not in the Oracle Integration trust store, you must also upload the certificate to your Oracle Integration instance.See Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 for the full list of tasks.Use an OCI DNS Management Zone Configure DNS records and for your Oracle Integration instances.You can use an OCI DNS zone to manage DNS records and provide hostname resolution for your Oracle Integration instances.1.After you've acquired a domain (or a sub-domain) for your Oracle Integration instance, add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.For details on creating an OCI DNS zone and adding a record to it, see Managing DNS Service Zones .The following image shows a sample DNS zone created for the domain named archdevpro.com .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-42.In the zone, add the Oracle Integration custom hostname as a CNAME record.3.After you've successfully published the above changes, update your domain to use the OCI DNS nameservers.Migrate Metadata from the Primary Instance Export the metadata from the primary instance to the standby instance.The Oracle Integration metadata consists of connections, integrations, lookups, libraries, and packages. |
Configure a common custom endpoint for your Oracle Integration instances, so that applications and users can access Oracle Integration with the same URL regardless of which instance is active in the background.To configure a custom endpoint: 1.Choose a custom hostname for your instances and register it with a DNS provider.2.Obtain an SSL certificate from a certificate authority (CA) for your hostname.Note: If you use a hostname certificate whose certificate authority (CA) is not in the Oracle Integration trust store, you must also upload the certificate to your Oracle Integration instance.See Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 for the full list of tasks.Use an OCI DNS Management Zone Configure DNS records and for your Oracle Integration instances.You can use an OCI DNS zone to manage DNS records and provide hostname resolution for your Oracle Integration instances.1.After you've acquired a domain (or a sub-domain) for your Oracle Integration instance, add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.For details on creating an OCI DNS zone and adding a record to it, see Managing DNS Service Zones .The following image shows a sample DNS zone created for the domain named archdevpro.com .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-42.In the zone, add the Oracle Integration custom hostname as a CNAME record.3.After you've successfully published the above changes, update your domain to use the OCI DNS nameservers.Migrate Metadata from the Primary Instance Export the metadata from the primary instance to the standby instance.The Oracle Integration metadata consists of connections, integrations, lookups, libraries, and packages.After youve configured the primary instance with all your integration deployments, you can export the metadata from the instance and import it into the standby instance. |
To configure a custom endpoint: 1.Choose a custom hostname for your instances and register it with a DNS provider.2.Obtain an SSL certificate from a certificate authority (CA) for your hostname.Note: If you use a hostname certificate whose certificate authority (CA) is not in the Oracle Integration trust store, you must also upload the certificate to your Oracle Integration instance.See Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 for the full list of tasks.Use an OCI DNS Management Zone Configure DNS records and for your Oracle Integration instances.You can use an OCI DNS zone to manage DNS records and provide hostname resolution for your Oracle Integration instances.1.After you've acquired a domain (or a sub-domain) for your Oracle Integration instance, add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.For details on creating an OCI DNS zone and adding a record to it, see Managing DNS Service Zones .The following image shows a sample DNS zone created for the domain named archdevpro.com .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-42.In the zone, add the Oracle Integration custom hostname as a CNAME record.3.After you've successfully published the above changes, update your domain to use the OCI DNS nameservers.Migrate Metadata from the Primary Instance Export the metadata from the primary instance to the standby instance.The Oracle Integration metadata consists of connections, integrations, lookups, libraries, and packages.After youve configured the primary instance with all your integration deployments, you can export the metadata from the instance and import it into the standby instance.This as an initial, one-time task. |
2.Obtain an SSL certificate from a certificate authority (CA) for your hostname.Note: If you use a hostname certificate whose certificate authority (CA) is not in the Oracle Integration trust store, you must also upload the certificate to your Oracle Integration instance.See Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 for the full list of tasks.Use an OCI DNS Management Zone Configure DNS records and for your Oracle Integration instances.You can use an OCI DNS zone to manage DNS records and provide hostname resolution for your Oracle Integration instances.1.After you've acquired a domain (or a sub-domain) for your Oracle Integration instance, add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.For details on creating an OCI DNS zone and adding a record to it, see Managing DNS Service Zones .The following image shows a sample DNS zone created for the domain named archdevpro.com .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-42.In the zone, add the Oracle Integration custom hostname as a CNAME record.3.After you've successfully published the above changes, update your domain to use the OCI DNS nameservers.Migrate Metadata from the Primary Instance Export the metadata from the primary instance to the standby instance.The Oracle Integration metadata consists of connections, integrations, lookups, libraries, and packages.After youve configured the primary instance with all your integration deployments, you can export the metadata from the instance and import it into the standby instance.This as an initial, one-time task.You can export the metadata using any one of the following methods: Use REST APIs to export the metadata and import the same. |
Note: If you use a hostname certificate whose certificate authority (CA) is not in the Oracle Integration trust store, you must also upload the certificate to your Oracle Integration instance.See Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 for the full list of tasks.Use an OCI DNS Management Zone Configure DNS records and for your Oracle Integration instances.You can use an OCI DNS zone to manage DNS records and provide hostname resolution for your Oracle Integration instances.1.After you've acquired a domain (or a sub-domain) for your Oracle Integration instance, add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.For details on creating an OCI DNS zone and adding a record to it, see Managing DNS Service Zones .The following image shows a sample DNS zone created for the domain named archdevpro.com .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-42.In the zone, add the Oracle Integration custom hostname as a CNAME record.3.After you've successfully published the above changes, update your domain to use the OCI DNS nameservers.Migrate Metadata from the Primary Instance Export the metadata from the primary instance to the standby instance.The Oracle Integration metadata consists of connections, integrations, lookups, libraries, and packages.After youve configured the primary instance with all your integration deployments, you can export the metadata from the instance and import it into the standby instance.This as an initial, one-time task.You can export the metadata using any one of the following methods: Use REST APIs to export the metadata and import the same.Use the Oracle Integration UI to export and import the metadata. |
See Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 for the full list of tasks.Use an OCI DNS Management Zone Configure DNS records and for your Oracle Integration instances.You can use an OCI DNS zone to manage DNS records and provide hostname resolution for your Oracle Integration instances.1.After you've acquired a domain (or a sub-domain) for your Oracle Integration instance, add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.For details on creating an OCI DNS zone and adding a record to it, see Managing DNS Service Zones .The following image shows a sample DNS zone created for the domain named archdevpro.com .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-42.In the zone, add the Oracle Integration custom hostname as a CNAME record.3.After you've successfully published the above changes, update your domain to use the OCI DNS nameservers.Migrate Metadata from the Primary Instance Export the metadata from the primary instance to the standby instance.The Oracle Integration metadata consists of connections, integrations, lookups, libraries, and packages.After youve configured the primary instance with all your integration deployments, you can export the metadata from the instance and import it into the standby instance.This as an initial, one-time task.You can export the metadata using any one of the following methods: Use REST APIs to export the metadata and import the same.Use the Oracle Integration UI to export and import the metadata.For details, see Export and Import Design-Time Metadata Between Instances in Provisioning and Administering Oracle Integration Generation 2 . |
Use an OCI DNS Management Zone Configure DNS records and for your Oracle Integration instances.You can use an OCI DNS zone to manage DNS records and provide hostname resolution for your Oracle Integration instances.1.After you've acquired a domain (or a sub-domain) for your Oracle Integration instance, add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.For details on creating an OCI DNS zone and adding a record to it, see Managing DNS Service Zones .The following image shows a sample DNS zone created for the domain named archdevpro.com .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-42.In the zone, add the Oracle Integration custom hostname as a CNAME record.3.After you've successfully published the above changes, update your domain to use the OCI DNS nameservers.Migrate Metadata from the Primary Instance Export the metadata from the primary instance to the standby instance.The Oracle Integration metadata consists of connections, integrations, lookups, libraries, and packages.After youve configured the primary instance with all your integration deployments, you can export the metadata from the instance and import it into the standby instance.This as an initial, one-time task.You can export the metadata using any one of the following methods: Use REST APIs to export the metadata and import the same.Use the Oracle Integration UI to export and import the metadata.For details, see Export and Import Design-Time Metadata Between Instances in Provisioning and Administering Oracle Integration Generation 2 .Note: Before you use either of the preceding methods, you require an OCI Object Storage bucket to store the artifacts. |
You can use an OCI DNS zone to manage DNS records and provide hostname resolution for your Oracle Integration instances.1.After you've acquired a domain (or a sub-domain) for your Oracle Integration instance, add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.For details on creating an OCI DNS zone and adding a record to it, see Managing DNS Service Zones .The following image shows a sample DNS zone created for the domain named archdevpro.com .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-42.In the zone, add the Oracle Integration custom hostname as a CNAME record.3.After you've successfully published the above changes, update your domain to use the OCI DNS nameservers.Migrate Metadata from the Primary Instance Export the metadata from the primary instance to the standby instance.The Oracle Integration metadata consists of connections, integrations, lookups, libraries, and packages.After youve configured the primary instance with all your integration deployments, you can export the metadata from the instance and import it into the standby instance.This as an initial, one-time task.You can export the metadata using any one of the following methods: Use REST APIs to export the metadata and import the same.Use the Oracle Integration UI to export and import the metadata.For details, see Export and Import Design-Time Metadata Between Instances in Provisioning and Administering Oracle Integration Generation 2 .Note: Before you use either of the preceding methods, you require an OCI Object Storage bucket to store the artifacts.Subsequently, you can employ continuous integration continuous deployment (CICD) to have the metadata synchronized between instances. |
1.After you've acquired a domain (or a sub-domain) for your Oracle Integration instance, add an OCI DNS zone through the Oracle Cloud Infrastructure Console or the API.For details on creating an OCI DNS zone and adding a record to it, see Managing DNS Service Zones .The following image shows a sample DNS zone created for the domain named archdevpro.com .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-42.In the zone, add the Oracle Integration custom hostname as a CNAME record.3.After you've successfully published the above changes, update your domain to use the OCI DNS nameservers.Migrate Metadata from the Primary Instance Export the metadata from the primary instance to the standby instance.The Oracle Integration metadata consists of connections, integrations, lookups, libraries, and packages.After youve configured the primary instance with all your integration deployments, you can export the metadata from the instance and import it into the standby instance.This as an initial, one-time task.You can export the metadata using any one of the following methods: Use REST APIs to export the metadata and import the same.Use the Oracle Integration UI to export and import the metadata.For details, see Export and Import Design-Time Metadata Between Instances in Provisioning and Administering Oracle Integration Generation 2 .Note: Before you use either of the preceding methods, you require an OCI Object Storage bucket to store the artifacts.Subsequently, you can employ continuous integration continuous deployment (CICD) to have the metadata synchronized between instances.See Automate Metadata Synchronization .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-5Note: You must use the original instance hostnames for all administrative tasks, including metadata migration. |
For details on creating an OCI DNS zone and adding a record to it, see Managing DNS Service Zones .The following image shows a sample DNS zone created for the domain named archdevpro.com .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-42.In the zone, add the Oracle Integration custom hostname as a CNAME record.3.After you've successfully published the above changes, update your domain to use the OCI DNS nameservers.Migrate Metadata from the Primary Instance Export the metadata from the primary instance to the standby instance.The Oracle Integration metadata consists of connections, integrations, lookups, libraries, and packages.After youve configured the primary instance with all your integration deployments, you can export the metadata from the instance and import it into the standby instance.This as an initial, one-time task.You can export the metadata using any one of the following methods: Use REST APIs to export the metadata and import the same.Use the Oracle Integration UI to export and import the metadata.For details, see Export and Import Design-Time Metadata Between Instances in Provisioning and Administering Oracle Integration Generation 2 .Note: Before you use either of the preceding methods, you require an OCI Object Storage bucket to store the artifacts.Subsequently, you can employ continuous integration continuous deployment (CICD) to have the metadata synchronized between instances.See Automate Metadata Synchronization .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-5Note: You must use the original instance hostnames for all administrative tasks, including metadata migration.Its recommended that you import the artifacts without activating them so that the connections created in the secondary instance will not be in the Activated state. |
The following image shows a sample DNS zone created for the domain named archdevpro.com .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-42.In the zone, add the Oracle Integration custom hostname as a CNAME record.3.After you've successfully published the above changes, update your domain to use the OCI DNS nameservers.Migrate Metadata from the Primary Instance Export the metadata from the primary instance to the standby instance.The Oracle Integration metadata consists of connections, integrations, lookups, libraries, and packages.After youve configured the primary instance with all your integration deployments, you can export the metadata from the instance and import it into the standby instance.This as an initial, one-time task.You can export the metadata using any one of the following methods: Use REST APIs to export the metadata and import the same.Use the Oracle Integration UI to export and import the metadata.For details, see Export and Import Design-Time Metadata Between Instances in Provisioning and Administering Oracle Integration Generation 2 .Note: Before you use either of the preceding methods, you require an OCI Object Storage bucket to store the artifacts.Subsequently, you can employ continuous integration continuous deployment (CICD) to have the metadata synchronized between instances.See Automate Metadata Synchronization .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-5Note: You must use the original instance hostnames for all administrative tasks, including metadata migration.Its recommended that you import the artifacts without activating them so that the connections created in the secondary instance will not be in the Activated state.Once you have imported the artifacts, you can manually test the connections and activate them. |
Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-42.In the zone, add the Oracle Integration custom hostname as a CNAME record.3.After you've successfully published the above changes, update your domain to use the OCI DNS nameservers.Migrate Metadata from the Primary Instance Export the metadata from the primary instance to the standby instance.The Oracle Integration metadata consists of connections, integrations, lookups, libraries, and packages.After youve configured the primary instance with all your integration deployments, you can export the metadata from the instance and import it into the standby instance.This as an initial, one-time task.You can export the metadata using any one of the following methods: Use REST APIs to export the metadata and import the same.Use the Oracle Integration UI to export and import the metadata.For details, see Export and Import Design-Time Metadata Between Instances in Provisioning and Administering Oracle Integration Generation 2 .Note: Before you use either of the preceding methods, you require an OCI Object Storage bucket to store the artifacts.Subsequently, you can employ continuous integration continuous deployment (CICD) to have the metadata synchronized between instances.See Automate Metadata Synchronization .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-5Note: You must use the original instance hostnames for all administrative tasks, including metadata migration.Its recommended that you import the artifacts without activating them so that the connections created in the secondary instance will not be in the Activated state.Once you have imported the artifacts, you can manually test the connections and activate them.Else, you can also use Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the same. |
3.After you've successfully published the above changes, update your domain to use the OCI DNS nameservers.Migrate Metadata from the Primary Instance Export the metadata from the primary instance to the standby instance.The Oracle Integration metadata consists of connections, integrations, lookups, libraries, and packages.After youve configured the primary instance with all your integration deployments, you can export the metadata from the instance and import it into the standby instance.This as an initial, one-time task.You can export the metadata using any one of the following methods: Use REST APIs to export the metadata and import the same.Use the Oracle Integration UI to export and import the metadata.For details, see Export and Import Design-Time Metadata Between Instances in Provisioning and Administering Oracle Integration Generation 2 .Note: Before you use either of the preceding methods, you require an OCI Object Storage bucket to store the artifacts.Subsequently, you can employ continuous integration continuous deployment (CICD) to have the metadata synchronized between instances.See Automate Metadata Synchronization .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-5Note: You must use the original instance hostnames for all administrative tasks, including metadata migration.Its recommended that you import the artifacts without activating them so that the connections created in the secondary instance will not be in the Activated state.Once you have imported the artifacts, you can manually test the connections and activate them.Else, you can also use Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the same.To synchronize the metadata between the instances using REST APIs: 1.Export the metadata from the primary instance. |
Migrate Metadata from the Primary Instance Export the metadata from the primary instance to the standby instance.The Oracle Integration metadata consists of connections, integrations, lookups, libraries, and packages.After youve configured the primary instance with all your integration deployments, you can export the metadata from the instance and import it into the standby instance.This as an initial, one-time task.You can export the metadata using any one of the following methods: Use REST APIs to export the metadata and import the same.Use the Oracle Integration UI to export and import the metadata.For details, see Export and Import Design-Time Metadata Between Instances in Provisioning and Administering Oracle Integration Generation 2 .Note: Before you use either of the preceding methods, you require an OCI Object Storage bucket to store the artifacts.Subsequently, you can employ continuous integration continuous deployment (CICD) to have the metadata synchronized between instances.See Automate Metadata Synchronization .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-5Note: You must use the original instance hostnames for all administrative tasks, including metadata migration.Its recommended that you import the artifacts without activating them so that the connections created in the secondary instance will not be in the Activated state.Once you have imported the artifacts, you can manually test the connections and activate them.Else, you can also use Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the same.To synchronize the metadata between the instances using REST APIs: 1.Export the metadata from the primary instance.Invoke the REST API using the following postman or curl command. |
The Oracle Integration metadata consists of connections, integrations, lookups, libraries, and packages.After youve configured the primary instance with all your integration deployments, you can export the metadata from the instance and import it into the standby instance.This as an initial, one-time task.You can export the metadata using any one of the following methods: Use REST APIs to export the metadata and import the same.Use the Oracle Integration UI to export and import the metadata.For details, see Export and Import Design-Time Metadata Between Instances in Provisioning and Administering Oracle Integration Generation 2 .Note: Before you use either of the preceding methods, you require an OCI Object Storage bucket to store the artifacts.Subsequently, you can employ continuous integration continuous deployment (CICD) to have the metadata synchronized between instances.See Automate Metadata Synchronization .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-5Note: You must use the original instance hostnames for all administrative tasks, including metadata migration.Its recommended that you import the artifacts without activating them so that the connections created in the secondary instance will not be in the Activated state.Once you have imported the artifacts, you can manually test the connections and activate them.Else, you can also use Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the same.To synchronize the metadata between the instances using REST APIs: 1.Export the metadata from the primary instance.Invoke the REST API using the following postman or curl command.This action uploads the metadata to the OCI Object Storage Cloud Service bucket instance. |
After youve configured the primary instance with all your integration deployments, you can export the metadata from the instance and import it into the standby instance.This as an initial, one-time task.You can export the metadata using any one of the following methods: Use REST APIs to export the metadata and import the same.Use the Oracle Integration UI to export and import the metadata.For details, see Export and Import Design-Time Metadata Between Instances in Provisioning and Administering Oracle Integration Generation 2 .Note: Before you use either of the preceding methods, you require an OCI Object Storage bucket to store the artifacts.Subsequently, you can employ continuous integration continuous deployment (CICD) to have the metadata synchronized between instances.See Automate Metadata Synchronization .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-5Note: You must use the original instance hostnames for all administrative tasks, including metadata migration.Its recommended that you import the artifacts without activating them so that the connections created in the secondary instance will not be in the Activated state.Once you have imported the artifacts, you can manually test the connections and activate them.Else, you can also use Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the same.To synchronize the metadata between the instances using REST APIs: 1.Export the metadata from the primary instance.Invoke the REST API using the following postman or curl command.This action uploads the metadata to the OCI Object Storage Cloud Service bucket instance.POST http:/host:port/ic/api/common/v1/exportServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "jobName":"Pod1_Metadata" - If jobName is omitted filename will default to "archive_Local_Suite_Instance-<jobId>.zip", "overwrite":false, - defaults to false, will return error if archive file already exists "exportSecurityArtifacts":true, "exportAppRoleMembers":true, "description":"Export description", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"<OCI user name>", "storagePassword":"<Auth Password> } } Response Headers: Location http://host:port/ic/api/common/v1/ exportServiceInstanceArchive/483Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-6Response Payload: { jobId: 483, location: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/<bucket name>, status: NOT_STARTED } Response Status: 202 Accepted Export job was accepted. |
This as an initial, one-time task.You can export the metadata using any one of the following methods: Use REST APIs to export the metadata and import the same.Use the Oracle Integration UI to export and import the metadata.For details, see Export and Import Design-Time Metadata Between Instances in Provisioning and Administering Oracle Integration Generation 2 .Note: Before you use either of the preceding methods, you require an OCI Object Storage bucket to store the artifacts.Subsequently, you can employ continuous integration continuous deployment (CICD) to have the metadata synchronized between instances.See Automate Metadata Synchronization .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-5Note: You must use the original instance hostnames for all administrative tasks, including metadata migration.Its recommended that you import the artifacts without activating them so that the connections created in the secondary instance will not be in the Activated state.Once you have imported the artifacts, you can manually test the connections and activate them.Else, you can also use Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the same.To synchronize the metadata between the instances using REST APIs: 1.Export the metadata from the primary instance.Invoke the REST API using the following postman or curl command.This action uploads the metadata to the OCI Object Storage Cloud Service bucket instance.POST http:/host:port/ic/api/common/v1/exportServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "jobName":"Pod1_Metadata" - If jobName is omitted filename will default to "archive_Local_Suite_Instance-<jobId>.zip", "overwrite":false, - defaults to false, will return error if archive file already exists "exportSecurityArtifacts":true, "exportAppRoleMembers":true, "description":"Export description", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"<OCI user name>", "storagePassword":"<Auth Password> } } Response Headers: Location http://host:port/ic/api/common/v1/ exportServiceInstanceArchive/483Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-6Response Payload: { jobId: 483, location: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/<bucket name>, status: NOT_STARTED } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/ missing, or the file already exists (if overwrite is set to false ). |
You can export the metadata using any one of the following methods: Use REST APIs to export the metadata and import the same.Use the Oracle Integration UI to export and import the metadata.For details, see Export and Import Design-Time Metadata Between Instances in Provisioning and Administering Oracle Integration Generation 2 .Note: Before you use either of the preceding methods, you require an OCI Object Storage bucket to store the artifacts.Subsequently, you can employ continuous integration continuous deployment (CICD) to have the metadata synchronized between instances.See Automate Metadata Synchronization .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-5Note: You must use the original instance hostnames for all administrative tasks, including metadata migration.Its recommended that you import the artifacts without activating them so that the connections created in the secondary instance will not be in the Activated state.Once you have imported the artifacts, you can manually test the connections and activate them.Else, you can also use Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the same.To synchronize the metadata between the instances using REST APIs: 1.Export the metadata from the primary instance.Invoke the REST API using the following postman or curl command.This action uploads the metadata to the OCI Object Storage Cloud Service bucket instance.POST http:/host:port/ic/api/common/v1/exportServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "jobName":"Pod1_Metadata" - If jobName is omitted filename will default to "archive_Local_Suite_Instance-<jobId>.zip", "overwrite":false, - defaults to false, will return error if archive file already exists "exportSecurityArtifacts":true, "exportAppRoleMembers":true, "description":"Export description", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"<OCI user name>", "storagePassword":"<Auth Password> } } Response Headers: Location http://host:port/ic/api/common/v1/ exportServiceInstanceArchive/483Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-6Response Payload: { jobId: 483, location: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/<bucket name>, status: NOT_STARTED } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/ missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage. |
Use the Oracle Integration UI to export and import the metadata.For details, see Export and Import Design-Time Metadata Between Instances in Provisioning and Administering Oracle Integration Generation 2 .Note: Before you use either of the preceding methods, you require an OCI Object Storage bucket to store the artifacts.Subsequently, you can employ continuous integration continuous deployment (CICD) to have the metadata synchronized between instances.See Automate Metadata Synchronization .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-5Note: You must use the original instance hostnames for all administrative tasks, including metadata migration.Its recommended that you import the artifacts without activating them so that the connections created in the secondary instance will not be in the Activated state.Once you have imported the artifacts, you can manually test the connections and activate them.Else, you can also use Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the same.To synchronize the metadata between the instances using REST APIs: 1.Export the metadata from the primary instance.Invoke the REST API using the following postman or curl command.This action uploads the metadata to the OCI Object Storage Cloud Service bucket instance.POST http:/host:port/ic/api/common/v1/exportServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "jobName":"Pod1_Metadata" - If jobName is omitted filename will default to "archive_Local_Suite_Instance-<jobId>.zip", "overwrite":false, - defaults to false, will return error if archive file already exists "exportSecurityArtifacts":true, "exportAppRoleMembers":true, "description":"Export description", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"<OCI user name>", "storagePassword":"<Auth Password> } } Response Headers: Location http://host:port/ic/api/common/v1/ exportServiceInstanceArchive/483Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-6Response Payload: { jobId: 483, location: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/<bucket name>, status: NOT_STARTED } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/ missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.2.Check the status of the export operation using the following command: GET http://host:port/ic/api/common/v1/exportServiceInstanceArchive/{jobId} If the status is Completed , the metadata has been successfully exported to the object storage bucket. |
For details, see Export and Import Design-Time Metadata Between Instances in Provisioning and Administering Oracle Integration Generation 2 .Note: Before you use either of the preceding methods, you require an OCI Object Storage bucket to store the artifacts.Subsequently, you can employ continuous integration continuous deployment (CICD) to have the metadata synchronized between instances.See Automate Metadata Synchronization .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-5Note: You must use the original instance hostnames for all administrative tasks, including metadata migration.Its recommended that you import the artifacts without activating them so that the connections created in the secondary instance will not be in the Activated state.Once you have imported the artifacts, you can manually test the connections and activate them.Else, you can also use Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the same.To synchronize the metadata between the instances using REST APIs: 1.Export the metadata from the primary instance.Invoke the REST API using the following postman or curl command.This action uploads the metadata to the OCI Object Storage Cloud Service bucket instance.POST http:/host:port/ic/api/common/v1/exportServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "jobName":"Pod1_Metadata" - If jobName is omitted filename will default to "archive_Local_Suite_Instance-<jobId>.zip", "overwrite":false, - defaults to false, will return error if archive file already exists "exportSecurityArtifacts":true, "exportAppRoleMembers":true, "description":"Export description", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"<OCI user name>", "storagePassword":"<Auth Password> } } Response Headers: Location http://host:port/ic/api/common/v1/ exportServiceInstanceArchive/483Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-6Response Payload: { jobId: 483, location: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/<bucket name>, status: NOT_STARTED } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/ missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.2.Check the status of the export operation using the following command: GET http://host:port/ic/api/common/v1/exportServiceInstanceArchive/{jobId} If the status is Completed , the metadata has been successfully exported to the object storage bucket.3.Now, import the metadata into the standby instance. |
Note: Before you use either of the preceding methods, you require an OCI Object Storage bucket to store the artifacts.Subsequently, you can employ continuous integration continuous deployment (CICD) to have the metadata synchronized between instances.See Automate Metadata Synchronization .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-5Note: You must use the original instance hostnames for all administrative tasks, including metadata migration.Its recommended that you import the artifacts without activating them so that the connections created in the secondary instance will not be in the Activated state.Once you have imported the artifacts, you can manually test the connections and activate them.Else, you can also use Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the same.To synchronize the metadata between the instances using REST APIs: 1.Export the metadata from the primary instance.Invoke the REST API using the following postman or curl command.This action uploads the metadata to the OCI Object Storage Cloud Service bucket instance.POST http:/host:port/ic/api/common/v1/exportServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "jobName":"Pod1_Metadata" - If jobName is omitted filename will default to "archive_Local_Suite_Instance-<jobId>.zip", "overwrite":false, - defaults to false, will return error if archive file already exists "exportSecurityArtifacts":true, "exportAppRoleMembers":true, "description":"Export description", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"<OCI user name>", "storagePassword":"<Auth Password> } } Response Headers: Location http://host:port/ic/api/common/v1/ exportServiceInstanceArchive/483Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-6Response Payload: { jobId: 483, location: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/<bucket name>, status: NOT_STARTED } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/ missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.2.Check the status of the export operation using the following command: GET http://host:port/ic/api/common/v1/exportServiceInstanceArchive/{jobId} If the status is Completed , the metadata has been successfully exported to the object storage bucket.3.Now, import the metadata into the standby instance.Invoke the REST API using the following postman or curl command. |
Subsequently, you can employ continuous integration continuous deployment (CICD) to have the metadata synchronized between instances.See Automate Metadata Synchronization .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-5Note: You must use the original instance hostnames for all administrative tasks, including metadata migration.Its recommended that you import the artifacts without activating them so that the connections created in the secondary instance will not be in the Activated state.Once you have imported the artifacts, you can manually test the connections and activate them.Else, you can also use Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the same.To synchronize the metadata between the instances using REST APIs: 1.Export the metadata from the primary instance.Invoke the REST API using the following postman or curl command.This action uploads the metadata to the OCI Object Storage Cloud Service bucket instance.POST http:/host:port/ic/api/common/v1/exportServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "jobName":"Pod1_Metadata" - If jobName is omitted filename will default to "archive_Local_Suite_Instance-<jobId>.zip", "overwrite":false, - defaults to false, will return error if archive file already exists "exportSecurityArtifacts":true, "exportAppRoleMembers":true, "description":"Export description", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"<OCI user name>", "storagePassword":"<Auth Password> } } Response Headers: Location http://host:port/ic/api/common/v1/ exportServiceInstanceArchive/483Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-6Response Payload: { jobId: 483, location: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/<bucket name>, status: NOT_STARTED } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/ missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.2.Check the status of the export operation using the following command: GET http://host:port/ic/api/common/v1/exportServiceInstanceArchive/{jobId} If the status is Completed , the metadata has been successfully exported to the object storage bucket.3.Now, import the metadata into the standby instance.Invoke the REST API using the following postman or curl command.This action retrieves the archive from the OCI Object Storage Cloud Service bucket instance where the archive was initially created. |
See Automate Metadata Synchronization .Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-5Note: You must use the original instance hostnames for all administrative tasks, including metadata migration.Its recommended that you import the artifacts without activating them so that the connections created in the secondary instance will not be in the Activated state.Once you have imported the artifacts, you can manually test the connections and activate them.Else, you can also use Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the same.To synchronize the metadata between the instances using REST APIs: 1.Export the metadata from the primary instance.Invoke the REST API using the following postman or curl command.This action uploads the metadata to the OCI Object Storage Cloud Service bucket instance.POST http:/host:port/ic/api/common/v1/exportServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "jobName":"Pod1_Metadata" - If jobName is omitted filename will default to "archive_Local_Suite_Instance-<jobId>.zip", "overwrite":false, - defaults to false, will return error if archive file already exists "exportSecurityArtifacts":true, "exportAppRoleMembers":true, "description":"Export description", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"<OCI user name>", "storagePassword":"<Auth Password> } } Response Headers: Location http://host:port/ic/api/common/v1/ exportServiceInstanceArchive/483Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-6Response Payload: { jobId: 483, location: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/<bucket name>, status: NOT_STARTED } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/ missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.2.Check the status of the export operation using the following command: GET http://host:port/ic/api/common/v1/exportServiceInstanceArchive/{jobId} If the status is Completed , the metadata has been successfully exported to the object storage bucket.3.Now, import the metadata into the standby instance.Invoke the REST API using the following postman or curl command.This action retrieves the archive from the OCI Object Storage Cloud Service bucket instance where the archive was initially created.POST http://host:port/ic/api/common/v1/importServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "archiveFile":"archive_Local_Suite_Instance-483.zip", "importActivateMode":"importOnly", // ImportOnly | ImportActivate | ActivateOnly | StartSchedulesOnly "importSecurityArtifacts":true, "importAppRoleMembers":true, "importScheduleParams":true, "startSchedules":false, "description":"Import to standby", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"OCI cloud user name", Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-7 "storagePassword":Auth password" } } Note: Set the importActivateMode variable to ImportOnly , so that the integration flows are imported but aren't activated. |
Its recommended that you import the artifacts without activating them so that the connections created in the secondary instance will not be in the Activated state.Once you have imported the artifacts, you can manually test the connections and activate them.Else, you can also use Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the same.To synchronize the metadata between the instances using REST APIs: 1.Export the metadata from the primary instance.Invoke the REST API using the following postman or curl command.This action uploads the metadata to the OCI Object Storage Cloud Service bucket instance.POST http:/host:port/ic/api/common/v1/exportServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "jobName":"Pod1_Metadata" - If jobName is omitted filename will default to "archive_Local_Suite_Instance-<jobId>.zip", "overwrite":false, - defaults to false, will return error if archive file already exists "exportSecurityArtifacts":true, "exportAppRoleMembers":true, "description":"Export description", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"<OCI user name>", "storagePassword":"<Auth Password> } } Response Headers: Location http://host:port/ic/api/common/v1/ exportServiceInstanceArchive/483Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-6Response Payload: { jobId: 483, location: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/<bucket name>, status: NOT_STARTED } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/ missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.2.Check the status of the export operation using the following command: GET http://host:port/ic/api/common/v1/exportServiceInstanceArchive/{jobId} If the status is Completed , the metadata has been successfully exported to the object storage bucket.3.Now, import the metadata into the standby instance.Invoke the REST API using the following postman or curl command.This action retrieves the archive from the OCI Object Storage Cloud Service bucket instance where the archive was initially created.POST http://host:port/ic/api/common/v1/importServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "archiveFile":"archive_Local_Suite_Instance-483.zip", "importActivateMode":"importOnly", // ImportOnly | ImportActivate | ActivateOnly | StartSchedulesOnly "importSecurityArtifacts":true, "importAppRoleMembers":true, "importScheduleParams":true, "startSchedules":false, "description":"Import to standby", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"OCI cloud user name", Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-7 "storagePassword":Auth password" } } Note: Set the importActivateMode variable to ImportOnly , so that the integration flows are imported but aren't activated.Response Payload: { "jobId": "457", "status": "NOT_STARTED" } Response Status: 202 Accepted Export job was accepted. |
Once you have imported the artifacts, you can manually test the connections and activate them.Else, you can also use Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the same.To synchronize the metadata between the instances using REST APIs: 1.Export the metadata from the primary instance.Invoke the REST API using the following postman or curl command.This action uploads the metadata to the OCI Object Storage Cloud Service bucket instance.POST http:/host:port/ic/api/common/v1/exportServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "jobName":"Pod1_Metadata" - If jobName is omitted filename will default to "archive_Local_Suite_Instance-<jobId>.zip", "overwrite":false, - defaults to false, will return error if archive file already exists "exportSecurityArtifacts":true, "exportAppRoleMembers":true, "description":"Export description", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"<OCI user name>", "storagePassword":"<Auth Password> } } Response Headers: Location http://host:port/ic/api/common/v1/ exportServiceInstanceArchive/483Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-6Response Payload: { jobId: 483, location: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/<bucket name>, status: NOT_STARTED } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/ missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.2.Check the status of the export operation using the following command: GET http://host:port/ic/api/common/v1/exportServiceInstanceArchive/{jobId} If the status is Completed , the metadata has been successfully exported to the object storage bucket.3.Now, import the metadata into the standby instance.Invoke the REST API using the following postman or curl command.This action retrieves the archive from the OCI Object Storage Cloud Service bucket instance where the archive was initially created.POST http://host:port/ic/api/common/v1/importServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "archiveFile":"archive_Local_Suite_Instance-483.zip", "importActivateMode":"importOnly", // ImportOnly | ImportActivate | ActivateOnly | StartSchedulesOnly "importSecurityArtifacts":true, "importAppRoleMembers":true, "importScheduleParams":true, "startSchedules":false, "description":"Import to standby", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"OCI cloud user name", Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-7 "storagePassword":Auth password" } } Note: Set the importActivateMode variable to ImportOnly , so that the integration flows are imported but aren't activated.Response Payload: { "jobId": "457", "status": "NOT_STARTED" } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/missing, or the file already exists (if overwrite is set to false ). |
Else, you can also use Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the same.To synchronize the metadata between the instances using REST APIs: 1.Export the metadata from the primary instance.Invoke the REST API using the following postman or curl command.This action uploads the metadata to the OCI Object Storage Cloud Service bucket instance.POST http:/host:port/ic/api/common/v1/exportServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "jobName":"Pod1_Metadata" - If jobName is omitted filename will default to "archive_Local_Suite_Instance-<jobId>.zip", "overwrite":false, - defaults to false, will return error if archive file already exists "exportSecurityArtifacts":true, "exportAppRoleMembers":true, "description":"Export description", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"<OCI user name>", "storagePassword":"<Auth Password> } } Response Headers: Location http://host:port/ic/api/common/v1/ exportServiceInstanceArchive/483Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-6Response Payload: { jobId: 483, location: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/<bucket name>, status: NOT_STARTED } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/ missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.2.Check the status of the export operation using the following command: GET http://host:port/ic/api/common/v1/exportServiceInstanceArchive/{jobId} If the status is Completed , the metadata has been successfully exported to the object storage bucket.3.Now, import the metadata into the standby instance.Invoke the REST API using the following postman or curl command.This action retrieves the archive from the OCI Object Storage Cloud Service bucket instance where the archive was initially created.POST http://host:port/ic/api/common/v1/importServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "archiveFile":"archive_Local_Suite_Instance-483.zip", "importActivateMode":"importOnly", // ImportOnly | ImportActivate | ActivateOnly | StartSchedulesOnly "importSecurityArtifacts":true, "importAppRoleMembers":true, "importScheduleParams":true, "startSchedules":false, "description":"Import to standby", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"OCI cloud user name", Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-7 "storagePassword":Auth password" } } Note: Set the importActivateMode variable to ImportOnly , so that the integration flows are imported but aren't activated.Response Payload: { "jobId": "457", "status": "NOT_STARTED" } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage. |
To synchronize the metadata between the instances using REST APIs: 1.Export the metadata from the primary instance.Invoke the REST API using the following postman or curl command.This action uploads the metadata to the OCI Object Storage Cloud Service bucket instance.POST http:/host:port/ic/api/common/v1/exportServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "jobName":"Pod1_Metadata" - If jobName is omitted filename will default to "archive_Local_Suite_Instance-<jobId>.zip", "overwrite":false, - defaults to false, will return error if archive file already exists "exportSecurityArtifacts":true, "exportAppRoleMembers":true, "description":"Export description", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"<OCI user name>", "storagePassword":"<Auth Password> } } Response Headers: Location http://host:port/ic/api/common/v1/ exportServiceInstanceArchive/483Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-6Response Payload: { jobId: 483, location: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/<bucket name>, status: NOT_STARTED } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/ missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.2.Check the status of the export operation using the following command: GET http://host:port/ic/api/common/v1/exportServiceInstanceArchive/{jobId} If the status is Completed , the metadata has been successfully exported to the object storage bucket.3.Now, import the metadata into the standby instance.Invoke the REST API using the following postman or curl command.This action retrieves the archive from the OCI Object Storage Cloud Service bucket instance where the archive was initially created.POST http://host:port/ic/api/common/v1/importServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "archiveFile":"archive_Local_Suite_Instance-483.zip", "importActivateMode":"importOnly", // ImportOnly | ImportActivate | ActivateOnly | StartSchedulesOnly "importSecurityArtifacts":true, "importAppRoleMembers":true, "importScheduleParams":true, "startSchedules":false, "description":"Import to standby", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"OCI cloud user name", Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-7 "storagePassword":Auth password" } } Note: Set the importActivateMode variable to ImportOnly , so that the integration flows are imported but aren't activated.Response Payload: { "jobId": "457", "status": "NOT_STARTED" } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.4.Verify the import status. |
Invoke the REST API using the following postman or curl command.This action uploads the metadata to the OCI Object Storage Cloud Service bucket instance.POST http:/host:port/ic/api/common/v1/exportServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "jobName":"Pod1_Metadata" - If jobName is omitted filename will default to "archive_Local_Suite_Instance-<jobId>.zip", "overwrite":false, - defaults to false, will return error if archive file already exists "exportSecurityArtifacts":true, "exportAppRoleMembers":true, "description":"Export description", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"<OCI user name>", "storagePassword":"<Auth Password> } } Response Headers: Location http://host:port/ic/api/common/v1/ exportServiceInstanceArchive/483Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-6Response Payload: { jobId: 483, location: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/<bucket name>, status: NOT_STARTED } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/ missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.2.Check the status of the export operation using the following command: GET http://host:port/ic/api/common/v1/exportServiceInstanceArchive/{jobId} If the status is Completed , the metadata has been successfully exported to the object storage bucket.3.Now, import the metadata into the standby instance.Invoke the REST API using the following postman or curl command.This action retrieves the archive from the OCI Object Storage Cloud Service bucket instance where the archive was initially created.POST http://host:port/ic/api/common/v1/importServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "archiveFile":"archive_Local_Suite_Instance-483.zip", "importActivateMode":"importOnly", // ImportOnly | ImportActivate | ActivateOnly | StartSchedulesOnly "importSecurityArtifacts":true, "importAppRoleMembers":true, "importScheduleParams":true, "startSchedules":false, "description":"Import to standby", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"OCI cloud user name", Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-7 "storagePassword":Auth password" } } Note: Set the importActivateMode variable to ImportOnly , so that the integration flows are imported but aren't activated.Response Payload: { "jobId": "457", "status": "NOT_STARTED" } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.4.Verify the import status.GET https://host:port/ic/api/common/v1/importServiceInstanceArchive/457 Where 457 is the Job ID from the import response payload. |
This action uploads the metadata to the OCI Object Storage Cloud Service bucket instance.POST http:/host:port/ic/api/common/v1/exportServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "jobName":"Pod1_Metadata" - If jobName is omitted filename will default to "archive_Local_Suite_Instance-<jobId>.zip", "overwrite":false, - defaults to false, will return error if archive file already exists "exportSecurityArtifacts":true, "exportAppRoleMembers":true, "description":"Export description", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"<OCI user name>", "storagePassword":"<Auth Password> } } Response Headers: Location http://host:port/ic/api/common/v1/ exportServiceInstanceArchive/483Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-6Response Payload: { jobId: 483, location: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/<bucket name>, status: NOT_STARTED } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/ missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.2.Check the status of the export operation using the following command: GET http://host:port/ic/api/common/v1/exportServiceInstanceArchive/{jobId} If the status is Completed , the metadata has been successfully exported to the object storage bucket.3.Now, import the metadata into the standby instance.Invoke the REST API using the following postman or curl command.This action retrieves the archive from the OCI Object Storage Cloud Service bucket instance where the archive was initially created.POST http://host:port/ic/api/common/v1/importServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "archiveFile":"archive_Local_Suite_Instance-483.zip", "importActivateMode":"importOnly", // ImportOnly | ImportActivate | ActivateOnly | StartSchedulesOnly "importSecurityArtifacts":true, "importAppRoleMembers":true, "importScheduleParams":true, "startSchedules":false, "description":"Import to standby", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"OCI cloud user name", Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-7 "storagePassword":Auth password" } } Note: Set the importActivateMode variable to ImportOnly , so that the integration flows are imported but aren't activated.Response Payload: { "jobId": "457", "status": "NOT_STARTED" } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.4.Verify the import status.GET https://host:port/ic/api/common/v1/importServiceInstanceArchive/457 Where 457 is the Job ID from the import response payload.Note: In this example, the integrations imported are not activated, conforming to the best practice. |
POST http:/host:port/ic/api/common/v1/exportServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "jobName":"Pod1_Metadata" - If jobName is omitted filename will default to "archive_Local_Suite_Instance-<jobId>.zip", "overwrite":false, - defaults to false, will return error if archive file already exists "exportSecurityArtifacts":true, "exportAppRoleMembers":true, "description":"Export description", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"<OCI user name>", "storagePassword":"<Auth Password> } } Response Headers: Location http://host:port/ic/api/common/v1/ exportServiceInstanceArchive/483Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-6Response Payload: { jobId: 483, location: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic/<bucket name>, status: NOT_STARTED } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/ missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.2.Check the status of the export operation using the following command: GET http://host:port/ic/api/common/v1/exportServiceInstanceArchive/{jobId} If the status is Completed , the metadata has been successfully exported to the object storage bucket.3.Now, import the metadata into the standby instance.Invoke the REST API using the following postman or curl command.This action retrieves the archive from the OCI Object Storage Cloud Service bucket instance where the archive was initially created.POST http://host:port/ic/api/common/v1/importServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "archiveFile":"archive_Local_Suite_Instance-483.zip", "importActivateMode":"importOnly", // ImportOnly | ImportActivate | ActivateOnly | StartSchedulesOnly "importSecurityArtifacts":true, "importAppRoleMembers":true, "importScheduleParams":true, "startSchedules":false, "description":"Import to standby", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"OCI cloud user name", Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-7 "storagePassword":Auth password" } } Note: Set the importActivateMode variable to ImportOnly , so that the integration flows are imported but aren't activated.Response Payload: { "jobId": "457", "status": "NOT_STARTED" } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.4.Verify the import status.GET https://host:port/ic/api/common/v1/importServiceInstanceArchive/457 Where 457 is the Job ID from the import response payload.Note: In this example, the integrations imported are not activated, conforming to the best practice.However, if you have many integrations, you can activate the stateless integrations while importing, but do not activate scheduled, publish-subscribe, polling, or business-events integrations. |
409 Conflict Import or export job is already running or storage details are incorrect/ missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.2.Check the status of the export operation using the following command: GET http://host:port/ic/api/common/v1/exportServiceInstanceArchive/{jobId} If the status is Completed , the metadata has been successfully exported to the object storage bucket.3.Now, import the metadata into the standby instance.Invoke the REST API using the following postman or curl command.This action retrieves the archive from the OCI Object Storage Cloud Service bucket instance where the archive was initially created.POST http://host:port/ic/api/common/v1/importServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "archiveFile":"archive_Local_Suite_Instance-483.zip", "importActivateMode":"importOnly", // ImportOnly | ImportActivate | ActivateOnly | StartSchedulesOnly "importSecurityArtifacts":true, "importAppRoleMembers":true, "importScheduleParams":true, "startSchedules":false, "description":"Import to standby", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"OCI cloud user name", Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-7 "storagePassword":Auth password" } } Note: Set the importActivateMode variable to ImportOnly , so that the integration flows are imported but aren't activated.Response Payload: { "jobId": "457", "status": "NOT_STARTED" } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.4.Verify the import status.GET https://host:port/ic/api/common/v1/importServiceInstanceArchive/457 Where 457 is the Job ID from the import response payload.Note: In this example, the integrations imported are not activated, conforming to the best practice.However, if you have many integrations, you can activate the stateless integrations while importing, but do not activate scheduled, publish-subscribe, polling, or business-events integrations.Perform Post-Configuration Tasks Learn how to regularly update integrations with scheduled parameters between your primary and standby integration instances. |
500 Internal Server Error Error communicating to the registry or storage.2.Check the status of the export operation using the following command: GET http://host:port/ic/api/common/v1/exportServiceInstanceArchive/{jobId} If the status is Completed , the metadata has been successfully exported to the object storage bucket.3.Now, import the metadata into the standby instance.Invoke the REST API using the following postman or curl command.This action retrieves the archive from the OCI Object Storage Cloud Service bucket instance where the archive was initially created.POST http://host:port/ic/api/common/v1/importServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "archiveFile":"archive_Local_Suite_Instance-483.zip", "importActivateMode":"importOnly", // ImportOnly | ImportActivate | ActivateOnly | StartSchedulesOnly "importSecurityArtifacts":true, "importAppRoleMembers":true, "importScheduleParams":true, "startSchedules":false, "description":"Import to standby", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"OCI cloud user name", Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-7 "storagePassword":Auth password" } } Note: Set the importActivateMode variable to ImportOnly , so that the integration flows are imported but aren't activated.Response Payload: { "jobId": "457", "status": "NOT_STARTED" } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.4.Verify the import status.GET https://host:port/ic/api/common/v1/importServiceInstanceArchive/457 Where 457 is the Job ID from the import response payload.Note: In this example, the integrations imported are not activated, conforming to the best practice.However, if you have many integrations, you can activate the stateless integrations while importing, but do not activate scheduled, publish-subscribe, polling, or business-events integrations.Perform Post-Configuration Tasks Learn how to regularly update integrations with scheduled parameters between your primary and standby integration instances.After the DR system is set up, you need to regularly update integrations with scheduled parameters in the secondary Oracle Integration instances, monitor the instances for a failover, and execute failover-handling tasks when necessary. |
2.Check the status of the export operation using the following command: GET http://host:port/ic/api/common/v1/exportServiceInstanceArchive/{jobId} If the status is Completed , the metadata has been successfully exported to the object storage bucket.3.Now, import the metadata into the standby instance.Invoke the REST API using the following postman or curl command.This action retrieves the archive from the OCI Object Storage Cloud Service bucket instance where the archive was initially created.POST http://host:port/ic/api/common/v1/importServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "archiveFile":"archive_Local_Suite_Instance-483.zip", "importActivateMode":"importOnly", // ImportOnly | ImportActivate | ActivateOnly | StartSchedulesOnly "importSecurityArtifacts":true, "importAppRoleMembers":true, "importScheduleParams":true, "startSchedules":false, "description":"Import to standby", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"OCI cloud user name", Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-7 "storagePassword":Auth password" } } Note: Set the importActivateMode variable to ImportOnly , so that the integration flows are imported but aren't activated.Response Payload: { "jobId": "457", "status": "NOT_STARTED" } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.4.Verify the import status.GET https://host:port/ic/api/common/v1/importServiceInstanceArchive/457 Where 457 is the Job ID from the import response payload.Note: In this example, the integrations imported are not activated, conforming to the best practice.However, if you have many integrations, you can activate the stateless integrations while importing, but do not activate scheduled, publish-subscribe, polling, or business-events integrations.Perform Post-Configuration Tasks Learn how to regularly update integrations with scheduled parameters between your primary and standby integration instances.After the DR system is set up, you need to regularly update integrations with scheduled parameters in the secondary Oracle Integration instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Automate Scheduled Parameters Updates Monitor Your InstancesChapter 3 Perform Post-Configuration Tasks 3-8Automate Metadata Synchronization Ensure that the metadata is regularly synchronized between the primary and the standby instance using CICD. |
3.Now, import the metadata into the standby instance.Invoke the REST API using the following postman or curl command.This action retrieves the archive from the OCI Object Storage Cloud Service bucket instance where the archive was initially created.POST http://host:port/ic/api/common/v1/importServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "archiveFile":"archive_Local_Suite_Instance-483.zip", "importActivateMode":"importOnly", // ImportOnly | ImportActivate | ActivateOnly | StartSchedulesOnly "importSecurityArtifacts":true, "importAppRoleMembers":true, "importScheduleParams":true, "startSchedules":false, "description":"Import to standby", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"OCI cloud user name", Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-7 "storagePassword":Auth password" } } Note: Set the importActivateMode variable to ImportOnly , so that the integration flows are imported but aren't activated.Response Payload: { "jobId": "457", "status": "NOT_STARTED" } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.4.Verify the import status.GET https://host:port/ic/api/common/v1/importServiceInstanceArchive/457 Where 457 is the Job ID from the import response payload.Note: In this example, the integrations imported are not activated, conforming to the best practice.However, if you have many integrations, you can activate the stateless integrations while importing, but do not activate scheduled, publish-subscribe, polling, or business-events integrations.Perform Post-Configuration Tasks Learn how to regularly update integrations with scheduled parameters between your primary and standby integration instances.After the DR system is set up, you need to regularly update integrations with scheduled parameters in the secondary Oracle Integration instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Automate Scheduled Parameters Updates Monitor Your InstancesChapter 3 Perform Post-Configuration Tasks 3-8Automate Metadata Synchronization Ensure that the metadata is regularly synchronized between the primary and the standby instance using CICD.After the initial, one-time migration of the metadata is complete, you must keep the metadata synchronized between the instances using CICD. |
Invoke the REST API using the following postman or curl command.This action retrieves the archive from the OCI Object Storage Cloud Service bucket instance where the archive was initially created.POST http://host:port/ic/api/common/v1/importServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "archiveFile":"archive_Local_Suite_Instance-483.zip", "importActivateMode":"importOnly", // ImportOnly | ImportActivate | ActivateOnly | StartSchedulesOnly "importSecurityArtifacts":true, "importAppRoleMembers":true, "importScheduleParams":true, "startSchedules":false, "description":"Import to standby", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"OCI cloud user name", Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-7 "storagePassword":Auth password" } } Note: Set the importActivateMode variable to ImportOnly , so that the integration flows are imported but aren't activated.Response Payload: { "jobId": "457", "status": "NOT_STARTED" } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.4.Verify the import status.GET https://host:port/ic/api/common/v1/importServiceInstanceArchive/457 Where 457 is the Job ID from the import response payload.Note: In this example, the integrations imported are not activated, conforming to the best practice.However, if you have many integrations, you can activate the stateless integrations while importing, but do not activate scheduled, publish-subscribe, polling, or business-events integrations.Perform Post-Configuration Tasks Learn how to regularly update integrations with scheduled parameters between your primary and standby integration instances.After the DR system is set up, you need to regularly update integrations with scheduled parameters in the secondary Oracle Integration instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Automate Scheduled Parameters Updates Monitor Your InstancesChapter 3 Perform Post-Configuration Tasks 3-8Automate Metadata Synchronization Ensure that the metadata is regularly synchronized between the primary and the standby instance using CICD.After the initial, one-time migration of the metadata is complete, you must keep the metadata synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the metadata synchronized. |
This action retrieves the archive from the OCI Object Storage Cloud Service bucket instance where the archive was initially created.POST http://host:port/ic/api/common/v1/importServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "archiveFile":"archive_Local_Suite_Instance-483.zip", "importActivateMode":"importOnly", // ImportOnly | ImportActivate | ActivateOnly | StartSchedulesOnly "importSecurityArtifacts":true, "importAppRoleMembers":true, "importScheduleParams":true, "startSchedules":false, "description":"Import to standby", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"OCI cloud user name", Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-7 "storagePassword":Auth password" } } Note: Set the importActivateMode variable to ImportOnly , so that the integration flows are imported but aren't activated.Response Payload: { "jobId": "457", "status": "NOT_STARTED" } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.4.Verify the import status.GET https://host:port/ic/api/common/v1/importServiceInstanceArchive/457 Where 457 is the Job ID from the import response payload.Note: In this example, the integrations imported are not activated, conforming to the best practice.However, if you have many integrations, you can activate the stateless integrations while importing, but do not activate scheduled, publish-subscribe, polling, or business-events integrations.Perform Post-Configuration Tasks Learn how to regularly update integrations with scheduled parameters between your primary and standby integration instances.After the DR system is set up, you need to regularly update integrations with scheduled parameters in the secondary Oracle Integration instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Automate Scheduled Parameters Updates Monitor Your InstancesChapter 3 Perform Post-Configuration Tasks 3-8Automate Metadata Synchronization Ensure that the metadata is regularly synchronized between the primary and the standby instance using CICD.After the initial, one-time migration of the metadata is complete, you must keep the metadata synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the metadata synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub. |
POST http://host:port/ic/api/common/v1/importServiceInstanceArchive Request Headers: Content-Type application/json Request Payload: { "archiveFile":"archive_Local_Suite_Instance-483.zip", "importActivateMode":"importOnly", // ImportOnly | ImportActivate | ActivateOnly | StartSchedulesOnly "importSecurityArtifacts":true, "importAppRoleMembers":true, "importScheduleParams":true, "startSchedules":false, "description":"Import to standby", "storageName", - name of storage configuration, this can be used instead of storageInfo, if both are defined storageInfo will take precedence "storageInfo":{ "storageUrl":"https://swiftobjectstorage.us- ashburn-1.oraclecloud.com/v1/paasdevoic/<bucket name>", "storageUser":"OCI cloud user name", Chapter 3 Set Up the Disaster Recovery Solution for Integrations 3-7 "storagePassword":Auth password" } } Note: Set the importActivateMode variable to ImportOnly , so that the integration flows are imported but aren't activated.Response Payload: { "jobId": "457", "status": "NOT_STARTED" } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.4.Verify the import status.GET https://host:port/ic/api/common/v1/importServiceInstanceArchive/457 Where 457 is the Job ID from the import response payload.Note: In this example, the integrations imported are not activated, conforming to the best practice.However, if you have many integrations, you can activate the stateless integrations while importing, but do not activate scheduled, publish-subscribe, polling, or business-events integrations.Perform Post-Configuration Tasks Learn how to regularly update integrations with scheduled parameters between your primary and standby integration instances.After the DR system is set up, you need to regularly update integrations with scheduled parameters in the secondary Oracle Integration instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Automate Scheduled Parameters Updates Monitor Your InstancesChapter 3 Perform Post-Configuration Tasks 3-8Automate Metadata Synchronization Ensure that the metadata is regularly synchronized between the primary and the standby instance using CICD.After the initial, one-time migration of the metadata is complete, you must keep the metadata synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the metadata synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See Integrations REST Endpoints and Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the REST APIs to use. |
Response Payload: { "jobId": "457", "status": "NOT_STARTED" } Response Status: 202 Accepted Export job was accepted.409 Conflict Import or export job is already running or storage details are incorrect/missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.4.Verify the import status.GET https://host:port/ic/api/common/v1/importServiceInstanceArchive/457 Where 457 is the Job ID from the import response payload.Note: In this example, the integrations imported are not activated, conforming to the best practice.However, if you have many integrations, you can activate the stateless integrations while importing, but do not activate scheduled, publish-subscribe, polling, or business-events integrations.Perform Post-Configuration Tasks Learn how to regularly update integrations with scheduled parameters between your primary and standby integration instances.After the DR system is set up, you need to regularly update integrations with scheduled parameters in the secondary Oracle Integration instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Automate Scheduled Parameters Updates Monitor Your InstancesChapter 3 Perform Post-Configuration Tasks 3-8Automate Metadata Synchronization Ensure that the metadata is regularly synchronized between the primary and the standby instance using CICD.After the initial, one-time migration of the metadata is complete, you must keep the metadata synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the metadata synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See Integrations REST Endpoints and Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the REST APIs to use.The following figure shows the CICD forking to both the instances: Automate Scheduled Parameters Updates Update the integrations with scheduled parameters in the standby Oracle Integration instance. |
409 Conflict Import or export job is already running or storage details are incorrect/missing, or the file already exists (if overwrite is set to false ).500 Internal Server Error Error communicating to the registry or storage.4.Verify the import status.GET https://host:port/ic/api/common/v1/importServiceInstanceArchive/457 Where 457 is the Job ID from the import response payload.Note: In this example, the integrations imported are not activated, conforming to the best practice.However, if you have many integrations, you can activate the stateless integrations while importing, but do not activate scheduled, publish-subscribe, polling, or business-events integrations.Perform Post-Configuration Tasks Learn how to regularly update integrations with scheduled parameters between your primary and standby integration instances.After the DR system is set up, you need to regularly update integrations with scheduled parameters in the secondary Oracle Integration instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Automate Scheduled Parameters Updates Monitor Your InstancesChapter 3 Perform Post-Configuration Tasks 3-8Automate Metadata Synchronization Ensure that the metadata is regularly synchronized between the primary and the standby instance using CICD.After the initial, one-time migration of the metadata is complete, you must keep the metadata synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the metadata synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See Integrations REST Endpoints and Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the REST APIs to use.The following figure shows the CICD forking to both the instances: Automate Scheduled Parameters Updates Update the integrations with scheduled parameters in the standby Oracle Integration instance.You must frequently retrieve the metadata with scheduled parameters of integrations from the primary instance; for example, you can execute this every fifteen or thirty minutes. |
500 Internal Server Error Error communicating to the registry or storage.4.Verify the import status.GET https://host:port/ic/api/common/v1/importServiceInstanceArchive/457 Where 457 is the Job ID from the import response payload.Note: In this example, the integrations imported are not activated, conforming to the best practice.However, if you have many integrations, you can activate the stateless integrations while importing, but do not activate scheduled, publish-subscribe, polling, or business-events integrations.Perform Post-Configuration Tasks Learn how to regularly update integrations with scheduled parameters between your primary and standby integration instances.After the DR system is set up, you need to regularly update integrations with scheduled parameters in the secondary Oracle Integration instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Automate Scheduled Parameters Updates Monitor Your InstancesChapter 3 Perform Post-Configuration Tasks 3-8Automate Metadata Synchronization Ensure that the metadata is regularly synchronized between the primary and the standby instance using CICD.After the initial, one-time migration of the metadata is complete, you must keep the metadata synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the metadata synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See Integrations REST Endpoints and Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the REST APIs to use.The following figure shows the CICD forking to both the instances: Automate Scheduled Parameters Updates Update the integrations with scheduled parameters in the standby Oracle Integration instance.You must frequently retrieve the metadata with scheduled parameters of integrations from the primary instance; for example, you can execute this every fifteen or thirty minutes.Use REST APIs to update the integrations with the extracted scheduled parameters in the standby Oracle Integration instance. |
4.Verify the import status.GET https://host:port/ic/api/common/v1/importServiceInstanceArchive/457 Where 457 is the Job ID from the import response payload.Note: In this example, the integrations imported are not activated, conforming to the best practice.However, if you have many integrations, you can activate the stateless integrations while importing, but do not activate scheduled, publish-subscribe, polling, or business-events integrations.Perform Post-Configuration Tasks Learn how to regularly update integrations with scheduled parameters between your primary and standby integration instances.After the DR system is set up, you need to regularly update integrations with scheduled parameters in the secondary Oracle Integration instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Automate Scheduled Parameters Updates Monitor Your InstancesChapter 3 Perform Post-Configuration Tasks 3-8Automate Metadata Synchronization Ensure that the metadata is regularly synchronized between the primary and the standby instance using CICD.After the initial, one-time migration of the metadata is complete, you must keep the metadata synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the metadata synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See Integrations REST Endpoints and Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the REST APIs to use.The following figure shows the CICD forking to both the instances: Automate Scheduled Parameters Updates Update the integrations with scheduled parameters in the standby Oracle Integration instance.You must frequently retrieve the metadata with scheduled parameters of integrations from the primary instance; for example, you can execute this every fifteen or thirty minutes.Use REST APIs to update the integrations with the extracted scheduled parameters in the standby Oracle Integration instance.Subsequently, you can choose to update the corresponding integrations in the standby instance either periodically or during a failover. |
GET https://host:port/ic/api/common/v1/importServiceInstanceArchive/457 Where 457 is the Job ID from the import response payload.Note: In this example, the integrations imported are not activated, conforming to the best practice.However, if you have many integrations, you can activate the stateless integrations while importing, but do not activate scheduled, publish-subscribe, polling, or business-events integrations.Perform Post-Configuration Tasks Learn how to regularly update integrations with scheduled parameters between your primary and standby integration instances.After the DR system is set up, you need to regularly update integrations with scheduled parameters in the secondary Oracle Integration instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Automate Scheduled Parameters Updates Monitor Your InstancesChapter 3 Perform Post-Configuration Tasks 3-8Automate Metadata Synchronization Ensure that the metadata is regularly synchronized between the primary and the standby instance using CICD.After the initial, one-time migration of the metadata is complete, you must keep the metadata synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the metadata synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See Integrations REST Endpoints and Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the REST APIs to use.The following figure shows the CICD forking to both the instances: Automate Scheduled Parameters Updates Update the integrations with scheduled parameters in the standby Oracle Integration instance.You must frequently retrieve the metadata with scheduled parameters of integrations from the primary instance; for example, you can execute this every fifteen or thirty minutes.Use REST APIs to update the integrations with the extracted scheduled parameters in the standby Oracle Integration instance.Subsequently, you can choose to update the corresponding integrations in the standby instance either periodically or during a failover.To get the details of each scheduled integration from the primary instance, see Retrieve an Integration in REST API for Oracle Integration Generation 2 . |
Note: In this example, the integrations imported are not activated, conforming to the best practice.However, if you have many integrations, you can activate the stateless integrations while importing, but do not activate scheduled, publish-subscribe, polling, or business-events integrations.Perform Post-Configuration Tasks Learn how to regularly update integrations with scheduled parameters between your primary and standby integration instances.After the DR system is set up, you need to regularly update integrations with scheduled parameters in the secondary Oracle Integration instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Automate Scheduled Parameters Updates Monitor Your InstancesChapter 3 Perform Post-Configuration Tasks 3-8Automate Metadata Synchronization Ensure that the metadata is regularly synchronized between the primary and the standby instance using CICD.After the initial, one-time migration of the metadata is complete, you must keep the metadata synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the metadata synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See Integrations REST Endpoints and Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the REST APIs to use.The following figure shows the CICD forking to both the instances: Automate Scheduled Parameters Updates Update the integrations with scheduled parameters in the standby Oracle Integration instance.You must frequently retrieve the metadata with scheduled parameters of integrations from the primary instance; for example, you can execute this every fifteen or thirty minutes.Use REST APIs to update the integrations with the extracted scheduled parameters in the standby Oracle Integration instance.Subsequently, you can choose to update the corresponding integrations in the standby instance either periodically or during a failover.To get the details of each scheduled integration from the primary instance, see Retrieve an Integration in REST API for Oracle Integration Generation 2 .To update an integration in the standby instance, see Update Scheduled Integration Parameters . |
However, if you have many integrations, you can activate the stateless integrations while importing, but do not activate scheduled, publish-subscribe, polling, or business-events integrations.Perform Post-Configuration Tasks Learn how to regularly update integrations with scheduled parameters between your primary and standby integration instances.After the DR system is set up, you need to regularly update integrations with scheduled parameters in the secondary Oracle Integration instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Automate Scheduled Parameters Updates Monitor Your InstancesChapter 3 Perform Post-Configuration Tasks 3-8Automate Metadata Synchronization Ensure that the metadata is regularly synchronized between the primary and the standby instance using CICD.After the initial, one-time migration of the metadata is complete, you must keep the metadata synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the metadata synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See Integrations REST Endpoints and Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the REST APIs to use.The following figure shows the CICD forking to both the instances: Automate Scheduled Parameters Updates Update the integrations with scheduled parameters in the standby Oracle Integration instance.You must frequently retrieve the metadata with scheduled parameters of integrations from the primary instance; for example, you can execute this every fifteen or thirty minutes.Use REST APIs to update the integrations with the extracted scheduled parameters in the standby Oracle Integration instance.Subsequently, you can choose to update the corresponding integrations in the standby instance either periodically or during a failover.To get the details of each scheduled integration from the primary instance, see Retrieve an Integration in REST API for Oracle Integration Generation 2 .To update an integration in the standby instance, see Update Scheduled Integration Parameters .After a failover, you may have to manually update the parameter values to avoid reprocessing of old data.Chapter 3 Perform Post-Configuration Tasks 3-9Note: Optionally, you can use the export-import APIs, see Migrate Metadata from the Primary Instance . |
Perform Post-Configuration Tasks Learn how to regularly update integrations with scheduled parameters between your primary and standby integration instances.After the DR system is set up, you need to regularly update integrations with scheduled parameters in the secondary Oracle Integration instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Automate Scheduled Parameters Updates Monitor Your InstancesChapter 3 Perform Post-Configuration Tasks 3-8Automate Metadata Synchronization Ensure that the metadata is regularly synchronized between the primary and the standby instance using CICD.After the initial, one-time migration of the metadata is complete, you must keep the metadata synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the metadata synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See Integrations REST Endpoints and Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the REST APIs to use.The following figure shows the CICD forking to both the instances: Automate Scheduled Parameters Updates Update the integrations with scheduled parameters in the standby Oracle Integration instance.You must frequently retrieve the metadata with scheduled parameters of integrations from the primary instance; for example, you can execute this every fifteen or thirty minutes.Use REST APIs to update the integrations with the extracted scheduled parameters in the standby Oracle Integration instance.Subsequently, you can choose to update the corresponding integrations in the standby instance either periodically or during a failover.To get the details of each scheduled integration from the primary instance, see Retrieve an Integration in REST API for Oracle Integration Generation 2 .To update an integration in the standby instance, see Update Scheduled Integration Parameters .After a failover, you may have to manually update the parameter values to avoid reprocessing of old data.Chapter 3 Perform Post-Configuration Tasks 3-9Note: Optionally, you can use the export-import APIs, see Migrate Metadata from the Primary Instance .Monitor Your Instances Regularly monitor the health of your active Oracle Integration instances. |
After the DR system is set up, you need to regularly update integrations with scheduled parameters in the secondary Oracle Integration instances, monitor the instances for a failover, and execute failover-handling tasks when necessary.Automate Metadata Synchronization Automate Scheduled Parameters Updates Monitor Your InstancesChapter 3 Perform Post-Configuration Tasks 3-8Automate Metadata Synchronization Ensure that the metadata is regularly synchronized between the primary and the standby instance using CICD.After the initial, one-time migration of the metadata is complete, you must keep the metadata synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the metadata synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See Integrations REST Endpoints and Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the REST APIs to use.The following figure shows the CICD forking to both the instances: Automate Scheduled Parameters Updates Update the integrations with scheduled parameters in the standby Oracle Integration instance.You must frequently retrieve the metadata with scheduled parameters of integrations from the primary instance; for example, you can execute this every fifteen or thirty minutes.Use REST APIs to update the integrations with the extracted scheduled parameters in the standby Oracle Integration instance.Subsequently, you can choose to update the corresponding integrations in the standby instance either periodically or during a failover.To get the details of each scheduled integration from the primary instance, see Retrieve an Integration in REST API for Oracle Integration Generation 2 .To update an integration in the standby instance, see Update Scheduled Integration Parameters .After a failover, you may have to manually update the parameter values to avoid reprocessing of old data.Chapter 3 Perform Post-Configuration Tasks 3-9Note: Optionally, you can use the export-import APIs, see Migrate Metadata from the Primary Instance .Monitor Your Instances Regularly monitor the health of your active Oracle Integration instances.You can use the OCI health-check service or a third-party monitoring service. |
Automate Metadata Synchronization Automate Scheduled Parameters Updates Monitor Your InstancesChapter 3 Perform Post-Configuration Tasks 3-8Automate Metadata Synchronization Ensure that the metadata is regularly synchronized between the primary and the standby instance using CICD.After the initial, one-time migration of the metadata is complete, you must keep the metadata synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the metadata synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See Integrations REST Endpoints and Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the REST APIs to use.The following figure shows the CICD forking to both the instances: Automate Scheduled Parameters Updates Update the integrations with scheduled parameters in the standby Oracle Integration instance.You must frequently retrieve the metadata with scheduled parameters of integrations from the primary instance; for example, you can execute this every fifteen or thirty minutes.Use REST APIs to update the integrations with the extracted scheduled parameters in the standby Oracle Integration instance.Subsequently, you can choose to update the corresponding integrations in the standby instance either periodically or during a failover.To get the details of each scheduled integration from the primary instance, see Retrieve an Integration in REST API for Oracle Integration Generation 2 .To update an integration in the standby instance, see Update Scheduled Integration Parameters .After a failover, you may have to manually update the parameter values to avoid reprocessing of old data.Chapter 3 Perform Post-Configuration Tasks 3-9Note: Optionally, you can use the export-import APIs, see Migrate Metadata from the Primary Instance .Monitor Your Instances Regularly monitor the health of your active Oracle Integration instances.You can use the OCI health-check service or a third-party monitoring service.Additionally, define a process to identify outages and, subsequently, trigger failovers. |
After the initial, one-time migration of the metadata is complete, you must keep the metadata synchronized between the instances using CICD.You can use Jenkins or a similar tool to implement CICD for your instances and have the metadata synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See Integrations REST Endpoints and Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the REST APIs to use.The following figure shows the CICD forking to both the instances: Automate Scheduled Parameters Updates Update the integrations with scheduled parameters in the standby Oracle Integration instance.You must frequently retrieve the metadata with scheduled parameters of integrations from the primary instance; for example, you can execute this every fifteen or thirty minutes.Use REST APIs to update the integrations with the extracted scheduled parameters in the standby Oracle Integration instance.Subsequently, you can choose to update the corresponding integrations in the standby instance either periodically or during a failover.To get the details of each scheduled integration from the primary instance, see Retrieve an Integration in REST API for Oracle Integration Generation 2 .To update an integration in the standby instance, see Update Scheduled Integration Parameters .After a failover, you may have to manually update the parameter values to avoid reprocessing of old data.Chapter 3 Perform Post-Configuration Tasks 3-9Note: Optionally, you can use the export-import APIs, see Migrate Metadata from the Primary Instance .Monitor Your Instances Regularly monitor the health of your active Oracle Integration instances.You can use the OCI health-check service or a third-party monitoring service.Additionally, define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Learn how to manually switch to the DR environment. |
You can use Jenkins or a similar tool to implement CICD for your instances and have the metadata synchronized.You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See Integrations REST Endpoints and Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the REST APIs to use.The following figure shows the CICD forking to both the instances: Automate Scheduled Parameters Updates Update the integrations with scheduled parameters in the standby Oracle Integration instance.You must frequently retrieve the metadata with scheduled parameters of integrations from the primary instance; for example, you can execute this every fifteen or thirty minutes.Use REST APIs to update the integrations with the extracted scheduled parameters in the standby Oracle Integration instance.Subsequently, you can choose to update the corresponding integrations in the standby instance either periodically or during a failover.To get the details of each scheduled integration from the primary instance, see Retrieve an Integration in REST API for Oracle Integration Generation 2 .To update an integration in the standby instance, see Update Scheduled Integration Parameters .After a failover, you may have to manually update the parameter values to avoid reprocessing of old data.Chapter 3 Perform Post-Configuration Tasks 3-9Note: Optionally, you can use the export-import APIs, see Migrate Metadata from the Primary Instance .Monitor Your Instances Regularly monitor the health of your active Oracle Integration instances.You can use the OCI health-check service or a third-party monitoring service.Additionally, define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Learn how to manually switch to the DR environment.To switch from your primary instance to the standby instance during outages: 1.Stop the primary Oracle Integration instance from the Oracle Cloud Infrastructure Console. |
You can also use an OCI Compute instance as the Jenkins CI server and CD hub.See Integrations REST Endpoints and Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the REST APIs to use.The following figure shows the CICD forking to both the instances: Automate Scheduled Parameters Updates Update the integrations with scheduled parameters in the standby Oracle Integration instance.You must frequently retrieve the metadata with scheduled parameters of integrations from the primary instance; for example, you can execute this every fifteen or thirty minutes.Use REST APIs to update the integrations with the extracted scheduled parameters in the standby Oracle Integration instance.Subsequently, you can choose to update the corresponding integrations in the standby instance either periodically or during a failover.To get the details of each scheduled integration from the primary instance, see Retrieve an Integration in REST API for Oracle Integration Generation 2 .To update an integration in the standby instance, see Update Scheduled Integration Parameters .After a failover, you may have to manually update the parameter values to avoid reprocessing of old data.Chapter 3 Perform Post-Configuration Tasks 3-9Note: Optionally, you can use the export-import APIs, see Migrate Metadata from the Primary Instance .Monitor Your Instances Regularly monitor the health of your active Oracle Integration instances.You can use the OCI health-check service or a third-party monitoring service.Additionally, define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Learn how to manually switch to the DR environment.To switch from your primary instance to the standby instance during outages: 1.Stop the primary Oracle Integration instance from the Oracle Cloud Infrastructure Console.2.Prepare your secondary instance. |
See Integrations REST Endpoints and Connections REST Endpoints in REST API for Oracle Integration Generation 2 for the REST APIs to use.The following figure shows the CICD forking to both the instances: Automate Scheduled Parameters Updates Update the integrations with scheduled parameters in the standby Oracle Integration instance.You must frequently retrieve the metadata with scheduled parameters of integrations from the primary instance; for example, you can execute this every fifteen or thirty minutes.Use REST APIs to update the integrations with the extracted scheduled parameters in the standby Oracle Integration instance.Subsequently, you can choose to update the corresponding integrations in the standby instance either periodically or during a failover.To get the details of each scheduled integration from the primary instance, see Retrieve an Integration in REST API for Oracle Integration Generation 2 .To update an integration in the standby instance, see Update Scheduled Integration Parameters .After a failover, you may have to manually update the parameter values to avoid reprocessing of old data.Chapter 3 Perform Post-Configuration Tasks 3-9Note: Optionally, you can use the export-import APIs, see Migrate Metadata from the Primary Instance .Monitor Your Instances Regularly monitor the health of your active Oracle Integration instances.You can use the OCI health-check service or a third-party monitoring service.Additionally, define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Learn how to manually switch to the DR environment.To switch from your primary instance to the standby instance during outages: 1.Stop the primary Oracle Integration instance from the Oracle Cloud Infrastructure Console.2.Prepare your secondary instance.a.If you are not using CICD, then ensure that the standby (secondary) instance contains the latest versions of integrations. |
The following figure shows the CICD forking to both the instances: Automate Scheduled Parameters Updates Update the integrations with scheduled parameters in the standby Oracle Integration instance.You must frequently retrieve the metadata with scheduled parameters of integrations from the primary instance; for example, you can execute this every fifteen or thirty minutes.Use REST APIs to update the integrations with the extracted scheduled parameters in the standby Oracle Integration instance.Subsequently, you can choose to update the corresponding integrations in the standby instance either periodically or during a failover.To get the details of each scheduled integration from the primary instance, see Retrieve an Integration in REST API for Oracle Integration Generation 2 .To update an integration in the standby instance, see Update Scheduled Integration Parameters .After a failover, you may have to manually update the parameter values to avoid reprocessing of old data.Chapter 3 Perform Post-Configuration Tasks 3-9Note: Optionally, you can use the export-import APIs, see Migrate Metadata from the Primary Instance .Monitor Your Instances Regularly monitor the health of your active Oracle Integration instances.You can use the OCI health-check service or a third-party monitoring service.Additionally, define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Learn how to manually switch to the DR environment.To switch from your primary instance to the standby instance during outages: 1.Stop the primary Oracle Integration instance from the Oracle Cloud Infrastructure Console.2.Prepare your secondary instance.a.If you are not using CICD, then ensure that the standby (secondary) instance contains the latest versions of integrations.You can use the import API to import the latest snapshot extracted. |
You must frequently retrieve the metadata with scheduled parameters of integrations from the primary instance; for example, you can execute this every fifteen or thirty minutes.Use REST APIs to update the integrations with the extracted scheduled parameters in the standby Oracle Integration instance.Subsequently, you can choose to update the corresponding integrations in the standby instance either periodically or during a failover.To get the details of each scheduled integration from the primary instance, see Retrieve an Integration in REST API for Oracle Integration Generation 2 .To update an integration in the standby instance, see Update Scheduled Integration Parameters .After a failover, you may have to manually update the parameter values to avoid reprocessing of old data.Chapter 3 Perform Post-Configuration Tasks 3-9Note: Optionally, you can use the export-import APIs, see Migrate Metadata from the Primary Instance .Monitor Your Instances Regularly monitor the health of your active Oracle Integration instances.You can use the OCI health-check service or a third-party monitoring service.Additionally, define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Learn how to manually switch to the DR environment.To switch from your primary instance to the standby instance during outages: 1.Stop the primary Oracle Integration instance from the Oracle Cloud Infrastructure Console.2.Prepare your secondary instance.a.If you are not using CICD, then ensure that the standby (secondary) instance contains the latest versions of integrations.You can use the import API to import the latest snapshot extracted.b.Activate all relevant integrations. |
Use REST APIs to update the integrations with the extracted scheduled parameters in the standby Oracle Integration instance.Subsequently, you can choose to update the corresponding integrations in the standby instance either periodically or during a failover.To get the details of each scheduled integration from the primary instance, see Retrieve an Integration in REST API for Oracle Integration Generation 2 .To update an integration in the standby instance, see Update Scheduled Integration Parameters .After a failover, you may have to manually update the parameter values to avoid reprocessing of old data.Chapter 3 Perform Post-Configuration Tasks 3-9Note: Optionally, you can use the export-import APIs, see Migrate Metadata from the Primary Instance .Monitor Your Instances Regularly monitor the health of your active Oracle Integration instances.You can use the OCI health-check service or a third-party monitoring service.Additionally, define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Learn how to manually switch to the DR environment.To switch from your primary instance to the standby instance during outages: 1.Stop the primary Oracle Integration instance from the Oracle Cloud Infrastructure Console.2.Prepare your secondary instance.a.If you are not using CICD, then ensure that the standby (secondary) instance contains the latest versions of integrations.You can use the import API to import the latest snapshot extracted.b.Activate all relevant integrations.c.Update the scheduled parameters with the latest values to avoid reprocessing of old data. |
Subsequently, you can choose to update the corresponding integrations in the standby instance either periodically or during a failover.To get the details of each scheduled integration from the primary instance, see Retrieve an Integration in REST API for Oracle Integration Generation 2 .To update an integration in the standby instance, see Update Scheduled Integration Parameters .After a failover, you may have to manually update the parameter values to avoid reprocessing of old data.Chapter 3 Perform Post-Configuration Tasks 3-9Note: Optionally, you can use the export-import APIs, see Migrate Metadata from the Primary Instance .Monitor Your Instances Regularly monitor the health of your active Oracle Integration instances.You can use the OCI health-check service or a third-party monitoring service.Additionally, define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Learn how to manually switch to the DR environment.To switch from your primary instance to the standby instance during outages: 1.Stop the primary Oracle Integration instance from the Oracle Cloud Infrastructure Console.2.Prepare your secondary instance.a.If you are not using CICD, then ensure that the standby (secondary) instance contains the latest versions of integrations.You can use the import API to import the latest snapshot extracted.b.Activate all relevant integrations.c.Update the scheduled parameters with the latest values to avoid reprocessing of old data.3.Update the DNS record at your DNS provider or in the OCI DNS zone to route the traffic to the standby instance. |
To get the details of each scheduled integration from the primary instance, see Retrieve an Integration in REST API for Oracle Integration Generation 2 .To update an integration in the standby instance, see Update Scheduled Integration Parameters .After a failover, you may have to manually update the parameter values to avoid reprocessing of old data.Chapter 3 Perform Post-Configuration Tasks 3-9Note: Optionally, you can use the export-import APIs, see Migrate Metadata from the Primary Instance .Monitor Your Instances Regularly monitor the health of your active Oracle Integration instances.You can use the OCI health-check service or a third-party monitoring service.Additionally, define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Learn how to manually switch to the DR environment.To switch from your primary instance to the standby instance during outages: 1.Stop the primary Oracle Integration instance from the Oracle Cloud Infrastructure Console.2.Prepare your secondary instance.a.If you are not using CICD, then ensure that the standby (secondary) instance contains the latest versions of integrations.You can use the import API to import the latest snapshot extracted.b.Activate all relevant integrations.c.Update the scheduled parameters with the latest values to avoid reprocessing of old data.3.Update the DNS record at your DNS provider or in the OCI DNS zone to route the traffic to the standby instance.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance. |
To update an integration in the standby instance, see Update Scheduled Integration Parameters .After a failover, you may have to manually update the parameter values to avoid reprocessing of old data.Chapter 3 Perform Post-Configuration Tasks 3-9Note: Optionally, you can use the export-import APIs, see Migrate Metadata from the Primary Instance .Monitor Your Instances Regularly monitor the health of your active Oracle Integration instances.You can use the OCI health-check service or a third-party monitoring service.Additionally, define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Learn how to manually switch to the DR environment.To switch from your primary instance to the standby instance during outages: 1.Stop the primary Oracle Integration instance from the Oracle Cloud Infrastructure Console.2.Prepare your secondary instance.a.If you are not using CICD, then ensure that the standby (secondary) instance contains the latest versions of integrations.You can use the import API to import the latest snapshot extracted.b.Activate all relevant integrations.c.Update the scheduled parameters with the latest values to avoid reprocessing of old data.3.Update the DNS record at your DNS provider or in the OCI DNS zone to route the traffic to the standby instance.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Note: If your original primary instance restarts itself after the failover process, deactivate or shut down scheduled and polling-based integrations. |
After a failover, you may have to manually update the parameter values to avoid reprocessing of old data.Chapter 3 Perform Post-Configuration Tasks 3-9Note: Optionally, you can use the export-import APIs, see Migrate Metadata from the Primary Instance .Monitor Your Instances Regularly monitor the health of your active Oracle Integration instances.You can use the OCI health-check service or a third-party monitoring service.Additionally, define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Learn how to manually switch to the DR environment.To switch from your primary instance to the standby instance during outages: 1.Stop the primary Oracle Integration instance from the Oracle Cloud Infrastructure Console.2.Prepare your secondary instance.a.If you are not using CICD, then ensure that the standby (secondary) instance contains the latest versions of integrations.You can use the import API to import the latest snapshot extracted.b.Activate all relevant integrations.c.Update the scheduled parameters with the latest values to avoid reprocessing of old data.3.Update the DNS record at your DNS provider or in the OCI DNS zone to route the traffic to the standby instance.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Note: If your original primary instance restarts itself after the failover process, deactivate or shut down scheduled and polling-based integrations.If there are backlogs (of asynchronous transactions) in the original primary instance, these may be triggered when the instance restarts, resulting in duplicate transactions. |
Monitor Your Instances Regularly monitor the health of your active Oracle Integration instances.You can use the OCI health-check service or a third-party monitoring service.Additionally, define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Learn how to manually switch to the DR environment.To switch from your primary instance to the standby instance during outages: 1.Stop the primary Oracle Integration instance from the Oracle Cloud Infrastructure Console.2.Prepare your secondary instance.a.If you are not using CICD, then ensure that the standby (secondary) instance contains the latest versions of integrations.You can use the import API to import the latest snapshot extracted.b.Activate all relevant integrations.c.Update the scheduled parameters with the latest values to avoid reprocessing of old data.3.Update the DNS record at your DNS provider or in the OCI DNS zone to route the traffic to the standby instance.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Note: If your original primary instance restarts itself after the failover process, deactivate or shut down scheduled and polling-based integrations.If there are backlogs (of asynchronous transactions) in the original primary instance, these may be triggered when the instance restarts, resulting in duplicate transactions.The backlogs belong to the faulted instances of integrations. |
You can use the OCI health-check service or a third-party monitoring service.Additionally, define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Learn how to manually switch to the DR environment.To switch from your primary instance to the standby instance during outages: 1.Stop the primary Oracle Integration instance from the Oracle Cloud Infrastructure Console.2.Prepare your secondary instance.a.If you are not using CICD, then ensure that the standby (secondary) instance contains the latest versions of integrations.You can use the import API to import the latest snapshot extracted.b.Activate all relevant integrations.c.Update the scheduled parameters with the latest values to avoid reprocessing of old data.3.Update the DNS record at your DNS provider or in the OCI DNS zone to route the traffic to the standby instance.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Note: If your original primary instance restarts itself after the failover process, deactivate or shut down scheduled and polling-based integrations.If there are backlogs (of asynchronous transactions) in the original primary instance, these may be triggered when the instance restarts, resulting in duplicate transactions.The backlogs belong to the faulted instances of integrations.You can choose how you handle them. |
Additionally, define a process to identify outages and, subsequently, trigger failovers.Execute Failover Tasks Learn how to manually switch to the DR environment.To switch from your primary instance to the standby instance during outages: 1.Stop the primary Oracle Integration instance from the Oracle Cloud Infrastructure Console.2.Prepare your secondary instance.a.If you are not using CICD, then ensure that the standby (secondary) instance contains the latest versions of integrations.You can use the import API to import the latest snapshot extracted.b.Activate all relevant integrations.c.Update the scheduled parameters with the latest values to avoid reprocessing of old data.3.Update the DNS record at your DNS provider or in the OCI DNS zone to route the traffic to the standby instance.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Note: If your original primary instance restarts itself after the failover process, deactivate or shut down scheduled and polling-based integrations.If there are backlogs (of asynchronous transactions) in the original primary instance, these may be triggered when the instance restarts, resulting in duplicate transactions.The backlogs belong to the faulted instances of integrations.You can choose how you handle them.See Set Data Retention for Runtime Instances in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 Execute Failover Tasks 3-104 Disaster Recovery for File Server Learn about the architecture, prerequisites, and the procedure required to setup the Disaster Recovery solution for the File Server feature in Oracle Integration Topics: Architecture Prerequisites Set Up the Disaster Recovery Solution for File Server Perform Post-Configuration Tasks Architecture The DR architecture for File Server is similar to the Integrations DR topology. |
Execute Failover Tasks Learn how to manually switch to the DR environment.To switch from your primary instance to the standby instance during outages: 1.Stop the primary Oracle Integration instance from the Oracle Cloud Infrastructure Console.2.Prepare your secondary instance.a.If you are not using CICD, then ensure that the standby (secondary) instance contains the latest versions of integrations.You can use the import API to import the latest snapshot extracted.b.Activate all relevant integrations.c.Update the scheduled parameters with the latest values to avoid reprocessing of old data.3.Update the DNS record at your DNS provider or in the OCI DNS zone to route the traffic to the standby instance.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Note: If your original primary instance restarts itself after the failover process, deactivate or shut down scheduled and polling-based integrations.If there are backlogs (of asynchronous transactions) in the original primary instance, these may be triggered when the instance restarts, resulting in duplicate transactions.The backlogs belong to the faulted instances of integrations.You can choose how you handle them.See Set Data Retention for Runtime Instances in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 Execute Failover Tasks 3-104 Disaster Recovery for File Server Learn about the architecture, prerequisites, and the procedure required to setup the Disaster Recovery solution for the File Server feature in Oracle Integration Topics: Architecture Prerequisites Set Up the Disaster Recovery Solution for File Server Perform Post-Configuration Tasks Architecture The DR architecture for File Server is similar to the Integrations DR topology.It consists of two File Server instances (designated as primary and secondary) in two different cloud regions, which are accessed using a single custom endpoint. |
To switch from your primary instance to the standby instance during outages: 1.Stop the primary Oracle Integration instance from the Oracle Cloud Infrastructure Console.2.Prepare your secondary instance.a.If you are not using CICD, then ensure that the standby (secondary) instance contains the latest versions of integrations.You can use the import API to import the latest snapshot extracted.b.Activate all relevant integrations.c.Update the scheduled parameters with the latest values to avoid reprocessing of old data.3.Update the DNS record at your DNS provider or in the OCI DNS zone to route the traffic to the standby instance.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Note: If your original primary instance restarts itself after the failover process, deactivate or shut down scheduled and polling-based integrations.If there are backlogs (of asynchronous transactions) in the original primary instance, these may be triggered when the instance restarts, resulting in duplicate transactions.The backlogs belong to the faulted instances of integrations.You can choose how you handle them.See Set Data Retention for Runtime Instances in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 Execute Failover Tasks 3-104 Disaster Recovery for File Server Learn about the architecture, prerequisites, and the procedure required to setup the Disaster Recovery solution for the File Server feature in Oracle Integration Topics: Architecture Prerequisites Set Up the Disaster Recovery Solution for File Server Perform Post-Configuration Tasks Architecture The DR architecture for File Server is similar to the Integrations DR topology.It consists of two File Server instances (designated as primary and secondary) in two different cloud regions, which are accessed using a single custom endpoint.It also includes two public load balancers, one for each File Server instance, that direct traffic from the internet to the respective instances. |
2.Prepare your secondary instance.a.If you are not using CICD, then ensure that the standby (secondary) instance contains the latest versions of integrations.You can use the import API to import the latest snapshot extracted.b.Activate all relevant integrations.c.Update the scheduled parameters with the latest values to avoid reprocessing of old data.3.Update the DNS record at your DNS provider or in the OCI DNS zone to route the traffic to the standby instance.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Note: If your original primary instance restarts itself after the failover process, deactivate or shut down scheduled and polling-based integrations.If there are backlogs (of asynchronous transactions) in the original primary instance, these may be triggered when the instance restarts, resulting in duplicate transactions.The backlogs belong to the faulted instances of integrations.You can choose how you handle them.See Set Data Retention for Runtime Instances in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 Execute Failover Tasks 3-104 Disaster Recovery for File Server Learn about the architecture, prerequisites, and the procedure required to setup the Disaster Recovery solution for the File Server feature in Oracle Integration Topics: Architecture Prerequisites Set Up the Disaster Recovery Solution for File Server Perform Post-Configuration Tasks Architecture The DR architecture for File Server is similar to the Integrations DR topology.It consists of two File Server instances (designated as primary and secondary) in two different cloud regions, which are accessed using a single custom endpoint.It also includes two public load balancers, one for each File Server instance, that direct traffic from the internet to the respective instances.Optionally, you can use an OCI DNS zone as a front-end to route traffic to the load balancers. |
a.If you are not using CICD, then ensure that the standby (secondary) instance contains the latest versions of integrations.You can use the import API to import the latest snapshot extracted.b.Activate all relevant integrations.c.Update the scheduled parameters with the latest values to avoid reprocessing of old data.3.Update the DNS record at your DNS provider or in the OCI DNS zone to route the traffic to the standby instance.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Note: If your original primary instance restarts itself after the failover process, deactivate or shut down scheduled and polling-based integrations.If there are backlogs (of asynchronous transactions) in the original primary instance, these may be triggered when the instance restarts, resulting in duplicate transactions.The backlogs belong to the faulted instances of integrations.You can choose how you handle them.See Set Data Retention for Runtime Instances in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 Execute Failover Tasks 3-104 Disaster Recovery for File Server Learn about the architecture, prerequisites, and the procedure required to setup the Disaster Recovery solution for the File Server feature in Oracle Integration Topics: Architecture Prerequisites Set Up the Disaster Recovery Solution for File Server Perform Post-Configuration Tasks Architecture The DR architecture for File Server is similar to the Integrations DR topology.It consists of two File Server instances (designated as primary and secondary) in two different cloud regions, which are accessed using a single custom endpoint.It also includes two public load balancers, one for each File Server instance, that direct traffic from the internet to the respective instances.Optionally, you can use an OCI DNS zone as a front-end to route traffic to the load balancers.The following image shows the architecture in detail: 4-1 Chapter 4 Architecture 4-2You must implement CICD to keep the users and folder data synchronized at all times between the two sites. |
You can use the import API to import the latest snapshot extracted.b.Activate all relevant integrations.c.Update the scheduled parameters with the latest values to avoid reprocessing of old data.3.Update the DNS record at your DNS provider or in the OCI DNS zone to route the traffic to the standby instance.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Note: If your original primary instance restarts itself after the failover process, deactivate or shut down scheduled and polling-based integrations.If there are backlogs (of asynchronous transactions) in the original primary instance, these may be triggered when the instance restarts, resulting in duplicate transactions.The backlogs belong to the faulted instances of integrations.You can choose how you handle them.See Set Data Retention for Runtime Instances in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 Execute Failover Tasks 3-104 Disaster Recovery for File Server Learn about the architecture, prerequisites, and the procedure required to setup the Disaster Recovery solution for the File Server feature in Oracle Integration Topics: Architecture Prerequisites Set Up the Disaster Recovery Solution for File Server Perform Post-Configuration Tasks Architecture The DR architecture for File Server is similar to the Integrations DR topology.It consists of two File Server instances (designated as primary and secondary) in two different cloud regions, which are accessed using a single custom endpoint.It also includes two public load balancers, one for each File Server instance, that direct traffic from the internet to the respective instances.Optionally, you can use an OCI DNS zone as a front-end to route traffic to the load balancers.The following image shows the architecture in detail: 4-1 Chapter 4 Architecture 4-2You must implement CICD to keep the users and folder data synchronized at all times between the two sites.During a failover, you must update the DNS record at your DNS provider or in the OCI DNS zone to switch between File Server instances. |
b.Activate all relevant integrations.c.Update the scheduled parameters with the latest values to avoid reprocessing of old data.3.Update the DNS record at your DNS provider or in the OCI DNS zone to route the traffic to the standby instance.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Note: If your original primary instance restarts itself after the failover process, deactivate or shut down scheduled and polling-based integrations.If there are backlogs (of asynchronous transactions) in the original primary instance, these may be triggered when the instance restarts, resulting in duplicate transactions.The backlogs belong to the faulted instances of integrations.You can choose how you handle them.See Set Data Retention for Runtime Instances in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 Execute Failover Tasks 3-104 Disaster Recovery for File Server Learn about the architecture, prerequisites, and the procedure required to setup the Disaster Recovery solution for the File Server feature in Oracle Integration Topics: Architecture Prerequisites Set Up the Disaster Recovery Solution for File Server Perform Post-Configuration Tasks Architecture The DR architecture for File Server is similar to the Integrations DR topology.It consists of two File Server instances (designated as primary and secondary) in two different cloud regions, which are accessed using a single custom endpoint.It also includes two public load balancers, one for each File Server instance, that direct traffic from the internet to the respective instances.Optionally, you can use an OCI DNS zone as a front-end to route traffic to the load balancers.The following image shows the architecture in detail: 4-1 Chapter 4 Architecture 4-2You must implement CICD to keep the users and folder data synchronized at all times between the two sites.During a failover, you must update the DNS record at your DNS provider or in the OCI DNS zone to switch between File Server instances.Prerequisites Ensure that all prerequisites for the File Server DR solution are met before you begin the configuration process. |
c.Update the scheduled parameters with the latest values to avoid reprocessing of old data.3.Update the DNS record at your DNS provider or in the OCI DNS zone to route the traffic to the standby instance.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Note: If your original primary instance restarts itself after the failover process, deactivate or shut down scheduled and polling-based integrations.If there are backlogs (of asynchronous transactions) in the original primary instance, these may be triggered when the instance restarts, resulting in duplicate transactions.The backlogs belong to the faulted instances of integrations.You can choose how you handle them.See Set Data Retention for Runtime Instances in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 Execute Failover Tasks 3-104 Disaster Recovery for File Server Learn about the architecture, prerequisites, and the procedure required to setup the Disaster Recovery solution for the File Server feature in Oracle Integration Topics: Architecture Prerequisites Set Up the Disaster Recovery Solution for File Server Perform Post-Configuration Tasks Architecture The DR architecture for File Server is similar to the Integrations DR topology.It consists of two File Server instances (designated as primary and secondary) in two different cloud regions, which are accessed using a single custom endpoint.It also includes two public load balancers, one for each File Server instance, that direct traffic from the internet to the respective instances.Optionally, you can use an OCI DNS zone as a front-end to route traffic to the load balancers.The following image shows the architecture in detail: 4-1 Chapter 4 Architecture 4-2You must implement CICD to keep the users and folder data synchronized at all times between the two sites.During a failover, you must update the DNS record at your DNS provider or in the OCI DNS zone to switch between File Server instances.Prerequisites Ensure that all prerequisites for the File Server DR solution are met before you begin the configuration process.Before you begin the disaster recovery configuration process for File Server, you must: Create two Oracle Integration instances in two different OCI regions. |
3.Update the DNS record at your DNS provider or in the OCI DNS zone to route the traffic to the standby instance.After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Note: If your original primary instance restarts itself after the failover process, deactivate or shut down scheduled and polling-based integrations.If there are backlogs (of asynchronous transactions) in the original primary instance, these may be triggered when the instance restarts, resulting in duplicate transactions.The backlogs belong to the faulted instances of integrations.You can choose how you handle them.See Set Data Retention for Runtime Instances in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 Execute Failover Tasks 3-104 Disaster Recovery for File Server Learn about the architecture, prerequisites, and the procedure required to setup the Disaster Recovery solution for the File Server feature in Oracle Integration Topics: Architecture Prerequisites Set Up the Disaster Recovery Solution for File Server Perform Post-Configuration Tasks Architecture The DR architecture for File Server is similar to the Integrations DR topology.It consists of two File Server instances (designated as primary and secondary) in two different cloud regions, which are accessed using a single custom endpoint.It also includes two public load balancers, one for each File Server instance, that direct traffic from the internet to the respective instances.Optionally, you can use an OCI DNS zone as a front-end to route traffic to the load balancers.The following image shows the architecture in detail: 4-1 Chapter 4 Architecture 4-2You must implement CICD to keep the users and folder data synchronized at all times between the two sites.During a failover, you must update the DNS record at your DNS provider or in the OCI DNS zone to switch between File Server instances.Prerequisites Ensure that all prerequisites for the File Server DR solution are met before you begin the configuration process.Before you begin the disaster recovery configuration process for File Server, you must: Create two Oracle Integration instances in two different OCI regions.If youve already created these instances while configuring the Integrations DR, you can use the same instances. |
After the failover process, the standby instance becomes your primary instance, and the instance previously designated as primary becomes the new standby instance.Note: If your original primary instance restarts itself after the failover process, deactivate or shut down scheduled and polling-based integrations.If there are backlogs (of asynchronous transactions) in the original primary instance, these may be triggered when the instance restarts, resulting in duplicate transactions.The backlogs belong to the faulted instances of integrations.You can choose how you handle them.See Set Data Retention for Runtime Instances in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 Execute Failover Tasks 3-104 Disaster Recovery for File Server Learn about the architecture, prerequisites, and the procedure required to setup the Disaster Recovery solution for the File Server feature in Oracle Integration Topics: Architecture Prerequisites Set Up the Disaster Recovery Solution for File Server Perform Post-Configuration Tasks Architecture The DR architecture for File Server is similar to the Integrations DR topology.It consists of two File Server instances (designated as primary and secondary) in two different cloud regions, which are accessed using a single custom endpoint.It also includes two public load balancers, one for each File Server instance, that direct traffic from the internet to the respective instances.Optionally, you can use an OCI DNS zone as a front-end to route traffic to the load balancers.The following image shows the architecture in detail: 4-1 Chapter 4 Architecture 4-2You must implement CICD to keep the users and folder data synchronized at all times between the two sites.During a failover, you must update the DNS record at your DNS provider or in the OCI DNS zone to switch between File Server instances.Prerequisites Ensure that all prerequisites for the File Server DR solution are met before you begin the configuration process.Before you begin the disaster recovery configuration process for File Server, you must: Create two Oracle Integration instances in two different OCI regions.If youve already created these instances while configuring the Integrations DR, you can use the same instances.Enable File Server on both the Oracle Integration instances. |
Note: If your original primary instance restarts itself after the failover process, deactivate or shut down scheduled and polling-based integrations.If there are backlogs (of asynchronous transactions) in the original primary instance, these may be triggered when the instance restarts, resulting in duplicate transactions.The backlogs belong to the faulted instances of integrations.You can choose how you handle them.See Set Data Retention for Runtime Instances in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 Execute Failover Tasks 3-104 Disaster Recovery for File Server Learn about the architecture, prerequisites, and the procedure required to setup the Disaster Recovery solution for the File Server feature in Oracle Integration Topics: Architecture Prerequisites Set Up the Disaster Recovery Solution for File Server Perform Post-Configuration Tasks Architecture The DR architecture for File Server is similar to the Integrations DR topology.It consists of two File Server instances (designated as primary and secondary) in two different cloud regions, which are accessed using a single custom endpoint.It also includes two public load balancers, one for each File Server instance, that direct traffic from the internet to the respective instances.Optionally, you can use an OCI DNS zone as a front-end to route traffic to the load balancers.The following image shows the architecture in detail: 4-1 Chapter 4 Architecture 4-2You must implement CICD to keep the users and folder data synchronized at all times between the two sites.During a failover, you must update the DNS record at your DNS provider or in the OCI DNS zone to switch between File Server instances.Prerequisites Ensure that all prerequisites for the File Server DR solution are met before you begin the configuration process.Before you begin the disaster recovery configuration process for File Server, you must: Create two Oracle Integration instances in two different OCI regions.If youve already created these instances while configuring the Integrations DR, you can use the same instances.Enable File Server on both the Oracle Integration instances.See Enable File Server in Using File Server in Oracle Integration Generation 2 . |
If there are backlogs (of asynchronous transactions) in the original primary instance, these may be triggered when the instance restarts, resulting in duplicate transactions.The backlogs belong to the faulted instances of integrations.You can choose how you handle them.See Set Data Retention for Runtime Instances in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 Execute Failover Tasks 3-104 Disaster Recovery for File Server Learn about the architecture, prerequisites, and the procedure required to setup the Disaster Recovery solution for the File Server feature in Oracle Integration Topics: Architecture Prerequisites Set Up the Disaster Recovery Solution for File Server Perform Post-Configuration Tasks Architecture The DR architecture for File Server is similar to the Integrations DR topology.It consists of two File Server instances (designated as primary and secondary) in two different cloud regions, which are accessed using a single custom endpoint.It also includes two public load balancers, one for each File Server instance, that direct traffic from the internet to the respective instances.Optionally, you can use an OCI DNS zone as a front-end to route traffic to the load balancers.The following image shows the architecture in detail: 4-1 Chapter 4 Architecture 4-2You must implement CICD to keep the users and folder data synchronized at all times between the two sites.During a failover, you must update the DNS record at your DNS provider or in the OCI DNS zone to switch between File Server instances.Prerequisites Ensure that all prerequisites for the File Server DR solution are met before you begin the configuration process.Before you begin the disaster recovery configuration process for File Server, you must: Create two Oracle Integration instances in two different OCI regions.If youve already created these instances while configuring the Integrations DR, you can use the same instances.Enable File Server on both the Oracle Integration instances.See Enable File Server in Using File Server in Oracle Integration Generation 2 .Note the public IP address and port number of each File Server instance. |
The backlogs belong to the faulted instances of integrations.You can choose how you handle them.See Set Data Retention for Runtime Instances in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 Execute Failover Tasks 3-104 Disaster Recovery for File Server Learn about the architecture, prerequisites, and the procedure required to setup the Disaster Recovery solution for the File Server feature in Oracle Integration Topics: Architecture Prerequisites Set Up the Disaster Recovery Solution for File Server Perform Post-Configuration Tasks Architecture The DR architecture for File Server is similar to the Integrations DR topology.It consists of two File Server instances (designated as primary and secondary) in two different cloud regions, which are accessed using a single custom endpoint.It also includes two public load balancers, one for each File Server instance, that direct traffic from the internet to the respective instances.Optionally, you can use an OCI DNS zone as a front-end to route traffic to the load balancers.The following image shows the architecture in detail: 4-1 Chapter 4 Architecture 4-2You must implement CICD to keep the users and folder data synchronized at all times between the two sites.During a failover, you must update the DNS record at your DNS provider or in the OCI DNS zone to switch between File Server instances.Prerequisites Ensure that all prerequisites for the File Server DR solution are met before you begin the configuration process.Before you begin the disaster recovery configuration process for File Server, you must: Create two Oracle Integration instances in two different OCI regions.If youve already created these instances while configuring the Integrations DR, you can use the same instances.Enable File Server on both the Oracle Integration instances.See Enable File Server in Using File Server in Oracle Integration Generation 2 .Note the public IP address and port number of each File Server instance.Create the following resources for public load balancers in both the OCI regions: A Virtual Cloud Network (VCN) and an internet gateway. |
You can choose how you handle them.See Set Data Retention for Runtime Instances in Provisioning and Administering Oracle Integration Generation 2 .Chapter 3 Execute Failover Tasks 3-104 Disaster Recovery for File Server Learn about the architecture, prerequisites, and the procedure required to setup the Disaster Recovery solution for the File Server feature in Oracle Integration Topics: Architecture Prerequisites Set Up the Disaster Recovery Solution for File Server Perform Post-Configuration Tasks Architecture The DR architecture for File Server is similar to the Integrations DR topology.It consists of two File Server instances (designated as primary and secondary) in two different cloud regions, which are accessed using a single custom endpoint.It also includes two public load balancers, one for each File Server instance, that direct traffic from the internet to the respective instances.Optionally, you can use an OCI DNS zone as a front-end to route traffic to the load balancers.The following image shows the architecture in detail: 4-1 Chapter 4 Architecture 4-2You must implement CICD to keep the users and folder data synchronized at all times between the two sites.During a failover, you must update the DNS record at your DNS provider or in the OCI DNS zone to switch between File Server instances.Prerequisites Ensure that all prerequisites for the File Server DR solution are met before you begin the configuration process.Before you begin the disaster recovery configuration process for File Server, you must: Create two Oracle Integration instances in two different OCI regions.If youve already created these instances while configuring the Integrations DR, you can use the same instances.Enable File Server on both the Oracle Integration instances.See Enable File Server in Using File Server in Oracle Integration Generation 2 .Note the public IP address and port number of each File Server instance.Create the following resources for public load balancers in both the OCI regions: A Virtual Cloud Network (VCN) and an internet gateway.A public regional subnet in the VCN, with an associated security list and a route table. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.