VisualAge Generator to Enterprise Generation Language Migration Guide
To achieve a good cross-part migration, when you migrate a part, you must
provide not only the part itself but all parts that it references. For
example, when you migrate a program, you should provide not only the program,
but also all the parts that the program references. For a program, the
set of parts that you need when you migrate the program is the same set of
parts that you need when you generate the program in VisualAge
Generator. This set of parts is the program's associates
list.
In VisualAge Generator, the common techniques for providing all the parts
for generation are as follows:
-
Project List Parts (PLPs) in VisualAge Generator on Java
-
Configuration maps in VisualAge Generator on Smalltalk.
The migration tool makes use of these two techniques. The tool uses
the following terminology:
- If you are migrating from VisualAge Generator on Java:
-
A high-level PLP project is a Java project that contains a Project
List Part (PLP) and is not referenced by any other PLP.
-
A migration set consists of all the VAGen projects referenced in a
Java high-level PLP project, including all VAGen projects in the entire PLP
chain starting at the high-level PLP project.
- If you are migrating from VisualAge Generator on Smalltalk:
-
A high-level configuration map is a Smalltalk configuration map
that is not listed as a required map by any other configuration map.
- A migration set consists of all the Smalltalk configuration
maps listed as required maps in a Smalltalk high-level configuration
map. The migration set includes all the configuration maps from the
entire chain of Smalltalk required maps starting at the high-level
configuration map.
-
A migration plan is a file that specifies the information for one
or more migration sets.
If you specify a migration plan file name in your Stage 1 preferences then
all the migration sets that match your repository filters are placed in the
same migration plan file. If you do not specify a migration plan file
name, then each migration set is placed in a separate migration plan
file.
Note: If you are migrating from VisualAge Generator on Java and do
not currently use PLP projects, you can create PLP projects to use just for
migration. Alternatively, you can do one of the following:
-
If you have information in a database or other system that specifies what is
needed for generation in terms of Java project versions, then you can write a
tool to create the migration plan file (or files) automatically from your
database.
- Create the migration plan file (or files) by hand.
If you are migrating from VisualAge Generator on Java, see the section Migration plans and high-level PLP projects for more details.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.