Use this task to configure the application data source Java™ Database Connectivity (JDBC) provider to
use pureQuery to access DB2® in a Java EE
environment.
Before you begin
If you need to use multiple DB2 package
collections, see the information center topic, Configuring pureQuery
to use multiple package collections, before continuing
with this task.
About this task
PureQuery makes use
of DB2 packages. These packages consist of information
for one or more SQL statements and are stored in the DB2 catalog.
You must first run the wsdb2gen command on a JPA application to
create the packages. The wsdb2gen command creates an XML file containing
SQL statement information. This XML file must be included into the
application Java archive (JAR) file. The DB2 bind
command uses this file as input to create the DB2 package.
Attention: Read more about the DB2 JAR level compliance for
pureQuery at the IBM Support Website: System requirements for IBM
Optim pureQuery Runtime for Linux, UNIX, and Windows.
Procedure
- Update the application data source JDBC provider configuration
to include the pureQuery runtime JAR file. Either define
an new JDBC provider or modify an existing provider to include the
following JAR files. See information center topics on JDBC provider
settings and installing pureQuery Runtime for more information.
- Using the DB2 bind command, bind the XML file
to the database. This creates the DB2 packages.
There are three ways to do this:
- Use the wsadmin command. Refer to the information center topic
on application management command group for the AdminTask object for
more information.
- Using the administrative console. Refer to the information center
topic on SQLj profiles and pureQuery bind files settings for more
information.
- Using the DB2 bind command provided by Data Studio. Refer
to the information center topic on the pureQuery Bind utility for
more information.
What to do next
If you want to reconfigure the data source for JDBC, just
remove the pdq.jar and pdqmgmt.jar from the class
path.