Package, Deploy, and Manage Visual Applications

From the Steps tab on the job’s configuration page, you can create a Visual Application Package job that packages a visual application build artifact and a Deploy job that deploys the build artifact to a Visual Builder development instance, production instance, or any other instance. You can then add these jobs to a pipeline and run them in sequence.

You can deploy a visual application to a standalone Visual Builder instance or to a Visual Builder instance that’s part of Oracle Integration.

It’s important to keep these things in mind before you deploy a visual application to a Visual Builder instance:

• The Visual Builder instance must be version 19.4.3.1, or later.

• To ensure that business objects work properly, Visual Builder administrator must manually add the VB Studio hostname to the list of domains that are allowed access for each Visual Builder instance. See Allow Other Domains Access to Services in Administering Oracle Visual Builder in Oracle Integration 3.

Deployed visual applications can be viewed from the Deployments tab on the Environments page and can be undeployed manually from there too, if they are deployed to a Visual Builder instance that is in the same identity domain as VB Studio. If a visual application is deployed to a Visual Builder instance that is in a different identity domain than VB Studio, you’ll have to create and use a Visual Application build step to undeploy the deployed visual application.