1. Administering Visual Builder Studio
  2. Set Up VB Studio to Extend Oracle Cloud Applications
  3. Advanced Administrator Tasks
  4. Set Up the Project to Deploy to Production
  5. Add the Oracle Cloud Application's Production Instance to an Environment

Add the Oracle Cloud Application's Production Instance to an Environment

Only one Oracle Cloud Applications instance can be added to an environment. As the Development environment already points to the TEST instance (or DEV, if you asked Oracle to re-associate it), you must create a new environment for the PROD instance.

To create a new environment for the PROD instance:

  1. In the VB Studio navigator, click Environments.
  2. Click + Create Environment.
  3. In the Service Instances tab, click + Add Instance.
  4. In the Add Service Instances dialog box, select the Oracle Cloud Applications option button.
  5. Under Authentication Method, select the Application Credentials option.
  6. In Base URL, enter the Oracle Cloud Application's base URL.
  7. In Instance Name, if required, update the instance's display name. The name will be displayed in the Service Instances tab.

  8. In Username and Password, enter the credentials of a user who can access this Oracle Cloud Applications instance.

    These credentials must be those of a local user, not a federated identity, and must not require multi-factor authentication.

  9. Under Authorization Type, select OAuth 2.0 or Basic.
  10. Click Add.

  11. If you chose OAuth 2.0 as the Authorization Type, you may be prompted to authorize IDCS to acquire OAuth tokens for accessing the target instance. Click Authorize when prompted, then sign in to IDCS with credentials to access the Oracle Cloud Applications instance.

    Note:

    OAuth tokens (access and refresh) are typically cycled during regular use. If a token expires during an extended period of inactivity, like when you're away on vacation, click Actions Three horizontal dots and select Renew OAuth Access to restart the OAuth workflow.

    Note that the username that shows in the environment Details section isn't the VB Studio user, but the user for the connected instance whose credentials were used to create the connection's refresh token. The details don't show the VB Studio username, which isn't relevant for a 3-legged OAuth Environment connection.

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 Oracle Cloud Applications instance, but can't access it. In this case, click Actions Three horizontal dots and select Remove to remove the Oracle Cloud Applications instance from the environment, and then click Add to add it again.