VisualAge Generator to Enterprise Generation Language Migration Guide


Overview of Single File Migration

When you are first getting accustomed to WebSphere Studio and setting up your environment, you might want to migrate just a few programs to verify your environment, ensure generation and preparation are working properly, and ensure your runtime environment is properly configured for EGL. In this case, you might not want to go through the full Stage 1 to 3 migration. The Stage 2 migration tool provides a mechanism for you to migrate programs using what is called single file migration as shown in the following figure:
Graphic of single file migration

Single file migration is a more manual process than Stage 1 to 3 migration. In single file mode, you use VisualAge Generator to export External Source Format source code to a file. Then you use WebSphere Studio to create an EGL project and EGL package. From WebSphere Studio, you can then use the Import wizard to import the External Source Format file. The single file migration tool runs and does the following:

The External Source Format to EGL conversion that occurs during single file migration is essentially the same syntax conversion that occurs during Stage 2 of the Stage 1 to 3 migration. However, single file migration has several limitations that do not make it suitable for large scale migrations. The limitations include:

See "Migration challenges" and Techniques used by the VisualAge Generator to EGL Migration Tool for a better understanding of the differences between single file migration and Stage 1 to 3 migration.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]