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 .
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. Locate and add your Visual Builder instance:
   • With Instance Type set to Visual Builder and Add Instance Using set to Instance List (preferred), select your Visual Builder instance and click Add.
   • If you don't see the instance you want to add (because it's connected to a different OCI account), select the Authentication method as Visual Builder Credentials. In Base URL, enter the Visual Builder instance's URL; update the Instance Name if you want; enter the credentials of a user who can access the Visual Builder instance in Username and Password; and click Add.

   If your target instance in a different identity domain than your VB Studio instance, OAuth tokens (via three-legged OAuth flows) are used to secure programmatic access to the instance. Before any OAuth tokens can be created, you must provide authorization to acquire OAuth tokens. Click Authorize when prompted, then sign in with credentials to connect and deploy to the instance.

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 Details to see additional information (Visual Builder release version, Instance URL, 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 IDCS Application provisioning may have failed. VB Studio added the Visual Builder instance but can't access it. In such a case, click Actions and select Remove to delete the Visual Builder instance from the environment, and then click Add to add it again.

Note

OAuth tokens (access and refresh) are cycled during regular use. A refresh token is used to obtain an access token whenever a user accesses the target instance. This refresh token is typically valid for seven days. (The token expiration time is set in the IDCS resource app and may be different based on your security requirements.) If the user authenticates with the target instance within the seven-day period, the active refresh token generates a new access token and a new refresh token. This cycle continues indefinitely as long as the refresh token stays valid. If the refresh token expires during extended periods of inactivity (say, when you're away on vacation), click Actions and select Renew OAuth Access.

Once you're done, the Recent Activities feed on the Project Home page lists the newly created environment along with the Visual Builder instance you added.