Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
EclipseLink/UserGuide/JPA/Advanced JPA Development/Platform Specific Configurations
For current information, please see "Database Support" in the EclipseLink Concepts Guide: http://www.eclipse.org/eclipselink/documentation/latest/concepts/app_tl_ext001.htm
EclipseLink JPA
EclipseLink | |
Website | |
Download | |
Community | |
Mailing List • Forums • IRC • mattermost | |
Issues | |
Open • Help Wanted • Bug Day | |
Contribute | |
Browse Source |
Database and Application Server Support
EclipseLink supports a number of database platforms and application servers, as described below.
Database Support
EclipseLink supports any relational database that is compliant with SQL and has a compliant JDBC driver. EclipseLink has extended support for several database platforms. The extended support mainly consists of providing native sequencing support, schema creation, and certain database functions.
The following databases are supported. Click the names below to see the Javadoc that describes the support for that platform. The classes are in the org.eclipse.persistence.platform.database package.
Database | JavaDoc | Features | |
Apache Derby | DerbyPlatform | Provides Derby specific behavior. | |
Attunity | AttunityPlatform | Platform class that works with Attunity's Connect JDBC driver. | |
dBASE | DBasePlatform | Provides dBASE specific behavior, including:
|
|
Firebird | FirebirdPlatform | Provides Firebird specific behavior. | |
H2 | H2Platform | Provides H2 specific behavior. | |
HyperSQL DataBase (HSQL) | HSQLPlatform | Provides HSQL specific behavior. Supports HSQL functionality as of 1.8.1. Features include:
|
|
IBM Cloudscape | CloudscapePlatform | Provides CloudScape DBMS specific behavior. | |
IBM DB2 Mainframe | DB2MainframePlatform | Provides DB2 Mainframe specific behavior. This provides for some additional compatibility in certain DB2 versions on OS390. Features include:
|
|
IBM DB2 | DB2Platform | Provides DB2 specific behavior, including:
|
|
IBM Informix | InformixPlatform | Provides Informix specific behavior, including:
|
|
Microsoft Access | AccessPlatformPlatform | Provides Microsoft Access specific behavior. | . |
Microsoft SQLServer | SQLServerPlatform | Provides Microsoft SQL Server specific behavior, including:
|
|
MySQL | MySQLPlatform | Provides MySQL specific behavior, including:
|
|
Oracle | OraclePlatform | Provides Oracle Database specific behavior, including:
|
|
Oracle JavaDB | JavaDBPlatform | Allows to use JavaDBPlatform as a synonym for DerbyPlatform | |
Oracle TimesTen | TimesTenPlatform | Provides Oracle TimesTen database specific behavior. | |
Oracle TimesTen7 | TimesTen7Platform | Provides Oracle TimesTen 7 database specific behavior. | |
PointBase | PointBasePlatform | Provides PointBase database specific behavior. | |
PostgreSQL | PostgreSQLPlatform |
See also PostgreSQL |
|
SAP MaxDB | MaxDBPlatform | See MaxDBPlatform. | . |
SAP SyBase SQLAnywhere | SQLAnywherePlatform | Provides SQL Anywhere specific behaviour. | |
Sybase | SybasePlatform |
|
|
Fujitsu Symfoware | SymfowarePlatform |
See also Fujitsu Symfoware Support |
It also possible to extend EclipseLink to add extended support for additional platforms. There are also several user contributed platforms in the EclipseLink incubator project. See Platform Incubator.
Application Server Support
EclipseLink can be used with any Java EE application server that meets the software requirements through the EclipseLink API.
EclipseLink provides integration support for the following servers. See the Javadoc for more information. These classes are concrete subclasses of org.eclipse.persistence.platform.server.ServerPlatformBase responsible for representing server-specific behavior. These classes provide the behavior for the following:
- Which external transaction controller to use
- Whether or not to enable JTA (external transaction control)
- How to register/unregister for runtime services (JMX/MBean)
- Whether or not to enable runtime services
- How to launch container Threads
Server Name | Javadoc | |
IBM WebSphere Application Server |
org.eclipse.persistence.platform.server.was.WebSphere_6_1_Platform org.eclipse.persistence.platform.server.was.WebSphere_7_Platform org.eclipse.persistence.platform.server.was.WebSpherePlatform |
|
JBoss Application Server | org.eclipse.persistence.platform.server.jboss.JBossPlatform | |
Oracle Containers for J2EE (OC4J) | org.eclipse.persistence.platform.server.oc4j.Oc4jPlatform | |
Oracle Sun Application Server | org.eclipse.persistence.platform.server.sunas | . |
Oracle WebLogic Server |
org.eclipse.persistence.platform.server.wls.WebLogic_10_Platform org.eclipse.persistence.platform.server.wls.WebLogic_9_Platform org.eclipse.persistence.platform.server.wls.WebLogicPlatform |
|
SAP NetWeaver Application Server | org.eclipse.persistence.platform.server.sap.SAPNetWeaver_7_1_Platform |