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:
-
In the left navigation pane, click Home > Integrations > Connections.
-
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.)
-
-
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.
-
In the Create Connection dialog, enter the information that describes this 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, don't include blank spaces (for example,
SALES OPPORTUNITY
). - Enter optional keywords (tags). You can search on the connection keywords on the Connections page.
- 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.
- Enter an optional description of 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, don't include blank spaces (for example,
-
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 for Invoke Connections
Configure connection security to invoke a protected target service with the REST Adapter.
Configure Connection Security
Configure security for your REST Adapter connection by selecting the security policy and specifying the required details.
- Go to the Security section.
- Select the security policy to use. If you selected the
Invoke role or the Trigger and
Invoke role during REST Adapter connection creation, the page is refreshed to display various login
credential fields. You must already have created your client application to
complete the necessary fields.
The following security policy restrictions apply when configuring a REST Adapter connection with the trigger and invoke role on the Connections page:
- If you select Basic Authentication, it can be used as a trigger and an invoke.
- If you select any other security policy, it can only be used as an invoke. Dragging the connection to the trigger area causes an exception error to be displayed.
- For existing integrations, the above restrictions do not apply when editing the REST Adapter in the Adapter Endpoint Configuration Wizard.
Note:
The following standard OAuth security policies are implemented to work with providers that are implemented as illustrated in RFC 6749.- OAuth Resource Owner Password Credentials
- OAuth Client Credentials
Configure Security Policies for Trigger Connections
Selected Security Policy | Description | Fields |
---|---|---|
OAuth2.0 |
See Authenticate Requests for Invoking Oracle Integration Flows. |
No fields are displayed. |
Basic Authentication |
|
No fields are displayed. |
OAuth 2.0 or Basic Authentication | The client can use any of the OAuth 2.0 bearer tokens or the HTTP Basic Authentication header. | No fields are displayed. |
Configure Security Policies for Invoke Connections
Note:
OAuth Authorization Code Credentials, OAuth Custom Three Legged Flow, and OAuth Custom Two Legged Flow security types, the connection is only successful after you click the Provide Consent button. Configuring all the details alone is not sufficient.Note:
Testing a REST Adapter connection configured with the HTTP basic authentication security policy and a role connection of Trigger and Invoke or Invoke does not validate the credentials and simply opens a connection to the provided URL. To validate the endpoint and credentials, the REST Adapter must invoke an API that is idempotent.Selected Security Policy | Fields |
---|---|
AWS Signature Version 4 |
|
Basic Authentication |
|
OAuth Client Credentials |
|
OAuth Resource Owner Password Credentials |
|
OAuth Authorization Code Credentials |
|
OAuth Custom Three Legged Flow See Configure the REST Adapter to Consume a REST API Protected with OAuth Custom Three Legged Flow Token-Based Authentication to learn more about this security policy. |
|
OAuth Custom Two Legged Flow See Configure the REST Adapter to Consume a REST API Protected with OAuth Custom Two Legged Token-Based Authentication to learn more about this security policy. |
|
API Key Based Authentication See Configure the REST Adapter to Consume a REST API Protected with the API Key to learn more about this security policy. |
|
OAuth 1.0 One Legged Authentication |
|
OCI Signature Version 1 | Specify the values you created when satisfying the
prerequisites for using this security policy. See Prerequisites for Creating a Connection.
|
No Security Policy |
If you select this security policy, no additional fields are displayed. |
Configure an Agent Group
Configure an agent group for accessing the service hosted on your premises behind the fire wall.