About Downtime Requirements

For most of the migration process, the availability of your existing Oracle Visual Builder applications is not affected.

Your Oracle Visual Builder instance continues to run and can serve client requests while you complete the pre-migration tasks in Oracle Visual Builder Studio. Some downtime is required after you complete the pre-migration tasks as you need to transfer application data from the Oracle Visual Builder instance to Oracle Visual Builder Studio. Before you attempt to transfer the application data, lock the live application on the Oracle Visual Builder instance so that application users do not update data while you complete the transfer.

You’ll need to communicate this downtime to application users and also the new URL that they need to access their application once you complete post-migration tasks on Oracle Visual Builder Studio. Typically, the URL part that changes is the part that identifies the host name where the Oracle Visual Builder and Oracle Visual Builder Studio instances are hosted, for example:

https://oci-oldinstance/ic/builder/rt/visualapp/live/webApps/appname/

and

https://oci-newinstance/ic/builder/rt/visualapp/live/webApps/appname/

For mobile apps that consume REST endpoints from custom business objects that you migrate to a new Oracle Visual Builder instance as the runtime, you’ll need to update the appropriate app store with a new version of the mobile app that you have built using VB Studio. This requirement extends to any client application that consumes REST endpoints from business objects that you migrate to a new instance. You’ll need to update these client applications so that REST calls continue to work post-migration.