When you use the workbench to configure the static execution
of SQL statements in non-pureQuery API applications, you can use a
number of helpful features.
- Automatic configuration of your Java™ projects
- After you create a Java project
that contains your non-pureQuery API application, you can enable support
for capturing and binding the SQL statements in your application.
When you enable that support, the workbench adds the required JAR
files to your project's build path. The workbench also creates the
following files, or modifies them if they already exist:
- pdq.properties
- Use this file to set the properties that are needed by the IBM® Data Server Driver for JDBC
and SQLJ.
- Default.genProps
- Use this file to set the collection, root name, and version ID
for DB2® packages that you create.
- Do not rename this file.
- Default.bindProps
- Use this file to set options for binding SQL statements into the
packages that you specified in the Default.genProps file. If you create
more than one pureQueryXML file, you can set these options for each.
- Do not rename this file. When you bind captured SQL statements,
the workbench expects the bind options to be in a file with this name.
- Tools for creating JUnit tests for running the SQL statements
that you want to capture
- To capture the SQL statements that you plan to run statically,
you must run them either from your non-pureQuery API application or
by means of JUnit tests. If you want to use JUnit tests, you can use
workbench tools for writing and running JUnits.
- Ease of switching connections for binding against different databases
- When you bind the SQL statements that are in a pureQueryXML file,
you can bind against the database that is associated with your Java project or against other databases.
If your non-pureQuery API application runs SQL statements on different DB2 databases, you can capture those
statements in separate pureQueryXML files and then select the database
against which you want to bind the SQL in each pureQueryXML file.
- SQL Outline view for seeing the relationships between the objects
that you work with
- Use this view to see the relationships between your SQL statements,
the DB2 packages that the workbench
suggests or creates based on your specifications, the Java files that contain the SQL statements,
and the database objects that the statements access or refer to.
- Java editor that includes
assistance for writing and validating SQL statements
- If your project contains Java source
files, you can write and edit SQL statements by using the Java editor's content assistance and SQL validation
features.
- Generation of pureQuery code from SQL statements and database
objects
- Optionally modify your non-pureQuery API application to include
code that uses the pureQuery API.
- Managing pureQuery information in a SQL Management repository
- You can store, manage, and retrieve pureQuery information in a
repository. You can manage pureQuery properties and the SQL statements
and related SQL information contained in pureQueryXML files. You can
configure an application enabled with pureQuery client optimization
to store captured SQL information from the application in a repository.