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 to use in this integration:

   https://webservices.netsuite.com/wsdl/NetSuite_application_version/netsuite.wsdl

   where NetSuite_application_version is the version of the NetSuite application. For example:

   https://webservices.netsuite.com/wsdl/v2014_2_0/netsuite.wsdl

   https://webservices.netsuite.com/wsdl/v2015_1_0/netsuite.wsdl

   The web services may or may not be hosted at the above location. The adapter can programmatically determine the correct URL for the web services. NetSuite hosts customer accounts in multiple locations. For example:

   • webservices.netsuite.com

   • webservices.na1.netsuite.com

Configure Connection Security

Configure security for your Oracle NetSuite Adapter connection by selecting the security policy and providing the login credentials.

1. Go to the Security section.
2. Select the security policy. You must first satisfy several prerequisites. See Create an Oracle NetSuite Adapter Connection.

   Security Policy	Fields
   User Credentials	Email Address — Enter the email address that serves as the user name. Account — Enter the account. Role — Enter the role ID received from NetSuite, and not the role name. Role-based access control ensures that users can only use data and application functionality that is related to their responsibilities. Password — Enter the password. Confirm Password — Reenter the password. Application Id — Enter the application ID received from NetSuite. This is a mandatory field starting with the 2015_02 version of the NetSuite WSDL.
   Token-Based Authentication	Enter the following values. You must obtain these values before you can complete these fields. See Prerequisites for the Token-Based Authentication Security Policy. The tokens do not expire. If the token is revoked or a new token is generated, you must update the provided values. Consumer Key — Enter the consumer key for the integration record in Oracle NetSuite. Consumer Secret — Enter the consumer secret for the integration record in Oracle NetSuite. Confirm Consumer Secret — Re-enter the consumer secret. Token — Enter the token ID provided by Oracle NetSuite. Token Secret — Enter the token secret provided by Oracle NetSuite. Confirm Token Secret — Re-enter the token secret. Account ID — Enter your Oracle NetSuite account identifier.
   TBA Authorization Flow Note: The TBA Authorization Flow security policy does not work with custom endpoints. Custom endpoints enable you to map a uniquely-defined hostname to an Oracle Integration instance and use it to access the instance instead of the original URL generated in the Oracle Cloud Infrastructure Console. See Configure a Custom Endpoint for an Instance in Provisioning and Administering Oracle Integration Generation 2.	This security policy is a three-legged, authorization flow grant type. An out-of-the-box Oracle client application is automatically installed. The client ID and client secret are automatically included, eliminating the need to manually specify these values. Click Provide Consent. When prompted. enter the user name and password for your Oracle Integration instance. When prompted, enter the user account and password for your Oracle NetSuite application. This permits the Oracle client application to access your Oracle NetSuite account. Click Allow to allow Oracle Integration to access your account and Oracle NetSuite data.

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.