Create a Connection

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

To create a connection in Oracle Integration:

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

2. Click Create.

   Note:

   You can also create a connection in the integration canvas. See Define Inbound Triggers and Outbound Invokes.

3. In the Create connection panel, 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.

4. 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 (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, 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.

5. Click Create.

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

Configure Connection Properties

Enter connection information so your application can process requests. This section only appears when you configure the RosettaNet Adapter as an invoke connection.

1. Go to the Properties section.
2. In the RosettaNet Service URL field, enter the endpoint address of the trading partner to receive RosettaNet messages.
3. Expand Optional properties.

   Element	Description
   Enable two way SSL for outbound connections	Select Yes if you want to enable communication.
   Client Identity Key Alias (Two Way SSL)	Enter the certificate key alias to use for client identity during two-way SSL communication.

Configure Connection Security

Configure security for your RosettaNet Adapter connection.

1. Go to the Security section.
2. Select the security policy to use.
   1. If you select RosettaNet Basic Policy, and expand Optional security.

      Element	Description
      Username	Enter the username to use for HTTP authentication of the partner's protected endpoint address.
      Password	Enter the password to use for HTTP authentication of the partner's protected endpoint address.
      Private Key Alias	Enter the private key used for inbound data decryption and outbound signature generation. This is the same key alias as uploaded in the identity store when you select Settings and then Certificates in the navigation pane.
      Key Password	Enter the password associated with the private key.
      Partner Certificate Alias	Enter the partner certificate to use for outbound data encryption and inbound signature verification.

   2. If you select RosettaNet Advanced Policy, and expand Optional security.

      Element	Description
      Private Key Alias (RosettaNet Decryption)	Enter the private key used for inbound data decryption by a trigger action.
      Key Password (RosettaNet Decryption)	Enter the key password associated with the private key.
      Certificate Alias (Inbound RosettaNet Sign Verify)	Enter the partner public key certificate used by a trigger connection for inbound RosettaNet certificate verification.
      Username (RosettaNet Endpoint)	Enter the user name required for sending the RosettaNet password to the protected partner endpoint.
      Password (RosettaNet Endpoint)	Enter the password required for sending the RosettaNet password to the protected partner endpoint.
      Private Key Alias (RosettaNet Signature)	Enter the private key used by the invoke connection to send a signed RosettaNet message.
      Key Password (RosettaNet Signature)	Enter the key password associated with the private key (RosettaNet signature).
      Certificate Alias (Outbound RosettaNet Encrypt)	Enter the partner public certificate used by an invoke connection for outbound RosettaNet message encryption. This is the same key alias as uploaded in the identity store when you select Settings and then Certificates in the navigation pane.

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.