Getting Startedwith pureQuery

302
Getting Started with pureQuery
16.5.1 Running the application in static mode
Since we created and bound the packages using the WAS administration console, our
application has been configured to use pureQuery instead of JDBC as the data access
mechanism.
We can run the application the same way we would do before converting the data access
to pureQuery, either from the WAS administration console or by simply typing the
application URL in a browser.
The URL for our sample application is http://localhost:9080/JPA_W_EJB_WEB/. Enter
this address in your browser and the JPA sample application will launch, as seen in Figure
16.4.
Figure 16.4 - JPA application running in static SQL mode
16.6 Summary
This chapter discussed the integration of JPA and the pureQuery runtime, which allows for
JPA applications that run on WAS V7 to take advantage of static SQL execution in DB2.
We described the process of using the Static Generator utility to generate SQL statements
in bind files that were later used by the pureQuery Static Binder in order to create and bind
the DB2 packages into the database. We also described the process of authorizing users
to run the application in static SQL mode.
Using the Static Generator is a quick way to get started with pureQuery execution for JPA
applications. If you have an application that generates dynamic SQL statements, then you
can leverage the purequery Client Optimizer to capture those statements and improve the
performance, security and maintainability of your application.