text
stringlengths 65
20k
|
|---|
Conjunction Select the logical operator for grouping together the smaller condition elements.And: Both search conditions must be met for the document to be returned.Or: Either condition must be met for the document to be returned.Click to remove the selected condition.Test Get Operation Click to validate the query/ template parameters against the Magento application.The query response is displayed for a successful query and the response fields are displayed accordingly in the response schema.Note: The Test Get operation fetches a maximum of three results.The store ID cannot be a parameter in the Test Get operation unless it is already a query parameter.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-4Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2 F24348-03 December 2022 Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2, F24348-03 Copyright 2022, Oracle and/or its affiliates. |
And: Both search conditions must be met for the document to be returned.Or: Either condition must be met for the document to be returned.Click to remove the selected condition.Test Get Operation Click to validate the query/ template parameters against the Magento application.The query response is displayed for a successful query and the response fields are displayed accordingly in the response schema.Note: The Test Get operation fetches a maximum of three results.The store ID cannot be a parameter in the Test Get operation unless it is already a query parameter.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-4Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2 F24348-03 December 2022 Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2, F24348-03 Copyright 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. |
Or: Either condition must be met for the document to be returned.Click to remove the selected condition.Test Get Operation Click to validate the query/ template parameters against the Magento application.The query response is displayed for a successful query and the response fields are displayed accordingly in the response schema.Note: The Test Get operation fetches a maximum of three results.The store ID cannot be a parameter in the Test Get operation unless it is already a query parameter.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-4Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2 F24348-03 December 2022 Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2, F24348-03 Copyright 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. |
Click to remove the selected condition.Test Get Operation Click to validate the query/ template parameters against the Magento application.The query response is displayed for a successful query and the response fields are displayed accordingly in the response schema.Note: The Test Get operation fetches a maximum of three results.The store ID cannot be a parameter in the Test Get operation unless it is already a query parameter.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-4Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2 F24348-03 December 2022 Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2, F24348-03 Copyright 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. |
Test Get Operation Click to validate the query/ template parameters against the Magento application.The query response is displayed for a successful query and the response fields are displayed accordingly in the response schema.Note: The Test Get operation fetches a maximum of three results.The store ID cannot be a parameter in the Test Get operation unless it is already a query parameter.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-4Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2 F24348-03 December 2022 Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2, F24348-03 Copyright 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free. |
The query response is displayed for a successful query and the response fields are displayed accordingly in the response schema.Note: The Test Get operation fetches a maximum of three results.The store ID cannot be a parameter in the Test Get operation unless it is already a query parameter.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-4Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2 F24348-03 December 2022 Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2, F24348-03 Copyright 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing. |
Note: The Test Get operation fetches a maximum of three results.The store ID cannot be a parameter in the Test Get operation unless it is already a query parameter.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-4Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2 F24348-03 December 2022 Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2, F24348-03 Copyright 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. |
The store ID cannot be a parameter in the Test Get operation unless it is already a query parameter.Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-4Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2 F24348-03 December 2022 Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2, F24348-03 Copyright 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. |
Summary Page You can review the specified adapter configuration values on the Summary page.Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-4Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2 F24348-03 December 2022 Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2, F24348-03 Copyright 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services. |
Element Description Summary Displays a summary of the configuration values you defined on previous pages of the wizard.The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-4Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2 F24348-03 December 2022 Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2, F24348-03 Copyright 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government. |
The information that is displayed can vary by adapter.For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-4Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2 F24348-03 December 2022 Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2, F24348-03 Copyright 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications. |
For some adapters, the selected business objects and operation name are displayed.For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-4Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2 F24348-03 December 2022 Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2, F24348-03 Copyright 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. |
For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-4Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2 F24348-03 December 2022 Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2, F24348-03 Copyright 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. |
To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-4Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2 F24348-03 December 2022 Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2, F24348-03 Copyright 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. |
To cancel your configuration details, click Cancel.Chapter 3 Summary Page 3-4Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2 F24348-03 December 2022 Oracle Cloud Configuring a Disaster Recovery Solution for Oracle Integration Generation 2, F24348-03 Copyright 2022, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates. |
Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners. |
Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. |
Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. |
The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group. |
If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties. |
If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. |
As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Introduction Disaster Recovery Concepts 1-1 2 About the Solution Scope Whats Supported? |
The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Introduction Disaster Recovery Concepts 1-1 2 About the Solution Scope Whats Supported?2-1 Whats Not Supported? |
No other rights are granted to the U.S. Government.This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Introduction Disaster Recovery Concepts 1-1 2 About the Solution Scope Whats Supported?2-1 Whats Not Supported?2-1 3 Disaster Recovery for Integrations Architecture 3-1 Key Considerations 3-2 Prerequisites 3-3 Set Up the Disaster Recovery Solution for Integrations 3-3 Configure a Custom Endpoint 3-4 Use an OCI DNS Management Zone 3-4 Migrate Metadata from the Primary Instance 3-5 Perform Post-Configuration Tasks 3-8 Automate Metadata Synchronization 3-9 Automate Scheduled Parameters Updates 3-9 Monitor Your Instances 3-10 Execute Failover Tasks 3-10 iii4 Disaster Recovery for File Server Architecture 4-1 Prerequisites 4-3 Set Up the Disaster Recovery Solution for File Server 4-3 Create Load Balancers 4-3 Configure Custom Hostnames for Load Balancers 4-5 Configure a Common Custom Endpoint 4-5 Perform Post-Configuration Tasks 4-6 Automate Metadata Synchronization 4-6 Monitor Your Instances 4-6 Execute Failover Tasks 4-7 ivPreface This document describes how to configure a disaster recovery solution for Oracle Integration. |
This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Introduction Disaster Recovery Concepts 1-1 2 About the Solution Scope Whats Supported?2-1 Whats Not Supported?2-1 3 Disaster Recovery for Integrations Architecture 3-1 Key Considerations 3-2 Prerequisites 3-3 Set Up the Disaster Recovery Solution for Integrations 3-3 Configure a Custom Endpoint 3-4 Use an OCI DNS Management Zone 3-4 Migrate Metadata from the Primary Instance 3-5 Perform Post-Configuration Tasks 3-8 Automate Metadata Synchronization 3-9 Automate Scheduled Parameters Updates 3-9 Monitor Your Instances 3-10 Execute Failover Tasks 3-10 iii4 Disaster Recovery for File Server Architecture 4-1 Prerequisites 4-3 Set Up the Disaster Recovery Solution for File Server 4-3 Create Load Balancers 4-3 Configure Custom Hostnames for Load Balancers 4-5 Configure a Common Custom Endpoint 4-5 Perform Post-Configuration Tasks 4-6 Automate Metadata Synchronization 4-6 Monitor Your Instances 4-6 Execute Failover Tasks 4-7 ivPreface This document describes how to configure a disaster recovery solution for Oracle Integration.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This document is intended for personnel who are responsible for configuring a disaster recovery solution for Oracle Integration. |
It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury.If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Introduction Disaster Recovery Concepts 1-1 2 About the Solution Scope Whats Supported?2-1 Whats Not Supported?2-1 3 Disaster Recovery for Integrations Architecture 3-1 Key Considerations 3-2 Prerequisites 3-3 Set Up the Disaster Recovery Solution for Integrations 3-3 Configure a Custom Endpoint 3-4 Use an OCI DNS Management Zone 3-4 Migrate Metadata from the Primary Instance 3-5 Perform Post-Configuration Tasks 3-8 Automate Metadata Synchronization 3-9 Automate Scheduled Parameters Updates 3-9 Monitor Your Instances 3-10 Execute Failover Tasks 3-10 iii4 Disaster Recovery for File Server Architecture 4-1 Prerequisites 4-3 Set Up the Disaster Recovery Solution for File Server 4-3 Create Load Balancers 4-3 Configure Custom Hostnames for Load Balancers 4-5 Configure a Common Custom Endpoint 4-5 Perform Post-Configuration Tasks 4-6 Automate Metadata Synchronization 4-6 Monitor Your Instances 4-6 Execute Failover Tasks 4-7 ivPreface This document describes how to configure a disaster recovery solution for Oracle Integration.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This document is intended for personnel who are responsible for configuring a disaster recovery solution for Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc . |
If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Introduction Disaster Recovery Concepts 1-1 2 About the Solution Scope Whats Supported?2-1 Whats Not Supported?2-1 3 Disaster Recovery for Integrations Architecture 3-1 Key Considerations 3-2 Prerequisites 3-3 Set Up the Disaster Recovery Solution for Integrations 3-3 Configure a Custom Endpoint 3-4 Use an OCI DNS Management Zone 3-4 Migrate Metadata from the Primary Instance 3-5 Perform Post-Configuration Tasks 3-8 Automate Metadata Synchronization 3-9 Automate Scheduled Parameters Updates 3-9 Monitor Your Instances 3-10 Execute Failover Tasks 3-10 iii4 Disaster Recovery for File Server Architecture 4-1 Prerequisites 4-3 Set Up the Disaster Recovery Solution for File Server 4-3 Create Load Balancers 4-3 Configure Custom Hostnames for Load Balancers 4-5 Configure a Common Custom Endpoint 4-5 Perform Post-Configuration Tasks 4-6 Automate Metadata Synchronization 4-6 Monitor Your Instances 4-6 Execute Failover Tasks 4-7 ivPreface This document describes how to configure a disaster recovery solution for Oracle Integration.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This document is intended for personnel who are responsible for configuring a disaster recovery solution for Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support. |
Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Introduction Disaster Recovery Concepts 1-1 2 About the Solution Scope Whats Supported?2-1 Whats Not Supported?2-1 3 Disaster Recovery for Integrations Architecture 3-1 Key Considerations 3-2 Prerequisites 3-3 Set Up the Disaster Recovery Solution for Integrations 3-3 Configure a Custom Endpoint 3-4 Use an OCI DNS Management Zone 3-4 Migrate Metadata from the Primary Instance 3-5 Perform Post-Configuration Tasks 3-8 Automate Metadata Synchronization 3-9 Automate Scheduled Parameters Updates 3-9 Monitor Your Instances 3-10 Execute Failover Tasks 3-10 iii4 Disaster Recovery for File Server Architecture 4-1 Prerequisites 4-3 Set Up the Disaster Recovery Solution for File Server 4-3 Create Load Balancers 4-3 Configure Custom Hostnames for Load Balancers 4-5 Configure a Common Custom Endpoint 4-5 Perform Post-Configuration Tasks 4-6 Automate Metadata Synchronization 4-6 Monitor Your Instances 4-6 Execute Failover Tasks 4-7 ivPreface This document describes how to configure a disaster recovery solution for Oracle Integration.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This document is intended for personnel who are responsible for configuring a disaster recovery solution for Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup? |
Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Introduction Disaster Recovery Concepts 1-1 2 About the Solution Scope Whats Supported?2-1 Whats Not Supported?2-1 3 Disaster Recovery for Integrations Architecture 3-1 Key Considerations 3-2 Prerequisites 3-3 Set Up the Disaster Recovery Solution for Integrations 3-3 Configure a Custom Endpoint 3-4 Use an OCI DNS Management Zone 3-4 Migrate Metadata from the Primary Instance 3-5 Perform Post-Configuration Tasks 3-8 Automate Metadata Synchronization 3-9 Automate Scheduled Parameters Updates 3-9 Monitor Your Instances 3-10 Execute Failover Tasks 3-10 iii4 Disaster Recovery for File Server Architecture 4-1 Prerequisites 4-3 Set Up the Disaster Recovery Solution for File Server 4-3 Create Load Balancers 4-3 Configure Custom Hostnames for Load Balancers 4-5 Configure a Common Custom Endpoint 4-5 Perform Post-Configuration Tasks 4-6 Automate Metadata Synchronization 4-6 Monitor Your Instances 4-6 Execute Failover Tasks 4-7 ivPreface This document describes how to configure a disaster recovery solution for Oracle Integration.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This document is intended for personnel who are responsible for configuring a disaster recovery solution for Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired. |
Other names may be trademarks of their respective owners.Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Introduction Disaster Recovery Concepts 1-1 2 About the Solution Scope Whats Supported?2-1 Whats Not Supported?2-1 3 Disaster Recovery for Integrations Architecture 3-1 Key Considerations 3-2 Prerequisites 3-3 Set Up the Disaster Recovery Solution for Integrations 3-3 Configure a Custom Endpoint 3-4 Use an OCI DNS Management Zone 3-4 Migrate Metadata from the Primary Instance 3-5 Perform Post-Configuration Tasks 3-8 Automate Metadata Synchronization 3-9 Automate Scheduled Parameters Updates 3-9 Monitor Your Instances 3-10 Execute Failover Tasks 3-10 iii4 Disaster Recovery for File Server Architecture 4-1 Prerequisites 4-3 Set Up the Disaster Recovery Solution for File Server 4-3 Create Load Balancers 4-3 Configure Custom Hostnames for Load Balancers 4-5 Configure a Common Custom Endpoint 4-5 Perform Post-Configuration Tasks 4-6 Automate Metadata Synchronization 4-6 Monitor Your Instances 4-6 Execute Failover Tasks 4-7 ivPreface This document describes how to configure a disaster recovery solution for Oracle Integration.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This document is intended for personnel who are responsible for configuring a disaster recovery solution for Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion. |
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation.All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Introduction Disaster Recovery Concepts 1-1 2 About the Solution Scope Whats Supported?2-1 Whats Not Supported?2-1 3 Disaster Recovery for Integrations Architecture 3-1 Key Considerations 3-2 Prerequisites 3-3 Set Up the Disaster Recovery Solution for Integrations 3-3 Configure a Custom Endpoint 3-4 Use an OCI DNS Management Zone 3-4 Migrate Metadata from the Primary Instance 3-5 Perform Post-Configuration Tasks 3-8 Automate Metadata Synchronization 3-9 Automate Scheduled Parameters Updates 3-9 Monitor Your Instances 3-10 Execute Failover Tasks 3-10 iii4 Disaster Recovery for File Server Architecture 4-1 Prerequisites 4-3 Set Up the Disaster Recovery Solution for File Server 4-3 Create Load Balancers 4-3 Configure Custom Hostnames for Load Balancers 4-5 Configure a Common Custom Endpoint 4-5 Perform Post-Configuration Tasks 4-6 Automate Metadata Synchronization 4-6 Monitor Your Instances 4-6 Execute Failover Tasks 4-7 ivPreface This document describes how to configure a disaster recovery solution for Oracle Integration.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This document is intended for personnel who are responsible for configuring a disaster recovery solution for Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation. |
All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices.UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Introduction Disaster Recovery Concepts 1-1 2 About the Solution Scope Whats Supported?2-1 Whats Not Supported?2-1 3 Disaster Recovery for Integrations Architecture 3-1 Key Considerations 3-2 Prerequisites 3-3 Set Up the Disaster Recovery Solution for Integrations 3-3 Configure a Custom Endpoint 3-4 Use an OCI DNS Management Zone 3-4 Migrate Metadata from the Primary Instance 3-5 Perform Post-Configuration Tasks 3-8 Automate Metadata Synchronization 3-9 Automate Scheduled Parameters Updates 3-9 Monitor Your Instances 3-10 Execute Failover Tasks 3-10 iii4 Disaster Recovery for File Server Architecture 4-1 Prerequisites 4-3 Set Up the Disaster Recovery Solution for File Server 4-3 Create Load Balancers 4-3 Configure Custom Hostnames for Load Balancers 4-5 Configure a Common Custom Endpoint 4-5 Perform Post-Configuration Tasks 4-6 Automate Metadata Synchronization 4-6 Monitor Your Instances 4-6 Execute Failover Tasks 4-7 ivPreface This document describes how to configure a disaster recovery solution for Oracle Integration.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This document is intended for personnel who are responsible for configuring a disaster recovery solution for Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation. |
UNIX is a registered trademark of The Open Group.This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Introduction Disaster Recovery Concepts 1-1 2 About the Solution Scope Whats Supported?2-1 Whats Not Supported?2-1 3 Disaster Recovery for Integrations Architecture 3-1 Key Considerations 3-2 Prerequisites 3-3 Set Up the Disaster Recovery Solution for Integrations 3-3 Configure a Custom Endpoint 3-4 Use an OCI DNS Management Zone 3-4 Migrate Metadata from the Primary Instance 3-5 Perform Post-Configuration Tasks 3-8 Automate Metadata Synchronization 3-9 Automate Scheduled Parameters Updates 3-9 Monitor Your Instances 3-10 Execute Failover Tasks 3-10 iii4 Disaster Recovery for File Server Architecture 4-1 Prerequisites 4-3 Set Up the Disaster Recovery Solution for File Server 4-3 Create Load Balancers 4-3 Configure Custom Hostnames for Load Balancers 4-5 Configure a Common Custom Endpoint 4-5 Perform Post-Configuration Tasks 4-6 Automate Metadata Synchronization 4-6 Monitor Your Instances 4-6 Execute Failover Tasks 4-7 ivPreface This document describes how to configure a disaster recovery solution for Oracle Integration.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This document is intended for personnel who are responsible for configuring a disaster recovery solution for Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve. |
This software or hardware and documentation may provide access to or information about content, products, and services from third parties.Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Introduction Disaster Recovery Concepts 1-1 2 About the Solution Scope Whats Supported?2-1 Whats Not Supported?2-1 3 Disaster Recovery for Integrations Architecture 3-1 Key Considerations 3-2 Prerequisites 3-3 Set Up the Disaster Recovery Solution for Integrations 3-3 Configure a Custom Endpoint 3-4 Use an OCI DNS Management Zone 3-4 Migrate Metadata from the Primary Instance 3-5 Perform Post-Configuration Tasks 3-8 Automate Metadata Synchronization 3-9 Automate Scheduled Parameters Updates 3-9 Monitor Your Instances 3-10 Execute Failover Tasks 3-10 iii4 Disaster Recovery for File Server Architecture 4-1 Prerequisites 4-3 Set Up the Disaster Recovery Solution for File Server 4-3 Create Load Balancers 4-3 Configure Custom Hostnames for Load Balancers 4-5 Configure a Common Custom Endpoint 4-5 Perform Post-Configuration Tasks 4-6 Automate Metadata Synchronization 4-6 Monitor Your Instances 4-6 Execute Failover Tasks 4-7 ivPreface This document describes how to configure a disaster recovery solution for Oracle Integration.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This document is intended for personnel who are responsible for configuring a disaster recovery solution for Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation. |
Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle.Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Introduction Disaster Recovery Concepts 1-1 2 About the Solution Scope Whats Supported?2-1 Whats Not Supported?2-1 3 Disaster Recovery for Integrations Architecture 3-1 Key Considerations 3-2 Prerequisites 3-3 Set Up the Disaster Recovery Solution for Integrations 3-3 Configure a Custom Endpoint 3-4 Use an OCI DNS Management Zone 3-4 Migrate Metadata from the Primary Instance 3-5 Perform Post-Configuration Tasks 3-8 Automate Metadata Synchronization 3-9 Automate Scheduled Parameters Updates 3-9 Monitor Your Instances 3-10 Execute Failover Tasks 3-10 iii4 Disaster Recovery for File Server Architecture 4-1 Prerequisites 4-3 Set Up the Disaster Recovery Solution for File Server 4-3 Create Load Balancers 4-3 Configure Custom Hostnames for Load Balancers 4-5 Configure a Common Custom Endpoint 4-5 Perform Post-Configuration Tasks 4-6 Automate Metadata Synchronization 4-6 Monitor Your Instances 4-6 Execute Failover Tasks 4-7 ivPreface This document describes how to configure a disaster recovery solution for Oracle Integration.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This document is intended for personnel who are responsible for configuring a disaster recovery solution for Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources For more information, see the Oracle Integration documentation in the Oracle Cloud Library on the Oracle Help Center . |
Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.Contents Preface Audience v Documentation Accessibility v Diversity and Inclusion v Related Resources vi Conventions vi 1 Introduction Disaster Recovery Concepts 1-1 2 About the Solution Scope Whats Supported?2-1 Whats Not Supported?2-1 3 Disaster Recovery for Integrations Architecture 3-1 Key Considerations 3-2 Prerequisites 3-3 Set Up the Disaster Recovery Solution for Integrations 3-3 Configure a Custom Endpoint 3-4 Use an OCI DNS Management Zone 3-4 Migrate Metadata from the Primary Instance 3-5 Perform Post-Configuration Tasks 3-8 Automate Metadata Synchronization 3-9 Automate Scheduled Parameters Updates 3-9 Monitor Your Instances 3-10 Execute Failover Tasks 3-10 iii4 Disaster Recovery for File Server Architecture 4-1 Prerequisites 4-3 Set Up the Disaster Recovery Solution for File Server 4-3 Create Load Balancers 4-3 Configure Custom Hostnames for Load Balancers 4-5 Configure a Common Custom Endpoint 4-5 Perform Post-Configuration Tasks 4-6 Automate Metadata Synchronization 4-6 Monitor Your Instances 4-6 Execute Failover Tasks 4-7 ivPreface This document describes how to configure a disaster recovery solution for Oracle Integration.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This document is intended for personnel who are responsible for configuring a disaster recovery solution for Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources For more information, see the Oracle Integration documentation in the Oracle Cloud Library on the Oracle Help Center .Conventions The following text conventions are used in this document. |
2-1 Whats Not Supported?2-1 3 Disaster Recovery for Integrations Architecture 3-1 Key Considerations 3-2 Prerequisites 3-3 Set Up the Disaster Recovery Solution for Integrations 3-3 Configure a Custom Endpoint 3-4 Use an OCI DNS Management Zone 3-4 Migrate Metadata from the Primary Instance 3-5 Perform Post-Configuration Tasks 3-8 Automate Metadata Synchronization 3-9 Automate Scheduled Parameters Updates 3-9 Monitor Your Instances 3-10 Execute Failover Tasks 3-10 iii4 Disaster Recovery for File Server Architecture 4-1 Prerequisites 4-3 Set Up the Disaster Recovery Solution for File Server 4-3 Create Load Balancers 4-3 Configure Custom Hostnames for Load Balancers 4-5 Configure a Common Custom Endpoint 4-5 Perform Post-Configuration Tasks 4-6 Automate Metadata Synchronization 4-6 Monitor Your Instances 4-6 Execute Failover Tasks 4-7 ivPreface This document describes how to configure a disaster recovery solution for Oracle Integration.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This document is intended for personnel who are responsible for configuring a disaster recovery solution for Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources For more information, see the Oracle Integration documentation in the Oracle Cloud Library on the Oracle Help Center .Conventions The following text conventions are used in this document.Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. |
2-1 3 Disaster Recovery for Integrations Architecture 3-1 Key Considerations 3-2 Prerequisites 3-3 Set Up the Disaster Recovery Solution for Integrations 3-3 Configure a Custom Endpoint 3-4 Use an OCI DNS Management Zone 3-4 Migrate Metadata from the Primary Instance 3-5 Perform Post-Configuration Tasks 3-8 Automate Metadata Synchronization 3-9 Automate Scheduled Parameters Updates 3-9 Monitor Your Instances 3-10 Execute Failover Tasks 3-10 iii4 Disaster Recovery for File Server Architecture 4-1 Prerequisites 4-3 Set Up the Disaster Recovery Solution for File Server 4-3 Create Load Balancers 4-3 Configure Custom Hostnames for Load Balancers 4-5 Configure a Common Custom Endpoint 4-5 Perform Post-Configuration Tasks 4-6 Automate Metadata Synchronization 4-6 Monitor Your Instances 4-6 Execute Failover Tasks 4-7 ivPreface This document describes how to configure a disaster recovery solution for Oracle Integration.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This document is intended for personnel who are responsible for configuring a disaster recovery solution for Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources For more information, see the Oracle Integration documentation in the Oracle Cloud Library on the Oracle Help Center .Conventions The following text conventions are used in this document.Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. |
Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience This document is intended for personnel who are responsible for configuring a disaster recovery solution for Oracle Integration.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources For more information, see the Oracle Integration documentation in the Oracle Cloud Library on the Oracle Help Center .Conventions The following text conventions are used in this document.Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Introduction Oracle Integration is available in an Oracle Cloud Infrastructure (OCI) region governed by service-level agreements (SLAs). |
Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources For more information, see the Oracle Integration documentation in the Oracle Cloud Library on the Oracle Help Center .Conventions The following text conventions are used in this document.Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Introduction Oracle Integration is available in an Oracle Cloud Infrastructure (OCI) region governed by service-level agreements (SLAs).This guide details the procedure to build a cross-region, customer-managed disaster recovery solution for Oracle Integration, specifically for the Integrations and File Server features in Oracle Integration. |
Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources For more information, see the Oracle Integration documentation in the Oracle Cloud Library on the Oracle Help Center .Conventions The following text conventions are used in this document.Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Introduction Oracle Integration is available in an Oracle Cloud Infrastructure (OCI) region governed by service-level agreements (SLAs).This guide details the procedure to build a cross-region, customer-managed disaster recovery solution for Oracle Integration, specifically for the Integrations and File Server features in Oracle Integration.Disaster Recovery Concepts A disaster recovery (DR) solution enables you to recover quickly from natural or human-made disasters and continue to provide services to your users. |
For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources For more information, see the Oracle Integration documentation in the Oracle Cloud Library on the Oracle Help Center .Conventions The following text conventions are used in this document.Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Introduction Oracle Integration is available in an Oracle Cloud Infrastructure (OCI) region governed by service-level agreements (SLAs).This guide details the procedure to build a cross-region, customer-managed disaster recovery solution for Oracle Integration, specifically for the Integrations and File Server features in Oracle Integration.Disaster Recovery Concepts A disaster recovery (DR) solution enables you to recover quickly from natural or human-made disasters and continue to provide services to your users.In addition, you can use the DR set up for planned migrations and switch between different regions periodically. |
ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources For more information, see the Oracle Integration documentation in the Oracle Cloud Library on the Oracle Help Center .Conventions The following text conventions are used in this document.Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Introduction Oracle Integration is available in an Oracle Cloud Infrastructure (OCI) region governed by service-level agreements (SLAs).This guide details the procedure to build a cross-region, customer-managed disaster recovery solution for Oracle Integration, specifically for the Integrations and File Server features in Oracle Integration.Disaster Recovery Concepts A disaster recovery (DR) solution enables you to recover quickly from natural or human-made disasters and continue to provide services to your users.In addition, you can use the DR set up for planned migrations and switch between different regions periodically.Before you set up any DR solution, you determine the recovery point objective (RPO) and recovery time objective (RTO) for your service. |
Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources For more information, see the Oracle Integration documentation in the Oracle Cloud Library on the Oracle Help Center .Conventions The following text conventions are used in this document.Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Introduction Oracle Integration is available in an Oracle Cloud Infrastructure (OCI) region governed by service-level agreements (SLAs).This guide details the procedure to build a cross-region, customer-managed disaster recovery solution for Oracle Integration, specifically for the Integrations and File Server features in Oracle Integration.Disaster Recovery Concepts A disaster recovery (DR) solution enables you to recover quickly from natural or human-made disasters and continue to provide services to your users.In addition, you can use the DR set up for planned migrations and switch between different regions periodically.Before you set up any DR solution, you determine the recovery point objective (RPO) and recovery time objective (RTO) for your service.The RTO is the target time within which your service must be restored after a disaster occurs. |
Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources For more information, see the Oracle Integration documentation in the Oracle Cloud Library on the Oracle Help Center .Conventions The following text conventions are used in this document.Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Introduction Oracle Integration is available in an Oracle Cloud Infrastructure (OCI) region governed by service-level agreements (SLAs).This guide details the procedure to build a cross-region, customer-managed disaster recovery solution for Oracle Integration, specifically for the Integrations and File Server features in Oracle Integration.Disaster Recovery Concepts A disaster recovery (DR) solution enables you to recover quickly from natural or human-made disasters and continue to provide services to your users.In addition, you can use the DR set up for planned migrations and switch between different regions periodically.Before you set up any DR solution, you determine the recovery point objective (RPO) and recovery time objective (RTO) for your service.The RTO is the target time within which your service must be restored after a disaster occurs.The RPO is the period after a disaster occurs for which the service can tolerate lost data before the disaster begins to affect the business. |
As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources For more information, see the Oracle Integration documentation in the Oracle Cloud Library on the Oracle Help Center .Conventions The following text conventions are used in this document.Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Introduction Oracle Integration is available in an Oracle Cloud Infrastructure (OCI) region governed by service-level agreements (SLAs).This guide details the procedure to build a cross-region, customer-managed disaster recovery solution for Oracle Integration, specifically for the Integrations and File Server features in Oracle Integration.Disaster Recovery Concepts A disaster recovery (DR) solution enables you to recover quickly from natural or human-made disasters and continue to provide services to your users.In addition, you can use the DR set up for planned migrations and switch between different regions periodically.Before you set up any DR solution, you determine the recovery point objective (RPO) and recovery time objective (RTO) for your service.The RTO is the target time within which your service must be restored after a disaster occurs.The RPO is the period after a disaster occurs for which the service can tolerate lost data before the disaster begins to affect the business.The DR solution described in this guide replicates only the design-time artifacts; therefore, the RPO is not applicable in this scenario. |
We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources For more information, see the Oracle Integration documentation in the Oracle Cloud Library on the Oracle Help Center .Conventions The following text conventions are used in this document.Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Introduction Oracle Integration is available in an Oracle Cloud Infrastructure (OCI) region governed by service-level agreements (SLAs).This guide details the procedure to build a cross-region, customer-managed disaster recovery solution for Oracle Integration, specifically for the Integrations and File Server features in Oracle Integration.Disaster Recovery Concepts A disaster recovery (DR) solution enables you to recover quickly from natural or human-made disasters and continue to provide services to your users.In addition, you can use the DR set up for planned migrations and switch between different regions periodically.Before you set up any DR solution, you determine the recovery point objective (RPO) and recovery time objective (RTO) for your service.The RTO is the target time within which your service must be restored after a disaster occurs.The RPO is the period after a disaster occurs for which the service can tolerate lost data before the disaster begins to affect the business.The DR solution described in this guide replicates only the design-time artifacts; therefore, the RPO is not applicable in this scenario.You can measure the RTO based on how quickly youre able to complete the failover tasks in the secondary region. |
Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources For more information, see the Oracle Integration documentation in the Oracle Cloud Library on the Oracle Help Center .Conventions The following text conventions are used in this document.Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Introduction Oracle Integration is available in an Oracle Cloud Infrastructure (OCI) region governed by service-level agreements (SLAs).This guide details the procedure to build a cross-region, customer-managed disaster recovery solution for Oracle Integration, specifically for the Integrations and File Server features in Oracle Integration.Disaster Recovery Concepts A disaster recovery (DR) solution enables you to recover quickly from natural or human-made disasters and continue to provide services to your users.In addition, you can use the DR set up for planned migrations and switch between different regions periodically.Before you set up any DR solution, you determine the recovery point objective (RPO) and recovery time objective (RTO) for your service.The RTO is the target time within which your service must be restored after a disaster occurs.The RPO is the period after a disaster occurs for which the service can tolerate lost data before the disaster begins to affect the business.The DR solution described in this guide replicates only the design-time artifacts; therefore, the RPO is not applicable in this scenario.You can measure the RTO based on how quickly youre able to complete the failover tasks in the secondary region.This DR solution only supports an active-passive configuration. |
vRelated Resources For more information, see the Oracle Integration documentation in the Oracle Cloud Library on the Oracle Help Center .Conventions The following text conventions are used in this document.Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Introduction Oracle Integration is available in an Oracle Cloud Infrastructure (OCI) region governed by service-level agreements (SLAs).This guide details the procedure to build a cross-region, customer-managed disaster recovery solution for Oracle Integration, specifically for the Integrations and File Server features in Oracle Integration.Disaster Recovery Concepts A disaster recovery (DR) solution enables you to recover quickly from natural or human-made disasters and continue to provide services to your users.In addition, you can use the DR set up for planned migrations and switch between different regions periodically.Before you set up any DR solution, you determine the recovery point objective (RPO) and recovery time objective (RTO) for your service.The RTO is the target time within which your service must be restored after a disaster occurs.The RPO is the period after a disaster occurs for which the service can tolerate lost data before the disaster begins to affect the business.The DR solution described in this guide replicates only the design-time artifacts; therefore, the RPO is not applicable in this scenario.You can measure the RTO based on how quickly youre able to complete the failover tasks in the secondary region.This DR solution only supports an active-passive configuration.Only one instance or region of the DR configuration can be active and processing transactions at a time. |
Conventions The following text conventions are used in this document.Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Introduction Oracle Integration is available in an Oracle Cloud Infrastructure (OCI) region governed by service-level agreements (SLAs).This guide details the procedure to build a cross-region, customer-managed disaster recovery solution for Oracle Integration, specifically for the Integrations and File Server features in Oracle Integration.Disaster Recovery Concepts A disaster recovery (DR) solution enables you to recover quickly from natural or human-made disasters and continue to provide services to your users.In addition, you can use the DR set up for planned migrations and switch between different regions periodically.Before you set up any DR solution, you determine the recovery point objective (RPO) and recovery time objective (RTO) for your service.The RTO is the target time within which your service must be restored after a disaster occurs.The RPO is the period after a disaster occurs for which the service can tolerate lost data before the disaster begins to affect the business.The DR solution described in this guide replicates only the design-time artifacts; therefore, the RPO is not applicable in this scenario.You can measure the RTO based on how quickly youre able to complete the failover tasks in the secondary region.This DR solution only supports an active-passive configuration.Only one instance or region of the DR configuration can be active and processing transactions at a time.Other details on the scope and constraints of the solution are provided in the following sections. |
Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Introduction Oracle Integration is available in an Oracle Cloud Infrastructure (OCI) region governed by service-level agreements (SLAs).This guide details the procedure to build a cross-region, customer-managed disaster recovery solution for Oracle Integration, specifically for the Integrations and File Server features in Oracle Integration.Disaster Recovery Concepts A disaster recovery (DR) solution enables you to recover quickly from natural or human-made disasters and continue to provide services to your users.In addition, you can use the DR set up for planned migrations and switch between different regions periodically.Before you set up any DR solution, you determine the recovery point objective (RPO) and recovery time objective (RTO) for your service.The RTO is the target time within which your service must be restored after a disaster occurs.The RPO is the period after a disaster occurs for which the service can tolerate lost data before the disaster begins to affect the business.The DR solution described in this guide replicates only the design-time artifacts; therefore, the RPO is not applicable in this scenario.You can measure the RTO based on how quickly youre able to complete the failover tasks in the secondary region.This DR solution only supports an active-passive configuration.Only one instance or region of the DR configuration can be active and processing transactions at a time.Other details on the scope and constraints of the solution are provided in the following sections.1-12 About the Solution Scope Learn about the scope and constraints of the DR solution. |
italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Introduction Oracle Integration is available in an Oracle Cloud Infrastructure (OCI) region governed by service-level agreements (SLAs).This guide details the procedure to build a cross-region, customer-managed disaster recovery solution for Oracle Integration, specifically for the Integrations and File Server features in Oracle Integration.Disaster Recovery Concepts A disaster recovery (DR) solution enables you to recover quickly from natural or human-made disasters and continue to provide services to your users.In addition, you can use the DR set up for planned migrations and switch between different regions periodically.Before you set up any DR solution, you determine the recovery point objective (RPO) and recovery time objective (RTO) for your service.The RTO is the target time within which your service must be restored after a disaster occurs.The RPO is the period after a disaster occurs for which the service can tolerate lost data before the disaster begins to affect the business.The DR solution described in this guide replicates only the design-time artifacts; therefore, the RPO is not applicable in this scenario.You can measure the RTO based on how quickly youre able to complete the failover tasks in the secondary region.This DR solution only supports an active-passive configuration.Only one instance or region of the DR configuration can be active and processing transactions at a time.Other details on the scope and constraints of the solution are provided in the following sections.1-12 About the Solution Scope Learn about the scope and constraints of the DR solution.Topics: Whats Supported? |
monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Introduction Oracle Integration is available in an Oracle Cloud Infrastructure (OCI) region governed by service-level agreements (SLAs).This guide details the procedure to build a cross-region, customer-managed disaster recovery solution for Oracle Integration, specifically for the Integrations and File Server features in Oracle Integration.Disaster Recovery Concepts A disaster recovery (DR) solution enables you to recover quickly from natural or human-made disasters and continue to provide services to your users.In addition, you can use the DR set up for planned migrations and switch between different regions periodically.Before you set up any DR solution, you determine the recovery point objective (RPO) and recovery time objective (RTO) for your service.The RTO is the target time within which your service must be restored after a disaster occurs.The RPO is the period after a disaster occurs for which the service can tolerate lost data before the disaster begins to affect the business.The DR solution described in this guide replicates only the design-time artifacts; therefore, the RPO is not applicable in this scenario.You can measure the RTO based on how quickly youre able to complete the failover tasks in the secondary region.This DR solution only supports an active-passive configuration.Only one instance or region of the DR configuration can be active and processing transactions at a time.Other details on the scope and constraints of the solution are provided in the following sections.1-12 About the Solution Scope Learn about the scope and constraints of the DR solution.Topics: Whats Supported?Whats Not Supported? |
This guide details the procedure to build a cross-region, customer-managed disaster recovery solution for Oracle Integration, specifically for the Integrations and File Server features in Oracle Integration.Disaster Recovery Concepts A disaster recovery (DR) solution enables you to recover quickly from natural or human-made disasters and continue to provide services to your users.In addition, you can use the DR set up for planned migrations and switch between different regions periodically.Before you set up any DR solution, you determine the recovery point objective (RPO) and recovery time objective (RTO) for your service.The RTO is the target time within which your service must be restored after a disaster occurs.The RPO is the period after a disaster occurs for which the service can tolerate lost data before the disaster begins to affect the business.The DR solution described in this guide replicates only the design-time artifacts; therefore, the RPO is not applicable in this scenario.You can measure the RTO based on how quickly youre able to complete the failover tasks in the secondary region.This DR solution only supports an active-passive configuration.Only one instance or region of the DR configuration can be active and processing transactions at a time.Other details on the scope and constraints of the solution are provided in the following sections.1-12 About the Solution Scope Learn about the scope and constraints of the DR solution.Topics: Whats Supported?Whats Not Supported?Whats Supported? |
Disaster Recovery Concepts A disaster recovery (DR) solution enables you to recover quickly from natural or human-made disasters and continue to provide services to your users.In addition, you can use the DR set up for planned migrations and switch between different regions periodically.Before you set up any DR solution, you determine the recovery point objective (RPO) and recovery time objective (RTO) for your service.The RTO is the target time within which your service must be restored after a disaster occurs.The RPO is the period after a disaster occurs for which the service can tolerate lost data before the disaster begins to affect the business.The DR solution described in this guide replicates only the design-time artifacts; therefore, the RPO is not applicable in this scenario.You can measure the RTO based on how quickly youre able to complete the failover tasks in the secondary region.This DR solution only supports an active-passive configuration.Only one instance or region of the DR configuration can be active and processing transactions at a time.Other details on the scope and constraints of the solution are provided in the following sections.1-12 About the Solution Scope Learn about the scope and constraints of the DR solution.Topics: Whats Supported?Whats Not Supported?Whats Supported?This DR solution supports: Active-passive topologies. |
In addition, you can use the DR set up for planned migrations and switch between different regions periodically.Before you set up any DR solution, you determine the recovery point objective (RPO) and recovery time objective (RTO) for your service.The RTO is the target time within which your service must be restored after a disaster occurs.The RPO is the period after a disaster occurs for which the service can tolerate lost data before the disaster begins to affect the business.The DR solution described in this guide replicates only the design-time artifacts; therefore, the RPO is not applicable in this scenario.You can measure the RTO based on how quickly youre able to complete the failover tasks in the secondary region.This DR solution only supports an active-passive configuration.Only one instance or region of the DR configuration can be active and processing transactions at a time.Other details on the scope and constraints of the solution are provided in the following sections.1-12 About the Solution Scope Learn about the scope and constraints of the DR solution.Topics: Whats Supported?Whats Not Supported?Whats Supported?This DR solution supports: Active-passive topologies.Integrations (replication of the design-time artifacts only). |
Before you set up any DR solution, you determine the recovery point objective (RPO) and recovery time objective (RTO) for your service.The RTO is the target time within which your service must be restored after a disaster occurs.The RPO is the period after a disaster occurs for which the service can tolerate lost data before the disaster begins to affect the business.The DR solution described in this guide replicates only the design-time artifacts; therefore, the RPO is not applicable in this scenario.You can measure the RTO based on how quickly youre able to complete the failover tasks in the secondary region.This DR solution only supports an active-passive configuration.Only one instance or region of the DR configuration can be active and processing transactions at a time.Other details on the scope and constraints of the solution are provided in the following sections.1-12 About the Solution Scope Learn about the scope and constraints of the DR solution.Topics: Whats Supported?Whats Not Supported?Whats Supported?This DR solution supports: Active-passive topologies.Integrations (replication of the design-time artifacts only).Publish-subscribe integration patterns and integrations with scheduled parameters or polling triggers require special handling. |
The RTO is the target time within which your service must be restored after a disaster occurs.The RPO is the period after a disaster occurs for which the service can tolerate lost data before the disaster begins to affect the business.The DR solution described in this guide replicates only the design-time artifacts; therefore, the RPO is not applicable in this scenario.You can measure the RTO based on how quickly youre able to complete the failover tasks in the secondary region.This DR solution only supports an active-passive configuration.Only one instance or region of the DR configuration can be active and processing transactions at a time.Other details on the scope and constraints of the solution are provided in the following sections.1-12 About the Solution Scope Learn about the scope and constraints of the DR solution.Topics: Whats Supported?Whats Not Supported?Whats Supported?This DR solution supports: Active-passive topologies.Integrations (replication of the design-time artifacts only).Publish-subscribe integration patterns and integrations with scheduled parameters or polling triggers require special handling.See Key Considerations . |
The RPO is the period after a disaster occurs for which the service can tolerate lost data before the disaster begins to affect the business.The DR solution described in this guide replicates only the design-time artifacts; therefore, the RPO is not applicable in this scenario.You can measure the RTO based on how quickly youre able to complete the failover tasks in the secondary region.This DR solution only supports an active-passive configuration.Only one instance or region of the DR configuration can be active and processing transactions at a time.Other details on the scope and constraints of the solution are provided in the following sections.1-12 About the Solution Scope Learn about the scope and constraints of the DR solution.Topics: Whats Supported?Whats Not Supported?Whats Supported?This DR solution supports: Active-passive topologies.Integrations (replication of the design-time artifacts only).Publish-subscribe integration patterns and integrations with scheduled parameters or polling triggers require special handling.See Key Considerations .File Server. |
The DR solution described in this guide replicates only the design-time artifacts; therefore, the RPO is not applicable in this scenario.You can measure the RTO based on how quickly youre able to complete the failover tasks in the secondary region.This DR solution only supports an active-passive configuration.Only one instance or region of the DR configuration can be active and processing transactions at a time.Other details on the scope and constraints of the solution are provided in the following sections.1-12 About the Solution Scope Learn about the scope and constraints of the DR solution.Topics: Whats Supported?Whats Not Supported?Whats Supported?This DR solution supports: Active-passive topologies.Integrations (replication of the design-time artifacts only).Publish-subscribe integration patterns and integrations with scheduled parameters or polling triggers require special handling.See Key Considerations .File Server.Visual Builder. |
You can measure the RTO based on how quickly youre able to complete the failover tasks in the secondary region.This DR solution only supports an active-passive configuration.Only one instance or region of the DR configuration can be active and processing transactions at a time.Other details on the scope and constraints of the solution are provided in the following sections.1-12 About the Solution Scope Learn about the scope and constraints of the DR solution.Topics: Whats Supported?Whats Not Supported?Whats Supported?This DR solution supports: Active-passive topologies.Integrations (replication of the design-time artifacts only).Publish-subscribe integration patterns and integrations with scheduled parameters or polling triggers require special handling.See Key Considerations .File Server.Visual Builder.Related Resources For more information, see the Configuring Disaster Recovery for Oracle Visual Builder document. |
This DR solution only supports an active-passive configuration.Only one instance or region of the DR configuration can be active and processing transactions at a time.Other details on the scope and constraints of the solution are provided in the following sections.1-12 About the Solution Scope Learn about the scope and constraints of the DR solution.Topics: Whats Supported?Whats Not Supported?Whats Supported?This DR solution supports: Active-passive topologies.Integrations (replication of the design-time artifacts only).Publish-subscribe integration patterns and integrations with scheduled parameters or polling triggers require special handling.See Key Considerations .File Server.Visual Builder.Related Resources For more information, see the Configuring Disaster Recovery for Oracle Visual Builder document.Whats Not Supported? |
Only one instance or region of the DR configuration can be active and processing transactions at a time.Other details on the scope and constraints of the solution are provided in the following sections.1-12 About the Solution Scope Learn about the scope and constraints of the DR solution.Topics: Whats Supported?Whats Not Supported?Whats Supported?This DR solution supports: Active-passive topologies.Integrations (replication of the design-time artifacts only).Publish-subscribe integration patterns and integrations with scheduled parameters or polling triggers require special handling.See Key Considerations .File Server.Visual Builder.Related Resources For more information, see the Configuring Disaster Recovery for Oracle Visual Builder document.Whats Not Supported?This DR solution does not support: Processes. |
Other details on the scope and constraints of the solution are provided in the following sections.1-12 About the Solution Scope Learn about the scope and constraints of the DR solution.Topics: Whats Supported?Whats Not Supported?Whats Supported?This DR solution supports: Active-passive topologies.Integrations (replication of the design-time artifacts only).Publish-subscribe integration patterns and integrations with scheduled parameters or polling triggers require special handling.See Key Considerations .File Server.Visual Builder.Related Resources For more information, see the Configuring Disaster Recovery for Oracle Visual Builder document.Whats Not Supported?This DR solution does not support: Processes.Insight. |
1-12 About the Solution Scope Learn about the scope and constraints of the DR solution.Topics: Whats Supported?Whats Not Supported?Whats Supported?This DR solution supports: Active-passive topologies.Integrations (replication of the design-time artifacts only).Publish-subscribe integration patterns and integrations with scheduled parameters or polling triggers require special handling.See Key Considerations .File Server.Visual Builder.Related Resources For more information, see the Configuring Disaster Recovery for Oracle Visual Builder document.Whats Not Supported?This DR solution does not support: Processes.Insight.B2B. |
Topics: Whats Supported?Whats Not Supported?Whats Supported?This DR solution supports: Active-passive topologies.Integrations (replication of the design-time artifacts only).Publish-subscribe integration patterns and integrations with scheduled parameters or polling triggers require special handling.See Key Considerations .File Server.Visual Builder.Related Resources For more information, see the Configuring Disaster Recovery for Oracle Visual Builder document.Whats Not Supported?This DR solution does not support: Processes.Insight.B2B.2-13 Disaster Recovery for Integrations Learn about the architectural view of the DR solution for the Integrations feature in Oracle Integration. |
Whats Not Supported?Whats Supported?This DR solution supports: Active-passive topologies.Integrations (replication of the design-time artifacts only).Publish-subscribe integration patterns and integrations with scheduled parameters or polling triggers require special handling.See Key Considerations .File Server.Visual Builder.Related Resources For more information, see the Configuring Disaster Recovery for Oracle Visual Builder document.Whats Not Supported?This DR solution does not support: Processes.Insight.B2B.2-13 Disaster Recovery for Integrations Learn about the architectural view of the DR solution for the Integrations feature in Oracle Integration.Additionally, you can know more about the key considerations, prerequisites, and procedure to set up the solution. |
Whats Supported?This DR solution supports: Active-passive topologies.Integrations (replication of the design-time artifacts only).Publish-subscribe integration patterns and integrations with scheduled parameters or polling triggers require special handling.See Key Considerations .File Server.Visual Builder.Related Resources For more information, see the Configuring Disaster Recovery for Oracle Visual Builder document.Whats Not Supported?This DR solution does not support: Processes.Insight.B2B.2-13 Disaster Recovery for Integrations Learn about the architectural view of the DR solution for the Integrations feature in Oracle Integration.Additionally, you can know more about the key considerations, prerequisites, and procedure to set up the solution.Topics: Architecture Key Considerations Prerequisites Set Up the Disaster Recovery Solution for Integrations Perform Post-Configuration Tasks Architecture Learn about the architecture of the DR solution for the Integration feature. |
This DR solution supports: Active-passive topologies.Integrations (replication of the design-time artifacts only).Publish-subscribe integration patterns and integrations with scheduled parameters or polling triggers require special handling.See Key Considerations .File Server.Visual Builder.Related Resources For more information, see the Configuring Disaster Recovery for Oracle Visual Builder document.Whats Not Supported?This DR solution does not support: Processes.Insight.B2B.2-13 Disaster Recovery for Integrations Learn about the architectural view of the DR solution for the Integrations feature in Oracle Integration.Additionally, you can know more about the key considerations, prerequisites, and procedure to set up the solution.Topics: Architecture Key Considerations Prerequisites Set Up the Disaster Recovery Solution for Integrations Perform Post-Configuration Tasks Architecture Learn about the architecture of the DR solution for the Integration feature.The DR architecture for Integrations consists of two Oracle Integration instances in two different cloud regions, which are accessed using a single custom endpoint (URL). |
Integrations (replication of the design-time artifacts only).Publish-subscribe integration patterns and integrations with scheduled parameters or polling triggers require special handling.See Key Considerations .File Server.Visual Builder.Related Resources For more information, see the Configuring Disaster Recovery for Oracle Visual Builder document.Whats Not Supported?This DR solution does not support: Processes.Insight.B2B.2-13 Disaster Recovery for Integrations Learn about the architectural view of the DR solution for the Integrations feature in Oracle Integration.Additionally, you can know more about the key considerations, prerequisites, and procedure to set up the solution.Topics: Architecture Key Considerations Prerequisites Set Up the Disaster Recovery Solution for Integrations Perform Post-Configuration Tasks Architecture Learn about the architecture of the DR solution for the Integration feature.The DR architecture for Integrations consists of two Oracle Integration instances in two different cloud regions, which are accessed using a single custom endpoint (URL).Optionally, you can use an OCI Domain Name System (DNS) zone to resolve the custom endpoint name. |
Publish-subscribe integration patterns and integrations with scheduled parameters or polling triggers require special handling.See Key Considerations .File Server.Visual Builder.Related Resources For more information, see the Configuring Disaster Recovery for Oracle Visual Builder document.Whats Not Supported?This DR solution does not support: Processes.Insight.B2B.2-13 Disaster Recovery for Integrations Learn about the architectural view of the DR solution for the Integrations feature in Oracle Integration.Additionally, you can know more about the key considerations, prerequisites, and procedure to set up the solution.Topics: Architecture Key Considerations Prerequisites Set Up the Disaster Recovery Solution for Integrations Perform Post-Configuration Tasks Architecture Learn about the architecture of the DR solution for the Integration feature.The DR architecture for Integrations consists of two Oracle Integration instances in two different cloud regions, which are accessed using a single custom endpoint (URL).Optionally, you can use an OCI Domain Name System (DNS) zone to resolve the custom endpoint name.Custom endpoint URLs are a feature provided by Oracle Integration that allow you to define a custom URL in a domain that you manage. |
See Key Considerations .File Server.Visual Builder.Related Resources For more information, see the Configuring Disaster Recovery for Oracle Visual Builder document.Whats Not Supported?This DR solution does not support: Processes.Insight.B2B.2-13 Disaster Recovery for Integrations Learn about the architectural view of the DR solution for the Integrations feature in Oracle Integration.Additionally, you can know more about the key considerations, prerequisites, and procedure to set up the solution.Topics: Architecture Key Considerations Prerequisites Set Up the Disaster Recovery Solution for Integrations Perform Post-Configuration Tasks Architecture Learn about the architecture of the DR solution for the Integration feature.The DR architecture for Integrations consists of two Oracle Integration instances in two different cloud regions, which are accessed using a single custom endpoint (URL).Optionally, you can use an OCI Domain Name System (DNS) zone to resolve the custom endpoint name.Custom endpoint URLs are a feature provided by Oracle Integration that allow you to define a custom URL in a domain that you manage.You can use these URLs as the entry point to the Oracle Integration instances. |
File Server.Visual Builder.Related Resources For more information, see the Configuring Disaster Recovery for Oracle Visual Builder document.Whats Not Supported?This DR solution does not support: Processes.Insight.B2B.2-13 Disaster Recovery for Integrations Learn about the architectural view of the DR solution for the Integrations feature in Oracle Integration.Additionally, you can know more about the key considerations, prerequisites, and procedure to set up the solution.Topics: Architecture Key Considerations Prerequisites Set Up the Disaster Recovery Solution for Integrations Perform Post-Configuration Tasks Architecture Learn about the architecture of the DR solution for the Integration feature.The DR architecture for Integrations consists of two Oracle Integration instances in two different cloud regions, which are accessed using a single custom endpoint (URL).Optionally, you can use an OCI Domain Name System (DNS) zone to resolve the custom endpoint name.Custom endpoint URLs are a feature provided by Oracle Integration that allow you to define a custom URL in a domain that you manage.You can use these URLs as the entry point to the Oracle Integration instances.For example, prod-integration.mycompany.com. |
Visual Builder.Related Resources For more information, see the Configuring Disaster Recovery for Oracle Visual Builder document.Whats Not Supported?This DR solution does not support: Processes.Insight.B2B.2-13 Disaster Recovery for Integrations Learn about the architectural view of the DR solution for the Integrations feature in Oracle Integration.Additionally, you can know more about the key considerations, prerequisites, and procedure to set up the solution.Topics: Architecture Key Considerations Prerequisites Set Up the Disaster Recovery Solution for Integrations Perform Post-Configuration Tasks Architecture Learn about the architecture of the DR solution for the Integration feature.The DR architecture for Integrations consists of two Oracle Integration instances in two different cloud regions, which are accessed using a single custom endpoint (URL).Optionally, you can use an OCI Domain Name System (DNS) zone to resolve the custom endpoint name.Custom endpoint URLs are a feature provided by Oracle Integration that allow you to define a custom URL in a domain that you manage.You can use these URLs as the entry point to the Oracle Integration instances.For example, prod-integration.mycompany.com.For more information about configuring custom endpoints, see Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 . |
Related Resources For more information, see the Configuring Disaster Recovery for Oracle Visual Builder document.Whats Not Supported?This DR solution does not support: Processes.Insight.B2B.2-13 Disaster Recovery for Integrations Learn about the architectural view of the DR solution for the Integrations feature in Oracle Integration.Additionally, you can know more about the key considerations, prerequisites, and procedure to set up the solution.Topics: Architecture Key Considerations Prerequisites Set Up the Disaster Recovery Solution for Integrations Perform Post-Configuration Tasks Architecture Learn about the architecture of the DR solution for the Integration feature.The DR architecture for Integrations consists of two Oracle Integration instances in two different cloud regions, which are accessed using a single custom endpoint (URL).Optionally, you can use an OCI Domain Name System (DNS) zone to resolve the custom endpoint name.Custom endpoint URLs are a feature provided by Oracle Integration that allow you to define a custom URL in a domain that you manage.You can use these URLs as the entry point to the Oracle Integration instances.For example, prod-integration.mycompany.com.For more information about configuring custom endpoints, see Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 .The two Oracle Integration instances in the architecture are designated as primary and secondary, and both the instances run concurrently; however, only one of the instances receives traffic. |
Whats Not Supported?This DR solution does not support: Processes.Insight.B2B.2-13 Disaster Recovery for Integrations Learn about the architectural view of the DR solution for the Integrations feature in Oracle Integration.Additionally, you can know more about the key considerations, prerequisites, and procedure to set up the solution.Topics: Architecture Key Considerations Prerequisites Set Up the Disaster Recovery Solution for Integrations Perform Post-Configuration Tasks Architecture Learn about the architecture of the DR solution for the Integration feature.The DR architecture for Integrations consists of two Oracle Integration instances in two different cloud regions, which are accessed using a single custom endpoint (URL).Optionally, you can use an OCI Domain Name System (DNS) zone to resolve the custom endpoint name.Custom endpoint URLs are a feature provided by Oracle Integration that allow you to define a custom URL in a domain that you manage.You can use these URLs as the entry point to the Oracle Integration instances.For example, prod-integration.mycompany.com.For more information about configuring custom endpoints, see Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 .The two Oracle Integration instances in the architecture are designated as primary and secondary, and both the instances run concurrently; however, only one of the instances receives traffic.Initially, its the primary instance that receives the traffic flow. |
This DR solution does not support: Processes.Insight.B2B.2-13 Disaster Recovery for Integrations Learn about the architectural view of the DR solution for the Integrations feature in Oracle Integration.Additionally, you can know more about the key considerations, prerequisites, and procedure to set up the solution.Topics: Architecture Key Considerations Prerequisites Set Up the Disaster Recovery Solution for Integrations Perform Post-Configuration Tasks Architecture Learn about the architecture of the DR solution for the Integration feature.The DR architecture for Integrations consists of two Oracle Integration instances in two different cloud regions, which are accessed using a single custom endpoint (URL).Optionally, you can use an OCI Domain Name System (DNS) zone to resolve the custom endpoint name.Custom endpoint URLs are a feature provided by Oracle Integration that allow you to define a custom URL in a domain that you manage.You can use these URLs as the entry point to the Oracle Integration instances.For example, prod-integration.mycompany.com.For more information about configuring custom endpoints, see Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 .The two Oracle Integration instances in the architecture are designated as primary and secondary, and both the instances run concurrently; however, only one of the instances receives traffic.Initially, its the primary instance that receives the traffic flow.When this instance becomes unavailable, the DNS record is updated to route the traffic to the secondary instance. |
Insight.B2B.2-13 Disaster Recovery for Integrations Learn about the architectural view of the DR solution for the Integrations feature in Oracle Integration.Additionally, you can know more about the key considerations, prerequisites, and procedure to set up the solution.Topics: Architecture Key Considerations Prerequisites Set Up the Disaster Recovery Solution for Integrations Perform Post-Configuration Tasks Architecture Learn about the architecture of the DR solution for the Integration feature.The DR architecture for Integrations consists of two Oracle Integration instances in two different cloud regions, which are accessed using a single custom endpoint (URL).Optionally, you can use an OCI Domain Name System (DNS) zone to resolve the custom endpoint name.Custom endpoint URLs are a feature provided by Oracle Integration that allow you to define a custom URL in a domain that you manage.You can use these URLs as the entry point to the Oracle Integration instances.For example, prod-integration.mycompany.com.For more information about configuring custom endpoints, see Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 .The two Oracle Integration instances in the architecture are designated as primary and secondary, and both the instances run concurrently; however, only one of the instances receives traffic.Initially, its the primary instance that receives the traffic flow.When this instance becomes unavailable, the DNS record is updated to route the traffic to the secondary instance.The following image shows this architecture in detail for a scenario using connectivity agents: 3-1 You must update the DNS record at your DNS provider to switch between instances. |
B2B.2-13 Disaster Recovery for Integrations Learn about the architectural view of the DR solution for the Integrations feature in Oracle Integration.Additionally, you can know more about the key considerations, prerequisites, and procedure to set up the solution.Topics: Architecture Key Considerations Prerequisites Set Up the Disaster Recovery Solution for Integrations Perform Post-Configuration Tasks Architecture Learn about the architecture of the DR solution for the Integration feature.The DR architecture for Integrations consists of two Oracle Integration instances in two different cloud regions, which are accessed using a single custom endpoint (URL).Optionally, you can use an OCI Domain Name System (DNS) zone to resolve the custom endpoint name.Custom endpoint URLs are a feature provided by Oracle Integration that allow you to define a custom URL in a domain that you manage.You can use these URLs as the entry point to the Oracle Integration instances.For example, prod-integration.mycompany.com.For more information about configuring custom endpoints, see Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 .The two Oracle Integration instances in the architecture are designated as primary and secondary, and both the instances run concurrently; however, only one of the instances receives traffic.Initially, its the primary instance that receives the traffic flow.When this instance becomes unavailable, the DNS record is updated to route the traffic to the secondary instance.The following image shows this architecture in detail for a scenario using connectivity agents: 3-1 You must update the DNS record at your DNS provider to switch between instances.Optionally, you can implement an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname. |
2-13 Disaster Recovery for Integrations Learn about the architectural view of the DR solution for the Integrations feature in Oracle Integration.Additionally, you can know more about the key considerations, prerequisites, and procedure to set up the solution.Topics: Architecture Key Considerations Prerequisites Set Up the Disaster Recovery Solution for Integrations Perform Post-Configuration Tasks Architecture Learn about the architecture of the DR solution for the Integration feature.The DR architecture for Integrations consists of two Oracle Integration instances in two different cloud regions, which are accessed using a single custom endpoint (URL).Optionally, you can use an OCI Domain Name System (DNS) zone to resolve the custom endpoint name.Custom endpoint URLs are a feature provided by Oracle Integration that allow you to define a custom URL in a domain that you manage.You can use these URLs as the entry point to the Oracle Integration instances.For example, prod-integration.mycompany.com.For more information about configuring custom endpoints, see Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 .The two Oracle Integration instances in the architecture are designated as primary and secondary, and both the instances run concurrently; however, only one of the instances receives traffic.Initially, its the primary instance that receives the traffic flow.When this instance becomes unavailable, the DNS record is updated to route the traffic to the secondary instance.The following image shows this architecture in detail for a scenario using connectivity agents: 3-1 You must update the DNS record at your DNS provider to switch between instances.Optionally, you can implement an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.The OCI DNS zone can reflect changes to the CNAME much faster. |
Additionally, you can know more about the key considerations, prerequisites, and procedure to set up the solution.Topics: Architecture Key Considerations Prerequisites Set Up the Disaster Recovery Solution for Integrations Perform Post-Configuration Tasks Architecture Learn about the architecture of the DR solution for the Integration feature.The DR architecture for Integrations consists of two Oracle Integration instances in two different cloud regions, which are accessed using a single custom endpoint (URL).Optionally, you can use an OCI Domain Name System (DNS) zone to resolve the custom endpoint name.Custom endpoint URLs are a feature provided by Oracle Integration that allow you to define a custom URL in a domain that you manage.You can use these URLs as the entry point to the Oracle Integration instances.For example, prod-integration.mycompany.com.For more information about configuring custom endpoints, see Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 .The two Oracle Integration instances in the architecture are designated as primary and secondary, and both the instances run concurrently; however, only one of the instances receives traffic.Initially, its the primary instance that receives the traffic flow.When this instance becomes unavailable, the DNS record is updated to route the traffic to the secondary instance.The following image shows this architecture in detail for a scenario using connectivity agents: 3-1 You must update the DNS record at your DNS provider to switch between instances.Optionally, you can implement an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.The OCI DNS zone can reflect changes to the CNAME much faster.In this setup, you must synchronize the Oracle Integration metadata at both the sites using continuous integration and continuous deployment (CICD). |
Topics: Architecture Key Considerations Prerequisites Set Up the Disaster Recovery Solution for Integrations Perform Post-Configuration Tasks Architecture Learn about the architecture of the DR solution for the Integration feature.The DR architecture for Integrations consists of two Oracle Integration instances in two different cloud regions, which are accessed using a single custom endpoint (URL).Optionally, you can use an OCI Domain Name System (DNS) zone to resolve the custom endpoint name.Custom endpoint URLs are a feature provided by Oracle Integration that allow you to define a custom URL in a domain that you manage.You can use these URLs as the entry point to the Oracle Integration instances.For example, prod-integration.mycompany.com.For more information about configuring custom endpoints, see Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 .The two Oracle Integration instances in the architecture are designated as primary and secondary, and both the instances run concurrently; however, only one of the instances receives traffic.Initially, its the primary instance that receives the traffic flow.When this instance becomes unavailable, the DNS record is updated to route the traffic to the secondary instance.The following image shows this architecture in detail for a scenario using connectivity agents: 3-1 You must update the DNS record at your DNS provider to switch between instances.Optionally, you can implement an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.The OCI DNS zone can reflect changes to the CNAME much faster.In this setup, you must synchronize the Oracle Integration metadata at both the sites using continuous integration and continuous deployment (CICD).Key Considerations Consider the following important information before you start implementing the DR solution: The scheduled parameters in the integrations may not be the latest in the secondary instance because this depends on how often you update them. |
The DR architecture for Integrations consists of two Oracle Integration instances in two different cloud regions, which are accessed using a single custom endpoint (URL).Optionally, you can use an OCI Domain Name System (DNS) zone to resolve the custom endpoint name.Custom endpoint URLs are a feature provided by Oracle Integration that allow you to define a custom URL in a domain that you manage.You can use these URLs as the entry point to the Oracle Integration instances.For example, prod-integration.mycompany.com.For more information about configuring custom endpoints, see Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 .The two Oracle Integration instances in the architecture are designated as primary and secondary, and both the instances run concurrently; however, only one of the instances receives traffic.Initially, its the primary instance that receives the traffic flow.When this instance becomes unavailable, the DNS record is updated to route the traffic to the secondary instance.The following image shows this architecture in detail for a scenario using connectivity agents: 3-1 You must update the DNS record at your DNS provider to switch between instances.Optionally, you can implement an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.The OCI DNS zone can reflect changes to the CNAME much faster.In this setup, you must synchronize the Oracle Integration metadata at both the sites using continuous integration and continuous deployment (CICD).Key Considerations Consider the following important information before you start implementing the DR solution: The scheduled parameters in the integrations may not be the latest in the secondary instance because this depends on how often you update them.Hence, you must frequently update integrations with scheduled parameters in the secondary Oracle Integration instance. |
Optionally, you can use an OCI Domain Name System (DNS) zone to resolve the custom endpoint name.Custom endpoint URLs are a feature provided by Oracle Integration that allow you to define a custom URL in a domain that you manage.You can use these URLs as the entry point to the Oracle Integration instances.For example, prod-integration.mycompany.com.For more information about configuring custom endpoints, see Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 .The two Oracle Integration instances in the architecture are designated as primary and secondary, and both the instances run concurrently; however, only one of the instances receives traffic.Initially, its the primary instance that receives the traffic flow.When this instance becomes unavailable, the DNS record is updated to route the traffic to the secondary instance.The following image shows this architecture in detail for a scenario using connectivity agents: 3-1 You must update the DNS record at your DNS provider to switch between instances.Optionally, you can implement an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.The OCI DNS zone can reflect changes to the CNAME much faster.In this setup, you must synchronize the Oracle Integration metadata at both the sites using continuous integration and continuous deployment (CICD).Key Considerations Consider the following important information before you start implementing the DR solution: The scheduled parameters in the integrations may not be the latest in the secondary instance because this depends on how often you update them.Hence, you must frequently update integrations with scheduled parameters in the secondary Oracle Integration instance.See Automate Scheduled Parameters Updates . |
Custom endpoint URLs are a feature provided by Oracle Integration that allow you to define a custom URL in a domain that you manage.You can use these URLs as the entry point to the Oracle Integration instances.For example, prod-integration.mycompany.com.For more information about configuring custom endpoints, see Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 .The two Oracle Integration instances in the architecture are designated as primary and secondary, and both the instances run concurrently; however, only one of the instances receives traffic.Initially, its the primary instance that receives the traffic flow.When this instance becomes unavailable, the DNS record is updated to route the traffic to the secondary instance.The following image shows this architecture in detail for a scenario using connectivity agents: 3-1 You must update the DNS record at your DNS provider to switch between instances.Optionally, you can implement an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.The OCI DNS zone can reflect changes to the CNAME much faster.In this setup, you must synchronize the Oracle Integration metadata at both the sites using continuous integration and continuous deployment (CICD).Key Considerations Consider the following important information before you start implementing the DR solution: The scheduled parameters in the integrations may not be the latest in the secondary instance because this depends on how often you update them.Hence, you must frequently update integrations with scheduled parameters in the secondary Oracle Integration instance.See Automate Scheduled Parameters Updates .If a connectivity agent is required, you must provision and configure separate connectivity agents for the primary and secondary Oracle Integration instances. |
You can use these URLs as the entry point to the Oracle Integration instances.For example, prod-integration.mycompany.com.For more information about configuring custom endpoints, see Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 .The two Oracle Integration instances in the architecture are designated as primary and secondary, and both the instances run concurrently; however, only one of the instances receives traffic.Initially, its the primary instance that receives the traffic flow.When this instance becomes unavailable, the DNS record is updated to route the traffic to the secondary instance.The following image shows this architecture in detail for a scenario using connectivity agents: 3-1 You must update the DNS record at your DNS provider to switch between instances.Optionally, you can implement an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.The OCI DNS zone can reflect changes to the CNAME much faster.In this setup, you must synchronize the Oracle Integration metadata at both the sites using continuous integration and continuous deployment (CICD).Key Considerations Consider the following important information before you start implementing the DR solution: The scheduled parameters in the integrations may not be the latest in the secondary instance because this depends on how often you update them.Hence, you must frequently update integrations with scheduled parameters in the secondary Oracle Integration instance.See Automate Scheduled Parameters Updates .If a connectivity agent is required, you must provision and configure separate connectivity agents for the primary and secondary Oracle Integration instances.When the primary instance is active, you must stop or deactivate scheduled flows and integrations with polling triggers in the secondary instance. |
For example, prod-integration.mycompany.com.For more information about configuring custom endpoints, see Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 .The two Oracle Integration instances in the architecture are designated as primary and secondary, and both the instances run concurrently; however, only one of the instances receives traffic.Initially, its the primary instance that receives the traffic flow.When this instance becomes unavailable, the DNS record is updated to route the traffic to the secondary instance.The following image shows this architecture in detail for a scenario using connectivity agents: 3-1 You must update the DNS record at your DNS provider to switch between instances.Optionally, you can implement an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.The OCI DNS zone can reflect changes to the CNAME much faster.In this setup, you must synchronize the Oracle Integration metadata at both the sites using continuous integration and continuous deployment (CICD).Key Considerations Consider the following important information before you start implementing the DR solution: The scheduled parameters in the integrations may not be the latest in the secondary instance because this depends on how often you update them.Hence, you must frequently update integrations with scheduled parameters in the secondary Oracle Integration instance.See Automate Scheduled Parameters Updates .If a connectivity agent is required, you must provision and configure separate connectivity agents for the primary and secondary Oracle Integration instances.When the primary instance is active, you must stop or deactivate scheduled flows and integrations with polling triggers in the secondary instance.After a failover, activate these artifacts in the secondary instance. |
For more information about configuring custom endpoints, see Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2 .The two Oracle Integration instances in the architecture are designated as primary and secondary, and both the instances run concurrently; however, only one of the instances receives traffic.Initially, its the primary instance that receives the traffic flow.When this instance becomes unavailable, the DNS record is updated to route the traffic to the secondary instance.The following image shows this architecture in detail for a scenario using connectivity agents: 3-1 You must update the DNS record at your DNS provider to switch between instances.Optionally, you can implement an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.The OCI DNS zone can reflect changes to the CNAME much faster.In this setup, you must synchronize the Oracle Integration metadata at both the sites using continuous integration and continuous deployment (CICD).Key Considerations Consider the following important information before you start implementing the DR solution: The scheduled parameters in the integrations may not be the latest in the secondary instance because this depends on how often you update them.Hence, you must frequently update integrations with scheduled parameters in the secondary Oracle Integration instance.See Automate Scheduled Parameters Updates .If a connectivity agent is required, you must provision and configure separate connectivity agents for the primary and secondary Oracle Integration instances.When the primary instance is active, you must stop or deactivate scheduled flows and integrations with polling triggers in the secondary instance.After a failover, activate these artifacts in the secondary instance.The monitoring data (message history) is not replicated. |
The two Oracle Integration instances in the architecture are designated as primary and secondary, and both the instances run concurrently; however, only one of the instances receives traffic.Initially, its the primary instance that receives the traffic flow.When this instance becomes unavailable, the DNS record is updated to route the traffic to the secondary instance.The following image shows this architecture in detail for a scenario using connectivity agents: 3-1 You must update the DNS record at your DNS provider to switch between instances.Optionally, you can implement an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.The OCI DNS zone can reflect changes to the CNAME much faster.In this setup, you must synchronize the Oracle Integration metadata at both the sites using continuous integration and continuous deployment (CICD).Key Considerations Consider the following important information before you start implementing the DR solution: The scheduled parameters in the integrations may not be the latest in the secondary instance because this depends on how often you update them.Hence, you must frequently update integrations with scheduled parameters in the secondary Oracle Integration instance.See Automate Scheduled Parameters Updates .If a connectivity agent is required, you must provision and configure separate connectivity agents for the primary and secondary Oracle Integration instances.When the primary instance is active, you must stop or deactivate scheduled flows and integrations with polling triggers in the secondary instance.After a failover, activate these artifacts in the secondary instance.The monitoring data (message history) is not replicated.You can use the OCI Logging service to extract the message history in your data lake or warehouse to have a global view. |
Initially, its the primary instance that receives the traffic flow.When this instance becomes unavailable, the DNS record is updated to route the traffic to the secondary instance.The following image shows this architecture in detail for a scenario using connectivity agents: 3-1 You must update the DNS record at your DNS provider to switch between instances.Optionally, you can implement an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.The OCI DNS zone can reflect changes to the CNAME much faster.In this setup, you must synchronize the Oracle Integration metadata at both the sites using continuous integration and continuous deployment (CICD).Key Considerations Consider the following important information before you start implementing the DR solution: The scheduled parameters in the integrations may not be the latest in the secondary instance because this depends on how often you update them.Hence, you must frequently update integrations with scheduled parameters in the secondary Oracle Integration instance.See Automate Scheduled Parameters Updates .If a connectivity agent is required, you must provision and configure separate connectivity agents for the primary and secondary Oracle Integration instances.When the primary instance is active, you must stop or deactivate scheduled flows and integrations with polling triggers in the secondary instance.After a failover, activate these artifacts in the secondary instance.The monitoring data (message history) is not replicated.You can use the OCI Logging service to extract the message history in your data lake or warehouse to have a global view.Ensure that your source applications and end users use the custom endpoint to access the Oracle Integration instance. |
When this instance becomes unavailable, the DNS record is updated to route the traffic to the secondary instance.The following image shows this architecture in detail for a scenario using connectivity agents: 3-1 You must update the DNS record at your DNS provider to switch between instances.Optionally, you can implement an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.The OCI DNS zone can reflect changes to the CNAME much faster.In this setup, you must synchronize the Oracle Integration metadata at both the sites using continuous integration and continuous deployment (CICD).Key Considerations Consider the following important information before you start implementing the DR solution: The scheduled parameters in the integrations may not be the latest in the secondary instance because this depends on how often you update them.Hence, you must frequently update integrations with scheduled parameters in the secondary Oracle Integration instance.See Automate Scheduled Parameters Updates .If a connectivity agent is required, you must provision and configure separate connectivity agents for the primary and secondary Oracle Integration instances.When the primary instance is active, you must stop or deactivate scheduled flows and integrations with polling triggers in the secondary instance.After a failover, activate these artifacts in the secondary instance.The monitoring data (message history) is not replicated.You can use the OCI Logging service to extract the message history in your data lake or warehouse to have a global view.Ensure that your source applications and end users use the custom endpoint to access the Oracle Integration instance.Your administrators must use the respective original instance hostnames to manage the instances.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. |
The following image shows this architecture in detail for a scenario using connectivity agents: 3-1 You must update the DNS record at your DNS provider to switch between instances.Optionally, you can implement an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.The OCI DNS zone can reflect changes to the CNAME much faster.In this setup, you must synchronize the Oracle Integration metadata at both the sites using continuous integration and continuous deployment (CICD).Key Considerations Consider the following important information before you start implementing the DR solution: The scheduled parameters in the integrations may not be the latest in the secondary instance because this depends on how often you update them.Hence, you must frequently update integrations with scheduled parameters in the secondary Oracle Integration instance.See Automate Scheduled Parameters Updates .If a connectivity agent is required, you must provision and configure separate connectivity agents for the primary and secondary Oracle Integration instances.When the primary instance is active, you must stop or deactivate scheduled flows and integrations with polling triggers in the secondary instance.After a failover, activate these artifacts in the secondary instance.The monitoring data (message history) is not replicated.You can use the OCI Logging service to extract the message history in your data lake or warehouse to have a global view.Ensure that your source applications and end users use the custom endpoint to access the Oracle Integration instance.Your administrators must use the respective original instance hostnames to manage the instances.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. |
Optionally, you can implement an OCI DNS zone to manage the sub-domain related to the Oracle Integration custom hostname.The OCI DNS zone can reflect changes to the CNAME much faster.In this setup, you must synchronize the Oracle Integration metadata at both the sites using continuous integration and continuous deployment (CICD).Key Considerations Consider the following important information before you start implementing the DR solution: The scheduled parameters in the integrations may not be the latest in the secondary instance because this depends on how often you update them.Hence, you must frequently update integrations with scheduled parameters in the secondary Oracle Integration instance.See Automate Scheduled Parameters Updates .If a connectivity agent is required, you must provision and configure separate connectivity agents for the primary and secondary Oracle Integration instances.When the primary instance is active, you must stop or deactivate scheduled flows and integrations with polling triggers in the secondary instance.After a failover, activate these artifacts in the secondary instance.The monitoring data (message history) is not replicated.You can use the OCI Logging service to extract the message history in your data lake or warehouse to have a global view.Ensure that your source applications and end users use the custom endpoint to access the Oracle Integration instance.Your administrators must use the respective original instance hostnames to manage the instances.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. |
The OCI DNS zone can reflect changes to the CNAME much faster.In this setup, you must synchronize the Oracle Integration metadata at both the sites using continuous integration and continuous deployment (CICD).Key Considerations Consider the following important information before you start implementing the DR solution: The scheduled parameters in the integrations may not be the latest in the secondary instance because this depends on how often you update them.Hence, you must frequently update integrations with scheduled parameters in the secondary Oracle Integration instance.See Automate Scheduled Parameters Updates .If a connectivity agent is required, you must provision and configure separate connectivity agents for the primary and secondary Oracle Integration instances.When the primary instance is active, you must stop or deactivate scheduled flows and integrations with polling triggers in the secondary instance.After a failover, activate these artifacts in the secondary instance.The monitoring data (message history) is not replicated.You can use the OCI Logging service to extract the message history in your data lake or warehouse to have a global view.Ensure that your source applications and end users use the custom endpoint to access the Oracle Integration instance.Your administrators must use the respective original instance hostnames to manage the instances.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. |
In this setup, you must synchronize the Oracle Integration metadata at both the sites using continuous integration and continuous deployment (CICD).Key Considerations Consider the following important information before you start implementing the DR solution: The scheduled parameters in the integrations may not be the latest in the secondary instance because this depends on how often you update them.Hence, you must frequently update integrations with scheduled parameters in the secondary Oracle Integration instance.See Automate Scheduled Parameters Updates .If a connectivity agent is required, you must provision and configure separate connectivity agents for the primary and secondary Oracle Integration instances.When the primary instance is active, you must stop or deactivate scheduled flows and integrations with polling triggers in the secondary instance.After a failover, activate these artifacts in the secondary instance.The monitoring data (message history) is not replicated.You can use the OCI Logging service to extract the message history in your data lake or warehouse to have a global view.Ensure that your source applications and end users use the custom endpoint to access the Oracle Integration instance.Your administrators must use the respective original instance hostnames to manage the instances.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. |
Key Considerations Consider the following important information before you start implementing the DR solution: The scheduled parameters in the integrations may not be the latest in the secondary instance because this depends on how often you update them.Hence, you must frequently update integrations with scheduled parameters in the secondary Oracle Integration instance.See Automate Scheduled Parameters Updates .If a connectivity agent is required, you must provision and configure separate connectivity agents for the primary and secondary Oracle Integration instances.When the primary instance is active, you must stop or deactivate scheduled flows and integrations with polling triggers in the secondary instance.After a failover, activate these artifacts in the secondary instance.The monitoring data (message history) is not replicated.You can use the OCI Logging service to extract the message history in your data lake or warehouse to have a global view.Ensure that your source applications and end users use the custom endpoint to access the Oracle Integration instance.Your administrators must use the respective original instance hostnames to manage the instances.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. |
Hence, you must frequently update integrations with scheduled parameters in the secondary Oracle Integration instance.See Automate Scheduled Parameters Updates .If a connectivity agent is required, you must provision and configure separate connectivity agents for the primary and secondary Oracle Integration instances.When the primary instance is active, you must stop or deactivate scheduled flows and integrations with polling triggers in the secondary instance.After a failover, activate these artifacts in the secondary instance.The monitoring data (message history) is not replicated.You can use the OCI Logging service to extract the message history in your data lake or warehouse to have a global view.Ensure that your source applications and end users use the custom endpoint to access the Oracle Integration instance.Your administrators must use the respective original instance hostnames to manage the instances.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. |
See Automate Scheduled Parameters Updates .If a connectivity agent is required, you must provision and configure separate connectivity agents for the primary and secondary Oracle Integration instances.When the primary instance is active, you must stop or deactivate scheduled flows and integrations with polling triggers in the secondary instance.After a failover, activate these artifacts in the secondary instance.The monitoring data (message history) is not replicated.You can use the OCI Logging service to extract the message history in your data lake or warehouse to have a global view.Ensure that your source applications and end users use the custom endpoint to access the Oracle Integration instance.Your administrators must use the respective original instance hostnames to manage the instances.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. |
If a connectivity agent is required, you must provision and configure separate connectivity agents for the primary and secondary Oracle Integration instances.When the primary instance is active, you must stop or deactivate scheduled flows and integrations with polling triggers in the secondary instance.After a failover, activate these artifacts in the secondary instance.The monitoring data (message history) is not replicated.You can use the OCI Logging service to extract the message history in your data lake or warehouse to have a global view.Ensure that your source applications and end users use the custom endpoint to access the Oracle Integration instance.Your administrators must use the respective original instance hostnames to manage the instances.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. |
When the primary instance is active, you must stop or deactivate scheduled flows and integrations with polling triggers in the secondary instance.After a failover, activate these artifacts in the secondary instance.The monitoring data (message history) is not replicated.You can use the OCI Logging service to extract the message history in your data lake or warehouse to have a global view.Ensure that your source applications and end users use the custom endpoint to access the Oracle Integration instance.Your administrators must use the respective original instance hostnames to manage the instances.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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.