Review the Migration Task Flow

Review the following list to understand the tasks that you or an administrator need to complete to migrate web and mobile applications from your Oracle Visual Builder instance to VB Studio by importing an archive.

The task list assumes you have provisioned the new VB Studio instance and Oracle Visual Builder instances that you'll use as the development, test, and production environments.

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 VB Studio. 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 that will be migrated, the project owner should create a new project in VB Studio and add other team members to the project, if any.
3. For each visual application (and for each version of each visual application that you want to migrate), migrate the visual application sources and data from the Oracle Visual Builder instance, either by exporting it as an archive and then importing it, or by cloning the visual application's Git repository.

   Note:

   It is not possible today to import a version of a visual application; import always creates a new visual application in the VB Studio project.
4. Ensure proper mapping of virtual roles to Oracle Identity Cloud Service groups and app roles. You might need to remap the virtual roles in your app's Settings editor if you are migrating an older app.
5. Re-enter the security-related details for your visual application that are not captured when migrated from the old instance. This includes any client IDs and authentication details, along with build configurations details needed to build mobile apps.
6. Update the visual application settings to include a root URL and version number, then merge these changes to your main branch in Git. Unlike apps created in VB Studio, those created in Visual Builder aren't configured with a root URL. You'll need to provide one for your visual application before you deploy it. You'll also want to specify a version number at the same time.
7. Configure the project's build jobs to use the new repository and to deploy to your development, test and production environments.
8. Configure the settings for each of the Oracle Visual Builder environments to ensure that when your application is deployed to the environment it can access required services.
9. Use the build tools in VB Studio to share and publish the visual application to your Oracle Visual Builder environments.
10. Test the behavior of the migrated visual application. To perform testing, you may want to export data from the visual application on the old instance and then import the data into your environments. 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 an Oracle Cloud Application, update and test your Cloud Application to ensure your embedded application continues to function post-migration.

11. For each migrated visual application, lock the live visual application on the old instance.
12. For each migrated visual application, use the Data Manager screen to export the live data from the old instance.
13. For each migrated visual application, use the Deployments screen in VB Studio to import the live data to the Visual Builder instance you are using for production.
14. 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.
15. 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.
16. Migration is complete. Delete the old Oracle Visual Builder instance if you are no longer using it.