After we did the migration of a sample application, jmsconsole to JBoss, I was thinking about the strategy for such migrations. Some of my thoughts on how to attack the migration of applications.
Deploy Test and Solve
This kind of approach can be used in simple, well coded, or in almost migrated applications (J2EE complaint). It consists of deploying the application, testing it , finding errors, going back to the application, fixing the problems, and deploying the application again. It is can be a good way to start for some one doing the migration for the first time.
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.
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.
