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.

1. Go to the Properties section.
2. In the Hostname field, enter the Jira instance hostname.

Configure Connection Security

Configure security for your Jira Adapter connection.

1. Go to the Security section.
2. From the Security Policy list, select the security policy to use:
   • Basic Authentication
   • Authorization Code Credentials
3. If you selected Basic Authentication:
   1. In the Username field, enter the username.
   2. In the Password field, enter the API token. An API token is used (instead of your account password) as a password whenever you programmatically authenticate with basic authentication. See Create an API Token.

      Note:

      The Basic Authentication security policy can be used for invoke connections only.
4. If you selected Authorization Code Credentials:
   1. In the Client Id field, enter the client ID that you obtained when creating an app. See Create an App and Obtain the Client ID and Client Secret.
   2. In the Client Secret field, enter the client secret key that you obtained when creating an app. See Create an App and Obtain the Client ID and Client Secret.
   3. In the Scope field, enter read:jira-work manage:jira-webhook for your Jira Adapter trigger connection, and enter read:jira-work read:jira-user write:jira-work for your Jira Adapter invoke connection. These are the minimum older scopes required to configure a connection. However, you can enter new Jira scopes. See Minimum Scopes for Creating a Connection.

      You can also enter other space-separated scopes that you need to configure. Ensure that the scopes you want to provide are configured in the Jira application. See Configure the OAuth 2.0 Authorization Code and Assign the Scopes.

      Note:

      • The Authorization Code Credentials security policy can be used for trigger and invoke connections.
      • The Scope field is not marked with an asterisk (*). This incorrectly implies that this field is not mandatory. This field is mandatory.
   4. Click Provide Consent. You are redirected to the Jira login page.
   5. Log in to the Jira account with your credentials. Once you successfully log in, the following message appears:

      Access Allowed! Please switch back to connection page to proceed with testing and saving 
      connection configuration.

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
• Ensure Private Endpoint Configuration is Successful

Select the Endpoint Access Type

Select the option for accessing your endpoint.

Option	This Option Appears If Your Adapter Supports ...
Public gateway	Connections to endpoints using the public internet.
Private endpoint	Connections to endpoints using a private virtual cloud network (VCN). Note: To connect to private endpoints, you must complete prerequisite tasks in the Oracle Cloud Infrastructure Console. Failure to do so results in errors when testing the connection. See Connect to Private Resources in Provisioning and Administering Oracle Integration 3 and Troubleshoot Private Endpoints in Using Integrations in Oracle Integration 3.

Ensure Private Endpoint Configuration is Successful

• To connect to private endpoints, you must complete prerequisite tasks in the Oracle Cloud Infrastructure Console. Failure to do so results in errors when testing the connection. See Connect to Private Resources in Provisioning and Administering Oracle Integration 3.
• When configuring an adapter on the Connections page to connect to endpoints using a private network, specify the fully-qualified domain name (FQDN) and not the IP address. If you enter an IP address, validation fails when you click Test.
• IPSec tunneling and FastConnect are not supported for use with private endpoints.

Test the Connection

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

1. In the page title bar, click Test.
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.