VisualAge Generator to Enterprise Generation Language Migration Guide
The design of the VisualAge Generator to EGL migration tools has several
major objectives:
-
Preserve the program behavior from VisualAge Generator to EGL.
-
Preserve the Java project and package structure from VisualAge Generator to
EGL when appropriate.
-
Preserve the Smalltalk configuration map and application structure from
VisualAge Generator to EGL when appropriate.
-
Enable you to perform incremental migration of subsystems, one subsystem at a
time.
- Enable you to migrate multiple versions of your subsystems.
The design of the VisualAge Generator to EGL migration tools also has
several secondary objectives:
-
Use batch mode processing as much as possible with opportunities for you to
optionally review the planned migration at critical points before proceeding
to the next step.
-
Store information about the planned migration in a database so that it can be
preserved across multiple project versions and multiple subsystems.
This also enables you to save intermediate results as backup. This is
important if you have large numbers of parts in your repository.
-
Provide a set of sample programs for the tool that extracts the VAGen source
from your repository and loads the migration database. You can
optionally tailor the sample programs to more accurately reflect your
environment.
The design of the VisualAge Generator to EGL migration tools is based on
the following assumptions:
- Migration is from VisualAge Generator 4.5 using External
Source Format that is produced by VisualAge Generator 4.5.
- The parts to be migrated are valid VisualAge Generator
parts. Programs, tables, and map groups can be validated and/or
generated in VisualAge Generator 4.5.
There are two methods for using the VisualAge Generator to EGL migration
tools:
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.