Loading Additional Drivers
This article describes how to add external drivers not included with the MDM packages.
Overview
Drivers for some of the third-party data sources and other components are not included in standard packages due to the size or licensing reasons.
It is, however, possible for the MDM Server to load those additional drivers from a designated external drivers folder specified in the MDM Server application.properties
(see MDM Server Application Properties, section External drivers folder (named lib-ext
by default).
The individual JARs can be stored in subfolders.
See the following sections for examples of configuration and lists of drivers required by the third-party components.
Azure Data Lake Storage
Configuration
<config class="com.ataccama.dqc.azure.config.AzureGen2Contributor">
<azureGen2Connections>
<azureGen2Connection authType="AAD_CLIENT_CREDENTIAL" clientId="<client_id>" authenticateUser="false" clientKey="<client_key>" containerName="<container_name>" name="adls" storageAccount="<storage_account>" authTokenEndpoint="<oauth2_token_endpoint>"/>
</azureGen2Connections>
</config>
Drivers
Required JARs |
---|
|
Amazon SQS
Configuration
<component class="com.ataccama.dqc.jms.JmsProviderComponent">
<connectionPoolSize>5</connectionPoolSize>
<jmsResources>
<resource>awssqsmdm</resource>
</jmsResources>
</component>
<config class="com.ataccama.dqc.jms.config.JmsContributor">
<jmsConnections>
<jmsConnection connectionFactory="QueueConnectionFactory" name="awssqsmdm">
<contextParams>
<contextParam name="java.naming.factory.initial" value="com.ataccama.dqc.jms.sqs.SQSInitialContextFactory"/>
<contextParam name="java.naming.provider.url" value="https://sqs.eu-central-1.amazonaws.com/773634404733/awssqsmdmqueue"/>
<contextParam name="region" value="eu-central-1"/>
<contextParam name="queue.awssqsmdmqueue" value="awssqsmdmqueue"/>
<contextParam name="authType" value="AWS_ACCESS_KEY"/>
<contextParam name="accessKey" value="crypted:AES:{value}"/>
<contextParam name="secretKey" value="crypted:AES:{value}"/>
</contextParams>
</jmsConnection>
</jmsConnections>
</config>
Active MQ, Rabbit MQ, IBM Websphere MQ, Tibco MQ
Configuration
<component class="com.ataccama.dqc.jms.JmsProviderComponent">
<connectionPoolSize>5</connectionPoolSize>
<jmsResources>
<resource>{QUEUE NAME}</resource>
</jmsResources>
</component>
<config class="com.ataccama.dqc.jms.config.JmsContributor">
<jmsConnections>
<jmsConnection connectionFactory="QueueConnectionFactory" name="{QUEUE NAME}">
<contextParams>
<contextParam name="java.naming.factory.initial"
value="org.apache.activemq.jndi.ActiveMQInitialContextFactory"/>
<contextParam name="java.naming.provider.url" value="tcp://localhost:61616"/>
</contextParams>
</jmsConnection>
...
</jmsConnections>
</config>
Drivers
Active MQ |
---|
Included in the standard package |
Rabbit MQ |
|
IBM WebSphere |
|
Tibco MQ |
|
HBase
Configuration
<dataSource driverClass="cdata.jdbc.apachehbase.ApacheHBaseDriver" url="jdbc:apachehbase:Server=127.0.0.1;Port=8080;" name="HBase-CData" user="<user_name>" password="<password>">
<properties/>
<propertiesEncrypted/>
<propertiesFile/>
<propertiesFileEncrypted/>
</dataSource>
Salesforce
Configuration
<config class="com.ataccama.extension.salesforce.dqc.config.SalesforceContributor">
<salesforceConnections>
<connection name="SFServer" credentialsType="login" password="<password>" secretToken="<secret_token>" username="<user_name>" />
</salesforceConnections>
</config>
Parquet File Reader
Drivers
Required JARs |
---|
|
Additional JARs for use with AWS and Azure |
|
Was this page useful?