Migrating workspaces and projects from version 9.1.x or version 9.0.x

This topic describes the steps for migrating projects that you developed in version 9.1.x or version 9.0.x so that you can continue to work with them in the current version or the product.

Before you begin

Before you migrate your projects, do the following things:

Read Migration overview and Compatibility with version 9.1.x and version 9.0.x.
Make a copy of your version 9.1.x or version 9.0.x workspace.

About this task

Migration steps:

Procedure

To start the migration process, bring the version 9.1.x or version 9.0.x projects into the workspace by using one of the following methods. Important: Always ensure that all of your projects build cleanly in the earlier product version before you start the migration.
- Best practice: Import projects shared in a source code management (SCM) system.
  Tip: Start by creating a new stream or branch (as applicable) in your SCM system. This will ensure that the original project versions are available for use in the earlier product versions of the product. It will also provide a fall-back point, should you encounter any problem during migration and need to start over again.
- Alternate method (if you do not use an SCM system): Import projects that have been exported as archive files from the earlier version.
  Tip: Save backup copies of the project archives. This will ensure that the original project versions are available if needed to be used in the earlier versions of the product. It will also provide a fall-back point, should you encounter any problem during migration and need to start over again.
- Alternate method (if you do not use an SCM system): Open a version 9.1.x or version 9.0.x workspace with the current version of the product.
  Tip: Save a backup copy of the original workspace before you begin. This will ensure that the original workspace is available if needed for use in the earlier versions of the product. It will also provide a fall-back point, should you encounter any problem during migration and need to start over again.
The Workspace Migration wizard starts automatically.
In the Workspace Migration page in the Workspace projects which need migration section, select the projects that you want to migrate and click Next.
Tip: If there are any projects that choose not to migrate at this time, then the next that you start the current workspace the Workspace Migration wizard will start and select the projects that you did not migrate.

Note: If you choose not to migrate your projects, they will not function properly, and error messages may appear in the problems view. If you decide not to perform migration at this time, close your projects if you decide not to perform migration at this time. When the projects are reopened, you will be prompted again to migrate them.
If you have any projects that target a runtime environment that is not available in the current version (for example, you are migrating a project from version 9.0.x that targets the WebSphere Application Server V6.0 runtime), then the Undefined Server Runtime page displays. Do the following things:
1. Under Server Runtimes, the Undefined Server Runtime column lists the runtimes that are not available in the current version. For each undefined server runtime, select the runtime environment to use in place of it in the New Server Runtime column.
2. Near the bottom of the page, all projects that target an undefined server runtime are selected by default to change to the new server runtime. Clear any projects that you do not want to change and then click Next.
On the Migration Project Resources page, you can see which files in the workspace will be modified by the migration process. To copy a the list of files, right-click the list and click Select All, then right-click the list and click Copy. After you copy the list, you can paste the list into a text editor or similar program to save for your reference. When you are finished with the list of files, click Next.
Note: In the case your workspace is under a source code management (SCM) system, these files are going to be checked-out from the SCM system. They are not checked in again when the migration process completes; you must check in theses files manually.
Click Finish.
When the migration process completes, the Migration Validation window opens. Click OK. The Migration Results view opens. You can see the messages generated during the validation of the migration.
- Blue messages are informational messages.
- Green messages are successful validation checks.
- Orange messages are warning messages.
- Red messages are error messages.

What to do next

Depending on the projects in your workspace and the version that you are migrating from, you might need to perform additional steps to complete the migration of your projects.

Note:

Some workspace perspectives that were available in earlier versions might not be available in version 9.5.x. (For example, the J2EE perspective from version 7.0.x is replaced by the Java EE perspective in later versions.) However, you might still see an icon for old perspective in the top-left corner of the version 9.5.x workspace. If you click the icon, you will get the following error message: Could not restore workbench layout. Reason: Problems occurred restoring workbench.
If this happens, close the perspective (Window > Close Perspective ).
Some views that were available in earlier versions might not be available in the current version. For example, you might not have not installed the same features or extensions in your current workbench. In these cases, the first time that you open your previous workspace in version 9.5.x or switch to a perspective that used the view that is not available, you will get the following error message: Could not restore workbench layout. Reason: Problems occurred restoring perspective. The details section of the error message window will have one or more messages starting with the text Could not find view In this case, the message is expected and will only occur the first time that there is an attempt to open the missing view.

Feedback