JDBC connector

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 CREATE or UPDATE statement or SELECT query
• 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.

Prerequisites

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 you're connect to.
• The integration user's authentication credentials.
• The JDBC connection's URL, such as jdbc:solution://host:port/database
• A GroundRunner dedicated to the connector; CloudRunners are not supported.
• The JDBC driver for the connection, including its class name and path on the GroundRunner's file system.

Note: The driver must be located on the GroundRunner -- .jar files can't be uploaded to the Resources field.

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.

1. From Chain Builder, click Connections  compare_arrows, and then Create at the top right.
2. Under BizApp Connection, select JDBC and the GroundRunner to use with the connection.
   
3. Under Basic Info, enter a unique name and description to help identify the connection.
4. 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:solution://host:port/database.
   JDBC drive class	Enter the class name for the JDBC driver's .jar file. For example, for Sybase®, enter com.sybase.jdbc.sybdriver.
   Path to JDBC driver	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.

5. Select the environments to use with the connection, and click Save.
6. To test the connection, create and run a chain with the connector's Get Table Definition command, and verify it returns a valid output.

Troubleshooting

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.