Skip to main content
Jump to: navigation, search

EclipseLink/Examples/JPA/WebSphereCE Web Tutorial

< EclipseLink‎ | Examples‎ | JPA
Revision as of 11:56, 18 September 2008 by (Talk | contribs) (EclipseLink JPA Deployed on IBM WebSphere CE 2.1 using Eclipse WTP)

EclipseLink JPA Deployed on IBM WebSphere CE 2.1 using Eclipse WTP

Note: This tutorial' is under construction for the next week as of 20080918.

If you want to get a small web application running quickly on GlassFish - the services provided by the Web Tools Project pluggin in the Eclipse IDE can take care of the deployment details and set the server into debug mode for you.

This basic example details how to use Eclipse to run/debug a minimum J2EE web application servlet using EclipseLink JPA as the persistence provider. The goal of this example is to detail the minimum steps required to run EclipseLink inside the IBM WebSphere Application Server Community Edition server using the Eclipse IDE. At this point no presentation/controller layer such as JSF, Spring or Struts will be used beyond a basic HttpServlet so we can concentrate on the the integration layer JPA setup.

The DALI project was used to generate Entities from a schema with sequences already populated.

Development Environment

Software: Eclipse IDE for Java EE 3.4 Ganymede (June 2008 +) with all 5 packages (DTP 1.6, EMF 2.4, GEF 3.4, WTP 3.0, XSD 2.4), Derby Database 10.4, Java JDK 1.6.0_04 - Note 1.5.0_14 comes with the server, IBM WebSphere CE

This example will run fine with any Database that EclipseLink supports.


Install Eclipse EE

  • I installed a clean version of Eclipse Ganymede (June 2008) with all of WTP 3.0

Install a Database

  • In this example I am using the embedded Derby 10.4, the table schemas have already been created manually and all entity java classes may be generated using the Eclipse DALI tool.
  • There is also an express version of IBM DB2 Express C 9.5 available

Install WebSphere CE

I installed the latest GlassFish V2.1 WebSphere CE build (Sept 2008) and followed the instructions on that page.

Install WebSphere CE Eclipse 3.4 Server Plugin

The WebSphere CE server plugin is not shipped by default with Eclipse - you will need to update your Eclipse IDE to pick up the WebSphere CE Eclipse plugin.

  • I selected to download the zip, and treat is a a local update site in eclipse

Validating the GlassFish/Eclipse configuration

  • In the servers view select New | Server

Wasce define new server.JPG

  • Use the IBM|IBM WASCE v2.1 Server plugin when creating a server
  • Note: WebSphere CE 2.1 only supports Java SE 1.5 (JDK 1.6 runtime support is not available)

Wasce server plugin supports jse5.JPG

  • Start the server to test the plugin

WebSphere Configuration Changes

JNDI Datasource Setup

Global Scoped Datasource Setup

Persistence JAR location

EclipseLink JAR location

JDBC JAR location

Create J2EE application

Create your own J2EE Enterprise Application as below. File | new | project | J2EE | Enterprise Application Project Select server, use 5.0 Ear version

Create a new Web and an optional EJB project

Select generate deployment descriptor if you want to change the context-root

  • Path changes
	<classpathentry combineaccessrules="false" kind="src" path="/org.eclipse.persistence.core"/>
	<classpathentry combineaccessrules="false" kind="src" path="/org.eclipse.persistence.jpa"/>
	<classpathentry combineaccessrules="false" kind="src" path="/eclipselink.jar"/>
  • After EAR project creation - reference the org.eclipse.peristence.core and jpa projects or include a reference to eclipselink.jar in your EJB/WAR projects.
  • If you don't reference the eclipselink.* projects then include a classpath reference to persistence.jar and an Oracle (or other Database) JDBC driver jar for your DB.


The WebSphere CE server is defined as generic "WebSphere"

  • JTA : Put persistence.xml beside your JPA entities in yourProjectEJB/ejbModule/META-INF
<persistence version="1.0" xmlns="" xmlns:xsi="" xsi:schemaLocation="">
  <persistence-unit name="unified" transaction-type="JTA">
      <property name="" value="WebSphere"/>
      <property name="eclipselink.logging.level" value="FINEST"/>
      <property name="eclipselink.session-name" value="eclipselinkwls"/>
  • RESOURCE_LOCAL : non-JTA : Put persistence.xml beside your JPA entities in yourProjectEJB/ejbModule/META-INF
  • This one is used by a local SE Java app to create and pre-populated the derby database
  <persistence-unit name="stat.create.tables" transaction-type="RESOURCE_LOCAL">
      <property name="eclipselink.jdbc.platform" value="oracle.toplink.platform.database.DerbyPlatform"/>
      <property name="eclipselink.jdbc.driver" value="org.apache.derby.jdbc.EmbeddedDriver"/>
      <property name="" value="Derby"/>            
      <property name="eclipselink.jdbc.url" value="jdbc:derby:C:/opt/derby104/unified;create=true"/>
      <property name="eclipselink.jdbc.user" value="APP"/>
      <property name="eclipselink.jdbc.password" value="APP"/>
      <property name="eclipselink.logging.level" value="FINEST"/>            
      <property name="eclipselink.ddl-generation" value="drop-and-create-tables"/>
      <property name="eclipselink.ddl-generation.output-mode" value="database"/>

Start Server

  • Steps: Select the EAR and [Run on Server].
  • The first "Run on Server" may not start the server, in this case you "Start Server" and then "Run on Server".

Publish EAR

Perform CRUD operations: JPQL insert and query

Browser Output

All of persistence.xml configuration, jpql query example - in progress ......


Originated on build 20080916 - Michael O'Brien

Back to the top