Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

On this Page

...

You can create a Generic JDBC Account to connect to data sources that you want to use in your Pipelinespipelines. You can configure your Generic JDBC account in SnapLogic using either the Designer or the Manager.

Snap-Account Compatibility

Configuring Generic JDBC Account Using SnapLogic Designer

...

SnapLogic organizes and displays all accounts to which you have access to, sorting them by account type and location. To select an existing account:

  1. In the Account tab, click the Expand(blue star) icon to view the accounts to which you have access , to and select the an account that you want to use.

  2. Click the Save (blue star) icon.

Creating an account

...

You can use Manager to create accounts without associating them immediately with Pipelinespipelines.

Accounts in SnapLogic are associated with projects. You can use accounts created in other projects only if you have at least Read access to them.

...

Avoid updating account credentials while Pipelines pipelines using that account are executing. Doing so may lead to unexpected results, including your account getting locked.

Account Encryption

Standard Encryption

If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.

Enhanced Encryption

If you have the Enhanced Account Encryption feature, the following fields are encrypted for each sensitivity level selected for this account.

  • High: Password

  • Medium + High: Username, password

  • Low + Medium + High: Username, password, JDBC URL

Active Directory authentication

SnapLogic supports Active Directory authentication for SQL server for mssql-jdbc-6.2.2-jre8.jar driver. Ensure that you have installed the mssql-jdbc-6.2.2-jre8.jar file. Also, use the following configurations in Account Settings to configure Active Directory authentication:

  • JDBC Driver class: com.microsoft.sqlserver.jdbc.SQLServerDriver

  • JDBC Connection URL: jdbc:sqlserver://ServerNameFQDN:portNumber;databaseName=DBNAME

SnapLogic supports Active Directory authentication for SQL Server using the User impersonation method. The prerequisites are as follows:

...

Athena JDBC Driver 1.x versions are deprecated, and the Generic JDBC Snaps are not compatible with them. Therefore, we recommend you to use Athena JDBC Driver 2.x or later for the AWS Athena database when using Generic JDBC Snaps.

...

To connect to the Cassandra database using the Cassandra Simba driver, ensure that the appropriate Simba JAR files are installed based on the version of JDK in the Snaplex node. Contact your Org admin to know the JDK in the Snaplex node. Learn more about the JAR version to be used: JDBC Install Guide.

Besides the JAR files, configure the following settings in the Account Settings when using the Cassandra Simba driver:

  • JDBC Driver class"com.simba.cassandra.jdbc42.Driver"

  • JDBC URL: jdbc:cassandra://<host>:<port>;AuthMech=1;UID=<user id>;PWD=<password>;DefaultKeyspace=<database name>

  • Database name: Auto detect

For JDK

8

11 and Above

  • For JDK 8 11 and above, use version 4.2 of the Cassandra Simba Driver.

  • Of the JARs included with version 4.2, do not include the following since they are already provided as part of the Snap pack:

    • asm-5.0.3.jar

    • guava-16.0.1.jar

    • jackson-annotations-2.6.0.jar

    • jackson-core-2.6.3.jar

    • jackson-databind-2.6.3.jar

    • joda-time-2.9.1.jar

    • metrics-core-3.1.2.jar

    • snappy-java-1.1.2.6.jar

    • slf4j-api-1.7.7.jar

    • netty-transport-4.0.37.Final.jar

    • netty-handler-4.0.37.Final.jar

    • netty-common-4.0.37.Final.jar

    • netty-codec-4.0.37.Final.jar

    • netty-buffer-4.0.37.Final.jar

...

jConnect provides high performance native access to the complete family of Sybase products, including Adaptive Server Enterprise, Adaptive Server Anywhere, Adaptive Server IQ, and Replication Server.

...

The jConnect JDBC driver is usually delivered as a zip file. First, you need to unzip this file and locate the jconn4.jar file, which usually is stored in the classes directory.

You can download the Sybase JDBC Driver from here: http://www.sybase.com/products/allproductsa-z/softwaredeveloperkit/jconnect here.

Another open-source alternative to connect Sybase database is  jTDS Drivers, which you can find at http://jtds.sourceforge.net/.

jTDS Driver 

  • DRIVER CLASS: net.sourceforge.jtds.jdbc.Driver 

  • JDBC URL FORMAT: jdbc:jtds:sybase://<host>[:<port>][/<database_name>] 
    Examples:  jdbc:jtds:sybase://127.0.0.1:5000/SAMPLE

Examples

This section provides examples of JDBC connection details for different sources. Note that specifics may vary based on the Operating System or Database version.

Hive

Varies based on version. See https://cwiki.apache.org/confluence/display/Hive/HiveServer2+Clients#HiveServer2Clients-JDBC  for for general information on Hive JDBC Drivers for HiveServer2.

...

Note

Oracle does not support the JDBC-ODBC Bridge from Java 8 and recommends using JDBC drivers provided by the vendor for database. However, if the database vendor supports the JDBC ODBC bridge, then you can use it with the JDBC Snap Pack, but SnapLogic does not certify any JDBC ODBC bridge connections.

SAP Hana

  • JDBC Driver Jar: ngdbc.jar

  • JDBC Driver Class:  com.sap.db.jdbc.Driver

  • JDBC URL: jdbc:sap://<host>:<port>/?currentschema=<your HANA Schema> 

Sybase

  • JDBC Driver Jar: jconn4.jar

  • JDBC Driver Classcom.sybase.jdbc4.jdbc.SybDriver

  • JDBC URL: dbcjdbc:sybase:Tds:<host>:<port2048>/<database> 

...

  • If you have several JDBC accounts, one for system A and another for system B, you must ensure that all drivers can be loaded. If driver A fails to load, then driver B will always fail, even if it is a valid driver, as this is the expected behavior of the JDBC driver registry. It loads all drivers and goes through them in sequence. If any driver fails in the process, all drivers loaded later will also fail. Once you fix the driver for After fixing the failing account's driver, you must restart the JCC needsnodes.

  • To disable the mysql-cj-abandoned-connection-cleanup  thread that is generated by MySQL JDBC driver, use the latest version of MySQL (later than 8.0.22) , and add the following settings in the Node Properties:

Key

Value

jcc.jvm_options

-Dcom.mysql.cj.disableAbandonedConnectionCleanup=true 

If the Snap fails to connect to the database, it retries three times.excerpt

Snap Pack History

Expand

Multiexcerpt-include-macro
nameJDBC

...

_SPH
templateData[]
pageJDBC Snap Pack

...

addpanel

...

false