Zendesk
Building the JDBC URL
After installing the license, access the connection management page by executing the command java -jar kingswaysoft.jdbc.jar
. Enter the necessary details, and the program will automatically generate the JDBC connection URL. Users can click Test Connection to test the generated URL, and Copy to Clipboard to copy the connection string for use within the application where the JDBC driver is being used.
Note: If the license is not installed, you can still use the connection manager to generate a JDBC URL; however, the 'Test Connection' feature will be disabled.
General Page
The General page allows you to specify connection properties and login credentials for the Zendesk REST service.
- General Settings
-
- Subdomain
-
This option allows you to specify the subdomain of your Zendesk account.
- API Throttling Rate
-
The API Throttling Rate will limit the number of requests that can be sent per the unit of time selected. Set this value to 0 to disable API throttling.
- Authentication
-
- Authentication Mode
-
The Authentication Mode option allows you to choose the method used to authenticate with the Zendesk API. Available options are:
- API Token
- OAuth Authorization Code
- OAuth Client Credentials
Authentication Methods for Zendesk
API Token
Use an API Token to establish a connection.
- Username
-
The Username to use when accessing Zendesk service.
- API Token
-
The API Token to use when accessing Zendesk service.
OAuth Authorization Code
Use a saved token file along with its token password to establish a connection. To generate a new token file, click Generate Token File and follow the on-screen process. After saving the token file locally, enter the token password to connect. A dropdown menu allows you to customize where the access token appears in your request.
- Generate Token
-
This button completes the OAuth authentication process in order to generate a new access token.
- Client Id: The Client Id option allows you to specify the unique ID which identifies the application making the request.
- Client Secret: The Client Secret option allows you to specify the client secret belonging to your app.
- Redirect Url: The Redirect Url option allows you to specify the Redirect Url to complete the authentication process.
- Scope: The Scope option allows you to specify the scope of the token file being generated.
- PKCE (Enhanced Security): The PKCE (Proof Key for Code Exchange) option may be enabled for PKCE App Type. Ensures that the client that initiates the OAuth flow is the same client that completes flow.
- Path to Token File
-
The path to the token file on the file system.
- Token File Password
-
The password of the token file.
OAuth Client Credentials
Use your ClientId, and ClientSecret to establish an OAuth connection.
- Client Id
-
The Client Id OAuth parameter.
- Client Secret
-
The Client Secret OAuth parameter.
After all the connection information has been provided, click the "Test Connection" button to test if the user credentials entered can successfully connect to the selected service.
Advanced Settings Page
The Advanced Settings page allows you to specify advanced settings for the connection.
- Proxy Mode
-
The Proxy Mode option allows you to specify how you want to configure the proxy server setting. There are three options available.
- No Proxy
- Auto-detect (Use system configured proxy)
- Manual
- Proxy Server
-
Using the Proxy Server option allows you to specify the name of the proxy server for the connection.
- Port
-
The Port option allows you to specify the port number of the proxy server for the connection.
- Username (Proxy Server Authentication)
-
The Username option (under Proxy Server Authentication) allows you to specify the proxy user account.
- Password (Proxy Server Authentication)
-
The Password option (under Proxy Server Authentication) allows you to specify the proxy user's password.
- Timeout (secs)
-
The Timeout (secs) option allows you to specify a timeout value in seconds for the connection. The default value is 120 seconds. Specify 0 for infinite timeout.
- Retry on Intermittent Errors
-
The retry on intermittent errors determines if requests will be retried when there is an error. If this option is checked requests will be retried up to 3 times.
- Ignore Certificate Errors
-
This option can be used to ignore those SSL certificate errors when connecting to the target server.
Warning: Enabling the "Ignore Certificate Errors" option is generally NOT recommended, particularly for production instances. Unless there is a strong reason to believe the connection is secure - such as the network communication is only happening in an internal infrastructure, this option should be unchecked for best security.
Note: When this option is enabled, it applies to all HTTP-based SSL connections in the same job process.
- Concurrent Writing Threads
-
This option can be used to set the number of threads to be used during write operations. This can improve performance during large-volume write operations.
Using the JDBC Driver
Explore detailed examples in this section that demonstrate the application of JDBC classes such as Connection, Statement, and ResultSet to effectively manage interactions with Zendesk data. This section covers the use of regular statements and prepared statements for executing complex or frequently executed queries.
Executing Statements
Once you've connected from your code (see Connecting with DriverManager and Connecting with DataSource), you can execute SQL statements using the Statement class. Refer to the Executing Prepared Statements section for information on how to execute parameterized statements.
SELECT
Use the Statement class's generic execute method or the executeQuery method to execute SQL statements that return data. To retrieve the results of a query, you would then call the getResultSet method of the Statement.
String sql = "SELECT TOP 50 * FROM tickets"; try { ResultSet resultSet = statement.executeQuery(sql); LOGGER.info(resultSet.toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
INSERT
Use either the generic execute method or the executeUpdate method of the Statement class to execute an INSERT operation.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the inserted data's ID, exceptions raised during execution, and details of the affected data.
String sql = "INSERT INTO users (email, name, organization.name) VALUES ('[email protected]', 'tester3', 'KingswaySoft')"; try { statement.executeUpdate(sql); LOGGER.info(statement.getResultSet().toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
id,errorcode,errormessage,processdata,haserrors 39982357595284,null,null,{"user":{"email":"[email protected]","name":"tester3","organization":{"name":"KingswaySoft"}}},false
UPDATE
Use either the generic execute method or the executeUpdate method of the Statement class to execute an UPDATE operation.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the updated data's ID, exceptions raised during execution, and details of the affected data.
String sql = "UPDATE tickets SET subject = 'updated ticket subject' WHERE ticket_id = 744"; try { statement.executeUpdate(sql); LOGGER.info(statement.getResultSet().toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
id,errorcode,errormessage,processdata,haserrors 744,null,null,{"ticket":{"subject":"updated ticket subject"}},false
DELETE
Use either the generic execute method or the executeUpdate method of the Statement class to execute a DELETE operation.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the deleted data's ID, exceptions raised during execution, and details of the affected data.
String sql = "DELETE FROM tickets WHERE ticket_id = 8830"; try { statement.executeUpdate(sql); LOGGER.info(statement.getResultSet().toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
id,errorcode,errormessage,processdata,haserrors null,null,null,null,false
UPSERT
Using the UPSERT operation, you can either insert or update an existing record in one call.
Not all tables support the upsert operation. Query the system.tables table to identify which tables support UPSERT operations.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the ID of upserted data, exceptions raised during execution, and the data affected by the upserting.
String sql = "UPSERT INTO users (email, external_id, name, password, organization_id, organization.name, role) VALUES " + "('[email protected]', 'external_id1', 'John', 'example', 360001043154, 'KingswaySoft', 'end-user')"; try { statement.executeUpdate(sql); LOGGER.info(statement.getResultSet().toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
id,errorcode,errormessage,processdata,haserrors,isnew 40911484513172,null,null,{"user":{"email":"[email protected]","external_id":"external_id1","name":"John","password":"****","organization_id":360001043154,"organization":{"name":"KingswaySoft"},"role":"end-user"}},false,true
Executing Prepared Statements
Using a PreparedStatement can improve performance when you need to execute a SQL statement multiple times with different parameters. Unlike a Statement object, a PreparedStatement object is provided with a SQL statement when it is created, which can then be executed with different values each time. This special type of statement is derived from the more general class, Statement.
Below are the steps outlining how to execute a prepared statement:
- Create a PreparedStatement: Use the prepareStatement method of the Connection class to instantiate a PreparedStatement. Refer to Connecting with DriverManager or Connecting with DataSource for information related to establishing connections.
- Set Parameters: Declare parameters by calling the corresponding setter method of the PreparedStatement. Note: The parameter indices start at 1.
- Execute the Prepared Statement: Use the generic execute or executeUpdate method of the PreparedStatement.
- Retrieve Results: Call the getResultSet method of the Prepared Statement to obtain the query results, which will be returned as a ResultSet.
- Iterate Over the Result Set: Use the next method of the ResultSet to iterate through the results. To obtain column information, utilize the ResultSetMetaData class. Instantiate a ResultSetMetaData object by calling the getMetaData method of the ResultSet.
SELECT
Use the Statement class's generic execute method or the executeQuery method to execute SQL statements that return data.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the retrieved data.
String sql = "SELECT * FROM accounts/available WHERE subdomain = ?"; try { PreparedStatement ps = connection.prepareStatement(sql); ps.setString(1, "d3vkingswaysoftsandbox"); boolean ret = ps.execute(sql); if (ret) { ResultSet rs = ps.getResultSet(); LOGGER.info(rs.toString()); } } catch (SQLException e) { LOGGER.severe(e.toString()); }
INSERT
Use either the generic execute method or the executeUpdate method of the PreparedStatement class to execute an INSERT operation.
The results of SQL queries are saved in a ResultSet. Users can retrieve the ResultSet after execution to view the ID of inserted data, exceptions raised during execution, and the data affected by the insertion.
String sql = "INSERT INTO NewObject (custom_object_fields.textfield, name) VALUES (?, ?)"; try { PreparedStatement ps = connection.prepareStatement(sql); ps.setString(1, "text123"); ps.setString(2, "testName2"); ps.executeUpdate(); LOGGER.info(ps.getResultSet().toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
id,errorcode,errormessage,processdata,haserrors 01K1XV7YKVX9B58R3QBNY6KKZA,null,null,{"custom_object_record":{"custom_object_fields":{"textfield":"text123"},"name":"testName2"}},false
UPDATE
Use either the generic execute method or the executeUpdate method of the Statement class to execute an UPDATE operation.
The results of SQL queries are saved in a ResultSet. Users can retrieve the ResultSet after execution to view the ID of updated data, exceptions raised during execution, and the data affected by the update.
String sql = "UPDATE tickets SET subject = ? WHERE ticket_id = ?"; try { PreparedStatement ps = connection.prepareStatement(sql); ps.setString(1, "updated ticket subject"); ps.setString(2, "744"); ps.executeUpdate(); LOGGER.info(ps.getResultSet().toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
id,errorcode,errormessage,processdata,haserrors 744,null,null,{"ticket":{"subject":"updated ticket subject"}},false
DELETE
Use either the generic execute method or the executeUpdate method of the Statement class to execute a DELETE operation.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the deleted data's ID, exceptions raised during execution, and details of the affected data.
String deleteSql = "DELETE FROM tickets WHERE ticket_id = ?"; try { PreparedStatement ps = connection.prepareStatement(deleteSql); ps.setString(1, "8838"); ps.executeUpdate(); LOGGER.info(ps.getResultSet().toString()); } catch (SQLException e) { e.printStackTrace(); }
id,errorcode,errormessage,processdata,haserrors null,null,null,null,false
UPSERT
Using the UPSERT operation, you can either insert or update an existing record in one call.
Not all tables support the upsert operation. Query the system.tables table to identify which tables support UPSERT operations.
The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the ID of upserted data, exceptions raised during execution, and the data affected by the upserting.
String sql = "UPSERT INTO users (email, external_id, name, password, organization_id, organization.name, role) " + "VALUES (?, ?, ?, ?, ?, ?, ?)"; try (PreparedStatement ps = connection.prepareStatement(sql)) { ps.setString(1, "[email protected]"); ps.setString(2, "external_id2"); ps.setString(3, "John"); ps.setString(4, "example"); ps.setString(5, "360001043154"); ps.setString(6, "KingswaySoft"); ps.setString(7, "end-user"); statement.executeUpdate(sql); LOGGER.info(statement.getResultSet().toString()); } catch (SQLException e) { LOGGER.severe(e.toString()); }
id,errorcode,errormessage,processdata,haserrors,isnew 40911591266452,null,null,{"user":{"email":"[email protected]","external_id":"external_id2","name":"John","password":"****","organization_id":360001043154,"organization":{"name":"KingswaySoft"},"role":"end-user"}},false,true
Metadata Discovery
This section provides examples on how to retrieve table and column metadata using the getTables and getColumns methods from the DatabaseMetaData interface. These are essential for discovering database structures.
Tables
The getTables method from the DatabaseMetaData interface can be used to retrieve a list of tables.
This method only retrieves tables that are not write-only.
To get a list of tables which include write-only tables, query the table [system.tables](/products/jdbc-driver-pack/help-manual/advancedfeatures#systemtables).
try { Connection connection = buildRestConnectionFromDriverManager(); ResultSet rs = connection.getMetaData().getTables(null, null, null, null); LOGGER.info("\r\n" + rs.toString()); } catch (SQLException e) { LOGGER.severe(e.getMessage()); }
TABLE_CAT,TABLE_SCHEM,TABLE_NAME,TABLE_TYPE,REMARKS null,null,account/settings,Table,nullnull,null,accounts/available,Table,nullnull,null,activities,Table,nullnull,null,approval_workflow_instances/approval_requests,Table,nullnull,null,attachments,Table,nullnull,null,audit_logs,Table,null ......
The getTables method returns the following metadata columns:
Column Name | Data Type | Description |
---|---|---|
TABLE_CAT | String | The catalog that contains the table. |
TABLE_SCHEM | String | The schema of the table. |
TABLE_NAME | String | The name of the table. |
TABLE_TYPE | String | The type of the table (e.g., TABLE or VIEW). |
REMARKS | String | An optional description of the table. |
Columns
Use the getColumns method of the DatabaseMetaData interface to retrieve detailed information about database columns. To narrow the results to a specific table, specify the table name using the parameter table_name
.
This method returns columns only for tables that are not write-only.
To get columns for tables which are write-only, query the table [system.columns](/products/jdbc-driver-pack/help-manual/advancedfeatures#systemcolumns).
try { Connection connection = buildRestConnectionFromDriverManager(); ResultSet rs = connection.getMetaData().getColumns(null, null, "tickets", null); LOGGER.info(rs.toString()); } catch (SQLException e) { e.printStackTrace(); }
TABLE_CAT,TABLE_SCHEM,TABLE_NAME,COLUMN_NAME,DATA_TYPE,TYPE_NAME,COLUMN_SIZE,BUFFER_LENGTH,DECIMAL_DIGITS,NUM_PREC_RADIX,NULLABLE,REMARKS,COLUMN_DEF,SQL_DATA_TYPE,SQL_DATETIME_SUB,CHAR_OCTET_LENGTH,ORDINAL_POSITION,IS_NULLABLE,IS_AUTOINCREMENT,IS_GENERATEDCOLUMN,DTS_TYPE null,null,tickets,Age.360001835774,-5,BIGINT,null,null,0,0,null,null,null,-5,null,null,null,null,null,null,DT_I8 null,null,tickets,Assignee.360000323234,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,DT_WSTR null,null,tickets,Big_Text.360001835754,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,DT_WSTR null,null,tickets,Custom_Field.360000491168,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,DT_WSTR null,null,tickets,Description.360000323134,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,DT_WSTR null,null,tickets,id,-5,BIGINT,null,null,0,0,null,null,null,-5,null,null,null,null,null,null,DT_I8 ......
The getColumns method returns the following columns:
Column Name | Data Type | Description |
---|---|---|
TABLE_CAT | String | The database name. |
TABLE_SCHEM | String | The table schema. |
TABLE_NAME | String | The table name. |
COLUMN_NAME | String | The column name. |
DATA_TYPE | Integer | The data type represented by a constant value from java.sql.Types. |
TYPE_NAME | String | The data type name used by the driver. |
COLUMN_SIZE | Integer | The length in characters of the column or the numeric precision. |
BUFFER_LENGTH | Integer | The buffer length. |
DECIMAL_DIGITS | Integer | The column scale or number of digits to the right of the decimal point. |
NUM_PREC_RADIX | Integer | The radix, or base. |
NULLABLE | Integer | Whether the column can contain null as defined by the following JDBC DatabaseMetaData constants: columnNoNulls (0) or columnNullable (1). |
REMARKS | String | The comment or note associated with the object. |
COLUMN_DEF | String | The default value for the column. |
SQL_DATA_TYPE | Integer | Reserved by the specification. |
SQL_DATETIME_SUB | Integer | Reserved by the specification. |
CHAR_OCTET_LENGTH | Integer | The maximum length of binary and character-based columns. |
ORDINAL_POSITION | Integer | The position of the column in the table, starting at 1. |
IS_NULLABLE | String | Whether a null value is allowed: YES or NO. |
IS_AUTOINCREMENT | String | Whether the column value is assigned by Zendesk in fixed increments. |
IS_GENERATEDCOLUMN | String | Whether the column is generated: YES or NO. |
DTS_TYPE | String | Object DTS attribute type. |
Primary Keys
The getPrimaryKeys method in the DatabaseMetaData interface is used to retrieve metadata about primary keys for a given table in Zendesk.
try { Connection connection = buildRestConnectionFromDriverManager(); ResultSet resultSet = connection.getMetaData().getPrimaryKeys(null, null, "tickets"); LOGGER.info("\r\n" + resultSet.toString()); Assertions.assertNotNull(resultSet); } catch (SQLException e) { LOGGER.severe(e.getMessage()); }
TABLE_NAME,PRIMARY_COLUMN_NAME tickets,id
The getPrimaryKeys method returns the following columns:
Column Name | Data Type | Description |
---|---|---|
TABLE_NAME | String | The name of the table that contains the primary key. |
PRIMARY_COLUMN_NAME | String | The name of the column that serves as the primary key for the table. |
Connection Settings
Connection Setting | Type | Default Value | Description |
---|---|---|---|
ApiThrottleRate | Integer | 0 | The maximum number of API requests a client can make to the server within a specific time period, defined in the ThrottleRateUnit setting. A value of 0 disables throttling. |
ApiToken | String | "" | The API Token allows requests to authenticate using a static access token. Must be used in combination with UserName. |
AuthenticationMode | String | "OAuth Authorization Code" | AuthenticationMode specifies the method used to authenticate when connecting to the Zendesk API. |
CacheExpirationTime | Integer | 30 | Defines the expiration time for cache. A value of 0 disables caching. |
ClientId | String | "" | The Client ID to be used when authenticating via OAuth Client Credentials |
ClientSecret | String | "" | The Client Secret to be used when authenticating via OAuth Client Credentials. |
ConcurrentWritingThreads | Integer | 1 | The number of threads for executing operations in parallel. A value of 0 will disable multi threading. |
ConnectionTimeout | Integer | 30 | ConnectionTimeout is the maximum amount of time the program will wait to set up a connection to the Zendesk API. |
IgnoreCertificateErrors | Boolean | false | Specifies whether to verify the certificate when connecting to Zendesk. If certificate verification is not required, you can set this value to 'true'. |
IgnoreError | Boolean | false | Determines if the program continues executing SQL statements after encountering an error. |
LogFileSize | String | "10485760" | A string specifying the maximum size in bytes for a log file. |
LogLevel | String | "INFO" | The logging level for the JDBC driver. |
LogPath | String | "./jdbcLogs" | The directory where log files are stored. |
OemKey | String | "" | The OEM license key. |
PathToTokenFile | String | "" | The path to the token file. |
ProxyMode | String | NoProxy | This setting configures the proxy. Allowed values are "NoProxy", "AutoDetect" and "Manual". |
ProxyPassword | String | "" | The password to be used to authenticate to the proxy. |
ProxyServer | String | "" | The host of the proxy server. |
ProxyServerPort | Integer | 0 | The port of the proxy server. |
ProxyUsername | String | "" | The username to be used to authenticate to the proxy. |
ReadBatchSize | Integer | 100 | ReadBatchSize is used to set how many records can be read from Zendesk in a single call. |
ResultPath | String | "" | The path where the execution result files are saved. |
RetryOnIntermittentErrors | Boolean | true | The RetryOnIntermittentErrors parameter indicates whether to retry the connection when it might occasionally fail due to temporary issues. |
SaveResult | Boolean | false | The SaveResult parameter indicates whether to save the execution results to a file. |
ServiceName | String | "" | The ServiceName refers to the name of the service API selected by the user. |
ServiceTimeout | Integer | 120 | The ServiceTimeout is the timeout to receive the full response from Zendesk API. |
Suppress404NotFoundError | Boolean | true | When set to true, if a query results in an HTTP 404 error, a result set will still be created. When set to false, an error is logged instead and no result set is created. |
ThrottleRateUnit | String | "PerMinute" | The unit of time for limiting API requests to avoid being throttled. Valid values include, "PerSecond", "PerMinute" and "PerHour". |
TokenPassword | String | "" | The password used to read the token file. |
UserName | String | "" | The UserName is used in API Token authentication. It is the User Name of the account associated with the provided API Token |
WriteBatchSize | Integer | 1 | WriteBatchSize is used to set how many records can be written to Zendesk in a single call. At this time, Zendesk does not support batch writing. As such, the value of this property should be kept at 1. |