Create the VB Studio Instance

You can create only one VB Studio instance in an Oracle Cloud account. You must create it in your tenancy's root compartment.

Note

The VB Studio instance is created in the identity domain you're logged into; there is no mechanism to request a different domain. As long as you have the proper user credentials, you should be able to create the instance in any domain you wish. All users who wish to access the new VB Studio instance must be in its same domain.
  1. In a web browser, go to https://cloud.oracle.com.

    To view the list of supported browsers for the OCI Console, see Supported Browsers.

  2. In Cloud Account Name, enter your Oracle Cloud account or tenancy name and click Next.
  3. On the Single Sign-On (SSO) panel, if required, select your identity provider and click Continue.
  4. Enter your Oracle Cloud account credentials and click Sign In.
    The Oracle Cloud Console, also called the OCI console, opens. If you've recently created your Oracle Cloud account, wait for some time to see your services in the Oracle Cloud Console.
  5. In the upper-left corner, click Navigation Menu the Menu icon.
  6. Select Developer Services and then select Visual Builder Studio.
  7. On the Visual Builder Studio Instances page, from the Compartment drop-down list, select the root compartment.
  8. Click Create VB Studio Instance.
    The Instance Name page is displayed.
  9. In Instance Name, enter the VB Studio's instance name.
  10. The Compartment field always displays the root compartment you selected in step 7.
    This field is read-only. The the root compartment (displayed) is the only compartment allowed.
  11. (Optional) Add one or more tags to this resource.

    Default tags, which help you identify the instance, always get created.

    If you aren't sure whether to add tags, skip this option now. You can always add tags later. For more information about tagging resources, see Resource Tags.

    1. Click Show Advanced Options Show Advanced Options to display the Tag section.
    2. Select the Tag namespace, or select None to apply a free-form tag.
    3. Select or enter the Tag key.
    4. In Tag value, either enter a value or select one from the list.
    5. To apply another tag, click + Additional Tag.
    6. Click Add tag (or Add tags, if you are adding multiple tags).
  12. Click Next.
  13. On the CI/CD Setup page, click the Yes, I authorize this check box.

    This authorizes VB Studio to create and use Compute and Storage instances and automatically creates a policy that authorizes VB Studio to perform the necessary operations in the selected compartment for the CI/CD resources. It also creates a policy authorizing VB Studio to access Oracle Visual Builder and Oracle Integration instances connected to your OCI account. For this automatic policy creation to succeed, the user who creates the instance must also have permissions to manage policies in the root compartment. See Get the Right Roles.

    Typically, tenancy administrators have these permissions, so the easiest way to create a VB Studio instance is to have a tenancy administrator do it. However, if that isn't feasible, it's also possible to create the VB Studio instance without the CI/CD authorization and then set it up later by performing an edit operation.

    Note

    If you want to use the built-in free account's free VM build executor, don't select the authorization check box. See VB Studio's Free VM Build Executor for information about the resources provided with the free VM build executor. Make sure you manually authorize this VB Studio instance to access Visual Builder and Integration instances connected to your OCI account, so you can add these instances to an environment later on.
  14. If you've selected the Yes, I authorize this check box, in Compartment, select the compartment you created to host VB Studio's Compute and Storage instances.
    When you select the check box, the required policies are applied to the selected compartment.
  15. Click the Create Visual Builder Studio button.
Once the service instance is created, click Service Console to open VB Studio's Organization page.
Here's an example:

Description of organization_page_firstaccess.png follows

What Are the Next Steps?

After you create the instance:
  1. You're assigned the DEVELOPER_ADMINISTRATOR IDCS role, which enables you to set up VB Studio, manage the VM build executors, and update the organization details. After you're assigned the role, you become a VB Studio Organization Administrator.
  2. You'll receive an email with the subject Verify your Oracle Visual Builder Studio email. Open the email and click the URL link in the email body to verify your email. If you don't do this, you won't receive important email notifications.
  3. After verifying the email address, you’ll receive another email with the subject Welcome to Oracle Visual Builder Studio. This email contains the VB Studio URL that you can bookmark.
  4. You now need to provide access for additional VB Studio users. See Step 5: Set Up Users and Groups to add individual users or Manage Your Organization's Groups to add groups of users.
  5. Set up VB Studio's build system for CI/CD, which enables your organization's developers to create jobs to build, package, test, and deploy their apps. See Set Up VB Studio for CI/CD.
  6. If your users want to customize Oracle Cloud Applications by creating extensions, see Set Up VB Studio to Extend Oracle Cloud Applications. If they want to develop visual applications and deploy them to Visual Builder runtime instances, see Set Up VB Studio for Developing Visual Applications.
    Note

    If your users are using the Free VM account to develop and deploy visual applications, make sure the VB Studio instance is authorized to access Visual Builder instances connected to your OCI account. Without this authorization, they 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.