text
stringlengths 65
20k
|
|---|
2.On the Visual Applications home page, open the visual application and open the Business Objects pane in the Navigator.3.Click the Options menu in the Business Objects pane and select Data Manager .4.Select the Live database in the dropdown list.5.Click Export All Data to download a ZIP archive that contains CSV files with the data.You will import the zip archive into the Live database of the published app on the new instance on Oracle Cloud Infrastructure.Import the Live Application Data into the New Application You can populate the database of your new visual app with the live data exported from your application on the Oracle Integration Classic instance.You can import the archive containing the Live data into the Development, Staging or Live database of your new application, and then include the data when you stage or publish the app.For example, if your app is staged but not yet published, you can import the Live data into the Staging database and then publish the app, making sure that you select Include data from Stage in the Publish Application dialog box.To import Live data into your application's database: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open your visual application and open the Business Objects pane in the Navigator.3.Click the Options menu in the Business Objects pane and select Data Manager .4.In the Database dropdown list, select the database that you want to import the Live data into.The options available in the Database dropdown list depend upon if you have staged or published your application.If your application has not been staged, you can only select Development in the dropdown list.5.Click Import from file .6.Drag the archive with the CSV files into the drop area in the Confirm Import Data dialog box. |
3.Click the Options menu in the Business Objects pane and select Data Manager .4.Select the Live database in the dropdown list.5.Click Export All Data to download a ZIP archive that contains CSV files with the data.You will import the zip archive into the Live database of the published app on the new instance on Oracle Cloud Infrastructure.Import the Live Application Data into the New Application You can populate the database of your new visual app with the live data exported from your application on the Oracle Integration Classic instance.You can import the archive containing the Live data into the Development, Staging or Live database of your new application, and then include the data when you stage or publish the app.For example, if your app is staged but not yet published, you can import the Live data into the Staging database and then publish the app, making sure that you select Include data from Stage in the Publish Application dialog box.To import Live data into your application's database: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open your visual application and open the Business Objects pane in the Navigator.3.Click the Options menu in the Business Objects pane and select Data Manager .4.In the Database dropdown list, select the database that you want to import the Live data into.The options available in the Database dropdown list depend upon if you have staged or published your application.If your application has not been staged, you can only select Development in the dropdown list.5.Click Import from file .6.Drag the archive with the CSV files into the drop area in the Confirm Import Data dialog box.Click Import . |
4.Select the Live database in the dropdown list.5.Click Export All Data to download a ZIP archive that contains CSV files with the data.You will import the zip archive into the Live database of the published app on the new instance on Oracle Cloud Infrastructure.Import the Live Application Data into the New Application You can populate the database of your new visual app with the live data exported from your application on the Oracle Integration Classic instance.You can import the archive containing the Live data into the Development, Staging or Live database of your new application, and then include the data when you stage or publish the app.For example, if your app is staged but not yet published, you can import the Live data into the Staging database and then publish the app, making sure that you select Include data from Stage in the Publish Application dialog box.To import Live data into your application's database: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open your visual application and open the Business Objects pane in the Navigator.3.Click the Options menu in the Business Objects pane and select Data Manager .4.In the Database dropdown list, select the database that you want to import the Live data into.The options available in the Database dropdown list depend upon if you have staged or published your application.If your application has not been staged, you can only select Development in the dropdown list.5.Click Import from file .6.Drag the archive with the CSV files into the drop area in the Confirm Import Data dialog box.Click Import .7.In the Import from File dialog box, confirm that the data was imported successfully. |
5.Click Export All Data to download a ZIP archive that contains CSV files with the data.You will import the zip archive into the Live database of the published app on the new instance on Oracle Cloud Infrastructure.Import the Live Application Data into the New Application You can populate the database of your new visual app with the live data exported from your application on the Oracle Integration Classic instance.You can import the archive containing the Live data into the Development, Staging or Live database of your new application, and then include the data when you stage or publish the app.For example, if your app is staged but not yet published, you can import the Live data into the Staging database and then publish the app, making sure that you select Include data from Stage in the Publish Application dialog box.To import Live data into your application's database: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open your visual application and open the Business Objects pane in the Navigator.3.Click the Options menu in the Business Objects pane and select Data Manager .4.In the Database dropdown list, select the database that you want to import the Live data into.The options available in the Database dropdown list depend upon if you have staged or published your application.If your application has not been staged, you can only select Development in the dropdown list.5.Click Import from file .6.Drag the archive with the CSV files into the drop area in the Confirm Import Data dialog box.Click Import .7.In the Import from File dialog box, confirm that the data was imported successfully.Click OK. You can confirm that the data was imported successfully in the Business Objects editor. |
You will import the zip archive into the Live database of the published app on the new instance on Oracle Cloud Infrastructure.Import the Live Application Data into the New Application You can populate the database of your new visual app with the live data exported from your application on the Oracle Integration Classic instance.You can import the archive containing the Live data into the Development, Staging or Live database of your new application, and then include the data when you stage or publish the app.For example, if your app is staged but not yet published, you can import the Live data into the Staging database and then publish the app, making sure that you select Include data from Stage in the Publish Application dialog box.To import Live data into your application's database: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open your visual application and open the Business Objects pane in the Navigator.3.Click the Options menu in the Business Objects pane and select Data Manager .4.In the Database dropdown list, select the database that you want to import the Live data into.The options available in the Database dropdown list depend upon if you have staged or published your application.If your application has not been staged, you can only select Development in the dropdown list.5.Click Import from file .6.Drag the archive with the CSV files into the drop area in the Confirm Import Data dialog box.Click Import .7.In the Import from File dialog box, confirm that the data was imported successfully.Click OK. You can confirm that the data was imported successfully in the Business Objects editor.Publish the New Application with the Live Application Data You can publish a staged version of your application from the Home page or from the main menu. |
Import the Live Application Data into the New Application You can populate the database of your new visual app with the live data exported from your application on the Oracle Integration Classic instance.You can import the archive containing the Live data into the Development, Staging or Live database of your new application, and then include the data when you stage or publish the app.For example, if your app is staged but not yet published, you can import the Live data into the Staging database and then publish the app, making sure that you select Include data from Stage in the Publish Application dialog box.To import Live data into your application's database: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open your visual application and open the Business Objects pane in the Navigator.3.Click the Options menu in the Business Objects pane and select Data Manager .4.In the Database dropdown list, select the database that you want to import the Live data into.The options available in the Database dropdown list depend upon if you have staged or published your application.If your application has not been staged, you can only select Development in the dropdown list.5.Click Import from file .6.Drag the archive with the CSV files into the drop area in the Confirm Import Data dialog box.Click Import .7.In the Import from File dialog box, confirm that the data was imported successfully.Click OK. You can confirm that the data was imported successfully in the Business Objects editor.Publish the New Application with the Live Application Data You can publish a staged version of your application from the Home page or from the main menu.After you publish a version of an app it is read-only and can no longer be changed. |
You can import the archive containing the Live data into the Development, Staging or Live database of your new application, and then include the data when you stage or publish the app.For example, if your app is staged but not yet published, you can import the Live data into the Staging database and then publish the app, making sure that you select Include data from Stage in the Publish Application dialog box.To import Live data into your application's database: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open your visual application and open the Business Objects pane in the Navigator.3.Click the Options menu in the Business Objects pane and select Data Manager .4.In the Database dropdown list, select the database that you want to import the Live data into.The options available in the Database dropdown list depend upon if you have staged or published your application.If your application has not been staged, you can only select Development in the dropdown list.5.Click Import from file .6.Drag the archive with the CSV files into the drop area in the Confirm Import Data dialog box.Click Import .7.In the Import from File dialog box, confirm that the data was imported successfully.Click OK. You can confirm that the data was imported successfully in the Business Objects editor.Publish the New Application with the Live Application Data You can publish a staged version of your application from the Home page or from the main menu.After you publish a version of an app it is read-only and can no longer be changed.To make changes to update the app you need to create a new version. |
For example, if your app is staged but not yet published, you can import the Live data into the Staging database and then publish the app, making sure that you select Include data from Stage in the Publish Application dialog box.To import Live data into your application's database: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open your visual application and open the Business Objects pane in the Navigator.3.Click the Options menu in the Business Objects pane and select Data Manager .4.In the Database dropdown list, select the database that you want to import the Live data into.The options available in the Database dropdown list depend upon if you have staged or published your application.If your application has not been staged, you can only select Development in the dropdown list.5.Click Import from file .6.Drag the archive with the CSV files into the drop area in the Confirm Import Data dialog box.Click Import .7.In the Import from File dialog box, confirm that the data was imported successfully.Click OK. You can confirm that the data was imported successfully in the Business Objects editor.Publish the New Application with the Live Application Data You can publish a staged version of your application from the Home page or from the main menu.After you publish a version of an app it is read-only and can no longer be changed.To make changes to update the app you need to create a new version.To publish the application: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open the Application Options menu for the application version you want to publish and select Publish .Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-53.For web applications, communicate the URL that end users must now use to access the web application(s) that you have published. |
To import Live data into your application's database: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open your visual application and open the Business Objects pane in the Navigator.3.Click the Options menu in the Business Objects pane and select Data Manager .4.In the Database dropdown list, select the database that you want to import the Live data into.The options available in the Database dropdown list depend upon if you have staged or published your application.If your application has not been staged, you can only select Development in the dropdown list.5.Click Import from file .6.Drag the archive with the CSV files into the drop area in the Confirm Import Data dialog box.Click Import .7.In the Import from File dialog box, confirm that the data was imported successfully.Click OK. You can confirm that the data was imported successfully in the Business Objects editor.Publish the New Application with the Live Application Data You can publish a staged version of your application from the Home page or from the main menu.After you publish a version of an app it is read-only and can no longer be changed.To make changes to update the app you need to create a new version.To publish the application: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open the Application Options menu for the application version you want to publish and select Publish .Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-53.For web applications, communicate the URL that end users must now use to access the web application(s) that you have published.4.For mobile applications, update the app store with an instance of the app that you have just published so end users can update their installation with the newer version of the app that has been built using Oracle Cloud Infrastructure.Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-6A Alternate Migration Options Instead of using the Application Migration Service to migrate design-time metadata, you can use alternate migration methods. |
3.Click the Options menu in the Business Objects pane and select Data Manager .4.In the Database dropdown list, select the database that you want to import the Live data into.The options available in the Database dropdown list depend upon if you have staged or published your application.If your application has not been staged, you can only select Development in the dropdown list.5.Click Import from file .6.Drag the archive with the CSV files into the drop area in the Confirm Import Data dialog box.Click Import .7.In the Import from File dialog box, confirm that the data was imported successfully.Click OK. You can confirm that the data was imported successfully in the Business Objects editor.Publish the New Application with the Live Application Data You can publish a staged version of your application from the Home page or from the main menu.After you publish a version of an app it is read-only and can no longer be changed.To make changes to update the app you need to create a new version.To publish the application: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open the Application Options menu for the application version you want to publish and select Publish .Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-53.For web applications, communicate the URL that end users must now use to access the web application(s) that you have published.4.For mobile applications, update the app store with an instance of the app that you have just published so end users can update their installation with the newer version of the app that has been built using Oracle Cloud Infrastructure.Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-6A Alternate Migration Options Instead of using the Application Migration Service to migrate design-time metadata, you can use alternate migration methods.Note: Oracle recommends that you use the Application Migration Service to migrate Integrations design-time metadata. |
4.In the Database dropdown list, select the database that you want to import the Live data into.The options available in the Database dropdown list depend upon if you have staged or published your application.If your application has not been staged, you can only select Development in the dropdown list.5.Click Import from file .6.Drag the archive with the CSV files into the drop area in the Confirm Import Data dialog box.Click Import .7.In the Import from File dialog box, confirm that the data was imported successfully.Click OK. You can confirm that the data was imported successfully in the Business Objects editor.Publish the New Application with the Live Application Data You can publish a staged version of your application from the Home page or from the main menu.After you publish a version of an app it is read-only and can no longer be changed.To make changes to update the app you need to create a new version.To publish the application: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open the Application Options menu for the application version you want to publish and select Publish .Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-53.For web applications, communicate the URL that end users must now use to access the web application(s) that you have published.4.For mobile applications, update the app store with an instance of the app that you have just published so end users can update their installation with the newer version of the app that has been built using Oracle Cloud Infrastructure.Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-6A Alternate Migration Options Instead of using the Application Migration Service to migrate design-time metadata, you can use alternate migration methods.Note: Oracle recommends that you use the Application Migration Service to migrate Integrations design-time metadata.See Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure . |
The options available in the Database dropdown list depend upon if you have staged or published your application.If your application has not been staged, you can only select Development in the dropdown list.5.Click Import from file .6.Drag the archive with the CSV files into the drop area in the Confirm Import Data dialog box.Click Import .7.In the Import from File dialog box, confirm that the data was imported successfully.Click OK. You can confirm that the data was imported successfully in the Business Objects editor.Publish the New Application with the Live Application Data You can publish a staged version of your application from the Home page or from the main menu.After you publish a version of an app it is read-only and can no longer be changed.To make changes to update the app you need to create a new version.To publish the application: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open the Application Options menu for the application version you want to publish and select Publish .Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-53.For web applications, communicate the URL that end users must now use to access the web application(s) that you have published.4.For mobile applications, update the app store with an instance of the app that you have just published so end users can update their installation with the newer version of the app that has been built using Oracle Cloud Infrastructure.Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-6A Alternate Migration Options Instead of using the Application Migration Service to migrate design-time metadata, you can use alternate migration methods.Note: Oracle recommends that you use the Application Migration Service to migrate Integrations design-time metadata.See Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure .If you choose not to use the Application Migration Service, the alternate migration options described in this appendix are available after you perform Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) . |
If your application has not been staged, you can only select Development in the dropdown list.5.Click Import from file .6.Drag the archive with the CSV files into the drop area in the Confirm Import Data dialog box.Click Import .7.In the Import from File dialog box, confirm that the data was imported successfully.Click OK. You can confirm that the data was imported successfully in the Business Objects editor.Publish the New Application with the Live Application Data You can publish a staged version of your application from the Home page or from the main menu.After you publish a version of an app it is read-only and can no longer be changed.To make changes to update the app you need to create a new version.To publish the application: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open the Application Options menu for the application version you want to publish and select Publish .Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-53.For web applications, communicate the URL that end users must now use to access the web application(s) that you have published.4.For mobile applications, update the app store with an instance of the app that you have just published so end users can update their installation with the newer version of the app that has been built using Oracle Cloud Infrastructure.Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-6A Alternate Migration Options Instead of using the Application Migration Service to migrate design-time metadata, you can use alternate migration methods.Note: Oracle recommends that you use the Application Migration Service to migrate Integrations design-time metadata.See Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure .If you choose not to use the Application Migration Service, the alternate migration options described in this appendix are available after you perform Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Topics: Migrate Processes Design-Time Metadata into Oracle Integration Migrate Integration and Process Design-Time Metadata into Oracle Integration Migrate Processes Design-Time Metadata into Oracle Integration As an administrator, you can import your Processes design-time metadata (process applications and decision models) into Oracle Integration. |
5.Click Import from file .6.Drag the archive with the CSV files into the drop area in the Confirm Import Data dialog box.Click Import .7.In the Import from File dialog box, confirm that the data was imported successfully.Click OK. You can confirm that the data was imported successfully in the Business Objects editor.Publish the New Application with the Live Application Data You can publish a staged version of your application from the Home page or from the main menu.After you publish a version of an app it is read-only and can no longer be changed.To make changes to update the app you need to create a new version.To publish the application: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open the Application Options menu for the application version you want to publish and select Publish .Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-53.For web applications, communicate the URL that end users must now use to access the web application(s) that you have published.4.For mobile applications, update the app store with an instance of the app that you have just published so end users can update their installation with the newer version of the app that has been built using Oracle Cloud Infrastructure.Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-6A Alternate Migration Options Instead of using the Application Migration Service to migrate design-time metadata, you can use alternate migration methods.Note: Oracle recommends that you use the Application Migration Service to migrate Integrations design-time metadata.See Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure .If you choose not to use the Application Migration Service, the alternate migration options described in this appendix are available after you perform Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Topics: Migrate Processes Design-Time Metadata into Oracle Integration Migrate Integration and Process Design-Time Metadata into Oracle Integration Migrate Processes Design-Time Metadata into Oracle Integration As an administrator, you can import your Processes design-time metadata (process applications and decision models) into Oracle Integration.The import tool provides migration flexibility: choose to migrate the entire instance, a selected space, or individual items. |
6.Drag the archive with the CSV files into the drop area in the Confirm Import Data dialog box.Click Import .7.In the Import from File dialog box, confirm that the data was imported successfully.Click OK. You can confirm that the data was imported successfully in the Business Objects editor.Publish the New Application with the Live Application Data You can publish a staged version of your application from the Home page or from the main menu.After you publish a version of an app it is read-only and can no longer be changed.To make changes to update the app you need to create a new version.To publish the application: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open the Application Options menu for the application version you want to publish and select Publish .Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-53.For web applications, communicate the URL that end users must now use to access the web application(s) that you have published.4.For mobile applications, update the app store with an instance of the app that you have just published so end users can update their installation with the newer version of the app that has been built using Oracle Cloud Infrastructure.Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-6A Alternate Migration Options Instead of using the Application Migration Service to migrate design-time metadata, you can use alternate migration methods.Note: Oracle recommends that you use the Application Migration Service to migrate Integrations design-time metadata.See Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure .If you choose not to use the Application Migration Service, the alternate migration options described in this appendix are available after you perform Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Topics: Migrate Processes Design-Time Metadata into Oracle Integration Migrate Integration and Process Design-Time Metadata into Oracle Integration Migrate Processes Design-Time Metadata into Oracle Integration As an administrator, you can import your Processes design-time metadata (process applications and decision models) into Oracle Integration.The import tool provides migration flexibility: choose to migrate the entire instance, a selected space, or individual items.Import Processes Design-Time Metadata into Oracle Integration Import Using the Import Command Line Utility Import Processes Design-Time Metadata into Oracle Integration Use the Process import tool to automatically move Process and decision design-time metadata from one instance to another. |
Click Import .7.In the Import from File dialog box, confirm that the data was imported successfully.Click OK. You can confirm that the data was imported successfully in the Business Objects editor.Publish the New Application with the Live Application Data You can publish a staged version of your application from the Home page or from the main menu.After you publish a version of an app it is read-only and can no longer be changed.To make changes to update the app you need to create a new version.To publish the application: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open the Application Options menu for the application version you want to publish and select Publish .Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-53.For web applications, communicate the URL that end users must now use to access the web application(s) that you have published.4.For mobile applications, update the app store with an instance of the app that you have just published so end users can update their installation with the newer version of the app that has been built using Oracle Cloud Infrastructure.Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-6A Alternate Migration Options Instead of using the Application Migration Service to migrate design-time metadata, you can use alternate migration methods.Note: Oracle recommends that you use the Application Migration Service to migrate Integrations design-time metadata.See Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure .If you choose not to use the Application Migration Service, the alternate migration options described in this appendix are available after you perform Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Topics: Migrate Processes Design-Time Metadata into Oracle Integration Migrate Integration and Process Design-Time Metadata into Oracle Integration Migrate Processes Design-Time Metadata into Oracle Integration As an administrator, you can import your Processes design-time metadata (process applications and decision models) into Oracle Integration.The import tool provides migration flexibility: choose to migrate the entire instance, a selected space, or individual items.Import Processes Design-Time Metadata into Oracle Integration Import Using the Import Command Line Utility Import Processes Design-Time Metadata into Oracle Integration Use the Process import tool to automatically move Process and decision design-time metadata from one instance to another.The tool moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models. |
7.In the Import from File dialog box, confirm that the data was imported successfully.Click OK. You can confirm that the data was imported successfully in the Business Objects editor.Publish the New Application with the Live Application Data You can publish a staged version of your application from the Home page or from the main menu.After you publish a version of an app it is read-only and can no longer be changed.To make changes to update the app you need to create a new version.To publish the application: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open the Application Options menu for the application version you want to publish and select Publish .Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-53.For web applications, communicate the URL that end users must now use to access the web application(s) that you have published.4.For mobile applications, update the app store with an instance of the app that you have just published so end users can update their installation with the newer version of the app that has been built using Oracle Cloud Infrastructure.Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-6A Alternate Migration Options Instead of using the Application Migration Service to migrate design-time metadata, you can use alternate migration methods.Note: Oracle recommends that you use the Application Migration Service to migrate Integrations design-time metadata.See Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure .If you choose not to use the Application Migration Service, the alternate migration options described in this appendix are available after you perform Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Topics: Migrate Processes Design-Time Metadata into Oracle Integration Migrate Integration and Process Design-Time Metadata into Oracle Integration Migrate Processes Design-Time Metadata into Oracle Integration As an administrator, you can import your Processes design-time metadata (process applications and decision models) into Oracle Integration.The import tool provides migration flexibility: choose to migrate the entire instance, a selected space, or individual items.Import Processes Design-Time Metadata into Oracle Integration Import Using the Import Command Line Utility Import Processes Design-Time Metadata into Oracle Integration Use the Process import tool to automatically move Process and decision design-time metadata from one instance to another.The tool moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Alternatively, you can import process applications and decision models from the command line instead of the user interface. |
Click OK. You can confirm that the data was imported successfully in the Business Objects editor.Publish the New Application with the Live Application Data You can publish a staged version of your application from the Home page or from the main menu.After you publish a version of an app it is read-only and can no longer be changed.To make changes to update the app you need to create a new version.To publish the application: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open the Application Options menu for the application version you want to publish and select Publish .Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-53.For web applications, communicate the URL that end users must now use to access the web application(s) that you have published.4.For mobile applications, update the app store with an instance of the app that you have just published so end users can update their installation with the newer version of the app that has been built using Oracle Cloud Infrastructure.Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-6A Alternate Migration Options Instead of using the Application Migration Service to migrate design-time metadata, you can use alternate migration methods.Note: Oracle recommends that you use the Application Migration Service to migrate Integrations design-time metadata.See Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure .If you choose not to use the Application Migration Service, the alternate migration options described in this appendix are available after you perform Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Topics: Migrate Processes Design-Time Metadata into Oracle Integration Migrate Integration and Process Design-Time Metadata into Oracle Integration Migrate Processes Design-Time Metadata into Oracle Integration As an administrator, you can import your Processes design-time metadata (process applications and decision models) into Oracle Integration.The import tool provides migration flexibility: choose to migrate the entire instance, a selected space, or individual items.Import Processes Design-Time Metadata into Oracle Integration Import Using the Import Command Line Utility Import Processes Design-Time Metadata into Oracle Integration Use the Process import tool to automatically move Process and decision design-time metadata from one instance to another.The tool moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Alternatively, you can import process applications and decision models from the command line instead of the user interface.See Import Using the Import Command Line Utility . |
Publish the New Application with the Live Application Data You can publish a staged version of your application from the Home page or from the main menu.After you publish a version of an app it is read-only and can no longer be changed.To make changes to update the app you need to create a new version.To publish the application: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open the Application Options menu for the application version you want to publish and select Publish .Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-53.For web applications, communicate the URL that end users must now use to access the web application(s) that you have published.4.For mobile applications, update the app store with an instance of the app that you have just published so end users can update their installation with the newer version of the app that has been built using Oracle Cloud Infrastructure.Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-6A Alternate Migration Options Instead of using the Application Migration Service to migrate design-time metadata, you can use alternate migration methods.Note: Oracle recommends that you use the Application Migration Service to migrate Integrations design-time metadata.See Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure .If you choose not to use the Application Migration Service, the alternate migration options described in this appendix are available after you perform Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Topics: Migrate Processes Design-Time Metadata into Oracle Integration Migrate Integration and Process Design-Time Metadata into Oracle Integration Migrate Processes Design-Time Metadata into Oracle Integration As an administrator, you can import your Processes design-time metadata (process applications and decision models) into Oracle Integration.The import tool provides migration flexibility: choose to migrate the entire instance, a selected space, or individual items.Import Processes Design-Time Metadata into Oracle Integration Import Using the Import Command Line Utility Import Processes Design-Time Metadata into Oracle Integration Use the Process import tool to automatically move Process and decision design-time metadata from one instance to another.The tool moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Alternatively, you can import process applications and decision models from the command line instead of the user interface.See Import Using the Import Command Line Utility .Note that using the import tool is highly recommended. |
After you publish a version of an app it is read-only and can no longer be changed.To make changes to update the app you need to create a new version.To publish the application: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open the Application Options menu for the application version you want to publish and select Publish .Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-53.For web applications, communicate the URL that end users must now use to access the web application(s) that you have published.4.For mobile applications, update the app store with an instance of the app that you have just published so end users can update their installation with the newer version of the app that has been built using Oracle Cloud Infrastructure.Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-6A Alternate Migration Options Instead of using the Application Migration Service to migrate design-time metadata, you can use alternate migration methods.Note: Oracle recommends that you use the Application Migration Service to migrate Integrations design-time metadata.See Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure .If you choose not to use the Application Migration Service, the alternate migration options described in this appendix are available after you perform Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Topics: Migrate Processes Design-Time Metadata into Oracle Integration Migrate Integration and Process Design-Time Metadata into Oracle Integration Migrate Processes Design-Time Metadata into Oracle Integration As an administrator, you can import your Processes design-time metadata (process applications and decision models) into Oracle Integration.The import tool provides migration flexibility: choose to migrate the entire instance, a selected space, or individual items.Import Processes Design-Time Metadata into Oracle Integration Import Using the Import Command Line Utility Import Processes Design-Time Metadata into Oracle Integration Use the Process import tool to automatically move Process and decision design-time metadata from one instance to another.The tool moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Alternatively, you can import process applications and decision models from the command line instead of the user interface.See Import Using the Import Command Line Utility .Note that using the import tool is highly recommended.A-1Important: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model. |
To make changes to update the app you need to create a new version.To publish the application: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open the Application Options menu for the application version you want to publish and select Publish .Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-53.For web applications, communicate the URL that end users must now use to access the web application(s) that you have published.4.For mobile applications, update the app store with an instance of the app that you have just published so end users can update their installation with the newer version of the app that has been built using Oracle Cloud Infrastructure.Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-6A Alternate Migration Options Instead of using the Application Migration Service to migrate design-time metadata, you can use alternate migration methods.Note: Oracle recommends that you use the Application Migration Service to migrate Integrations design-time metadata.See Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure .If you choose not to use the Application Migration Service, the alternate migration options described in this appendix are available after you perform Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Topics: Migrate Processes Design-Time Metadata into Oracle Integration Migrate Integration and Process Design-Time Metadata into Oracle Integration Migrate Processes Design-Time Metadata into Oracle Integration As an administrator, you can import your Processes design-time metadata (process applications and decision models) into Oracle Integration.The import tool provides migration flexibility: choose to migrate the entire instance, a selected space, or individual items.Import Processes Design-Time Metadata into Oracle Integration Import Using the Import Command Line Utility Import Processes Design-Time Metadata into Oracle Integration Use the Process import tool to automatically move Process and decision design-time metadata from one instance to another.The tool moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Alternatively, you can import process applications and decision models from the command line instead of the user interface.See Import Using the Import Command Line Utility .Note that using the import tool is highly recommended.A-1Important: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results. |
To publish the application: 1.Open the new Oracle Visual Builder instance on Oracle Cloud Infrastructure 2.On the Visual Applications home page, open the Application Options menu for the application version you want to publish and select Publish .Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-53.For web applications, communicate the URL that end users must now use to access the web application(s) that you have published.4.For mobile applications, update the app store with an instance of the app that you have just published so end users can update their installation with the newer version of the app that has been built using Oracle Cloud Infrastructure.Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-6A Alternate Migration Options Instead of using the Application Migration Service to migrate design-time metadata, you can use alternate migration methods.Note: Oracle recommends that you use the Application Migration Service to migrate Integrations design-time metadata.See Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure .If you choose not to use the Application Migration Service, the alternate migration options described in this appendix are available after you perform Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Topics: Migrate Processes Design-Time Metadata into Oracle Integration Migrate Integration and Process Design-Time Metadata into Oracle Integration Migrate Processes Design-Time Metadata into Oracle Integration As an administrator, you can import your Processes design-time metadata (process applications and decision models) into Oracle Integration.The import tool provides migration flexibility: choose to migrate the entire instance, a selected space, or individual items.Import Processes Design-Time Metadata into Oracle Integration Import Using the Import Command Line Utility Import Processes Design-Time Metadata into Oracle Integration Use the Process import tool to automatically move Process and decision design-time metadata from one instance to another.The tool moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Alternatively, you can import process applications and decision models from the command line instead of the user interface.See Import Using the Import Command Line Utility .Note that using the import tool is highly recommended.A-1Important: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Avoid refreshing or closing the tool during the import. |
4.For mobile applications, update the app store with an instance of the app that you have just published so end users can update their installation with the newer version of the app that has been built using Oracle Cloud Infrastructure.Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-6A Alternate Migration Options Instead of using the Application Migration Service to migrate design-time metadata, you can use alternate migration methods.Note: Oracle recommends that you use the Application Migration Service to migrate Integrations design-time metadata.See Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure .If you choose not to use the Application Migration Service, the alternate migration options described in this appendix are available after you perform Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Topics: Migrate Processes Design-Time Metadata into Oracle Integration Migrate Integration and Process Design-Time Metadata into Oracle Integration Migrate Processes Design-Time Metadata into Oracle Integration As an administrator, you can import your Processes design-time metadata (process applications and decision models) into Oracle Integration.The import tool provides migration flexibility: choose to migrate the entire instance, a selected space, or individual items.Import Processes Design-Time Metadata into Oracle Integration Import Using the Import Command Line Utility Import Processes Design-Time Metadata into Oracle Integration Use the Process import tool to automatically move Process and decision design-time metadata from one instance to another.The tool moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Alternatively, you can import process applications and decision models from the command line instead of the user interface.See Import Using the Import Command Line Utility .Note that using the import tool is highly recommended.A-1Important: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Avoid refreshing or closing the tool during the import.1.On the Oracle Integration Home page, click Processes in the navigation pane. |
Note: Oracle recommends that you use the Application Migration Service to migrate Integrations design-time metadata.See Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure .If you choose not to use the Application Migration Service, the alternate migration options described in this appendix are available after you perform Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Topics: Migrate Processes Design-Time Metadata into Oracle Integration Migrate Integration and Process Design-Time Metadata into Oracle Integration Migrate Processes Design-Time Metadata into Oracle Integration As an administrator, you can import your Processes design-time metadata (process applications and decision models) into Oracle Integration.The import tool provides migration flexibility: choose to migrate the entire instance, a selected space, or individual items.Import Processes Design-Time Metadata into Oracle Integration Import Using the Import Command Line Utility Import Processes Design-Time Metadata into Oracle Integration Use the Process import tool to automatically move Process and decision design-time metadata from one instance to another.The tool moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Alternatively, you can import process applications and decision models from the command line instead of the user interface.See Import Using the Import Command Line Utility .Note that using the import tool is highly recommended.A-1Important: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Avoid refreshing or closing the tool during the import.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import from the top options on the Administration page. |
See Workflow to Migrate Your Oracle Integration Classic Instance to Oracle Cloud Infrastructure .If you choose not to use the Application Migration Service, the alternate migration options described in this appendix are available after you perform Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Topics: Migrate Processes Design-Time Metadata into Oracle Integration Migrate Integration and Process Design-Time Metadata into Oracle Integration Migrate Processes Design-Time Metadata into Oracle Integration As an administrator, you can import your Processes design-time metadata (process applications and decision models) into Oracle Integration.The import tool provides migration flexibility: choose to migrate the entire instance, a selected space, or individual items.Import Processes Design-Time Metadata into Oracle Integration Import Using the Import Command Line Utility Import Processes Design-Time Metadata into Oracle Integration Use the Process import tool to automatically move Process and decision design-time metadata from one instance to another.The tool moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Alternatively, you can import process applications and decision models from the command line instead of the user interface.See Import Using the Import Command Line Utility .Note that using the import tool is highly recommended.A-1Important: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Avoid refreshing or closing the tool during the import.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import from the top options on the Administration page.3.On the Import Administration page, specify a source for the import. |
If you choose not to use the Application Migration Service, the alternate migration options described in this appendix are available after you perform Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Topics: Migrate Processes Design-Time Metadata into Oracle Integration Migrate Integration and Process Design-Time Metadata into Oracle Integration Migrate Processes Design-Time Metadata into Oracle Integration As an administrator, you can import your Processes design-time metadata (process applications and decision models) into Oracle Integration.The import tool provides migration flexibility: choose to migrate the entire instance, a selected space, or individual items.Import Processes Design-Time Metadata into Oracle Integration Import Using the Import Command Line Utility Import Processes Design-Time Metadata into Oracle Integration Use the Process import tool to automatically move Process and decision design-time metadata from one instance to another.The tool moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Alternatively, you can import process applications and decision models from the command line instead of the user interface.See Import Using the Import Command Line Utility .Note that using the import tool is highly recommended.A-1Important: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Avoid refreshing or closing the tool during the import.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import from the top options on the Administration page.3.On the Import Administration page, specify a source for the import.a.In the Identify the instance to import from fields, choose an Oracle Integration instance. |
Topics: Migrate Processes Design-Time Metadata into Oracle Integration Migrate Integration and Process Design-Time Metadata into Oracle Integration Migrate Processes Design-Time Metadata into Oracle Integration As an administrator, you can import your Processes design-time metadata (process applications and decision models) into Oracle Integration.The import tool provides migration flexibility: choose to migrate the entire instance, a selected space, or individual items.Import Processes Design-Time Metadata into Oracle Integration Import Using the Import Command Line Utility Import Processes Design-Time Metadata into Oracle Integration Use the Process import tool to automatically move Process and decision design-time metadata from one instance to another.The tool moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Alternatively, you can import process applications and decision models from the command line instead of the user interface.See Import Using the Import Command Line Utility .Note that using the import tool is highly recommended.A-1Important: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Avoid refreshing or closing the tool during the import.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import from the top options on the Administration page.3.On the Import Administration page, specify a source for the import.a.In the Identify the instance to import from fields, choose an Oracle Integration instance.b.In the Host Name field, enter the host, using the format https://host:port . |
The import tool provides migration flexibility: choose to migrate the entire instance, a selected space, or individual items.Import Processes Design-Time Metadata into Oracle Integration Import Using the Import Command Line Utility Import Processes Design-Time Metadata into Oracle Integration Use the Process import tool to automatically move Process and decision design-time metadata from one instance to another.The tool moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Alternatively, you can import process applications and decision models from the command line instead of the user interface.See Import Using the Import Command Line Utility .Note that using the import tool is highly recommended.A-1Important: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Avoid refreshing or closing the tool during the import.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import from the top options on the Administration page.3.On the Import Administration page, specify a source for the import.a.In the Identify the instance to import from fields, choose an Oracle Integration instance.b.In the Host Name field, enter the host, using the format https://host:port .c.Enter a user name and password to sign in to the instance as an administrator. |
Import Processes Design-Time Metadata into Oracle Integration Import Using the Import Command Line Utility Import Processes Design-Time Metadata into Oracle Integration Use the Process import tool to automatically move Process and decision design-time metadata from one instance to another.The tool moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Alternatively, you can import process applications and decision models from the command line instead of the user interface.See Import Using the Import Command Line Utility .Note that using the import tool is highly recommended.A-1Important: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Avoid refreshing or closing the tool during the import.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import from the top options on the Administration page.3.On the Import Administration page, specify a source for the import.a.In the Identify the instance to import from fields, choose an Oracle Integration instance.b.In the Host Name field, enter the host, using the format https://host:port .c.Enter a user name and password to sign in to the instance as an administrator.4.Identify a destination for the import. |
The tool moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Alternatively, you can import process applications and decision models from the command line instead of the user interface.See Import Using the Import Command Line Utility .Note that using the import tool is highly recommended.A-1Important: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Avoid refreshing or closing the tool during the import.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import from the top options on the Administration page.3.On the Import Administration page, specify a source for the import.a.In the Identify the instance to import from fields, choose an Oracle Integration instance.b.In the Host Name field, enter the host, using the format https://host:port .c.Enter a user name and password to sign in to the instance as an administrator.4.Identify a destination for the import.To import to your current instance, skip the Import to the current Oracle Integration instance field. |
Alternatively, you can import process applications and decision models from the command line instead of the user interface.See Import Using the Import Command Line Utility .Note that using the import tool is highly recommended.A-1Important: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Avoid refreshing or closing the tool during the import.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import from the top options on the Administration page.3.On the Import Administration page, specify a source for the import.a.In the Identify the instance to import from fields, choose an Oracle Integration instance.b.In the Host Name field, enter the host, using the format https://host:port .c.Enter a user name and password to sign in to the instance as an administrator.4.Identify a destination for the import.To import to your current instance, skip the Import to the current Oracle Integration instance field.To import to another Oracle Integration instance than your current instance, click Edit and complete the host, user name, and password fields for the instance you want to import to. |
See Import Using the Import Command Line Utility .Note that using the import tool is highly recommended.A-1Important: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Avoid refreshing or closing the tool during the import.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import from the top options on the Administration page.3.On the Import Administration page, specify a source for the import.a.In the Identify the instance to import from fields, choose an Oracle Integration instance.b.In the Host Name field, enter the host, using the format https://host:port .c.Enter a user name and password to sign in to the instance as an administrator.4.Identify a destination for the import.To import to your current instance, skip the Import to the current Oracle Integration instance field.To import to another Oracle Integration instance than your current instance, click Edit and complete the host, user name, and password fields for the instance you want to import to.To select importing to the current instance, click Reset . |
Note that using the import tool is highly recommended.A-1Important: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Avoid refreshing or closing the tool during the import.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import from the top options on the Administration page.3.On the Import Administration page, specify a source for the import.a.In the Identify the instance to import from fields, choose an Oracle Integration instance.b.In the Host Name field, enter the host, using the format https://host:port .c.Enter a user name and password to sign in to the instance as an administrator.4.Identify a destination for the import.To import to your current instance, skip the Import to the current Oracle Integration instance field.To import to another Oracle Integration instance than your current instance, click Edit and complete the host, user name, and password fields for the instance you want to import to.To select importing to the current instance, click Reset .5.In the Scope field, identify what you want to import. |
A-1Important: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Avoid refreshing or closing the tool during the import.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import from the top options on the Administration page.3.On the Import Administration page, specify a source for the import.a.In the Identify the instance to import from fields, choose an Oracle Integration instance.b.In the Host Name field, enter the host, using the format https://host:port .c.Enter a user name and password to sign in to the instance as an administrator.4.Identify a destination for the import.To import to your current instance, skip the Import to the current Oracle Integration instance field.To import to another Oracle Integration instance than your current instance, click Edit and complete the host, user name, and password fields for the instance you want to import to.To select importing to the current instance, click Reset .5.In the Scope field, identify what you want to import.Choose Entire Instance to import all process applications and decision models from all spaces located on the instance. |
Be sure not to import assets more than once, because doing so can lead to unpredictable results.Avoid refreshing or closing the tool during the import.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import from the top options on the Administration page.3.On the Import Administration page, specify a source for the import.a.In the Identify the instance to import from fields, choose an Oracle Integration instance.b.In the Host Name field, enter the host, using the format https://host:port .c.Enter a user name and password to sign in to the instance as an administrator.4.Identify a destination for the import.To import to your current instance, skip the Import to the current Oracle Integration instance field.To import to another Oracle Integration instance than your current instance, click Edit and complete the host, user name, and password fields for the instance you want to import to.To select importing to the current instance, click Reset .5.In the Scope field, identify what you want to import.Choose Entire Instance to import all process applications and decision models from all spaces located on the instance.Choose Space to import a selected source only. |
Avoid refreshing or closing the tool during the import.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import from the top options on the Administration page.3.On the Import Administration page, specify a source for the import.a.In the Identify the instance to import from fields, choose an Oracle Integration instance.b.In the Host Name field, enter the host, using the format https://host:port .c.Enter a user name and password to sign in to the instance as an administrator.4.Identify a destination for the import.To import to your current instance, skip the Import to the current Oracle Integration instance field.To import to another Oracle Integration instance than your current instance, click Edit and complete the host, user name, and password fields for the instance you want to import to.To select importing to the current instance, click Reset .5.In the Scope field, identify what you want to import.Choose Entire Instance to import all process applications and decision models from all spaces located on the instance.Choose Space to import a selected source only.Select the space in the Source Space field that displays. |
1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import from the top options on the Administration page.3.On the Import Administration page, specify a source for the import.a.In the Identify the instance to import from fields, choose an Oracle Integration instance.b.In the Host Name field, enter the host, using the format https://host:port .c.Enter a user name and password to sign in to the instance as an administrator.4.Identify a destination for the import.To import to your current instance, skip the Import to the current Oracle Integration instance field.To import to another Oracle Integration instance than your current instance, click Edit and complete the host, user name, and password fields for the instance you want to import to.To select importing to the current instance, click Reset .5.In the Scope field, identify what you want to import.Choose Entire Instance to import all process applications and decision models from all spaces located on the instance.Choose Space to import a selected source only.Select the space in the Source Space field that displays.Choose Process Application or Decision Model to import a selected application or decision model only. |
2.Click Settings in the navigation pane, then Import from the top options on the Administration page.3.On the Import Administration page, specify a source for the import.a.In the Identify the instance to import from fields, choose an Oracle Integration instance.b.In the Host Name field, enter the host, using the format https://host:port .c.Enter a user name and password to sign in to the instance as an administrator.4.Identify a destination for the import.To import to your current instance, skip the Import to the current Oracle Integration instance field.To import to another Oracle Integration instance than your current instance, click Edit and complete the host, user name, and password fields for the instance you want to import to.To select importing to the current instance, click Reset .5.In the Scope field, identify what you want to import.Choose Entire Instance to import all process applications and decision models from all spaces located on the instance.Choose Space to import a selected source only.Select the space in the Source Space field that displays.Choose Process Application or Decision Model to import a selected application or decision model only.In the additional fields that display, select the source space, process application or decision model to import, and the destination space. |
3.On the Import Administration page, specify a source for the import.a.In the Identify the instance to import from fields, choose an Oracle Integration instance.b.In the Host Name field, enter the host, using the format https://host:port .c.Enter a user name and password to sign in to the instance as an administrator.4.Identify a destination for the import.To import to your current instance, skip the Import to the current Oracle Integration instance field.To import to another Oracle Integration instance than your current instance, click Edit and complete the host, user name, and password fields for the instance you want to import to.To select importing to the current instance, click Reset .5.In the Scope field, identify what you want to import.Choose Entire Instance to import all process applications and decision models from all spaces located on the instance.Choose Space to import a selected source only.Select the space in the Source Space field that displays.Choose Process Application or Decision Model to import a selected application or decision model only.In the additional fields that display, select the source space, process application or decision model to import, and the destination space.6.Click Import . |
a.In the Identify the instance to import from fields, choose an Oracle Integration instance.b.In the Host Name field, enter the host, using the format https://host:port .c.Enter a user name and password to sign in to the instance as an administrator.4.Identify a destination for the import.To import to your current instance, skip the Import to the current Oracle Integration instance field.To import to another Oracle Integration instance than your current instance, click Edit and complete the host, user name, and password fields for the instance you want to import to.To select importing to the current instance, click Reset .5.In the Scope field, identify what you want to import.Choose Entire Instance to import all process applications and decision models from all spaces located on the instance.Choose Space to import a selected source only.Select the space in the Source Space field that displays.Choose Process Application or Decision Model to import a selected application or decision model only.In the additional fields that display, select the source space, process application or decision model to import, and the destination space.6.Click Import .7.Review the import log. |
b.In the Host Name field, enter the host, using the format https://host:port .c.Enter a user name and password to sign in to the instance as an administrator.4.Identify a destination for the import.To import to your current instance, skip the Import to the current Oracle Integration instance field.To import to another Oracle Integration instance than your current instance, click Edit and complete the host, user name, and password fields for the instance you want to import to.To select importing to the current instance, click Reset .5.In the Scope field, identify what you want to import.Choose Entire Instance to import all process applications and decision models from all spaces located on the instance.Choose Space to import a selected source only.Select the space in the Source Space field that displays.Choose Process Application or Decision Model to import a selected application or decision model only.In the additional fields that display, select the source space, process application or decision model to import, and the destination space.6.Click Import .7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps. |
c.Enter a user name and password to sign in to the instance as an administrator.4.Identify a destination for the import.To import to your current instance, skip the Import to the current Oracle Integration instance field.To import to another Oracle Integration instance than your current instance, click Edit and complete the host, user name, and password fields for the instance you want to import to.To select importing to the current instance, click Reset .5.In the Scope field, identify what you want to import.Choose Entire Instance to import all process applications and decision models from all spaces located on the instance.Choose Space to import a selected source only.Select the space in the Source Space field that displays.Choose Process Application or Decision Model to import a selected application or decision model only.In the additional fields that display, select the source space, process application or decision model to import, and the destination space.6.Click Import .7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.Click Download Import Log in the import dialog to download a zip file containing the import log. |
4.Identify a destination for the import.To import to your current instance, skip the Import to the current Oracle Integration instance field.To import to another Oracle Integration instance than your current instance, click Edit and complete the host, user name, and password fields for the instance you want to import to.To select importing to the current instance, click Reset .5.In the Scope field, identify what you want to import.Choose Entire Instance to import all process applications and decision models from all spaces located on the instance.Choose Space to import a selected source only.Select the space in the Source Space field that displays.Choose Process Application or Decision Model to import a selected application or decision model only.In the additional fields that display, select the source space, process application or decision model to import, and the destination space.6.Click Import .7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.Click Download Import Log in the import dialog to download a zip file containing the import log.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-28.In Oracle Integration, change space settings as needed. |
To import to your current instance, skip the Import to the current Oracle Integration instance field.To import to another Oracle Integration instance than your current instance, click Edit and complete the host, user name, and password fields for the instance you want to import to.To select importing to the current instance, click Reset .5.In the Scope field, identify what you want to import.Choose Entire Instance to import all process applications and decision models from all spaces located on the instance.Choose Space to import a selected source only.Select the space in the Source Space field that displays.Choose Process Application or Decision Model to import a selected application or decision model only.In the additional fields that display, select the source space, process application or decision model to import, and the destination space.6.Click Import .7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.Click Download Import Log in the import dialog to download a zip file containing the import log.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-28.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions. |
To import to another Oracle Integration instance than your current instance, click Edit and complete the host, user name, and password fields for the instance you want to import to.To select importing to the current instance, click Reset .5.In the Scope field, identify what you want to import.Choose Entire Instance to import all process applications and decision models from all spaces located on the instance.Choose Space to import a selected source only.Select the space in the Source Space field that displays.Choose Process Application or Decision Model to import a selected application or decision model only.In the additional fields that display, select the source space, process application or decision model to import, and the destination space.6.Click Import .7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.Click Download Import Log in the import dialog to download a zip file containing the import log.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-28.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Import Using the Import Command Line Utility Optionally, use an import command line to automatically move Process and decision design- time metadata from one instance to another instead of the user interface. |
To select importing to the current instance, click Reset .5.In the Scope field, identify what you want to import.Choose Entire Instance to import all process applications and decision models from all spaces located on the instance.Choose Space to import a selected source only.Select the space in the Source Space field that displays.Choose Process Application or Decision Model to import a selected application or decision model only.In the additional fields that display, select the source space, process application or decision model to import, and the destination space.6.Click Import .7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.Click Download Import Log in the import dialog to download a zip file containing the import log.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-28.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Import Using the Import Command Line Utility Optionally, use an import command line to automatically move Process and decision design- time metadata from one instance to another instead of the user interface.(The user interface tool is recommended.) |
5.In the Scope field, identify what you want to import.Choose Entire Instance to import all process applications and decision models from all spaces located on the instance.Choose Space to import a selected source only.Select the space in the Source Space field that displays.Choose Process Application or Decision Model to import a selected application or decision model only.In the additional fields that display, select the source space, process application or decision model to import, and the destination space.6.Click Import .7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.Click Download Import Log in the import dialog to download a zip file containing the import log.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-28.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Import Using the Import Command Line Utility Optionally, use an import command line to automatically move Process and decision design- time metadata from one instance to another instead of the user interface.(The user interface tool is recommended.)The utility moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models. |
Choose Entire Instance to import all process applications and decision models from all spaces located on the instance.Choose Space to import a selected source only.Select the space in the Source Space field that displays.Choose Process Application or Decision Model to import a selected application or decision model only.In the additional fields that display, select the source space, process application or decision model to import, and the destination space.6.Click Import .7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.Click Download Import Log in the import dialog to download a zip file containing the import log.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-28.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Import Using the Import Command Line Utility Optionally, use an import command line to automatically move Process and decision design- time metadata from one instance to another instead of the user interface.(The user interface tool is recommended.)The utility moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Note: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model. |
Choose Space to import a selected source only.Select the space in the Source Space field that displays.Choose Process Application or Decision Model to import a selected application or decision model only.In the additional fields that display, select the source space, process application or decision model to import, and the destination space.6.Click Import .7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.Click Download Import Log in the import dialog to download a zip file containing the import log.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-28.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Import Using the Import Command Line Utility Optionally, use an import command line to automatically move Process and decision design- time metadata from one instance to another instead of the user interface.(The user interface tool is recommended.)The utility moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Note: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results. |
Select the space in the Source Space field that displays.Choose Process Application or Decision Model to import a selected application or decision model only.In the additional fields that display, select the source space, process application or decision model to import, and the destination space.6.Click Import .7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.Click Download Import Log in the import dialog to download a zip file containing the import log.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-28.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Import Using the Import Command Line Utility Optionally, use an import command line to automatically move Process and decision design- time metadata from one instance to another instead of the user interface.(The user interface tool is recommended.)The utility moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Note: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Note: The import utility requires Java version 8 or later. |
Choose Process Application or Decision Model to import a selected application or decision model only.In the additional fields that display, select the source space, process application or decision model to import, and the destination space.6.Click Import .7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.Click Download Import Log in the import dialog to download a zip file containing the import log.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-28.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Import Using the Import Command Line Utility Optionally, use an import command line to automatically move Process and decision design- time metadata from one instance to another instead of the user interface.(The user interface tool is recommended.)The utility moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Note: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Note: The import utility requires Java version 8 or later.In addition, both the source and target instances must return a ping response. |
In the additional fields that display, select the source space, process application or decision model to import, and the destination space.6.Click Import .7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.Click Download Import Log in the import dialog to download a zip file containing the import log.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-28.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Import Using the Import Command Line Utility Optionally, use an import command line to automatically move Process and decision design- time metadata from one instance to another instead of the user interface.(The user interface tool is recommended.)The utility moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Note: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Note: The import utility requires Java version 8 or later.In addition, both the source and target instances must return a ping response.1.On the Oracle Integration Home page, click Processes in the navigation pane. |
6.Click Import .7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.Click Download Import Log in the import dialog to download a zip file containing the import log.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-28.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Import Using the Import Command Line Utility Optionally, use an import command line to automatically move Process and decision design- time metadata from one instance to another instead of the user interface.(The user interface tool is recommended.)The utility moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Note: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Note: The import utility requires Java version 8 or later.In addition, both the source and target instances must return a ping response.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import on the Administration page. |
7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.Click Download Import Log in the import dialog to download a zip file containing the import log.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-28.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Import Using the Import Command Line Utility Optionally, use an import command line to automatically move Process and decision design- time metadata from one instance to another instead of the user interface.(The user interface tool is recommended.)The utility moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Note: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Note: The import utility requires Java version 8 or later.In addition, both the source and target instances must return a ping response.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import on the Administration page.3.Click the Download Utility button and save it to a selected location. |
Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.Click Download Import Log in the import dialog to download a zip file containing the import log.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-28.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Import Using the Import Command Line Utility Optionally, use an import command line to automatically move Process and decision design- time metadata from one instance to another instead of the user interface.(The user interface tool is recommended.)The utility moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Note: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Note: The import utility requires Java version 8 or later.In addition, both the source and target instances must return a ping response.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import on the Administration page.3.Click the Download Utility button and save it to a selected location.4.Sign in to the Oracle Integration source and target environments. |
Click Download Import Log in the import dialog to download a zip file containing the import log.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-28.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Import Using the Import Command Line Utility Optionally, use an import command line to automatically move Process and decision design- time metadata from one instance to another instead of the user interface.(The user interface tool is recommended.)The utility moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Note: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Note: The import utility requires Java version 8 or later.In addition, both the source and target instances must return a ping response.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import on the Administration page.3.Click the Download Utility button and save it to a selected location.4.Sign in to the Oracle Integration source and target environments.5.Run the utility from the command line. |
It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-28.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Import Using the Import Command Line Utility Optionally, use an import command line to automatically move Process and decision design- time metadata from one instance to another instead of the user interface.(The user interface tool is recommended.)The utility moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Note: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Note: The import utility requires Java version 8 or later.In addition, both the source and target instances must return a ping response.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import on the Administration page.3.Click the Download Utility button and save it to a selected location.4.Sign in to the Oracle Integration source and target environments.5.Run the utility from the command line.Use arguments to import an entire instance, one or more of its spaces, or one or more process applications or decision models. |
Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Import Using the Import Command Line Utility Optionally, use an import command line to automatically move Process and decision design- time metadata from one instance to another instead of the user interface.(The user interface tool is recommended.)The utility moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Note: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Note: The import utility requires Java version 8 or later.In addition, both the source and target instances must return a ping response.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import on the Administration page.3.Click the Download Utility button and save it to a selected location.4.Sign in to the Oracle Integration source and target environments.5.Run the utility from the command line.Use arguments to import an entire instance, one or more of its spaces, or one or more process applications or decision models.Format $java -jar ImportTool.jar srcType=PCS srcHost=http:// host:port srcUser=user oicHost=http://host:port oicUser=user scope=scope Example: Import the entire Oracle Integration instance $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=SPACE srcSpace="123456789" Example: Import process applications (delimit items by pipe line) $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=PROJECT srcSpace="132457689 srcProject="Loan Application|Travel Application" oicSpace=123456789Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-36.When prompted by the utility, enter the source system password, then the target system password. |
Import Using the Import Command Line Utility Optionally, use an import command line to automatically move Process and decision design- time metadata from one instance to another instead of the user interface.(The user interface tool is recommended.)The utility moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Note: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Note: The import utility requires Java version 8 or later.In addition, both the source and target instances must return a ping response.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import on the Administration page.3.Click the Download Utility button and save it to a selected location.4.Sign in to the Oracle Integration source and target environments.5.Run the utility from the command line.Use arguments to import an entire instance, one or more of its spaces, or one or more process applications or decision models.Format $java -jar ImportTool.jar srcType=PCS srcHost=http:// host:port srcUser=user oicHost=http://host:port oicUser=user scope=scope Example: Import the entire Oracle Integration instance $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=SPACE srcSpace="123456789" Example: Import process applications (delimit items by pipe line) $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=PROJECT srcSpace="132457689 srcProject="Loan Application|Travel Application" oicSpace=123456789Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-36.When prompted by the utility, enter the source system password, then the target system password.7.Review the import log. |
(The user interface tool is recommended.)The utility moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Note: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Note: The import utility requires Java version 8 or later.In addition, both the source and target instances must return a ping response.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import on the Administration page.3.Click the Download Utility button and save it to a selected location.4.Sign in to the Oracle Integration source and target environments.5.Run the utility from the command line.Use arguments to import an entire instance, one or more of its spaces, or one or more process applications or decision models.Format $java -jar ImportTool.jar srcType=PCS srcHost=http:// host:port srcUser=user oicHost=http://host:port oicUser=user scope=scope Example: Import the entire Oracle Integration instance $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=SPACE srcSpace="123456789" Example: Import process applications (delimit items by pipe line) $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=PROJECT srcSpace="132457689 srcProject="Loan Application|Travel Application" oicSpace=123456789Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-36.When prompted by the utility, enter the source system password, then the target system password.7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps. |
The utility moves process applications and active decision models from a selected source (an Oracle Integration instance) to a selected Oracle Integration destination, and activates the decision models.Note: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Note: The import utility requires Java version 8 or later.In addition, both the source and target instances must return a ping response.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import on the Administration page.3.Click the Download Utility button and save it to a selected location.4.Sign in to the Oracle Integration source and target environments.5.Run the utility from the command line.Use arguments to import an entire instance, one or more of its spaces, or one or more process applications or decision models.Format $java -jar ImportTool.jar srcType=PCS srcHost=http:// host:port srcUser=user oicHost=http://host:port oicUser=user scope=scope Example: Import the entire Oracle Integration instance $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=SPACE srcSpace="123456789" Example: Import process applications (delimit items by pipe line) $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=PROJECT srcSpace="132457689 srcProject="Loan Application|Travel Application" oicSpace=123456789Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-36.When prompted by the utility, enter the source system password, then the target system password.7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.A zip file containing the import log is created in the SRC_TO_OIC folder. |
Note: You can specify an import scope, which allows you to import all Process assets for an instance, for a space, or a specific process application or decision model.Be sure not to import assets more than once, because doing so can lead to unpredictable results.Note: The import utility requires Java version 8 or later.In addition, both the source and target instances must return a ping response.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import on the Administration page.3.Click the Download Utility button and save it to a selected location.4.Sign in to the Oracle Integration source and target environments.5.Run the utility from the command line.Use arguments to import an entire instance, one or more of its spaces, or one or more process applications or decision models.Format $java -jar ImportTool.jar srcType=PCS srcHost=http:// host:port srcUser=user oicHost=http://host:port oicUser=user scope=scope Example: Import the entire Oracle Integration instance $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=SPACE srcSpace="123456789" Example: Import process applications (delimit items by pipe line) $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=PROJECT srcSpace="132457689 srcProject="Loan Application|Travel Application" oicSpace=123456789Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-36.When prompted by the utility, enter the source system password, then the target system password.7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.A zip file containing the import log is created in the SRC_TO_OIC folder.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported. |
Be sure not to import assets more than once, because doing so can lead to unpredictable results.Note: The import utility requires Java version 8 or later.In addition, both the source and target instances must return a ping response.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import on the Administration page.3.Click the Download Utility button and save it to a selected location.4.Sign in to the Oracle Integration source and target environments.5.Run the utility from the command line.Use arguments to import an entire instance, one or more of its spaces, or one or more process applications or decision models.Format $java -jar ImportTool.jar srcType=PCS srcHost=http:// host:port srcUser=user oicHost=http://host:port oicUser=user scope=scope Example: Import the entire Oracle Integration instance $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=SPACE srcSpace="123456789" Example: Import process applications (delimit items by pipe line) $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=PROJECT srcSpace="132457689 srcProject="Loan Application|Travel Application" oicSpace=123456789Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-36.When prompted by the utility, enter the source system password, then the target system password.7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.A zip file containing the import log is created in the SRC_TO_OIC folder.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.8.In Oracle Integration, change space settings as needed. |
Note: The import utility requires Java version 8 or later.In addition, both the source and target instances must return a ping response.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import on the Administration page.3.Click the Download Utility button and save it to a selected location.4.Sign in to the Oracle Integration source and target environments.5.Run the utility from the command line.Use arguments to import an entire instance, one or more of its spaces, or one or more process applications or decision models.Format $java -jar ImportTool.jar srcType=PCS srcHost=http:// host:port srcUser=user oicHost=http://host:port oicUser=user scope=scope Example: Import the entire Oracle Integration instance $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=SPACE srcSpace="123456789" Example: Import process applications (delimit items by pipe line) $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=PROJECT srcSpace="132457689 srcProject="Loan Application|Travel Application" oicSpace=123456789Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-36.When prompted by the utility, enter the source system password, then the target system password.7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.A zip file containing the import log is created in the SRC_TO_OIC folder.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.8.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions. |
In addition, both the source and target instances must return a ping response.1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import on the Administration page.3.Click the Download Utility button and save it to a selected location.4.Sign in to the Oracle Integration source and target environments.5.Run the utility from the command line.Use arguments to import an entire instance, one or more of its spaces, or one or more process applications or decision models.Format $java -jar ImportTool.jar srcType=PCS srcHost=http:// host:port srcUser=user oicHost=http://host:port oicUser=user scope=scope Example: Import the entire Oracle Integration instance $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=SPACE srcSpace="123456789" Example: Import process applications (delimit items by pipe line) $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=PROJECT srcSpace="132457689 srcProject="Loan Application|Travel Application" oicSpace=123456789Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-36.When prompted by the utility, enter the source system password, then the target system password.7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.A zip file containing the import log is created in the SRC_TO_OIC folder.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.8.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Migrate Integration and Process Design-Time Metadata into Oracle Integration You can export an archive of design-time metadata from an Oracle Integration Classic instance and import that archive into an Oracle Integration instance. |
1.On the Oracle Integration Home page, click Processes in the navigation pane.2.Click Settings in the navigation pane, then Import on the Administration page.3.Click the Download Utility button and save it to a selected location.4.Sign in to the Oracle Integration source and target environments.5.Run the utility from the command line.Use arguments to import an entire instance, one or more of its spaces, or one or more process applications or decision models.Format $java -jar ImportTool.jar srcType=PCS srcHost=http:// host:port srcUser=user oicHost=http://host:port oicUser=user scope=scope Example: Import the entire Oracle Integration instance $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=SPACE srcSpace="123456789" Example: Import process applications (delimit items by pipe line) $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=PROJECT srcSpace="132457689 srcProject="Loan Application|Travel Application" oicSpace=123456789Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-36.When prompted by the utility, enter the source system password, then the target system password.7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.A zip file containing the import log is created in the SRC_TO_OIC folder.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.8.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Migrate Integration and Process Design-Time Metadata into Oracle Integration You can export an archive of design-time metadata from an Oracle Integration Classic instance and import that archive into an Oracle Integration instance.All design-time metadata for Integrations and Processes gets migrated during import, including security and credential settings, IDCS role mappings, connection endpoints and password, and other dependencies. |
2.Click Settings in the navigation pane, then Import on the Administration page.3.Click the Download Utility button and save it to a selected location.4.Sign in to the Oracle Integration source and target environments.5.Run the utility from the command line.Use arguments to import an entire instance, one or more of its spaces, or one or more process applications or decision models.Format $java -jar ImportTool.jar srcType=PCS srcHost=http:// host:port srcUser=user oicHost=http://host:port oicUser=user scope=scope Example: Import the entire Oracle Integration instance $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=SPACE srcSpace="123456789" Example: Import process applications (delimit items by pipe line) $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=PROJECT srcSpace="132457689 srcProject="Loan Application|Travel Application" oicSpace=123456789Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-36.When prompted by the utility, enter the source system password, then the target system password.7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.A zip file containing the import log is created in the SRC_TO_OIC folder.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.8.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Migrate Integration and Process Design-Time Metadata into Oracle Integration You can export an archive of design-time metadata from an Oracle Integration Classic instance and import that archive into an Oracle Integration instance.All design-time metadata for Integrations and Processes gets migrated during import, including security and credential settings, IDCS role mappings, connection endpoints and password, and other dependencies.Integration and process activations occur automatically upon import if ImportActivateMode is set to ImportActivate . |
3.Click the Download Utility button and save it to a selected location.4.Sign in to the Oracle Integration source and target environments.5.Run the utility from the command line.Use arguments to import an entire instance, one or more of its spaces, or one or more process applications or decision models.Format $java -jar ImportTool.jar srcType=PCS srcHost=http:// host:port srcUser=user oicHost=http://host:port oicUser=user scope=scope Example: Import the entire Oracle Integration instance $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=SPACE srcSpace="123456789" Example: Import process applications (delimit items by pipe line) $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=PROJECT srcSpace="132457689 srcProject="Loan Application|Travel Application" oicSpace=123456789Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-36.When prompted by the utility, enter the source system password, then the target system password.7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.A zip file containing the import log is created in the SRC_TO_OIC folder.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.8.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Migrate Integration and Process Design-Time Metadata into Oracle Integration You can export an archive of design-time metadata from an Oracle Integration Classic instance and import that archive into an Oracle Integration instance.All design-time metadata for Integrations and Processes gets migrated during import, including security and credential settings, IDCS role mappings, connection endpoints and password, and other dependencies.Integration and process activations occur automatically upon import if ImportActivateMode is set to ImportActivate .Export the Integration and Process Design-Time Metadata Import the Design-Time Metadata into Oracle Integration Check the Design-Time Metadata Import Status Import the Design-Time Metadata into Oracle Integration After exporting Integration and Process design-time metadata to a zip archive file, import the file to Oracle Integration on Oracle Cloud Infrastructure. |
4.Sign in to the Oracle Integration source and target environments.5.Run the utility from the command line.Use arguments to import an entire instance, one or more of its spaces, or one or more process applications or decision models.Format $java -jar ImportTool.jar srcType=PCS srcHost=http:// host:port srcUser=user oicHost=http://host:port oicUser=user scope=scope Example: Import the entire Oracle Integration instance $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=SPACE srcSpace="123456789" Example: Import process applications (delimit items by pipe line) $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=PROJECT srcSpace="132457689 srcProject="Loan Application|Travel Application" oicSpace=123456789Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-36.When prompted by the utility, enter the source system password, then the target system password.7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.A zip file containing the import log is created in the SRC_TO_OIC folder.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.8.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Migrate Integration and Process Design-Time Metadata into Oracle Integration You can export an archive of design-time metadata from an Oracle Integration Classic instance and import that archive into an Oracle Integration instance.All design-time metadata for Integrations and Processes gets migrated during import, including security and credential settings, IDCS role mappings, connection endpoints and password, and other dependencies.Integration and process activations occur automatically upon import if ImportActivateMode is set to ImportActivate .Export the Integration and Process Design-Time Metadata Import the Design-Time Metadata into Oracle Integration Check the Design-Time Metadata Import Status Import the Design-Time Metadata into Oracle Integration After exporting Integration and Process design-time metadata to a zip archive file, import the file to Oracle Integration on Oracle Cloud Infrastructure.{ "archiveFile": " archive_file_name ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { // storageUrl points to the storage container "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-41.To import the archive, go to the Oracle Integration instance and invoke the REST API. |
5.Run the utility from the command line.Use arguments to import an entire instance, one or more of its spaces, or one or more process applications or decision models.Format $java -jar ImportTool.jar srcType=PCS srcHost=http:// host:port srcUser=user oicHost=http://host:port oicUser=user scope=scope Example: Import the entire Oracle Integration instance $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=SPACE srcSpace="123456789" Example: Import process applications (delimit items by pipe line) $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=PROJECT srcSpace="132457689 srcProject="Loan Application|Travel Application" oicSpace=123456789Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-36.When prompted by the utility, enter the source system password, then the target system password.7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.A zip file containing the import log is created in the SRC_TO_OIC folder.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.8.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Migrate Integration and Process Design-Time Metadata into Oracle Integration You can export an archive of design-time metadata from an Oracle Integration Classic instance and import that archive into an Oracle Integration instance.All design-time metadata for Integrations and Processes gets migrated during import, including security and credential settings, IDCS role mappings, connection endpoints and password, and other dependencies.Integration and process activations occur automatically upon import if ImportActivateMode is set to ImportActivate .Export the Integration and Process Design-Time Metadata Import the Design-Time Metadata into Oracle Integration Check the Design-Time Metadata Import Status Import the Design-Time Metadata into Oracle Integration After exporting Integration and Process design-time metadata to a zip archive file, import the file to Oracle Integration on Oracle Cloud Infrastructure.{ "archiveFile": " archive_file_name ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { // storageUrl points to the storage container "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-41.To import the archive, go to the Oracle Integration instance and invoke the REST API.This action retrieves the archive from the Oracle Storage Cloud Service instance where the archive was created. |
Use arguments to import an entire instance, one or more of its spaces, or one or more process applications or decision models.Format $java -jar ImportTool.jar srcType=PCS srcHost=http:// host:port srcUser=user oicHost=http://host:port oicUser=user scope=scope Example: Import the entire Oracle Integration instance $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=SPACE srcSpace="123456789" Example: Import process applications (delimit items by pipe line) $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=PROJECT srcSpace="132457689 srcProject="Loan Application|Travel Application" oicSpace=123456789Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-36.When prompted by the utility, enter the source system password, then the target system password.7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.A zip file containing the import log is created in the SRC_TO_OIC folder.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.8.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Migrate Integration and Process Design-Time Metadata into Oracle Integration You can export an archive of design-time metadata from an Oracle Integration Classic instance and import that archive into an Oracle Integration instance.All design-time metadata for Integrations and Processes gets migrated during import, including security and credential settings, IDCS role mappings, connection endpoints and password, and other dependencies.Integration and process activations occur automatically upon import if ImportActivateMode is set to ImportActivate .Export the Integration and Process Design-Time Metadata Import the Design-Time Metadata into Oracle Integration Check the Design-Time Metadata Import Status Import the Design-Time Metadata into Oracle Integration After exporting Integration and Process design-time metadata to a zip archive file, import the file to Oracle Integration on Oracle Cloud Infrastructure.{ "archiveFile": " archive_file_name ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { // storageUrl points to the storage container "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-41.To import the archive, go to the Oracle Integration instance and invoke the REST API.This action retrieves the archive from the Oracle Storage Cloud Service instance where the archive was created.Headers Authorization : Basic Content-Type : application/json payload { "archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04- e9b9e8374b68.zip ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/ v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to import the archive of design time objects into Oracle Integration. |
Format $java -jar ImportTool.jar srcType=PCS srcHost=http:// host:port srcUser=user oicHost=http://host:port oicUser=user scope=scope Example: Import the entire Oracle Integration instance $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=SPACE srcSpace="123456789" Example: Import process applications (delimit items by pipe line) $java -jar ImportTool.jar srcType=PCS srcHost=http:// abc01xyz.example.com:7001 srcUser=user1 oicHost=http:// def02uvw.example.com:7001 oicUser=user1 scope=PROJECT srcSpace="132457689 srcProject="Loan Application|Travel Application" oicSpace=123456789Appendix A Migrate Processes Design-Time Metadata into Oracle Integration A-36.When prompted by the utility, enter the source system password, then the target system password.7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.A zip file containing the import log is created in the SRC_TO_OIC folder.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.8.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Migrate Integration and Process Design-Time Metadata into Oracle Integration You can export an archive of design-time metadata from an Oracle Integration Classic instance and import that archive into an Oracle Integration instance.All design-time metadata for Integrations and Processes gets migrated during import, including security and credential settings, IDCS role mappings, connection endpoints and password, and other dependencies.Integration and process activations occur automatically upon import if ImportActivateMode is set to ImportActivate .Export the Integration and Process Design-Time Metadata Import the Design-Time Metadata into Oracle Integration Check the Design-Time Metadata Import Status Import the Design-Time Metadata into Oracle Integration After exporting Integration and Process design-time metadata to a zip archive file, import the file to Oracle Integration on Oracle Cloud Infrastructure.{ "archiveFile": " archive_file_name ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { // storageUrl points to the storage container "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-41.To import the archive, go to the Oracle Integration instance and invoke the REST API.This action retrieves the archive from the Oracle Storage Cloud Service instance where the archive was created.Headers Authorization : Basic Content-Type : application/json payload { "archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04- e9b9e8374b68.zip ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/ v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to import the archive of design time objects into Oracle Integration.You can set importActivateMode to the following values: ImportOnly : Imports, but does not activate, integrations and process applications. |
7.Review the import log.Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.A zip file containing the import log is created in the SRC_TO_OIC folder.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.8.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Migrate Integration and Process Design-Time Metadata into Oracle Integration You can export an archive of design-time metadata from an Oracle Integration Classic instance and import that archive into an Oracle Integration instance.All design-time metadata for Integrations and Processes gets migrated during import, including security and credential settings, IDCS role mappings, connection endpoints and password, and other dependencies.Integration and process activations occur automatically upon import if ImportActivateMode is set to ImportActivate .Export the Integration and Process Design-Time Metadata Import the Design-Time Metadata into Oracle Integration Check the Design-Time Metadata Import Status Import the Design-Time Metadata into Oracle Integration After exporting Integration and Process design-time metadata to a zip archive file, import the file to Oracle Integration on Oracle Cloud Infrastructure.{ "archiveFile": " archive_file_name ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { // storageUrl points to the storage container "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-41.To import the archive, go to the Oracle Integration instance and invoke the REST API.This action retrieves the archive from the Oracle Storage Cloud Service instance where the archive was created.Headers Authorization : Basic Content-Type : application/json payload { "archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04- e9b9e8374b68.zip ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/ v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to import the archive of design time objects into Oracle Integration.You can set importActivateMode to the following values: ImportOnly : Imports, but does not activate, integrations and process applications.ActivateOnly : Activates previously imported integrations and process applications. |
Note: You must check the logs and make sure there are no errors before proceeding with post migration steps.A zip file containing the import log is created in the SRC_TO_OIC folder.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.8.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Migrate Integration and Process Design-Time Metadata into Oracle Integration You can export an archive of design-time metadata from an Oracle Integration Classic instance and import that archive into an Oracle Integration instance.All design-time metadata for Integrations and Processes gets migrated during import, including security and credential settings, IDCS role mappings, connection endpoints and password, and other dependencies.Integration and process activations occur automatically upon import if ImportActivateMode is set to ImportActivate .Export the Integration and Process Design-Time Metadata Import the Design-Time Metadata into Oracle Integration Check the Design-Time Metadata Import Status Import the Design-Time Metadata into Oracle Integration After exporting Integration and Process design-time metadata to a zip archive file, import the file to Oracle Integration on Oracle Cloud Infrastructure.{ "archiveFile": " archive_file_name ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { // storageUrl points to the storage container "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-41.To import the archive, go to the Oracle Integration instance and invoke the REST API.This action retrieves the archive from the Oracle Storage Cloud Service instance where the archive was created.Headers Authorization : Basic Content-Type : application/json payload { "archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04- e9b9e8374b68.zip ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/ v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to import the archive of design time objects into Oracle Integration.You can set importActivateMode to the following values: ImportOnly : Imports, but does not activate, integrations and process applications.ActivateOnly : Activates previously imported integrations and process applications.This enables you to update connection parameters before activating integrations. |
A zip file containing the import log is created in the SRC_TO_OIC folder.It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.8.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Migrate Integration and Process Design-Time Metadata into Oracle Integration You can export an archive of design-time metadata from an Oracle Integration Classic instance and import that archive into an Oracle Integration instance.All design-time metadata for Integrations and Processes gets migrated during import, including security and credential settings, IDCS role mappings, connection endpoints and password, and other dependencies.Integration and process activations occur automatically upon import if ImportActivateMode is set to ImportActivate .Export the Integration and Process Design-Time Metadata Import the Design-Time Metadata into Oracle Integration Check the Design-Time Metadata Import Status Import the Design-Time Metadata into Oracle Integration After exporting Integration and Process design-time metadata to a zip archive file, import the file to Oracle Integration on Oracle Cloud Infrastructure.{ "archiveFile": " archive_file_name ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { // storageUrl points to the storage container "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-41.To import the archive, go to the Oracle Integration instance and invoke the REST API.This action retrieves the archive from the Oracle Storage Cloud Service instance where the archive was created.Headers Authorization : Basic Content-Type : application/json payload { "archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04- e9b9e8374b68.zip ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/ v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to import the archive of design time objects into Oracle Integration.You can set importActivateMode to the following values: ImportOnly : Imports, but does not activate, integrations and process applications.ActivateOnly : Activates previously imported integrations and process applications.This enables you to update connection parameters before activating integrations.ImportActivate : Imports and activates integrations and process applications. |
It lists any errors that might have occurred along with a summary of the number of spaces or items (process applications or decision models) imported.8.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Migrate Integration and Process Design-Time Metadata into Oracle Integration You can export an archive of design-time metadata from an Oracle Integration Classic instance and import that archive into an Oracle Integration instance.All design-time metadata for Integrations and Processes gets migrated during import, including security and credential settings, IDCS role mappings, connection endpoints and password, and other dependencies.Integration and process activations occur automatically upon import if ImportActivateMode is set to ImportActivate .Export the Integration and Process Design-Time Metadata Import the Design-Time Metadata into Oracle Integration Check the Design-Time Metadata Import Status Import the Design-Time Metadata into Oracle Integration After exporting Integration and Process design-time metadata to a zip archive file, import the file to Oracle Integration on Oracle Cloud Infrastructure.{ "archiveFile": " archive_file_name ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { // storageUrl points to the storage container "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-41.To import the archive, go to the Oracle Integration instance and invoke the REST API.This action retrieves the archive from the Oracle Storage Cloud Service instance where the archive was created.Headers Authorization : Basic Content-Type : application/json payload { "archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04- e9b9e8374b68.zip ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/ v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to import the archive of design time objects into Oracle Integration.You can set importActivateMode to the following values: ImportOnly : Imports, but does not activate, integrations and process applications.ActivateOnly : Activates previously imported integrations and process applications.This enables you to update connection parameters before activating integrations.ImportActivate : Imports and activates integrations and process applications.curl -k -v -H "Content-Type: application/json" -X POST -d {"archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04-e9b9e8374b68.zip", "importActivateMode": "ImportOnly", "storageInfo": { "storageUrl":"https:// swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo","storageUser" :"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/importServiceInstanceArchive Possible sample output from this command is as follows: { "jobId":"554", "status":"NOT_STARTED" }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-5Check the Design-Time Metadata Import Status Verify the design-time metadata import status after completing the import task. |
8.In Oracle Integration, change space settings as needed.Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Migrate Integration and Process Design-Time Metadata into Oracle Integration You can export an archive of design-time metadata from an Oracle Integration Classic instance and import that archive into an Oracle Integration instance.All design-time metadata for Integrations and Processes gets migrated during import, including security and credential settings, IDCS role mappings, connection endpoints and password, and other dependencies.Integration and process activations occur automatically upon import if ImportActivateMode is set to ImportActivate .Export the Integration and Process Design-Time Metadata Import the Design-Time Metadata into Oracle Integration Check the Design-Time Metadata Import Status Import the Design-Time Metadata into Oracle Integration After exporting Integration and Process design-time metadata to a zip archive file, import the file to Oracle Integration on Oracle Cloud Infrastructure.{ "archiveFile": " archive_file_name ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { // storageUrl points to the storage container "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-41.To import the archive, go to the Oracle Integration instance and invoke the REST API.This action retrieves the archive from the Oracle Storage Cloud Service instance where the archive was created.Headers Authorization : Basic Content-Type : application/json payload { "archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04- e9b9e8374b68.zip ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/ v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to import the archive of design time objects into Oracle Integration.You can set importActivateMode to the following values: ImportOnly : Imports, but does not activate, integrations and process applications.ActivateOnly : Activates previously imported integrations and process applications.This enables you to update connection parameters before activating integrations.ImportActivate : Imports and activates integrations and process applications.curl -k -v -H "Content-Type: application/json" -X POST -d {"archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04-e9b9e8374b68.zip", "importActivateMode": "ImportOnly", "storageInfo": { "storageUrl":"https:// swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo","storageUser" :"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/importServiceInstanceArchive Possible sample output from this command is as follows: { "jobId":"554", "status":"NOT_STARTED" }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-5Check the Design-Time Metadata Import Status Verify the design-time metadata import status after completing the import task.1.Check the status of the import operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ importServiceInstanceArchive/554 Possible sample output from this command is as follows. |
Return to the design-time Administration screen, and share the space(s) you migrated to Oracle Integration and change their permissions.Migrate Integration and Process Design-Time Metadata into Oracle Integration You can export an archive of design-time metadata from an Oracle Integration Classic instance and import that archive into an Oracle Integration instance.All design-time metadata for Integrations and Processes gets migrated during import, including security and credential settings, IDCS role mappings, connection endpoints and password, and other dependencies.Integration and process activations occur automatically upon import if ImportActivateMode is set to ImportActivate .Export the Integration and Process Design-Time Metadata Import the Design-Time Metadata into Oracle Integration Check the Design-Time Metadata Import Status Import the Design-Time Metadata into Oracle Integration After exporting Integration and Process design-time metadata to a zip archive file, import the file to Oracle Integration on Oracle Cloud Infrastructure.{ "archiveFile": " archive_file_name ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { // storageUrl points to the storage container "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-41.To import the archive, go to the Oracle Integration instance and invoke the REST API.This action retrieves the archive from the Oracle Storage Cloud Service instance where the archive was created.Headers Authorization : Basic Content-Type : application/json payload { "archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04- e9b9e8374b68.zip ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/ v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to import the archive of design time objects into Oracle Integration.You can set importActivateMode to the following values: ImportOnly : Imports, but does not activate, integrations and process applications.ActivateOnly : Activates previously imported integrations and process applications.This enables you to update connection parameters before activating integrations.ImportActivate : Imports and activates integrations and process applications.curl -k -v -H "Content-Type: application/json" -X POST -d {"archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04-e9b9e8374b68.zip", "importActivateMode": "ImportOnly", "storageInfo": { "storageUrl":"https:// swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo","storageUser" :"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/importServiceInstanceArchive Possible sample output from this command is as follows: { "jobId":"554", "status":"NOT_STARTED" }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-5Check the Design-Time Metadata Import Status Verify the design-time metadata import status after completing the import task.1.Check the status of the import operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ importServiceInstanceArchive/554 Possible sample output from this command is as follows.Other potential output includes RUNNING , COMPLETED , and FAILED . |
Migrate Integration and Process Design-Time Metadata into Oracle Integration You can export an archive of design-time metadata from an Oracle Integration Classic instance and import that archive into an Oracle Integration instance.All design-time metadata for Integrations and Processes gets migrated during import, including security and credential settings, IDCS role mappings, connection endpoints and password, and other dependencies.Integration and process activations occur automatically upon import if ImportActivateMode is set to ImportActivate .Export the Integration and Process Design-Time Metadata Import the Design-Time Metadata into Oracle Integration Check the Design-Time Metadata Import Status Import the Design-Time Metadata into Oracle Integration After exporting Integration and Process design-time metadata to a zip archive file, import the file to Oracle Integration on Oracle Cloud Infrastructure.{ "archiveFile": " archive_file_name ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { // storageUrl points to the storage container "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-41.To import the archive, go to the Oracle Integration instance and invoke the REST API.This action retrieves the archive from the Oracle Storage Cloud Service instance where the archive was created.Headers Authorization : Basic Content-Type : application/json payload { "archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04- e9b9e8374b68.zip ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/ v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to import the archive of design time objects into Oracle Integration.You can set importActivateMode to the following values: ImportOnly : Imports, but does not activate, integrations and process applications.ActivateOnly : Activates previously imported integrations and process applications.This enables you to update connection parameters before activating integrations.ImportActivate : Imports and activates integrations and process applications.curl -k -v -H "Content-Type: application/json" -X POST -d {"archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04-e9b9e8374b68.zip", "importActivateMode": "ImportOnly", "storageInfo": { "storageUrl":"https:// swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo","storageUser" :"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/importServiceInstanceArchive Possible sample output from this command is as follows: { "jobId":"554", "status":"NOT_STARTED" }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-5Check the Design-Time Metadata Import Status Verify the design-time metadata import status after completing the import task.1.Check the status of the import operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ importServiceInstanceArchive/554 Possible sample output from this command is as follows.Other potential output includes RUNNING , COMPLETED , and FAILED .{ "jobId":"5108", "overallStatus":"RUNNING", "componentStatus":[ { "component":"Integration", "status":"RUNNING" } ] } { "jobId":"5108", "overall Status":"COMPLETED", "componentStatus":[ { "component":"Integration", "status":"COMPLETED", "percentage":100 } ] } 2.Log in to your Oracle Integration instance. |
All design-time metadata for Integrations and Processes gets migrated during import, including security and credential settings, IDCS role mappings, connection endpoints and password, and other dependencies.Integration and process activations occur automatically upon import if ImportActivateMode is set to ImportActivate .Export the Integration and Process Design-Time Metadata Import the Design-Time Metadata into Oracle Integration Check the Design-Time Metadata Import Status Import the Design-Time Metadata into Oracle Integration After exporting Integration and Process design-time metadata to a zip archive file, import the file to Oracle Integration on Oracle Cloud Infrastructure.{ "archiveFile": " archive_file_name ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { // storageUrl points to the storage container "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-41.To import the archive, go to the Oracle Integration instance and invoke the REST API.This action retrieves the archive from the Oracle Storage Cloud Service instance where the archive was created.Headers Authorization : Basic Content-Type : application/json payload { "archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04- e9b9e8374b68.zip ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/ v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to import the archive of design time objects into Oracle Integration.You can set importActivateMode to the following values: ImportOnly : Imports, but does not activate, integrations and process applications.ActivateOnly : Activates previously imported integrations and process applications.This enables you to update connection parameters before activating integrations.ImportActivate : Imports and activates integrations and process applications.curl -k -v -H "Content-Type: application/json" -X POST -d {"archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04-e9b9e8374b68.zip", "importActivateMode": "ImportOnly", "storageInfo": { "storageUrl":"https:// swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo","storageUser" :"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/importServiceInstanceArchive Possible sample output from this command is as follows: { "jobId":"554", "status":"NOT_STARTED" }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-5Check the Design-Time Metadata Import Status Verify the design-time metadata import status after completing the import task.1.Check the status of the import operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ importServiceInstanceArchive/554 Possible sample output from this command is as follows.Other potential output includes RUNNING , COMPLETED , and FAILED .{ "jobId":"5108", "overallStatus":"RUNNING", "componentStatus":[ { "component":"Integration", "status":"RUNNING" } ] } { "jobId":"5108", "overall Status":"COMPLETED", "componentStatus":[ { "component":"Integration", "status":"COMPLETED", "percentage":100 } ] } 2.Log in to your Oracle Integration instance.3.Browse the pages and note that the design-time metadata you exported from your Oracle Integration Classic instance are now visible. |
Integration and process activations occur automatically upon import if ImportActivateMode is set to ImportActivate .Export the Integration and Process Design-Time Metadata Import the Design-Time Metadata into Oracle Integration Check the Design-Time Metadata Import Status Import the Design-Time Metadata into Oracle Integration After exporting Integration and Process design-time metadata to a zip archive file, import the file to Oracle Integration on Oracle Cloud Infrastructure.{ "archiveFile": " archive_file_name ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { // storageUrl points to the storage container "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-41.To import the archive, go to the Oracle Integration instance and invoke the REST API.This action retrieves the archive from the Oracle Storage Cloud Service instance where the archive was created.Headers Authorization : Basic Content-Type : application/json payload { "archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04- e9b9e8374b68.zip ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/ v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to import the archive of design time objects into Oracle Integration.You can set importActivateMode to the following values: ImportOnly : Imports, but does not activate, integrations and process applications.ActivateOnly : Activates previously imported integrations and process applications.This enables you to update connection parameters before activating integrations.ImportActivate : Imports and activates integrations and process applications.curl -k -v -H "Content-Type: application/json" -X POST -d {"archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04-e9b9e8374b68.zip", "importActivateMode": "ImportOnly", "storageInfo": { "storageUrl":"https:// swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo","storageUser" :"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/importServiceInstanceArchive Possible sample output from this command is as follows: { "jobId":"554", "status":"NOT_STARTED" }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-5Check the Design-Time Metadata Import Status Verify the design-time metadata import status after completing the import task.1.Check the status of the import operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ importServiceInstanceArchive/554 Possible sample output from this command is as follows.Other potential output includes RUNNING , COMPLETED , and FAILED .{ "jobId":"5108", "overallStatus":"RUNNING", "componentStatus":[ { "component":"Integration", "status":"RUNNING" } ] } { "jobId":"5108", "overall Status":"COMPLETED", "componentStatus":[ { "component":"Integration", "status":"COMPLETED", "percentage":100 } ] } 2.Log in to your Oracle Integration instance.3.Browse the pages and note that the design-time metadata you exported from your Oracle Integration Classic instance are now visible.For example, for Integrations, look for integrations, connections, lookups, and more. |
Export the Integration and Process Design-Time Metadata Import the Design-Time Metadata into Oracle Integration Check the Design-Time Metadata Import Status Import the Design-Time Metadata into Oracle Integration After exporting Integration and Process design-time metadata to a zip archive file, import the file to Oracle Integration on Oracle Cloud Infrastructure.{ "archiveFile": " archive_file_name ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { // storageUrl points to the storage container "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-41.To import the archive, go to the Oracle Integration instance and invoke the REST API.This action retrieves the archive from the Oracle Storage Cloud Service instance where the archive was created.Headers Authorization : Basic Content-Type : application/json payload { "archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04- e9b9e8374b68.zip ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/ v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to import the archive of design time objects into Oracle Integration.You can set importActivateMode to the following values: ImportOnly : Imports, but does not activate, integrations and process applications.ActivateOnly : Activates previously imported integrations and process applications.This enables you to update connection parameters before activating integrations.ImportActivate : Imports and activates integrations and process applications.curl -k -v -H "Content-Type: application/json" -X POST -d {"archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04-e9b9e8374b68.zip", "importActivateMode": "ImportOnly", "storageInfo": { "storageUrl":"https:// swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo","storageUser" :"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/importServiceInstanceArchive Possible sample output from this command is as follows: { "jobId":"554", "status":"NOT_STARTED" }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-5Check the Design-Time Metadata Import Status Verify the design-time metadata import status after completing the import task.1.Check the status of the import operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ importServiceInstanceArchive/554 Possible sample output from this command is as follows.Other potential output includes RUNNING , COMPLETED , and FAILED .{ "jobId":"5108", "overallStatus":"RUNNING", "componentStatus":[ { "component":"Integration", "status":"RUNNING" } ] } { "jobId":"5108", "overall Status":"COMPLETED", "componentStatus":[ { "component":"Integration", "status":"COMPLETED", "percentage":100 } ] } 2.Log in to your Oracle Integration instance.3.Browse the pages and note that the design-time metadata you exported from your Oracle Integration Classic instance are now visible.For example, for Integrations, look for integrations, connections, lookups, and more.For Processes, look for process applications and decision models.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-6Export the Integration and Process Design-Time Metadata You must export the design-time metadata. |
{ "archiveFile": " archive_file_name ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { // storageUrl points to the storage container "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-41.To import the archive, go to the Oracle Integration instance and invoke the REST API.This action retrieves the archive from the Oracle Storage Cloud Service instance where the archive was created.Headers Authorization : Basic Content-Type : application/json payload { "archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04- e9b9e8374b68.zip ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/ v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to import the archive of design time objects into Oracle Integration.You can set importActivateMode to the following values: ImportOnly : Imports, but does not activate, integrations and process applications.ActivateOnly : Activates previously imported integrations and process applications.This enables you to update connection parameters before activating integrations.ImportActivate : Imports and activates integrations and process applications.curl -k -v -H "Content-Type: application/json" -X POST -d {"archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04-e9b9e8374b68.zip", "importActivateMode": "ImportOnly", "storageInfo": { "storageUrl":"https:// swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo","storageUser" :"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/importServiceInstanceArchive Possible sample output from this command is as follows: { "jobId":"554", "status":"NOT_STARTED" }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-5Check the Design-Time Metadata Import Status Verify the design-time metadata import status after completing the import task.1.Check the status of the import operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ importServiceInstanceArchive/554 Possible sample output from this command is as follows.Other potential output includes RUNNING , COMPLETED , and FAILED .{ "jobId":"5108", "overallStatus":"RUNNING", "componentStatus":[ { "component":"Integration", "status":"RUNNING" } ] } { "jobId":"5108", "overall Status":"COMPLETED", "componentStatus":[ { "component":"Integration", "status":"COMPLETED", "percentage":100 } ] } 2.Log in to your Oracle Integration instance.3.Browse the pages and note that the design-time metadata you exported from your Oracle Integration Classic instance are now visible.For example, for Integrations, look for integrations, connections, lookups, and more.For Processes, look for process applications and decision models.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-6Export the Integration and Process Design-Time Metadata You must export the design-time metadata.Note: Before attempting to export design-time metadata, ensure that you completed Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) . |
This action retrieves the archive from the Oracle Storage Cloud Service instance where the archive was created.Headers Authorization : Basic Content-Type : application/json payload { "archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04- e9b9e8374b68.zip ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/ v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to import the archive of design time objects into Oracle Integration.You can set importActivateMode to the following values: ImportOnly : Imports, but does not activate, integrations and process applications.ActivateOnly : Activates previously imported integrations and process applications.This enables you to update connection parameters before activating integrations.ImportActivate : Imports and activates integrations and process applications.curl -k -v -H "Content-Type: application/json" -X POST -d {"archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04-e9b9e8374b68.zip", "importActivateMode": "ImportOnly", "storageInfo": { "storageUrl":"https:// swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo","storageUser" :"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/importServiceInstanceArchive Possible sample output from this command is as follows: { "jobId":"554", "status":"NOT_STARTED" }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-5Check the Design-Time Metadata Import Status Verify the design-time metadata import status after completing the import task.1.Check the status of the import operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ importServiceInstanceArchive/554 Possible sample output from this command is as follows.Other potential output includes RUNNING , COMPLETED , and FAILED .{ "jobId":"5108", "overallStatus":"RUNNING", "componentStatus":[ { "component":"Integration", "status":"RUNNING" } ] } { "jobId":"5108", "overall Status":"COMPLETED", "componentStatus":[ { "component":"Integration", "status":"COMPLETED", "percentage":100 } ] } 2.Log in to your Oracle Integration instance.3.Browse the pages and note that the design-time metadata you exported from your Oracle Integration Classic instance are now visible.For example, for Integrations, look for integrations, connections, lookups, and more.For Processes, look for process applications and decision models.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-6Export the Integration and Process Design-Time Metadata You must export the design-time metadata.Note: Before attempting to export design-time metadata, ensure that you completed Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .For details about the scope of Integrations, Processes, and Visual Builder design-time metadata migrated, see About the Migration Scope . |
Headers Authorization : Basic Content-Type : application/json payload { "archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04- e9b9e8374b68.zip ", "importActivateMode": "ImportActivate", // options are "ImportOnly" || "ActivateOnly" || "ImportActivate" "storageInfo": { "storageUrl":"https://swiftobjectstorage.us- region -1.oraclecloud.com/ v1/paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to import the archive of design time objects into Oracle Integration.You can set importActivateMode to the following values: ImportOnly : Imports, but does not activate, integrations and process applications.ActivateOnly : Activates previously imported integrations and process applications.This enables you to update connection parameters before activating integrations.ImportActivate : Imports and activates integrations and process applications.curl -k -v -H "Content-Type: application/json" -X POST -d {"archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04-e9b9e8374b68.zip", "importActivateMode": "ImportOnly", "storageInfo": { "storageUrl":"https:// swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo","storageUser" :"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/importServiceInstanceArchive Possible sample output from this command is as follows: { "jobId":"554", "status":"NOT_STARTED" }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-5Check the Design-Time Metadata Import Status Verify the design-time metadata import status after completing the import task.1.Check the status of the import operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ importServiceInstanceArchive/554 Possible sample output from this command is as follows.Other potential output includes RUNNING , COMPLETED , and FAILED .{ "jobId":"5108", "overallStatus":"RUNNING", "componentStatus":[ { "component":"Integration", "status":"RUNNING" } ] } { "jobId":"5108", "overall Status":"COMPLETED", "componentStatus":[ { "component":"Integration", "status":"COMPLETED", "percentage":100 } ] } 2.Log in to your Oracle Integration instance.3.Browse the pages and note that the design-time metadata you exported from your Oracle Integration Classic instance are now visible.For example, for Integrations, look for integrations, connections, lookups, and more.For Processes, look for process applications and decision models.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-6Export the Integration and Process Design-Time Metadata You must export the design-time metadata.Note: Before attempting to export design-time metadata, ensure that you completed Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .For details about the scope of Integrations, Processes, and Visual Builder design-time metadata migrated, see About the Migration Scope .1.For the design-time metadata of the Oracle Integration Classic instance to export to Oracle Integration, invoke the REST API. |
You can set importActivateMode to the following values: ImportOnly : Imports, but does not activate, integrations and process applications.ActivateOnly : Activates previously imported integrations and process applications.This enables you to update connection parameters before activating integrations.ImportActivate : Imports and activates integrations and process applications.curl -k -v -H "Content-Type: application/json" -X POST -d {"archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04-e9b9e8374b68.zip", "importActivateMode": "ImportOnly", "storageInfo": { "storageUrl":"https:// swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo","storageUser" :"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/importServiceInstanceArchive Possible sample output from this command is as follows: { "jobId":"554", "status":"NOT_STARTED" }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-5Check the Design-Time Metadata Import Status Verify the design-time metadata import status after completing the import task.1.Check the status of the import operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ importServiceInstanceArchive/554 Possible sample output from this command is as follows.Other potential output includes RUNNING , COMPLETED , and FAILED .{ "jobId":"5108", "overallStatus":"RUNNING", "componentStatus":[ { "component":"Integration", "status":"RUNNING" } ] } { "jobId":"5108", "overall Status":"COMPLETED", "componentStatus":[ { "component":"Integration", "status":"COMPLETED", "percentage":100 } ] } 2.Log in to your Oracle Integration instance.3.Browse the pages and note that the design-time metadata you exported from your Oracle Integration Classic instance are now visible.For example, for Integrations, look for integrations, connections, lookups, and more.For Processes, look for process applications and decision models.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-6Export the Integration and Process Design-Time Metadata You must export the design-time metadata.Note: Before attempting to export design-time metadata, ensure that you completed Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .For details about the scope of Integrations, Processes, and Visual Builder design-time metadata migrated, see About the Migration Scope .1.For the design-time metadata of the Oracle Integration Classic instance to export to Oracle Integration, invoke the REST API.This action asynchronously creates an archive that includes all above-mentioned objects. |
ActivateOnly : Activates previously imported integrations and process applications.This enables you to update connection parameters before activating integrations.ImportActivate : Imports and activates integrations and process applications.curl -k -v -H "Content-Type: application/json" -X POST -d {"archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04-e9b9e8374b68.zip", "importActivateMode": "ImportOnly", "storageInfo": { "storageUrl":"https:// swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo","storageUser" :"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/importServiceInstanceArchive Possible sample output from this command is as follows: { "jobId":"554", "status":"NOT_STARTED" }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-5Check the Design-Time Metadata Import Status Verify the design-time metadata import status after completing the import task.1.Check the status of the import operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ importServiceInstanceArchive/554 Possible sample output from this command is as follows.Other potential output includes RUNNING , COMPLETED , and FAILED .{ "jobId":"5108", "overallStatus":"RUNNING", "componentStatus":[ { "component":"Integration", "status":"RUNNING" } ] } { "jobId":"5108", "overall Status":"COMPLETED", "componentStatus":[ { "component":"Integration", "status":"COMPLETED", "percentage":100 } ] } 2.Log in to your Oracle Integration instance.3.Browse the pages and note that the design-time metadata you exported from your Oracle Integration Classic instance are now visible.For example, for Integrations, look for integrations, connections, lookups, and more.For Processes, look for process applications and decision models.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-6Export the Integration and Process Design-Time Metadata You must export the design-time metadata.Note: Before attempting to export design-time metadata, ensure that you completed Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .For details about the scope of Integrations, Processes, and Visual Builder design-time metadata migrated, see About the Migration Scope .1.For the design-time metadata of the Oracle Integration Classic instance to export to Oracle Integration, invoke the REST API.This action asynchronously creates an archive that includes all above-mentioned objects.Headers Authorization : Basic Content-Type : application/json payload { "storageInfo": { "storageUrl": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to export all Integration and Process design time metadata to an Oracle Storage Cloud Service instance that you specify: curl -k -v -H "Content-Type: application/json" -X POST -d {"storageInfo":{"storageUrl":" https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo","storageUser":"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/exportServiceInstanceArchive where: storageInfo : Is the URL of the storage container. |
This enables you to update connection parameters before activating integrations.ImportActivate : Imports and activates integrations and process applications.curl -k -v -H "Content-Type: application/json" -X POST -d {"archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04-e9b9e8374b68.zip", "importActivateMode": "ImportOnly", "storageInfo": { "storageUrl":"https:// swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo","storageUser" :"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/importServiceInstanceArchive Possible sample output from this command is as follows: { "jobId":"554", "status":"NOT_STARTED" }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-5Check the Design-Time Metadata Import Status Verify the design-time metadata import status after completing the import task.1.Check the status of the import operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ importServiceInstanceArchive/554 Possible sample output from this command is as follows.Other potential output includes RUNNING , COMPLETED , and FAILED .{ "jobId":"5108", "overallStatus":"RUNNING", "componentStatus":[ { "component":"Integration", "status":"RUNNING" } ] } { "jobId":"5108", "overall Status":"COMPLETED", "componentStatus":[ { "component":"Integration", "status":"COMPLETED", "percentage":100 } ] } 2.Log in to your Oracle Integration instance.3.Browse the pages and note that the design-time metadata you exported from your Oracle Integration Classic instance are now visible.For example, for Integrations, look for integrations, connections, lookups, and more.For Processes, look for process applications and decision models.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-6Export the Integration and Process Design-Time Metadata You must export the design-time metadata.Note: Before attempting to export design-time metadata, ensure that you completed Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .For details about the scope of Integrations, Processes, and Visual Builder design-time metadata migrated, see About the Migration Scope .1.For the design-time metadata of the Oracle Integration Classic instance to export to Oracle Integration, invoke the REST API.This action asynchronously creates an archive that includes all above-mentioned objects.Headers Authorization : Basic Content-Type : application/json payload { "storageInfo": { "storageUrl": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to export all Integration and Process design time metadata to an Oracle Storage Cloud Service instance that you specify: curl -k -v -H "Content-Type: application/json" -X POST -d {"storageInfo":{"storageUrl":" https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo","storageUser":"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/exportServiceInstanceArchive where: storageInfo : Is the URL of the storage container.storageUser : Is the storage user name. |
ImportActivate : Imports and activates integrations and process applications.curl -k -v -H "Content-Type: application/json" -X POST -d {"archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04-e9b9e8374b68.zip", "importActivateMode": "ImportOnly", "storageInfo": { "storageUrl":"https:// swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo","storageUser" :"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/importServiceInstanceArchive Possible sample output from this command is as follows: { "jobId":"554", "status":"NOT_STARTED" }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-5Check the Design-Time Metadata Import Status Verify the design-time metadata import status after completing the import task.1.Check the status of the import operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ importServiceInstanceArchive/554 Possible sample output from this command is as follows.Other potential output includes RUNNING , COMPLETED , and FAILED .{ "jobId":"5108", "overallStatus":"RUNNING", "componentStatus":[ { "component":"Integration", "status":"RUNNING" } ] } { "jobId":"5108", "overall Status":"COMPLETED", "componentStatus":[ { "component":"Integration", "status":"COMPLETED", "percentage":100 } ] } 2.Log in to your Oracle Integration instance.3.Browse the pages and note that the design-time metadata you exported from your Oracle Integration Classic instance are now visible.For example, for Integrations, look for integrations, connections, lookups, and more.For Processes, look for process applications and decision models.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-6Export the Integration and Process Design-Time Metadata You must export the design-time metadata.Note: Before attempting to export design-time metadata, ensure that you completed Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .For details about the scope of Integrations, Processes, and Visual Builder design-time metadata migrated, see About the Migration Scope .1.For the design-time metadata of the Oracle Integration Classic instance to export to Oracle Integration, invoke the REST API.This action asynchronously creates an archive that includes all above-mentioned objects.Headers Authorization : Basic Content-Type : application/json payload { "storageInfo": { "storageUrl": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to export all Integration and Process design time metadata to an Oracle Storage Cloud Service instance that you specify: curl -k -v -H "Content-Type: application/json" -X POST -d {"storageInfo":{"storageUrl":" https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo","storageUser":"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/exportServiceInstanceArchive where: storageInfo : Is the URL of the storage container.storageUser : Is the storage user name.storagePassword : Is the storage password.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-7You specified these details when creating the object storage bucket. |
curl -k -v -H "Content-Type: application/json" -X POST -d {"archiveFile": "archive_Local_Suite_Instance-67e7358b-077b-420f-9e04-e9b9e8374b68.zip", "importActivateMode": "ImportOnly", "storageInfo": { "storageUrl":"https:// swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/ cloneRepo","storageUser" :"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/importServiceInstanceArchive Possible sample output from this command is as follows: { "jobId":"554", "status":"NOT_STARTED" }Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-5Check the Design-Time Metadata Import Status Verify the design-time metadata import status after completing the import task.1.Check the status of the import operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ importServiceInstanceArchive/554 Possible sample output from this command is as follows.Other potential output includes RUNNING , COMPLETED , and FAILED .{ "jobId":"5108", "overallStatus":"RUNNING", "componentStatus":[ { "component":"Integration", "status":"RUNNING" } ] } { "jobId":"5108", "overall Status":"COMPLETED", "componentStatus":[ { "component":"Integration", "status":"COMPLETED", "percentage":100 } ] } 2.Log in to your Oracle Integration instance.3.Browse the pages and note that the design-time metadata you exported from your Oracle Integration Classic instance are now visible.For example, for Integrations, look for integrations, connections, lookups, and more.For Processes, look for process applications and decision models.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-6Export the Integration and Process Design-Time Metadata You must export the design-time metadata.Note: Before attempting to export design-time metadata, ensure that you completed Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .For details about the scope of Integrations, Processes, and Visual Builder design-time metadata migrated, see About the Migration Scope .1.For the design-time metadata of the Oracle Integration Classic instance to export to Oracle Integration, invoke the REST API.This action asynchronously creates an archive that includes all above-mentioned objects.Headers Authorization : Basic Content-Type : application/json payload { "storageInfo": { "storageUrl": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to export all Integration and Process design time metadata to an Oracle Storage Cloud Service instance that you specify: curl -k -v -H "Content-Type: application/json" -X POST -d {"storageInfo":{"storageUrl":" https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo","storageUser":"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/exportServiceInstanceArchive where: storageInfo : Is the URL of the storage container.storageUser : Is the storage user name.storagePassword : Is the storage password.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-7You specified these details when creating the object storage bucket.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) . |
1.Check the status of the import operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ importServiceInstanceArchive/554 Possible sample output from this command is as follows.Other potential output includes RUNNING , COMPLETED , and FAILED .{ "jobId":"5108", "overallStatus":"RUNNING", "componentStatus":[ { "component":"Integration", "status":"RUNNING" } ] } { "jobId":"5108", "overall Status":"COMPLETED", "componentStatus":[ { "component":"Integration", "status":"COMPLETED", "percentage":100 } ] } 2.Log in to your Oracle Integration instance.3.Browse the pages and note that the design-time metadata you exported from your Oracle Integration Classic instance are now visible.For example, for Integrations, look for integrations, connections, lookups, and more.For Processes, look for process applications and decision models.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-6Export the Integration and Process Design-Time Metadata You must export the design-time metadata.Note: Before attempting to export design-time metadata, ensure that you completed Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .For details about the scope of Integrations, Processes, and Visual Builder design-time metadata migrated, see About the Migration Scope .1.For the design-time metadata of the Oracle Integration Classic instance to export to Oracle Integration, invoke the REST API.This action asynchronously creates an archive that includes all above-mentioned objects.Headers Authorization : Basic Content-Type : application/json payload { "storageInfo": { "storageUrl": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to export all Integration and Process design time metadata to an Oracle Storage Cloud Service instance that you specify: curl -k -v -H "Content-Type: application/json" -X POST -d {"storageInfo":{"storageUrl":" https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo","storageUser":"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/exportServiceInstanceArchive where: storageInfo : Is the URL of the storage container.storageUser : Is the storage user name.storagePassword : Is the storage password.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-7You specified these details when creating the object storage bucket.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Possible sample output from this command is as follows: { "archiveFilename": "archive_Local_Suite_Instance-d1e4295f- e17a-498a-a96e-44dcb417dfb4.zip", "jobID": "d1e4295f-e17a-498a-a96e-44dcb417dfb4", "location": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/cloneRepo", "status": "Starting" 2.Check the status of the export operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ exportServiceInstanceArchive/{jobId} Possible sample output from this command is as follows: { "status": "COMPLETED" } The archive is created in the Oracle Storage Cloud Service instance of Oracle Integration. |
Other potential output includes RUNNING , COMPLETED , and FAILED .{ "jobId":"5108", "overallStatus":"RUNNING", "componentStatus":[ { "component":"Integration", "status":"RUNNING" } ] } { "jobId":"5108", "overall Status":"COMPLETED", "componentStatus":[ { "component":"Integration", "status":"COMPLETED", "percentage":100 } ] } 2.Log in to your Oracle Integration instance.3.Browse the pages and note that the design-time metadata you exported from your Oracle Integration Classic instance are now visible.For example, for Integrations, look for integrations, connections, lookups, and more.For Processes, look for process applications and decision models.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-6Export the Integration and Process Design-Time Metadata You must export the design-time metadata.Note: Before attempting to export design-time metadata, ensure that you completed Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .For details about the scope of Integrations, Processes, and Visual Builder design-time metadata migrated, see About the Migration Scope .1.For the design-time metadata of the Oracle Integration Classic instance to export to Oracle Integration, invoke the REST API.This action asynchronously creates an archive that includes all above-mentioned objects.Headers Authorization : Basic Content-Type : application/json payload { "storageInfo": { "storageUrl": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to export all Integration and Process design time metadata to an Oracle Storage Cloud Service instance that you specify: curl -k -v -H "Content-Type: application/json" -X POST -d {"storageInfo":{"storageUrl":" https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo","storageUser":"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/exportServiceInstanceArchive where: storageInfo : Is the URL of the storage container.storageUser : Is the storage user name.storagePassword : Is the storage password.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-7You specified these details when creating the object storage bucket.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Possible sample output from this command is as follows: { "archiveFilename": "archive_Local_Suite_Instance-d1e4295f- e17a-498a-a96e-44dcb417dfb4.zip", "jobID": "d1e4295f-e17a-498a-a96e-44dcb417dfb4", "location": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/cloneRepo", "status": "Starting" 2.Check the status of the export operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ exportServiceInstanceArchive/{jobId} Possible sample output from this command is as follows: { "status": "COMPLETED" } The archive is created in the Oracle Storage Cloud Service instance of Oracle Integration.3.If the status is completed, you are now ready to import the archive.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-8Oracle Cloud Using the IBM DB2 Adapter with Oracle Integration Generation 2 E85529-23 November 2023 Oracle Cloud Using the IBM DB2 Adapter with Oracle Integration Generation 2, E85529-23 Copyright 2017, 2023, Oracle and/or its affiliates. |
{ "jobId":"5108", "overallStatus":"RUNNING", "componentStatus":[ { "component":"Integration", "status":"RUNNING" } ] } { "jobId":"5108", "overall Status":"COMPLETED", "componentStatus":[ { "component":"Integration", "status":"COMPLETED", "percentage":100 } ] } 2.Log in to your Oracle Integration instance.3.Browse the pages and note that the design-time metadata you exported from your Oracle Integration Classic instance are now visible.For example, for Integrations, look for integrations, connections, lookups, and more.For Processes, look for process applications and decision models.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-6Export the Integration and Process Design-Time Metadata You must export the design-time metadata.Note: Before attempting to export design-time metadata, ensure that you completed Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .For details about the scope of Integrations, Processes, and Visual Builder design-time metadata migrated, see About the Migration Scope .1.For the design-time metadata of the Oracle Integration Classic instance to export to Oracle Integration, invoke the REST API.This action asynchronously creates an archive that includes all above-mentioned objects.Headers Authorization : Basic Content-Type : application/json payload { "storageInfo": { "storageUrl": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to export all Integration and Process design time metadata to an Oracle Storage Cloud Service instance that you specify: curl -k -v -H "Content-Type: application/json" -X POST -d {"storageInfo":{"storageUrl":" https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo","storageUser":"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/exportServiceInstanceArchive where: storageInfo : Is the URL of the storage container.storageUser : Is the storage user name.storagePassword : Is the storage password.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-7You specified these details when creating the object storage bucket.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Possible sample output from this command is as follows: { "archiveFilename": "archive_Local_Suite_Instance-d1e4295f- e17a-498a-a96e-44dcb417dfb4.zip", "jobID": "d1e4295f-e17a-498a-a96e-44dcb417dfb4", "location": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/cloneRepo", "status": "Starting" 2.Check the status of the export operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ exportServiceInstanceArchive/{jobId} Possible sample output from this command is as follows: { "status": "COMPLETED" } The archive is created in the Oracle Storage Cloud Service instance of Oracle Integration.3.If the status is completed, you are now ready to import the archive.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-8Oracle Cloud Using the IBM DB2 Adapter with Oracle Integration Generation 2 E85529-23 November 2023 Oracle Cloud Using the IBM DB2 Adapter with Oracle Integration Generation 2, E85529-23 Copyright 2017, 2023, 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. |
3.Browse the pages and note that the design-time metadata you exported from your Oracle Integration Classic instance are now visible.For example, for Integrations, look for integrations, connections, lookups, and more.For Processes, look for process applications and decision models.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-6Export the Integration and Process Design-Time Metadata You must export the design-time metadata.Note: Before attempting to export design-time metadata, ensure that you completed Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .For details about the scope of Integrations, Processes, and Visual Builder design-time metadata migrated, see About the Migration Scope .1.For the design-time metadata of the Oracle Integration Classic instance to export to Oracle Integration, invoke the REST API.This action asynchronously creates an archive that includes all above-mentioned objects.Headers Authorization : Basic Content-Type : application/json payload { "storageInfo": { "storageUrl": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to export all Integration and Process design time metadata to an Oracle Storage Cloud Service instance that you specify: curl -k -v -H "Content-Type: application/json" -X POST -d {"storageInfo":{"storageUrl":" https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo","storageUser":"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/exportServiceInstanceArchive where: storageInfo : Is the URL of the storage container.storageUser : Is the storage user name.storagePassword : Is the storage password.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-7You specified these details when creating the object storage bucket.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Possible sample output from this command is as follows: { "archiveFilename": "archive_Local_Suite_Instance-d1e4295f- e17a-498a-a96e-44dcb417dfb4.zip", "jobID": "d1e4295f-e17a-498a-a96e-44dcb417dfb4", "location": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/cloneRepo", "status": "Starting" 2.Check the status of the export operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ exportServiceInstanceArchive/{jobId} Possible sample output from this command is as follows: { "status": "COMPLETED" } The archive is created in the Oracle Storage Cloud Service instance of Oracle Integration.3.If the status is completed, you are now ready to import the archive.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-8Oracle Cloud Using the IBM DB2 Adapter with Oracle Integration Generation 2 E85529-23 November 2023 Oracle Cloud Using the IBM DB2 Adapter with Oracle Integration Generation 2, E85529-23 Copyright 2017, 2023, 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. |
For example, for Integrations, look for integrations, connections, lookups, and more.For Processes, look for process applications and decision models.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-6Export the Integration and Process Design-Time Metadata You must export the design-time metadata.Note: Before attempting to export design-time metadata, ensure that you completed Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .For details about the scope of Integrations, Processes, and Visual Builder design-time metadata migrated, see About the Migration Scope .1.For the design-time metadata of the Oracle Integration Classic instance to export to Oracle Integration, invoke the REST API.This action asynchronously creates an archive that includes all above-mentioned objects.Headers Authorization : Basic Content-Type : application/json payload { "storageInfo": { "storageUrl": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to export all Integration and Process design time metadata to an Oracle Storage Cloud Service instance that you specify: curl -k -v -H "Content-Type: application/json" -X POST -d {"storageInfo":{"storageUrl":" https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo","storageUser":"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/exportServiceInstanceArchive where: storageInfo : Is the URL of the storage container.storageUser : Is the storage user name.storagePassword : Is the storage password.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-7You specified these details when creating the object storage bucket.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Possible sample output from this command is as follows: { "archiveFilename": "archive_Local_Suite_Instance-d1e4295f- e17a-498a-a96e-44dcb417dfb4.zip", "jobID": "d1e4295f-e17a-498a-a96e-44dcb417dfb4", "location": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/cloneRepo", "status": "Starting" 2.Check the status of the export operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ exportServiceInstanceArchive/{jobId} Possible sample output from this command is as follows: { "status": "COMPLETED" } The archive is created in the Oracle Storage Cloud Service instance of Oracle Integration.3.If the status is completed, you are now ready to import the archive.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-8Oracle Cloud Using the IBM DB2 Adapter with Oracle Integration Generation 2 E85529-23 November 2023 Oracle Cloud Using the IBM DB2 Adapter with Oracle Integration Generation 2, E85529-23 Copyright 2017, 2023, 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. |
For Processes, look for process applications and decision models.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-6Export the Integration and Process Design-Time Metadata You must export the design-time metadata.Note: Before attempting to export design-time metadata, ensure that you completed Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .For details about the scope of Integrations, Processes, and Visual Builder design-time metadata migrated, see About the Migration Scope .1.For the design-time metadata of the Oracle Integration Classic instance to export to Oracle Integration, invoke the REST API.This action asynchronously creates an archive that includes all above-mentioned objects.Headers Authorization : Basic Content-Type : application/json payload { "storageInfo": { "storageUrl": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to export all Integration and Process design time metadata to an Oracle Storage Cloud Service instance that you specify: curl -k -v -H "Content-Type: application/json" -X POST -d {"storageInfo":{"storageUrl":" https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo","storageUser":"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/exportServiceInstanceArchive where: storageInfo : Is the URL of the storage container.storageUser : Is the storage user name.storagePassword : Is the storage password.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-7You specified these details when creating the object storage bucket.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Possible sample output from this command is as follows: { "archiveFilename": "archive_Local_Suite_Instance-d1e4295f- e17a-498a-a96e-44dcb417dfb4.zip", "jobID": "d1e4295f-e17a-498a-a96e-44dcb417dfb4", "location": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/cloneRepo", "status": "Starting" 2.Check the status of the export operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ exportServiceInstanceArchive/{jobId} Possible sample output from this command is as follows: { "status": "COMPLETED" } The archive is created in the Oracle Storage Cloud Service instance of Oracle Integration.3.If the status is completed, you are now ready to import the archive.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-8Oracle Cloud Using the IBM DB2 Adapter with Oracle Integration Generation 2 E85529-23 November 2023 Oracle Cloud Using the IBM DB2 Adapter with Oracle Integration Generation 2, E85529-23 Copyright 2017, 2023, 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. |
Note: Before attempting to export design-time metadata, ensure that you completed Step 1: Create a Cloud Storage Compartment or Use an Existing Compartment through Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .For details about the scope of Integrations, Processes, and Visual Builder design-time metadata migrated, see About the Migration Scope .1.For the design-time metadata of the Oracle Integration Classic instance to export to Oracle Integration, invoke the REST API.This action asynchronously creates an archive that includes all above-mentioned objects.Headers Authorization : Basic Content-Type : application/json payload { "storageInfo": { "storageUrl": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to export all Integration and Process design time metadata to an Oracle Storage Cloud Service instance that you specify: curl -k -v -H "Content-Type: application/json" -X POST -d {"storageInfo":{"storageUrl":" https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo","storageUser":"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/exportServiceInstanceArchive where: storageInfo : Is the URL of the storage container.storageUser : Is the storage user name.storagePassword : Is the storage password.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-7You specified these details when creating the object storage bucket.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Possible sample output from this command is as follows: { "archiveFilename": "archive_Local_Suite_Instance-d1e4295f- e17a-498a-a96e-44dcb417dfb4.zip", "jobID": "d1e4295f-e17a-498a-a96e-44dcb417dfb4", "location": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/cloneRepo", "status": "Starting" 2.Check the status of the export operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ exportServiceInstanceArchive/{jobId} Possible sample output from this command is as follows: { "status": "COMPLETED" } The archive is created in the Oracle Storage Cloud Service instance of Oracle Integration.3.If the status is completed, you are now ready to import the archive.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-8Oracle Cloud Using the IBM DB2 Adapter with Oracle Integration Generation 2 E85529-23 November 2023 Oracle Cloud Using the IBM DB2 Adapter with Oracle Integration Generation 2, E85529-23 Copyright 2017, 2023, 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. |
For details about the scope of Integrations, Processes, and Visual Builder design-time metadata migrated, see About the Migration Scope .1.For the design-time metadata of the Oracle Integration Classic instance to export to Oracle Integration, invoke the REST API.This action asynchronously creates an archive that includes all above-mentioned objects.Headers Authorization : Basic Content-Type : application/json payload { "storageInfo": { "storageUrl": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to export all Integration and Process design time metadata to an Oracle Storage Cloud Service instance that you specify: curl -k -v -H "Content-Type: application/json" -X POST -d {"storageInfo":{"storageUrl":" https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo","storageUser":"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/exportServiceInstanceArchive where: storageInfo : Is the URL of the storage container.storageUser : Is the storage user name.storagePassword : Is the storage password.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-7You specified these details when creating the object storage bucket.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Possible sample output from this command is as follows: { "archiveFilename": "archive_Local_Suite_Instance-d1e4295f- e17a-498a-a96e-44dcb417dfb4.zip", "jobID": "d1e4295f-e17a-498a-a96e-44dcb417dfb4", "location": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/cloneRepo", "status": "Starting" 2.Check the status of the export operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ exportServiceInstanceArchive/{jobId} Possible sample output from this command is as follows: { "status": "COMPLETED" } The archive is created in the Oracle Storage Cloud Service instance of Oracle Integration.3.If the status is completed, you are now ready to import the archive.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-8Oracle Cloud Using the IBM DB2 Adapter with Oracle Integration Generation 2 E85529-23 November 2023 Oracle Cloud Using the IBM DB2 Adapter with Oracle Integration Generation 2, E85529-23 Copyright 2017, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. |
1.For the design-time metadata of the Oracle Integration Classic instance to export to Oracle Integration, invoke the REST API.This action asynchronously creates an archive that includes all above-mentioned objects.Headers Authorization : Basic Content-Type : application/json payload { "storageInfo": { "storageUrl": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to export all Integration and Process design time metadata to an Oracle Storage Cloud Service instance that you specify: curl -k -v -H "Content-Type: application/json" -X POST -d {"storageInfo":{"storageUrl":" https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo","storageUser":"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/exportServiceInstanceArchive where: storageInfo : Is the URL of the storage container.storageUser : Is the storage user name.storagePassword : Is the storage password.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-7You specified these details when creating the object storage bucket.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Possible sample output from this command is as follows: { "archiveFilename": "archive_Local_Suite_Instance-d1e4295f- e17a-498a-a96e-44dcb417dfb4.zip", "jobID": "d1e4295f-e17a-498a-a96e-44dcb417dfb4", "location": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/cloneRepo", "status": "Starting" 2.Check the status of the export operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ exportServiceInstanceArchive/{jobId} Possible sample output from this command is as follows: { "status": "COMPLETED" } The archive is created in the Oracle Storage Cloud Service instance of Oracle Integration.3.If the status is completed, you are now ready to import the archive.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-8Oracle Cloud Using the IBM DB2 Adapter with Oracle Integration Generation 2 E85529-23 November 2023 Oracle Cloud Using the IBM DB2 Adapter with Oracle Integration Generation 2, E85529-23 Copyright 2017, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. |
This action asynchronously creates an archive that includes all above-mentioned objects.Headers Authorization : Basic Content-Type : application/json payload { "storageInfo": { "storageUrl": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo", "storageUser":"[email protected]", "storagePassword":" generated_token " } } For example, use a postman or curl (as shown below) command to export all Integration and Process design time metadata to an Oracle Storage Cloud Service instance that you specify: curl -k -v -H "Content-Type: application/json" -X POST -d {"storageInfo":{"storageUrl":" https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/ paasdevoic/cloneRepo","storageUser":"[email protected]", "storagePassword":" generated_token "}} -u admin:password https://host/ic/api/common/v1/exportServiceInstanceArchive where: storageInfo : Is the URL of the storage container.storageUser : Is the storage user name.storagePassword : Is the storage password.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-7You specified these details when creating the object storage bucket.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .Possible sample output from this command is as follows: { "archiveFilename": "archive_Local_Suite_Instance-d1e4295f- e17a-498a-a96e-44dcb417dfb4.zip", "jobID": "d1e4295f-e17a-498a-a96e-44dcb417dfb4", "location": "https://swiftobjectstorage.us- region -1.oraclecloud.com/v1/paasdevoic/cloneRepo", "status": "Starting" 2.Check the status of the export operation using a postman or curl (as shown below) command: curl -k -v -X GET -u admin: password https://host/ic/api/common/v1/ exportServiceInstanceArchive/{jobId} Possible sample output from this command is as follows: { "status": "COMPLETED" } The archive is created in the Oracle Storage Cloud Service instance of Oracle Integration.3.If the status is completed, you are now ready to import the archive.Appendix A Migrate Integration and Process Design-Time Metadata into Oracle Integration A-8Oracle Cloud Using the IBM DB2 Adapter with Oracle Integration Generation 2 E85529-23 November 2023 Oracle Cloud Using the IBM DB2 Adapter with Oracle Integration Generation 2, E85529-23 Copyright 2017, 2023, Oracle and/or its affiliates.Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws.Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.