Generic JDBC as a source

Select the Generic JDBC endpoint to load data from JDBC-compliant endpoints that are not currently supported by Autosync, such as Hive, Informix, or Sybase. The endpoint must support JDBC and you must provide the endpoint-specific JDBC JAR file. To provide the information SnapLogic AutoSync needs to connect to your source that supports JDBC, supply new credentials in the wizard or select saved credentials.

Note: AutoSync supports a variety of JDBC-compatible sources. We recommend using those source-specific endpoints instead of Generic JDBC because they take advantage of native functionality.

Supported account types

To provide connection information, you can enter credentials in AutoSync, Designer, or Classic Manager. Designer and Classic Manager offer multiple account types for most endpoints and not all types are compatible with AutoSync. When you create or edit a data pipeline, the existing credentials list includes only compatible account assets. AutoSync supports the following Designer and Classic Manager account types:

  • Generic Database Account

Known limitations

  • In Chrome version 113, closing the JDBC JAR file input window causes the account dialog to force close. You can still create or edit credentials using Add new credentials or Edit/Remove Credentials.
  • DB2 credentials created in AutoSync for the Generic JDBC endpoint don't work because you can't select a database name.

    Workaround: Create a Generic Database Account in Classic Manager, specify the database name, and select that account when using the Generic JDBC endpoint in AutoSync.

  • If you create the credentials in AutoSync, you can only upload one JAR file, the JDBC JAR. To use the Generic JDBC endpoint for databases that require two JAR files, such as Teradata:
    • create a Generic Database Account in Classic Manager that specifies the required JAR files.
    • Select that account when using the Generic JDBC endpoint in AutoSync.

Connection configuration

Generic JBDC properties include the following:

  • Account Properties
    • Credential label: A unique, meaningful name such as JBDC-Sales. If a configuration with the same name exists, AutoSync displays an Asset conflict error message.
    • JBDC JAR: An endpoint-specific JDBC JAR file.
    • JBDC Driver Class: The name of the JBDC driver associated with your endpoint.
    • JBDC Url: The JBDC Url to connect to your account.
    • Username: The username for an account with the correct permissions to write data. For example Sales-admin.
    • Password: The password for the account. Multiple retries with an invalid password can cause your account to be locked.
    • Share: (Optional) Select a user group to share this configuration with. Org admins create user groups to share credentials. If you are a member of a user group, you can select it from the dropdown. You can also select the global shared folder, which shares the credentials with everyone in your Org.
  • Validate and Save: After saving and validating, AutoSync adds the configuration to the list of saved credentials.
  • Select schema: AutoSync populates this list from the account. Choose the schema to use as the destination.
  • Select tables to synchronize: After configuring a destination, choose tables to synchronize. AutoSync populates the list from your endpoint.
  • Database: Select the database type.