Set Persistence Provider support in the appserver

Persistence providers are implementations of the Java Persistence API (JPA) spec and can be deployed in the Java EE compliant appserver that supports JPA persistence.

The EJB 3.0 specifications require that an appserver container that supports the EJB 3.0 programming model must provide a JPA implementation. This is also referred to as a persistence provider. There are two built-in JPA persistence providers: the JPA persistence provider for the appserver and the OpenJPA persistence provider. If an explicit provider element is not specified in the persistence unit definitions, the appserver will use the default persistence provider, which is the JPA persistence provider for the appserver.

The application server provides both the default persistence provider and the Apache OpenJPA persistence provider to support the open source implementation of JPA and allow for easy migration of existing OpenJPA applications to the application server's solution for JPA.

 

• Configuring a default persistence provider

  Use the default persistence provider, or specify a persistence provider for the application. With the appserver's JPA persistence provider, we can take advantage of the stability and application extensions that are provided with the application server's implementation of JPA. We can decide which persistence implementation best fits the needs. If an application relies on a specific persistence provider for certain functions and settings, you should specify the provider in the persistence unit definition to avoid any incompatibilities.

• Use third-party persistence providers

  Use third-party persistence providers in the appserver environment.

Set the Java Persistence API (JPA) default persistence provider
Use third-party persistence providers
Task overview: Data Studio pureQuery

 

Related concepts

Java Persistence API (JPA) Architecture

 

Related tasks

Task overview: Storing and retrieving persistent data with the Java Persistence API (JPA)