-
1. Re: porting to jboss as 7 from weblogic
jaikiran Feb 2, 2012 6:42 AM (in response to rahul_p)Rahul P wrote:
what changes are required while porting to jboss as 7 from weblogic ?
Depends on your application. What kind of an application are you deploying? What components does it contain? Did it have WebLogic specific resources/descriptors/functionalities?
-
2. Re: porting to jboss as 7 from weblogic
rahul_p Feb 2, 2012 6:54 AM (in response to jaikiran)yes it is weblogic dependent. But in general which are the different files that need to be changed. eg weblogic.xml in WEB-INF folder
-
3. Re: porting to jboss as 7 from weblogic
rodakr Feb 2, 2012 8:15 AM (in response to rahul_p)1 of 1 people found this helpfulIt realy depends what and how you want to do it...
Make small Proof of concept Project, where you try to migrate 1-2 Applications and where you have the source code...
Every thing you figured out... write in document, so you get your migration guide :-)
I can give you just few hints:
https://community.jboss.org/wiki/PortingFromWeblogic ( it's not up to date but you see at least what you have to do )
https://docs.jboss.org/author/display/AS7/Developer+Guide
https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+client+using+JNDI
- Weblogic Custome Security Modules -> picketbox custom jaas login modules
- Classloading ( see Developer Guide )
- EJB Remoting ( you can't do this via descriptors in jboss any more with AS 7 .. sees static host to host )
- remote JMS Client ...
If you have old stuff... before JEE 6.... you might need to migrate it ...AS 7.1 is pretty strict to JEE 6...
-
4. Re: porting to jboss as 7 from weblogic
prasad.deshpande Feb 2, 2012 9:33 AM (in response to rahul_p)1 of 1 people found this helpful1. If your application is EE5 std, then to port from weblogic to AS 7.1, you'll need to make JNDI naming of EJB's standardise..
2. If you are injecting JMS destinations/Datasources, that you'll need to consider.
3. All your standalone client might need some change if you use "t3://<host>:<port>" url format to communicate using wlclient/wlthint3client or wlfullclient jars.
4. Classloading is different in weblogic & jboss7.1
I'm having an application that runs on different app servers like JBoss 7.1, Weblogic 12c, Websphere 8 etc.. so my advice is if it's EE5 or EE6 compliant, then it will be easier to port (jboss 7.1 really expects JNDI naming as per EE6 std even thought rest application is EE5 std)