Migration from a previous version of EGL

The migration process from a previous version of EGL depends on the version that you are migrating from. Parts of the process are automated and other parts involve manual changes.

You do not need to run a migration tool to move from version 8.0 to a later version.

You also do not need to run a migration tool to move from version 7 to version 8.5. However, in this case, be aware of the considerations in “Migrating from version 7.0 and after.”

To migrate from a version earlier than 7.0, you must migrate your code from one level to the next until you reach the version 7.0 level.

You can use the following migration tools:
V6.0 Migration
The V6.0 migration tool converts EGL source from versions V5.1.2 and V6.0 to comply with EGL V6.0 iFix001.
V7.0 Migration
The V7.0 migration tool migrates code from EGL version 6.0.1 and later to the current version.
Workspace Migration
The workspace migration wizard migrates projects from version 6.0.x or 7.0.x to the current version. It runs automatically when an earlier project is detected. You can select to run the migration later. If you use web projects in version 6, you must migrate your workspace to version 7 before trying to use those projects in version 8. Version 8 cannot migrate version 6 web projects.

Before you begin

After the migration

After the migration tool finishes, you can review the changes that the tool made to the source code.

If you are migrating COBOL source or Rich UI projects, you might need to make more changes. For details, see “COBOL-to-EGL migration" and "Rich UI project migration.”

Note: When you start using a new version of the product, use a new workspace to avoid problems. For example, changes in the set of available preferences can cause errors if you continue to use a workspace that was created with an earlier version of the product.

Feedback