Migrating from GlassFish 2.x to 3.1.x

With clustering now available in GlassFish since version 3.1 (our Spring 2011 release), a good number of folks have been looking at migrating their existing GlassFish 2.x-based clustered environments to a more recent version to take advantage of Java EE 6, our modular design, improved SSH-based provisioning and enhanced HA performance.

ALT_DESCR

The GlassFish documentation set is quite extensive and has a dedicated Upgrade Guide. It obviously lists a number of small changes such as file layout on disk (mostly due to modularity), some option changes (grizzly, shoal), the removal of node agents (using SSH instead), new JPA default provider name, etc...

There is even a migration tool (glassfish/bin/asupgrade) to upgrade existing domains. But really the only thing you need to know is that each module in GlassFish 3 and beyond is responsible for doing its part of the upgrade job which means that the migration is as simple as copying a 2.x domain directory to the domains/ directory and starting the server with asadmin start-domain --upgrade.

Binary-compatible products eligible for such upgrades include Sun Java System Application Server 9.1 Update 2 as well as version 2.1 and 2.1.1 of Sun GlassFish Enterprise Server.

Comments:

Upgrading from 2.1.1 to 3.x is very hard for many people who implemented JSF using Icefaces and Richfaces.

Icefaces 1.x and Richfaces 3.x etc did their own AJAX that does not work with JSF2.
This makes it almost impossible to migrate.

I am guessing the best way is to include:
<property name="useBundledJsf" value="true"/>

in glassfishweb.xml ?

Posted by Richard on November 22, 2011 at 08:00 PM PST #

Jsf 1.2 is keeping me blocked on glassfish 2.1.1. The trick with useBundledJsf doesn't work for EAR applitacions bundled with more then 1 WAR and in this way are most of our products. So in theory it's a nice feature but as Richard wrote all JSF 1.2 libraries with some kind of AJAX won't work on Glassfish 3

Posted by Luka on November 23, 2011 at 09:20 AM PST #

Post a Comment:
Comments are closed for this entry.