Porting Applications from WebSphere to WebLogic?
JFP queries: "I work for a division of a manufacturing company. We're currently running IBM WebSphere 3.5. We are considering a switch to BEA WebLogic 6./7. Has anyone had luck with IBM's upgrade path? Has anyone else ported a WebSphere 3.5 application to WebLogic? If so, how much of code did you have to rewrite? Are there any 'gotcha!'s that you ran into that you would care to pass along?"
THey have a bunch of discussions about the various App Server platforms and porting between them.
My question is wrt the form processing: How much of your code is written using IBMs custom libraries. This is the point that is going to burn you. And BEA has there own, different solution to the same problem. You may want to look into Struts or Velocity instead, to avoid being locked in to the Vendor.
Why are you switching away from IBM?
Open Source Identity Management: FreeIPA.org
Has anyone else ported a WebSphere 3.5 application to WebLogic?
:)
I haven't done that, but I did the opposite: migrating from welogic to websphere (and also jboss/tomcat)
Besides some minor problems (easily solvable) on the jsp tags, the main difference between the app servers are the features that are not defined in the J2EE specification yet, and so are implemented in different ways by each app server. In particular:
- authentication mechanism (this is a PITA if you are implementing your own authentication, like we do
- custom services (jboss supports MBeans, which might be the standard in the future, but websphere and weblogic have their own way to do that)
- how to start/stop/restart the app server
- how/where to define JNDI objects (like user transacation and data sources)
Overall, I think moving from websphere to weblogic would be easier than the opposite way (websphere is a powerfull tool, but in my opinion it is pretty hard to configure/mantain).
Felipe