Oracle Cloud Infrastructure Documentation

Essential Set-up Tasks

Before you can start setting up or using VB Studio, there are a few tasks that must be performed first:

  1. Make sure you have the FND_ADMINISTER_SANDBOX_PRIV privilege or any of these roles in your development and production instances:
    • APPLICATION ADMINISTRATOR
    • APPLICATION DEVELOPER
    • SALES_ADMINISTRATOR
    • CUSTOMER RELATIONSHIP MANAGEMENT APPLICATION ADMINISTRATOR

    You’ll need these permissions to set up VB Studio and your Oracle Cloud Applications instances, and to deploy an extension to an Oracle Cloud Application environment.

  2. If role synchronization is enabled, the Oracle Cloud Applications roles listed in step 1 are sufficient and will grant VB Studio access after 30 minutes. If role synchronization is disabled, you need to use the IDCS console and explicitly grant VB Studio access by assigning the DEVELOPER_USER or DEVELOPER_ADMIN VB Studio role in your instance.

    See Assign VB Studio Roles in Oracle Identity Cloud Service (IDCS). Without these role assignments, the first user (you or one of your users) who begins to create a simple extension will see the error, "You are not a member of this Organization."

    If you can't do this yourself, please consult with the infrastructure administrator at your site who has the necessary IDCS identity administrator privileges.

  3. If your Oracle Cloud Applications instances restrict ingress IP access, you must add your VB Studio infrastructure IP address to the list of allowed IP addresses in your Web Application Firewall (WAF) and/or Location Based Access Control (LBAC) configuration.
    If you have done this, but are still experiencing access problems please check the following:
    • If you have LBAC enabled, but you haven't added your VB Studio IP address to the LBAC allow list, your users may receive error messages that say: “We are not able to determine the status of environment <environment name>. We couldn't retrieve the list of sandboxes from <instance name> due to :Forbidden.”
    • If you see an "Unauthorized" status in the Service Instances tab on VB Studio's Environments page, the issue could be related to LBAC or WAF. However, it could also be an issue with your credentials not having access to the FA status endpoints. Only certain endpoints, not all of them, are protected by the LBAC configuration.
    • If you are still experiencing problems, you should contact your Oracle Support representative and file an SR so Oracle can assist you in setting up this access to VB Studio.
  4. Ask the Oracle Cloud Applications administrator to enable Cross-Origin Resource Sharing (CORS) by adding the VB Studio's root URL to the Oracle Cloud Application's ORA_CORS_ORIGINS profile option. This option is used to specify which domains can talk to each other.
    Note

    Production to Test (P2T) and other operations that replace the database may cause the profile option value to change. If you perform any operation that replaces the database, you must repeat these steps.

    To enable CORS, the Oracle Cloud Applications admin must:

    1. Open VB Studio from the Oracle Cloud Applications instance and copy the VB Studio URL from the browser's address bar.
    2. In the Oracle Cloud Applications instance, click Navigator the Menu icon .
    3. Under Others, click Setup and Maintenance.
    4. On the right side of the page, click Tasks,Tasks icon then click Search.
    5. In the search box, enter Manage Administrator Profile Values and click the Search icon.
    6. In the search results, click Manage Administrator Profile Values.
    7. In Profile Options Code, enter ORA_CORS_ORIGINS, then click Search.
    8. Under ORA_CORS_ORIGINS: Profile Values, click New.
    9. In Profile Level, select Site.
    10. In Profile Value, add VB Studio’s root URL.

      The URL must be separated from other values by a space. For example, if the full VB Studio URL is https://abcd-test-DEVCSAPP-07012210-2070-abcd.developer.ocp.oraclecloud.com:443/abcd-test-devcsapp-07012210-2070-abcd, the root URL is simply https://abcd-test-DEVCSAPP-07012210-2070-abcd.developer.ocp.oraclecloud.com.

    11. Before you finish the CORS setup, you should check the CORS headers to be added.

      Although all of the other CORS options should be configured by default, in every pod, some of these settings may be missing or may have been erased inadvertently. See Configure Cross-Origin Resource Sharing for additional information about all the settings that can be configured, including a list of acceptable values for each option.

    12. Click Save and Close.