Version 2501 of Visual Builder Studio offers a new approach for mapping Visual Builder instances as environments that can be used during development and deployment stages. The new approach leverages OCI resources as the way to define the connection from VB Studio to VB. This applies both to standalone VB instances and to instances of VB that are part of Oracle Integration. We covered how to connect to OIC gen3 instances here.
Here are the steps for mapping your Oracle Visual Builder instances in Oracle Visual Builder Studio:
Getting Permissions
VB Studio can now use OCI Resources as the approach for discovering Integration and Visual Builder instances (replacing the older IDCS resources approach). To allow your VB Studio to discover these you'll need to define a security policy in your cloud tenancy.
As a first step find out and copy the OCID identifying your VB Studio instance – you'll use it in the policies you are about to define.
From the Cloud console, navigate to the policies section of the "Identity and Security" section. Here you'll want to either modify the policy defined for your VB Studio instance (search the list of available policies) or create a new one to add three new policies as explained here. Use the OCID you copied in the policies.
Adding Instances to Environments
Now that your VB Studio has the right policies in place, you should be able to discover Visual Builder instances in your tenancy and add them to environments in your project.
Define or edit an Environment and click the add instance button – VB Studio queries OCI to find out the instance you can access. For VB instances that are part of Oracle Integration, you'll see separate entries for Integration instances and Visual Builder instances (unlike in the days of OIC gen2 which had them combined). Add to your environment the VB instance you are interested in integrating with. Each environment can have a single VB instance in it.
Important note – if the instances that you are after are in a different region or compartment, switch the region being searched by click the pencil icon on the left and picking a different region from the list.
Once added you'll see the status for your instances, and will also be able to directly navigate to their home pages from the environments tab:
Once the instance is mapped in an environment you'll be able manage the full development and deployment lifecycle of apps on it.
Note that you can still add VB instance using their URL and providing credentials if you don't have the right policies in place to inspect the OCI resources.