Manage Oracle Integration Connections

These are the build steps you'll need to use to update an Oracle Integration connection's security and connection properties and upload a property attachment for a specific Oracle Integration connection. You can make updates to a connection's security and connection properties, agentGroupId, or to the securityPolicy property. Other properties are ignored. Supported security properties depend on the securityPolicy that is selected. The connection type determines which securityPolicy values are supported.

Step Description See this topic
Configure a build job to update an OIC connection's security and connection properties and more. Creates and executes a job to:
  • Identify the connection in the Oracle Integration instance that you want to update.
  • Specify the path and filename of the file containing updates to the connection details or lets you change the details directly using inline JSON content.
 Configure a Job to Update an Oracle Integration Connection
Optional: Configure a build job to upload a property attachment for an OIC connection. Creates and executes a job to upload an attachment (such as a ZIP or WSDL file) to a connection and associates the attachment with a specific connection property. This is how SOAP adapters are configured. Configure a Job to Upload a Property Attachment for an Oracle Integration Connection

Configure a Job to Update an Oracle Integration Connection

You can create and use job (or a build step) to update an Oracle Integration connection's security properties, connection properties, agentGroupId, or securityPolicy.

To configure a build job that updates an Oracle Integration connection's details:
  1. In the left navigator, click Builds 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 Update Connection.
  9. In Target Instance , select the environment that points to the Oracle Integration instance with the connection details you want to modify.
  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 Identifier, select the identifier of the connection in the target Oracle Integration instance that you want to update.

    You can also click Search Search icon and open the Search Connections window to get a list of connections 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.

  12. In the Source section, select and complete one of the following:
    • Choose JSON file and, in JSON File Path, enter the path and the filename of the file containing updates to the connection details.
    • Choose Inline JSON and enter the JSON updates directly in the text box.
  13. Click Save.

Configure a Job to Upload a Property Attachment for an Oracle Integration Connection

You can create and use a job (or a build step) to upload a property attachment (a zip or WSDL file) that updates a single property for an Oracle Integration connection.

To configure a build job that uploads an attachment (a zip or WSDL file) that modifies one Oracle Integration connection property:
  1. In the left navigator, click Builds 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 Upload Connection Property Attachment.
  9. In Target Instance , select the environment that points to the Oracle Integration instance with the connection property you want to modify.
  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 Identifier, select the identifier of the connection in the target Oracle Integration instance to receive the file.

    You can also click Search Search icon and open the Search Connections window to get a list of connections 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.

  12. In Property Name, enter the name of the connection property to receive the file.
  13. In File Path, enter the name of the file to upload, such as a zip or WSDL file.
  14. If you're uploading a zip file, in Service WSDL, enter the file path for the WSDL file within the zip file.
  15. Click Save.