Integrating JPA and pureQuery, Leveraging DB2 static execution for the Java Persistence API

From the developerWorks archives

Fay Wang, Catalina Wei, David Wisneski, and Asim Singh

Date archived: January 3, 2017 | First published: December 10, 2008

IBM® WebSphere® Application Server V7 delivers an enhancement to its implementation of the Java™ Persistence API (JPA) to enable optimization of data access to IBM DB2® data servers for enhanced security, and the potential to significantly reduce overhead for data access. The optimization is achieved by using a built-in integration between the WebSphere JPA and IBM Data Studio pureQuery Runtime to enable static SQL access -- all without changing application code or running extensive test cases. This article uses a sample JPA application and takes you through the steps of enabling static SQL using the JPA/pureQuery integration. It also includes the optional follow-on step of using pureQuery client optimization to capture additional queries during run time. This content is part of the IBM WebSphere Developer Technical Journal.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.

Zone=WebSphere, Information Management
ArticleTitle=Integrating JPA and pureQuery: Leveraging DB2 static execution for the Java Persistence API