Getting Startedwith pureQuery

Listing 16.1 - Static Generator command line execution
Chapter 16 – pureQuery and JPA 299
The last line in Listing 16.1 shows how to run the Static Generator utility to generate the
SQL statements for the JPASample persistence unit:
wsdb2gen –pu JPASample –url jdbc:db2://localhost:50000/demodb –user
db2admin –pw passw0rd
Upon execution, this command will generate a file consisting of the SQL statements that
reflect the data operations implemented by the persistence unit JPASample.
The generated file will have extension .pdqxml and the name will reflect that of the
persistence unit. In the example described in this section, the filed created has the name
JPASample.pdqxml. The .pdqxml file format is known as the pureQuery capture file
format, already described in Chapter 6. This file contains SQL statements that will later be
converted to DB2 packages.
The Static Generator utility created the bind file in the same location of the
persistence.xml file.
16.4.1 Creating and binding the packages
After all the SQL statements have been generated, the next step is to create and bind the
DB2 packages that will contain these same SQL statements.
This step can be achieved using two different methods:
• using the command line based tool pureQuery Static Binder
• using the Websphere Application Server V7 administration console
Since the pureQuery Static Binder has already been covered on Chapter 7, we will
describe how to generated and bind the packages using the WAS administration console.
Starting with version 7, the WAS admin console provides an option that lets users load and
bind a pureQuery bind file. This option is available on the application’s configuration page,
as shown in Figure 16.2 and it provides an intuitive wizard that guides the user through the
binding process.