Task overview: IBM Optim pureQuery Runtime

IBM Optim pureQuery Runtime provides Java Persistence API (JPA) with an alternative way to access a database. IBM Optim pureQuery Runtime supports static Structured Query Language (SQL).

About this task

When doing the bind process and when you define your JDBC provider, the following four Java archive (JAR) files must be in the class path:
  • db2jcc_license_cisuz.jar
  • db2jcc_license_cu.jar
  • pdq.jar
  • pdqmgmt.jar
Attention: Read more about the DB2® JAR level compliance for IBM Optim pureQuery Runtime at the IBM® Support Web site: System requirements for IBM Optim pureQuery Runtime for Linux®, UNIX®, and Windows®.

WebSphere® Application Server support for IBM Optim pureQuery Runtime

Restriction:
  • OpenJPA large result processing uses JDBC APIs for scrollable cursors.
Important:
  • JPA sets the IBM Optim pureQuery Runtime property, pdq.executionMode, to the value STATIC.
  • In addition to the JDBC driver JAR file, the JDBC provider configuration must include the JAR file for the IBM Optim pureQuery Runtime environment.
  • Input parameter values in JPA queries (with both EJB SQL queries and native SQL queries) cannot be NULL values except in the case of update statements SET expression values. To search for NULL values in a WHERE clause of SELECT, UPDATE or DELETE, then enter the is null predicate instead.

Procedure




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Jun 11, 2013 8:40:09 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v701sca&product=was-nd-mp&topic=tejb_jpapdq
File name: tejb_jpapdq.html