Migrating WebFacing projects

Migration of old projects must be completed before you can continue development of your WebFacing applications. For example, you cannot convert DDS source or change your project's properties. You can run unmigrated projects as is, however. To differentiate between unmigrated and up-to-date projects, unmigrated projects are identified with unique icons in the WebFacing Projects view.

There are two stages of project migration. The first stage is performed by the base product for any type of Web project, and the second is performed by the WebFacing Migration wizard to handle updates specific to WebFacing projects.
Important:
  • WebFacing only supports migrating projects at release level V7.0 and later.
  • See the WebFacing Migration technote for a list of known issues and resolutions related to migration as well as updates to the migration process that may become known after this document has been released.

Base migration

Start of changeBegin by making sure the latest updates and fix packs for all Rational® products are installed using the IBM® Installation Manager. This step is very important as it will eliminate many problems you may run into. See Updating installed product packages at http://www-01.ibm.com/support/knowledgecenter/SSRTLW_9.5.0/com.ibm.rad.install.doc/topics/t_update.html and Updating the HATS Toolkit installation at http://www-01.ibm.com/support/knowledgecenter/SSXKAY_9.5.0/com.ibm.hats.doc/doc/gsinstal.htm%23update for details.End of change

WebFacing projects must be loaded into a current workspace before they can be migrated with the WebFacing Migration wizard. Migration is irreversible, so it is recommended that you back up your workspace or projects.

Previous WebFacing projects can be introduced into the current level workspace by opening the old workspace or importing old projects. Existing projects can be imported directly from folders or archive files, including project interchange files (Import > General > Existing Projects into Workspace, then choose Select archive file).

After a project is opened in the current level workspace, the Rational Desktop Migration wizard may appear. The wizard enables you to select which projects to update and shows you which files will be modified. Go through the wizard and make any necessary changes, and click Finish to start project migration. When workspace migration is complete, results are displayed in the Migration Results view. See Migrating workspaces and projects at http://publib.boulder.ibm.com/infocenter/radhelp/v8r5/index.jsp?topic=/com.ibm.etools.rad.migration.doc/topics/t_migratefrom70.html for more details.

If any errors are reported, or if the migrated project is flagged with errors, refer to Troubleshooting WebFacing applications as well as the online document WebFacing Migration technote, which is kept up-to-date.

Note: You can ignore the following dialog if it appears after the Workspace Migration wizard has completed. This error will be resolved later in this document.
  • Migration validation completed with some errors. See the Migration Results view for additional information. The Migration Results view highlights errors similar to: The WebSphere facet "WebSphere Web (Extended) 5.1" is not compatible with the WebSphere runtime "WebSphere Application Server vX.Y.

After workspace migration is complete, you can manually reset the perspective by clicking Window > Reset Perspective.

Your projects are now ready for use in the new workspace; however, they still must be migrated using the WebFacing Migration wizard.

Using the WebFacing Migration wizard

Preparing a project for WebFacing migration

You must perform the following preparatory tasks before running the WebFacing Migration wizard.

  1. Ensure that a valid server is selected on the Targeted Runtimes page. This is required if the server originally targeted is no longer supported.
    1. In the Navigator view, right-click your project and select Properties.
    2. Open the Targeted Runtimes page and select the server level where the project will be run.
    3. Click OK.
  2. If your project is at the Java™ EE 1.3 level, it must be migrated to 1.4 or higher using the Java EE Specifications Migration wizard before WebFacing migration can proceed. Refer to Migrating the specification level of Java EE projects at http://publib.boulder.ibm.com/infocenter/radhelp/v8r5/index.jsp?topic=/com.ibm.javaee.doc/topics/tmgv6j2eewiz.html.
    Note: If you see a dialog titled Inconsistent Files during Java EE migration, click Yes to dismiss it. Similarly, if at the end of the wizard you see the message Migration finished with errors, click the Details button. The following message can be safely disregarded: Error: org.eclipse.core.runtime.CoreException: Runtime WebSphere Portal v6.0 stub does not support project facet WebFacing 1.0.
  3. Resolve any classpath errors in your project.
    1. Open the Problems view (Window > Show View > Other > Problems).
    2. Check if there are any classpath or build errors reported, for example: ClassName cannot be resolved [to a type], The project cannot be built until build path errors are resolved, or Unbound classpath variable.
    3. Resolve any such errors as described in the WebFacing Migration technote.

Running the WebFacing Migration wizard

Next, use the WebFacing Migration wizard to update your projects to the current version. You can no longer migrate projects by reconverting DDS files.

  1. To launch the WebFacing Migration wizard, right-click your unmigrated project in the WebFacing Projects view and select Migrate WebFacing Project.
  2. Click Finish to migrate the selected project to the current version.
  3. Click OK if a Results dialog appears notifying you that the Struts version of your project has been changed.
  4. If your project was migrated from a version earlier than V7.5.0, it is recommended that you reconvert your DDS, especially if you plan to use the Firefox browser with your WebFacing applications.
Note: If the project being migrated is a HATS/WebFacing Enabled project, the corresponding HATS project must also be migrated. See Start of changeMigrating to HATS V9.5End of change for details.

Customized projects may require manual intervention. See Manual steps for migrating projects with customized files and WebFacing support for multiple browsers for further details.

Migrated WebFacing projects require a HATS license to be deployed, just as new WebFacing projects do. If you already have a HATS license applied, your migrated projects will also contain this license setting. Refer to Enabling licenses for more information.


Feedback