- This topic has 7 replies, 3 voices, and was last updated 10 years, 3 months ago by support-piotr.
-
AuthorPosts
-
joe.stanisicMemberWe currently use MyEclipse Blue 10.7.1 and have several applications that are JEE5 and currently run within a Websphere 7.0 server. We are planning to migrate the applications to Websphere 8.5. After migrating the application to Websphere 8.5 we were planning to migrate the application from JEE5 to JEE6. Would you be able to provide some documentation or instructions for performing this type of migration? I may have missed it, but I searched your support forum but haven’t seen any documentation on this topic.
support-swapnaModeratorJoe,
Our documentation covers the process of migrating RAD projects for use in MyEclipse Blue Edition.We do not have any documentation or instructions about project migration between different versions of Websphere.
The migration to the WAS 8 server can be handled by importing the project into a workspace which does not have WAS 7 configured. Once imported, you can go ahead and configure WAS 8.The JEE libraries for the project will be picked up from WAS.
Let us know if you see any issues during the migration.
joe.stanisicMemberYes. I understand that part.
But once I do that I believe I’ll still have a JEE5 application running within Websphere 8.5. Is that correct? If so, then how do I go about upgrading the application to JEE6 so that I could later use JEE6-specific features?
support-swapnaModeratorJoe,
When you import the project to a workspace which has WAS 8.5 configured, the import wizard allows you to select WAS 8.5 as the target runtime. Once done, the project will automatically update to WAS 8.5 JDK which by default supports JDK 1.6.
Let us know if you have further questions.
support-swapnaModeratorJoe,
Once the project is imported by selecting the WAS 8.5 as target runtime, the EAR facet in the EAR project will be updated to 6.0 , the EJB facet in the EJB project will be updated to 3.1 automatically. Right click on the project > properties > MyEclipse > Project Facets to check for the same.
You should manually change the Dynamic Web Module facet for the Web project from 2.5 to 3.0. The migration wizard must automatically update the Web module facet to 3.0, but it looks like a bug here. I have filed a PR for the dev team to look into it.
Hope this helps.
Let us know if you have further questions.
joe.stanisicMemberI tried creating a new workspace and importing a preference file that we have been using for base WAS 8.5 setup. I made sure that before the import only the WAS 8.5 JDK was installed. I also created an empty WAS 8.5 server. I then performed an import–>Existing Projects Into Workspace and selected the root location of the workspace I have been using for JEE5 and WAS7. During the import process, I was never prompted to use the WAS 8.5 runtime. Each time I tried, the import ended and all the projects were still pointing to JEE5.
So I must be misinterpreting something you stated.
When you say “a workspace that has WAS 8.5 configured” what exactly do you mean by that?
When you talk about importing, I assume you mean selecting File–>Import–>Existing Projects Into Workspace and then selecting either the base workspace directory or an archive file. I have tried both ways and have not seen any difference in behavior. Is there some other import wizard I should be using?
support-swapnaModeratorJoe,
Apologies for not being clear. There are some known migration issues in MyEclipse 10.7.1. Our latest release MyEclipse 2015 C1 includes several fixes and enhancements in terms of project migration and Websphere support.
Here are the steps to follow for migration :
1. Export the project as .ear using File > Export > MyEclipse JEE > EAR file.
2. Download MyEclipse 2015 C1 from here and install it.Apply the Blue license to work with Blue specific features.
3. Switch to a new workspace. File > New > Other > Server. Select Websphere Application Server 8.5 and proceed to configure the WAS 8.5 server.
4. Once done import the project using File > Import > MyEclipse JEE > EAR file wizard. Change the target runtime to WAS 8.5 as shown in the below screenshot :
5. Follow the wizard and once done ,recheck the project facet for EAR,EJB and manually change the Dynamic Web Module facet for web project to 3.0 as mentioned in my previous response.
Let us know how it works for you.
support-piotrParticipantJoe,
Apologies for the delay in addressing your question. We haven’t received any confirmation from you regarding whether the previously proposed solution worked for you or not.
Anyways, the first step in the migration process should be to move projects to MyEclipse 2014 and make sure they work with WebSphere 7.0 in MyEclipse 2014. You can either open MyEclipse 10.7.1 workspace in MyEclipse 2014 or import your projects to a fresh MyEclipse 2014 workspace. During that step you should assign WebSphere 7.0 as target runtime for the projects. Next you need to ensure that projects compile and work OK with WebSphere 7.0.
Once your projects are migrated to MyEclipse 2014 you can upgrade them to JEE6. There is no automated process in MyEclipse to do that. JEE 6 is backward compatible with JEE 5, so you don’t have to do any java code changes, unless you like. Main part of the upgrade process is to change JEE version in Deployment Descriptors ( web.xml, ejb-jar.xml, application.xml, etc.). You need to modify only attributes of the root element. Please create EE6 projects of particular type with deployment descriptors created to see how root element should look like (check “version” attribute and XML namespace attributes).
Once you correct deployment descriptor you should change facet version, so that MyEclipse recognizes JEE version correctly. Open project properties and navigate to MyEclipse/Project Facets. Select WebSphere 8.0 as target runtime (on target runtimes tab) and deselect WebSphere 7.0. Change version of appropriate facet (WEB, EJB or EAR) to JEE 6 (3.0, 3.1, 6.0 respectively). Press ok.
All of your projects should now be recognized as JEE 6 and they should have WebSphere 8.0 Runtime Containers and JDKs on the classpath.
Once again, sorry for delayed instructions and please let us know what is the status of your migration. I’ll be glad to help you if you have any other questions or issues!
-
AuthorPosts