Use these tips to help you determine if a JDBC Data Mediator
Service suits the requirements of your application serving environment.
Driver requirements for using SDO
to access DB2 UDB for iSeries
Because
the SDO JDBC Mediator takes advantage of the ResultSetMetaData interface
in JDBC 2.0, it must use JDBC providers that are fully compliant with
that specification. Both the IBM
® Developer Kit for Java JDBC driver (also known as the DB2 UDB
for iSeries Native driver) and the IBM Toolbox
for Java JDBC driver meet this criteria for JDBC
access to DB2 UDB for iSeries.
For performance reasons, however, neither of these drivers have default
settings to return all the information that the mediator requires.
You must set a connection property on the JDBC provider or data source
that corresponds to each driver for it to return full ResultSetMetaData
data sets.
The property you use varies according to how your driver
implementation acquires database connections.
- If your driver gets connections through the DriverManager class,
set the JDBC provider URL property extended metadata to true: extended
metadata=true. In this scenario, both the IBM Developer
Kit for Java and IBM Toolbox
for Java JDBC drivers require the same setting on
the JDBC provider object.
- If your application acquires connections through a data source,
set a different custom property on the data source, depending on the
driver that you use:
- For the IBM Toolbox for Java JDBC
driver, set the custom property extendedMetaData to
true.
- For the IBM Developer Kit for Java JDBC
driver, set the custom property returnExtendedMetaData to
true.