Migrating WebSphere Portal V4.2 portlets to V5.x

Rational® Application Developer V6.0 does not support developing WebSphere® Portal V4.2 portlets. You need to migrate WebSphere Portal V4.2 portlet projects to V5.x.

Most portlets written for WebSphere Portal V4.2 will run unchanged in WebSphere Portal V5.x. Some of the Portlet 4.2.x APIs are now marked as deprecated, but still available on WebSphere Portal V5.x.

Note: Migrated portlet application projects are not backward compatible.
To migrate portlet applications for WebSphere Portal V4.2 to V5.x, do the following steps:
  1. Migrate the Portal V4.2 portlet projects to Portal V5.x portlet projects:
    1. Right-click the portlet application project that you want to migrate.
    2. Select Properties > Portlet API to open the Portlet API page.
    3. Select WebSphere Portal Version 5.x from the Portlet API level drop-down list.
    4. Click OK, and the following changes are automatically made:
      • The tag library descriptor (TLD) file for the portlet API is removed if it exists.
      • The Web level is changed from 2.2 to 2.3.
      • The portlet specific class path entries are removed, as the WebSphere Portal JRE container and WebSphere Portal runtime target container will dynamically add them.
  2. If your portlet project is associated to an enterprise application project, it is recommended that you migrate the J2EE level of the EAR project to J2EE 1.3. Portlet applications designed for WebSphere Portal V5.x should be compliant with the J2EE level 1.3 specifications.
    Note: Before migrating your enterprise application project to J2EE 1.3, read Migrating J2EE projects. For information on using the J2EE Migration Wizard, refer to the online help.
    1. If the migrated portlet project is only associated to the enterprise application project, do as follows:
      1. Close all editors in the workbench.
      2. Right-click the enterprise application project with which the migrated portlet project is associated.
      3. Select Migrate > J2EE Migration Wizard and click Next.
      4. Select J2EE version 1.3 and WebSphere Portal as the target server.
      5. Click Finish.
    2. If other portlet projects are associated with the enterprise application project, you must remove the migrated portlet project and add it to another enterprise application project.
      1. Remove the module of the migrated portlet project from the enterprise application project.
        1. Expand the enterprise application project and select the deployment descriptor.
        2. Select Open With > Deployment Descriptor Editor.
        3. Select the Module tab. On the Module page of the editor, select the WAR file of the migrated portlet project.
        4. Click Remove.
        5. Select File > Save to save the changes.
      2. Create a new enterprise application project and add the portlet project to it.
        1. Select File > New > Project.
        2. Select Show All Wizards check box.
        3. Expand the J2EE and select Enterprise Application Project.
        4. Fill in the project Name field, select J2EE version 1.3 and WebSphere Portal as the target server and click Next.
        5. On the EAR Module Projects page, select the migrated portlet project and click Finish.
The portlet project is now migrated to WebSphere Portal V5.x.
Related tasks
Migrating to the portal tools in Rational Application Developer V6.0
Updating Faces runtime resources in a portlet project
Feedback
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.