Set up a connection to Oracle Autonomous Database / NSAW

Oracle Autonomous Database (ADB) is a cloud database that automatically tunes, secures, and manages data using machine learning. It is completely automated and performs these tasks without human intervention. You can use this connector to connect to Oracle Autonomous Data Warehouse (OADW) and NetSuite Analytics Warehouse (NSAW).

Note: Celigo uses a JDBC connection to connect to Oracle Autonomous Database / NSAW; we use the ojdbc10.jar. If you would like to connect to any application that supports this JAR file but is currently not available in our connector list, you're welcome to submit the idea on the Product portal.

Contents

• Set up a connection to Oracle Autonomous Database / NSAW
• Edit the general Oracle Autonomous Database / NSAW settings
• Edit the Oracle Autonomous Database / NSAW settings for authentication
• Edit the advanced Oracle Autonomous Database / NSAW settings for customization
• Test the connection

1. Set up a connection to Oracle Autonomous Database / NSAW 

Start establishing a connection to Oracle Autonomous Database / NSAW in either of the following ways:

• From the Resources menu, select Connections. Then, click + Create connection at the top right.
      – or –
• While working in a new or existing integration, you can add an application to a flow simply by clicking Add source or Add destination.

In the resulting Application list, click Oracle Autonomous Database / NSAW.

2. Edit the general Oracle Autonomous Database / NSAW settings

First, you must name your connection.

 

Name (required): Enter a clear and distinguishable name for your connection.
Throughout integrator.io imports and exports, you will have the option to choose this new connection. A unique identifier will prove helpful later when selecting it from a list of the connections in your account.

3. Edit the Oracle Autonomous Database / NSAW settings for authentication

Based on the authentication type you choose, the settings shown vary.

Authentication type (required): Select Custom JDBC or Cloud Wallet to connect to an Autonomous Database using the Oracle database tool, Oracle SQL Developer. For more information, see Connect to ADB using Oracle database tools.

• Custom JDBC – select this option to connect without a wallet (TLS)
• Cloud Wallet – select this option to connect with a wallet (mTLS) for applications such as NSAW

Host (required only for Custom JDBC authentication type): Enter the connection string/URL to connect to the server that hosts the database. To get the connection string, click the link below.

How to find host details

1. Sign in to Oracle Cloud.

2. In the navigation pane, click Oracle Database > Autonomous Database.

2. Click an Autonomous Database instance.

 

3. In the Autonomous Database details page, click Database connection.

4. In the Database connection page, go to the Connection strings section. Then, in the Connection string column, click Show to view and copy the value. (Paste this string in the Host field in the Celigo platform.)

Credentials .zip file (required only for Cloud Wallet authentication type): Upload the credentials.zip file (wallet file) for authentication. if you are a database administrator, you can follow the instructions and download client credentials. If you are not a database administrator, you can request your administrator to provide the file.

Service Name (required only for Cloud Wallet authentication type): Select the service name based on your workload. Each service provides a different level of performance and concurrency. For details, see the database service names.

Username (required): Enter your user name for database authentication.

Password (required): Enter your password for database authentication.

4. Edit the advanced Oracle Autonomous Database / NSAW settings for customization

Configure properties: Define additional configurations for the database connection. For example, you can configure the connection timeout if the server you are trying to connect to is slow.

Borrow concurrency from: Select another connection from the list. By default, all data flowing through a connection record is submitted to the respective endpoint application at the Concurrency level configured for that connection record. There are cases, however, where multiple integrator.io connections need to share the same concurrency level, and this field allows you to specify which connection you would like to borrow from. With borrowed concurrency, the data flowing through both connections will be submitted to the endpoint application together, via a shared concurrency model.

Auto-recover rate limit errors: This setting is enabled by default with a pre-defined value for Target concurrency level. You can disable the setting if required. To set or make changes in any of these settings, you must have administer or manage permissions.

Target concurrency (required if Auto-recover rate limit errors is enabled): This field is shown only if Auto-recover rate limit errors is enabled. Change the predefined value as required to limit the number of concurrent API requests allowed by the connection resource. See also, Setting currency level on a connection.

Concurrency level (required if Auto-recover rate limit errors is not enabled): When Auto-recover rate limit errors is enabled, the Concurrency level cannot be edited and shows the concurrency level that the platform is currently using (runtime). When Auto-recover rate limit errors is not enabled, enter a value to limit the number of concurrent API requests allowed by the connection resource. See also, Setting currency level on a connection.

Configure encrypted fields:  Store all sensitive fields required by your imports and exports to access the app you are connecting to. Click the Expand window (  ) button to modify the JSON sent to the app in the Encrypted Advanced Field Editor. For example, enter {"secretKey": "someSecretKeyValue"}. (You can also retrieve these sensitive values elsewhere, such as How to test this connection?, via the example handlebars format {{{connection.http.encrypted.secretKey}}}.) Multiple layers of protection are in place, including AES 256 encryption, to keep your connection’s encrypted fields safe. When editing this form later, you must enter this value again; it is stored only when the connection is saved and never displayed as text.

5. Test the connection

Once you have configured the Oracle Autonomous Database / NSAW connection, click one of the following options:

• Save – click this button to test the connection, commit the new connection so that it will be available to all integrations for your account
• Save & close – click to test and save the connection and exit the Create connection pane
• Cancel – click to exit without saving any new changes
• Test connection – click this button to verify that your new connection is free of errors

When you test or save the connection, you will receive the following message:

The connection is added to your account.

• You can see it listed under Resources > Connections.
• If a connection is part of an integration, you can see it listed under Home > Integration name > Connections, and you may proceed to register the connection.