1. Administering Visual Builder Studio
  2. Set Up VB Studio for Developing Visual Applications
  3. Set Up Additional Deployment Instances

Set Up Additional Deployment Instances

If you want to deploy a visual application to additional Visual Builder instances (for example, a production or QA instance), you must create a separate VB Studio environment and add the instance to it. You can add only one Visual Builder instance to an environment.

  1. In the left navigator, click Environments Environments.
  2. Click + Create Environment.
    In Environment Name and Description, enter a unique name and description, and click Create.
  3. In the Service Instances tab, click Add Instance.
  4. In the Add Service Instances dialog box, select the Visual Builder and Oracle Integration option button.
  5. Do one of the following:
    • If the Visual Builder instance is in the same identity domain, select the instance you want to deploy to from the list of available instances displayed on the right and click Add.
    • If the Visual Builder instance is in a different identity domain, add the service instance using the Visual Builder instance's base URL and credentials that can access the instance:
      1. Select the Visual Builder Credentials option.
      2. In Base URL, enter the base Visual Builder instance's URL. For example: https://yourserver.
      3. In Instance Name, if required, update the instance's display name. The name will be displayed in the Service Instances tab.
      4. In Username and Password, enter the credentials of a user who can access the Visual Builder instance.
      5. Click Add.

After you add a Visual Builder instance to an environment, the Service Instances tab displays a tile that shows basic information, such as status and response time, about the instance. Click Expand Details Details to see additional information (Visual Builder release version, Service URI, etc.) or click the Home Page link to visit its home page URL.

If the newly added instance stays in the Unknown status for some time, it usually indicates that the IDCS Application provisioning may have failed. VB Studio added the Visual Builder instance but can't access it. In such a case, click Actions Three horizontal dots and select Remove to delete the Visual Builder instance from the environment, and then click Add to add it again.