Migrating to the portal tools in Rational Application Developer V6.0

Portal Toolkit V5.0.2.2 projects will be migrated automatically to Rational® Application Developer V6.0 Portal Tools by migrating the Portal Toolkit workspace, or loading the project from a SCM (source code management) system, or importing the project using the Project Interchange feature. If you are migrating from earlier versions of Portal Toolkit, you will need to export your portlet projects to WAR files and import the WAR files into the Portal Tools in Rational Application Developer V6.0.

Before migrating portal applications, you must install the portal tools feature of Rational Application Developer V6.0. Refer to the installation guide.

Note: Backward compatibility of portlet projects is not supported.
Automatic migration is only supported for projects created in Portal Toolkit V5.0.2.2 with WebSphere® Studio V5.1.2. Refer to Migrating from WebSphere Studio V5.1, 5.1.1, or 5.1.2 for details on migration.

If your portlet project is associated to an enterprise application project, you will need to set the appropriate target server on the EAR project. You can set the target server on the Server Properties page (Properties > Server).

During migration of Portal Toolkit V5.0.2.2 projects, some additional changes take place:
  • The target server is set to WebSphere Portal V5.0, if no target server is set to the project.
  • The portlet build path is corrected
  • A portlet project nature is added.

If you are migrating from earlier versions of Portal Toolkit, you need to manually migrate your portlet projects to Portal Tools in Rational Application Developer V6.0, as follows:

  1. Export the existing project to a WAR file: In the earlier version of Portal Toolkit, export each project to a WAR file with source files.
    1. Right-click the project and select Export.
    2. Select WAR file and Export source files and click Finish.
  2. Import the portlet WAR file:
    1. In the Portal Tools for Rational Application Developer V6.0, create a new empty portlet project.
      1. Select File > New > Project > Portal > Portlet Project or Portlet Project (JSR 168).
      2. Deselect Create a portlet.
      3. Click Show Advanced.
      4. If you are importing a WebSphere Portal 4.2 portlet, select 2.2 as the servlet version.
      5. Select WebSphere Portal v5.0 as the target server, and click Finish.
    2. Import the WAR file to this new empty portlet project.
      1. Select Import.
      2. Select WAR file and specify the WAR file that you exported above (Exporting project to WAR file in earlier version).
      3. Select the new empty portlet project.
      4. Select Overwrite existing resources without warning.
      5. Do not select Delete project on overwrite.
  3. Delete the TLD file:

    It is recommended that you delete the portlet TLD file from the project if it exists. Otherwise, you will get a warning message when you rebuild the project. Leaving it may cause a problem when the portlet project is deployed to WebSphere Portal and the TLD file of the portlet is different from the file in the server.

  4. If you are migrating a WebSphere Portal 4.2 portlet, you need to migrate this migrated portlet project to WebSphere Portal 5.x.
For information on migrating WebSphere Portal V4.2 portlets to V5.x, refer to Migrating WebSphere Portal V4.2 portlets to V5.x.

For information on migrating Faces resources in a portlet project, refer to Updating Faces runtime resources in a portlet project.

Related tasks
Migrating WebSphere Portal V4.2 portlets to V5.x
Updating Faces runtime resources in a portlet project
Migrating from WebSphere Studio V5.1, 5.1.1, or 5.1.2
Related reference
Changes in WebSphere test environments
Feedback
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.