We are involved in a project to migrate a J2EE infrastructure from OC4J to Glassfish v2.1. The applications running on OC4J are based on EJB and JSF (sun impl + tomahawk) and have successfully be migrated with little changes. We new stack are using is Apache 2.2, mod_jk and Glassfish v2.1.
So far, so good!
%A %B %e%q, %Y at %I:%M %p
Glad to see GlassFish is working or you. Make sure you keep blogging about your experience, good or bad.
%A %B %e%q, %Y at %I:%M %p
The web based console and command line tool provided to manage glassfish is really cool. This is the first time we’re using it and we have found you can monitor the server, logs, configure jdbc pools (Oracle RDBMS), integrate with LDAP authentication (we successfully set up Microsoft Active Directory integration), set up JVM options all through the web interface or asadmin command.
We are now load testing the applications with JMeter to check performance and stability so that we can complete the switchover.
Thanks to this post, we integrated Apache and Glasfish really quickly:
http://louisbotterill.blogspot.com/2008/11/apache-httpd-2x-glassfish-2x-modjk.html
We already installed glassfish with the setup-cluser.xml option:
https://glassfish.dev.java.net/downloads/v2.1-b60e.html
One of the plans in the roadmap is to add further clustered Glassfish nodes loadbalanced by mod_jk