On this Page
...
You can create a Generic JDBC Account to connect to data sources that you want to use in your Pipelines. You can configure your S3 Generic JDBC account in SnapLogic using either the Designer or the Manager.
Snap-Account Compatibility
...
Configuring Generic JDBC Account Using SnapLogic Designer
Drag an a Generic JDBC Snap to the Canvas and click the Snap to open its settings. Click the Account tab. You can now either use an existing account or create a new one.
...
In the Account tab, click Add Account below the Account Reference field.
Select the Location in which you want to create the account, select the Generic JDBC Account Type, and click Continue. The Add Account dialog window associated with the account type is displayed.
Enter the required account details. Learn more on how to provide information for the account type in S3 Generic JDBC account.
Click Validate to verify the account, if the account type supports validation.
Click Apply to complete configuring the S3 Generic JDBC account.
| Info |
|---|
Enter additional information on this account in the Notes field of the Info tab. This will help you–and other users–understand the purpose of the account, especially if there are multiple accounts of the same type. |
...
In the left pane, browse to the project in which you want to create the account and click
> Account > JDBC > Generic JDBC Account, followed by the appropriate account type. The Create Account dialog associated with the selected account type is displayed.
Repeat steps 3 through 5 in the Creating the Creating an account sectionaccount section.
Avoid updating account credentials while 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.
| |
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.SQLServerDriverJDBC 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:
...
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 general information on Hive JDBC Drivers for HiveServer2.
...
| Note |
|---|
Oracle has stopped support for JDBC-ODBC Bridge from Java 8 and recommends using JDBC drivers provided by the vendor for database instead of the JDBC-ODBC Bridge. However, if the database vendor supports the JDBC ODBC bridge, then you can use it with the SnapLogic JDBC Snap Pack, but SnapLogic does not certify any JDBC ODBC bridge connections. |
SAP Hana
JDBC Driver Jar:
ngdbc.jarJDBC Driver Class:
com.sap.db.jdbc.DriverJDBC URL:
jdbc:sap://<host>:<port>/?currentschema=<your HANA Schema>
Sybase
JDBC Driver Jar:
jconn4.jarJDBC Driver Class:
com.sybase.jdbc4.jdbc.SybDriverJDBC URL:
dbc:sybase:Tds:<host>:<port2048>/<database>
...
If you have several JDBC accounts, one for system A and another for system B, then 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 the failing account, you must restart the JCC needs.
To disable the
mysql-cj-abandoned-connection-cleanupthread that is generated by MySQL JDBC driver, use the latest version of MySQL (later than 8.0.22), and add-Dcom.mysql.cj.disableAbandonedConnectionCleanup=trueto the jcc.jvm_options in the node properties under ‘Global Properties’.If the Snap fails to connect to the database, it will retry three more times.
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|