text
stringlengths 65
20k
|
|---|
7.In the mapper, map the search_data and start parameters in the request mapper and query result elements to the respective fields of Salesforce Commerce Cloud in the response mapper.The completed integration looks as follows.Chapter 4 Fetch Records in Salesforce Commerce Cloud Using the Query Operation 4-6 8.Specify the tracking variable, save, and close the integration.9.Activate the integration.10.After successful activation, you can submit the integration and monitor the runtime in Oracle Integration.The integration keeps running until it completes the search for fetching product results as the output response.Chapter 4 Fetch Records in Salesforce Commerce Cloud Using the Query Operation 4-7Oracle Cloud Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure F15345-21 August 2021 Oracle Cloud Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure, F15345-21 Copyright 2019, 2021, 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 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" or "commercial computer software documentation" 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.Governments use of Oracle cloud services are defined by the applicable contract for such services. |
The completed integration looks as follows.Chapter 4 Fetch Records in Salesforce Commerce Cloud Using the Query Operation 4-6 8.Specify the tracking variable, save, and close the integration.9.Activate the integration.10.After successful activation, you can submit the integration and monitor the runtime in Oracle Integration.The integration keeps running until it completes the search for fetching product results as the output response.Chapter 4 Fetch Records in Salesforce Commerce Cloud Using the Query Operation 4-7Oracle Cloud Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure F15345-21 August 2021 Oracle Cloud Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure, F15345-21 Copyright 2019, 2021, 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 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" or "commercial computer software documentation" 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.Governments use of Oracle cloud services are defined by the applicable contract for such services.No other rights are granted to the U.S. Government. |
Chapter 4 Fetch Records in Salesforce Commerce Cloud Using the Query Operation 4-6 8.Specify the tracking variable, save, and close the integration.9.Activate the integration.10.After successful activation, you can submit the integration and monitor the runtime in Oracle Integration.The integration keeps running until it completes the search for fetching product results as the output response.Chapter 4 Fetch Records in Salesforce Commerce Cloud Using the Query Operation 4-7Oracle Cloud Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure F15345-21 August 2021 Oracle Cloud Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure, F15345-21 Copyright 2019, 2021, 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 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" or "commercial computer software documentation" 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.Governments 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. |
9.Activate the integration.10.After successful activation, you can submit the integration and monitor the runtime in Oracle Integration.The integration keeps running until it completes the search for fetching product results as the output response.Chapter 4 Fetch Records in Salesforce Commerce Cloud Using the Query Operation 4-7Oracle Cloud Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure F15345-21 August 2021 Oracle Cloud Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure, F15345-21 Copyright 2019, 2021, 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 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" or "commercial computer software documentation" 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.Governments 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. |
10.After successful activation, you can submit the integration and monitor the runtime in Oracle Integration.The integration keeps running until it completes the search for fetching product results as the output response.Chapter 4 Fetch Records in Salesforce Commerce Cloud Using the Query Operation 4-7Oracle Cloud Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure F15345-21 August 2021 Oracle Cloud Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure, F15345-21 Copyright 2019, 2021, 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 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" or "commercial computer software documentation" 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.Governments 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. |
The integration keeps running until it completes the search for fetching product results as the output response.Chapter 4 Fetch Records in Salesforce Commerce Cloud Using the Query Operation 4-7Oracle Cloud Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure F15345-21 August 2021 Oracle Cloud Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure, F15345-21 Copyright 2019, 2021, 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 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" or "commercial computer software documentation" 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.Governments 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. |
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 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" or "commercial computer software documentation" 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.Governments 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. |
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 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" or "commercial computer software documentation" 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.Governments 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. |
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 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" or "commercial computer software documentation" 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.Governments 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. |
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 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" or "commercial computer software documentation" 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.Governments 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. |
If you find any errors, please report them to us in writing.If this is software 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" or "commercial computer software documentation" 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.Governments 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 this is software 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" or "commercial computer software documentation" 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.Governments 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. |
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.Governments 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. |
The terms governing the U.S.Governments 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 vi Documentation Accessibility vi Diversity and Inclusion vii Related Resources vii Conventions vii 1 Learn About Migrating to Oracle Cloud Infrastructure Why Migrate to Oracle Cloud Infrastructure 1-1 About the Migration Scope 1-1 Oracle Integration Classic Administration Restrictions 1-2 Integrations Design-Time Metadata Migration Scope 1-3 Integrations Migration Restrictions 1-3 Processes Design-Time Metadata Migration Scope 1-4 Processes Migration Restrictions 1-4 Visual Builder Design-Time Metadata Migration Scope 1-4 Visual Builder Migration Restrictions 1-6 About Oracle Cloud Infrastructure 1-6 About the Migration Task Flow 1-7 About the Migration Tooling 1-7 2 Prepare to Migrate Oracle Integration Classic to Oracle Cloud Infrastructure Integrations and Processes Tasks 2-1 Plan Your Migration 2-1 Prepare to Migrate 2-2 Size Oracle Integration Instances 2-2 Size Processes 2-3 Allowlist IP Addresses 2-4 Ensure Your Oracle Integration Classic Version is Correct for Migration with the Application Migration Service 2-5 iiiEnable Access to the Application Migration Service 2-5 Visual Builder Tasks 2-5 Create and Validate Oracle Integration (If Not Using the Application Migration Service) 2-7 3 Migrate Your Oracle Integration Classic Instances to Oracle Cloud Infrastructure Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure 3-1 Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment 3-2 Step 2: Create a User and Group and Add Policies 3-3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 Step 4: Migrate Integrations and Processes 3-8 Create a Source 3-9 Create a Migration 3-11 Configure the Migration Target Instance 3-12 Start the Migration 3-14 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15 Export Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata from a Git Repository 3-17 4 Complete the Post-Migration Tasks Verify Your Environment and Activate Your Integrations 4-1 Complete Post-Migration Tasks for Processes 4-1 Perform Post Import Steps for Processes 4-1 Handle In-Flight Process Instances 4-3 Follow Migration Best Practices for Processes 4-3 Complete Post-Migration Tasks for Visual Builder Applications 4-4 Lock the Live Visual Builder Application 4-4 Export Application Data From the Live Database 4-4 Import the Live Application Data into the New Application 4-5 Publish the New Application with the Live Application Data 4-5 A Alternate Migration Options Migrate Processes Design-Time Metadata into Oracle Integration A-1 Import Processes Design-Time Metadata into Oracle Integration A-1 Import Using the Import Command Line Utility A-3 Migrate Integration and Process Design-Time Metadata into Oracle Integration A-4 Import the Design-Time Metadata into Oracle Integration A-4 ivCheck the Design-Time Metadata Import Status A-6 Export the Integration and Process Design-Time Metadata A-7 vPreface Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure describes how to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure. |
Governments 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 vi Documentation Accessibility vi Diversity and Inclusion vii Related Resources vii Conventions vii 1 Learn About Migrating to Oracle Cloud Infrastructure Why Migrate to Oracle Cloud Infrastructure 1-1 About the Migration Scope 1-1 Oracle Integration Classic Administration Restrictions 1-2 Integrations Design-Time Metadata Migration Scope 1-3 Integrations Migration Restrictions 1-3 Processes Design-Time Metadata Migration Scope 1-4 Processes Migration Restrictions 1-4 Visual Builder Design-Time Metadata Migration Scope 1-4 Visual Builder Migration Restrictions 1-6 About Oracle Cloud Infrastructure 1-6 About the Migration Task Flow 1-7 About the Migration Tooling 1-7 2 Prepare to Migrate Oracle Integration Classic to Oracle Cloud Infrastructure Integrations and Processes Tasks 2-1 Plan Your Migration 2-1 Prepare to Migrate 2-2 Size Oracle Integration Instances 2-2 Size Processes 2-3 Allowlist IP Addresses 2-4 Ensure Your Oracle Integration Classic Version is Correct for Migration with the Application Migration Service 2-5 iiiEnable Access to the Application Migration Service 2-5 Visual Builder Tasks 2-5 Create and Validate Oracle Integration (If Not Using the Application Migration Service) 2-7 3 Migrate Your Oracle Integration Classic Instances to Oracle Cloud Infrastructure Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure 3-1 Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment 3-2 Step 2: Create a User and Group and Add Policies 3-3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 Step 4: Migrate Integrations and Processes 3-8 Create a Source 3-9 Create a Migration 3-11 Configure the Migration Target Instance 3-12 Start the Migration 3-14 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15 Export Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata from a Git Repository 3-17 4 Complete the Post-Migration Tasks Verify Your Environment and Activate Your Integrations 4-1 Complete Post-Migration Tasks for Processes 4-1 Perform Post Import Steps for Processes 4-1 Handle In-Flight Process Instances 4-3 Follow Migration Best Practices for Processes 4-3 Complete Post-Migration Tasks for Visual Builder Applications 4-4 Lock the Live Visual Builder Application 4-4 Export Application Data From the Live Database 4-4 Import the Live Application Data into the New Application 4-5 Publish the New Application with the Live Application Data 4-5 A Alternate Migration Options Migrate Processes Design-Time Metadata into Oracle Integration A-1 Import Processes Design-Time Metadata into Oracle Integration A-1 Import Using the Import Command Line Utility A-3 Migrate Integration and Process Design-Time Metadata into Oracle Integration A-4 Import the Design-Time Metadata into Oracle Integration A-4 ivCheck the Design-Time Metadata Import Status A-6 Export the Integration and Process Design-Time Metadata A-7 vPreface Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure describes how to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.Note: The information in this guide applies to all of your Oracle Integration instances. |
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 vi Documentation Accessibility vi Diversity and Inclusion vii Related Resources vii Conventions vii 1 Learn About Migrating to Oracle Cloud Infrastructure Why Migrate to Oracle Cloud Infrastructure 1-1 About the Migration Scope 1-1 Oracle Integration Classic Administration Restrictions 1-2 Integrations Design-Time Metadata Migration Scope 1-3 Integrations Migration Restrictions 1-3 Processes Design-Time Metadata Migration Scope 1-4 Processes Migration Restrictions 1-4 Visual Builder Design-Time Metadata Migration Scope 1-4 Visual Builder Migration Restrictions 1-6 About Oracle Cloud Infrastructure 1-6 About the Migration Task Flow 1-7 About the Migration Tooling 1-7 2 Prepare to Migrate Oracle Integration Classic to Oracle Cloud Infrastructure Integrations and Processes Tasks 2-1 Plan Your Migration 2-1 Prepare to Migrate 2-2 Size Oracle Integration Instances 2-2 Size Processes 2-3 Allowlist IP Addresses 2-4 Ensure Your Oracle Integration Classic Version is Correct for Migration with the Application Migration Service 2-5 iiiEnable Access to the Application Migration Service 2-5 Visual Builder Tasks 2-5 Create and Validate Oracle Integration (If Not Using the Application Migration Service) 2-7 3 Migrate Your Oracle Integration Classic Instances to Oracle Cloud Infrastructure Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure 3-1 Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment 3-2 Step 2: Create a User and Group and Add Policies 3-3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 Step 4: Migrate Integrations and Processes 3-8 Create a Source 3-9 Create a Migration 3-11 Configure the Migration Target Instance 3-12 Start the Migration 3-14 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15 Export Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata from a Git Repository 3-17 4 Complete the Post-Migration Tasks Verify Your Environment and Activate Your Integrations 4-1 Complete Post-Migration Tasks for Processes 4-1 Perform Post Import Steps for Processes 4-1 Handle In-Flight Process Instances 4-3 Follow Migration Best Practices for Processes 4-3 Complete Post-Migration Tasks for Visual Builder Applications 4-4 Lock the Live Visual Builder Application 4-4 Export Application Data From the Live Database 4-4 Import the Live Application Data into the New Application 4-5 Publish the New Application with the Live Application Data 4-5 A Alternate Migration Options Migrate Processes Design-Time Metadata into Oracle Integration A-1 Import Processes Design-Time Metadata into Oracle Integration A-1 Import Using the Import Command Line Utility A-3 Migrate Integration and Process Design-Time Metadata into Oracle Integration A-4 Import the Design-Time Metadata into Oracle Integration A-4 ivCheck the Design-Time Metadata Import Status A-6 Export the Integration and Process Design-Time Metadata A-7 vPreface Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure describes how to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.Note: The information in this guide applies to all of your Oracle Integration instances.It doesnt matter which edition youre using, what features you have, or who manages your cloud environment. |
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 vi Documentation Accessibility vi Diversity and Inclusion vii Related Resources vii Conventions vii 1 Learn About Migrating to Oracle Cloud Infrastructure Why Migrate to Oracle Cloud Infrastructure 1-1 About the Migration Scope 1-1 Oracle Integration Classic Administration Restrictions 1-2 Integrations Design-Time Metadata Migration Scope 1-3 Integrations Migration Restrictions 1-3 Processes Design-Time Metadata Migration Scope 1-4 Processes Migration Restrictions 1-4 Visual Builder Design-Time Metadata Migration Scope 1-4 Visual Builder Migration Restrictions 1-6 About Oracle Cloud Infrastructure 1-6 About the Migration Task Flow 1-7 About the Migration Tooling 1-7 2 Prepare to Migrate Oracle Integration Classic to Oracle Cloud Infrastructure Integrations and Processes Tasks 2-1 Plan Your Migration 2-1 Prepare to Migrate 2-2 Size Oracle Integration Instances 2-2 Size Processes 2-3 Allowlist IP Addresses 2-4 Ensure Your Oracle Integration Classic Version is Correct for Migration with the Application Migration Service 2-5 iiiEnable Access to the Application Migration Service 2-5 Visual Builder Tasks 2-5 Create and Validate Oracle Integration (If Not Using the Application Migration Service) 2-7 3 Migrate Your Oracle Integration Classic Instances to Oracle Cloud Infrastructure Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure 3-1 Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment 3-2 Step 2: Create a User and Group and Add Policies 3-3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 Step 4: Migrate Integrations and Processes 3-8 Create a Source 3-9 Create a Migration 3-11 Configure the Migration Target Instance 3-12 Start the Migration 3-14 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15 Export Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata from a Git Repository 3-17 4 Complete the Post-Migration Tasks Verify Your Environment and Activate Your Integrations 4-1 Complete Post-Migration Tasks for Processes 4-1 Perform Post Import Steps for Processes 4-1 Handle In-Flight Process Instances 4-3 Follow Migration Best Practices for Processes 4-3 Complete Post-Migration Tasks for Visual Builder Applications 4-4 Lock the Live Visual Builder Application 4-4 Export Application Data From the Live Database 4-4 Import the Live Application Data into the New Application 4-5 Publish the New Application with the Live Application Data 4-5 A Alternate Migration Options Migrate Processes Design-Time Metadata into Oracle Integration A-1 Import Processes Design-Time Metadata into Oracle Integration A-1 Import Using the Import Command Line Utility A-3 Migrate Integration and Process Design-Time Metadata into Oracle Integration A-4 Import the Design-Time Metadata into Oracle Integration A-4 ivCheck the Design-Time Metadata Import Status A-6 Export the Integration and Process Design-Time Metadata A-7 vPreface Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure describes how to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.Note: The information in this guide applies to all of your Oracle Integration instances.It doesnt matter which edition youre using, what features you have, or who manages your cloud environment.Youll find what you need here, including notes about any differences between the various flavors of Oracle Integration when necessary. |
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 vi Documentation Accessibility vi Diversity and Inclusion vii Related Resources vii Conventions vii 1 Learn About Migrating to Oracle Cloud Infrastructure Why Migrate to Oracle Cloud Infrastructure 1-1 About the Migration Scope 1-1 Oracle Integration Classic Administration Restrictions 1-2 Integrations Design-Time Metadata Migration Scope 1-3 Integrations Migration Restrictions 1-3 Processes Design-Time Metadata Migration Scope 1-4 Processes Migration Restrictions 1-4 Visual Builder Design-Time Metadata Migration Scope 1-4 Visual Builder Migration Restrictions 1-6 About Oracle Cloud Infrastructure 1-6 About the Migration Task Flow 1-7 About the Migration Tooling 1-7 2 Prepare to Migrate Oracle Integration Classic to Oracle Cloud Infrastructure Integrations and Processes Tasks 2-1 Plan Your Migration 2-1 Prepare to Migrate 2-2 Size Oracle Integration Instances 2-2 Size Processes 2-3 Allowlist IP Addresses 2-4 Ensure Your Oracle Integration Classic Version is Correct for Migration with the Application Migration Service 2-5 iiiEnable Access to the Application Migration Service 2-5 Visual Builder Tasks 2-5 Create and Validate Oracle Integration (If Not Using the Application Migration Service) 2-7 3 Migrate Your Oracle Integration Classic Instances to Oracle Cloud Infrastructure Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure 3-1 Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment 3-2 Step 2: Create a User and Group and Add Policies 3-3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 Step 4: Migrate Integrations and Processes 3-8 Create a Source 3-9 Create a Migration 3-11 Configure the Migration Target Instance 3-12 Start the Migration 3-14 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15 Export Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata from a Git Repository 3-17 4 Complete the Post-Migration Tasks Verify Your Environment and Activate Your Integrations 4-1 Complete Post-Migration Tasks for Processes 4-1 Perform Post Import Steps for Processes 4-1 Handle In-Flight Process Instances 4-3 Follow Migration Best Practices for Processes 4-3 Complete Post-Migration Tasks for Visual Builder Applications 4-4 Lock the Live Visual Builder Application 4-4 Export Application Data From the Live Database 4-4 Import the Live Application Data into the New Application 4-5 Publish the New Application with the Live Application Data 4-5 A Alternate Migration Options Migrate Processes Design-Time Metadata into Oracle Integration A-1 Import Processes Design-Time Metadata into Oracle Integration A-1 Import Using the Import Command Line Utility A-3 Migrate Integration and Process Design-Time Metadata into Oracle Integration A-4 Import the Design-Time Metadata into Oracle Integration A-4 ivCheck the Design-Time Metadata Import Status A-6 Export the Integration and Process Design-Time Metadata A-7 vPreface Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure describes how to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.Note: The information in this guide applies to all of your Oracle Integration instances.It doesnt matter which edition youre using, what features you have, or who manages your cloud environment.Youll find what you need here, including notes about any differences between the various flavors of Oracle Integration when necessary.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure is intended for users who need to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure. |
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 vi Documentation Accessibility vi Diversity and Inclusion vii Related Resources vii Conventions vii 1 Learn About Migrating to Oracle Cloud Infrastructure Why Migrate to Oracle Cloud Infrastructure 1-1 About the Migration Scope 1-1 Oracle Integration Classic Administration Restrictions 1-2 Integrations Design-Time Metadata Migration Scope 1-3 Integrations Migration Restrictions 1-3 Processes Design-Time Metadata Migration Scope 1-4 Processes Migration Restrictions 1-4 Visual Builder Design-Time Metadata Migration Scope 1-4 Visual Builder Migration Restrictions 1-6 About Oracle Cloud Infrastructure 1-6 About the Migration Task Flow 1-7 About the Migration Tooling 1-7 2 Prepare to Migrate Oracle Integration Classic to Oracle Cloud Infrastructure Integrations and Processes Tasks 2-1 Plan Your Migration 2-1 Prepare to Migrate 2-2 Size Oracle Integration Instances 2-2 Size Processes 2-3 Allowlist IP Addresses 2-4 Ensure Your Oracle Integration Classic Version is Correct for Migration with the Application Migration Service 2-5 iiiEnable Access to the Application Migration Service 2-5 Visual Builder Tasks 2-5 Create and Validate Oracle Integration (If Not Using the Application Migration Service) 2-7 3 Migrate Your Oracle Integration Classic Instances to Oracle Cloud Infrastructure Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure 3-1 Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment 3-2 Step 2: Create a User and Group and Add Policies 3-3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 Step 4: Migrate Integrations and Processes 3-8 Create a Source 3-9 Create a Migration 3-11 Configure the Migration Target Instance 3-12 Start the Migration 3-14 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15 Export Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata from a Git Repository 3-17 4 Complete the Post-Migration Tasks Verify Your Environment and Activate Your Integrations 4-1 Complete Post-Migration Tasks for Processes 4-1 Perform Post Import Steps for Processes 4-1 Handle In-Flight Process Instances 4-3 Follow Migration Best Practices for Processes 4-3 Complete Post-Migration Tasks for Visual Builder Applications 4-4 Lock the Live Visual Builder Application 4-4 Export Application Data From the Live Database 4-4 Import the Live Application Data into the New Application 4-5 Publish the New Application with the Live Application Data 4-5 A Alternate Migration Options Migrate Processes Design-Time Metadata into Oracle Integration A-1 Import Processes Design-Time Metadata into Oracle Integration A-1 Import Using the Import Command Line Utility A-3 Migrate Integration and Process Design-Time Metadata into Oracle Integration A-4 Import the Design-Time Metadata into Oracle Integration A-4 ivCheck the Design-Time Metadata Import Status A-6 Export the Integration and Process Design-Time Metadata A-7 vPreface Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure describes how to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.Note: The information in this guide applies to all of your Oracle Integration instances.It doesnt matter which edition youre using, what features you have, or who manages your cloud environment.Youll find what you need here, including notes about any differences between the various flavors of Oracle Integration when necessary.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure is intended for users who need to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup? |
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 vi Documentation Accessibility vi Diversity and Inclusion vii Related Resources vii Conventions vii 1 Learn About Migrating to Oracle Cloud Infrastructure Why Migrate to Oracle Cloud Infrastructure 1-1 About the Migration Scope 1-1 Oracle Integration Classic Administration Restrictions 1-2 Integrations Design-Time Metadata Migration Scope 1-3 Integrations Migration Restrictions 1-3 Processes Design-Time Metadata Migration Scope 1-4 Processes Migration Restrictions 1-4 Visual Builder Design-Time Metadata Migration Scope 1-4 Visual Builder Migration Restrictions 1-6 About Oracle Cloud Infrastructure 1-6 About the Migration Task Flow 1-7 About the Migration Tooling 1-7 2 Prepare to Migrate Oracle Integration Classic to Oracle Cloud Infrastructure Integrations and Processes Tasks 2-1 Plan Your Migration 2-1 Prepare to Migrate 2-2 Size Oracle Integration Instances 2-2 Size Processes 2-3 Allowlist IP Addresses 2-4 Ensure Your Oracle Integration Classic Version is Correct for Migration with the Application Migration Service 2-5 iiiEnable Access to the Application Migration Service 2-5 Visual Builder Tasks 2-5 Create and Validate Oracle Integration (If Not Using the Application Migration Service) 2-7 3 Migrate Your Oracle Integration Classic Instances to Oracle Cloud Infrastructure Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure 3-1 Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment 3-2 Step 2: Create a User and Group and Add Policies 3-3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 Step 4: Migrate Integrations and Processes 3-8 Create a Source 3-9 Create a Migration 3-11 Configure the Migration Target Instance 3-12 Start the Migration 3-14 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15 Export Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata from a Git Repository 3-17 4 Complete the Post-Migration Tasks Verify Your Environment and Activate Your Integrations 4-1 Complete Post-Migration Tasks for Processes 4-1 Perform Post Import Steps for Processes 4-1 Handle In-Flight Process Instances 4-3 Follow Migration Best Practices for Processes 4-3 Complete Post-Migration Tasks for Visual Builder Applications 4-4 Lock the Live Visual Builder Application 4-4 Export Application Data From the Live Database 4-4 Import the Live Application Data into the New Application 4-5 Publish the New Application with the Live Application Data 4-5 A Alternate Migration Options Migrate Processes Design-Time Metadata into Oracle Integration A-1 Import Processes Design-Time Metadata into Oracle Integration A-1 Import Using the Import Command Line Utility A-3 Migrate Integration and Process Design-Time Metadata into Oracle Integration A-4 Import the Design-Time Metadata into Oracle Integration A-4 ivCheck the Design-Time Metadata Import Status A-6 Export the Integration and Process Design-Time Metadata A-7 vPreface Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure describes how to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.Note: The information in this guide applies to all of your Oracle Integration instances.It doesnt matter which edition youre using, what features you have, or who manages your cloud environment.Youll find what you need here, including notes about any differences between the various flavors of Oracle Integration when necessary.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure is intended for users who need to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.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 . |
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 vi Documentation Accessibility vi Diversity and Inclusion vii Related Resources vii Conventions vii 1 Learn About Migrating to Oracle Cloud Infrastructure Why Migrate to Oracle Cloud Infrastructure 1-1 About the Migration Scope 1-1 Oracle Integration Classic Administration Restrictions 1-2 Integrations Design-Time Metadata Migration Scope 1-3 Integrations Migration Restrictions 1-3 Processes Design-Time Metadata Migration Scope 1-4 Processes Migration Restrictions 1-4 Visual Builder Design-Time Metadata Migration Scope 1-4 Visual Builder Migration Restrictions 1-6 About Oracle Cloud Infrastructure 1-6 About the Migration Task Flow 1-7 About the Migration Tooling 1-7 2 Prepare to Migrate Oracle Integration Classic to Oracle Cloud Infrastructure Integrations and Processes Tasks 2-1 Plan Your Migration 2-1 Prepare to Migrate 2-2 Size Oracle Integration Instances 2-2 Size Processes 2-3 Allowlist IP Addresses 2-4 Ensure Your Oracle Integration Classic Version is Correct for Migration with the Application Migration Service 2-5 iiiEnable Access to the Application Migration Service 2-5 Visual Builder Tasks 2-5 Create and Validate Oracle Integration (If Not Using the Application Migration Service) 2-7 3 Migrate Your Oracle Integration Classic Instances to Oracle Cloud Infrastructure Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure 3-1 Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment 3-2 Step 2: Create a User and Group and Add Policies 3-3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 Step 4: Migrate Integrations and Processes 3-8 Create a Source 3-9 Create a Migration 3-11 Configure the Migration Target Instance 3-12 Start the Migration 3-14 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15 Export Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata from a Git Repository 3-17 4 Complete the Post-Migration Tasks Verify Your Environment and Activate Your Integrations 4-1 Complete Post-Migration Tasks for Processes 4-1 Perform Post Import Steps for Processes 4-1 Handle In-Flight Process Instances 4-3 Follow Migration Best Practices for Processes 4-3 Complete Post-Migration Tasks for Visual Builder Applications 4-4 Lock the Live Visual Builder Application 4-4 Export Application Data From the Live Database 4-4 Import the Live Application Data into the New Application 4-5 Publish the New Application with the Live Application Data 4-5 A Alternate Migration Options Migrate Processes Design-Time Metadata into Oracle Integration A-1 Import Processes Design-Time Metadata into Oracle Integration A-1 Import Using the Import Command Line Utility A-3 Migrate Integration and Process Design-Time Metadata into Oracle Integration A-4 Import the Design-Time Metadata into Oracle Integration A-4 ivCheck the Design-Time Metadata Import Status A-6 Export the Integration and Process Design-Time Metadata A-7 vPreface Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure describes how to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.Note: The information in this guide applies to all of your Oracle Integration instances.It doesnt matter which edition youre using, what features you have, or who manages your cloud environment.Youll find what you need here, including notes about any differences between the various flavors of Oracle Integration when necessary.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure is intended for users who need to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.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. |
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 vi Documentation Accessibility vi Diversity and Inclusion vii Related Resources vii Conventions vii 1 Learn About Migrating to Oracle Cloud Infrastructure Why Migrate to Oracle Cloud Infrastructure 1-1 About the Migration Scope 1-1 Oracle Integration Classic Administration Restrictions 1-2 Integrations Design-Time Metadata Migration Scope 1-3 Integrations Migration Restrictions 1-3 Processes Design-Time Metadata Migration Scope 1-4 Processes Migration Restrictions 1-4 Visual Builder Design-Time Metadata Migration Scope 1-4 Visual Builder Migration Restrictions 1-6 About Oracle Cloud Infrastructure 1-6 About the Migration Task Flow 1-7 About the Migration Tooling 1-7 2 Prepare to Migrate Oracle Integration Classic to Oracle Cloud Infrastructure Integrations and Processes Tasks 2-1 Plan Your Migration 2-1 Prepare to Migrate 2-2 Size Oracle Integration Instances 2-2 Size Processes 2-3 Allowlist IP Addresses 2-4 Ensure Your Oracle Integration Classic Version is Correct for Migration with the Application Migration Service 2-5 iiiEnable Access to the Application Migration Service 2-5 Visual Builder Tasks 2-5 Create and Validate Oracle Integration (If Not Using the Application Migration Service) 2-7 3 Migrate Your Oracle Integration Classic Instances to Oracle Cloud Infrastructure Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure 3-1 Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment 3-2 Step 2: Create a User and Group and Add Policies 3-3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 Step 4: Migrate Integrations and Processes 3-8 Create a Source 3-9 Create a Migration 3-11 Configure the Migration Target Instance 3-12 Start the Migration 3-14 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15 Export Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata from a Git Repository 3-17 4 Complete the Post-Migration Tasks Verify Your Environment and Activate Your Integrations 4-1 Complete Post-Migration Tasks for Processes 4-1 Perform Post Import Steps for Processes 4-1 Handle In-Flight Process Instances 4-3 Follow Migration Best Practices for Processes 4-3 Complete Post-Migration Tasks for Visual Builder Applications 4-4 Lock the Live Visual Builder Application 4-4 Export Application Data From the Live Database 4-4 Import the Live Application Data into the New Application 4-5 Publish the New Application with the Live Application Data 4-5 A Alternate Migration Options Migrate Processes Design-Time Metadata into Oracle Integration A-1 Import Processes Design-Time Metadata into Oracle Integration A-1 Import Using the Import Command Line Utility A-3 Migrate Integration and Process Design-Time Metadata into Oracle Integration A-4 Import the Design-Time Metadata into Oracle Integration A-4 ivCheck the Design-Time Metadata Import Status A-6 Export the Integration and Process Design-Time Metadata A-7 vPreface Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure describes how to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.Note: The information in this guide applies to all of your Oracle Integration instances.It doesnt matter which edition youre using, what features you have, or who manages your cloud environment.Youll find what you need here, including notes about any differences between the various flavors of Oracle Integration when necessary.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure is intended for users who need to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.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? |
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 vi Documentation Accessibility vi Diversity and Inclusion vii Related Resources vii Conventions vii 1 Learn About Migrating to Oracle Cloud Infrastructure Why Migrate to Oracle Cloud Infrastructure 1-1 About the Migration Scope 1-1 Oracle Integration Classic Administration Restrictions 1-2 Integrations Design-Time Metadata Migration Scope 1-3 Integrations Migration Restrictions 1-3 Processes Design-Time Metadata Migration Scope 1-4 Processes Migration Restrictions 1-4 Visual Builder Design-Time Metadata Migration Scope 1-4 Visual Builder Migration Restrictions 1-6 About Oracle Cloud Infrastructure 1-6 About the Migration Task Flow 1-7 About the Migration Tooling 1-7 2 Prepare to Migrate Oracle Integration Classic to Oracle Cloud Infrastructure Integrations and Processes Tasks 2-1 Plan Your Migration 2-1 Prepare to Migrate 2-2 Size Oracle Integration Instances 2-2 Size Processes 2-3 Allowlist IP Addresses 2-4 Ensure Your Oracle Integration Classic Version is Correct for Migration with the Application Migration Service 2-5 iiiEnable Access to the Application Migration Service 2-5 Visual Builder Tasks 2-5 Create and Validate Oracle Integration (If Not Using the Application Migration Service) 2-7 3 Migrate Your Oracle Integration Classic Instances to Oracle Cloud Infrastructure Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure 3-1 Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment 3-2 Step 2: Create a User and Group and Add Policies 3-3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 Step 4: Migrate Integrations and Processes 3-8 Create a Source 3-9 Create a Migration 3-11 Configure the Migration Target Instance 3-12 Start the Migration 3-14 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15 Export Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata from a Git Repository 3-17 4 Complete the Post-Migration Tasks Verify Your Environment and Activate Your Integrations 4-1 Complete Post-Migration Tasks for Processes 4-1 Perform Post Import Steps for Processes 4-1 Handle In-Flight Process Instances 4-3 Follow Migration Best Practices for Processes 4-3 Complete Post-Migration Tasks for Visual Builder Applications 4-4 Lock the Live Visual Builder Application 4-4 Export Application Data From the Live Database 4-4 Import the Live Application Data into the New Application 4-5 Publish the New Application with the Live Application Data 4-5 A Alternate Migration Options Migrate Processes Design-Time Metadata into Oracle Integration A-1 Import Processes Design-Time Metadata into Oracle Integration A-1 Import Using the Import Command Line Utility A-3 Migrate Integration and Process Design-Time Metadata into Oracle Integration A-4 Import the Design-Time Metadata into Oracle Integration A-4 ivCheck the Design-Time Metadata Import Status A-6 Export the Integration and Process Design-Time Metadata A-7 vPreface Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure describes how to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.Note: The information in this guide applies to all of your Oracle Integration instances.It doesnt matter which edition youre using, what features you have, or who manages your cloud environment.Youll find what you need here, including notes about any differences between the various flavors of Oracle Integration when necessary.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure is intended for users who need to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.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.Preface viDiversity and Inclusion Oracle is fully committed to diversity and inclusion. |
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 vi Documentation Accessibility vi Diversity and Inclusion vii Related Resources vii Conventions vii 1 Learn About Migrating to Oracle Cloud Infrastructure Why Migrate to Oracle Cloud Infrastructure 1-1 About the Migration Scope 1-1 Oracle Integration Classic Administration Restrictions 1-2 Integrations Design-Time Metadata Migration Scope 1-3 Integrations Migration Restrictions 1-3 Processes Design-Time Metadata Migration Scope 1-4 Processes Migration Restrictions 1-4 Visual Builder Design-Time Metadata Migration Scope 1-4 Visual Builder Migration Restrictions 1-6 About Oracle Cloud Infrastructure 1-6 About the Migration Task Flow 1-7 About the Migration Tooling 1-7 2 Prepare to Migrate Oracle Integration Classic to Oracle Cloud Infrastructure Integrations and Processes Tasks 2-1 Plan Your Migration 2-1 Prepare to Migrate 2-2 Size Oracle Integration Instances 2-2 Size Processes 2-3 Allowlist IP Addresses 2-4 Ensure Your Oracle Integration Classic Version is Correct for Migration with the Application Migration Service 2-5 iiiEnable Access to the Application Migration Service 2-5 Visual Builder Tasks 2-5 Create and Validate Oracle Integration (If Not Using the Application Migration Service) 2-7 3 Migrate Your Oracle Integration Classic Instances to Oracle Cloud Infrastructure Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure 3-1 Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment 3-2 Step 2: Create a User and Group and Add Policies 3-3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 Step 4: Migrate Integrations and Processes 3-8 Create a Source 3-9 Create a Migration 3-11 Configure the Migration Target Instance 3-12 Start the Migration 3-14 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15 Export Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata from a Git Repository 3-17 4 Complete the Post-Migration Tasks Verify Your Environment and Activate Your Integrations 4-1 Complete Post-Migration Tasks for Processes 4-1 Perform Post Import Steps for Processes 4-1 Handle In-Flight Process Instances 4-3 Follow Migration Best Practices for Processes 4-3 Complete Post-Migration Tasks for Visual Builder Applications 4-4 Lock the Live Visual Builder Application 4-4 Export Application Data From the Live Database 4-4 Import the Live Application Data into the New Application 4-5 Publish the New Application with the Live Application Data 4-5 A Alternate Migration Options Migrate Processes Design-Time Metadata into Oracle Integration A-1 Import Processes Design-Time Metadata into Oracle Integration A-1 Import Using the Import Command Line Utility A-3 Migrate Integration and Process Design-Time Metadata into Oracle Integration A-4 Import the Design-Time Metadata into Oracle Integration A-4 ivCheck the Design-Time Metadata Import Status A-6 Export the Integration and Process Design-Time Metadata A-7 vPreface Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure describes how to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.Note: The information in this guide applies to all of your Oracle Integration instances.It doesnt matter which edition youre using, what features you have, or who manages your cloud environment.Youll find what you need here, including notes about any differences between the various flavors of Oracle Integration when necessary.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure is intended for users who need to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.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.Preface viDiversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation. |
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 vi Documentation Accessibility vi Diversity and Inclusion vii Related Resources vii Conventions vii 1 Learn About Migrating to Oracle Cloud Infrastructure Why Migrate to Oracle Cloud Infrastructure 1-1 About the Migration Scope 1-1 Oracle Integration Classic Administration Restrictions 1-2 Integrations Design-Time Metadata Migration Scope 1-3 Integrations Migration Restrictions 1-3 Processes Design-Time Metadata Migration Scope 1-4 Processes Migration Restrictions 1-4 Visual Builder Design-Time Metadata Migration Scope 1-4 Visual Builder Migration Restrictions 1-6 About Oracle Cloud Infrastructure 1-6 About the Migration Task Flow 1-7 About the Migration Tooling 1-7 2 Prepare to Migrate Oracle Integration Classic to Oracle Cloud Infrastructure Integrations and Processes Tasks 2-1 Plan Your Migration 2-1 Prepare to Migrate 2-2 Size Oracle Integration Instances 2-2 Size Processes 2-3 Allowlist IP Addresses 2-4 Ensure Your Oracle Integration Classic Version is Correct for Migration with the Application Migration Service 2-5 iiiEnable Access to the Application Migration Service 2-5 Visual Builder Tasks 2-5 Create and Validate Oracle Integration (If Not Using the Application Migration Service) 2-7 3 Migrate Your Oracle Integration Classic Instances to Oracle Cloud Infrastructure Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure 3-1 Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment 3-2 Step 2: Create a User and Group and Add Policies 3-3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 Step 4: Migrate Integrations and Processes 3-8 Create a Source 3-9 Create a Migration 3-11 Configure the Migration Target Instance 3-12 Start the Migration 3-14 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15 Export Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata from a Git Repository 3-17 4 Complete the Post-Migration Tasks Verify Your Environment and Activate Your Integrations 4-1 Complete Post-Migration Tasks for Processes 4-1 Perform Post Import Steps for Processes 4-1 Handle In-Flight Process Instances 4-3 Follow Migration Best Practices for Processes 4-3 Complete Post-Migration Tasks for Visual Builder Applications 4-4 Lock the Live Visual Builder Application 4-4 Export Application Data From the Live Database 4-4 Import the Live Application Data into the New Application 4-5 Publish the New Application with the Live Application Data 4-5 A Alternate Migration Options Migrate Processes Design-Time Metadata into Oracle Integration A-1 Import Processes Design-Time Metadata into Oracle Integration A-1 Import Using the Import Command Line Utility A-3 Migrate Integration and Process Design-Time Metadata into Oracle Integration A-4 Import the Design-Time Metadata into Oracle Integration A-4 ivCheck the Design-Time Metadata Import Status A-6 Export the Integration and Process Design-Time Metadata A-7 vPreface Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure describes how to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.Note: The information in this guide applies to all of your Oracle Integration instances.It doesnt matter which edition youre using, what features you have, or who manages your cloud environment.Youll find what you need here, including notes about any differences between the various flavors of Oracle Integration when necessary.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure is intended for users who need to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.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.Preface viDiversity 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. |
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 vi Documentation Accessibility vi Diversity and Inclusion vii Related Resources vii Conventions vii 1 Learn About Migrating to Oracle Cloud Infrastructure Why Migrate to Oracle Cloud Infrastructure 1-1 About the Migration Scope 1-1 Oracle Integration Classic Administration Restrictions 1-2 Integrations Design-Time Metadata Migration Scope 1-3 Integrations Migration Restrictions 1-3 Processes Design-Time Metadata Migration Scope 1-4 Processes Migration Restrictions 1-4 Visual Builder Design-Time Metadata Migration Scope 1-4 Visual Builder Migration Restrictions 1-6 About Oracle Cloud Infrastructure 1-6 About the Migration Task Flow 1-7 About the Migration Tooling 1-7 2 Prepare to Migrate Oracle Integration Classic to Oracle Cloud Infrastructure Integrations and Processes Tasks 2-1 Plan Your Migration 2-1 Prepare to Migrate 2-2 Size Oracle Integration Instances 2-2 Size Processes 2-3 Allowlist IP Addresses 2-4 Ensure Your Oracle Integration Classic Version is Correct for Migration with the Application Migration Service 2-5 iiiEnable Access to the Application Migration Service 2-5 Visual Builder Tasks 2-5 Create and Validate Oracle Integration (If Not Using the Application Migration Service) 2-7 3 Migrate Your Oracle Integration Classic Instances to Oracle Cloud Infrastructure Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure 3-1 Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment 3-2 Step 2: Create a User and Group and Add Policies 3-3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 Step 4: Migrate Integrations and Processes 3-8 Create a Source 3-9 Create a Migration 3-11 Configure the Migration Target Instance 3-12 Start the Migration 3-14 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15 Export Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata from a Git Repository 3-17 4 Complete the Post-Migration Tasks Verify Your Environment and Activate Your Integrations 4-1 Complete Post-Migration Tasks for Processes 4-1 Perform Post Import Steps for Processes 4-1 Handle In-Flight Process Instances 4-3 Follow Migration Best Practices for Processes 4-3 Complete Post-Migration Tasks for Visual Builder Applications 4-4 Lock the Live Visual Builder Application 4-4 Export Application Data From the Live Database 4-4 Import the Live Application Data into the New Application 4-5 Publish the New Application with the Live Application Data 4-5 A Alternate Migration Options Migrate Processes Design-Time Metadata into Oracle Integration A-1 Import Processes Design-Time Metadata into Oracle Integration A-1 Import Using the Import Command Line Utility A-3 Migrate Integration and Process Design-Time Metadata into Oracle Integration A-4 Import the Design-Time Metadata into Oracle Integration A-4 ivCheck the Design-Time Metadata Import Status A-6 Export the Integration and Process Design-Time Metadata A-7 vPreface Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure describes how to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.Note: The information in this guide applies to all of your Oracle Integration instances.It doesnt matter which edition youre using, what features you have, or who manages your cloud environment.Youll find what you need here, including notes about any differences between the various flavors of Oracle Integration when necessary.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure is intended for users who need to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.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.Preface viDiversity 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. |
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 vi Documentation Accessibility vi Diversity and Inclusion vii Related Resources vii Conventions vii 1 Learn About Migrating to Oracle Cloud Infrastructure Why Migrate to Oracle Cloud Infrastructure 1-1 About the Migration Scope 1-1 Oracle Integration Classic Administration Restrictions 1-2 Integrations Design-Time Metadata Migration Scope 1-3 Integrations Migration Restrictions 1-3 Processes Design-Time Metadata Migration Scope 1-4 Processes Migration Restrictions 1-4 Visual Builder Design-Time Metadata Migration Scope 1-4 Visual Builder Migration Restrictions 1-6 About Oracle Cloud Infrastructure 1-6 About the Migration Task Flow 1-7 About the Migration Tooling 1-7 2 Prepare to Migrate Oracle Integration Classic to Oracle Cloud Infrastructure Integrations and Processes Tasks 2-1 Plan Your Migration 2-1 Prepare to Migrate 2-2 Size Oracle Integration Instances 2-2 Size Processes 2-3 Allowlist IP Addresses 2-4 Ensure Your Oracle Integration Classic Version is Correct for Migration with the Application Migration Service 2-5 iiiEnable Access to the Application Migration Service 2-5 Visual Builder Tasks 2-5 Create and Validate Oracle Integration (If Not Using the Application Migration Service) 2-7 3 Migrate Your Oracle Integration Classic Instances to Oracle Cloud Infrastructure Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure 3-1 Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment 3-2 Step 2: Create a User and Group and Add Policies 3-3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 Step 4: Migrate Integrations and Processes 3-8 Create a Source 3-9 Create a Migration 3-11 Configure the Migration Target Instance 3-12 Start the Migration 3-14 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15 Export Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata from a Git Repository 3-17 4 Complete the Post-Migration Tasks Verify Your Environment and Activate Your Integrations 4-1 Complete Post-Migration Tasks for Processes 4-1 Perform Post Import Steps for Processes 4-1 Handle In-Flight Process Instances 4-3 Follow Migration Best Practices for Processes 4-3 Complete Post-Migration Tasks for Visual Builder Applications 4-4 Lock the Live Visual Builder Application 4-4 Export Application Data From the Live Database 4-4 Import the Live Application Data into the New Application 4-5 Publish the New Application with the Live Application Data 4-5 A Alternate Migration Options Migrate Processes Design-Time Metadata into Oracle Integration A-1 Import Processes Design-Time Metadata into Oracle Integration A-1 Import Using the Import Command Line Utility A-3 Migrate Integration and Process Design-Time Metadata into Oracle Integration A-4 Import the Design-Time Metadata into Oracle Integration A-4 ivCheck the Design-Time Metadata Import Status A-6 Export the Integration and Process Design-Time Metadata A-7 vPreface Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure describes how to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.Note: The information in this guide applies to all of your Oracle Integration instances.It doesnt matter which edition youre using, what features you have, or who manages your cloud environment.Youll find what you need here, including notes about any differences between the various flavors of Oracle Integration when necessary.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure is intended for users who need to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.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.Preface viDiversity 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 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 vi Documentation Accessibility vi Diversity and Inclusion vii Related Resources vii Conventions vii 1 Learn About Migrating to Oracle Cloud Infrastructure Why Migrate to Oracle Cloud Infrastructure 1-1 About the Migration Scope 1-1 Oracle Integration Classic Administration Restrictions 1-2 Integrations Design-Time Metadata Migration Scope 1-3 Integrations Migration Restrictions 1-3 Processes Design-Time Metadata Migration Scope 1-4 Processes Migration Restrictions 1-4 Visual Builder Design-Time Metadata Migration Scope 1-4 Visual Builder Migration Restrictions 1-6 About Oracle Cloud Infrastructure 1-6 About the Migration Task Flow 1-7 About the Migration Tooling 1-7 2 Prepare to Migrate Oracle Integration Classic to Oracle Cloud Infrastructure Integrations and Processes Tasks 2-1 Plan Your Migration 2-1 Prepare to Migrate 2-2 Size Oracle Integration Instances 2-2 Size Processes 2-3 Allowlist IP Addresses 2-4 Ensure Your Oracle Integration Classic Version is Correct for Migration with the Application Migration Service 2-5 iiiEnable Access to the Application Migration Service 2-5 Visual Builder Tasks 2-5 Create and Validate Oracle Integration (If Not Using the Application Migration Service) 2-7 3 Migrate Your Oracle Integration Classic Instances to Oracle Cloud Infrastructure Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure 3-1 Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment 3-2 Step 2: Create a User and Group and Add Policies 3-3 Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) 3-5 Step 4: Migrate Integrations and Processes 3-8 Create a Source 3-9 Create a Migration 3-11 Configure the Migration Target Instance 3-12 Start the Migration 3-14 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-15 Export Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata 3-16 Import Visual Builder Design-Time Metadata from a Git Repository 3-17 4 Complete the Post-Migration Tasks Verify Your Environment and Activate Your Integrations 4-1 Complete Post-Migration Tasks for Processes 4-1 Perform Post Import Steps for Processes 4-1 Handle In-Flight Process Instances 4-3 Follow Migration Best Practices for Processes 4-3 Complete Post-Migration Tasks for Visual Builder Applications 4-4 Lock the Live Visual Builder Application 4-4 Export Application Data From the Live Database 4-4 Import the Live Application Data into the New Application 4-5 Publish the New Application with the Live Application Data 4-5 A Alternate Migration Options Migrate Processes Design-Time Metadata into Oracle Integration A-1 Import Processes Design-Time Metadata into Oracle Integration A-1 Import Using the Import Command Line Utility A-3 Migrate Integration and Process Design-Time Metadata into Oracle Integration A-4 Import the Design-Time Metadata into Oracle Integration A-4 ivCheck the Design-Time Metadata Import Status A-6 Export the Integration and Process Design-Time Metadata A-7 vPreface Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure describes how to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.Note: The information in this guide applies to all of your Oracle Integration instances.It doesnt matter which edition youre using, what features you have, or who manages your cloud environment.Youll find what you need here, including notes about any differences between the various flavors of Oracle Integration when necessary.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure is intended for users who need to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.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.Preface viDiversity 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.Related Resources For more information, see these Oracle resources: Oracle Integration documentation in the Oracle Cloud Library on the Oracle Help Center. |
Note: The information in this guide applies to all of your Oracle Integration instances.It doesnt matter which edition youre using, what features you have, or who manages your cloud environment.Youll find what you need here, including notes about any differences between the various flavors of Oracle Integration when necessary.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure is intended for users who need to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.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.Preface viDiversity 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.Related Resources For more information, see these Oracle resources: Oracle Integration documentation in the Oracle Cloud Library on the Oracle Help Center.Conventions The following text conventions are used in this document. |
It doesnt matter which edition youre using, what features you have, or who manages your cloud environment.Youll find what you need here, including notes about any differences between the various flavors of Oracle Integration when necessary.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure is intended for users who need to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.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.Preface viDiversity 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.Related Resources For more information, see these Oracle resources: 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. |
Youll find what you need here, including notes about any differences between the various flavors of Oracle Integration when necessary.Topics: Audience Documentation Accessibility Diversity and Inclusion Related Resources Conventions Audience Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure is intended for users who need to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.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.Preface viDiversity 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.Related Resources For more information, see these Oracle resources: 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 Migrating Oracle Integration Classic Instances to Oracle Cloud Infrastructure is intended for users who need to migrate Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.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.Preface viDiversity 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.Related Resources For more information, see these Oracle resources: 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 vii1 Learn About Migrating to Oracle Cloud Infrastructure Learn about the benefits to migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, and receive an overview of the migration process and tools. |
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.Preface viDiversity 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.Related Resources For more information, see these Oracle resources: 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 vii1 Learn About Migrating to Oracle Cloud Infrastructure Learn about the benefits to migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, and receive an overview of the migration process and tools.Topics: Why Migrate to Oracle Cloud Infrastructure About the Migration Scope About Oracle Cloud Infrastructure About the Migration Task Flow About the Migration Tooling Video Why Migrate to Oracle Cloud Infrastructure Oracle encourages you to migrate your existing cloud resources to Oracle Cloud Infrastructure regions. |
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.Preface viDiversity 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.Related Resources For more information, see these Oracle resources: 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 vii1 Learn About Migrating to Oracle Cloud Infrastructure Learn about the benefits to migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, and receive an overview of the migration process and tools.Topics: Why Migrate to Oracle Cloud Infrastructure About the Migration Scope About Oracle Cloud Infrastructure About the Migration Task Flow About the Migration Tooling Video Why Migrate to Oracle Cloud Infrastructure Oracle encourages you to migrate your existing cloud resources to Oracle Cloud Infrastructure regions.You can gain several advantages by doing so. |
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.Preface viDiversity 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.Related Resources For more information, see these Oracle resources: 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 vii1 Learn About Migrating to Oracle Cloud Infrastructure Learn about the benefits to migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, and receive an overview of the migration process and tools.Topics: Why Migrate to Oracle Cloud Infrastructure About the Migration Scope About Oracle Cloud Infrastructure About the Migration Task Flow About the Migration Tooling Video Why Migrate to Oracle Cloud Infrastructure Oracle encourages you to migrate your existing cloud resources to Oracle Cloud Infrastructure regions.You can gain several advantages by doing so.In Oracle Cloud, you provision resources in specific regions, which are localized to geographic locations. |
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.Preface viDiversity 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.Related Resources For more information, see these Oracle resources: 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 vii1 Learn About Migrating to Oracle Cloud Infrastructure Learn about the benefits to migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, and receive an overview of the migration process and tools.Topics: Why Migrate to Oracle Cloud Infrastructure About the Migration Scope About Oracle Cloud Infrastructure About the Migration Task Flow About the Migration Tooling Video Why Migrate to Oracle Cloud Infrastructure Oracle encourages you to migrate your existing cloud resources to Oracle Cloud Infrastructure regions.You can gain several advantages by doing so.In Oracle Cloud, you provision resources in specific regions, which are localized to geographic locations.Certain regions support the Oracle Cloud Infrastructure platform. |
ctx=acc&id=trs if you are hearing impaired.Preface viDiversity 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.Related Resources For more information, see these Oracle resources: 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 vii1 Learn About Migrating to Oracle Cloud Infrastructure Learn about the benefits to migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, and receive an overview of the migration process and tools.Topics: Why Migrate to Oracle Cloud Infrastructure About the Migration Scope About Oracle Cloud Infrastructure About the Migration Task Flow About the Migration Tooling Video Why Migrate to Oracle Cloud Infrastructure Oracle encourages you to migrate your existing cloud resources to Oracle Cloud Infrastructure regions.You can gain several advantages by doing so.In Oracle Cloud, you provision resources in specific regions, which are localized to geographic locations.Certain regions support the Oracle Cloud Infrastructure platform.Oracle Cloud Infrastructure is Oracle's modern cloud platform that's based on the latest cloud technologies and standards. |
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.Related Resources For more information, see these Oracle resources: 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 vii1 Learn About Migrating to Oracle Cloud Infrastructure Learn about the benefits to migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, and receive an overview of the migration process and tools.Topics: Why Migrate to Oracle Cloud Infrastructure About the Migration Scope About Oracle Cloud Infrastructure About the Migration Task Flow About the Migration Tooling Video Why Migrate to Oracle Cloud Infrastructure Oracle encourages you to migrate your existing cloud resources to Oracle Cloud Infrastructure regions.You can gain several advantages by doing so.In Oracle Cloud, you provision resources in specific regions, which are localized to geographic locations.Certain regions support the Oracle Cloud Infrastructure platform.Oracle Cloud Infrastructure is Oracle's modern cloud platform that's based on the latest cloud technologies and standards.It provides more consistent performance and better features at lower costs. |
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.Related Resources For more information, see these Oracle resources: 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 vii1 Learn About Migrating to Oracle Cloud Infrastructure Learn about the benefits to migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, and receive an overview of the migration process and tools.Topics: Why Migrate to Oracle Cloud Infrastructure About the Migration Scope About Oracle Cloud Infrastructure About the Migration Task Flow About the Migration Tooling Video Why Migrate to Oracle Cloud Infrastructure Oracle encourages you to migrate your existing cloud resources to Oracle Cloud Infrastructure regions.You can gain several advantages by doing so.In Oracle Cloud, you provision resources in specific regions, which are localized to geographic locations.Certain regions support the Oracle Cloud Infrastructure platform.Oracle Cloud Infrastructure is Oracle's modern cloud platform that's based on the latest cloud technologies and standards.It provides more consistent performance and better features at lower costs.Oracle continues to invest in Oracle Cloud Infrastructure, including the addition of new regions, services, and features. |
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.Related Resources For more information, see these Oracle resources: 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 vii1 Learn About Migrating to Oracle Cloud Infrastructure Learn about the benefits to migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, and receive an overview of the migration process and tools.Topics: Why Migrate to Oracle Cloud Infrastructure About the Migration Scope About Oracle Cloud Infrastructure About the Migration Task Flow About the Migration Tooling Video Why Migrate to Oracle Cloud Infrastructure Oracle encourages you to migrate your existing cloud resources to Oracle Cloud Infrastructure regions.You can gain several advantages by doing so.In Oracle Cloud, you provision resources in specific regions, which are localized to geographic locations.Certain regions support the Oracle Cloud Infrastructure platform.Oracle Cloud Infrastructure is Oracle's modern cloud platform that's based on the latest cloud technologies and standards.It provides more consistent performance and better features at lower costs.Oracle continues to invest in Oracle Cloud Infrastructure, including the addition of new regions, services, and features.See Data Regions for Platform and Infrastructure Services . |
Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.Related Resources For more information, see these Oracle resources: 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 vii1 Learn About Migrating to Oracle Cloud Infrastructure Learn about the benefits to migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, and receive an overview of the migration process and tools.Topics: Why Migrate to Oracle Cloud Infrastructure About the Migration Scope About Oracle Cloud Infrastructure About the Migration Task Flow About the Migration Tooling Video Why Migrate to Oracle Cloud Infrastructure Oracle encourages you to migrate your existing cloud resources to Oracle Cloud Infrastructure regions.You can gain several advantages by doing so.In Oracle Cloud, you provision resources in specific regions, which are localized to geographic locations.Certain regions support the Oracle Cloud Infrastructure platform.Oracle Cloud Infrastructure is Oracle's modern cloud platform that's based on the latest cloud technologies and standards.It provides more consistent performance and better features at lower costs.Oracle continues to invest in Oracle Cloud Infrastructure, including the addition of new regions, services, and features.See Data Regions for Platform and Infrastructure Services .You can benefit from these additional administrative features when you migrate your cloud resources to Oracle Cloud Infrastructure: Organize cloud resources into a hierarchy of logical compartments. |
Related Resources For more information, see these Oracle resources: 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 vii1 Learn About Migrating to Oracle Cloud Infrastructure Learn about the benefits to migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, and receive an overview of the migration process and tools.Topics: Why Migrate to Oracle Cloud Infrastructure About the Migration Scope About Oracle Cloud Infrastructure About the Migration Task Flow About the Migration Tooling Video Why Migrate to Oracle Cloud Infrastructure Oracle encourages you to migrate your existing cloud resources to Oracle Cloud Infrastructure regions.You can gain several advantages by doing so.In Oracle Cloud, you provision resources in specific regions, which are localized to geographic locations.Certain regions support the Oracle Cloud Infrastructure platform.Oracle Cloud Infrastructure is Oracle's modern cloud platform that's based on the latest cloud technologies and standards.It provides more consistent performance and better features at lower costs.Oracle continues to invest in Oracle Cloud Infrastructure, including the addition of new regions, services, and features.See Data Regions for Platform and Infrastructure Services .You can benefit from these additional administrative features when you migrate your cloud resources to Oracle Cloud Infrastructure: Organize cloud resources into a hierarchy of logical compartments.Create fine-grained access policies for each compartment. |
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 vii1 Learn About Migrating to Oracle Cloud Infrastructure Learn about the benefits to migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, and receive an overview of the migration process and tools.Topics: Why Migrate to Oracle Cloud Infrastructure About the Migration Scope About Oracle Cloud Infrastructure About the Migration Task Flow About the Migration Tooling Video Why Migrate to Oracle Cloud Infrastructure Oracle encourages you to migrate your existing cloud resources to Oracle Cloud Infrastructure regions.You can gain several advantages by doing so.In Oracle Cloud, you provision resources in specific regions, which are localized to geographic locations.Certain regions support the Oracle Cloud Infrastructure platform.Oracle Cloud Infrastructure is Oracle's modern cloud platform that's based on the latest cloud technologies and standards.It provides more consistent performance and better features at lower costs.Oracle continues to invest in Oracle Cloud Infrastructure, including the addition of new regions, services, and features.See Data Regions for Platform and Infrastructure Services .You can benefit from these additional administrative features when you migrate your cloud resources to Oracle Cloud Infrastructure: Organize cloud resources into a hierarchy of logical compartments.Create fine-grained access policies for each compartment.About the Migration Scope Before migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, consider the scope and constraints of this migration path. |
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 vii1 Learn About Migrating to Oracle Cloud Infrastructure Learn about the benefits to migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, and receive an overview of the migration process and tools.Topics: Why Migrate to Oracle Cloud Infrastructure About the Migration Scope About Oracle Cloud Infrastructure About the Migration Task Flow About the Migration Tooling Video Why Migrate to Oracle Cloud Infrastructure Oracle encourages you to migrate your existing cloud resources to Oracle Cloud Infrastructure regions.You can gain several advantages by doing so.In Oracle Cloud, you provision resources in specific regions, which are localized to geographic locations.Certain regions support the Oracle Cloud Infrastructure platform.Oracle Cloud Infrastructure is Oracle's modern cloud platform that's based on the latest cloud technologies and standards.It provides more consistent performance and better features at lower costs.Oracle continues to invest in Oracle Cloud Infrastructure, including the addition of new regions, services, and features.See Data Regions for Platform and Infrastructure Services .You can benefit from these additional administrative features when you migrate your cloud resources to Oracle Cloud Infrastructure: Organize cloud resources into a hierarchy of logical compartments.Create fine-grained access policies for each compartment.About the Migration Scope Before migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, consider the scope and constraints of this migration path.There are restrictions to consider at the Oracle Integration Classic level and at the individual Integrations, Processes, and Visual Builder levels. |
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 vii1 Learn About Migrating to Oracle Cloud Infrastructure Learn about the benefits to migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, and receive an overview of the migration process and tools.Topics: Why Migrate to Oracle Cloud Infrastructure About the Migration Scope About Oracle Cloud Infrastructure About the Migration Task Flow About the Migration Tooling Video Why Migrate to Oracle Cloud Infrastructure Oracle encourages you to migrate your existing cloud resources to Oracle Cloud Infrastructure regions.You can gain several advantages by doing so.In Oracle Cloud, you provision resources in specific regions, which are localized to geographic locations.Certain regions support the Oracle Cloud Infrastructure platform.Oracle Cloud Infrastructure is Oracle's modern cloud platform that's based on the latest cloud technologies and standards.It provides more consistent performance and better features at lower costs.Oracle continues to invest in Oracle Cloud Infrastructure, including the addition of new regions, services, and features.See Data Regions for Platform and Infrastructure Services .You can benefit from these additional administrative features when you migrate your cloud resources to Oracle Cloud Infrastructure: Organize cloud resources into a hierarchy of logical compartments.Create fine-grained access policies for each compartment.About the Migration Scope Before migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, consider the scope and constraints of this migration path.There are restrictions to consider at the Oracle Integration Classic level and at the individual Integrations, Processes, and Visual Builder levels.Oracle Integration Classic Administration Restrictions Integrations Design-Time Metadata Migration Scope 1-1Integrations Migration Restrictions Processes Design-Time Metadata Migration Scope Processes Migration Restrictions Visual Builder Design-Time Metadata Migration Scope Visual Builder Migration Restrictions Oracle Integration Classic Administration Restrictions Understand the following restrictions when migrating Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure. |
monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vii1 Learn About Migrating to Oracle Cloud Infrastructure Learn about the benefits to migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, and receive an overview of the migration process and tools.Topics: Why Migrate to Oracle Cloud Infrastructure About the Migration Scope About Oracle Cloud Infrastructure About the Migration Task Flow About the Migration Tooling Video Why Migrate to Oracle Cloud Infrastructure Oracle encourages you to migrate your existing cloud resources to Oracle Cloud Infrastructure regions.You can gain several advantages by doing so.In Oracle Cloud, you provision resources in specific regions, which are localized to geographic locations.Certain regions support the Oracle Cloud Infrastructure platform.Oracle Cloud Infrastructure is Oracle's modern cloud platform that's based on the latest cloud technologies and standards.It provides more consistent performance and better features at lower costs.Oracle continues to invest in Oracle Cloud Infrastructure, including the addition of new regions, services, and features.See Data Regions for Platform and Infrastructure Services .You can benefit from these additional administrative features when you migrate your cloud resources to Oracle Cloud Infrastructure: Organize cloud resources into a hierarchy of logical compartments.Create fine-grained access policies for each compartment.About the Migration Scope Before migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, consider the scope and constraints of this migration path.There are restrictions to consider at the Oracle Integration Classic level and at the individual Integrations, Processes, and Visual Builder levels.Oracle Integration Classic Administration Restrictions Integrations Design-Time Metadata Migration Scope 1-1Integrations Migration Restrictions Processes Design-Time Metadata Migration Scope Processes Migration Restrictions Visual Builder Design-Time Metadata Migration Scope Visual Builder Migration Restrictions Oracle Integration Classic Administration Restrictions Understand the following restrictions when migrating Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.In addition to Oracle Integration Classic administration restrictions, there are also Integrations, Processes, and Visual Builder restrictions described in subsequent sections. |
Topics: Why Migrate to Oracle Cloud Infrastructure About the Migration Scope About Oracle Cloud Infrastructure About the Migration Task Flow About the Migration Tooling Video Why Migrate to Oracle Cloud Infrastructure Oracle encourages you to migrate your existing cloud resources to Oracle Cloud Infrastructure regions.You can gain several advantages by doing so.In Oracle Cloud, you provision resources in specific regions, which are localized to geographic locations.Certain regions support the Oracle Cloud Infrastructure platform.Oracle Cloud Infrastructure is Oracle's modern cloud platform that's based on the latest cloud technologies and standards.It provides more consistent performance and better features at lower costs.Oracle continues to invest in Oracle Cloud Infrastructure, including the addition of new regions, services, and features.See Data Regions for Platform and Infrastructure Services .You can benefit from these additional administrative features when you migrate your cloud resources to Oracle Cloud Infrastructure: Organize cloud resources into a hierarchy of logical compartments.Create fine-grained access policies for each compartment.About the Migration Scope Before migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, consider the scope and constraints of this migration path.There are restrictions to consider at the Oracle Integration Classic level and at the individual Integrations, Processes, and Visual Builder levels.Oracle Integration Classic Administration Restrictions Integrations Design-Time Metadata Migration Scope 1-1Integrations Migration Restrictions Processes Design-Time Metadata Migration Scope Processes Migration Restrictions Visual Builder Design-Time Metadata Migration Scope Visual Builder Migration Restrictions Oracle Integration Classic Administration Restrictions Understand the following restrictions when migrating Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.In addition to Oracle Integration Classic administration restrictions, there are also Integrations, Processes, and Visual Builder restrictions described in subsequent sections.Once migration is complete, you no longer manage your instances. |
You can gain several advantages by doing so.In Oracle Cloud, you provision resources in specific regions, which are localized to geographic locations.Certain regions support the Oracle Cloud Infrastructure platform.Oracle Cloud Infrastructure is Oracle's modern cloud platform that's based on the latest cloud technologies and standards.It provides more consistent performance and better features at lower costs.Oracle continues to invest in Oracle Cloud Infrastructure, including the addition of new regions, services, and features.See Data Regions for Platform and Infrastructure Services .You can benefit from these additional administrative features when you migrate your cloud resources to Oracle Cloud Infrastructure: Organize cloud resources into a hierarchy of logical compartments.Create fine-grained access policies for each compartment.About the Migration Scope Before migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, consider the scope and constraints of this migration path.There are restrictions to consider at the Oracle Integration Classic level and at the individual Integrations, Processes, and Visual Builder levels.Oracle Integration Classic Administration Restrictions Integrations Design-Time Metadata Migration Scope 1-1Integrations Migration Restrictions Processes Design-Time Metadata Migration Scope Processes Migration Restrictions Visual Builder Design-Time Metadata Migration Scope Visual Builder Migration Restrictions Oracle Integration Classic Administration Restrictions Understand the following restrictions when migrating Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.In addition to Oracle Integration Classic administration restrictions, there are also Integrations, Processes, and Visual Builder restrictions described in subsequent sections.Once migration is complete, you no longer manage your instances.Oracle manages your instances, including performing all backups and patching/upgrading. |
In Oracle Cloud, you provision resources in specific regions, which are localized to geographic locations.Certain regions support the Oracle Cloud Infrastructure platform.Oracle Cloud Infrastructure is Oracle's modern cloud platform that's based on the latest cloud technologies and standards.It provides more consistent performance and better features at lower costs.Oracle continues to invest in Oracle Cloud Infrastructure, including the addition of new regions, services, and features.See Data Regions for Platform and Infrastructure Services .You can benefit from these additional administrative features when you migrate your cloud resources to Oracle Cloud Infrastructure: Organize cloud resources into a hierarchy of logical compartments.Create fine-grained access policies for each compartment.About the Migration Scope Before migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, consider the scope and constraints of this migration path.There are restrictions to consider at the Oracle Integration Classic level and at the individual Integrations, Processes, and Visual Builder levels.Oracle Integration Classic Administration Restrictions Integrations Design-Time Metadata Migration Scope 1-1Integrations Migration Restrictions Processes Design-Time Metadata Migration Scope Processes Migration Restrictions Visual Builder Design-Time Metadata Migration Scope Visual Builder Migration Restrictions Oracle Integration Classic Administration Restrictions Understand the following restrictions when migrating Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.In addition to Oracle Integration Classic administration restrictions, there are also Integrations, Processes, and Visual Builder restrictions described in subsequent sections.Once migration is complete, you no longer manage your instances.Oracle manages your instances, including performing all backups and patching/upgrading.This enables you to concentrate on developing your integrations, processes, and applications. |
Certain regions support the Oracle Cloud Infrastructure platform.Oracle Cloud Infrastructure is Oracle's modern cloud platform that's based on the latest cloud technologies and standards.It provides more consistent performance and better features at lower costs.Oracle continues to invest in Oracle Cloud Infrastructure, including the addition of new regions, services, and features.See Data Regions for Platform and Infrastructure Services .You can benefit from these additional administrative features when you migrate your cloud resources to Oracle Cloud Infrastructure: Organize cloud resources into a hierarchy of logical compartments.Create fine-grained access policies for each compartment.About the Migration Scope Before migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, consider the scope and constraints of this migration path.There are restrictions to consider at the Oracle Integration Classic level and at the individual Integrations, Processes, and Visual Builder levels.Oracle Integration Classic Administration Restrictions Integrations Design-Time Metadata Migration Scope 1-1Integrations Migration Restrictions Processes Design-Time Metadata Migration Scope Processes Migration Restrictions Visual Builder Design-Time Metadata Migration Scope Visual Builder Migration Restrictions Oracle Integration Classic Administration Restrictions Understand the following restrictions when migrating Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.In addition to Oracle Integration Classic administration restrictions, there are also Integrations, Processes, and Visual Builder restrictions described in subsequent sections.Once migration is complete, you no longer manage your instances.Oracle manages your instances, including performing all backups and patching/upgrading.This enables you to concentrate on developing your integrations, processes, and applications.Restrictions By Design With the move to Oracle-managed instances, the following restrictions are by design. |
Oracle Cloud Infrastructure is Oracle's modern cloud platform that's based on the latest cloud technologies and standards.It provides more consistent performance and better features at lower costs.Oracle continues to invest in Oracle Cloud Infrastructure, including the addition of new regions, services, and features.See Data Regions for Platform and Infrastructure Services .You can benefit from these additional administrative features when you migrate your cloud resources to Oracle Cloud Infrastructure: Organize cloud resources into a hierarchy of logical compartments.Create fine-grained access policies for each compartment.About the Migration Scope Before migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, consider the scope and constraints of this migration path.There are restrictions to consider at the Oracle Integration Classic level and at the individual Integrations, Processes, and Visual Builder levels.Oracle Integration Classic Administration Restrictions Integrations Design-Time Metadata Migration Scope 1-1Integrations Migration Restrictions Processes Design-Time Metadata Migration Scope Processes Migration Restrictions Visual Builder Design-Time Metadata Migration Scope Visual Builder Migration Restrictions Oracle Integration Classic Administration Restrictions Understand the following restrictions when migrating Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.In addition to Oracle Integration Classic administration restrictions, there are also Integrations, Processes, and Visual Builder restrictions described in subsequent sections.Once migration is complete, you no longer manage your instances.Oracle manages your instances, including performing all backups and patching/upgrading.This enables you to concentrate on developing your integrations, processes, and applications.Restrictions By Design With the move to Oracle-managed instances, the following restrictions are by design.Any custom configurations done outside of the Oracle Integration Classic My Services Console are not migrated. |
It provides more consistent performance and better features at lower costs.Oracle continues to invest in Oracle Cloud Infrastructure, including the addition of new regions, services, and features.See Data Regions for Platform and Infrastructure Services .You can benefit from these additional administrative features when you migrate your cloud resources to Oracle Cloud Infrastructure: Organize cloud resources into a hierarchy of logical compartments.Create fine-grained access policies for each compartment.About the Migration Scope Before migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, consider the scope and constraints of this migration path.There are restrictions to consider at the Oracle Integration Classic level and at the individual Integrations, Processes, and Visual Builder levels.Oracle Integration Classic Administration Restrictions Integrations Design-Time Metadata Migration Scope 1-1Integrations Migration Restrictions Processes Design-Time Metadata Migration Scope Processes Migration Restrictions Visual Builder Design-Time Metadata Migration Scope Visual Builder Migration Restrictions Oracle Integration Classic Administration Restrictions Understand the following restrictions when migrating Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.In addition to Oracle Integration Classic administration restrictions, there are also Integrations, Processes, and Visual Builder restrictions described in subsequent sections.Once migration is complete, you no longer manage your instances.Oracle manages your instances, including performing all backups and patching/upgrading.This enables you to concentrate on developing your integrations, processes, and applications.Restrictions By Design With the move to Oracle-managed instances, the following restrictions are by design.Any custom configurations done outside of the Oracle Integration Classic My Services Console are not migrated.For example: Configurations performed through direct VM access Configurations performed through consoles such as Oracle WebLogic Server Console, Oracle Enterprise Manager Console, and others Any external processes you created ( cron jobs, Javascripting, and so on) There are additional customizations that are not supported. |
Oracle continues to invest in Oracle Cloud Infrastructure, including the addition of new regions, services, and features.See Data Regions for Platform and Infrastructure Services .You can benefit from these additional administrative features when you migrate your cloud resources to Oracle Cloud Infrastructure: Organize cloud resources into a hierarchy of logical compartments.Create fine-grained access policies for each compartment.About the Migration Scope Before migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, consider the scope and constraints of this migration path.There are restrictions to consider at the Oracle Integration Classic level and at the individual Integrations, Processes, and Visual Builder levels.Oracle Integration Classic Administration Restrictions Integrations Design-Time Metadata Migration Scope 1-1Integrations Migration Restrictions Processes Design-Time Metadata Migration Scope Processes Migration Restrictions Visual Builder Design-Time Metadata Migration Scope Visual Builder Migration Restrictions Oracle Integration Classic Administration Restrictions Understand the following restrictions when migrating Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.In addition to Oracle Integration Classic administration restrictions, there are also Integrations, Processes, and Visual Builder restrictions described in subsequent sections.Once migration is complete, you no longer manage your instances.Oracle manages your instances, including performing all backups and patching/upgrading.This enables you to concentrate on developing your integrations, processes, and applications.Restrictions By Design With the move to Oracle-managed instances, the following restrictions are by design.Any custom configurations done outside of the Oracle Integration Classic My Services Console are not migrated.For example: Configurations performed through direct VM access Configurations performed through consoles such as Oracle WebLogic Server Console, Oracle Enterprise Manager Console, and others Any external processes you created ( cron jobs, Javascripting, and so on) There are additional customizations that are not supported.See Unsupported Tasks of Administering Oracle Integration . |
See Data Regions for Platform and Infrastructure Services .You can benefit from these additional administrative features when you migrate your cloud resources to Oracle Cloud Infrastructure: Organize cloud resources into a hierarchy of logical compartments.Create fine-grained access policies for each compartment.About the Migration Scope Before migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, consider the scope and constraints of this migration path.There are restrictions to consider at the Oracle Integration Classic level and at the individual Integrations, Processes, and Visual Builder levels.Oracle Integration Classic Administration Restrictions Integrations Design-Time Metadata Migration Scope 1-1Integrations Migration Restrictions Processes Design-Time Metadata Migration Scope Processes Migration Restrictions Visual Builder Design-Time Metadata Migration Scope Visual Builder Migration Restrictions Oracle Integration Classic Administration Restrictions Understand the following restrictions when migrating Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.In addition to Oracle Integration Classic administration restrictions, there are also Integrations, Processes, and Visual Builder restrictions described in subsequent sections.Once migration is complete, you no longer manage your instances.Oracle manages your instances, including performing all backups and patching/upgrading.This enables you to concentrate on developing your integrations, processes, and applications.Restrictions By Design With the move to Oracle-managed instances, the following restrictions are by design.Any custom configurations done outside of the Oracle Integration Classic My Services Console are not migrated.For example: Configurations performed through direct VM access Configurations performed through consoles such as Oracle WebLogic Server Console, Oracle Enterprise Manager Console, and others Any external processes you created ( cron jobs, Javascripting, and so on) There are additional customizations that are not supported.See Unsupported Tasks of Administering Oracle Integration .You cannot log in to and access virtual machines (VMs). |
You can benefit from these additional administrative features when you migrate your cloud resources to Oracle Cloud Infrastructure: Organize cloud resources into a hierarchy of logical compartments.Create fine-grained access policies for each compartment.About the Migration Scope Before migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, consider the scope and constraints of this migration path.There are restrictions to consider at the Oracle Integration Classic level and at the individual Integrations, Processes, and Visual Builder levels.Oracle Integration Classic Administration Restrictions Integrations Design-Time Metadata Migration Scope 1-1Integrations Migration Restrictions Processes Design-Time Metadata Migration Scope Processes Migration Restrictions Visual Builder Design-Time Metadata Migration Scope Visual Builder Migration Restrictions Oracle Integration Classic Administration Restrictions Understand the following restrictions when migrating Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.In addition to Oracle Integration Classic administration restrictions, there are also Integrations, Processes, and Visual Builder restrictions described in subsequent sections.Once migration is complete, you no longer manage your instances.Oracle manages your instances, including performing all backups and patching/upgrading.This enables you to concentrate on developing your integrations, processes, and applications.Restrictions By Design With the move to Oracle-managed instances, the following restrictions are by design.Any custom configurations done outside of the Oracle Integration Classic My Services Console are not migrated.For example: Configurations performed through direct VM access Configurations performed through consoles such as Oracle WebLogic Server Console, Oracle Enterprise Manager Console, and others Any external processes you created ( cron jobs, Javascripting, and so on) There are additional customizations that are not supported.See Unsupported Tasks of Administering Oracle Integration .You cannot log in to and access virtual machines (VMs).There is no log management through VM access. |
Create fine-grained access policies for each compartment.About the Migration Scope Before migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, consider the scope and constraints of this migration path.There are restrictions to consider at the Oracle Integration Classic level and at the individual Integrations, Processes, and Visual Builder levels.Oracle Integration Classic Administration Restrictions Integrations Design-Time Metadata Migration Scope 1-1Integrations Migration Restrictions Processes Design-Time Metadata Migration Scope Processes Migration Restrictions Visual Builder Design-Time Metadata Migration Scope Visual Builder Migration Restrictions Oracle Integration Classic Administration Restrictions Understand the following restrictions when migrating Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.In addition to Oracle Integration Classic administration restrictions, there are also Integrations, Processes, and Visual Builder restrictions described in subsequent sections.Once migration is complete, you no longer manage your instances.Oracle manages your instances, including performing all backups and patching/upgrading.This enables you to concentrate on developing your integrations, processes, and applications.Restrictions By Design With the move to Oracle-managed instances, the following restrictions are by design.Any custom configurations done outside of the Oracle Integration Classic My Services Console are not migrated.For example: Configurations performed through direct VM access Configurations performed through consoles such as Oracle WebLogic Server Console, Oracle Enterprise Manager Console, and others Any external processes you created ( cron jobs, Javascripting, and so on) There are additional customizations that are not supported.See Unsupported Tasks of Administering Oracle Integration .You cannot log in to and access virtual machines (VMs).There is no log management through VM access.SSH access is not supported. |
About the Migration Scope Before migrating your existing Oracle Integration Classic instances to Oracle Integration on Oracle Cloud Infrastructure, consider the scope and constraints of this migration path.There are restrictions to consider at the Oracle Integration Classic level and at the individual Integrations, Processes, and Visual Builder levels.Oracle Integration Classic Administration Restrictions Integrations Design-Time Metadata Migration Scope 1-1Integrations Migration Restrictions Processes Design-Time Metadata Migration Scope Processes Migration Restrictions Visual Builder Design-Time Metadata Migration Scope Visual Builder Migration Restrictions Oracle Integration Classic Administration Restrictions Understand the following restrictions when migrating Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.In addition to Oracle Integration Classic administration restrictions, there are also Integrations, Processes, and Visual Builder restrictions described in subsequent sections.Once migration is complete, you no longer manage your instances.Oracle manages your instances, including performing all backups and patching/upgrading.This enables you to concentrate on developing your integrations, processes, and applications.Restrictions By Design With the move to Oracle-managed instances, the following restrictions are by design.Any custom configurations done outside of the Oracle Integration Classic My Services Console are not migrated.For example: Configurations performed through direct VM access Configurations performed through consoles such as Oracle WebLogic Server Console, Oracle Enterprise Manager Console, and others Any external processes you created ( cron jobs, Javascripting, and so on) There are additional customizations that are not supported.See Unsupported Tasks of Administering Oracle Integration .You cannot log in to and access virtual machines (VMs).There is no log management through VM access.SSH access is not supported.IP addresses change between Oracle Integration Classic and Oracle Integration, meaning you must update any client applications with which your integrations communicate (for example, Oracle ERP Cloud, Oracle HCM Cloud, and others). |
There are restrictions to consider at the Oracle Integration Classic level and at the individual Integrations, Processes, and Visual Builder levels.Oracle Integration Classic Administration Restrictions Integrations Design-Time Metadata Migration Scope 1-1Integrations Migration Restrictions Processes Design-Time Metadata Migration Scope Processes Migration Restrictions Visual Builder Design-Time Metadata Migration Scope Visual Builder Migration Restrictions Oracle Integration Classic Administration Restrictions Understand the following restrictions when migrating Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.In addition to Oracle Integration Classic administration restrictions, there are also Integrations, Processes, and Visual Builder restrictions described in subsequent sections.Once migration is complete, you no longer manage your instances.Oracle manages your instances, including performing all backups and patching/upgrading.This enables you to concentrate on developing your integrations, processes, and applications.Restrictions By Design With the move to Oracle-managed instances, the following restrictions are by design.Any custom configurations done outside of the Oracle Integration Classic My Services Console are not migrated.For example: Configurations performed through direct VM access Configurations performed through consoles such as Oracle WebLogic Server Console, Oracle Enterprise Manager Console, and others Any external processes you created ( cron jobs, Javascripting, and so on) There are additional customizations that are not supported.See Unsupported Tasks of Administering Oracle Integration .You cannot log in to and access virtual machines (VMs).There is no log management through VM access.SSH access is not supported.IP addresses change between Oracle Integration Classic and Oracle Integration, meaning you must update any client applications with which your integrations communicate (for example, Oracle ERP Cloud, Oracle HCM Cloud, and others).You cannot log in and manage the Oracle Cloud Infrastructure database (and therefore, application data). |
Oracle Integration Classic Administration Restrictions Integrations Design-Time Metadata Migration Scope 1-1Integrations Migration Restrictions Processes Design-Time Metadata Migration Scope Processes Migration Restrictions Visual Builder Design-Time Metadata Migration Scope Visual Builder Migration Restrictions Oracle Integration Classic Administration Restrictions Understand the following restrictions when migrating Oracle Integration Classic to Oracle Integration on Oracle Cloud Infrastructure.In addition to Oracle Integration Classic administration restrictions, there are also Integrations, Processes, and Visual Builder restrictions described in subsequent sections.Once migration is complete, you no longer manage your instances.Oracle manages your instances, including performing all backups and patching/upgrading.This enables you to concentrate on developing your integrations, processes, and applications.Restrictions By Design With the move to Oracle-managed instances, the following restrictions are by design.Any custom configurations done outside of the Oracle Integration Classic My Services Console are not migrated.For example: Configurations performed through direct VM access Configurations performed through consoles such as Oracle WebLogic Server Console, Oracle Enterprise Manager Console, and others Any external processes you created ( cron jobs, Javascripting, and so on) There are additional customizations that are not supported.See Unsupported Tasks of Administering Oracle Integration .You cannot log in to and access virtual machines (VMs).There is no log management through VM access.SSH access is not supported.IP addresses change between Oracle Integration Classic and Oracle Integration, meaning you must update any client applications with which your integrations communicate (for example, Oracle ERP Cloud, Oracle HCM Cloud, and others).You cannot log in and manage the Oracle Cloud Infrastructure database (and therefore, application data).Oracle performs all backup and patching/upgrading tasks. |
In addition to Oracle Integration Classic administration restrictions, there are also Integrations, Processes, and Visual Builder restrictions described in subsequent sections.Once migration is complete, you no longer manage your instances.Oracle manages your instances, including performing all backups and patching/upgrading.This enables you to concentrate on developing your integrations, processes, and applications.Restrictions By Design With the move to Oracle-managed instances, the following restrictions are by design.Any custom configurations done outside of the Oracle Integration Classic My Services Console are not migrated.For example: Configurations performed through direct VM access Configurations performed through consoles such as Oracle WebLogic Server Console, Oracle Enterprise Manager Console, and others Any external processes you created ( cron jobs, Javascripting, and so on) There are additional customizations that are not supported.See Unsupported Tasks of Administering Oracle Integration .You cannot log in to and access virtual machines (VMs).There is no log management through VM access.SSH access is not supported.IP addresses change between Oracle Integration Classic and Oracle Integration, meaning you must update any client applications with which your integrations communicate (for example, Oracle ERP Cloud, Oracle HCM Cloud, and others).You cannot log in and manage the Oracle Cloud Infrastructure database (and therefore, application data).Oracle performs all backup and patching/upgrading tasks.The only administration tasks you can perform are those accessible from the Oracle Integration My Services Console. |
Once migration is complete, you no longer manage your instances.Oracle manages your instances, including performing all backups and patching/upgrading.This enables you to concentrate on developing your integrations, processes, and applications.Restrictions By Design With the move to Oracle-managed instances, the following restrictions are by design.Any custom configurations done outside of the Oracle Integration Classic My Services Console are not migrated.For example: Configurations performed through direct VM access Configurations performed through consoles such as Oracle WebLogic Server Console, Oracle Enterprise Manager Console, and others Any external processes you created ( cron jobs, Javascripting, and so on) There are additional customizations that are not supported.See Unsupported Tasks of Administering Oracle Integration .You cannot log in to and access virtual machines (VMs).There is no log management through VM access.SSH access is not supported.IP addresses change between Oracle Integration Classic and Oracle Integration, meaning you must update any client applications with which your integrations communicate (for example, Oracle ERP Cloud, Oracle HCM Cloud, and others).You cannot log in and manage the Oracle Cloud Infrastructure database (and therefore, application data).Oracle performs all backup and patching/upgrading tasks.The only administration tasks you can perform are those accessible from the Oracle Integration My Services Console.Custom XPath functions and custom Javascript code are not supported. |
Oracle manages your instances, including performing all backups and patching/upgrading.This enables you to concentrate on developing your integrations, processes, and applications.Restrictions By Design With the move to Oracle-managed instances, the following restrictions are by design.Any custom configurations done outside of the Oracle Integration Classic My Services Console are not migrated.For example: Configurations performed through direct VM access Configurations performed through consoles such as Oracle WebLogic Server Console, Oracle Enterprise Manager Console, and others Any external processes you created ( cron jobs, Javascripting, and so on) There are additional customizations that are not supported.See Unsupported Tasks of Administering Oracle Integration .You cannot log in to and access virtual machines (VMs).There is no log management through VM access.SSH access is not supported.IP addresses change between Oracle Integration Classic and Oracle Integration, meaning you must update any client applications with which your integrations communicate (for example, Oracle ERP Cloud, Oracle HCM Cloud, and others).You cannot log in and manage the Oracle Cloud Infrastructure database (and therefore, application data).Oracle performs all backup and patching/upgrading tasks.The only administration tasks you can perform are those accessible from the Oracle Integration My Services Console.Custom XPath functions and custom Javascript code are not supported.Life cycle management REST APIs (for example, backing up, restoring, and patching) are not supported. |
This enables you to concentrate on developing your integrations, processes, and applications.Restrictions By Design With the move to Oracle-managed instances, the following restrictions are by design.Any custom configurations done outside of the Oracle Integration Classic My Services Console are not migrated.For example: Configurations performed through direct VM access Configurations performed through consoles such as Oracle WebLogic Server Console, Oracle Enterprise Manager Console, and others Any external processes you created ( cron jobs, Javascripting, and so on) There are additional customizations that are not supported.See Unsupported Tasks of Administering Oracle Integration .You cannot log in to and access virtual machines (VMs).There is no log management through VM access.SSH access is not supported.IP addresses change between Oracle Integration Classic and Oracle Integration, meaning you must update any client applications with which your integrations communicate (for example, Oracle ERP Cloud, Oracle HCM Cloud, and others).You cannot log in and manage the Oracle Cloud Infrastructure database (and therefore, application data).Oracle performs all backup and patching/upgrading tasks.The only administration tasks you can perform are those accessible from the Oracle Integration My Services Console.Custom XPath functions and custom Javascript code are not supported.Life cycle management REST APIs (for example, backing up, restoring, and patching) are not supported.Transport Level Security versions 1.0 and 1.1 are not supported. |
Restrictions By Design With the move to Oracle-managed instances, the following restrictions are by design.Any custom configurations done outside of the Oracle Integration Classic My Services Console are not migrated.For example: Configurations performed through direct VM access Configurations performed through consoles such as Oracle WebLogic Server Console, Oracle Enterprise Manager Console, and others Any external processes you created ( cron jobs, Javascripting, and so on) There are additional customizations that are not supported.See Unsupported Tasks of Administering Oracle Integration .You cannot log in to and access virtual machines (VMs).There is no log management through VM access.SSH access is not supported.IP addresses change between Oracle Integration Classic and Oracle Integration, meaning you must update any client applications with which your integrations communicate (for example, Oracle ERP Cloud, Oracle HCM Cloud, and others).You cannot log in and manage the Oracle Cloud Infrastructure database (and therefore, application data).Oracle performs all backup and patching/upgrading tasks.The only administration tasks you can perform are those accessible from the Oracle Integration My Services Console.Custom XPath functions and custom Javascript code are not supported.Life cycle management REST APIs (for example, backing up, restoring, and patching) are not supported.Transport Level Security versions 1.0 and 1.1 are not supported.Oracle Integration endpoints support only TLS 1.2 as a trigger connection. |
Any custom configurations done outside of the Oracle Integration Classic My Services Console are not migrated.For example: Configurations performed through direct VM access Configurations performed through consoles such as Oracle WebLogic Server Console, Oracle Enterprise Manager Console, and others Any external processes you created ( cron jobs, Javascripting, and so on) There are additional customizations that are not supported.See Unsupported Tasks of Administering Oracle Integration .You cannot log in to and access virtual machines (VMs).There is no log management through VM access.SSH access is not supported.IP addresses change between Oracle Integration Classic and Oracle Integration, meaning you must update any client applications with which your integrations communicate (for example, Oracle ERP Cloud, Oracle HCM Cloud, and others).You cannot log in and manage the Oracle Cloud Infrastructure database (and therefore, application data).Oracle performs all backup and patching/upgrading tasks.The only administration tasks you can perform are those accessible from the Oracle Integration My Services Console.Custom XPath functions and custom Javascript code are not supported.Life cycle management REST APIs (for example, backing up, restoring, and patching) are not supported.Transport Level Security versions 1.0 and 1.1 are not supported.Oracle Integration endpoints support only TLS 1.2 as a trigger connection.Ensure that you configure your client to use TLS 1.2 when invoking Oracle Integration services.Chapter 1 About the Migration Scope 1-2Additional Restrictions Private endpoints are not supported. |
For example: Configurations performed through direct VM access Configurations performed through consoles such as Oracle WebLogic Server Console, Oracle Enterprise Manager Console, and others Any external processes you created ( cron jobs, Javascripting, and so on) There are additional customizations that are not supported.See Unsupported Tasks of Administering Oracle Integration .You cannot log in to and access virtual machines (VMs).There is no log management through VM access.SSH access is not supported.IP addresses change between Oracle Integration Classic and Oracle Integration, meaning you must update any client applications with which your integrations communicate (for example, Oracle ERP Cloud, Oracle HCM Cloud, and others).You cannot log in and manage the Oracle Cloud Infrastructure database (and therefore, application data).Oracle performs all backup and patching/upgrading tasks.The only administration tasks you can perform are those accessible from the Oracle Integration My Services Console.Custom XPath functions and custom Javascript code are not supported.Life cycle management REST APIs (for example, backing up, restoring, and patching) are not supported.Transport Level Security versions 1.0 and 1.1 are not supported.Oracle Integration endpoints support only TLS 1.2 as a trigger connection.Ensure that you configure your client to use TLS 1.2 when invoking Oracle Integration services.Chapter 1 About the Migration Scope 1-2Additional Restrictions Private endpoints are not supported.Integration Analytics (which consists of Stream Analytics and Integration Insight) is not supported. |
See Unsupported Tasks of Administering Oracle Integration .You cannot log in to and access virtual machines (VMs).There is no log management through VM access.SSH access is not supported.IP addresses change between Oracle Integration Classic and Oracle Integration, meaning you must update any client applications with which your integrations communicate (for example, Oracle ERP Cloud, Oracle HCM Cloud, and others).You cannot log in and manage the Oracle Cloud Infrastructure database (and therefore, application data).Oracle performs all backup and patching/upgrading tasks.The only administration tasks you can perform are those accessible from the Oracle Integration My Services Console.Custom XPath functions and custom Javascript code are not supported.Life cycle management REST APIs (for example, backing up, restoring, and patching) are not supported.Transport Level Security versions 1.0 and 1.1 are not supported.Oracle Integration endpoints support only TLS 1.2 as a trigger connection.Ensure that you configure your client to use TLS 1.2 when invoking Oracle Integration services.Chapter 1 About the Migration Scope 1-2Additional Restrictions Private endpoints are not supported.Integration Analytics (which consists of Stream Analytics and Integration Insight) is not supported.Integrations Design-Time Metadata Migration Scope You export Integrations design-time metadata into an archive file to then import into Oracle Integration on Oracle Cloud Infrastructure. |
You cannot log in to and access virtual machines (VMs).There is no log management through VM access.SSH access is not supported.IP addresses change between Oracle Integration Classic and Oracle Integration, meaning you must update any client applications with which your integrations communicate (for example, Oracle ERP Cloud, Oracle HCM Cloud, and others).You cannot log in and manage the Oracle Cloud Infrastructure database (and therefore, application data).Oracle performs all backup and patching/upgrading tasks.The only administration tasks you can perform are those accessible from the Oracle Integration My Services Console.Custom XPath functions and custom Javascript code are not supported.Life cycle management REST APIs (for example, backing up, restoring, and patching) are not supported.Transport Level Security versions 1.0 and 1.1 are not supported.Oracle Integration endpoints support only TLS 1.2 as a trigger connection.Ensure that you configure your client to use TLS 1.2 when invoking Oracle Integration services.Chapter 1 About the Migration Scope 1-2Additional Restrictions Private endpoints are not supported.Integration Analytics (which consists of Stream Analytics and Integration Insight) is not supported.Integrations Design-Time Metadata Migration Scope You export Integrations design-time metadata into an archive file to then import into Oracle Integration on Oracle Cloud Infrastructure.The archive file consists of the following design- time metadata. |
There is no log management through VM access.SSH access is not supported.IP addresses change between Oracle Integration Classic and Oracle Integration, meaning you must update any client applications with which your integrations communicate (for example, Oracle ERP Cloud, Oracle HCM Cloud, and others).You cannot log in and manage the Oracle Cloud Infrastructure database (and therefore, application data).Oracle performs all backup and patching/upgrading tasks.The only administration tasks you can perform are those accessible from the Oracle Integration My Services Console.Custom XPath functions and custom Javascript code are not supported.Life cycle management REST APIs (for example, backing up, restoring, and patching) are not supported.Transport Level Security versions 1.0 and 1.1 are not supported.Oracle Integration endpoints support only TLS 1.2 as a trigger connection.Ensure that you configure your client to use TLS 1.2 when invoking Oracle Integration services.Chapter 1 About the Migration Scope 1-2Additional Restrictions Private endpoints are not supported.Integration Analytics (which consists of Stream Analytics and Integration Insight) is not supported.Integrations Design-Time Metadata Migration Scope You export Integrations design-time metadata into an archive file to then import into Oracle Integration on Oracle Cloud Infrastructure.The archive file consists of the following design- time metadata.Integrations, connections, lookups, agent groups, and so on. |
SSH access is not supported.IP addresses change between Oracle Integration Classic and Oracle Integration, meaning you must update any client applications with which your integrations communicate (for example, Oracle ERP Cloud, Oracle HCM Cloud, and others).You cannot log in and manage the Oracle Cloud Infrastructure database (and therefore, application data).Oracle performs all backup and patching/upgrading tasks.The only administration tasks you can perform are those accessible from the Oracle Integration My Services Console.Custom XPath functions and custom Javascript code are not supported.Life cycle management REST APIs (for example, backing up, restoring, and patching) are not supported.Transport Level Security versions 1.0 and 1.1 are not supported.Oracle Integration endpoints support only TLS 1.2 as a trigger connection.Ensure that you configure your client to use TLS 1.2 when invoking Oracle Integration services.Chapter 1 About the Migration Scope 1-2Additional Restrictions Private endpoints are not supported.Integration Analytics (which consists of Stream Analytics and Integration Insight) is not supported.Integrations Design-Time Metadata Migration Scope You export Integrations design-time metadata into an archive file to then import into Oracle Integration on Oracle Cloud Infrastructure.The archive file consists of the following design- time metadata.Integrations, connections, lookups, agent groups, and so on.Note that: Integrations, connections, or objects in any state (in-progress, activated, and so on) are exported. |
IP addresses change between Oracle Integration Classic and Oracle Integration, meaning you must update any client applications with which your integrations communicate (for example, Oracle ERP Cloud, Oracle HCM Cloud, and others).You cannot log in and manage the Oracle Cloud Infrastructure database (and therefore, application data).Oracle performs all backup and patching/upgrading tasks.The only administration tasks you can perform are those accessible from the Oracle Integration My Services Console.Custom XPath functions and custom Javascript code are not supported.Life cycle management REST APIs (for example, backing up, restoring, and patching) are not supported.Transport Level Security versions 1.0 and 1.1 are not supported.Oracle Integration endpoints support only TLS 1.2 as a trigger connection.Ensure that you configure your client to use TLS 1.2 when invoking Oracle Integration services.Chapter 1 About the Migration Scope 1-2Additional Restrictions Private endpoints are not supported.Integration Analytics (which consists of Stream Analytics and Integration Insight) is not supported.Integrations Design-Time Metadata Migration Scope You export Integrations design-time metadata into an archive file to then import into Oracle Integration on Oracle Cloud Infrastructure.The archive file consists of the following design- time metadata.Integrations, connections, lookups, agent groups, and so on.Note that: Integrations, connections, or objects in any state (in-progress, activated, and so on) are exported.All resources such as lookups and connections that are not currently referenced by integrations are exported. |
You cannot log in and manage the Oracle Cloud Infrastructure database (and therefore, application data).Oracle performs all backup and patching/upgrading tasks.The only administration tasks you can perform are those accessible from the Oracle Integration My Services Console.Custom XPath functions and custom Javascript code are not supported.Life cycle management REST APIs (for example, backing up, restoring, and patching) are not supported.Transport Level Security versions 1.0 and 1.1 are not supported.Oracle Integration endpoints support only TLS 1.2 as a trigger connection.Ensure that you configure your client to use TLS 1.2 when invoking Oracle Integration services.Chapter 1 About the Migration Scope 1-2Additional Restrictions Private endpoints are not supported.Integration Analytics (which consists of Stream Analytics and Integration Insight) is not supported.Integrations Design-Time Metadata Migration Scope You export Integrations design-time metadata into an archive file to then import into Oracle Integration on Oracle Cloud Infrastructure.The archive file consists of the following design- time metadata.Integrations, connections, lookups, agent groups, and so on.Note that: Integrations, connections, or objects in any state (in-progress, activated, and so on) are exported.All resources such as lookups and connections that are not currently referenced by integrations are exported.Endpoint configurations User-defined credentials. |
Oracle performs all backup and patching/upgrading tasks.The only administration tasks you can perform are those accessible from the Oracle Integration My Services Console.Custom XPath functions and custom Javascript code are not supported.Life cycle management REST APIs (for example, backing up, restoring, and patching) are not supported.Transport Level Security versions 1.0 and 1.1 are not supported.Oracle Integration endpoints support only TLS 1.2 as a trigger connection.Ensure that you configure your client to use TLS 1.2 when invoking Oracle Integration services.Chapter 1 About the Migration Scope 1-2Additional Restrictions Private endpoints are not supported.Integration Analytics (which consists of Stream Analytics and Integration Insight) is not supported.Integrations Design-Time Metadata Migration Scope You export Integrations design-time metadata into an archive file to then import into Oracle Integration on Oracle Cloud Infrastructure.The archive file consists of the following design- time metadata.Integrations, connections, lookups, agent groups, and so on.Note that: Integrations, connections, or objects in any state (in-progress, activated, and so on) are exported.All resources such as lookups and connections that are not currently referenced by integrations are exported.Endpoint configurations User-defined credentials.Note the following details: Credentials are exported into cwallet.sso. |
The only administration tasks you can perform are those accessible from the Oracle Integration My Services Console.Custom XPath functions and custom Javascript code are not supported.Life cycle management REST APIs (for example, backing up, restoring, and patching) are not supported.Transport Level Security versions 1.0 and 1.1 are not supported.Oracle Integration endpoints support only TLS 1.2 as a trigger connection.Ensure that you configure your client to use TLS 1.2 when invoking Oracle Integration services.Chapter 1 About the Migration Scope 1-2Additional Restrictions Private endpoints are not supported.Integration Analytics (which consists of Stream Analytics and Integration Insight) is not supported.Integrations Design-Time Metadata Migration Scope You export Integrations design-time metadata into an archive file to then import into Oracle Integration on Oracle Cloud Infrastructure.The archive file consists of the following design- time metadata.Integrations, connections, lookups, agent groups, and so on.Note that: Integrations, connections, or objects in any state (in-progress, activated, and so on) are exported.All resources such as lookups and connections that are not currently referenced by integrations are exported.Endpoint configurations User-defined credentials.Note the following details: Credentials are exported into cwallet.sso.The oracle.cloud.adapter map and oracle.wsm.security maps are imported. |
Custom XPath functions and custom Javascript code are not supported.Life cycle management REST APIs (for example, backing up, restoring, and patching) are not supported.Transport Level Security versions 1.0 and 1.1 are not supported.Oracle Integration endpoints support only TLS 1.2 as a trigger connection.Ensure that you configure your client to use TLS 1.2 when invoking Oracle Integration services.Chapter 1 About the Migration Scope 1-2Additional Restrictions Private endpoints are not supported.Integration Analytics (which consists of Stream Analytics and Integration Insight) is not supported.Integrations Design-Time Metadata Migration Scope You export Integrations design-time metadata into an archive file to then import into Oracle Integration on Oracle Cloud Infrastructure.The archive file consists of the following design- time metadata.Integrations, connections, lookups, agent groups, and so on.Note that: Integrations, connections, or objects in any state (in-progress, activated, and so on) are exported.All resources such as lookups and connections that are not currently referenced by integrations are exported.Endpoint configurations User-defined credentials.Note the following details: Credentials are exported into cwallet.sso.The oracle.cloud.adapter map and oracle.wsm.security maps are imported.User-defined certificates (not the seeded certificates). |
Life cycle management REST APIs (for example, backing up, restoring, and patching) are not supported.Transport Level Security versions 1.0 and 1.1 are not supported.Oracle Integration endpoints support only TLS 1.2 as a trigger connection.Ensure that you configure your client to use TLS 1.2 when invoking Oracle Integration services.Chapter 1 About the Migration Scope 1-2Additional Restrictions Private endpoints are not supported.Integration Analytics (which consists of Stream Analytics and Integration Insight) is not supported.Integrations Design-Time Metadata Migration Scope You export Integrations design-time metadata into an archive file to then import into Oracle Integration on Oracle Cloud Infrastructure.The archive file consists of the following design- time metadata.Integrations, connections, lookups, agent groups, and so on.Note that: Integrations, connections, or objects in any state (in-progress, activated, and so on) are exported.All resources such as lookups and connections that are not currently referenced by integrations are exported.Endpoint configurations User-defined credentials.Note the following details: Credentials are exported into cwallet.sso.The oracle.cloud.adapter map and oracle.wsm.security maps are imported.User-defined certificates (not the seeded certificates).Only user-uploaded trusted certificates (whose alias begins with icsuser_||_ ) from the following keystores are exported: system/trust owsm/keystore ics/keystore All security policies. |
Transport Level Security versions 1.0 and 1.1 are not supported.Oracle Integration endpoints support only TLS 1.2 as a trigger connection.Ensure that you configure your client to use TLS 1.2 when invoking Oracle Integration services.Chapter 1 About the Migration Scope 1-2Additional Restrictions Private endpoints are not supported.Integration Analytics (which consists of Stream Analytics and Integration Insight) is not supported.Integrations Design-Time Metadata Migration Scope You export Integrations design-time metadata into an archive file to then import into Oracle Integration on Oracle Cloud Infrastructure.The archive file consists of the following design- time metadata.Integrations, connections, lookups, agent groups, and so on.Note that: Integrations, connections, or objects in any state (in-progress, activated, and so on) are exported.All resources such as lookups and connections that are not currently referenced by integrations are exported.Endpoint configurations User-defined credentials.Note the following details: Credentials are exported into cwallet.sso.The oracle.cloud.adapter map and oracle.wsm.security maps are imported.User-defined certificates (not the seeded certificates).Only user-uploaded trusted certificates (whose alias begins with icsuser_||_ ) from the following keystores are exported: system/trust owsm/keystore ics/keystore All security policies.Existing policies are not overwritten. |
Oracle Integration endpoints support only TLS 1.2 as a trigger connection.Ensure that you configure your client to use TLS 1.2 when invoking Oracle Integration services.Chapter 1 About the Migration Scope 1-2Additional Restrictions Private endpoints are not supported.Integration Analytics (which consists of Stream Analytics and Integration Insight) is not supported.Integrations Design-Time Metadata Migration Scope You export Integrations design-time metadata into an archive file to then import into Oracle Integration on Oracle Cloud Infrastructure.The archive file consists of the following design- time metadata.Integrations, connections, lookups, agent groups, and so on.Note that: Integrations, connections, or objects in any state (in-progress, activated, and so on) are exported.All resources such as lookups and connections that are not currently referenced by integrations are exported.Endpoint configurations User-defined credentials.Note the following details: Credentials are exported into cwallet.sso.The oracle.cloud.adapter map and oracle.wsm.security maps are imported.User-defined certificates (not the seeded certificates).Only user-uploaded trusted certificates (whose alias begins with icsuser_||_ ) from the following keystores are exported: system/trust owsm/keystore ics/keystore All security policies.Existing policies are not overwritten.Connection passwords stored in the CSF store. |
Ensure that you configure your client to use TLS 1.2 when invoking Oracle Integration services.Chapter 1 About the Migration Scope 1-2Additional Restrictions Private endpoints are not supported.Integration Analytics (which consists of Stream Analytics and Integration Insight) is not supported.Integrations Design-Time Metadata Migration Scope You export Integrations design-time metadata into an archive file to then import into Oracle Integration on Oracle Cloud Infrastructure.The archive file consists of the following design- time metadata.Integrations, connections, lookups, agent groups, and so on.Note that: Integrations, connections, or objects in any state (in-progress, activated, and so on) are exported.All resources such as lookups and connections that are not currently referenced by integrations are exported.Endpoint configurations User-defined credentials.Note the following details: Credentials are exported into cwallet.sso.The oracle.cloud.adapter map and oracle.wsm.security maps are imported.User-defined certificates (not the seeded certificates).Only user-uploaded trusted certificates (whose alias begins with icsuser_||_ ) from the following keystores are exported: system/trust owsm/keystore ics/keystore All security policies.Existing policies are not overwritten.Connection passwords stored in the CSF store.Settings such as database settings, notification settings, and so on. |
Integration Analytics (which consists of Stream Analytics and Integration Insight) is not supported.Integrations Design-Time Metadata Migration Scope You export Integrations design-time metadata into an archive file to then import into Oracle Integration on Oracle Cloud Infrastructure.The archive file consists of the following design- time metadata.Integrations, connections, lookups, agent groups, and so on.Note that: Integrations, connections, or objects in any state (in-progress, activated, and so on) are exported.All resources such as lookups and connections that are not currently referenced by integrations are exported.Endpoint configurations User-defined credentials.Note the following details: Credentials are exported into cwallet.sso.The oracle.cloud.adapter map and oracle.wsm.security maps are imported.User-defined certificates (not the seeded certificates).Only user-uploaded trusted certificates (whose alias begins with icsuser_||_ ) from the following keystores are exported: system/trust owsm/keystore ics/keystore All security policies.Existing policies are not overwritten.Connection passwords stored in the CSF store.Settings such as database settings, notification settings, and so on.Recommendations engine details and API Platform connection details. |
Integrations Design-Time Metadata Migration Scope You export Integrations design-time metadata into an archive file to then import into Oracle Integration on Oracle Cloud Infrastructure.The archive file consists of the following design- time metadata.Integrations, connections, lookups, agent groups, and so on.Note that: Integrations, connections, or objects in any state (in-progress, activated, and so on) are exported.All resources such as lookups and connections that are not currently referenced by integrations are exported.Endpoint configurations User-defined credentials.Note the following details: Credentials are exported into cwallet.sso.The oracle.cloud.adapter map and oracle.wsm.security maps are imported.User-defined certificates (not the seeded certificates).Only user-uploaded trusted certificates (whose alias begins with icsuser_||_ ) from the following keystores are exported: system/trust owsm/keystore ics/keystore All security policies.Existing policies are not overwritten.Connection passwords stored in the CSF store.Settings such as database settings, notification settings, and so on.Recommendations engine details and API Platform connection details.Integrations Migration Restrictions Understand the following restrictions when migrating Integrations to Oracle Integration on Oracle Cloud Infrastructure. |
The archive file consists of the following design- time metadata.Integrations, connections, lookups, agent groups, and so on.Note that: Integrations, connections, or objects in any state (in-progress, activated, and so on) are exported.All resources such as lookups and connections that are not currently referenced by integrations are exported.Endpoint configurations User-defined credentials.Note the following details: Credentials are exported into cwallet.sso.The oracle.cloud.adapter map and oracle.wsm.security maps are imported.User-defined certificates (not the seeded certificates).Only user-uploaded trusted certificates (whose alias begins with icsuser_||_ ) from the following keystores are exported: system/trust owsm/keystore ics/keystore All security policies.Existing policies are not overwritten.Connection passwords stored in the CSF store.Settings such as database settings, notification settings, and so on.Recommendations engine details and API Platform connection details.Integrations Migration Restrictions Understand the following restrictions when migrating Integrations to Oracle Integration on Oracle Cloud Infrastructure.Logging settings that you configured are not migrated. |
Integrations, connections, lookups, agent groups, and so on.Note that: Integrations, connections, or objects in any state (in-progress, activated, and so on) are exported.All resources such as lookups and connections that are not currently referenced by integrations are exported.Endpoint configurations User-defined credentials.Note the following details: Credentials are exported into cwallet.sso.The oracle.cloud.adapter map and oracle.wsm.security maps are imported.User-defined certificates (not the seeded certificates).Only user-uploaded trusted certificates (whose alias begins with icsuser_||_ ) from the following keystores are exported: system/trust owsm/keystore ics/keystore All security policies.Existing policies are not overwritten.Connection passwords stored in the CSF store.Settings such as database settings, notification settings, and so on.Recommendations engine details and API Platform connection details.Integrations Migration Restrictions Understand the following restrictions when migrating Integrations to Oracle Integration on Oracle Cloud Infrastructure.Logging settings that you configured are not migrated.A best effort is made to migrate database settings. |
Note that: Integrations, connections, or objects in any state (in-progress, activated, and so on) are exported.All resources such as lookups and connections that are not currently referenced by integrations are exported.Endpoint configurations User-defined credentials.Note the following details: Credentials are exported into cwallet.sso.The oracle.cloud.adapter map and oracle.wsm.security maps are imported.User-defined certificates (not the seeded certificates).Only user-uploaded trusted certificates (whose alias begins with icsuser_||_ ) from the following keystores are exported: system/trust owsm/keystore ics/keystore All security policies.Existing policies are not overwritten.Connection passwords stored in the CSF store.Settings such as database settings, notification settings, and so on.Recommendations engine details and API Platform connection details.Integrations Migration Restrictions Understand the following restrictions when migrating Integrations to Oracle Integration on Oracle Cloud Infrastructure.Logging settings that you configured are not migrated.A best effort is made to migrate database settings.After importing a scheduled integration (scheduled is started) from Oracle Integration Classic into Oracle Integration, the integration is imported and the schedule is started automatically. |
All resources such as lookups and connections that are not currently referenced by integrations are exported.Endpoint configurations User-defined credentials.Note the following details: Credentials are exported into cwallet.sso.The oracle.cloud.adapter map and oracle.wsm.security maps are imported.User-defined certificates (not the seeded certificates).Only user-uploaded trusted certificates (whose alias begins with icsuser_||_ ) from the following keystores are exported: system/trust owsm/keystore ics/keystore All security policies.Existing policies are not overwritten.Connection passwords stored in the CSF store.Settings such as database settings, notification settings, and so on.Recommendations engine details and API Platform connection details.Integrations Migration Restrictions Understand the following restrictions when migrating Integrations to Oracle Integration on Oracle Cloud Infrastructure.Logging settings that you configured are not migrated.A best effort is made to migrate database settings.After importing a scheduled integration (scheduled is started) from Oracle Integration Classic into Oracle Integration, the integration is imported and the schedule is started automatically.You must manually stop the schedule in Oracle Integration, if necessary. |
Endpoint configurations User-defined credentials.Note the following details: Credentials are exported into cwallet.sso.The oracle.cloud.adapter map and oracle.wsm.security maps are imported.User-defined certificates (not the seeded certificates).Only user-uploaded trusted certificates (whose alias begins with icsuser_||_ ) from the following keystores are exported: system/trust owsm/keystore ics/keystore All security policies.Existing policies are not overwritten.Connection passwords stored in the CSF store.Settings such as database settings, notification settings, and so on.Recommendations engine details and API Platform connection details.Integrations Migration Restrictions Understand the following restrictions when migrating Integrations to Oracle Integration on Oracle Cloud Infrastructure.Logging settings that you configured are not migrated.A best effort is made to migrate database settings.After importing a scheduled integration (scheduled is started) from Oracle Integration Classic into Oracle Integration, the integration is imported and the schedule is started automatically.You must manually stop the schedule in Oracle Integration, if necessary.If you modify the default value of the recovery job in Oracle Integration Classic, the upgrade to Oracle Integration resets the value to the default value.Chapter 1 About the Migration Scope 1-3Only one export at a time can be started. |
Note the following details: Credentials are exported into cwallet.sso.The oracle.cloud.adapter map and oracle.wsm.security maps are imported.User-defined certificates (not the seeded certificates).Only user-uploaded trusted certificates (whose alias begins with icsuser_||_ ) from the following keystores are exported: system/trust owsm/keystore ics/keystore All security policies.Existing policies are not overwritten.Connection passwords stored in the CSF store.Settings such as database settings, notification settings, and so on.Recommendations engine details and API Platform connection details.Integrations Migration Restrictions Understand the following restrictions when migrating Integrations to Oracle Integration on Oracle Cloud Infrastructure.Logging settings that you configured are not migrated.A best effort is made to migrate database settings.After importing a scheduled integration (scheduled is started) from Oracle Integration Classic into Oracle Integration, the integration is imported and the schedule is started automatically.You must manually stop the schedule in Oracle Integration, if necessary.If you modify the default value of the recovery job in Oracle Integration Classic, the upgrade to Oracle Integration resets the value to the default value.Chapter 1 About the Migration Scope 1-3Only one export at a time can be started.Subsequent export requests are rejected if one is currently running. |
The oracle.cloud.adapter map and oracle.wsm.security maps are imported.User-defined certificates (not the seeded certificates).Only user-uploaded trusted certificates (whose alias begins with icsuser_||_ ) from the following keystores are exported: system/trust owsm/keystore ics/keystore All security policies.Existing policies are not overwritten.Connection passwords stored in the CSF store.Settings such as database settings, notification settings, and so on.Recommendations engine details and API Platform connection details.Integrations Migration Restrictions Understand the following restrictions when migrating Integrations to Oracle Integration on Oracle Cloud Infrastructure.Logging settings that you configured are not migrated.A best effort is made to migrate database settings.After importing a scheduled integration (scheduled is started) from Oracle Integration Classic into Oracle Integration, the integration is imported and the schedule is started automatically.You must manually stop the schedule in Oracle Integration, if necessary.If you modify the default value of the recovery job in Oracle Integration Classic, the upgrade to Oracle Integration resets the value to the default value.Chapter 1 About the Migration Scope 1-3Only one export at a time can be started.Subsequent export requests are rejected if one is currently running.If an integration uses the on-premises connectivity agent, those integrations have to be manually activated after registering the agents manually. |
User-defined certificates (not the seeded certificates).Only user-uploaded trusted certificates (whose alias begins with icsuser_||_ ) from the following keystores are exported: system/trust owsm/keystore ics/keystore All security policies.Existing policies are not overwritten.Connection passwords stored in the CSF store.Settings such as database settings, notification settings, and so on.Recommendations engine details and API Platform connection details.Integrations Migration Restrictions Understand the following restrictions when migrating Integrations to Oracle Integration on Oracle Cloud Infrastructure.Logging settings that you configured are not migrated.A best effort is made to migrate database settings.After importing a scheduled integration (scheduled is started) from Oracle Integration Classic into Oracle Integration, the integration is imported and the schedule is started automatically.You must manually stop the schedule in Oracle Integration, if necessary.If you modify the default value of the recovery job in Oracle Integration Classic, the upgrade to Oracle Integration resets the value to the default value.Chapter 1 About the Migration Scope 1-3Only one export at a time can be started.Subsequent export requests are rejected if one is currently running.If an integration uses the on-premises connectivity agent, those integrations have to be manually activated after registering the agents manually.If a parent integration calls a child integration, the child integration must be manually activated. |
Only user-uploaded trusted certificates (whose alias begins with icsuser_||_ ) from the following keystores are exported: system/trust owsm/keystore ics/keystore All security policies.Existing policies are not overwritten.Connection passwords stored in the CSF store.Settings such as database settings, notification settings, and so on.Recommendations engine details and API Platform connection details.Integrations Migration Restrictions Understand the following restrictions when migrating Integrations to Oracle Integration on Oracle Cloud Infrastructure.Logging settings that you configured are not migrated.A best effort is made to migrate database settings.After importing a scheduled integration (scheduled is started) from Oracle Integration Classic into Oracle Integration, the integration is imported and the schedule is started automatically.You must manually stop the schedule in Oracle Integration, if necessary.If you modify the default value of the recovery job in Oracle Integration Classic, the upgrade to Oracle Integration resets the value to the default value.Chapter 1 About the Migration Scope 1-3Only one export at a time can be started.Subsequent export requests are rejected if one is currently running.If an integration uses the on-premises connectivity agent, those integrations have to be manually activated after registering the agents manually.If a parent integration calls a child integration, the child integration must be manually activated.This is because the child must be activated after the parent. |
Existing policies are not overwritten.Connection passwords stored in the CSF store.Settings such as database settings, notification settings, and so on.Recommendations engine details and API Platform connection details.Integrations Migration Restrictions Understand the following restrictions when migrating Integrations to Oracle Integration on Oracle Cloud Infrastructure.Logging settings that you configured are not migrated.A best effort is made to migrate database settings.After importing a scheduled integration (scheduled is started) from Oracle Integration Classic into Oracle Integration, the integration is imported and the schedule is started automatically.You must manually stop the schedule in Oracle Integration, if necessary.If you modify the default value of the recovery job in Oracle Integration Classic, the upgrade to Oracle Integration resets the value to the default value.Chapter 1 About the Migration Scope 1-3Only one export at a time can be started.Subsequent export requests are rejected if one is currently running.If an integration uses the on-premises connectivity agent, those integrations have to be manually activated after registering the agents manually.If a parent integration calls a child integration, the child integration must be manually activated.This is because the child must be activated after the parent.Data of the same name is overwritten. |
Connection passwords stored in the CSF store.Settings such as database settings, notification settings, and so on.Recommendations engine details and API Platform connection details.Integrations Migration Restrictions Understand the following restrictions when migrating Integrations to Oracle Integration on Oracle Cloud Infrastructure.Logging settings that you configured are not migrated.A best effort is made to migrate database settings.After importing a scheduled integration (scheduled is started) from Oracle Integration Classic into Oracle Integration, the integration is imported and the schedule is started automatically.You must manually stop the schedule in Oracle Integration, if necessary.If you modify the default value of the recovery job in Oracle Integration Classic, the upgrade to Oracle Integration resets the value to the default value.Chapter 1 About the Migration Scope 1-3Only one export at a time can be started.Subsequent export requests are rejected if one is currently running.If an integration uses the on-premises connectivity agent, those integrations have to be manually activated after registering the agents manually.If a parent integration calls a child integration, the child integration must be manually activated.This is because the child must be activated after the parent.Data of the same name is overwritten.For example, if an integration of the same name and version exists in Oracle Integration, it is overwritten by the integration of the same name and version imported from Oracle Integration Classic. |
Settings such as database settings, notification settings, and so on.Recommendations engine details and API Platform connection details.Integrations Migration Restrictions Understand the following restrictions when migrating Integrations to Oracle Integration on Oracle Cloud Infrastructure.Logging settings that you configured are not migrated.A best effort is made to migrate database settings.After importing a scheduled integration (scheduled is started) from Oracle Integration Classic into Oracle Integration, the integration is imported and the schedule is started automatically.You must manually stop the schedule in Oracle Integration, if necessary.If you modify the default value of the recovery job in Oracle Integration Classic, the upgrade to Oracle Integration resets the value to the default value.Chapter 1 About the Migration Scope 1-3Only one export at a time can be started.Subsequent export requests are rejected if one is currently running.If an integration uses the on-premises connectivity agent, those integrations have to be manually activated after registering the agents manually.If a parent integration calls a child integration, the child integration must be manually activated.This is because the child must be activated after the parent.Data of the same name is overwritten.For example, if an integration of the same name and version exists in Oracle Integration, it is overwritten by the integration of the same name and version imported from Oracle Integration Classic.Instance runtime data such as monitoring, tracking, and error details is not migrated. |
Recommendations engine details and API Platform connection details.Integrations Migration Restrictions Understand the following restrictions when migrating Integrations to Oracle Integration on Oracle Cloud Infrastructure.Logging settings that you configured are not migrated.A best effort is made to migrate database settings.After importing a scheduled integration (scheduled is started) from Oracle Integration Classic into Oracle Integration, the integration is imported and the schedule is started automatically.You must manually stop the schedule in Oracle Integration, if necessary.If you modify the default value of the recovery job in Oracle Integration Classic, the upgrade to Oracle Integration resets the value to the default value.Chapter 1 About the Migration Scope 1-3Only one export at a time can be started.Subsequent export requests are rejected if one is currently running.If an integration uses the on-premises connectivity agent, those integrations have to be manually activated after registering the agents manually.If a parent integration calls a child integration, the child integration must be manually activated.This is because the child must be activated after the parent.Data of the same name is overwritten.For example, if an integration of the same name and version exists in Oracle Integration, it is overwritten by the integration of the same name and version imported from Oracle Integration Classic.Instance runtime data such as monitoring, tracking, and error details is not migrated.Custom adapters and their integrations are not migrated. |
Integrations Migration Restrictions Understand the following restrictions when migrating Integrations to Oracle Integration on Oracle Cloud Infrastructure.Logging settings that you configured are not migrated.A best effort is made to migrate database settings.After importing a scheduled integration (scheduled is started) from Oracle Integration Classic into Oracle Integration, the integration is imported and the schedule is started automatically.You must manually stop the schedule in Oracle Integration, if necessary.If you modify the default value of the recovery job in Oracle Integration Classic, the upgrade to Oracle Integration resets the value to the default value.Chapter 1 About the Migration Scope 1-3Only one export at a time can be started.Subsequent export requests are rejected if one is currently running.If an integration uses the on-premises connectivity agent, those integrations have to be manually activated after registering the agents manually.If a parent integration calls a child integration, the child integration must be manually activated.This is because the child must be activated after the parent.Data of the same name is overwritten.For example, if an integration of the same name and version exists in Oracle Integration, it is overwritten by the integration of the same name and version imported from Oracle Integration Classic.Instance runtime data such as monitoring, tracking, and error details is not migrated.Custom adapters and their integrations are not migrated.File a service request to have your custom adapters and their integrations included in Oracle Integration. |
Logging settings that you configured are not migrated.A best effort is made to migrate database settings.After importing a scheduled integration (scheduled is started) from Oracle Integration Classic into Oracle Integration, the integration is imported and the schedule is started automatically.You must manually stop the schedule in Oracle Integration, if necessary.If you modify the default value of the recovery job in Oracle Integration Classic, the upgrade to Oracle Integration resets the value to the default value.Chapter 1 About the Migration Scope 1-3Only one export at a time can be started.Subsequent export requests are rejected if one is currently running.If an integration uses the on-premises connectivity agent, those integrations have to be manually activated after registering the agents manually.If a parent integration calls a child integration, the child integration must be manually activated.This is because the child must be activated after the parent.Data of the same name is overwritten.For example, if an integration of the same name and version exists in Oracle Integration, it is overwritten by the integration of the same name and version imported from Oracle Integration Classic.Instance runtime data such as monitoring, tracking, and error details is not migrated.Custom adapters and their integrations are not migrated.File a service request to have your custom adapters and their integrations included in Oracle Integration.Processes Design-Time Metadata Migration Scope Use the Process Import tool to import Processes design-time metadata into Oracle Integration on Oracle Cloud Infrastructure. |
A best effort is made to migrate database settings.After importing a scheduled integration (scheduled is started) from Oracle Integration Classic into Oracle Integration, the integration is imported and the schedule is started automatically.You must manually stop the schedule in Oracle Integration, if necessary.If you modify the default value of the recovery job in Oracle Integration Classic, the upgrade to Oracle Integration resets the value to the default value.Chapter 1 About the Migration Scope 1-3Only one export at a time can be started.Subsequent export requests are rejected if one is currently running.If an integration uses the on-premises connectivity agent, those integrations have to be manually activated after registering the agents manually.If a parent integration calls a child integration, the child integration must be manually activated.This is because the child must be activated after the parent.Data of the same name is overwritten.For example, if an integration of the same name and version exists in Oracle Integration, it is overwritten by the integration of the same name and version imported from Oracle Integration Classic.Instance runtime data such as monitoring, tracking, and error details is not migrated.Custom adapters and their integrations are not migrated.File a service request to have your custom adapters and their integrations included in Oracle Integration.Processes Design-Time Metadata Migration Scope Use the Process Import tool to import Processes design-time metadata into Oracle Integration on Oracle Cloud Infrastructure.You can import the following design-time metadata. |
After importing a scheduled integration (scheduled is started) from Oracle Integration Classic into Oracle Integration, the integration is imported and the schedule is started automatically.You must manually stop the schedule in Oracle Integration, if necessary.If you modify the default value of the recovery job in Oracle Integration Classic, the upgrade to Oracle Integration resets the value to the default value.Chapter 1 About the Migration Scope 1-3Only one export at a time can be started.Subsequent export requests are rejected if one is currently running.If an integration uses the on-premises connectivity agent, those integrations have to be manually activated after registering the agents manually.If a parent integration calls a child integration, the child integration must be manually activated.This is because the child must be activated after the parent.Data of the same name is overwritten.For example, if an integration of the same name and version exists in Oracle Integration, it is overwritten by the integration of the same name and version imported from Oracle Integration Classic.Instance runtime data such as monitoring, tracking, and error details is not migrated.Custom adapters and their integrations are not migrated.File a service request to have your custom adapters and their integrations included in Oracle Integration.Processes Design-Time Metadata Migration Scope Use the Process Import tool to import Processes design-time metadata into Oracle Integration on Oracle Cloud Infrastructure.You can import the following design-time metadata.Process applications Decision models Processes Migration Restrictions Understand the following restrictions when migrating to Oracle Integration on Oracle Cloud Infrastructure. |
You must manually stop the schedule in Oracle Integration, if necessary.If you modify the default value of the recovery job in Oracle Integration Classic, the upgrade to Oracle Integration resets the value to the default value.Chapter 1 About the Migration Scope 1-3Only one export at a time can be started.Subsequent export requests are rejected if one is currently running.If an integration uses the on-premises connectivity agent, those integrations have to be manually activated after registering the agents manually.If a parent integration calls a child integration, the child integration must be manually activated.This is because the child must be activated after the parent.Data of the same name is overwritten.For example, if an integration of the same name and version exists in Oracle Integration, it is overwritten by the integration of the same name and version imported from Oracle Integration Classic.Instance runtime data such as monitoring, tracking, and error details is not migrated.Custom adapters and their integrations are not migrated.File a service request to have your custom adapters and their integrations included in Oracle Integration.Processes Design-Time Metadata Migration Scope Use the Process Import tool to import Processes design-time metadata into Oracle Integration on Oracle Cloud Infrastructure.You can import the following design-time metadata.Process applications Decision models Processes Migration Restrictions Understand the following restrictions when migrating to Oracle Integration on Oracle Cloud Infrastructure.Application user role (swimlane) mapping: Process role mappings are not migrated. |
If you modify the default value of the recovery job in Oracle Integration Classic, the upgrade to Oracle Integration resets the value to the default value.Chapter 1 About the Migration Scope 1-3Only one export at a time can be started.Subsequent export requests are rejected if one is currently running.If an integration uses the on-premises connectivity agent, those integrations have to be manually activated after registering the agents manually.If a parent integration calls a child integration, the child integration must be manually activated.This is because the child must be activated after the parent.Data of the same name is overwritten.For example, if an integration of the same name and version exists in Oracle Integration, it is overwritten by the integration of the same name and version imported from Oracle Integration Classic.Instance runtime data such as monitoring, tracking, and error details is not migrated.Custom adapters and their integrations are not migrated.File a service request to have your custom adapters and their integrations included in Oracle Integration.Processes Design-Time Metadata Migration Scope Use the Process Import tool to import Processes design-time metadata into Oracle Integration on Oracle Cloud Infrastructure.You can import the following design-time metadata.Process applications Decision models Processes Migration Restrictions Understand the following restrictions when migrating to Oracle Integration on Oracle Cloud Infrastructure.Application user role (swimlane) mapping: Process role mappings are not migrated.You must remap Process user roles (swim lanes) for all process applications after activation. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.