Create a Connection

Before you can build an integration, you must create the connections to the applications with which you want to share data.

Note:

You can also create a connection in the integration canvas. See why working with projects is preferred.

To create a connection in Oracle Integration:

  1. Decide where to start:
    • Work in a project (see why working with projects is preferred).
      1. In the navigation pane, click Projects.
      2. Select the project name.
      3. Click Integrations Integrations icon.
      4. In the Connections section, click Add if no connections currently exist or + if connections already exist. The Create connection panel opens.
    • Work outside a project.
      1. In the navigation pane, click Design, then Connections.
      2. Click Create. The Create connection panel opens.
  2. Select the adapter to use for this connection. To find the adapter, scroll through the list, or enter a partial or full name in the Search field.

  3. Enter the information that describes this connection.
    Element Description
    Name

    Enter a meaningful name to help others find your connection when they begin to create their own integrations.

    Identifier

    Automatically displays the name in capital letters that you entered in the Name field. If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY).

    Role

    Select the role (direction) in which to use this connection.

    Note: Only the roles supported by the adapter you selected are displayed for selection. Some adapters support all role combinations (trigger, invoke, or trigger and invoke). Other adapters support fewer role combinations.

    When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page. If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.

    For example, assume you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke. Dragging the adapter to a trigger section in the integration produces an error.

    Keywords

    Enter optional keywords (tags). You can search on the connection keywords on the Connections page.

    Description

    Enter an optional description of the connection.

    Share with other projects

    Note: This field only appears if you are creating a connection in a project.

    Select to make this connection publicly available in other projects. Connection sharing eliminates the need to create and maintain separate connections in different projects.

    When you configure an adapter connection in a different project, the Use a shared connection field is displayed at the top of the Connections page. If the connection you are configuring matches the same type and role as the publicly available connection, you can select that connection to reference (inherit) its resources.

    See Add and Share a Connection Across a Project.

  4. Click Create.

    Your connection is created. You're now ready to configure the connection properties, security policies, and (for some connections) access type.

  5. Follow the steps to configure a connection.

    The connection property and connection security values are specific to each adapter. Your connection may also require configuration with an access type such as a private endpoint or an agent group.

  6. Test the connection.

Configure Connection Properties

Enter connection information so your application can process requests.

  1. Go to the Properties section.
  2. Specify the following details.
    Element Description
    Base URL

    Enter the base URL.

    See Prerequisites for Creating a Connection.

    ArcGIS Products
    Select the product in the list.
    • ArcGIS Enterprise
    • ArcGIS Online

Configure Connection Security

Configure security for your ArcGIS (ESRI) Adapter connection.

  1. Go to the Security section.
  2. Select the security policy to use.
    Security Policy Field

    ArcGIS Generate Token Flow

    (In the invoke (outbound) direction, this security policy supports both ArcGIS Enterprise and ArcGIS Online products.)

    1. Access Token URI - Enter the authorization server that generates the access token. See Prerequisites for Creating a Connection.
    2. Username - Enter the case-sensitive user name of the user.
    3. Password ¬ Enter the password of the user.

    OAuth Authorization Code Credentials

    (In the invoke (outbound) direction, this security policy supports ArcGIS Online products.)

    1. OAuth Client ID - Enter the client identifier issued to the client during the registration process.
    2. OAuth Client secret - Enter the client secret.
    3. Authorization code URI - Enter the URI from which to request the authorization code.
    4. Access token URI - Enter the URI to use for the access token.

    ArcGIS Online OAuth Authorization Code Policy and HMAC

    (In the trigger (inbound) direction, this security policy supports OAuth Authorization Code Policy and HMAC for ArcGIS Online products.)

    1. OAuth Client ID - Enter the client identifier issued to the client during the registration process.
    2. OAuth Client secret - Enter the client secret.
    3. Authorization code URI - Enter the URI from which to request the authorization code.
    4. Access token URI - Enter the URI to use for the access token.
    5. Shared Secret - Enter a meaningful name or key. You can include English alphabetic characters, numbers, underscores, and hyphens.
    6. Client Identifier - Enter the client identifier issued to the client during the registration process.
    When configuration is complete, perform the following steps:
    1. Click Provide Consent to test the OAuth flow.
    2. If the Oracle Identity Cloud Service or identity domain Oracle Integration and Oracle Fusion Applications users are different, log in to the respective instance when prompted.

      Note: You are not prompted to log in if these users are the same.

    3. Return to the Connections page and click Test.

    ArcGIS API Key Validation Enterprise

    (In the trigger (inbound) direction, this policy supports OAuth Authorization Code Policy and HMAC for ArcGIS Enterprise products).

    1. Signature Key - Enter a meaningful name or key. You can include English alphabetic characters, numbers, underscores, and hyphens.
    2. Client Identifier - Enter the client secret. The client identifier is issued to the client during the registration. process.

Configure the Endpoint Access Type

Configure access to your endpoint. Depending on the capabilities of the adapter you are configuring, options may appear to configure access to the public internet, to a private endpoint, or to an on-premises service hosted behind a fire wall.

Select the Endpoint Access Type

  1. Go to the Access type section.
  2. Select the option for accessing your endpoint.
    Option This Option Appears If Your Adapter Supports ...
    Public gateway Connections to endpoints using the public internet.
    Connectivity agent

    Connections to on-premises endpoints through the connectivity agent.

    1. Click Associate agent group.

      The Associate agent group panel appears.

    2. Select the agent group, and click Use.

    To configure an agent group, you must download and install the on-premises connectivity agent. See Download and Run the Connectivity Agent Installer and About Creating Hybrid Integrations Using Oracle Integration in Using Integrations in Oracle Integration 3.

Test the Connection

Test your connection to ensure that it's configured successfully.

  1. In the page title bar, click Test. What happens next depends on whether your adapter connection uses a Web Services Description Language (WSDL) file. Only some adapter connections use WSDLs.
    If Your Connection... Then...

    Doesn't use a WSDL

    The test starts automatically and validates the inputs you provided for the connection.

    Uses a WSDL

    A dialog prompts you to select the type of connection testing to perform:

    • Validate and Test: Performs a full validation of the WSDL, including processing of the imported schemas and WSDLs. Complete validation can take several minutes depending on the number of imported schemas and WSDLs. No requests are sent to the operations exposed in the WSDL.

    • Test: Connects to the WSDL URL and performs a syntax check on the WSDL. No requests are sent to the operations exposed in the WSDL.

  2. Wait for a message about the results of the connection test.
    • If the test was successful, then the connection is configured properly.
    • If the test failed, then edit the configuration details you entered. Check for typos and verify URLs and credentials. Continue to test until the connection is successful.
  3. When complete, click Save.