The sandbox deployment job deploys the extension's artifact that was generated in the sandbox packaging job to the Oracle Cloud Applications production instance's sandbox. Before you create the job, make sure you have credentials that VB Studio can use to access the Oracle Cloud Applications production instance's sandbox.

1. In the left navigator, click Builds .
2. In the Jobs tab, click + Create Job.
3. In the New Job dialog box, in Name, enter a unique name.
4. In Description, enter the job's description.
5. In Template, select the System Default OL7 for Visual Builder template.
6. Click Create.
7. Click Configure .
8. Click the Before Build tab.
9. From Add Before Build Action, select Copy Artifacts.
10. In From Job, select the packaging job that generated the extension's artifact.
11. In Which Build, select one of the following:
    • Last successful build (default)
    • Last keep forever build
    • Upstream build in this pipeline instance
    • Specified by permalink
    • Specific build
    • Specified by build parameter

    Depending on what you select, you may be prompted to select which permalink, build, or build parameter you want to be used.
12. Leave other fields with their default or empty values.
13. Click the Steps tab.
14. From Add Step, select Application Extension, and then select Deploy.

    This image shows the Application Extension Deployment section that's been partially filled in.

    
    
    Description of the illustration oracle-deploy-build-step.png
    

15. In Target Instance, select the environment with the Oracle Cloud Application's production instance.
16. In the Authorization section, specify the authorization type to run this build step. With Use OAuth selected by default, you'll see the Authorization is required message, indicating that this build step needs a one-time authorization to handle OAuth requests to your environment's Oracle Cloud Applications instance. Click Authorize and enter credentials to access your Oracle Cloud Applications instance; you can also run the job manually and enter the credentials when prompted.

    Either way, it is recommended that you authorize your OAuth connection during initial configuration. If you skip this step, you won't be able to publish your changes from the Designer and will need to complete the required authorization before attempting to deploy changes.

    Once authorized, the Authorization has been provided message shows.

    Note
    
    OAuth is the recommended authorization type. Use Basic authentication only if you run into issues with setting up an OAuth connection. To use Basic authentication, select Use Basic, then enter the credentials of a user who can access the Oracle Cloud Applications instance in Username and Password. These credentials must be those of a local user, not a federated identity, and must not require multi-factor authentication.

    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 Renew Authorization (or run the job manually, so you're prompted to authorize any expired OAuth tokens).

17. The Build Artifact field should show the same artifact name that was used in the packaging build step. Confirm this value, especially if the packaging job used an artifact name other than the default, extension.vx.
18. Click Save.