watch this  

the official mrchucho blog

Migrating from Weblogic to JBoss

Posted 2005 Mar 10

I’ve done this countless times and saved my company tens-of-thousands of dollars in licensing and (worthless) support costs.

I started doing this when it became clear that WebLogic 6.1 did not work as advertised and I’ve never looked back. The only argument I ever hear in favor of BEA is that they provide support (again, at a cost in the tens-of-thousands of dollars). To which I respond: one, I’ve used BEA’s support (including their on-site Professional Services) and found it wholly lacking and, two, JBoss provides support services in addition to offering a better product!

Update: Coincidentally, my first day taking over a new project: the first production release had to be called off because app deployment is bringing the server down—though it worked perfectly and is configured identically in development. Guess which app server is being used… WebLogic.

It’d be funny if it weren’t so sad.

Responses to "Migrating from Weblogic to JBoss"

GlennWeb Blog

2005 Mar 11 at 22:46

Java migrations…

Ralph Churchill has a good observation about Java App Server migrations, notably Migrating from Weblogic to JBoss.

”...and saved my company tens-of-thousands of dollars in licensing and (worthless) support costs.”

Oh the lure of big name, high-...


2006 Jun 26 at 12:20



2007 Jan 05 at 13:37

Hi, Our application uses Weblogic 6.1 and panning for upgradation, please provide some salient guide lines for going to Jboss from Weblogic 6.1


2007 Jan 08 at 15:25

In general, my guidelines would be the following:

  1. Remove all dependencies on weblogic-specific classes in Java code (i.e. all of the import weblogic.*). I have yet to find anything that can’t be replaced with standard, Sun-provided Java/J2EE classes. Or, at least, something “portable” like Jakarta Commons.
  2. Re-target your application’s deployment descriptors, xml files, etc. for a standard Java/J2EE web application. One thing that is especially frustrating about many application servers is that they try to lure you into vendor-specific niceties… don’t fall for it!
  3. Lastly, fill in the gaps with JBoss configuration files (e.g. the datasource deployments, etc.)
Comments are now closed.
atom rss