By satishkumar on Mar 04, 2008
You have probably already heard of all the benefits of moving to GlassFish V2 - the fastest, easy-to-administer, enterprise class, open-source Application Server with clustering support. Here is more reason to cheer - The Migration Tool for Glassfish, like its parent project, is now an open-source project under the Java.net umbrella. The project's new home is https://migrate2glassfish.dev.java.net. A beta version of the tool that supports GlassFish V2 is available for download from – https://migrate2glassfish.dev.java.net/downloads/downl oads.html. The latest release of the tool is a lot slimmer @ just around 6 MB. Future releases of the tool shall be available from this new Java.net site. Earlier versions of the tool that supported GlassFish V1 and Sun Java System Application Server 8.x would continue to be accessible from http://java.sun.com/j2ee/tools/migration.
So what does this mean for you? quicker access to bug fixes and newer releases of the tool, transparent issue management, direct access to developer's through the dev email alias and through forums are just some of the benefits. The biggest benefit, in my opinion, is that this is the best way to develop software – the open source way!!
If you are not already aware, the Migration Tool for GlassFish can help you move your existing Java EE deployment from competing App servers over to GlassFish in three easy steps.
Download the Migration Tool binary from here and unzip the binary to a directory location of your choice.
Setup the following environment variables and launch the tool through the asmigrate script with the '-u' argument.
ASMT_HOME= The directory location where the migration tool binaries are installed
J2EE_HOME= The location of the GlassFish V2 application server.
JAVA_HOME= Java 1.5 install location
Specify the source archive or source code location, the source application server and target directory as illustrated in the image below and click on the 'Migrate' button.
The tool migrates the archive/source code and generates a comprehensive report like the one in the image below:
You could also choose to run the tool in the command line mode. More details are available in the online documentation.
But, be warned – migration may not always be so simple. The quantum of work involved would be directly proportional to the extent of usage of vendor provided proprietary APIs. This should be reason enough to avoid using them in the future.
The migrate2glassfish site also has a host of documentation that can help in your migration efforts. We plan to add more as we go along.
We would love to hear from you. Please mail your queries, suggestions and feedback regrading the tool to – firstname.lastname@example.org. We would also encourage you to share your migration experiences. If you have an existing blog on this subject do point us to it. And finally, in case you want to get involved in this project and contribute do write in to us.
If you are currently using GlassFish V2, do spend a few minutes to register your product to get access to adhoc developer patches and aggregated content like bug fixes, latest news and promotions. Once your application goes live, you might want to seriously consider buying a GlassFish subscription to get access to quality technical support besides a host of other benefits.