text
stringlengths 65
20k
|
|---|
2.Click Import on the Visual Applications home page.3.Click Application from GIT in the Import dialog box.4.Click Add Credentials in the Import Application from GIT dialog box.5.Enter the URL, username and password for your Oracle Developer Cloud Service account.Click Save Credentials .After your credentials are checked and saved, the new credentials are added to the list in the Configure DevCS Credentials dialog box.6.Select the URL of your account in the DevCS URL with Credentials field.7.Select the project, repository and branch of the application's sources.8.Enter a valid application name and ID.Click Import .After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-174 Complete the Post-Migration Tasks After successfully migrating your Oracle Integration Classic instances to Oracle Cloud Infrastructure, test your integrations thoroughly, and then perform cleanup and other optional configuration tasks.Topics: Verify Your Environment and Activate Your Integrations Complete Post-Migration Tasks for Processes Complete Post-Migration Tasks for Visual Builder Applications Verify Your Environment and Activate Your Integrations After Integrations migration to Oracle Integration is complete, perform the following post- migration tasks.1.Verify your integrations (for example, check the connections, lookups, and more).2.Activate your integrations (if you did not do so automatically during the import process). |
3.Click Application from GIT in the Import dialog box.4.Click Add Credentials in the Import Application from GIT dialog box.5.Enter the URL, username and password for your Oracle Developer Cloud Service account.Click Save Credentials .After your credentials are checked and saved, the new credentials are added to the list in the Configure DevCS Credentials dialog box.6.Select the URL of your account in the DevCS URL with Credentials field.7.Select the project, repository and branch of the application's sources.8.Enter a valid application name and ID.Click Import .After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-174 Complete the Post-Migration Tasks After successfully migrating your Oracle Integration Classic instances to Oracle Cloud Infrastructure, test your integrations thoroughly, and then perform cleanup and other optional configuration tasks.Topics: Verify Your Environment and Activate Your Integrations Complete Post-Migration Tasks for Processes Complete Post-Migration Tasks for Visual Builder Applications Verify Your Environment and Activate Your Integrations After Integrations migration to Oracle Integration is complete, perform the following post- migration tasks.1.Verify your integrations (for example, check the connections, lookups, and more).2.Activate your integrations (if you did not do so automatically during the import process).Complete Post-Migration Tasks for Processes After verifying and activating integrations, complete Processes tasks. |
4.Click Add Credentials in the Import Application from GIT dialog box.5.Enter the URL, username and password for your Oracle Developer Cloud Service account.Click Save Credentials .After your credentials are checked and saved, the new credentials are added to the list in the Configure DevCS Credentials dialog box.6.Select the URL of your account in the DevCS URL with Credentials field.7.Select the project, repository and branch of the application's sources.8.Enter a valid application name and ID.Click Import .After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-174 Complete the Post-Migration Tasks After successfully migrating your Oracle Integration Classic instances to Oracle Cloud Infrastructure, test your integrations thoroughly, and then perform cleanup and other optional configuration tasks.Topics: Verify Your Environment and Activate Your Integrations Complete Post-Migration Tasks for Processes Complete Post-Migration Tasks for Visual Builder Applications Verify Your Environment and Activate Your Integrations After Integrations migration to Oracle Integration is complete, perform the following post- migration tasks.1.Verify your integrations (for example, check the connections, lookups, and more).2.Activate your integrations (if you did not do so automatically during the import process).Complete Post-Migration Tasks for Processes After verifying and activating integrations, complete Processes tasks.Topics: Perform Post Import Steps for Processes Handle In-Flight Process Instances Follow Migration Best Practices for Processes Perform Post Import Steps for Processes After import, perform additional Processes steps as needed. |
5.Enter the URL, username and password for your Oracle Developer Cloud Service account.Click Save Credentials .After your credentials are checked and saved, the new credentials are added to the list in the Configure DevCS Credentials dialog box.6.Select the URL of your account in the DevCS URL with Credentials field.7.Select the project, repository and branch of the application's sources.8.Enter a valid application name and ID.Click Import .After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-174 Complete the Post-Migration Tasks After successfully migrating your Oracle Integration Classic instances to Oracle Cloud Infrastructure, test your integrations thoroughly, and then perform cleanup and other optional configuration tasks.Topics: Verify Your Environment and Activate Your Integrations Complete Post-Migration Tasks for Processes Complete Post-Migration Tasks for Visual Builder Applications Verify Your Environment and Activate Your Integrations After Integrations migration to Oracle Integration is complete, perform the following post- migration tasks.1.Verify your integrations (for example, check the connections, lookups, and more).2.Activate your integrations (if you did not do so automatically during the import process).Complete Post-Migration Tasks for Processes After verifying and activating integrations, complete Processes tasks.Topics: Perform Post Import Steps for Processes Handle In-Flight Process Instances Follow Migration Best Practices for Processes Perform Post Import Steps for Processes After import, perform additional Processes steps as needed.1.In Oracle Cloud Infrastructure, manually reconfigure any federated SSO configurations for Processes that were configured in Oracle Integration Classic. |
Click Save Credentials .After your credentials are checked and saved, the new credentials are added to the list in the Configure DevCS Credentials dialog box.6.Select the URL of your account in the DevCS URL with Credentials field.7.Select the project, repository and branch of the application's sources.8.Enter a valid application name and ID.Click Import .After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-174 Complete the Post-Migration Tasks After successfully migrating your Oracle Integration Classic instances to Oracle Cloud Infrastructure, test your integrations thoroughly, and then perform cleanup and other optional configuration tasks.Topics: Verify Your Environment and Activate Your Integrations Complete Post-Migration Tasks for Processes Complete Post-Migration Tasks for Visual Builder Applications Verify Your Environment and Activate Your Integrations After Integrations migration to Oracle Integration is complete, perform the following post- migration tasks.1.Verify your integrations (for example, check the connections, lookups, and more).2.Activate your integrations (if you did not do so automatically during the import process).Complete Post-Migration Tasks for Processes After verifying and activating integrations, complete Processes tasks.Topics: Perform Post Import Steps for Processes Handle In-Flight Process Instances Follow Migration Best Practices for Processes Perform Post Import Steps for Processes After import, perform additional Processes steps as needed.1.In Oracle Cloud Infrastructure, manually reconfigure any federated SSO configurations for Processes that were configured in Oracle Integration Classic.2.If you configured OAuth to work in Oracle Integration Classic for Processes, manually reconfigure it in Oracle Cloud Infrastructure. |
After your credentials are checked and saved, the new credentials are added to the list in the Configure DevCS Credentials dialog box.6.Select the URL of your account in the DevCS URL with Credentials field.7.Select the project, repository and branch of the application's sources.8.Enter a valid application name and ID.Click Import .After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-174 Complete the Post-Migration Tasks After successfully migrating your Oracle Integration Classic instances to Oracle Cloud Infrastructure, test your integrations thoroughly, and then perform cleanup and other optional configuration tasks.Topics: Verify Your Environment and Activate Your Integrations Complete Post-Migration Tasks for Processes Complete Post-Migration Tasks for Visual Builder Applications Verify Your Environment and Activate Your Integrations After Integrations migration to Oracle Integration is complete, perform the following post- migration tasks.1.Verify your integrations (for example, check the connections, lookups, and more).2.Activate your integrations (if you did not do so automatically during the import process).Complete Post-Migration Tasks for Processes After verifying and activating integrations, complete Processes tasks.Topics: Perform Post Import Steps for Processes Handle In-Flight Process Instances Follow Migration Best Practices for Processes Perform Post Import Steps for Processes After import, perform additional Processes steps as needed.1.In Oracle Cloud Infrastructure, manually reconfigure any federated SSO configurations for Processes that were configured in Oracle Integration Classic.2.If you configured OAuth to work in Oracle Integration Classic for Processes, manually reconfigure it in Oracle Cloud Infrastructure.See Security, Authentication, and Authorization in REST API for Oracle Integration . |
6.Select the URL of your account in the DevCS URL with Credentials field.7.Select the project, repository and branch of the application's sources.8.Enter a valid application name and ID.Click Import .After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-174 Complete the Post-Migration Tasks After successfully migrating your Oracle Integration Classic instances to Oracle Cloud Infrastructure, test your integrations thoroughly, and then perform cleanup and other optional configuration tasks.Topics: Verify Your Environment and Activate Your Integrations Complete Post-Migration Tasks for Processes Complete Post-Migration Tasks for Visual Builder Applications Verify Your Environment and Activate Your Integrations After Integrations migration to Oracle Integration is complete, perform the following post- migration tasks.1.Verify your integrations (for example, check the connections, lookups, and more).2.Activate your integrations (if you did not do so automatically during the import process).Complete Post-Migration Tasks for Processes After verifying and activating integrations, complete Processes tasks.Topics: Perform Post Import Steps for Processes Handle In-Flight Process Instances Follow Migration Best Practices for Processes Perform Post Import Steps for Processes After import, perform additional Processes steps as needed.1.In Oracle Cloud Infrastructure, manually reconfigure any federated SSO configurations for Processes that were configured in Oracle Integration Classic.2.If you configured OAuth to work in Oracle Integration Classic for Processes, manually reconfigure it in Oracle Cloud Infrastructure.See Security, Authentication, and Authorization in REST API for Oracle Integration .3.In runtime administration, configure supporting services and settings, as needed. |
7.Select the project, repository and branch of the application's sources.8.Enter a valid application name and ID.Click Import .After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-174 Complete the Post-Migration Tasks After successfully migrating your Oracle Integration Classic instances to Oracle Cloud Infrastructure, test your integrations thoroughly, and then perform cleanup and other optional configuration tasks.Topics: Verify Your Environment and Activate Your Integrations Complete Post-Migration Tasks for Processes Complete Post-Migration Tasks for Visual Builder Applications Verify Your Environment and Activate Your Integrations After Integrations migration to Oracle Integration is complete, perform the following post- migration tasks.1.Verify your integrations (for example, check the connections, lookups, and more).2.Activate your integrations (if you did not do so automatically during the import process).Complete Post-Migration Tasks for Processes After verifying and activating integrations, complete Processes tasks.Topics: Perform Post Import Steps for Processes Handle In-Flight Process Instances Follow Migration Best Practices for Processes Perform Post Import Steps for Processes After import, perform additional Processes steps as needed.1.In Oracle Cloud Infrastructure, manually reconfigure any federated SSO configurations for Processes that were configured in Oracle Integration Classic.2.If you configured OAuth to work in Oracle Integration Classic for Processes, manually reconfigure it in Oracle Cloud Infrastructure.See Security, Authentication, and Authorization in REST API for Oracle Integration .3.In runtime administration, configure supporting services and settings, as needed.On the Oracle Integration Home page, select My Tasks in the navigation pane, then Workspace . |
8.Enter a valid application name and ID.Click Import .After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-174 Complete the Post-Migration Tasks After successfully migrating your Oracle Integration Classic instances to Oracle Cloud Infrastructure, test your integrations thoroughly, and then perform cleanup and other optional configuration tasks.Topics: Verify Your Environment and Activate Your Integrations Complete Post-Migration Tasks for Processes Complete Post-Migration Tasks for Visual Builder Applications Verify Your Environment and Activate Your Integrations After Integrations migration to Oracle Integration is complete, perform the following post- migration tasks.1.Verify your integrations (for example, check the connections, lookups, and more).2.Activate your integrations (if you did not do so automatically during the import process).Complete Post-Migration Tasks for Processes After verifying and activating integrations, complete Processes tasks.Topics: Perform Post Import Steps for Processes Handle In-Flight Process Instances Follow Migration Best Practices for Processes Perform Post Import Steps for Processes After import, perform additional Processes steps as needed.1.In Oracle Cloud Infrastructure, manually reconfigure any federated SSO configurations for Processes that were configured in Oracle Integration Classic.2.If you configured OAuth to work in Oracle Integration Classic for Processes, manually reconfigure it in Oracle Cloud Infrastructure.See Security, Authentication, and Authorization in REST API for Oracle Integration .3.In runtime administration, configure supporting services and settings, as needed.On the Oracle Integration Home page, select My Tasks in the navigation pane, then Workspace .In the My Tasks navigation pane, select Administration . |
Click Import .After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-174 Complete the Post-Migration Tasks After successfully migrating your Oracle Integration Classic instances to Oracle Cloud Infrastructure, test your integrations thoroughly, and then perform cleanup and other optional configuration tasks.Topics: Verify Your Environment and Activate Your Integrations Complete Post-Migration Tasks for Processes Complete Post-Migration Tasks for Visual Builder Applications Verify Your Environment and Activate Your Integrations After Integrations migration to Oracle Integration is complete, perform the following post- migration tasks.1.Verify your integrations (for example, check the connections, lookups, and more).2.Activate your integrations (if you did not do so automatically during the import process).Complete Post-Migration Tasks for Processes After verifying and activating integrations, complete Processes tasks.Topics: Perform Post Import Steps for Processes Handle In-Flight Process Instances Follow Migration Best Practices for Processes Perform Post Import Steps for Processes After import, perform additional Processes steps as needed.1.In Oracle Cloud Infrastructure, manually reconfigure any federated SSO configurations for Processes that were configured in Oracle Integration Classic.2.If you configured OAuth to work in Oracle Integration Classic for Processes, manually reconfigure it in Oracle Cloud Infrastructure.See Security, Authentication, and Authorization in REST API for Oracle Integration .3.In runtime administration, configure supporting services and settings, as needed.On the Oracle Integration Home page, select My Tasks in the navigation pane, then Workspace .In the My Tasks navigation pane, select Administration .4.IMPORTANT: Under Archive and Purge , configure purge and archive settings for process instances and analytics data. |
After you import a visual application, you might need to provide additional details such as credential to service in the new copy of the application.For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-174 Complete the Post-Migration Tasks After successfully migrating your Oracle Integration Classic instances to Oracle Cloud Infrastructure, test your integrations thoroughly, and then perform cleanup and other optional configuration tasks.Topics: Verify Your Environment and Activate Your Integrations Complete Post-Migration Tasks for Processes Complete Post-Migration Tasks for Visual Builder Applications Verify Your Environment and Activate Your Integrations After Integrations migration to Oracle Integration is complete, perform the following post- migration tasks.1.Verify your integrations (for example, check the connections, lookups, and more).2.Activate your integrations (if you did not do so automatically during the import process).Complete Post-Migration Tasks for Processes After verifying and activating integrations, complete Processes tasks.Topics: Perform Post Import Steps for Processes Handle In-Flight Process Instances Follow Migration Best Practices for Processes Perform Post Import Steps for Processes After import, perform additional Processes steps as needed.1.In Oracle Cloud Infrastructure, manually reconfigure any federated SSO configurations for Processes that were configured in Oracle Integration Classic.2.If you configured OAuth to work in Oracle Integration Classic for Processes, manually reconfigure it in Oracle Cloud Infrastructure.See Security, Authentication, and Authorization in REST API for Oracle Integration .3.In runtime administration, configure supporting services and settings, as needed.On the Oracle Integration Home page, select My Tasks in the navigation pane, then Workspace .In the My Tasks navigation pane, select Administration .4.IMPORTANT: Under Archive and Purge , configure purge and archive settings for process instances and analytics data.4-1Be sure to verify the retention policies set to purge unused information. |
For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.Chapter 3 Step 5: Migrate Your Visual Builder Design-Time Metadata 3-174 Complete the Post-Migration Tasks After successfully migrating your Oracle Integration Classic instances to Oracle Cloud Infrastructure, test your integrations thoroughly, and then perform cleanup and other optional configuration tasks.Topics: Verify Your Environment and Activate Your Integrations Complete Post-Migration Tasks for Processes Complete Post-Migration Tasks for Visual Builder Applications Verify Your Environment and Activate Your Integrations After Integrations migration to Oracle Integration is complete, perform the following post- migration tasks.1.Verify your integrations (for example, check the connections, lookups, and more).2.Activate your integrations (if you did not do so automatically during the import process).Complete Post-Migration Tasks for Processes After verifying and activating integrations, complete Processes tasks.Topics: Perform Post Import Steps for Processes Handle In-Flight Process Instances Follow Migration Best Practices for Processes Perform Post Import Steps for Processes After import, perform additional Processes steps as needed.1.In Oracle Cloud Infrastructure, manually reconfigure any federated SSO configurations for Processes that were configured in Oracle Integration Classic.2.If you configured OAuth to work in Oracle Integration Classic for Processes, manually reconfigure it in Oracle Cloud Infrastructure.See Security, Authentication, and Authorization in REST API for Oracle Integration .3.In runtime administration, configure supporting services and settings, as needed.On the Oracle Integration Home page, select My Tasks in the navigation pane, then Workspace .In the My Tasks navigation pane, select Administration .4.IMPORTANT: Under Archive and Purge , configure purge and archive settings for process instances and analytics data.4-1Be sure to verify the retention policies set to purge unused information.Set the Purge Retention (Days) setting on the Schedule Instances Archive tab to the number of days to retain completed process instances before they get purged. |
Topics: Verify Your Environment and Activate Your Integrations Complete Post-Migration Tasks for Processes Complete Post-Migration Tasks for Visual Builder Applications Verify Your Environment and Activate Your Integrations After Integrations migration to Oracle Integration is complete, perform the following post- migration tasks.1.Verify your integrations (for example, check the connections, lookups, and more).2.Activate your integrations (if you did not do so automatically during the import process).Complete Post-Migration Tasks for Processes After verifying and activating integrations, complete Processes tasks.Topics: Perform Post Import Steps for Processes Handle In-Flight Process Instances Follow Migration Best Practices for Processes Perform Post Import Steps for Processes After import, perform additional Processes steps as needed.1.In Oracle Cloud Infrastructure, manually reconfigure any federated SSO configurations for Processes that were configured in Oracle Integration Classic.2.If you configured OAuth to work in Oracle Integration Classic for Processes, manually reconfigure it in Oracle Cloud Infrastructure.See Security, Authentication, and Authorization in REST API for Oracle Integration .3.In runtime administration, configure supporting services and settings, as needed.On the Oracle Integration Home page, select My Tasks in the navigation pane, then Workspace .In the My Tasks navigation pane, select Administration .4.IMPORTANT: Under Archive and Purge , configure purge and archive settings for process instances and analytics data.4-1Be sure to verify the retention policies set to purge unused information.Set the Purge Retention (Days) setting on the Schedule Instances Archive tab to the number of days to retain completed process instances before they get purged.(Purged instances cannot be recovered.) |
1.Verify your integrations (for example, check the connections, lookups, and more).2.Activate your integrations (if you did not do so automatically during the import process).Complete Post-Migration Tasks for Processes After verifying and activating integrations, complete Processes tasks.Topics: Perform Post Import Steps for Processes Handle In-Flight Process Instances Follow Migration Best Practices for Processes Perform Post Import Steps for Processes After import, perform additional Processes steps as needed.1.In Oracle Cloud Infrastructure, manually reconfigure any federated SSO configurations for Processes that were configured in Oracle Integration Classic.2.If you configured OAuth to work in Oracle Integration Classic for Processes, manually reconfigure it in Oracle Cloud Infrastructure.See Security, Authentication, and Authorization in REST API for Oracle Integration .3.In runtime administration, configure supporting services and settings, as needed.On the Oracle Integration Home page, select My Tasks in the navigation pane, then Workspace .In the My Tasks navigation pane, select Administration .4.IMPORTANT: Under Archive and Purge , configure purge and archive settings for process instances and analytics data.4-1Be sure to verify the retention policies set to purge unused information.Set the Purge Retention (Days) setting on the Schedule Instances Archive tab to the number of days to retain completed process instances before they get purged.(Purged instances cannot be recovered.)Because increasing retention days increases database consumption,you must balance your organization's retention needs with database capacity. |
2.Activate your integrations (if you did not do so automatically during the import process).Complete Post-Migration Tasks for Processes After verifying and activating integrations, complete Processes tasks.Topics: Perform Post Import Steps for Processes Handle In-Flight Process Instances Follow Migration Best Practices for Processes Perform Post Import Steps for Processes After import, perform additional Processes steps as needed.1.In Oracle Cloud Infrastructure, manually reconfigure any federated SSO configurations for Processes that were configured in Oracle Integration Classic.2.If you configured OAuth to work in Oracle Integration Classic for Processes, manually reconfigure it in Oracle Cloud Infrastructure.See Security, Authentication, and Authorization in REST API for Oracle Integration .3.In runtime administration, configure supporting services and settings, as needed.On the Oracle Integration Home page, select My Tasks in the navigation pane, then Workspace .In the My Tasks navigation pane, select Administration .4.IMPORTANT: Under Archive and Purge , configure purge and archive settings for process instances and analytics data.4-1Be sure to verify the retention policies set to purge unused information.Set the Purge Retention (Days) setting on the Schedule Instances Archive tab to the number of days to retain completed process instances before they get purged.(Purged instances cannot be recovered.)Because increasing retention days increases database consumption,you must balance your organization's retention needs with database capacity.See Archive and Purge Data in Using Processes in Oracle Integration . |
Complete Post-Migration Tasks for Processes After verifying and activating integrations, complete Processes tasks.Topics: Perform Post Import Steps for Processes Handle In-Flight Process Instances Follow Migration Best Practices for Processes Perform Post Import Steps for Processes After import, perform additional Processes steps as needed.1.In Oracle Cloud Infrastructure, manually reconfigure any federated SSO configurations for Processes that were configured in Oracle Integration Classic.2.If you configured OAuth to work in Oracle Integration Classic for Processes, manually reconfigure it in Oracle Cloud Infrastructure.See Security, Authentication, and Authorization in REST API for Oracle Integration .3.In runtime administration, configure supporting services and settings, as needed.On the Oracle Integration Home page, select My Tasks in the navigation pane, then Workspace .In the My Tasks navigation pane, select Administration .4.IMPORTANT: Under Archive and Purge , configure purge and archive settings for process instances and analytics data.4-1Be sure to verify the retention policies set to purge unused information.Set the Purge Retention (Days) setting on the Schedule Instances Archive tab to the number of days to retain completed process instances before they get purged.(Purged instances cannot be recovered.)Because increasing retention days increases database consumption,you must balance your organization's retention needs with database capacity.See Archive and Purge Data in Using Processes in Oracle Integration .5.Under Services (Platform tab), configure Oracle Content and Experience settings if integrating documents in process applications. |
Topics: Perform Post Import Steps for Processes Handle In-Flight Process Instances Follow Migration Best Practices for Processes Perform Post Import Steps for Processes After import, perform additional Processes steps as needed.1.In Oracle Cloud Infrastructure, manually reconfigure any federated SSO configurations for Processes that were configured in Oracle Integration Classic.2.If you configured OAuth to work in Oracle Integration Classic for Processes, manually reconfigure it in Oracle Cloud Infrastructure.See Security, Authentication, and Authorization in REST API for Oracle Integration .3.In runtime administration, configure supporting services and settings, as needed.On the Oracle Integration Home page, select My Tasks in the navigation pane, then Workspace .In the My Tasks navigation pane, select Administration .4.IMPORTANT: Under Archive and Purge , configure purge and archive settings for process instances and analytics data.4-1Be sure to verify the retention policies set to purge unused information.Set the Purge Retention (Days) setting on the Schedule Instances Archive tab to the number of days to retain completed process instances before they get purged.(Purged instances cannot be recovered.)Because increasing retention days increases database consumption,you must balance your organization's retention needs with database capacity.See Archive and Purge Data in Using Processes in Oracle Integration .5.Under Services (Platform tab), configure Oracle Content and Experience settings if integrating documents in process applications.See How do I integrate with Oracle Content and Experience Cloud? |
1.In Oracle Cloud Infrastructure, manually reconfigure any federated SSO configurations for Processes that were configured in Oracle Integration Classic.2.If you configured OAuth to work in Oracle Integration Classic for Processes, manually reconfigure it in Oracle Cloud Infrastructure.See Security, Authentication, and Authorization in REST API for Oracle Integration .3.In runtime administration, configure supporting services and settings, as needed.On the Oracle Integration Home page, select My Tasks in the navigation pane, then Workspace .In the My Tasks navigation pane, select Administration .4.IMPORTANT: Under Archive and Purge , configure purge and archive settings for process instances and analytics data.4-1Be sure to verify the retention policies set to purge unused information.Set the Purge Retention (Days) setting on the Schedule Instances Archive tab to the number of days to retain completed process instances before they get purged.(Purged instances cannot be recovered.)Because increasing retention days increases database consumption,you must balance your organization's retention needs with database capacity.See Archive and Purge Data in Using Processes in Oracle Integration .5.Under Services (Platform tab), configure Oracle Content and Experience settings if integrating documents in process applications.See How do I integrate with Oracle Content and Experience Cloud?in Using Processes in Oracle Integration . |
2.If you configured OAuth to work in Oracle Integration Classic for Processes, manually reconfigure it in Oracle Cloud Infrastructure.See Security, Authentication, and Authorization in REST API for Oracle Integration .3.In runtime administration, configure supporting services and settings, as needed.On the Oracle Integration Home page, select My Tasks in the navigation pane, then Workspace .In the My Tasks navigation pane, select Administration .4.IMPORTANT: Under Archive and Purge , configure purge and archive settings for process instances and analytics data.4-1Be sure to verify the retention policies set to purge unused information.Set the Purge Retention (Days) setting on the Schedule Instances Archive tab to the number of days to retain completed process instances before they get purged.(Purged instances cannot be recovered.)Because increasing retention days increases database consumption,you must balance your organization's retention needs with database capacity.See Archive and Purge Data in Using Processes in Oracle Integration .5.Under Services (Platform tab), configure Oracle Content and Experience settings if integrating documents in process applications.See How do I integrate with Oracle Content and Experience Cloud?in Using Processes in Oracle Integration .6.Under Services (Infrastructure tab), configure Oracle Cloud Storage settings and click Test. |
See Security, Authentication, and Authorization in REST API for Oracle Integration .3.In runtime administration, configure supporting services and settings, as needed.On the Oracle Integration Home page, select My Tasks in the navigation pane, then Workspace .In the My Tasks navigation pane, select Administration .4.IMPORTANT: Under Archive and Purge , configure purge and archive settings for process instances and analytics data.4-1Be sure to verify the retention policies set to purge unused information.Set the Purge Retention (Days) setting on the Schedule Instances Archive tab to the number of days to retain completed process instances before they get purged.(Purged instances cannot be recovered.)Because increasing retention days increases database consumption,you must balance your organization's retention needs with database capacity.See Archive and Purge Data in Using Processes in Oracle Integration .5.Under Services (Platform tab), configure Oracle Content and Experience settings if integrating documents in process applications.See How do I integrate with Oracle Content and Experience Cloud?in Using Processes in Oracle Integration .6.Under Services (Infrastructure tab), configure Oracle Cloud Storage settings and click Test.Use values from earlier compartment and object storage configurations. |
3.In runtime administration, configure supporting services and settings, as needed.On the Oracle Integration Home page, select My Tasks in the navigation pane, then Workspace .In the My Tasks navigation pane, select Administration .4.IMPORTANT: Under Archive and Purge , configure purge and archive settings for process instances and analytics data.4-1Be sure to verify the retention policies set to purge unused information.Set the Purge Retention (Days) setting on the Schedule Instances Archive tab to the number of days to retain completed process instances before they get purged.(Purged instances cannot be recovered.)Because increasing retention days increases database consumption,you must balance your organization's retention needs with database capacity.See Archive and Purge Data in Using Processes in Oracle Integration .5.Under Services (Platform tab), configure Oracle Content and Experience settings if integrating documents in process applications.See How do I integrate with Oracle Content and Experience Cloud?in Using Processes in Oracle Integration .6.Under Services (Infrastructure tab), configure Oracle Cloud Storage settings and click Test.Use values from earlier compartment and object storage configurations.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) . |
On the Oracle Integration Home page, select My Tasks in the navigation pane, then Workspace .In the My Tasks navigation pane, select Administration .4.IMPORTANT: Under Archive and Purge , configure purge and archive settings for process instances and analytics data.4-1Be sure to verify the retention policies set to purge unused information.Set the Purge Retention (Days) setting on the Schedule Instances Archive tab to the number of days to retain completed process instances before they get purged.(Purged instances cannot be recovered.)Because increasing retention days increases database consumption,you must balance your organization's retention needs with database capacity.See Archive and Purge Data in Using Processes in Oracle Integration .5.Under Services (Platform tab), configure Oracle Content and Experience settings if integrating documents in process applications.See How do I integrate with Oracle Content and Experience Cloud?in Using Processes in Oracle Integration .6.Under Services (Infrastructure tab), configure Oracle Cloud Storage settings and click Test.Use values from earlier compartment and object storage configurations.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .a.In the URL field, enter the URL constructed as follows: https://swiftobjectstorage. |
In the My Tasks navigation pane, select Administration .4.IMPORTANT: Under Archive and Purge , configure purge and archive settings for process instances and analytics data.4-1Be sure to verify the retention policies set to purge unused information.Set the Purge Retention (Days) setting on the Schedule Instances Archive tab to the number of days to retain completed process instances before they get purged.(Purged instances cannot be recovered.)Because increasing retention days increases database consumption,you must balance your organization's retention needs with database capacity.See Archive and Purge Data in Using Processes in Oracle Integration .5.Under Services (Platform tab), configure Oracle Content and Experience settings if integrating documents in process applications.See How do I integrate with Oracle Content and Experience Cloud?in Using Processes in Oracle Integration .6.Under Services (Infrastructure tab), configure Oracle Cloud Storage settings and click Test.Use values from earlier compartment and object storage configurations.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .a.In the URL field, enter the URL constructed as follows: https://swiftobjectstorage.region .oraclecloud.com/v1/ tenancy For example: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic b.In the Container Name field, enter the storage bucket name. |
4.IMPORTANT: Under Archive and Purge , configure purge and archive settings for process instances and analytics data.4-1Be sure to verify the retention policies set to purge unused information.Set the Purge Retention (Days) setting on the Schedule Instances Archive tab to the number of days to retain completed process instances before they get purged.(Purged instances cannot be recovered.)Because increasing retention days increases database consumption,you must balance your organization's retention needs with database capacity.See Archive and Purge Data in Using Processes in Oracle Integration .5.Under Services (Platform tab), configure Oracle Content and Experience settings if integrating documents in process applications.See How do I integrate with Oracle Content and Experience Cloud?in Using Processes in Oracle Integration .6.Under Services (Infrastructure tab), configure Oracle Cloud Storage settings and click Test.Use values from earlier compartment and object storage configurations.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .a.In the URL field, enter the URL constructed as follows: https://swiftobjectstorage.region .oraclecloud.com/v1/ tenancy For example: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic b.In the Container Name field, enter the storage bucket name.c.In the User field, enter your administrator username ( [email protected] ) d.In the Password field, enter the OAuth token you generated when creating the storage bucket. |
4-1Be sure to verify the retention policies set to purge unused information.Set the Purge Retention (Days) setting on the Schedule Instances Archive tab to the number of days to retain completed process instances before they get purged.(Purged instances cannot be recovered.)Because increasing retention days increases database consumption,you must balance your organization's retention needs with database capacity.See Archive and Purge Data in Using Processes in Oracle Integration .5.Under Services (Platform tab), configure Oracle Content and Experience settings if integrating documents in process applications.See How do I integrate with Oracle Content and Experience Cloud?in Using Processes in Oracle Integration .6.Under Services (Infrastructure tab), configure Oracle Cloud Storage settings and click Test.Use values from earlier compartment and object storage configurations.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .a.In the URL field, enter the URL constructed as follows: https://swiftobjectstorage.region .oraclecloud.com/v1/ tenancy For example: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic b.In the Container Name field, enter the storage bucket name.c.In the User field, enter your administrator username ( [email protected] ) d.In the Password field, enter the OAuth token you generated when creating the storage bucket.7.Under Services (Infrastructure tab), configure the Oracle Notification Service for email notifications. |
Set the Purge Retention (Days) setting on the Schedule Instances Archive tab to the number of days to retain completed process instances before they get purged.(Purged instances cannot be recovered.)Because increasing retention days increases database consumption,you must balance your organization's retention needs with database capacity.See Archive and Purge Data in Using Processes in Oracle Integration .5.Under Services (Platform tab), configure Oracle Content and Experience settings if integrating documents in process applications.See How do I integrate with Oracle Content and Experience Cloud?in Using Processes in Oracle Integration .6.Under Services (Infrastructure tab), configure Oracle Cloud Storage settings and click Test.Use values from earlier compartment and object storage configurations.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .a.In the URL field, enter the URL constructed as follows: https://swiftobjectstorage.region .oraclecloud.com/v1/ tenancy For example: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic b.In the Container Name field, enter the storage bucket name.c.In the User field, enter your administrator username ( [email protected] ) d.In the Password field, enter the OAuth token you generated when creating the storage bucket.7.Under Services (Infrastructure tab), configure the Oracle Notification Service for email notifications.This service must be configured for users to receive email notifications. |
(Purged instances cannot be recovered.)Because increasing retention days increases database consumption,you must balance your organization's retention needs with database capacity.See Archive and Purge Data in Using Processes in Oracle Integration .5.Under Services (Platform tab), configure Oracle Content and Experience settings if integrating documents in process applications.See How do I integrate with Oracle Content and Experience Cloud?in Using Processes in Oracle Integration .6.Under Services (Infrastructure tab), configure Oracle Cloud Storage settings and click Test.Use values from earlier compartment and object storage configurations.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .a.In the URL field, enter the URL constructed as follows: https://swiftobjectstorage.region .oraclecloud.com/v1/ tenancy For example: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic b.In the Container Name field, enter the storage bucket name.c.In the User field, enter your administrator username ( [email protected] ) d.In the Password field, enter the OAuth token you generated when creating the storage bucket.7.Under Services (Infrastructure tab), configure the Oracle Notification Service for email notifications.This service must be configured for users to receive email notifications.See Enable Email Notifications. |
Because increasing retention days increases database consumption,you must balance your organization's retention needs with database capacity.See Archive and Purge Data in Using Processes in Oracle Integration .5.Under Services (Platform tab), configure Oracle Content and Experience settings if integrating documents in process applications.See How do I integrate with Oracle Content and Experience Cloud?in Using Processes in Oracle Integration .6.Under Services (Infrastructure tab), configure Oracle Cloud Storage settings and click Test.Use values from earlier compartment and object storage configurations.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .a.In the URL field, enter the URL constructed as follows: https://swiftobjectstorage.region .oraclecloud.com/v1/ tenancy For example: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic b.In the Container Name field, enter the storage bucket name.c.In the User field, enter your administrator username ( [email protected] ) d.In the Password field, enter the OAuth token you generated when creating the storage bucket.7.Under Services (Infrastructure tab), configure the Oracle Notification Service for email notifications.This service must be configured for users to receive email notifications.See Enable Email Notifications.8.Open imported decision models used by process applications. |
See Archive and Purge Data in Using Processes in Oracle Integration .5.Under Services (Platform tab), configure Oracle Content and Experience settings if integrating documents in process applications.See How do I integrate with Oracle Content and Experience Cloud?in Using Processes in Oracle Integration .6.Under Services (Infrastructure tab), configure Oracle Cloud Storage settings and click Test.Use values from earlier compartment and object storage configurations.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .a.In the URL field, enter the URL constructed as follows: https://swiftobjectstorage.region .oraclecloud.com/v1/ tenancy For example: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic b.In the Container Name field, enter the storage bucket name.c.In the User field, enter your administrator username ( [email protected] ) d.In the Password field, enter the OAuth token you generated when creating the storage bucket.7.Under Services (Infrastructure tab), configure the Oracle Notification Service for email notifications.This service must be configured for users to receive email notifications.See Enable Email Notifications.8.Open imported decision models used by process applications.Decision models are automatically activated during import. |
5.Under Services (Platform tab), configure Oracle Content and Experience settings if integrating documents in process applications.See How do I integrate with Oracle Content and Experience Cloud?in Using Processes in Oracle Integration .6.Under Services (Infrastructure tab), configure Oracle Cloud Storage settings and click Test.Use values from earlier compartment and object storage configurations.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .a.In the URL field, enter the URL constructed as follows: https://swiftobjectstorage.region .oraclecloud.com/v1/ tenancy For example: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic b.In the Container Name field, enter the storage bucket name.c.In the User field, enter your administrator username ( [email protected] ) d.In the Password field, enter the OAuth token you generated when creating the storage bucket.7.Under Services (Infrastructure tab), configure the Oracle Notification Service for email notifications.This service must be configured for users to receive email notifications.See Enable Email Notifications.8.Open imported decision models used by process applications.Decision models are automatically activated during import.Navigate to Decisions and update the references. |
See How do I integrate with Oracle Content and Experience Cloud?in Using Processes in Oracle Integration .6.Under Services (Infrastructure tab), configure Oracle Cloud Storage settings and click Test.Use values from earlier compartment and object storage configurations.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .a.In the URL field, enter the URL constructed as follows: https://swiftobjectstorage.region .oraclecloud.com/v1/ tenancy For example: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic b.In the Container Name field, enter the storage bucket name.c.In the User field, enter your administrator username ( [email protected] ) d.In the Password field, enter the OAuth token you generated when creating the storage bucket.7.Under Services (Infrastructure tab), configure the Oracle Notification Service for email notifications.This service must be configured for users to receive email notifications.See Enable Email Notifications.8.Open imported decision models used by process applications.Decision models are automatically activated during import.Navigate to Decisions and update the references.9.Activate imported integration flows if used by process applications. |
in Using Processes in Oracle Integration .6.Under Services (Infrastructure tab), configure Oracle Cloud Storage settings and click Test.Use values from earlier compartment and object storage configurations.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .a.In the URL field, enter the URL constructed as follows: https://swiftobjectstorage.region .oraclecloud.com/v1/ tenancy For example: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic b.In the Container Name field, enter the storage bucket name.c.In the User field, enter your administrator username ( [email protected] ) d.In the Password field, enter the OAuth token you generated when creating the storage bucket.7.Under Services (Infrastructure tab), configure the Oracle Notification Service for email notifications.This service must be configured for users to receive email notifications.See Enable Email Notifications.8.Open imported decision models used by process applications.Decision models are automatically activated during import.Navigate to Decisions and update the references.9.Activate imported integration flows if used by process applications.Note that integrations must be activated. |
6.Under Services (Infrastructure tab), configure Oracle Cloud Storage settings and click Test.Use values from earlier compartment and object storage configurations.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .a.In the URL field, enter the URL constructed as follows: https://swiftobjectstorage.region .oraclecloud.com/v1/ tenancy For example: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic b.In the Container Name field, enter the storage bucket name.c.In the User field, enter your administrator username ( [email protected] ) d.In the Password field, enter the OAuth token you generated when creating the storage bucket.7.Under Services (Infrastructure tab), configure the Oracle Notification Service for email notifications.This service must be configured for users to receive email notifications.See Enable Email Notifications.8.Open imported decision models used by process applications.Decision models are automatically activated during import.Navigate to Decisions and update the references.9.Activate imported integration flows if used by process applications.Note that integrations must be activated.After migration, you may need to reconfigure the integrations and invocations from both Processes and Integrations, as both support direct interaction with each other from within Oracle Integration. |
Use values from earlier compartment and object storage configurations.See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .a.In the URL field, enter the URL constructed as follows: https://swiftobjectstorage.region .oraclecloud.com/v1/ tenancy For example: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic b.In the Container Name field, enter the storage bucket name.c.In the User field, enter your administrator username ( [email protected] ) d.In the Password field, enter the OAuth token you generated when creating the storage bucket.7.Under Services (Infrastructure tab), configure the Oracle Notification Service for email notifications.This service must be configured for users to receive email notifications.See Enable Email Notifications.8.Open imported decision models used by process applications.Decision models are automatically activated during import.Navigate to Decisions and update the references.9.Activate imported integration flows if used by process applications.Note that integrations must be activated.After migration, you may need to reconfigure the integrations and invocations from both Processes and Integrations, as both support direct interaction with each other from within Oracle Integration.a.On the Oracle Integration Home page, select Process Applications in the navigation pane, open an imported application, and select Integrations in the navigation pane. |
See Step 3: Create an Object Storage Bucket and Construct the Storage URL (If Not Using the Application Migration Service) .a.In the URL field, enter the URL constructed as follows: https://swiftobjectstorage.region .oraclecloud.com/v1/ tenancy For example: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic b.In the Container Name field, enter the storage bucket name.c.In the User field, enter your administrator username ( [email protected] ) d.In the Password field, enter the OAuth token you generated when creating the storage bucket.7.Under Services (Infrastructure tab), configure the Oracle Notification Service for email notifications.This service must be configured for users to receive email notifications.See Enable Email Notifications.8.Open imported decision models used by process applications.Decision models are automatically activated during import.Navigate to Decisions and update the references.9.Activate imported integration flows if used by process applications.Note that integrations must be activated.After migration, you may need to reconfigure the integrations and invocations from both Processes and Integrations, as both support direct interaction with each other from within Oracle Integration.a.On the Oracle Integration Home page, select Process Applications in the navigation pane, open an imported application, and select Integrations in the navigation pane.b.Select an integration to update, click Edit and update as needed. |
a.In the URL field, enter the URL constructed as follows: https://swiftobjectstorage.region .oraclecloud.com/v1/ tenancy For example: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic b.In the Container Name field, enter the storage bucket name.c.In the User field, enter your administrator username ( [email protected] ) d.In the Password field, enter the OAuth token you generated when creating the storage bucket.7.Under Services (Infrastructure tab), configure the Oracle Notification Service for email notifications.This service must be configured for users to receive email notifications.See Enable Email Notifications.8.Open imported decision models used by process applications.Decision models are automatically activated during import.Navigate to Decisions and update the references.9.Activate imported integration flows if used by process applications.Note that integrations must be activated.After migration, you may need to reconfigure the integrations and invocations from both Processes and Integrations, as both support direct interaction with each other from within Oracle Integration.a.On the Oracle Integration Home page, select Process Applications in the navigation pane, open an imported application, and select Integrations in the navigation pane.b.Select an integration to update, click Edit and update as needed.c.Update the security for the called service. |
region .oraclecloud.com/v1/ tenancy For example: https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/ paasdevoic b.In the Container Name field, enter the storage bucket name.c.In the User field, enter your administrator username ( [email protected] ) d.In the Password field, enter the OAuth token you generated when creating the storage bucket.7.Under Services (Infrastructure tab), configure the Oracle Notification Service for email notifications.This service must be configured for users to receive email notifications.See Enable Email Notifications.8.Open imported decision models used by process applications.Decision models are automatically activated during import.Navigate to Decisions and update the references.9.Activate imported integration flows if used by process applications.Note that integrations must be activated.After migration, you may need to reconfigure the integrations and invocations from both Processes and Integrations, as both support direct interaction with each other from within Oracle Integration.a.On the Oracle Integration Home page, select Process Applications in the navigation pane, open an imported application, and select Integrations in the navigation pane.b.Select an integration to update, click Edit and update as needed.c.Update the security for the called service.Click the Security tab, then the Keystore Credential and update as needed. |
c.In the User field, enter your administrator username ( [email protected] ) d.In the Password field, enter the OAuth token you generated when creating the storage bucket.7.Under Services (Infrastructure tab), configure the Oracle Notification Service for email notifications.This service must be configured for users to receive email notifications.See Enable Email Notifications.8.Open imported decision models used by process applications.Decision models are automatically activated during import.Navigate to Decisions and update the references.9.Activate imported integration flows if used by process applications.Note that integrations must be activated.After migration, you may need to reconfigure the integrations and invocations from both Processes and Integrations, as both support direct interaction with each other from within Oracle Integration.a.On the Oracle Integration Home page, select Process Applications in the navigation pane, open an imported application, and select Integrations in the navigation pane.b.Select an integration to update, click Edit and update as needed.c.Update the security for the called service.Click the Security tab, then the Keystore Credential and update as needed.Set or import credentials/ certificates for each REST or SOAP connector used in your process applications. |
7.Under Services (Infrastructure tab), configure the Oracle Notification Service for email notifications.This service must be configured for users to receive email notifications.See Enable Email Notifications.8.Open imported decision models used by process applications.Decision models are automatically activated during import.Navigate to Decisions and update the references.9.Activate imported integration flows if used by process applications.Note that integrations must be activated.After migration, you may need to reconfigure the integrations and invocations from both Processes and Integrations, as both support direct interaction with each other from within Oracle Integration.a.On the Oracle Integration Home page, select Process Applications in the navigation pane, open an imported application, and select Integrations in the navigation pane.b.Select an integration to update, click Edit and update as needed.c.Update the security for the called service.Click the Security tab, then the Keystore Credential and update as needed.Set or import credentials/ certificates for each REST or SOAP connector used in your process applications.d.Complete changes and click Update , and save.Chapter 4 Complete Post-Migration Tasks for Processes 4-210.Activate imported process applications, if needed. |
This service must be configured for users to receive email notifications.See Enable Email Notifications.8.Open imported decision models used by process applications.Decision models are automatically activated during import.Navigate to Decisions and update the references.9.Activate imported integration flows if used by process applications.Note that integrations must be activated.After migration, you may need to reconfigure the integrations and invocations from both Processes and Integrations, as both support direct interaction with each other from within Oracle Integration.a.On the Oracle Integration Home page, select Process Applications in the navigation pane, open an imported application, and select Integrations in the navigation pane.b.Select an integration to update, click Edit and update as needed.c.Update the security for the called service.Click the Security tab, then the Keystore Credential and update as needed.Set or import credentials/ certificates for each REST or SOAP connector used in your process applications.d.Complete changes and click Update , and save.Chapter 4 Complete Post-Migration Tasks for Processes 4-210.Activate imported process applications, if needed.See Activate Applications in Using Processes in Oracle Integration . |
See Enable Email Notifications.8.Open imported decision models used by process applications.Decision models are automatically activated during import.Navigate to Decisions and update the references.9.Activate imported integration flows if used by process applications.Note that integrations must be activated.After migration, you may need to reconfigure the integrations and invocations from both Processes and Integrations, as both support direct interaction with each other from within Oracle Integration.a.On the Oracle Integration Home page, select Process Applications in the navigation pane, open an imported application, and select Integrations in the navigation pane.b.Select an integration to update, click Edit and update as needed.c.Update the security for the called service.Click the Security tab, then the Keystore Credential and update as needed.Set or import credentials/ certificates for each REST or SOAP connector used in your process applications.d.Complete changes and click Update , and save.Chapter 4 Complete Post-Migration Tasks for Processes 4-210.Activate imported process applications, if needed.See Activate Applications in Using Processes in Oracle Integration .You can also use the Processes REST APIs that allow you to activate process applications. |
8.Open imported decision models used by process applications.Decision models are automatically activated during import.Navigate to Decisions and update the references.9.Activate imported integration flows if used by process applications.Note that integrations must be activated.After migration, you may need to reconfigure the integrations and invocations from both Processes and Integrations, as both support direct interaction with each other from within Oracle Integration.a.On the Oracle Integration Home page, select Process Applications in the navigation pane, open an imported application, and select Integrations in the navigation pane.b.Select an integration to update, click Edit and update as needed.c.Update the security for the called service.Click the Security tab, then the Keystore Credential and update as needed.Set or import credentials/ certificates for each REST or SOAP connector used in your process applications.d.Complete changes and click Update , and save.Chapter 4 Complete Post-Migration Tasks for Processes 4-210.Activate imported process applications, if needed.See Activate Applications in Using Processes in Oracle Integration .You can also use the Processes REST APIs that allow you to activate process applications.Previous runtime instance data is not migrated. |
Decision models are automatically activated during import.Navigate to Decisions and update the references.9.Activate imported integration flows if used by process applications.Note that integrations must be activated.After migration, you may need to reconfigure the integrations and invocations from both Processes and Integrations, as both support direct interaction with each other from within Oracle Integration.a.On the Oracle Integration Home page, select Process Applications in the navigation pane, open an imported application, and select Integrations in the navigation pane.b.Select an integration to update, click Edit and update as needed.c.Update the security for the called service.Click the Security tab, then the Keystore Credential and update as needed.Set or import credentials/ certificates for each REST or SOAP connector used in your process applications.d.Complete changes and click Update , and save.Chapter 4 Complete Post-Migration Tasks for Processes 4-210.Activate imported process applications, if needed.See Activate Applications in Using Processes in Oracle Integration .You can also use the Processes REST APIs that allow you to activate process applications.Previous runtime instance data is not migrated.See Handle In-Flight Process Instances . |
Navigate to Decisions and update the references.9.Activate imported integration flows if used by process applications.Note that integrations must be activated.After migration, you may need to reconfigure the integrations and invocations from both Processes and Integrations, as both support direct interaction with each other from within Oracle Integration.a.On the Oracle Integration Home page, select Process Applications in the navigation pane, open an imported application, and select Integrations in the navigation pane.b.Select an integration to update, click Edit and update as needed.c.Update the security for the called service.Click the Security tab, then the Keystore Credential and update as needed.Set or import credentials/ certificates for each REST or SOAP connector used in your process applications.d.Complete changes and click Update , and save.Chapter 4 Complete Post-Migration Tasks for Processes 4-210.Activate imported process applications, if needed.See Activate Applications in Using Processes in Oracle Integration .You can also use the Processes REST APIs that allow you to activate process applications.Previous runtime instance data is not migrated.See Handle In-Flight Process Instances .11.Remap Processes user roles (swim lanes) for all process applications. |
9.Activate imported integration flows if used by process applications.Note that integrations must be activated.After migration, you may need to reconfigure the integrations and invocations from both Processes and Integrations, as both support direct interaction with each other from within Oracle Integration.a.On the Oracle Integration Home page, select Process Applications in the navigation pane, open an imported application, and select Integrations in the navigation pane.b.Select an integration to update, click Edit and update as needed.c.Update the security for the called service.Click the Security tab, then the Keystore Credential and update as needed.Set or import credentials/ certificates for each REST or SOAP connector used in your process applications.d.Complete changes and click Update , and save.Chapter 4 Complete Post-Migration Tasks for Processes 4-210.Activate imported process applications, if needed.See Activate Applications in Using Processes in Oracle Integration .You can also use the Processes REST APIs that allow you to activate process applications.Previous runtime instance data is not migrated.See Handle In-Flight Process Instances .11.Remap Processes user roles (swim lanes) for all process applications.Process role mappings are not migrated. |
Note that integrations must be activated.After migration, you may need to reconfigure the integrations and invocations from both Processes and Integrations, as both support direct interaction with each other from within Oracle Integration.a.On the Oracle Integration Home page, select Process Applications in the navigation pane, open an imported application, and select Integrations in the navigation pane.b.Select an integration to update, click Edit and update as needed.c.Update the security for the called service.Click the Security tab, then the Keystore Credential and update as needed.Set or import credentials/ certificates for each REST or SOAP connector used in your process applications.d.Complete changes and click Update , and save.Chapter 4 Complete Post-Migration Tasks for Processes 4-210.Activate imported process applications, if needed.See Activate Applications in Using Processes in Oracle Integration .You can also use the Processes REST APIs that allow you to activate process applications.Previous runtime instance data is not migrated.See Handle In-Flight Process Instances .11.Remap Processes user roles (swim lanes) for all process applications.Process role mappings are not migrated.Reconfigure role mappings for each process application under Manage Roles in Workspace Administration. |
After migration, you may need to reconfigure the integrations and invocations from both Processes and Integrations, as both support direct interaction with each other from within Oracle Integration.a.On the Oracle Integration Home page, select Process Applications in the navigation pane, open an imported application, and select Integrations in the navigation pane.b.Select an integration to update, click Edit and update as needed.c.Update the security for the called service.Click the Security tab, then the Keystore Credential and update as needed.Set or import credentials/ certificates for each REST or SOAP connector used in your process applications.d.Complete changes and click Update , and save.Chapter 4 Complete Post-Migration Tasks for Processes 4-210.Activate imported process applications, if needed.See Activate Applications in Using Processes in Oracle Integration .You can also use the Processes REST APIs that allow you to activate process applications.Previous runtime instance data is not migrated.See Handle In-Flight Process Instances .11.Remap Processes user roles (swim lanes) for all process applications.Process role mappings are not migrated.Reconfigure role mappings for each process application under Manage Roles in Workspace Administration.Note that users must be migrated to Oracle Integration before they can be mapped to roles. |
a.On the Oracle Integration Home page, select Process Applications in the navigation pane, open an imported application, and select Integrations in the navigation pane.b.Select an integration to update, click Edit and update as needed.c.Update the security for the called service.Click the Security tab, then the Keystore Credential and update as needed.Set or import credentials/ certificates for each REST or SOAP connector used in your process applications.d.Complete changes and click Update , and save.Chapter 4 Complete Post-Migration Tasks for Processes 4-210.Activate imported process applications, if needed.See Activate Applications in Using Processes in Oracle Integration .You can also use the Processes REST APIs that allow you to activate process applications.Previous runtime instance data is not migrated.See Handle In-Flight Process Instances .11.Remap Processes user roles (swim lanes) for all process applications.Process role mappings are not migrated.Reconfigure role mappings for each process application under Manage Roles in Workspace Administration.Note that users must be migrated to Oracle Integration before they can be mapped to roles.See Assign and Manage Roles in Using Processes in Oracle Integration . |
b.Select an integration to update, click Edit and update as needed.c.Update the security for the called service.Click the Security tab, then the Keystore Credential and update as needed.Set or import credentials/ certificates for each REST or SOAP connector used in your process applications.d.Complete changes and click Update , and save.Chapter 4 Complete Post-Migration Tasks for Processes 4-210.Activate imported process applications, if needed.See Activate Applications in Using Processes in Oracle Integration .You can also use the Processes REST APIs that allow you to activate process applications.Previous runtime instance data is not migrated.See Handle In-Flight Process Instances .11.Remap Processes user roles (swim lanes) for all process applications.Process role mappings are not migrated.Reconfigure role mappings for each process application under Manage Roles in Workspace Administration.Note that users must be migrated to Oracle Integration before they can be mapped to roles.See Assign and Manage Roles in Using Processes in Oracle Integration .Handle In-Flight Process Instances After import, follow guidelines to handle currently running process instances. |
c.Update the security for the called service.Click the Security tab, then the Keystore Credential and update as needed.Set or import credentials/ certificates for each REST or SOAP connector used in your process applications.d.Complete changes and click Update , and save.Chapter 4 Complete Post-Migration Tasks for Processes 4-210.Activate imported process applications, if needed.See Activate Applications in Using Processes in Oracle Integration .You can also use the Processes REST APIs that allow you to activate process applications.Previous runtime instance data is not migrated.See Handle In-Flight Process Instances .11.Remap Processes user roles (swim lanes) for all process applications.Process role mappings are not migrated.Reconfigure role mappings for each process application under Manage Roles in Workspace Administration.Note that users must be migrated to Oracle Integration before they can be mapped to roles.See Assign and Manage Roles in Using Processes in Oracle Integration .Handle In-Flight Process Instances After import, follow guidelines to handle currently running process instances.Handling short lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then schedule a transition period during which no new instances are created in the classic environment. |
Click the Security tab, then the Keystore Credential and update as needed.Set or import credentials/ certificates for each REST or SOAP connector used in your process applications.d.Complete changes and click Update , and save.Chapter 4 Complete Post-Migration Tasks for Processes 4-210.Activate imported process applications, if needed.See Activate Applications in Using Processes in Oracle Integration .You can also use the Processes REST APIs that allow you to activate process applications.Previous runtime instance data is not migrated.See Handle In-Flight Process Instances .11.Remap Processes user roles (swim lanes) for all process applications.Process role mappings are not migrated.Reconfigure role mappings for each process application under Manage Roles in Workspace Administration.Note that users must be migrated to Oracle Integration before they can be mapped to roles.See Assign and Manage Roles in Using Processes in Oracle Integration .Handle In-Flight Process Instances After import, follow guidelines to handle currently running process instances.Handling short lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then schedule a transition period during which no new instances are created in the classic environment.Let classic environment instances and tasks complete and drain, with no new instances created. |
Set or import credentials/ certificates for each REST or SOAP connector used in your process applications.d.Complete changes and click Update , and save.Chapter 4 Complete Post-Migration Tasks for Processes 4-210.Activate imported process applications, if needed.See Activate Applications in Using Processes in Oracle Integration .You can also use the Processes REST APIs that allow you to activate process applications.Previous runtime instance data is not migrated.See Handle In-Flight Process Instances .11.Remap Processes user roles (swim lanes) for all process applications.Process role mappings are not migrated.Reconfigure role mappings for each process application under Manage Roles in Workspace Administration.Note that users must be migrated to Oracle Integration before they can be mapped to roles.See Assign and Manage Roles in Using Processes in Oracle Integration .Handle In-Flight Process Instances After import, follow guidelines to handle currently running process instances.Handling short lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then schedule a transition period during which no new instances are created in the classic environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance. |
d.Complete changes and click Update , and save.Chapter 4 Complete Post-Migration Tasks for Processes 4-210.Activate imported process applications, if needed.See Activate Applications in Using Processes in Oracle Integration .You can also use the Processes REST APIs that allow you to activate process applications.Previous runtime instance data is not migrated.See Handle In-Flight Process Instances .11.Remap Processes user roles (swim lanes) for all process applications.Process role mappings are not migrated.Reconfigure role mappings for each process application under Manage Roles in Workspace Administration.Note that users must be migrated to Oracle Integration before they can be mapped to roles.See Assign and Manage Roles in Using Processes in Oracle Integration .Handle In-Flight Process Instances After import, follow guidelines to handle currently running process instances.Handling short lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then schedule a transition period during which no new instances are created in the classic environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes. |
See Activate Applications in Using Processes in Oracle Integration .You can also use the Processes REST APIs that allow you to activate process applications.Previous runtime instance data is not migrated.See Handle In-Flight Process Instances .11.Remap Processes user roles (swim lanes) for all process applications.Process role mappings are not migrated.Reconfigure role mappings for each process application under Manage Roles in Workspace Administration.Note that users must be migrated to Oracle Integration before they can be mapped to roles.See Assign and Manage Roles in Using Processes in Oracle Integration .Handle In-Flight Process Instances After import, follow guidelines to handle currently running process instances.Handling short lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then schedule a transition period during which no new instances are created in the classic environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes.After the transition period, all process runtime activity ends on the classic environment. |
You can also use the Processes REST APIs that allow you to activate process applications.Previous runtime instance data is not migrated.See Handle In-Flight Process Instances .11.Remap Processes user roles (swim lanes) for all process applications.Process role mappings are not migrated.Reconfigure role mappings for each process application under Manage Roles in Workspace Administration.Note that users must be migrated to Oracle Integration before they can be mapped to roles.See Assign and Manage Roles in Using Processes in Oracle Integration .Handle In-Flight Process Instances After import, follow guidelines to handle currently running process instances.Handling short lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then schedule a transition period during which no new instances are created in the classic environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes.After the transition period, all process runtime activity ends on the classic environment.End users no longer need to use two inboxes. |
Previous runtime instance data is not migrated.See Handle In-Flight Process Instances .11.Remap Processes user roles (swim lanes) for all process applications.Process role mappings are not migrated.Reconfigure role mappings for each process application under Manage Roles in Workspace Administration.Note that users must be migrated to Oracle Integration before they can be mapped to roles.See Assign and Manage Roles in Using Processes in Oracle Integration .Handle In-Flight Process Instances After import, follow guidelines to handle currently running process instances.Handling short lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then schedule a transition period during which no new instances are created in the classic environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes.After the transition period, all process runtime activity ends on the classic environment.End users no longer need to use two inboxes.Handling long lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then terminate instances in the classic environment and manually recreate them in the Oracle Cloud Infrastructure environment. |
See Handle In-Flight Process Instances .11.Remap Processes user roles (swim lanes) for all process applications.Process role mappings are not migrated.Reconfigure role mappings for each process application under Manage Roles in Workspace Administration.Note that users must be migrated to Oracle Integration before they can be mapped to roles.See Assign and Manage Roles in Using Processes in Oracle Integration .Handle In-Flight Process Instances After import, follow guidelines to handle currently running process instances.Handling short lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then schedule a transition period during which no new instances are created in the classic environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes.After the transition period, all process runtime activity ends on the classic environment.End users no longer need to use two inboxes.Handling long lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then terminate instances in the classic environment and manually recreate them in the Oracle Cloud Infrastructure environment.Let classic environment instances and tasks complete and drain, with no new instances created. |
11.Remap Processes user roles (swim lanes) for all process applications.Process role mappings are not migrated.Reconfigure role mappings for each process application under Manage Roles in Workspace Administration.Note that users must be migrated to Oracle Integration before they can be mapped to roles.See Assign and Manage Roles in Using Processes in Oracle Integration .Handle In-Flight Process Instances After import, follow guidelines to handle currently running process instances.Handling short lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then schedule a transition period during which no new instances are created in the classic environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes.After the transition period, all process runtime activity ends on the classic environment.End users no longer need to use two inboxes.Handling long lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then terminate instances in the classic environment and manually recreate them in the Oracle Cloud Infrastructure environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance. |
Process role mappings are not migrated.Reconfigure role mappings for each process application under Manage Roles in Workspace Administration.Note that users must be migrated to Oracle Integration before they can be mapped to roles.See Assign and Manage Roles in Using Processes in Oracle Integration .Handle In-Flight Process Instances After import, follow guidelines to handle currently running process instances.Handling short lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then schedule a transition period during which no new instances are created in the classic environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes.After the transition period, all process runtime activity ends on the classic environment.End users no longer need to use two inboxes.Handling long lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then terminate instances in the classic environment and manually recreate them in the Oracle Cloud Infrastructure environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes during the transition period. |
Reconfigure role mappings for each process application under Manage Roles in Workspace Administration.Note that users must be migrated to Oracle Integration before they can be mapped to roles.See Assign and Manage Roles in Using Processes in Oracle Integration .Handle In-Flight Process Instances After import, follow guidelines to handle currently running process instances.Handling short lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then schedule a transition period during which no new instances are created in the classic environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes.After the transition period, all process runtime activity ends on the classic environment.End users no longer need to use two inboxes.Handling long lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then terminate instances in the classic environment and manually recreate them in the Oracle Cloud Infrastructure environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes during the transition period.After the transition period, use the Alter Flow option in the classic environment to terminate instances. |
Note that users must be migrated to Oracle Integration before they can be mapped to roles.See Assign and Manage Roles in Using Processes in Oracle Integration .Handle In-Flight Process Instances After import, follow guidelines to handle currently running process instances.Handling short lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then schedule a transition period during which no new instances are created in the classic environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes.After the transition period, all process runtime activity ends on the classic environment.End users no longer need to use two inboxes.Handling long lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then terminate instances in the classic environment and manually recreate them in the Oracle Cloud Infrastructure environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes during the transition period.After the transition period, use the Alter Flow option in the classic environment to terminate instances.Create new instances with the same payload as in the classic environment in the Oracle Cloud Infrastructure environment. |
See Assign and Manage Roles in Using Processes in Oracle Integration .Handle In-Flight Process Instances After import, follow guidelines to handle currently running process instances.Handling short lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then schedule a transition period during which no new instances are created in the classic environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes.After the transition period, all process runtime activity ends on the classic environment.End users no longer need to use two inboxes.Handling long lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then terminate instances in the classic environment and manually recreate them in the Oracle Cloud Infrastructure environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes during the transition period.After the transition period, use the Alter Flow option in the classic environment to terminate instances.Create new instances with the same payload as in the classic environment in the Oracle Cloud Infrastructure environment.Use Alter Flow in Processes on the Oracle Cloud Infrastructure to move newly created replicas of the classic environment instances to the correct activity in the Oracle Cloud Infrastructure process. |
Handle In-Flight Process Instances After import, follow guidelines to handle currently running process instances.Handling short lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then schedule a transition period during which no new instances are created in the classic environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes.After the transition period, all process runtime activity ends on the classic environment.End users no longer need to use two inboxes.Handling long lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then terminate instances in the classic environment and manually recreate them in the Oracle Cloud Infrastructure environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes during the transition period.After the transition period, use the Alter Flow option in the classic environment to terminate instances.Create new instances with the same payload as in the classic environment in the Oracle Cloud Infrastructure environment.Use Alter Flow in Processes on the Oracle Cloud Infrastructure to move newly created replicas of the classic environment instances to the correct activity in the Oracle Cloud Infrastructure process.You can automate these actions by programmatically invoking the Alter Flow option in the classic environment and the Oracle Cloud Infrastructure environment. |
Handling short lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then schedule a transition period during which no new instances are created in the classic environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes.After the transition period, all process runtime activity ends on the classic environment.End users no longer need to use two inboxes.Handling long lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then terminate instances in the classic environment and manually recreate them in the Oracle Cloud Infrastructure environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes during the transition period.After the transition period, use the Alter Flow option in the classic environment to terminate instances.Create new instances with the same payload as in the classic environment in the Oracle Cloud Infrastructure environment.Use Alter Flow in Processes on the Oracle Cloud Infrastructure to move newly created replicas of the classic environment instances to the correct activity in the Oracle Cloud Infrastructure process.You can automate these actions by programmatically invoking the Alter Flow option in the classic environment and the Oracle Cloud Infrastructure environment.See Alter the Flow of a Process Instance in Using Processes in Oracle Integration . |
Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes.After the transition period, all process runtime activity ends on the classic environment.End users no longer need to use two inboxes.Handling long lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then terminate instances in the classic environment and manually recreate them in the Oracle Cloud Infrastructure environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes during the transition period.After the transition period, use the Alter Flow option in the classic environment to terminate instances.Create new instances with the same payload as in the classic environment in the Oracle Cloud Infrastructure environment.Use Alter Flow in Processes on the Oracle Cloud Infrastructure to move newly created replicas of the classic environment instances to the correct activity in the Oracle Cloud Infrastructure process.You can automate these actions by programmatically invoking the Alter Flow option in the classic environment and the Oracle Cloud Infrastructure environment.See Alter the Flow of a Process Instance in Using Processes in Oracle Integration .Follow Migration Best Practices for Processes Follow best practices whenever possible after migration to Oracle Integration. |
At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes.After the transition period, all process runtime activity ends on the classic environment.End users no longer need to use two inboxes.Handling long lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then terminate instances in the classic environment and manually recreate them in the Oracle Cloud Infrastructure environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes during the transition period.After the transition period, use the Alter Flow option in the classic environment to terminate instances.Create new instances with the same payload as in the classic environment in the Oracle Cloud Infrastructure environment.Use Alter Flow in Processes on the Oracle Cloud Infrastructure to move newly created replicas of the classic environment instances to the correct activity in the Oracle Cloud Infrastructure process.You can automate these actions by programmatically invoking the Alter Flow option in the classic environment and the Oracle Cloud Infrastructure environment.See Alter the Flow of a Process Instance in Using Processes in Oracle Integration .Follow Migration Best Practices for Processes Follow best practices whenever possible after migration to Oracle Integration.Wrap all rules and policy logic into decision models rather than Oracle Business Rules. |
During this transition period, end users must use two inboxes.After the transition period, all process runtime activity ends on the classic environment.End users no longer need to use two inboxes.Handling long lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then terminate instances in the classic environment and manually recreate them in the Oracle Cloud Infrastructure environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes during the transition period.After the transition period, use the Alter Flow option in the classic environment to terminate instances.Create new instances with the same payload as in the classic environment in the Oracle Cloud Infrastructure environment.Use Alter Flow in Processes on the Oracle Cloud Infrastructure to move newly created replicas of the classic environment instances to the correct activity in the Oracle Cloud Infrastructure process.You can automate these actions by programmatically invoking the Alter Flow option in the classic environment and the Oracle Cloud Infrastructure environment.See Alter the Flow of a Process Instance in Using Processes in Oracle Integration .Follow Migration Best Practices for Processes Follow best practices whenever possible after migration to Oracle Integration.Wrap all rules and policy logic into decision models rather than Oracle Business Rules.While you are able to create integrations using REST and SOAP connectors in process applications, it is recommended that you create all integrations in the OIC IntegrationsChapter 4 Complete Post-Migration Tasks for Processes 4-3area instead. |
After the transition period, all process runtime activity ends on the classic environment.End users no longer need to use two inboxes.Handling long lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then terminate instances in the classic environment and manually recreate them in the Oracle Cloud Infrastructure environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes during the transition period.After the transition period, use the Alter Flow option in the classic environment to terminate instances.Create new instances with the same payload as in the classic environment in the Oracle Cloud Infrastructure environment.Use Alter Flow in Processes on the Oracle Cloud Infrastructure to move newly created replicas of the classic environment instances to the correct activity in the Oracle Cloud Infrastructure process.You can automate these actions by programmatically invoking the Alter Flow option in the classic environment and the Oracle Cloud Infrastructure environment.See Alter the Flow of a Process Instance in Using Processes in Oracle Integration .Follow Migration Best Practices for Processes Follow best practices whenever possible after migration to Oracle Integration.Wrap all rules and policy logic into decision models rather than Oracle Business Rules.While you are able to create integrations using REST and SOAP connectors in process applications, it is recommended that you create all integrations in the OIC IntegrationsChapter 4 Complete Post-Migration Tasks for Processes 4-3area instead.From there, you can easily select them for use in structured and dynamic processes. |
End users no longer need to use two inboxes.Handling long lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then terminate instances in the classic environment and manually recreate them in the Oracle Cloud Infrastructure environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes during the transition period.After the transition period, use the Alter Flow option in the classic environment to terminate instances.Create new instances with the same payload as in the classic environment in the Oracle Cloud Infrastructure environment.Use Alter Flow in Processes on the Oracle Cloud Infrastructure to move newly created replicas of the classic environment instances to the correct activity in the Oracle Cloud Infrastructure process.You can automate these actions by programmatically invoking the Alter Flow option in the classic environment and the Oracle Cloud Infrastructure environment.See Alter the Flow of a Process Instance in Using Processes in Oracle Integration .Follow Migration Best Practices for Processes Follow best practices whenever possible after migration to Oracle Integration.Wrap all rules and policy logic into decision models rather than Oracle Business Rules.While you are able to create integrations using REST and SOAP connectors in process applications, it is recommended that you create all integrations in the OIC IntegrationsChapter 4 Complete Post-Migration Tasks for Processes 4-3area instead.From there, you can easily select them for use in structured and dynamic processes.This practice centralizes all integration efforts in the OIC Integrations area. |
Handling long lived instances and their human tasks For a short overlapping period, run the instances in parallel in both environments, then terminate instances in the classic environment and manually recreate them in the Oracle Cloud Infrastructure environment.Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes during the transition period.After the transition period, use the Alter Flow option in the classic environment to terminate instances.Create new instances with the same payload as in the classic environment in the Oracle Cloud Infrastructure environment.Use Alter Flow in Processes on the Oracle Cloud Infrastructure to move newly created replicas of the classic environment instances to the correct activity in the Oracle Cloud Infrastructure process.You can automate these actions by programmatically invoking the Alter Flow option in the classic environment and the Oracle Cloud Infrastructure environment.See Alter the Flow of a Process Instance in Using Processes in Oracle Integration .Follow Migration Best Practices for Processes Follow best practices whenever possible after migration to Oracle Integration.Wrap all rules and policy logic into decision models rather than Oracle Business Rules.While you are able to create integrations using REST and SOAP connectors in process applications, it is recommended that you create all integrations in the OIC IntegrationsChapter 4 Complete Post-Migration Tasks for Processes 4-3area instead.From there, you can easily select them for use in structured and dynamic processes.This practice centralizes all integration efforts in the OIC Integrations area.Among many updates, Oracle Integration provides a new Task List, accessed on the Home page by choosing My Tasks . |
Let classic environment instances and tasks complete and drain, with no new instances created.At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes during the transition period.After the transition period, use the Alter Flow option in the classic environment to terminate instances.Create new instances with the same payload as in the classic environment in the Oracle Cloud Infrastructure environment.Use Alter Flow in Processes on the Oracle Cloud Infrastructure to move newly created replicas of the classic environment instances to the correct activity in the Oracle Cloud Infrastructure process.You can automate these actions by programmatically invoking the Alter Flow option in the classic environment and the Oracle Cloud Infrastructure environment.See Alter the Flow of a Process Instance in Using Processes in Oracle Integration .Follow Migration Best Practices for Processes Follow best practices whenever possible after migration to Oracle Integration.Wrap all rules and policy logic into decision models rather than Oracle Business Rules.While you are able to create integrations using REST and SOAP connectors in process applications, it is recommended that you create all integrations in the OIC IntegrationsChapter 4 Complete Post-Migration Tasks for Processes 4-3area instead.From there, you can easily select them for use in structured and dynamic processes.This practice centralizes all integration efforts in the OIC Integrations area.Among many updates, Oracle Integration provides a new Task List, accessed on the Home page by choosing My Tasks .It provides a lighter weight interface with better performance. |
At the same time, ensure all new instances and tasks get run on the Oracle Cloud Infrastructure instance.During this transition period, end users must use two inboxes during the transition period.After the transition period, use the Alter Flow option in the classic environment to terminate instances.Create new instances with the same payload as in the classic environment in the Oracle Cloud Infrastructure environment.Use Alter Flow in Processes on the Oracle Cloud Infrastructure to move newly created replicas of the classic environment instances to the correct activity in the Oracle Cloud Infrastructure process.You can automate these actions by programmatically invoking the Alter Flow option in the classic environment and the Oracle Cloud Infrastructure environment.See Alter the Flow of a Process Instance in Using Processes in Oracle Integration .Follow Migration Best Practices for Processes Follow best practices whenever possible after migration to Oracle Integration.Wrap all rules and policy logic into decision models rather than Oracle Business Rules.While you are able to create integrations using REST and SOAP connectors in process applications, it is recommended that you create all integrations in the OIC IntegrationsChapter 4 Complete Post-Migration Tasks for Processes 4-3area instead.From there, you can easily select them for use in structured and dynamic processes.This practice centralizes all integration efforts in the OIC Integrations area.Among many updates, Oracle Integration provides a new Task List, accessed on the Home page by choosing My Tasks .It provides a lighter weight interface with better performance.My Tasks works best for end users Workspace works best for advanced users for back office and tracking purposes Complete Post-Migration Tasks for Visual Builder Applications Any applications on the Oracle Integration Classic instance that are live will need to be staged and published again after they are migrated to the new instance on Oracle Cloud Infrastructure. |
During this transition period, end users must use two inboxes during the transition period.After the transition period, use the Alter Flow option in the classic environment to terminate instances.Create new instances with the same payload as in the classic environment in the Oracle Cloud Infrastructure environment.Use Alter Flow in Processes on the Oracle Cloud Infrastructure to move newly created replicas of the classic environment instances to the correct activity in the Oracle Cloud Infrastructure process.You can automate these actions by programmatically invoking the Alter Flow option in the classic environment and the Oracle Cloud Infrastructure environment.See Alter the Flow of a Process Instance in Using Processes in Oracle Integration .Follow Migration Best Practices for Processes Follow best practices whenever possible after migration to Oracle Integration.Wrap all rules and policy logic into decision models rather than Oracle Business Rules.While you are able to create integrations using REST and SOAP connectors in process applications, it is recommended that you create all integrations in the OIC IntegrationsChapter 4 Complete Post-Migration Tasks for Processes 4-3area instead.From there, you can easily select them for use in structured and dynamic processes.This practice centralizes all integration efforts in the OIC Integrations area.Among many updates, Oracle Integration provides a new Task List, accessed on the Home page by choosing My Tasks .It provides a lighter weight interface with better performance.My Tasks works best for end users Workspace works best for advanced users for back office and tracking purposes Complete Post-Migration Tasks for Visual Builder Applications Any applications on the Oracle Integration Classic instance that are live will need to be staged and published again after they are migrated to the new instance on Oracle Cloud Infrastructure.Developers can lock a live visual application to prevent changes to live application data, and then import the live data to the new version of the application on Oracle Cloud Infrastructure. |
After the transition period, use the Alter Flow option in the classic environment to terminate instances.Create new instances with the same payload as in the classic environment in the Oracle Cloud Infrastructure environment.Use Alter Flow in Processes on the Oracle Cloud Infrastructure to move newly created replicas of the classic environment instances to the correct activity in the Oracle Cloud Infrastructure process.You can automate these actions by programmatically invoking the Alter Flow option in the classic environment and the Oracle Cloud Infrastructure environment.See Alter the Flow of a Process Instance in Using Processes in Oracle Integration .Follow Migration Best Practices for Processes Follow best practices whenever possible after migration to Oracle Integration.Wrap all rules and policy logic into decision models rather than Oracle Business Rules.While you are able to create integrations using REST and SOAP connectors in process applications, it is recommended that you create all integrations in the OIC IntegrationsChapter 4 Complete Post-Migration Tasks for Processes 4-3area instead.From there, you can easily select them for use in structured and dynamic processes.This practice centralizes all integration efforts in the OIC Integrations area.Among many updates, Oracle Integration provides a new Task List, accessed on the Home page by choosing My Tasks .It provides a lighter weight interface with better performance.My Tasks works best for end users Workspace works best for advanced users for back office and tracking purposes Complete Post-Migration Tasks for Visual Builder Applications Any applications on the Oracle Integration Classic instance that are live will need to be staged and published again after they are migrated to the new instance on Oracle Cloud Infrastructure.Developers can lock a live visual application to prevent changes to live application data, and then import the live data to the new version of the application on Oracle Cloud Infrastructure.After the live data is imported and the application is published, users can be instructed to use the new version of the live app. |
Create new instances with the same payload as in the classic environment in the Oracle Cloud Infrastructure environment.Use Alter Flow in Processes on the Oracle Cloud Infrastructure to move newly created replicas of the classic environment instances to the correct activity in the Oracle Cloud Infrastructure process.You can automate these actions by programmatically invoking the Alter Flow option in the classic environment and the Oracle Cloud Infrastructure environment.See Alter the Flow of a Process Instance in Using Processes in Oracle Integration .Follow Migration Best Practices for Processes Follow best practices whenever possible after migration to Oracle Integration.Wrap all rules and policy logic into decision models rather than Oracle Business Rules.While you are able to create integrations using REST and SOAP connectors in process applications, it is recommended that you create all integrations in the OIC IntegrationsChapter 4 Complete Post-Migration Tasks for Processes 4-3area instead.From there, you can easily select them for use in structured and dynamic processes.This practice centralizes all integration efforts in the OIC Integrations area.Among many updates, Oracle Integration provides a new Task List, accessed on the Home page by choosing My Tasks .It provides a lighter weight interface with better performance.My Tasks works best for end users Workspace works best for advanced users for back office and tracking purposes Complete Post-Migration Tasks for Visual Builder Applications Any applications on the Oracle Integration Classic instance that are live will need to be staged and published again after they are migrated to the new instance on Oracle Cloud Infrastructure.Developers can lock a live visual application to prevent changes to live application data, and then import the live data to the new version of the application on Oracle Cloud Infrastructure.After the live data is imported and the application is published, users can be instructed to use the new version of the live app.For users who access a web application, youll need to communicate the new URL that replaces the URL they used previously to access their web applications. |
Use Alter Flow in Processes on the Oracle Cloud Infrastructure to move newly created replicas of the classic environment instances to the correct activity in the Oracle Cloud Infrastructure process.You can automate these actions by programmatically invoking the Alter Flow option in the classic environment and the Oracle Cloud Infrastructure environment.See Alter the Flow of a Process Instance in Using Processes in Oracle Integration .Follow Migration Best Practices for Processes Follow best practices whenever possible after migration to Oracle Integration.Wrap all rules and policy logic into decision models rather than Oracle Business Rules.While you are able to create integrations using REST and SOAP connectors in process applications, it is recommended that you create all integrations in the OIC IntegrationsChapter 4 Complete Post-Migration Tasks for Processes 4-3area instead.From there, you can easily select them for use in structured and dynamic processes.This practice centralizes all integration efforts in the OIC Integrations area.Among many updates, Oracle Integration provides a new Task List, accessed on the Home page by choosing My Tasks .It provides a lighter weight interface with better performance.My Tasks works best for end users Workspace works best for advanced users for back office and tracking purposes Complete Post-Migration Tasks for Visual Builder Applications Any applications on the Oracle Integration Classic instance that are live will need to be staged and published again after they are migrated to the new instance on Oracle Cloud Infrastructure.Developers can lock a live visual application to prevent changes to live application data, and then import the live data to the new version of the application on Oracle Cloud Infrastructure.After the live data is imported and the application is published, users can be instructed to use the new version of the live app.For users who access a web application, youll need to communicate the new URL that replaces the URL they used previously to access their web applications.For mobile applications, youll need to rebuild and republish your mobile apps to the app store(s) where you initially published it or use whatever mechanism you used previously to distribute the mobile app. |
You can automate these actions by programmatically invoking the Alter Flow option in the classic environment and the Oracle Cloud Infrastructure environment.See Alter the Flow of a Process Instance in Using Processes in Oracle Integration .Follow Migration Best Practices for Processes Follow best practices whenever possible after migration to Oracle Integration.Wrap all rules and policy logic into decision models rather than Oracle Business Rules.While you are able to create integrations using REST and SOAP connectors in process applications, it is recommended that you create all integrations in the OIC IntegrationsChapter 4 Complete Post-Migration Tasks for Processes 4-3area instead.From there, you can easily select them for use in structured and dynamic processes.This practice centralizes all integration efforts in the OIC Integrations area.Among many updates, Oracle Integration provides a new Task List, accessed on the Home page by choosing My Tasks .It provides a lighter weight interface with better performance.My Tasks works best for end users Workspace works best for advanced users for back office and tracking purposes Complete Post-Migration Tasks for Visual Builder Applications Any applications on the Oracle Integration Classic instance that are live will need to be staged and published again after they are migrated to the new instance on Oracle Cloud Infrastructure.Developers can lock a live visual application to prevent changes to live application data, and then import the live data to the new version of the application on Oracle Cloud Infrastructure.After the live data is imported and the application is published, users can be instructed to use the new version of the live app.For users who access a web application, youll need to communicate the new URL that replaces the URL they used previously to access their web applications.For mobile applications, youll need to rebuild and republish your mobile apps to the app store(s) where you initially published it or use whatever mechanism you used previously to distribute the mobile app.Do this so users can update the mobile app on their device to a version of the app that was built using Oracle Visual Builder on Oracle Cloud Infrastructure. |
See Alter the Flow of a Process Instance in Using Processes in Oracle Integration .Follow Migration Best Practices for Processes Follow best practices whenever possible after migration to Oracle Integration.Wrap all rules and policy logic into decision models rather than Oracle Business Rules.While you are able to create integrations using REST and SOAP connectors in process applications, it is recommended that you create all integrations in the OIC IntegrationsChapter 4 Complete Post-Migration Tasks for Processes 4-3area instead.From there, you can easily select them for use in structured and dynamic processes.This practice centralizes all integration efforts in the OIC Integrations area.Among many updates, Oracle Integration provides a new Task List, accessed on the Home page by choosing My Tasks .It provides a lighter weight interface with better performance.My Tasks works best for end users Workspace works best for advanced users for back office and tracking purposes Complete Post-Migration Tasks for Visual Builder Applications Any applications on the Oracle Integration Classic instance that are live will need to be staged and published again after they are migrated to the new instance on Oracle Cloud Infrastructure.Developers can lock a live visual application to prevent changes to live application data, and then import the live data to the new version of the application on Oracle Cloud Infrastructure.After the live data is imported and the application is published, users can be instructed to use the new version of the live app.For users who access a web application, youll need to communicate the new URL that replaces the URL they used previously to access their web applications.For mobile applications, youll need to rebuild and republish your mobile apps to the app store(s) where you initially published it or use whatever mechanism you used previously to distribute the mobile app.Do this so users can update the mobile app on their device to a version of the app that was built using Oracle Visual Builder on Oracle Cloud Infrastructure.Lock the Live Visual Builder Application If you are migrating an application that is a live application, you can lock the live application to prevent any users from using the application while you migrate it to your new instance. |
Follow Migration Best Practices for Processes Follow best practices whenever possible after migration to Oracle Integration.Wrap all rules and policy logic into decision models rather than Oracle Business Rules.While you are able to create integrations using REST and SOAP connectors in process applications, it is recommended that you create all integrations in the OIC IntegrationsChapter 4 Complete Post-Migration Tasks for Processes 4-3area instead.From there, you can easily select them for use in structured and dynamic processes.This practice centralizes all integration efforts in the OIC Integrations area.Among many updates, Oracle Integration provides a new Task List, accessed on the Home page by choosing My Tasks .It provides a lighter weight interface with better performance.My Tasks works best for end users Workspace works best for advanced users for back office and tracking purposes Complete Post-Migration Tasks for Visual Builder Applications Any applications on the Oracle Integration Classic instance that are live will need to be staged and published again after they are migrated to the new instance on Oracle Cloud Infrastructure.Developers can lock a live visual application to prevent changes to live application data, and then import the live data to the new version of the application on Oracle Cloud Infrastructure.After the live data is imported and the application is published, users can be instructed to use the new version of the live app.For users who access a web application, youll need to communicate the new URL that replaces the URL they used previously to access their web applications.For mobile applications, youll need to rebuild and republish your mobile apps to the app store(s) where you initially published it or use whatever mechanism you used previously to distribute the mobile app.Do this so users can update the mobile app on their device to a version of the app that was built using Oracle Visual Builder on Oracle Cloud Infrastructure.Lock the Live Visual Builder Application If you are migrating an application that is a live application, you can lock the live application to prevent any users from using the application while you migrate it to your new instance.To lock an application: 1.Open Visual Builder on Oracle Integration Classic. |
Wrap all rules and policy logic into decision models rather than Oracle Business Rules.While you are able to create integrations using REST and SOAP connectors in process applications, it is recommended that you create all integrations in the OIC IntegrationsChapter 4 Complete Post-Migration Tasks for Processes 4-3area instead.From there, you can easily select them for use in structured and dynamic processes.This practice centralizes all integration efforts in the OIC Integrations area.Among many updates, Oracle Integration provides a new Task List, accessed on the Home page by choosing My Tasks .It provides a lighter weight interface with better performance.My Tasks works best for end users Workspace works best for advanced users for back office and tracking purposes Complete Post-Migration Tasks for Visual Builder Applications Any applications on the Oracle Integration Classic instance that are live will need to be staged and published again after they are migrated to the new instance on Oracle Cloud Infrastructure.Developers can lock a live visual application to prevent changes to live application data, and then import the live data to the new version of the application on Oracle Cloud Infrastructure.After the live data is imported and the application is published, users can be instructed to use the new version of the live app.For users who access a web application, youll need to communicate the new URL that replaces the URL they used previously to access their web applications.For mobile applications, youll need to rebuild and republish your mobile apps to the app store(s) where you initially published it or use whatever mechanism you used previously to distribute the mobile app.Do this so users can update the mobile app on their device to a version of the app that was built using Oracle Visual Builder on Oracle Cloud Infrastructure.Lock the Live Visual Builder Application If you are migrating an application that is a live application, you can lock the live application to prevent any users from using the application while you migrate it to your new instance.To lock an application: 1.Open Visual Builder on Oracle Integration Classic.2.On the Visual Applications home page, open the Application Options menu for the live application you want to lock and select Lock . |
While you are able to create integrations using REST and SOAP connectors in process applications, it is recommended that you create all integrations in the OIC IntegrationsChapter 4 Complete Post-Migration Tasks for Processes 4-3area instead.From there, you can easily select them for use in structured and dynamic processes.This practice centralizes all integration efforts in the OIC Integrations area.Among many updates, Oracle Integration provides a new Task List, accessed on the Home page by choosing My Tasks .It provides a lighter weight interface with better performance.My Tasks works best for end users Workspace works best for advanced users for back office and tracking purposes Complete Post-Migration Tasks for Visual Builder Applications Any applications on the Oracle Integration Classic instance that are live will need to be staged and published again after they are migrated to the new instance on Oracle Cloud Infrastructure.Developers can lock a live visual application to prevent changes to live application data, and then import the live data to the new version of the application on Oracle Cloud Infrastructure.After the live data is imported and the application is published, users can be instructed to use the new version of the live app.For users who access a web application, youll need to communicate the new URL that replaces the URL they used previously to access their web applications.For mobile applications, youll need to rebuild and republish your mobile apps to the app store(s) where you initially published it or use whatever mechanism you used previously to distribute the mobile app.Do this so users can update the mobile app on their device to a version of the app that was built using Oracle Visual Builder on Oracle Cloud Infrastructure.Lock the Live Visual Builder Application If you are migrating an application that is a live application, you can lock the live application to prevent any users from using the application while you migrate it to your new instance.To lock an application: 1.Open Visual Builder on Oracle Integration Classic.2.On the Visual Applications home page, open the Application Options menu for the live application you want to lock and select Lock .3.Click Lock in the Confirm Lock Application dialog box. |
From there, you can easily select them for use in structured and dynamic processes.This practice centralizes all integration efforts in the OIC Integrations area.Among many updates, Oracle Integration provides a new Task List, accessed on the Home page by choosing My Tasks .It provides a lighter weight interface with better performance.My Tasks works best for end users Workspace works best for advanced users for back office and tracking purposes Complete Post-Migration Tasks for Visual Builder Applications Any applications on the Oracle Integration Classic instance that are live will need to be staged and published again after they are migrated to the new instance on Oracle Cloud Infrastructure.Developers can lock a live visual application to prevent changes to live application data, and then import the live data to the new version of the application on Oracle Cloud Infrastructure.After the live data is imported and the application is published, users can be instructed to use the new version of the live app.For users who access a web application, youll need to communicate the new URL that replaces the URL they used previously to access their web applications.For mobile applications, youll need to rebuild and republish your mobile apps to the app store(s) where you initially published it or use whatever mechanism you used previously to distribute the mobile app.Do this so users can update the mobile app on their device to a version of the app that was built using Oracle Visual Builder on Oracle Cloud Infrastructure.Lock the Live Visual Builder Application If you are migrating an application that is a live application, you can lock the live application to prevent any users from using the application while you migrate it to your new instance.To lock an application: 1.Open Visual Builder on Oracle Integration Classic.2.On the Visual Applications home page, open the Application Options menu for the live application you want to lock and select Lock .3.Click Lock in the Confirm Lock Application dialog box.On the Visual Applications home page, the status of the app is now Live Locked. |
This practice centralizes all integration efforts in the OIC Integrations area.Among many updates, Oracle Integration provides a new Task List, accessed on the Home page by choosing My Tasks .It provides a lighter weight interface with better performance.My Tasks works best for end users Workspace works best for advanced users for back office and tracking purposes Complete Post-Migration Tasks for Visual Builder Applications Any applications on the Oracle Integration Classic instance that are live will need to be staged and published again after they are migrated to the new instance on Oracle Cloud Infrastructure.Developers can lock a live visual application to prevent changes to live application data, and then import the live data to the new version of the application on Oracle Cloud Infrastructure.After the live data is imported and the application is published, users can be instructed to use the new version of the live app.For users who access a web application, youll need to communicate the new URL that replaces the URL they used previously to access their web applications.For mobile applications, youll need to rebuild and republish your mobile apps to the app store(s) where you initially published it or use whatever mechanism you used previously to distribute the mobile app.Do this so users can update the mobile app on their device to a version of the app that was built using Oracle Visual Builder on Oracle Cloud Infrastructure.Lock the Live Visual Builder Application If you are migrating an application that is a live application, you can lock the live application to prevent any users from using the application while you migrate it to your new instance.To lock an application: 1.Open Visual Builder on Oracle Integration Classic.2.On the Visual Applications home page, open the Application Options menu for the live application you want to lock and select Lock .3.Click Lock in the Confirm Lock Application dialog box.On the Visual Applications home page, the status of the app is now Live Locked.Users are not able to use the app to edit data while it is locked. |
Among many updates, Oracle Integration provides a new Task List, accessed on the Home page by choosing My Tasks .It provides a lighter weight interface with better performance.My Tasks works best for end users Workspace works best for advanced users for back office and tracking purposes Complete Post-Migration Tasks for Visual Builder Applications Any applications on the Oracle Integration Classic instance that are live will need to be staged and published again after they are migrated to the new instance on Oracle Cloud Infrastructure.Developers can lock a live visual application to prevent changes to live application data, and then import the live data to the new version of the application on Oracle Cloud Infrastructure.After the live data is imported and the application is published, users can be instructed to use the new version of the live app.For users who access a web application, youll need to communicate the new URL that replaces the URL they used previously to access their web applications.For mobile applications, youll need to rebuild and republish your mobile apps to the app store(s) where you initially published it or use whatever mechanism you used previously to distribute the mobile app.Do this so users can update the mobile app on their device to a version of the app that was built using Oracle Visual Builder on Oracle Cloud Infrastructure.Lock the Live Visual Builder Application If you are migrating an application that is a live application, you can lock the live application to prevent any users from using the application while you migrate it to your new instance.To lock an application: 1.Open Visual Builder on Oracle Integration Classic.2.On the Visual Applications home page, open the Application Options menu for the live application you want to lock and select Lock .3.Click Lock in the Confirm Lock Application dialog box.On the Visual Applications home page, the status of the app is now Live Locked.Users are not able to use the app to edit data while it is locked.Export Application Data From the Live Database You can export all the data contained in your database as CSV files. |
It provides a lighter weight interface with better performance.My Tasks works best for end users Workspace works best for advanced users for back office and tracking purposes Complete Post-Migration Tasks for Visual Builder Applications Any applications on the Oracle Integration Classic instance that are live will need to be staged and published again after they are migrated to the new instance on Oracle Cloud Infrastructure.Developers can lock a live visual application to prevent changes to live application data, and then import the live data to the new version of the application on Oracle Cloud Infrastructure.After the live data is imported and the application is published, users can be instructed to use the new version of the live app.For users who access a web application, youll need to communicate the new URL that replaces the URL they used previously to access their web applications.For mobile applications, youll need to rebuild and republish your mobile apps to the app store(s) where you initially published it or use whatever mechanism you used previously to distribute the mobile app.Do this so users can update the mobile app on their device to a version of the app that was built using Oracle Visual Builder on Oracle Cloud Infrastructure.Lock the Live Visual Builder Application If you are migrating an application that is a live application, you can lock the live application to prevent any users from using the application while you migrate it to your new instance.To lock an application: 1.Open Visual Builder on Oracle Integration Classic.2.On the Visual Applications home page, open the Application Options menu for the live application you want to lock and select Lock .3.Click Lock in the Confirm Lock Application dialog box.On the Visual Applications home page, the status of the app is now Live Locked.Users are not able to use the app to edit data while it is locked.Export Application Data From the Live Database You can export all the data contained in your database as CSV files.The export tool creates one CSV file for each of the custom business objects in your database and packages the files as a ZIP archive. |
My Tasks works best for end users Workspace works best for advanced users for back office and tracking purposes Complete Post-Migration Tasks for Visual Builder Applications Any applications on the Oracle Integration Classic instance that are live will need to be staged and published again after they are migrated to the new instance on Oracle Cloud Infrastructure.Developers can lock a live visual application to prevent changes to live application data, and then import the live data to the new version of the application on Oracle Cloud Infrastructure.After the live data is imported and the application is published, users can be instructed to use the new version of the live app.For users who access a web application, youll need to communicate the new URL that replaces the URL they used previously to access their web applications.For mobile applications, youll need to rebuild and republish your mobile apps to the app store(s) where you initially published it or use whatever mechanism you used previously to distribute the mobile app.Do this so users can update the mobile app on their device to a version of the app that was built using Oracle Visual Builder on Oracle Cloud Infrastructure.Lock the Live Visual Builder Application If you are migrating an application that is a live application, you can lock the live application to prevent any users from using the application while you migrate it to your new instance.To lock an application: 1.Open Visual Builder on Oracle Integration Classic.2.On the Visual Applications home page, open the Application Options menu for the live application you want to lock and select Lock .3.Click Lock in the Confirm Lock Application dialog box.On the Visual Applications home page, the status of the app is now Live Locked.Users are not able to use the app to edit data while it is locked.Export Application Data From the Live Database You can export all the data contained in your database as CSV files.The export tool creates one CSV file for each of the custom business objects in your database and packages the files as a ZIP archive.To export the database data as a CSV file:Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-41.Open Visual Builder on Oracle Integration Classic. |
Developers can lock a live visual application to prevent changes to live application data, and then import the live data to the new version of the application on Oracle Cloud Infrastructure.After the live data is imported and the application is published, users can be instructed to use the new version of the live app.For users who access a web application, youll need to communicate the new URL that replaces the URL they used previously to access their web applications.For mobile applications, youll need to rebuild and republish your mobile apps to the app store(s) where you initially published it or use whatever mechanism you used previously to distribute the mobile app.Do this so users can update the mobile app on their device to a version of the app that was built using Oracle Visual Builder on Oracle Cloud Infrastructure.Lock the Live Visual Builder Application If you are migrating an application that is a live application, you can lock the live application to prevent any users from using the application while you migrate it to your new instance.To lock an application: 1.Open Visual Builder on Oracle Integration Classic.2.On the Visual Applications home page, open the Application Options menu for the live application you want to lock and select Lock .3.Click Lock in the Confirm Lock Application dialog box.On the Visual Applications home page, the status of the app is now Live Locked.Users are not able to use the app to edit data while it is locked.Export Application Data From the Live Database You can export all the data contained in your database as CSV files.The export tool creates one CSV file for each of the custom business objects in your database and packages the files as a ZIP archive.To export the database data as a CSV file:Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-41.Open Visual Builder on Oracle Integration Classic.2.On the Visual Applications home page, open the visual application and open the Business Objects pane in the Navigator. |
After the live data is imported and the application is published, users can be instructed to use the new version of the live app.For users who access a web application, youll need to communicate the new URL that replaces the URL they used previously to access their web applications.For mobile applications, youll need to rebuild and republish your mobile apps to the app store(s) where you initially published it or use whatever mechanism you used previously to distribute the mobile app.Do this so users can update the mobile app on their device to a version of the app that was built using Oracle Visual Builder on Oracle Cloud Infrastructure.Lock the Live Visual Builder Application If you are migrating an application that is a live application, you can lock the live application to prevent any users from using the application while you migrate it to your new instance.To lock an application: 1.Open Visual Builder on Oracle Integration Classic.2.On the Visual Applications home page, open the Application Options menu for the live application you want to lock and select Lock .3.Click Lock in the Confirm Lock Application dialog box.On the Visual Applications home page, the status of the app is now Live Locked.Users are not able to use the app to edit data while it is locked.Export Application Data From the Live Database You can export all the data contained in your database as CSV files.The export tool creates one CSV file for each of the custom business objects in your database and packages the files as a ZIP archive.To export the database data as a CSV file:Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-41.Open Visual Builder on Oracle Integration Classic.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 . |
For users who access a web application, youll need to communicate the new URL that replaces the URL they used previously to access their web applications.For mobile applications, youll need to rebuild and republish your mobile apps to the app store(s) where you initially published it or use whatever mechanism you used previously to distribute the mobile app.Do this so users can update the mobile app on their device to a version of the app that was built using Oracle Visual Builder on Oracle Cloud Infrastructure.Lock the Live Visual Builder Application If you are migrating an application that is a live application, you can lock the live application to prevent any users from using the application while you migrate it to your new instance.To lock an application: 1.Open Visual Builder on Oracle Integration Classic.2.On the Visual Applications home page, open the Application Options menu for the live application you want to lock and select Lock .3.Click Lock in the Confirm Lock Application dialog box.On the Visual Applications home page, the status of the app is now Live Locked.Users are not able to use the app to edit data while it is locked.Export Application Data From the Live Database You can export all the data contained in your database as CSV files.The export tool creates one CSV file for each of the custom business objects in your database and packages the files as a ZIP archive.To export the database data as a CSV file:Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-41.Open Visual Builder on Oracle Integration Classic.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. |
For mobile applications, youll need to rebuild and republish your mobile apps to the app store(s) where you initially published it or use whatever mechanism you used previously to distribute the mobile app.Do this so users can update the mobile app on their device to a version of the app that was built using Oracle Visual Builder on Oracle Cloud Infrastructure.Lock the Live Visual Builder Application If you are migrating an application that is a live application, you can lock the live application to prevent any users from using the application while you migrate it to your new instance.To lock an application: 1.Open Visual Builder on Oracle Integration Classic.2.On the Visual Applications home page, open the Application Options menu for the live application you want to lock and select Lock .3.Click Lock in the Confirm Lock Application dialog box.On the Visual Applications home page, the status of the app is now Live Locked.Users are not able to use the app to edit data while it is locked.Export Application Data From the Live Database You can export all the data contained in your database as CSV files.The export tool creates one CSV file for each of the custom business objects in your database and packages the files as a ZIP archive.To export the database data as a CSV file:Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-41.Open Visual Builder on Oracle Integration Classic.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. |
Do this so users can update the mobile app on their device to a version of the app that was built using Oracle Visual Builder on Oracle Cloud Infrastructure.Lock the Live Visual Builder Application If you are migrating an application that is a live application, you can lock the live application to prevent any users from using the application while you migrate it to your new instance.To lock an application: 1.Open Visual Builder on Oracle Integration Classic.2.On the Visual Applications home page, open the Application Options menu for the live application you want to lock and select Lock .3.Click Lock in the Confirm Lock Application dialog box.On the Visual Applications home page, the status of the app is now Live Locked.Users are not able to use the app to edit data while it is locked.Export Application Data From the Live Database You can export all the data contained in your database as CSV files.The export tool creates one CSV file for each of the custom business objects in your database and packages the files as a ZIP archive.To export the database data as a CSV file:Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-41.Open Visual Builder on Oracle Integration Classic.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. |
Lock the Live Visual Builder Application If you are migrating an application that is a live application, you can lock the live application to prevent any users from using the application while you migrate it to your new instance.To lock an application: 1.Open Visual Builder on Oracle Integration Classic.2.On the Visual Applications home page, open the Application Options menu for the live application you want to lock and select Lock .3.Click Lock in the Confirm Lock Application dialog box.On the Visual Applications home page, the status of the app is now Live Locked.Users are not able to use the app to edit data while it is locked.Export Application Data From the Live Database You can export all the data contained in your database as CSV files.The export tool creates one CSV file for each of the custom business objects in your database and packages the files as a ZIP archive.To export the database data as a CSV file:Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-41.Open Visual Builder on Oracle Integration Classic.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. |
To lock an application: 1.Open Visual Builder on Oracle Integration Classic.2.On the Visual Applications home page, open the Application Options menu for the live application you want to lock and select Lock .3.Click Lock in the Confirm Lock Application dialog box.On the Visual Applications home page, the status of the app is now Live Locked.Users are not able to use the app to edit data while it is locked.Export Application Data From the Live Database You can export all the data contained in your database as CSV files.The export tool creates one CSV file for each of the custom business objects in your database and packages the files as a ZIP archive.To export the database data as a CSV file:Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-41.Open Visual Builder on Oracle Integration Classic.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. |
2.On the Visual Applications home page, open the Application Options menu for the live application you want to lock and select Lock .3.Click Lock in the Confirm Lock Application dialog box.On the Visual Applications home page, the status of the app is now Live Locked.Users are not able to use the app to edit data while it is locked.Export Application Data From the Live Database You can export all the data contained in your database as CSV files.The export tool creates one CSV file for each of the custom business objects in your database and packages the files as a ZIP archive.To export the database data as a CSV file:Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-41.Open Visual Builder on Oracle Integration Classic.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. |
3.Click Lock in the Confirm Lock Application dialog box.On the Visual Applications home page, the status of the app is now Live Locked.Users are not able to use the app to edit data while it is locked.Export Application Data From the Live Database You can export all the data contained in your database as CSV files.The export tool creates one CSV file for each of the custom business objects in your database and packages the files as a ZIP archive.To export the database data as a CSV file:Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-41.Open Visual Builder on Oracle Integration Classic.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. |
On the Visual Applications home page, the status of the app is now Live Locked.Users are not able to use the app to edit data while it is locked.Export Application Data From the Live Database You can export all the data contained in your database as CSV files.The export tool creates one CSV file for each of the custom business objects in your database and packages the files as a ZIP archive.To export the database data as a CSV file:Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-41.Open Visual Builder on Oracle Integration Classic.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 . |
Users are not able to use the app to edit data while it is locked.Export Application Data From the Live Database You can export all the data contained in your database as CSV files.The export tool creates one CSV file for each of the custom business objects in your database and packages the files as a ZIP archive.To export the database data as a CSV file:Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-41.Open Visual Builder on Oracle Integration Classic.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. |
Export Application Data From the Live Database You can export all the data contained in your database as CSV files.The export tool creates one CSV file for each of the custom business objects in your database and packages the files as a ZIP archive.To export the database data as a CSV file:Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-41.Open Visual Builder on Oracle Integration Classic.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. |
The export tool creates one CSV file for each of the custom business objects in your database and packages the files as a ZIP archive.To export the database data as a CSV file:Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-41.Open Visual Builder on Oracle Integration Classic.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. |
To export the database data as a CSV file:Chapter 4 Complete Post-Migration Tasks for Visual Builder Applications 4-41.Open Visual Builder on Oracle Integration Classic.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 . |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.