Get Access to Visual Builder Instances

You can deploy a visual application to a separate Visual Builder instance—you cannot deploy to Visual Builder Studio itself.

If you don’t already have an instance to deploy to:

1. Create a Visual Builder Service Instance. To create an instance, you’ll need the IDCS VISUALBUILDER_ENTITLEMENT_ADMINISTRATOR service role.
2. Add an IDCS User to Your Cloud Account and assign the user a Visual Builder role to connect and deploy applications.

You’ll also need to configure the instance once it’s created. If you’re a Visual Builder runtime administrator, sign in to the Visual Builder runtime to complete these tasks, as described in Administering Oracle Visual Builder, Gen 2:

• Access Instance Settings
• Configure Security Options for Applications
• Set Page Messages for Access Denied Errors
• Allow Other Domains Access to Services
• Switch to Your Own Oracle DB Instance
• Reset an Expired Password or ATP Wallet for Your Oracle DB Instance
• Manage Self-signed Certificates
• Configure Support for a Custom Domain

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, your Visual Builder administrator must manually add the VB Studio hostname to the allow list for each Visual Builder instance. For more information, see Add an Allowed Origins Domain.
• If you need to create a Visual Builder instance to deploy to, create it in the same Oracle Cloud account and identity domain as the VB Studio instance you are developing the visual application with. When you need to deploy your app for testing or to go live, you’ll need to create instances for those environments using working credentials in different identity domains. See Create a VB Studio Instance in Your Oracle Cloud Account.
• Follow your organization’s guidelines to create and set up Visual Builder instances for deployment targets. Your guidelines may suggest that you create instances for different deployment environments, such as development, integration, test, pre-stage, stage, pre-production, and production. You can create these instances in different identity domains or in a common identity domain. This documentation assumes that you have created and set up Visual Builder instances you can deploy to in your development and production environments, where each instance is in a different identity domain. To deploy your visual application to Visual Builder development and production instances, you’ll need credentials to access them. You’ll be prompted for these credentials when you set up the instances or when you perform a manual deployment to those instances.

Make sure your VB Studio instance is authorized to access Visual Builder instances connected to your OCI account. Without this authorization, your users won’t be able to create environments with a Visual Builder instance to deploy their visual applications. See Authorize VB Studio to Access Visual Builder and Integration Instances on the steps to complete this authorization.