When you combine pureQuery Runtime
with a WebSphere® environment,
you specify pureQuery Runtime properties at the data source level
and store pureQuery Runtime properties in a repository. You create
a repository in the transaction database and store the pureQuery Runtime
properties, pureQueryXML file, and captured SQL data in the repository.
The
following illustration shows an overview of the environment you will
create:
Figure 1. WebSphere configuration
for the deployment scenario
For this scenario, you can assume that three client applications
run the test application testApp.ear.
When you use pureQuery
client optimization for a WebSphere application,
you can configure pureQuery Runtime to retrieve pureQuery Runtime
properties and pureQueryXML data from a file system or a repository
in a database. You can also store captured SQL data in a file system
or repository. When the pureQuery information is stored in a location
that is separate from the pureQuery-enabled application, a database
administrator can access the pureQuery information without interrupting
the application.
You can modify the configuration when deploying
pureQuery client optimization for other application configurations.
For example, instead of setting pureQuery Runtime properties at the
data-source level, you can set the properties at the application level
when more than one application runs under the WebSphere Application Server for the same
data source. You can also change the location and configuration of
the repository where pureQuery Runtime stores the pureQuery data.
Before you begin
Ensure that the following requirements are met:
- WebSphere Application
Server is installed and running.
- IBM® Data Server Driver for
JDBC and SQLJ is available as db2jcc.jar with the license JAR file,
and a WebSphere JDBC provider
is created for it.
- The JAR files for pureQuery Runtime pdq.jar and pdqmgmt.jar are
available in the local file system and are added to the CLASSPATH
for the WebSphere DB2® Universal Driver JDBC provider.
In this scenario, you added the JAR file to the CLASSPATH when you
completed the task, Scenario: Enabling pureQuery Runtime with WebSphere Application Server
- The JNDI (Java™ Naming and
Directory Interface) data source named jdbc/nobleDS is available to
the WebSphere DB2 provider that connects to the
transaction database.
- The WebSphere Web
application named TestStaticProfileEAR is running and uses the DB2 database as a data source.
- The application in this scenario is in a test environment and
uses the schema of TEST.
The JDBC packages are bound to collection
NULLID. The CurrentPackagePath and CurrentPackageSet properties are
not set on the data source. The properties are not required for the
dynamic execution.
Note: You cannot use the SET CURRENT PACKAGESET
statement on the database. If you use the statement, JDBC dynamic
packages are also affected.
- The application has one WAR module called TestStaticProfile.war.
About this task
You specify pureQuery Runtime properties at the data source
level and store pureQuery Runtime properties in a repository. You
create a repository in the transaction database and store the pureQuery
Runtime properties, pureQueryXML file, and captured SQL data in the
repository.
The following tasks describe how to combine WebSphere, pureQuery client
optimization, and a repository.