1. Building Responsive Applications with Visual Builder Studio
  2. Manage Applications
  3. Preview, Share, and Deploy Visual Applications
  4. Deploy to Test and Production Instances
  5. Deploy a Live Version of an Application

Deploy a Live Version of an Application

When your visual application is fully developed and thoroughly tested, you are ready to deploy a live version of your application to a production instance.

The process to deploy a live version is similar to deploying other application versions, but your project must be configured to build and deploy visual applications to a Visual Builder production instance. See Set Up the Project to Deploy for Production in Administering Visual Builder Studio.

When you are ready to deploy your application to production, you'll want to remove the version that VB Studio includes by default in the application's URL (for example, https://host/something-else/0.1/index.html) and replace it instead with "live" (for example, https://host/something-else/live/index.html). This configuration is controlled by the deployment job used to deploy your visual application and is enabled by default in the Visual-Application-Deploy job that's created for projects that use the Visual Application template.

To remove the version and deploy a live version of an application:

  1. In the left navigator, click Builds Builds.
  2. In the Jobs tab, find your visual application's deployment job, usually the Visual-Application-Deploy job.
  3. Click Configure Configure icon for your deployment job.
  4. On the Job Configuration page, click the Steps tab, deselect the Include the application version in the URL check box, and click Save:

    Deselected application version check box in the Oracle Deployment job

With this configuration, the deployed application will include live in its URL instead of a version number.
Only one version of an app can be live at a time. If you want to make changes to the live version, you’ll need to first update the value of the Version field in the application's Settings editor (which corresponds to the version property in the visual-application.json file).