JBoss Migration
Recently, at Xebia, Rocky Jaiswal, Pallavi Jain , Megha Jain and myself did the migration of an application, JMSConsole, running on WebLogic 8.1.4 to JBoss 5.1. In this article we have shared some of the findings on the same.
The details of the JMSConsole application and the migration exercise have been captured in the clipping.
About JMSConsole application
Source environment : JDK1.4 , WebLogic's 8.1.4 and Oracle 10g.
Target environment : JDK 1.5 , JBoss 5.1 , Oracle 10g.
The JMSConsole application is a simple application that picks messages from a jms queue, Q_1, and pushes those messages to an Oracle database.
The application displays these messages on a UI and gives the user a choice to either delete the messages from the database or push the message to another jms queue, Q_2. Q_1 is configured to be the error destination for Q_2.
Following are the major changes that we had to do to make the application work on JBoss.
JNDI changes
For JBoss the the following JNDI properties are to be used.
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.provider.url=jnp://myhost:1099
For WebLogic the following JNDI properties are to be used.
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3://myhost:7001
This is a nice article sir,
Excellent
Thank you so much
great help for newbee’s
Hi Rahul. I am facing an issue with on of our app which has been migrated from Weblogic to JBOSS.
This is the issue:
The application has two user-roles:
1. Admin
2. Normal User
Firstly,an admin logs in,he is able to work fine with his privileges.
Secondly,a normal user logs in and he is able to work fine with his respective privileges.
Thirldy,when an admin logs in,his privileges have been set as of a normal-user.The buttons which were generally enabled for him have been disabled.
Rest of the application is working fine.
This problem persists until we restart the servers.And if a normal user logs in,the issue persists.
As of now,as a work-around,we have requested the normal users not to login into the application.
Note:
1.The JDK has been upgraded from 1.4 to 1.6
2.Oracle has been upgraded from 9i to 11G.
We do not know whether the issue is with code or the configuration settings of JBOSS server.
The log files are not showing any errors.
If you can help me,please contact me on my mai:
ainkollu@gmail.com
I could not send a mail to your mail ragrawal@xebia.com