Welcome
Upgrading and migrating
EGL migration overview
No migration is necessary if you are starting with EGL version 8.x. Otherwise, the process you follow to migrate to the current EGL version depends on whether you are migrating from a non-EGL source or from a previous EGL version.
Migration from non-EGL source code
If you migrate to the current version of EGL from other languages, see the following information:

Overview
Getting started
Installing
Upgrading and migrating
- EGL migration overview
  No migration is necessary if you are starting with EGL version 8.x. Otherwise, the process you follow to migrate to the current EGL version depends on whether you are migrating from a non-EGL source or from a previous EGL version.
  - Migration from non-EGL source code
    If you migrate to the current version of EGL from other languages, see the following information:
  - 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.
  - EGL migration tool
    You can use the EGL migration tool to migrate entire projects or individual packages and files. You must migrate JSP files and their associated pageHandler parts at the same time. The tool corrects syntax changes, updates invocations of system libraries that have changed, corrects the names of properties that have changed, and makes other updates.
  - COBOL-to-EGL migration
    If you migrate COBOL source code from either EGL version 6 or VisualAge® Generator, the amount of generated code increases. The architecture of the generated programs was revised in EGL version 7.0 to support the complete EGL syntax, including string data types. In most cases, even though the source program is larger, the program will run faster in EGL version 7 and above.
  - Rich UI project migration
    When you migrate Rich UI projects to later versions of EGL, remember these considerations.
  - Post migration results
- Migrating from VisualAge® Generator to EGL
EGL Code Accelerator for IBD
Developing
Samples
Troubleshooting and support
EGL runtime error messages
Reference
Glossary
Using the help
Notices for IBM Business Developer documentation

Migration from non-EGL source code

If you migrate to the current version of EGL from other languages, see the following information:

To migrate source code that was written in VisualAge® Generator, see Migrating from VisualAge® Generator to EGL.
To migrate source code that was written in Informix® 4GL, see Converting from IBM® Informix® 4GL to EGL.