Getting Startedwith pureQuery

Chapter 16 – pureQuery and JPA 297
statements, SQL statements are also generated to reflect the JPA named queries that exist
in the application. SQL statements that are dynamically generated by the application
cannot be captured by this utility. For more information on how to capture and optimize
dynamic queries, refer to Chapter 6 - The Client Optimizer: pureQuery for Existing JDBC
Applications.
In this chapter, we will use the sample application provided in the IBM developerWorks
article “Integrating JPA and pureQuery: Leveraging DB2 static execution for the Java
Persistence API”. In the Resources section of this book you can find a download link for the
JPA_EE_SAMPLE.ear application file.
The provided sample application contains a persistence unit, of name JPASample and
implements functionality that lets the user create, update and delete customer entities, as
well as retrieve information regarding orders.
16.4 Generating SQL statements
Before we describe the parameters of the Static Generator utility, please note that for the
utility to function properly, the following items must be part of the DataProvider classpath
in your WAS environment:
• pureQuery runtime .jar files
• DB2 driver .jar files
• the entity class .jar file or folder where it is located
• the location of the persistence.xml file
After you have correctly set up the system classpath, the Static Generator utility can be
invoked by executing the command wsdb2gen.bat, as shown in Listing 16.1.