Visual Builder Tasks

Review the following list to understand the tasks that you need to complete to migrate Visual Builder applications from your Oracle Integration Classic instance to Oracle Cloud Infrastructure.

1. Review the entries for users and roles in Oracle Identity Cloud Service to ensure that the instance of Oracle Identity Cloud Service that the new instance uses matches the entries in the instance of Oracle Identity Cloud Service used by Oracle Integration Classic. This task is not necessary if both old and new instances use the same instance of Oracle Identity Cloud Service. If you use a new instance of Oracle Identity Cloud Service, make sure that your application users are granted access to the new instance with the appropriate roles.
2. For each visual application (and for each version of each visual application that you wants to migrate), export the visual application from the Oracle Integration Classic instance.
3. If you use build tools and pipelines from Oracle Developer Cloud Service, configure build jobs to point to your new instance and rebuild. Otherwise, follow the next steps to manually export and import visual applications.
4. If you use Oracle Developer Cloud Service with a connection to a Git repository to manage visual applications, use Visual Builder's Import menu in the new instance to import the visual application. Each user who collaborates on a Git-managed visual application needs to perform this import. Otherwise, follow the next steps to manually export and import visual applications.
5. For each application (and for each version of each visual application you want to migrate), export the visual application from the old instance.
6. For each visual application, import the visual application into the Oracle Integration instance.

   Note:

   It is not possible today to import a version of a visual application; import always creates a new visual application in the Oracle Integration instance.
7. For each visual application, ensure proper mapping of virtual roles to Oracle Identity Cloud Service groups and app roles.
8. If using team collaboration features, add team members to the newly-imported visual application as necessary.
9. For each visual application, re-enter security-related details for your visual application that are not captured during export from the old instance. This includes any client IDs and basic authentication details, along with build configurations entries needed to build mobile apps.
10. For each visual application, stage and publish the visual application in the Oracle Integration instance.
11. Test the behavior of the migrated visual application. To perform testing, you may want to export application data from the visual application on the classic instance and import it to the new visual application on Oracle Integration. When you complete testing, perform the following post-migration steps to finish the migration of your visual applications.

    If your application is embedded with an iFrame in a Fusion Application, update and test your Fusion Application to ensure your embedded application continues to function post-migration.

12. For each migrated visual application, lock the visual application on the old instance.
13. For each migrated visual application, use the Data Manager screen to export live data from the old instance.
14. For each migrated visual application, use the Data Manager screen to import live data to your new instance.
15. Inform end user clients to use the URL for the new service instance and to update any bookmarks they may have.

    Note:

    This applies to accessing apps through a browser and client applications that may access business object REST APIs hosted in the new instance.
16. Mobile apps that do not use business object REST APIs and bypass Oracle Visual Builder authentication proxy should continue working the same post-migration. Otherwise, build a new version of your mobile app on the new instance and submit it to the appropriate app store for distribution to end users.