Skip to main content
Version: 4

Custom CDATA connectors

Connectors help you connect to and exchange data with an application such as NetSuite, SAP, and Salesforce. While Adeptia Connect offers you some pre-bundled connectors, it also gives you the flexibility to add your own custom connectors. 

You can add a JDBC-based custom CDATA connector to the application. 

WarningThough you cannot add a new REST-based custom connector, you can still edit and use an existing one. 

This section guides you on how to add a custom connector and what you need to have to accomplish this task. 

Adding a CDATA custom connector​

Follow the steps below to add a CDATA custom connector.

  1. Obtain the CDATA Accelerator for the required Connector from the Adeptia support team.

  2. Deploy this Accelerator. 
    Refer to this page to learn how you can deploy the Accelerator.
    Once the Accelerator is deployed, the new CDATA driver is added to the list of available Database drivers for creating DBInfos.

  3. Click Configure.

  4. In the left panel, click APP CONNECTOR > Connectors (CDATA). 

  5. On the CDATA connectors' manage page, click Create CDATA Connector.

  6. On the Add CDATA Connector page, provide a name and description for the connector in the respective fields.
    The Select Connector Type field will already have JDBC as the connector type.

  7. In the Select Database Driver field, Select the Database driver you want to use for this connector.

    Information

    The selected Database driver should be the one deployed through Migration Utility.

  8. In the Provide Date Format field, enter the date format.

  9. In the Provide Time Zone field, enter the time zone. 

    InformationThe previous two fields, Provide Date Format and Provide Time Zone are optional and used to fetch incremental data. 

  10. Click **Save.
    **This adds the connector to the CDATA connectors' manage page.  

Using a CDATA custom connector​

When you use a CDATA Custom Connector in a Template/Transaction or a Process Flow with OAuth authentication, you must ensure that you:

  • Provide the Access Token, Refresh Token, Client Id, and Client Secret values in the Database Info activity associated with the Template/Transaction or Process Flow.

  • Set the OAuthSettingsLocation parameter in the Database Info activity associated with the Template/Transaction or Process Flow to avoid overriding of the OAuth settings of any other Database Info activity you may have used.

    Information

    OAuthSettingsLocation defines the location of the settings file where OAuth values are saved when InitiateOAuth is set to GETANDREFRESH or REFRESH.