VisualAge Generator to Enterprise Generation Language Migration Guide

Stage 3 Details

The Stage 3 tool is shipped in the same vagenmigration Eclipse plug-in as the Stage 2 tool and also runs in the WebSphere Studio environment. Because the information you want to migrate is now in the migration database, you use the same Stage 3 tool regardless of whether you are migrating from VisualAge Generator on Java or VisualAge Generator on Smalltalk. The basic steps for running the Stage 3 tool are as follows:

  1. You define rules and preferences to tell the Stage 3 tool what you want to migrate, including the following:
  2. Based on the rules and preferences you have defined, the Stage 3 tool does the following:
    1. Creates a "to do" list for the migration set. This "to do" list contains a consolidated list of the messages produced by Stage 2 that might require you to perform additional tasks to complete the migration.
    2. Creates the EGL project and package structure in your workspace based on the information stored in the migration database during Stage 1.
    3. Creates the .egl source files based on the EGL source code that was stored for the VAGen parts during Stage 2. The .egl source files include most import statements that are needed to resolve EGL part references. See "EGL build path and import statements" for details about the import statements.
    4. Creates the .eglbld files based on the EGL XML source that was stored for VAGen control parts during Stage 2. The control parts are generation options (EGL build descriptor parts), linkage options, resource associations, bind control and linkedit parts.
  3. At this point you should do the following:
    1. Review the workspace for any messages on the Tasks list to see if there are any validation errors. You can do this in conjunction with the log produced in Stage 2.
    2. Generate (without preparing) all programs and tables to ensure proper migration for your target environment. When you generate the programs, be sure to use the genFormGroup and genHelpFormGroup build descriptor options so that all your formGroups are also preprocessed. This step is optional, but it is strongly recommended.
    3. Version or commit the EGL projects into your source code repository.
    4. Generate and test the migrated code. This step is also optional, but it is strongly recommended.

The Stage 3 migration tool can be run in batch mode. See Stage 3 for details about running the Stage 3 tool on EGL. The Stage 3 tool is installed automatically at the same time you install the Stage 2 tool. You cannot modify the Stage 3 migration tool.


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