If you already have external controls that determine what project versions to add to your workspace when you generate in VisualAge Generator, you might decide to create the migration plan file manually or to develop a tool to create the migration plan file automatically from your external information. The migration plan file must have a .pln file extension and the following format:
<migrationDefinition> <migrationSet name="migrationSet1" version="migrationSet1Version1" vgName="migrationSet1" vgVersion="migrationSet1Version1"> <project name="projectName1" version="projectName1Version1"></project> <project name="projectName2" version="projectName2Version1"></project> . . . <project name="projectNameN" version="projectNameNVersion1"></project> </migrationSet> <migrationSet name="migrationSet2" version="1.1" vgName="migrationSet2" vgVersion="1.1"> <project name="projectNameA" version="projectNameAVersion1"></project> <project name="projectNameB" version="projectNameBVersion1"></project> . . . <project name="projectNameZ" version="projectNameZVersion1"></project> </migrationSet> </migrationDefinition>
In the previous example, the following applies:
The migration set name is only used during migration as a way of identifying a group of projects. Other than the situation in which maps span multiple projects in VisualAge Generator, the migration set name is not used after migration.
You can build a migration plan file that contains just one migration set. Alternatively, you can build a migration plan file that contains several migration sets by repeating the information between the <migrationSet> and </migrationSet> tags for each migration set.
When you are ready to run the Stage 1 migration tool, do the following:
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.