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 Instance dialog box, select Oracle Cloud Applications.
  5. Under Add Instance Using, select Application Credentials.
  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 (default) and click Add.
    Note

    OAuth is the recommended authorization type. Use Basic authentication only if you run into issues with setting up an OAuth connection.
  10. If you chose OAuth 2.0 as the Authorization Type, you may be prompted for authorization to acquire OAuth tokens for accessing the target instance. Click Authorize when prompted, then sign in with credentials to access the Oracle Cloud Applications instance.

    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.

    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 Three horizontal dots and select Renew OAuth Access.

    Note

    Service administrators can control the OAuth access or refresh token's expiration in the IDCS resource app, specifically Fusion Applications Cloud Service under Oracle Cloud Services in your identity domain's resource app. See Edit High-Level Information for Oracle Applications.

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.

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