JDBC Connector
The JDBC Connector provides database access to a variety of systems. You need a JDBC driver from the system provider to reach a system using JDBC.
This provider is typically delivered with the product in a JAR or .zip file. These files must be in your path or copied to the
jars/ directory of your
IBM® Security Verify Directory Integrator installation; otherwise you may get cryptic messages like "Unable to load T2 native library", indicating that the driver was not found on the classpath.
You will also need to find out which of the classes in this JAR or .zip file implements the JDBC driver; this information goes into the JDBC Driver parameter.
The JDBC Connector also provides multi-line input fields for the SELECT, INSERT, UPDATE and DELETE statements. When configured, the JDBC connector will use the value for any of these instead of its own auto-generated statement. The value is a template expanded by the parameter substitution module that yields a complete SQL statement. The template has access to the connector configuration as well as the searchcriteria and conn objects. The work object is not available for substitution, since the connector does not know what work contains. Additional provider parameters are also supported in the connector configuration.
The JDBC Connector supports the following modes: AddOnly, Update, Delete, Lookup, Iterator, Delta.
This Connector in principle can handle secure connections using the SSL protocol; but it may require driver-specific configuration steps in order to set up the SSL support. Refer to the manufacturer's driver documentation for details.
- Connector structure and workflow
The JDBC connector makes a connection to the specified data sources during the connector initialization. You can read further about it through the information provided here. - Understanding JDBC Drivers
You can have an understanding on JDBC Drivers through the information provided in section here. Further, you can also view about the installation and things to take care while installing the JDBC Drivers. - Specifying ODBC database paths
When you use ODBC connectivity using the JDBC-ODBC bridge (supported on Windows systems only) you can specify a database or file path the ODBC driver must use, if the ODBC driver permits. - Schema
You can use the information and link provided here to know about JDBC connector schema. - Configuration
You can configure the JDBC connector using the parameters provided here. - Customizing select, insert, update and delete statements
The JDBC connector has the ability to expand a SQL template before executing any of its SQL operations. There are five operations where the templates can be used. You can use the information provided here for understanding these operations. - Custom Prepared Statements
You can know about Custom Prepared Statements using the information provided here. - Additional JDBC Connector functions
Apart from the standard functions exposed by all Connectors, this Connector also exposes several other functions you can use in your scripts. You can call them using the information provided here. - Timestamps
You should take care of the provided details, if you want to store a timestamp value containing both a date and a time. - Padding
You can use the information provided here to know about padding, enabling / disabling it. - Calling Stored Procedures
The JDBC Connector's "getConnection()" method gives you access to the JDBC Connection object created when the connector has successfully initialized. You can know more about this in the provided section. - SQL Databases: column names with special characters
You should use the AddOnly or Update modes, if you have columns with special characters in their names. - Using prepared statements
You can use the information provided here to create SQL queries through JDBC connector. You can skip this section unless you are curious about the internals. - On Multiple Entries
You can use the information and link provided here to work with multiple entries. - Additional built-in reconnect rules
The JDBC Connector takes advantage of the Reconnect engine that is part of IBM® Security Verify Directory Integrator. You can know more about this through the information provided here.