Create a Connection

The first step in creating an integration is to create the connections to the applications with which you want to share data.

  1. In the navigation pane, click Integrations, then click Connections.

  2. Click Create.

    Note:

    You can also create a connection in the integration canvas of:

    The Create Connection — Select Adapter dialog is displayed.

  3. Select an adapter from the dialog. You can also search for the type of adapter to use by entering a partial or full name in the Search field, and clicking Search.

    The Create New Connection dialog is displayed.

  4. Enter the information to describe the connection.

    • Enter a meaningful name to help others find your connection when they begin to create their own integrations. The name you enter is automatically added in capital letters to the Identifier field. If you modify the identifier name, do not include a blank space (for example, Sales Opportunity).

    • Select the role (direction) in which to use this connection (trigger, invoke, or both). Only the roles supported by this adapter are displayed for selection. 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, then try to drag the adapter into the section you did not select, you receive an error (for example, configure an Oracle Service Cloud (RightNow) Adapter as only an invoke, but drag the adapter to the trigger section).

    • Enter an optional description of the connection.


    Description of create_new_connection.png follows
    Description of the illustration create_new_connection.png
  5. Click Create.

    Your connection is created and you are now ready to configure connection details, such as email contact, connection properties, security policies, connection login credentials, and (for certain connections) agent group.

Add a Contact Email

You can add an optional contact email address for notifications.

  1. In the Email Address field, enter an optional email address. You do not receive automatic notifications at this address.
  2. In the upper right corner, click Save.

Configure Connection Properties

Enter connection information so your application can process requests.

  1. Click Configure Connectivity.
    The Connection Properties dialog is displayed.
  2. In the WSDL URL field, specify the URL in either of two ways:
    1. Click the Upload File checkbox, then click Upload to upload the WSDL.
      If you upload a ZIP file, the file is validated and the page is refreshed to display the Service WSDL list. The relative paths of all WSDLs in the ZIP are displayed. Select the WSDL to use in the connection.
      Description of soap_zip_wsdl.png follows
      Description of the illustration soap_zip_wsdl.png
    2. Manually specify the WSDL to use.
  3. In the Target Server's TLS version (Optional) field, optionally specify the Transport Layer Security (TLS) version of the target server. Oracle Integration is configured to use TLS v1.1 by default.
    • TLSv1.1

    • TLSv1.2

    The TLS protocol provides privacy and data integrity between two communicating computer applications. Depending on the JDK version in use, the version of TLS being used during connection establishment can differ for different clients and servers. If the outbound server requires a different TLS version, specify the required version to use.

  4. In the Suppress insertion of timestamp into the request (Optional) field, optionally suppress the timestamp in the WS-Security header. Suppression applies to the Username Password Token security policy in the invoke (outbound) direction. In secure Web Services transactions, a WS-Utility (WSU) timestamp can be inserted into a WS-Security header to define the lifetime of the message in which it is placed.
    • Yes: No timestamp is added to the WS-Security header sent as part of the outbound request. For inbound requests with the basic authentication security policy, no timestamp is required to be sent by the client.

    • No: Clients are expected to send a timestamp in the WS-Security header with the request.

  5. In the Ignore timestamp in the response message (Optional) field, specify if the timestamp is not required in the response message.
    • Yes: The timestamp is not required in the response message. If the timestamp is present in the SOAP security header when the response is received from the service , it is ignored.

    • No: The timestamp is received in the response from the service is not ignored.

  6. In the Enable two way SSL for outbound connection field, select Yes if you want to enable two-way SSL communication.
  7. In the Name of the certificate to use for SSL communication field, enter the key alias name configured for two-way SSL communication. This is the name you entered in the Key Alias Name field when uploading the identity certificate in the Upload Certificate dialog. See Upload an SSL Certificate.
  8. Click OK.
  9. Configure connection security.

Configure Connection Security

Configure security for your Update Adapter Product Name connection by selecting the security policy.

  1. Click Configure Credentials.
  2. Select the security policy.
    The page is refreshed to display the login credential fields.
  3. Specify the login credentials. For trigger (inbound) connections, the security policy must be either username password token, basic authentication, SAML, or OAuth 2.0. This is because all Oracle Integration inbound endpoints are protected with either of these policies.
    Security Policy Fields

    Basic Authentication

    (In the trigger (inbound) direction, supports HTTP basic authentication over SSL: oracle/wss_http_token_over_ssl_service_policy).

    Note the following behavior:

    • If the invoking client is secured with Oracle Web Services Manager (OWSM) using an oracle/wss* policy, the client receives a failure.

    • In the inbound (trigger) direction, if the Suppress insertion of timestamp into the request (Optional) field is enabled, then oracle/http_basic_auth_over_ssl_service_policy is supported.

    • In customer-managed environments, when configuring a trigger SOAP Adapter with Basic Authentication, the wss_http_token_service_policy policy is used regardless of whether the Suppress insertion of timestamp into the request option is set to Yes or No in the Connections page. Therefore, with or without the timestamp added in the SOAP header, as long as the username and password credentials are valid, the connection runs successfully at runtime.

    If Basic Authentication is required for both trigger and invoke connections, create one connection with the Trigger and Invoke role that uses the Basic Authentication security policy.

    • Username — Enter the name of a user who has access to the destination web service.

    • Password — Enter the password.

    • Confirm Password — Reenter the password.

    Username Password Token

    (In the trigger (inbound) direction, supports oracle/wss_username_token_over_ssl_service_policy.)

    • Username — Enter the name of a user

    • Password — Enter the password.

    • Confirm Password — Reenter the password.

    No Security Policy

    No fields are displayed.

    Security Assertion Markup Language (SAML)

    This policy is only available when configuring the SOAP Adapter as a trigger. If you attempt to add the SOAP Adapter with this security policy configuration as an invoke in an integration, you receive an error.

    • Username — Optionally enter the name of the SAML user.

    OAuth 2.0

    This policy is only available when configuring the SOAP Adapter as a trigger. If you attempt to add the SOAP Adapter with this security policy configuration as an invoke in an integration, you receive an error.

    No fields are displayed.

    If you select a security policy, the following behavior occurs.

    If the Inbound SOAP Connection is Configured with Security Policy... Then...
    Username Password Token
    • The client should send the username/password and timestamp as part of the WSEE header.

    • The response includes only the SOAP payload.

    Basic Authentication
    • The client should send the username/password in the HTTP headers and timestamp as part of the WSEE header.

    • The response includes only the SOAP payload.

    Basic Authentication and the Suppress insertion of timestamp into the request (Optional) field is enabled
    • The client should send the username/password in the HTTP headers.

    • The response includes only the SOAP payload.

    Note:

    If no timestamp is included as part of the header, configure the SOAP Adapter connection with the Basic Authentication security policy (oracle/http_basic_auth_over_ssl_client_policy) and set Suppress insertion of timestamp into the request (Optional) to Yes.
  4. Click OK.

Configure an Agent Group

Configure an agent group for accessing the service hosted on your premises behind the fire wall.

  1. Click Configure Agents.
    The Select an Agent Group page appears.
  2. Click the name of the agent group.
  3. Click Use.
To configure an agent group, you must download and install the on-premises connectivity agent. See Download and Run the On-Premises Agent Installer and About Agents and Integrations Between On-Premises Applications and Oracle Integration in Using Integrations in Oracle Integration.

Test the Connection

Test your connection to ensure that it is successfully configured.

  1. In the upper right corner of the page, click Test.
    If your adapter connection uses a WSDL, a dialog is displayed that prompts you to select the type of connection testing to perform. Otherwise, this step is not applicable.
    1. Select the 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.

    If successful, the following message is displayed and the progress indicator shows 100%.

    Connection connection_name was tested successfully.

  2. If your connection was unsuccessful, an error message is displayed with details. Verify that the configuration details you entered are correct.
  3. When complete, click Save, then click Close.