IBM Support

WebSphere Application Developer v5.1.2 and Rational Application Developer v6 to v7 Migration problems FAQ

Question & Answer


Question

Is there a list of Frequently Asked Questions (FAQ) regarding the migration of J2EE projects from IBM® WebSphere® Application Developer (WSAD) v5.1.2 and IBM Rational® Application Developer (RAD) v6.x to RAD v7.x?

Answer

  1. Why on some cases, migrated Projects are not recognized properly?

    After migrating Java Enterprise Edition (Java EE) projects from RAD v6 to v7, sometimes you will see the following behaviors:
    • Web Projects are migrated to EJB projects
    • Web Projects are migrated to Java Utility projects
    • Web Projects are not migrated at all
    • EJB Projects are migrated to Java Utility projects
    • EJB Projects are migrated to Web projects
    • EJB Projects are not migrated at all
    • EJB Projects not migrated correctly if they have source folders other than ejbModule
    • Or any Java EE project is not migrated at all.

      Note: The last scenario is very rare and will normally only occur on the very first project in the workspace. The workaround is to simply delete the project from the workspace and reimport it.

      The scenarios above are list of known defects in RAD v7 migration which have been fixed in RAD v7.0.0.6

  2. Why the second time you migrate the same project from CVS server into the same workspace, migration fails?

    The following are the steps to reproduce the problem:
    1. Start RAD workspace
    2. Connect to a CVS server and import a project that needs migration
    3. Wait for migration to finish
    4. Restart workspace
    5. Delete the project that was previously migrated
    6. Import the project again from CVS; migration will fail.

      The scenario above is also a known defect in RAD v7, which is scheduled to be fixed in RAD v7.0.0.7. The workaround is simply to switch to a fresh new workspace and import the project again from CVS server.

  3. Why if the .cvsignore file contains the .j2ee, .websettings, and .project files, the migration via CVS server will fail?

    .cvsignore is used by the CVS server to ignore files and directories specified by this file. If this .cvsignore file contains ignore flags for all the vital workspace meta-data including the .project, .websettings, and .j2ee files, then the migration will fail. These files are what RAD v7 uses to determine the type of project.

    You need to either remove the .cvsignore file from the project, or delete these 3 entries from it.

  4. How to troubleshoot if in some cases EJB projects get migrated into Java projects.

    Review technote 1293173 for more details.

  5. Migrated projects from IBM Rational® ClearCase® showing as plain projects in RAD v7.x?

    Review technote 1285443 for more details.

  6. Why do you see the following error in the Problems view after migrating your code from RAD v6 to v7:

    "IWAE0016E Line 1 in the MANIFEST.MF file in archive {jarfile} exceeds the specification limit of 72 bytes"

    Review technote 1294495 for more details.

  7. Why users may get the errors about duplicate build path entries for projects after they are migrated to RAD v7.0?

    Review technote 1284205 for more details.

  8. Can the MigrationBuilder be disabled once the projects have been successfully migrated to RAD version 7.0? What are the effects of disabling the MigrationBuilder?

    Review technote 1282539 for more details.

  9. How to prevent the JSF Facet from being applied after migration to RAD 7.x ?

    Review technote 1254151 for more details.

  10. After migrating error-free RAD 6.x projects versioned in IBM Rational ClearCase® to RAD v7.x or IBM Rational Software Architect (RSA) v7.0, the Problems view shows errors in the mapping file Map.mapxmi or the database model files of EJB projects (.dbxmi, .tblxmi, .conxmi, .schxmi or other files with name .*xmi beside Map.mapxmi in the database backend folder).

    Review technote 1284177 for more details.

  11. EJB projects containing connection to Oracle® Database might get the following error message after migrated to RAD v7:

    The mapping for backend Default is not valid. The database vendor may not be supported. See the META-INF/Schema/SQLModelMigration.log file for details ProductEjb Unknown 1211985005718 347506


    Review technote 1306466 for more details.

    [{"Product":{"code":"SSRTLW","label":"Rational Application Developer for WebSphere Software"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Installation","Platform":[{"code":"PF033","label":"Windows"}],"Version":"7.0;7.0.0.1;7.0.0.2;7.0.0.3;7.0.0.4;7.0.0.5;7.0.0.6","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSRTLW","label":"Rational Application Developer for WebSphere Software"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Install \/ Migration","Platform":[{"code":"PF033","label":"Windows"}],"Version":"7.0;7.0.0.1;7.0.0.2;7.0.0.3;7.0.0.4;7.0.0.5;7.0.0.6","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSYK2S","label":"Rational Software Architect Designer"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Install \/ Migration","Platform":[{"code":"PF033","label":"Windows"}],"Version":"7.0;7.0.0.1;7.0.0.2;7.0.0.3;7.0.0.4;7.0.0.5;7.0.0.6","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

    Document Information

    Modified date:
    10 September 2020

    UID

    swg21298078

    Page Feedback