We have the WAS application which is running on the WAS V6.0. We want to migrate it to version 7.
The workspace migration wizard has been run and the eclipse settings files are updated to version 7.
Now I have installed Application Migration Tool (Version 2.1.0) on RSA 7.5.4 and run the software Analyser by selecting the ruleset as WAS version 6.0.2 to V7 Migration.. But in the results window, it is always showing code review for WAS version 6.0.2 to V6.1 only. Any suggestion in this regard will be higly appreciated.
Re: WAS Migration 6.0.1 to V7.02011-06-14T11:51:44ZThis is the accepted answer. This is the accepted answer.Hi,
Can somebody pls give me the suggestion as what is missing or what is the cause of this? This is currently a showstopper.
SystemAdmin 110000D4XK102 Posts
Re: WAS Migration 6.0.1 to V7.02011-06-14T14:56:15ZThis is the accepted answer. This is the accepted answer.Hello, In your case the analysis results are indicating that there are no specific v6.1 to v7.0 migration issues found in the application you are migrating.
The version to version migration tool only displays the issues that need to be migrated. Those issues are organized in following categories:
- Changes from v5.1 to v6.0 (changes introduced in v6.0 of WebSphere)
- Changes from v6.0 to v6.1 (changes introduced in v6.1 of WebSphere)
- Changes from v6.1 to v7.0 (changes introduced in v7.0 of WebSphere)
- Changes from v7.0 to v8.0 (in the toolkit v3.0 beta release only) (changes introduced in v8.0 of WebSphere)
In your case, the migration to WebSphere v7.0 only detected issues in your application that belong to the v6.0 to v6.1 category. These would be the only necessary changes to migrate to v7.0.
Re: WAS Migration 6.0.1 to V7.02011-06-15T06:24:28ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
When I run the Software Analyser for migration from V6.0.2 to V7.0, In the java Code review results window (Version migration V6.0 to V6.1) fixes required for JRE 5.0 differences are being shown. Also in WAS 7 environment, the Java version is 1.6.0. Do we need to run the analyser again to migrate the application from WAS version 6.1 to 7.0?
Also In the Software Analyser Configuration, The following three rulesets are present
Migration from V5.1 to V7.1
Migration from V6.0.2 to V7.0
Migration from 6.1 to V7.0
When I select the ruleset as Migration from V6.0.2 to V7.0, I was expecting the Java code review results containing fixes required for Java version 1.6.0.
SystemAdmin 110000D4XK102 Posts
Re: WAS Migration 6.0.1 to V7.02011-06-15T15:46:19ZThis is the accepted answer. This is the accepted answer.
- guvimala 2700049RH2
If you run the rule set for "WebSphere Application Server Version 6.0 to 7.0 migration", all the issues you need to scan for will be included and you should only need to repeat the process until you get zero results. If you do not see any results for a particular category, it indicates your application does have any issues in that category.
You are right that there are 3 rule sets:
WebSphere Application Server Version 5.1 to 7.0 migration
WebSphere Application Server Version 6.0 to 7.0 migration
WebSphere Application Server Version 6.1 to 7.0 migration
When migrating from V6.0 to V7.0, we run the rules for both JRE 5 and JRE 6. JRE 5 was introduced in Version 6.1 and JRE 6 was introduced in Version 7. The fixes suggested for JRE 5 are still important and necessary for JRE 6. It is quite possible that your code did not have any problems that trigger the JRE 6 rules. Those rules include items like:
- Check exception logic on calls to the EventHandler
- Check for Duration and XMLGregorianCalendar equals() method compatibility
- Check for OverlappingFileLockException for theFileChannel lock() method
- Remove use of double slashes in JMX ObjectName elements
You do not need to run analysis again for V6.1 to V7.0 to pick up JRE 6 changes. If you do run it again you should get zero results if you have taken care of your other issues.
If you think that there is a particular rule that should be detected in your application but is not, check the Eclipse error log to see if there was a problem reported.