Jump to: navigation, search

Difference between revisions of "EclipseLink/Examples/JPA/GlassFishV3 Web Tutorial"

m (Deploying a secure EAR on GlassFish)
m (References)
 
(16 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
=EclipseLink JPA Deployed on GlassFish 3 using Eclipse 3.5=
 
=EclipseLink JPA Deployed on GlassFish 3 using Eclipse 3.5=
* '''<font color="orange">This tutorial's progress is on hold, it needs to be finished and significantly expanded - vote for EclipseLink bug# ''[http://bugs.eclipse.org/308477 308477]'' if you would like this work to be fast tracked and/or raised in the queue.</font>'''
+
* '''This Tutorial is back on as part of [http://bugs.eclipse.org/333336 333336] and [http://bugs.eclipse.org/322288 322288]'''
 +
*If you are using Glassfish 3 as your EE container then you likely are using Netbeans as your IDE - see the page on using [http://wiki.eclipse.org/EclipseLink/Examples/JPA/IDE/NetBeans#EclipseLink_library Netbeans with EclipseLink tutorial] as well.
 +
<!--* '''<font color="orange">This tutorial's progress is on hold, it needs to be finished and significantly expanded - vote for EclipseLink bug# ''[http://bugs.eclipse.org/308477 308477]'' if you would like this work to be fast tracked and/or raised in the queue.</font>'''-->
 
<!--[[Image:Oracle_buys_sun_20091017.jpg]]-->
 
<!--[[Image:Oracle_buys_sun_20091017.jpg]]-->
 
''[[EclipseLink/Examples/JPA/GlassFishV2_Web_Tutorial|Please refer to the GlassFish V2 page for generic EclipseLink on GlassFish Issues.]]
 
''[[EclipseLink/Examples/JPA/GlassFishV2_Web_Tutorial|Please refer to the GlassFish V2 page for generic EclipseLink on GlassFish Issues.]]
 
+
<font color="red">--old content start--</font>
 
If you want to get a small web application running quickly on the GlassFish V3 application server using the Eclipse IDE, follow the instructions in this tutorial.
 
If you want to get a small web application running quickly on the GlassFish V3 application server using the Eclipse IDE, follow the instructions in this tutorial.
  
Line 117: Line 119:
 
**The following page details four different ways to either obtain the binary jars or download the source and build them yourself with an anon account.
 
**The following page details four different ways to either obtain the binary jars or download the source and build them yourself with an anon account.
 
**http://wiki.eclipse.org/EclipseLink/Source-->
 
**http://wiki.eclipse.org/EclipseLink/Source-->
 +
 +
<font color="red">--old content end--</font>
  
 
==Deploying a secure EAR on GlassFish==
 
==Deploying a secure EAR on GlassFish==
Line 127: Line 131:
 
**http://www.oracle.com/technetwork/middleware/glassfish/overview/index.html
 
**http://www.oracle.com/technetwork/middleware/glassfish/overview/index.html
 
*Use the default derby datasource
 
*Use the default derby datasource
 +
 +
===Start the GlassFish Server===
 +
*Either start the server in Eclipse or from the command line
 +
<pre>
 +
C:\opt\glassfishv301b\glassfish\bin>asadmin start-domain
 +
Waiting for DAS to start ................
 +
Started domain: domain1
 +
Domain location: C:\opt\glassfishv301b\glassfish\domains\domain1
 +
Log file: C:\opt\glassfishv301b\glassfish\domains\domain1\logs\server.log
 +
Admin port for the domain: 4848
 +
Command start-domain executed successfully.
 +
</pre>
 +
<pre>
 +
[#|2011-01-13T12:03:09.065-0430|CONFIG|oracle-glassfish3.0.1|org.eclipse.persistence.session.file:/C:/opt/glassfishv301com/glassfish/domains/domain1/applications/org.eclipse.persistence.example.jpa.server.glassfishv3.EnterpriseEAR
 +
/org.eclipse.persistence.example.jpa.server.glassfishv3.EnterpriseEJB_jar/
 +
_enterprise.connection|_ThreadID=29;_ThreadName=Thread-1;
 +
|Connected: jdbc:derby://localhost:1527/sun-appserv-samples;;create=true
 +
</pre>
 +
<source lang="xml">
 +
<?xml version="1.0" encoding="UTF-8"?>
 +
<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
 +
    <persistence-unit name="enterprise" transaction-type="JTA">
 +
        <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
 +
        <jta-data-source>jdbc/__default</jta-data-source>
 +
        <properties>
 +
            <property name="eclipselink.target-server" value="SunAS9"/>
 +
            <!-- property name="eclipselink.target-database"
 +
                      value="org.eclipse.persistence.platform.database.DerbyPlatform"/-->
 +
            <property name="eclipselink.logging.level" value="FINEST"/>
 +
            <!-- turn off DDL generation after the model is stable -->           
 +
            <property name="eclipselink.ddl-generation" value="drop-and-create-tables"/>
 +
            <property name="eclipselink.ddl-generation.output-mode" value="database"/>
 +
        </properties>
 +
    </persistence-unit>
 +
</persistence>
 +
</source>
 +
 
*Create EAR application
 
*Create EAR application
 
*Deploy or drop EAR on server
 
*Deploy or drop EAR on server
 +
**GlassFish V3.0.1 is running EclipseLink 2.0.1 SVN rev# [https://fisheye2.atlassian.com/changelog/eclipselink/?cs=6600 6600] from Feb 2010
 +
<pre>[#|2011-01-13T12:03:09.049-0430|INFO|oracle-glassfish3.0.1|org.eclipse.persistence.session.file:/C:/opt/glassfishv301com/glassfish/domains/domain1/applications/org.eclipse.persistence.example.jpa.server.glassfishv3.EnterpriseEAR
 +
/org.eclipse.persistence.example.jpa.server.glassfishv3.EnterpriseEJB_jar/_enterprise
 +
|_ThreadID=29;_ThreadName=Thread-1;|EclipseLink, version: Eclipse Persistence Services - 2.0.1.v20100213-r6600|#]
 +
</pre>
 
*Browser results
 
*Browser results
 
[[Image:Glassfishv013_enterprise_app_browser_screencap.JPG]]
 
[[Image:Glassfishv013_enterprise_app_browser_screencap.JPG]]
*Now we will secure GlassFish
+
*Now we will secure GlassFish and upgrade EclipseLink to the latest 2.3 version so we can debug sychronized source in Eclipse.
 +
**Creating GlassFish bundles (5) from the EclipseLink trunk
 +
**Run the following target
 +
<pre>
 +
C:\view_22a\2.2\trunk>ant dev-package-bundles
 +
look in
 +
C:\view_22a\2.2\trunk\plugins
 +
</pre>
 +
*Note:<font color="red">'''The updated bundles are picked up by timestamp - you will need to clear the osgi-cache if the dates are older than the bundles currently on the modules dir.'''</font>
 +
 
 +
===Enabling the Security Manager in GlassFish 3===
 +
*In the following <font color="green>'''$GlassFish$/glassfish/bin'''</font> directory off the server perform these commands to run on the security manager (off by default in WebLogic and GlassFish)
 +
*Turning on the security manager in GlassFish is very simple.  It is WebLogic that has some issues that we need to look at surrounding any custom JTA datasources and their specific grants
 +
*Just an fyi that no Grant elements are required in the EAR if you use the default datasource.
 +
<source lang="xml"><jta-data-source>jdbc/__default</jta-data-source></source>
 +
*We can use the existing code for both and configure the server on the fly by creating and deleting the following two security properties.
 +
<pre>
 +
asadmin start-domain
 +
asadmin --user admin create-jvm-options -Djava.security.manager
 +
asadmin --user admin create-jvm-options -Declipselink.security.usedoprivileged=true
 +
asadmin stop-domain
 +
asadmin start-domain
 +
</pre>
 +
*Look for the following log to verify.
 +
<source lang="java">
 +
[#|2011-01-14T12:18:45.513-0430|INFO|glassfish3.0.1|javax.enterprise.system.core.security.com.sun.enterprise.security|_ThreadID=11;_ThreadName=Thread-1;|SEC1001: Security Manager is ON.|#]
 +
</source>
 +
*If you attach JConsole to your secured GlassFish 3.0.1 or 3.1 server after you exercise the EE application ''(to create a session)'' you will see the following view.
 +
[[Image:Jconsole_mbean_view_security_manager_on_glassfish301.JPG]]
  
 
==References==
 
==References==
[[EclipseLink/Examples/JPA/GlassFishV2_Web_Tutorial|EclipseLink JPA on GlassFish Server V2]]
+
*[[EclipseLink/Examples/JPA/GlassFishV2_Web_Tutorial|EclipseLink JPA on GlassFish Server V2]]
 +
*Failed deployment of Java EE application leaves broken Persistence Unit definition on Glassfish v3 b74  https://bugs.eclipse.org/bugs/show_bug.cgi?id=297312
 +
*JMX MBean Registration for GlassFish 3.1 https://bugs.eclipse.org/bugs/show_bug.cgi?id=316512
 +
*JMX PrivilegedAccess fix for EclipseLink 2.2 http://java.net/jira/browse/GLASSFISH-15337 http://bugs.eclipse.org/333336
 +
*JMX on GlassFish 1.2 http://forums.oracle.com/forums/thread.jspa?messageID=9124630&#9124630
 +
*https://bugs.eclipse.org/bugs/show_bug.cgi?id=296269
 +
*https://bugs.eclipse.org/bugs/show_bug.cgi?id=322287
 +
*https://bugs.eclipse.org/bugs/show_bug.cgi?id=320826
 +
*Build: default and dev-package-bundles target missing missing o.e.p.jpa.osgi jar for OSGI users in plugins dir https://bugs.eclipse.org/bugs/show_bug.cgi?id=297711
 +
*Need to verify that rev 8141 fixes https://bugs.eclipse.org/bugs/show_bug.cgi?id=297312
 +
===GlassFish Server in Use===
 +
*[http://blogs.sun.com/stories/entry/t_mobile_high_availability_and GlassFish and TMobile]
 +
*[http://blogs.sun.com/stories/entry/xeroxgs GlassFish and Xerox]
 +
*[http://blogs.sun.com/stories/entry/psa_peugeot GlassFish and Peugeot]
 +
*[http://blogs.sun.com/stories/entry/telefonica_brazil_tracking_touble_tickets GlassFish and Telefonica]
 +
*[http://blogs.sun.com/stories/entry/verizon_uses_opensso_in_large GlassFish and Verizon]

Latest revision as of 20:03, 2 March 2011

EclipseLink JPA Deployed on GlassFish 3 using Eclipse 3.5

Please refer to the GlassFish V2 page for generic EclipseLink on GlassFish Issues. --old content start-- If you want to get a small web application running quickly on the GlassFish V3 application server using the Eclipse IDE, follow the instructions in this tutorial.

This basic example details how to use Eclipse to run/debug a minimum J2EE 5/6 web application servlet using EclipseLink JPA as the persistence provider. The goal of this example is to detail the minimum steps needed to run EclipseLink inside GlassFish V3 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.

Tutorial Source

And the DDL generation J2SE JPA application used to populate the database schema.

http://dev.eclipse.org/svnroot/rt/org.eclipse.persistence/trunk/examples/org.eclipse.persistence.example.jpa.server.common.ddlgen

Development Environment

Software: Eclipse IDE for Java EE 3.5 Galileo (June 2009 +) , JavaDB (part of GlassFish), SUN Java JDK 1.6.0_xx, GlassFish V3 Prelude

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

Prerequisites

Install Eclipse EE

  • I installed a clean version of Eclipse 3.5 Galileo (June 2009)

Install a Database

  • In this example I am the included JavaDB that is part of GlassFish V3, the table schemas have already been created manually and all entity java classes have been generated using the Eclipse DALI tool.

Install GlassFish

Install Glassfish Tools Bundle for Eclipse

Install Eclipse GlassFish Server Plugin

  • Currently the "Download additional server adapters" link on the "New Server" dialog will not work with Eclipse 3.5 - Use the "Help | Install New Software" menu instead via the https://ajax.dev.java.net/eclipse/site.xml update site to get version 32+ of the plugin that is compatible with Galileo.
    • You may refer to the details of Eclipse Bug # 280365.
  • Currently we get
    • cannot Deploy org.eclipse.persistence.example.jpa.server.glassfishv3.EnterpriseEAR
 Deployment Error for module: org.eclipse.persistence.example.jpa.server.glassfishv3.EnterpriseEAR: Exception while deploying the app : java.lang.IllegalArgumentException: Application [org.eclipse.persistence.example.jpa.server.glassfishv3.EnterpriseEAR] contains no valid components%%%EOL%%%

EclipseLink Library Location

  • The EclipseLink modules ship as 5 separate jars in the standard modules directory (Note EclipseLink SDO and JAXB are precluded by the libraries shipped with GlassFish - the milestone version is from the JPA 2.0 trunk branch.
    • \glassfish\modules
      • org.eclipse.persistence.antlr.jar
      • org.eclipse.persistence.asm.jar
      • org.eclipse.persistence.core.jar
      • org.eclipse.persistence.jpa.jar
      • org.eclipse.persistence.jpa.modelgen.jar
      • org.eclipse.persistence.oracle.jar (optional)

JPA Specification Library Location

  • javax.persistence.jar ships with GlassFish in the standard modules directory.

Updating EclipseLink Bundles Shipped with GlassFish

Progress

  • NetBeans 6.8.1M1 20090822 with an embedded GlassFish b58 is working fine.
  • I am testing on NetBeans from now on and will investigate ant/eclipse deployment later
  • All of deployment, JNDI setup, persistence.xml configuration, jpql query example - in progress ......


--old content end--

Deploying a secure EAR on GlassFish

  • This section 20110112
  • Download Eclipse 3.6 Helios EE edition
  • Update the server plugins by adding the latest Oracle GlassFish Server Tools Plugin - GlassFish 3 OSS and Commercial will arrive with this one.
    • "Download additional server adapters" link on the top right of the define a new server dialog
    • Use Oracle GlassFish Server Tools - 1.6.1 version
  • Download GlassFish 3.0.1 standalone EE server (not the one in NetBeans) so we can create a server in Eclipse
  • Use the default derby datasource

Start the GlassFish Server

  • Either start the server in Eclipse or from the command line
C:\opt\glassfishv301b\glassfish\bin>asadmin start-domain
Waiting for DAS to start ................
Started domain: domain1
Domain location: C:\opt\glassfishv301b\glassfish\domains\domain1
Log file: C:\opt\glassfishv301b\glassfish\domains\domain1\logs\server.log
Admin port for the domain: 4848
Command start-domain executed successfully.
[#|2011-01-13T12:03:09.065-0430|CONFIG|oracle-glassfish3.0.1|org.eclipse.persistence.session.file:/C:/opt/glassfishv301com/glassfish/domains/domain1/applications/org.eclipse.persistence.example.jpa.server.glassfishv3.EnterpriseEAR
/org.eclipse.persistence.example.jpa.server.glassfishv3.EnterpriseEJB_jar/
_enterprise.connection|_ThreadID=29;_ThreadName=Thread-1;
|Connected: jdbc:derby://localhost:1527/sun-appserv-samples;;create=true
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
    <persistence-unit name="enterprise" transaction-type="JTA">
        <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
        <jta-data-source>jdbc/__default</jta-data-source>
        <properties>
            <property name="eclipselink.target-server" value="SunAS9"/>
            <!-- property name="eclipselink.target-database" 
                      value="org.eclipse.persistence.platform.database.DerbyPlatform"/-->
            <property name="eclipselink.logging.level" value="FINEST"/>
            <!-- turn off DDL generation after the model is stable -->            
            <property name="eclipselink.ddl-generation" value="drop-and-create-tables"/>
            <property name="eclipselink.ddl-generation.output-mode" value="database"/>
        </properties>
    </persistence-unit>
</persistence>
  • Create EAR application
  • Deploy or drop EAR on server
    • GlassFish V3.0.1 is running EclipseLink 2.0.1 SVN rev# 6600 from Feb 2010
[#|2011-01-13T12:03:09.049-0430|INFO|oracle-glassfish3.0.1|org.eclipse.persistence.session.file:/C:/opt/glassfishv301com/glassfish/domains/domain1/applications/org.eclipse.persistence.example.jpa.server.glassfishv3.EnterpriseEAR
/org.eclipse.persistence.example.jpa.server.glassfishv3.EnterpriseEJB_jar/_enterprise
|_ThreadID=29;_ThreadName=Thread-1;|EclipseLink, version: Eclipse Persistence Services - 2.0.1.v20100213-r6600|#]
  • Browser results

Glassfishv013 enterprise app browser screencap.JPG

  • Now we will secure GlassFish and upgrade EclipseLink to the latest 2.3 version so we can debug sychronized source in Eclipse.
    • Creating GlassFish bundles (5) from the EclipseLink trunk
    • Run the following target
C:\view_22a\2.2\trunk>ant dev-package-bundles
look in
C:\view_22a\2.2\trunk\plugins
  • Note:The updated bundles are picked up by timestamp - you will need to clear the osgi-cache if the dates are older than the bundles currently on the modules dir.

Enabling the Security Manager in GlassFish 3

  • In the following $GlassFish$/glassfish/bin directory off the server perform these commands to run on the security manager (off by default in WebLogic and GlassFish)
  • Turning on the security manager in GlassFish is very simple. It is WebLogic that has some issues that we need to look at surrounding any custom JTA datasources and their specific grants
  • Just an fyi that no Grant elements are required in the EAR if you use the default datasource.
<jta-data-source>jdbc/__default</jta-data-source>
  • We can use the existing code for both and configure the server on the fly by creating and deleting the following two security properties.
asadmin start-domain
asadmin --user admin create-jvm-options -Djava.security.manager
asadmin --user admin create-jvm-options -Declipselink.security.usedoprivileged=true
asadmin stop-domain
asadmin start-domain
  • Look for the following log to verify.
[#|2011-01-14T12:18:45.513-0430|INFO|glassfish3.0.1|javax.enterprise.system.core.security.com.sun.enterprise.security|_ThreadID=11;_ThreadName=Thread-1;|SEC1001: Security Manager is ON.|#]
  • If you attach JConsole to your secured GlassFish 3.0.1 or 3.1 server after you exercise the EE application (to create a session) you will see the following view.

Jconsole mbean view security manager on glassfish301.JPG

References

GlassFish Server in Use