Manage Oracle Integration Projects

These are the steps you'll need to use to import and export Oracle Integration projects using build jobs in VB Studio:

Step	Description	See this topic
Configure a build job to export an Integration project from an Oracle Integration instance.	Creates and executes a job to export an Integration project from an Oracle Integration instance.	Configure a Job to Export an Integration Project
Configure a build job to import an Integration project to an Oracle Integration instance.	Creates and executes a job to import an Integration project to an Oracle Integration instance.	Configure a Job to Import an Oracle Integration Project
Optional: Configure a build job to delete an Integration project that's no longer needed.	Creates and executes a job to delete an Integration project on an Oracle Integration instance.	Configure a Job to Delete an Integration Project

Configure a Job to Export an Integration Project

You can create and execute a job that exports an Integration project from a source Oracle Integration instance to a target Oracle Integration instance.

To configure a build job that exports an Integration project from an Oracle Integration instance:

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.

   The job configuration page is displayed.

7. Click the Steps tab.
8. From Add Step, select Oracle Integration, and then select Export Project.
9. In Source Instance , select the Oracle Integration instance from which you’ll be performing the export operation.
10. In the Authorization section, Use OAuth is selected by default. You can also select Use Basic, but OAuth is the recommended authorization method (and the only method supported for Oracle Integration 3 instances). You should only use Basic authentication if you run into issues with setting up an OAuth connection and aren't on an Oracle Integration 3 instance.

    • For Use OAuth, the Authorization is required message displayed before authorization indicates that this build step needs to be authorized, either by clicking the Authorize button or by running the build manually and, when prompted, entering the credentials of a user who has permissions to perform Oracle Integration operations. After authorization, the Authorization has been provided message and the Renew Authorization button are displayed.

      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).

    • If you select Use Basic, in Username and Password, provide the credentials of a user who has permissions to perform Oracle Integration operations.

11. In Project Id, provide the identifier of the project you'd like to export from the integration as defined in the source Oracle Integration service instance.

    You can also click Search and open the Search Projects dialog to get a list of integration projects in your instance (if you used Basic authentication, you'll need to specify credentials to see this list), or narrow your search by entering a prefix in the Search field. For example, if you enter "COUNTRYINFO", a list of integration projects that contain "COUNTRYINFO" will be displayed.

    If you selected an integration by using the Search Projects dialog, the Project Id will be filled in automatically.

12. The Archive Filename is generated based on the Project Id.
13. Click Save.

Configure a Job to Import an Oracle Integration Project

You can create and execute a job that imports an Oracle Integration project from one Oracle Integration instance to another Oracle Integration instance.

To configure a build job that imports an Oracle Integration project from another Oracle Integration instance:

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.

   The job configuration page is displayed.

7. From the Before Build tab select Before Build Action and then select Copy Artifacts.
   1. In From job, enter the previous Integration Export job you want to import.
   2. In Which build, select Last successful build.
8. Click the Steps tab.
9. From Add Step, select Oracle Integration, and then select Import Project.
10. In Target Instance , select the Oracle Integration instance to which the project will be imported.
11. In the Authorization section, Use OAuth is selected by default. You can also select Use Basic, but OAuth is the recommended authorization method (and the only method supported for Oracle Integration 3 instances). You should only use Basic authentication if you run into issues with setting up an OAuth connection and aren't on an Oracle Integration 3 instance.

    • For Use OAuth, the Authorization is required message displayed before authorization indicates that this build step needs to be authorized, either by clicking the Authorize button or by running the build manually and, when prompted, entering the credentials of a user who has permissions to perform Oracle Integration operations. After authorization, the Authorization has been provided message and the Renew Authorization button are displayed.

      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).

    • If you select Use Basic, in Username and Password, provide the credentials of a user who has permissions to perform Oracle Integration operations.

12. In Import Archive Filename, enter the name and version number of the archive file (with .car extension) that contains the integration project to import.
13. Click Save.

Configure a Job to Delete an Integration Project

You may want to configure a build job to delete an Integration project from an Oracle Integration instance.

To configure a build job that deletes an Integration project from an Oracle Integration instance:

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.

   The job configuration page is displayed.

7. Click the Steps tab.
8. From Add Step, select Oracle Integration, and then select Delete Project.
9. In Target Instance, select the environment that points to the Oracle Integration instance from which you want the Integration project removed.
10. In the Authorization section, Use OAuth is selected by default. You can also select Use Basic, but OAuth is the recommended authorization method (and the only method supported for Oracle Integration 3 instances). You should only use Basic authentication if you run into issues with setting up an OAuth connection and aren't on an Oracle Integration 3 instance.

    • For Use OAuth, the Authorization is required message displayed before authorization indicates that this build step needs to be authorized, either by clicking the Authorize button or by running the build manually and, when prompted, entering the credentials of a user who has permissions to perform Oracle Integration operations. After authorization, the Authorization has been provided message and the Renew Authorization button are displayed.

      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).

    • If you select Use Basic, in Username and Password, provide the credentials of a user who has permissions to perform Oracle Integration operations.

11. In Project Id, provide the identifier for the integration project as defined in the Oracle Integration service instance.

    You can also click Search and open the Search Projects dialog to get a list of integration projects in your instance (if you used Basic authentication, you'll need to specify credentials to see this list), or narrow your search by entering a prefix in the Search field. For example, if you enter "Hello", a list of Integration projects that contain "Hello" will be displayed.

    If you selected an integration by using the Search Projects dialog, the Project Id will be filled in automatically.

12. Click Save.