Using the HATS Migration wizard

When you switch to the HATS perspective, if you have a project created from a previous HATS release in your HATS V9.6 workspace, you will get a message stating that the workspace contains a HATS project that needs to be migrated.

You should use the HATS Migration wizard to migrate this project to HATS V9.6 before investigating any errors shown in the Problems view because migration may eliminate some or all of these errors.

To use the HATS Migration wizard follow these steps:
  1. In the HATS Projects view, right-click on the project and select Migrate Project.
  2. If you have other projects from a previous HATS release that are associated with the HATS project you have selected to migrate, those projects will also be migrated, as well as any associated HATS .ear projects.
  3. Click OK to begin the migration.
  4. If the project does not have an associated .ear project, you must associate the .war project after the migration. To associate the .war project with an .ear project, see Moving HATS Web projects to a different .ear file.
Note:
  1. After migration check the details on the Migration Report.
  2. If a HATS Web project being migrated has an unsupported target runtime (if the Rational® SDP Workspace Migration wizard has not been run) or unsupported WebSphere® facets, the HATS Migration wizard sets the target runtime and facets to the lowest supported WebSphere® Application Sever level for Web projects. A message is displayed and logged stating the fact that the change was made.
  3. If, after migration, you receive an error indicating that the target runtime is not defined, edit the properties for the project and select the appropriate target runtime. To do this, right-click on the project and select Properties. From the Properties window select Targeted Runtimes. From the Runtimes list, select the appropriate runtime.
  4. Migrating your project from a previous HATS release to HATS V9.6 cannot be undone.