Administer Java Persistence API (JPA) applications

Subtopics

• Configure a JDBC provider and data source
  For access to relational databases, applications use the JDBC drivers and data sources.
• Configure the default JTA and non-JTA data source JNDI names
  The Java Transaction API (JTA) and non-JTA data sources to be used for an application can be specified through the <jta-data-source> and <non-jta-data-source> elements of the persistence.xml file within an EJB module.
• Associating persistence providers and data sources
  Java Persistence API (JPA) applications specify the underlying data source used by the persistence provider to access the database.
• WAS persistence providers
  Persistence providers are implementations of the Java Persistence API (JPA) specification and can be deployed in the Java EE compliant application server that supports JPA persistence.
• wsjpaversion command
  Use this command line tool to find out information about the installed version of the Java Persistence API (JPA) 2.0 specification provider, WSJPA/OpenJPA, for WebSphere Application Server.
• eclversion command
  Use this command-line tool to find out information about the installed version of the Java Persistence API (JPA) 2.1 specification provider, Eclipselink, for the product.
• Identifying and modifying the JPA specification level
  Newly created profiles default to the Java Persistence API (JPA) 2.1 specification. We can run AdminTask wsadmin commands to list JPA specifications supported by the product and to change the JPA specification used by a server, server cluster, or servers that are members of a cluster.
• Configure WSJPA FastPath
  The Java Persistence API (JPA) is a very flexible specification that provides guidelines on how implementers are to convert relational data to Java object form. Due to the flexible nature of this API, a large amount of work is completed at runtime by the API provider to determine how to correctly load relational data into object form. This flexibility results in a runtime that, under certain circumstances, must continually run redundant code to ensure that data is loaded properly. By giving up some of this flexibility, the WSJPA FastPath optimization attempts to skip much of this redundant code and generates highly optimized code that interacts directly with the JDBC layer. This optimization translates to improved performance.
• IBM Optim pureQuery Runtime
  IBM Optim™ pureQuery Runtime provides Java Persistence API (JPA) with an alternative way to access a database. PureQuery supports static Structured Query Language (SQL). PureQuery is only supported by OpenJPA and WSJPA persistence providers.
• Configure a JDBC provider and data source
  For access to relational databases, applications use the JDBC drivers and data sources.
• Configure the default JTA and non-JTA data source JNDI names
  The Java Transaction API (JTA) and non-JTA data sources to be used for an application can be specified through the <jta-data-source> and <non-jta-data-source> elements of the persistence.xml file within an EJB module.
• Associating persistence providers and data sources
  Java Persistence API (JPA) applications specify the underlying data source used by the persistence provider to access the database.
• WAS persistence providers
  Persistence providers are implementations of the Java Persistence API (JPA) specification and can be deployed in the Java EE compliant application server that supports JPA persistence.
• wsjpaversion command
  Use this command line tool to find out information about the installed version of the Java Persistence API (JPA) 2.0 specification provider, WSJPA/OpenJPA, for WAS.
• eclversion command
  Use this command-line tool to find out information about the installed version of the Java Persistence API (JPA) 2.1 specification provider, Eclipselink, for the product.
• Identifying and modifying the JPA specification level
  Newly created profiles default to the Java Persistence API (JPA) 2.1 specification. We can run AdminTask wsadmin commands to list JPA specifications supported by the product and to change the JPA specification used by a server, server cluster, or servers that are members of a cluster.
• Configure WSJPA FastPath
  The Java Persistence API (JPA) is a very flexible specification that provides guidelines on how implementers are to convert relational data to Java object form. Due to the flexible nature of this API, a large amount of work is completed at runtime by the API provider to determine how to correctly load relational data into object form. This flexibility results in a runtime that, under certain circumstances, must continually run redundant code to ensure that data is loaded properly. By giving up some of this flexibility, the WSJPA FastPath optimization attempts to skip much of this redundant code and generates highly optimized code that interacts directly with the JDBC layer. This optimization translates to improved performance.
• IBM Optim pureQuery Runtime
  IBM Optim pureQuery Runtime provides Java Persistence API (JPA) with an alternative way to access a database. PureQuery supports static Structured Query Language (SQL). PureQuery is only supported by OpenJPA and WSJPA persistence providers.