MyEclipse Logo
 

RAD Project Migration Tutorial

Table of Contents
download the latest MyEclipse version

help and support

Update

MyEclipse Blue Edition now has the new ability of Enhancing RAD 7, RAD 6.x and WSAD 5 projects to work in both MyEclipse Blue and RAD simultaneously -- removing the older requirement of 1-way migrating a project from 1 IDE to another.

You can now enhance your projects with MyEclipse Blue and continue using them in both IDEs without problems at the same time.

 

1. Introduction

This document will outline the process of migrating RAD projects to MyEclipse Blue Edition. It would be good in general for RAD users to become more familiar with MyEclipse before attempting to migrate any existing projects.  The MyEclipse Blue Edition for RAD Users would be a good document to read prior to reading this document. 

MyEclipse Blue also supports developing all types of J2EE applications including Web, EJB, and web services that can also be deployed to WebSphere Portal Server since it is running on top of the WebSphere AppServer.

Additional resources covering the migration of RAD projects to MyEclipse are included in the Resources section of this document.


 

2. System Requirements

This tutorial was created with MyEclipse Blue Edition. However, if you notice portions of this tutorial looking different than the screens you are seeing, please let us know and we will make sure to resolve any inconsistencies.


3. RAD Project Migration Support Overview

The RAD Project Migration wizard introduced in MyEclipse 6.5 Blue edition was only our first step in supporting users migrating from RAD to MyEclipse Blue Edition. That wizard was limited in its scope of projects that it could migrate 100% without further user intervention. Here are some additional notes to keep in mind before running this wizard.

  1. This wizard is not designed to migrate all types of projects in all situtions.  After running this wizard, some further manual modifications to your project may be required.
  2. This wizard will not modify, but copy your existing project.  This decision was made as the most conservative choice for initial versions of migration support.  Subsequent versions of the wizard may take on more agressive migration tasks after we learn more about customer's requirements.  Merging the copied changes back into your existing project, if required, is a simple and documented process, see below.
  3. Online, live documentation supplements whatever functionality is not provided by the wizard itself.
  4. View more supplemental migration support documentation online that will be frequently updated with additional migration notes.
  5. This wizard and related documentation are evolving works in progress.  Your feedback will allow us to improve the migration experience from what we learn from our customers about their everyday practices.

View supplementalRAD Project Migration documentation online that is updated regularly.


4. Using RAD Project Migration Wizard

Using the Project Migration wizard is a very simple process that can be executed if you have any WSAD5.1 or RAD6 projects located in your workspace.  The first section shows the steps for Web or EJB project migration.  The 2nd section shows EAR migration which involves multiple Web or EJB project migration steps. 

Current Project Migration Support Notes

  1. Project migration uses copy and modify approach so your original project will not be modified.
  2. New migrated project is disconnected from any team providers.
  3. Migration of modules of an EAR should not be done individually, instead migration of parent EAR should be done instead. 
  4. Connector, AppClient projects in EAR projects will not be migrated.

4.1 Web Project Migration

  1. Import WSAD 5.1 or RAD6 Web project into your workspace
  2. Select the WSAD 5.1 or RAD6 Web project and select MyEclipse > Migration Project... action.



  3. When migrating a Web project, the only input needed is the new MyEclipse Web project name that will be used for the migrated version of the RAD project.



  4. Select Finish to migrate the project. 

Both Struts and JSF Project migration are currently handled in exactly the same manner as normal Web project migration.

4.2 EJB Project Migration

  1. Import WSAD 5.1 or RAD6 EJB project into your workspace
  2. Select the WSAD 5.1 or RAD6 EJB project and select MyEclipse > Migration Project... action.



  3. When migrating a EJBproject, the only input needed is the new MyEclipse EJBproject name that will be used for the migrated version of the RAD project.



  4. Select Finish to migrate the project.


4.3 EAR Project Migration

  1. Import WSAD 5.1 or RAD6 EAR project into your workspace.  Also make sure that all of the EAR module projects that are included in the EAR are also imported in your workspace.
  2. Select the WSAD 5.1 or RAD6 Web project and select MyEclipse > Migration Project... action.



  3. The next step is to provide a name of the migrated EAR project.



  4. At this point the wizard will provide you with a list of module projects that are a part of the EAR project.  In the list you can select or deselect each module project to indicate whether it should be migrated or not.  By default all module projects are selected and will be migrated.



  5. For each module that was selected in Step 4, you will get a seperate module migration page in the wizard that lets you select what migration options for that Web or EJB module project.  In the figure below we are being prompted for the EJB module migration details.



  6. When all of the module migration pages have been completed you will be able to select "Finish" to migrate all of the projects.


4.4 Upgrading J2EE 1.2 projects to 1.3

If any RAD Web, EJB, or EAR project is migrated and the spec level of the project is J2EE 1.2, you will be prompted during migration on if you would like to upgrade the project to J2EE 1.3 specification.


If you choose to not continue migration the wizard will not create a migrated project.  If you choose to continue when it copies the original project, it will modify the deployment descriptors, e.g. web.xml, ejb-jar.xml, application.xml, in the project to bring it up to the proper spec level.

5. Resources

In this section we want to provide you with additional links to resources that supplement the topics covered in this tutorial. While this is not an exhaustive list, we do make an effort to point to the more popular links that should provide you with diverse, high-quality information.


6. Feedback

We would like to hear from you! If you liked this tutorial, has some suggestions or even some corrections for us please let us know. We track all user feedback about our learning material in our Documentation Forum.  Please be sure to let us know which piece of MyEclipse material you are commenting on so we can quickly pinpoint any issues that arise.