16.10.2015 Views

Getting Startedwith pureQuery

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

300<br />

<strong>Getting</strong> Started with <strong>pureQuery</strong><br />

Figure 16.2 - JPA_EE_SAMPLE application configuration page<br />

Once the packages have been bound to the database, the next step is to make the JPA<br />

application run on top of the <strong>pureQuery</strong> runtime. We will discuss that in the next section.<br />

16.5 Running a JPA application using <strong>pureQuery</strong><br />

One of the advantages of running a JPA application on top of <strong>pureQuery</strong> runtime is the<br />

ability to use the enhanced security control of static SQL in DB2. As we explain in<br />

Appendix C, static SQL allows specifying individual access privileges at the package level.<br />

The first step to make our JPA application run on top of <strong>pureQuery</strong> is to set the correct<br />

access privileges to the packages generated and bound in the previous section. In order to<br />

allow a user to run the packages we created, we need to grant the user execute privilege<br />

on the packages. That can be done by specifying the <strong>pureQuery</strong> StaticBinder option –<br />

grant.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!