With the JDBC connector, you can use commands in a chain to perform structured query language (SQL) operations in on-premises solutions that support Java® database connectivity (JDBC). For example, with this connector, you can:
- Execute SQL commands, including a
- Retrieve details about a database table
- Insert records into a database via JDBC
Note: To connect to Amazon® Redshift®, IBM® Db2®, Microsoft® SQL Server®, MySQL®, NetSuite® JDBC, Oracle® Relational Database Management System (RDBMS) or Autonomous Data Warehouse (ADW), Postgres®, SAP HANA® JDBC, or Snowflake®, use its respective connector instead.
To secure the JDBC connection, the connector uses basic username and password authentication. To set up the connector, you'll need:
- A designated integration user set up in the solution to connect to
- The integration user's authentication credentials
- The JDBC connection's URL, such as
- A GroundRunner dedicated for the connector
- The JDBC driver for the connection, as either:
- The driver's Java archive (.JAR) file and its class name
- The path to the driver on the GroundRunner's file system
Set up the JDBC connector
Note: To make the connector available for use in your organization's chains, an org security administrator first enables it from Configuration.
- From Chain Builder, click Connections , and then Create at the top right.
- Under BizApp Connection, select JDBC and the GroundRunner to use with the connection.
- Under Basic Info, enter a unique name and description to help identify the connection.
- If you have the .JAR file for the connection's JDBC driver, upload it under Resources.
Note: If you don't have the driver's .JAR file, enter the path to its installation under Properties.
- Under Properties, enter the connection's details:
Property Details Username Enter the username for the connector's integration user. Password Enter the password for the Username property. Connection URL Enter the URL for the JDBC connection, such as
JDBC drive class If you uploaded the JDBC driver's .JAR file under Resources, enter its class name. For example, for Sybase®, enter
Path to JDBC driver If the .JAR file isn't uploaded under Resources, enter the path to the JDBC driver's installation on the GroundRunner's file system.
Note: All sensitive credentials are automatically encrypted and stored at Advanced Encryption Standard (AES)-256 encryption.
- Select the environments to use with the connection, and click Save.
- To test the connection, create and run a chain with the connector's Get Table Definition command, and verify it returns a valid output.
If the JDBC connection fails:
- Verify the integration user's authentication credentials.
- Check the URL for the JDBC connection, including its server, port, and database.
- Verify the JDBC driver class name or path entered for the connector.
If the connection fails to perform a command, verify its inputs—such as its SQL syntax or table—are valid.