VisualAge Generator to Enterprise Generation Language Migration Guide

Stage 2 Details

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

  1. You define rules and preferences to tell the Stage 2 tool what you want to migrate, including the following:
  2. Based on the rules and preferences you have defined, the Stage 2 tool does the following:
    1. Retrieves parts for one migration set from the database.
    2. Converts the External Source Format source code to EGL source code.
    3. Stores the EGL source code in the migration database. Messages associated with part migration are also stored in the migration database. This improves performance for Stage 2 because if the same part edition is used in another Java project version or Smalltalk configuration map version, the EGL source code is already available and not converted again.
    4. Creates a log file of any potential problems that are encountered, including generatable parts that conflict with the EGL reserved word list or ambiguous situations that the migration tool is unable to resolve.
    5. Iterates to process the next selected migration set.

The Stage 2 migration tool can be run in batch mode. See Stage 2 - Conversion to EGL syntax for details about installing and running the Stage 2 tool on WebSphere Studio. You cannot modify the Stage 2 migration tool.


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