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. If configuring the connection to use direct connectivity (that is, you are not using the connectivity agent):
   1. In the Host field, specify the host.
   2. In the Service Name field, specify the database service name. It is recommended that you use the low profile as the database service name. The database service name is not the same as the database service username that you specify in the Security section.

      Note:

      The service name must be the same as the one in the tnsnames.ora file in the wallet. However, if you receive an error when testing the connection, it may be because the name is too long. See Service Name Specified on the Connections Page is Too Long.
3. If configuring the connection to use the connectivity agent:
   1. In the Host field, specify the host.
   2. In the Port field, specify the SQL*Net port.
   3. In the SID field, specify the database SID.
   4. In the Service Name field, specify the database service name. It is recommended that you use the low profile as the database service name. The database service name is not the same as the database service username that you specify in the Security section.

      Note:

      You must specify either a SID or service name value. Do not specify values for both fields.

Configure Connection Security

Configure security for your database connection by selecting the security policy and setting login credentials. A database connection is only allowed for publicly accessible databases.

1. Go to the Security section.
2. Select the security policy.
3. If you select JDBC Basic Authentication:

   Note:

   Using the Username Password Token security policy, you can create and successfully test the connection to the database without the connectivity agent if the database is present in the same private network as the Oracle Integration instance. If the database is not in the same private network, it is not recommended that you connect without the connectivity agent because the connection won't be secure.
   1. Enter the database service username and password to connect to the Oracle Autonomous Transaction Processing database. The database service username is the schema username for the user to log in to the database. The database service username is not the same as the database service name that you specify in the Connection Properties section.
4. If you select JDBC Over SSL:

   Note:

   The Oracle Autonomous Transaction Processing Adapter can connect through the connectivity agent when using the wallet. It can be used as a trigger connection only if the connectivity agent is used in the connection. However, all operations that you select on the Basic Info page such as Run a SQL Statement, Invoke a Stored Procedure, and Perform an Operation On a table are supported when configuring the adapter to use direct connectivity (without the connectivity agent).
   1. In the Wallet field, select the check box, then click Upload to upload the wallet file.
   2. Enter the wallet password.
   3. Enter the database service username and password to connect to the Oracle Autonomous Transaction Processing database. The database service username is the schema username for the user to log in to the database. The database service username is not the same as the database service name that you specify in the Connection Properties section.
5. If you select JDBC With OCI Signature:

   Note:

   This option is required to use the bulk data import operation and is only supported when using direct connectivity (that is, you are not using the connectivity agent).
   1. In the Wallet field, select the check box, then click Upload to upload the wallet file.
   2. Enter the wallet password.
   3. Enter the database service username and password to connect to the Oracle Autonomous Transaction Processing - Shared (ATP-S) database. The database service username is the schema username for the user to log in to the database. The database service username is not the same as the database service name that you specify in the Connection Properties section.
   4. In the Object Storage Region field, specify the region in which your object storage is located (for example, us-ashburn-1).
   5. In the Object Storage Tenancy OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.tenancy.oc1.alphanumeric.value). See Prerequisites for Creating a Connection.
   6. In the Object Storage Compartment OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.compartment.oc1.alphanumeric.value).
   7. In the Object Storage User OCID field, specify the value you copied from the Oracle Cloud Infrastructure Console (for example, ocid1.user.oc1.alphanumeric.value).
   8. In the Private Key field, click Upload to select the key you created. Ensure that the key is in RSA (PKCS1) format.

      Note:

      Only a private key without a pass phrase/password is supported.
   9. In the Finger Print field, enter the finger print that was generated when you created the key in the Oracle Cloud Infrastructure Console.

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.
Connectivity agent	Connections to on-premises endpoints through the connectivity agent. Click Associate agent group. The Associate agent group panel appears. Select the agent group, and 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 Creating Hybrid Integrations Using Oracle Integration 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. 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.
   • If using the JDBC With OCI Signature security policy, compartment ID verification doesn't occur during the connection test. The Adapter Endpoint Configuration Wizard handles verification and authorization issues with the compartment OCID.
3. When complete, click Save.