Create a Connection

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

To create a connection in Oracle Integration:

1. In the left navigation pane, click Home > Integrations > Connections.

2. Click Create.

   Note:

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

   • An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)

   • A basic routing integration (See Add a Trigger (Source) Connection.)

3. In the Create Connection — Select Adapter dialog, 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 and click Search.

4. In the Create Connection dialog, enter the information that describes this connection.

   1. 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, don't include blank spaces (for example, SALES OPPORTUNITY).
   2. Enter optional keywords (tags). You can search on the connection keywords on the Connections page.
   3. Select the role (direction) in which to use this connection (trigger, invoke, or both). Only the roles supported by the 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, you'll get an error when you try to drag the adapter into the section you didn't select. For example, let's say 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.
   4. Enter an optional description of the connection.

5. Click Create.

   Your connection is created. You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.

Configure Connection Properties

Enter connection information so your application can process requests.

1. Go to the Connection Properties section.
2. In the WSDL URL field, specify the URL in either of two ways:
   1. Click , then click Browse to select the WSDL to upload.
      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.
   2. Manually specify the WSDL to use.
3. From the TLS Version (Optional) list, it is recommended that you not select a value for the Transport Layer Security (TLS) version of the target server. Oracle Integration automatically uses the latest TLS version for SSL communication. TLSv1 is no longer supported. If you previously configured a connection to use TLSv1.1, either update the connection by not selecting a value for this field or select TLSv1.2.

   The TLS protocol provides privacy and data integrity between two communicating computer applications.

   • TLSv1.1

   • TLSv1.2

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 connections (Optional) field, select Yes if you want to enable two-way SSL communication.
7. In the Identity keystore alias name (Optional) field, enter the key alias name configured for two-way SSL communication. Both the client and server pass certificates to each other to establish an SSL link when two-way SSL is enabled. This value should match the alias that was provided to import identity to Oracle Integration. 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.

   The alias name to provide must match the name provided for the private key entry in the JKS file.

Configure Connection Security

Configure security for your SOAP Adapter connection by selecting the security policy.

1. Go to the Security section.
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 any of these policies.

   When configuring the SOAP Adapter with the trigger-only role, you cannot select No Security Policy because all Oracle Integration endpoints are protected.

   • New connections do not show No Security Policy in the dropdown list.
   • Existing connections default to the Username Password Token security policy.
   • Connections updated with the REST APIs are automatically changed to use the Username Password Token security policy by default even though the request payload used No Security Policy.

   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.

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 Connectivity Agent Installer and About Connectivity Agents and Integrations Between On-Premises Applications and Oracle Integration in Using Integrations in Oracle Integration Generation 2.

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 connection uses a Web Services Description Language (WSDL) file.

   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, verify URLs and credentials, and download the diagnostic logs for additional details. Continue to test until the connection is successful.
3. When complete, click Save.