VisualAge Generator to Enterprise Generation Language Migration Guide
The Build Plans page enables you to specify information about where the
migration plan is to be placed.
The Build Plans page also enables you to indicate which configuration maps and
versions in the library you want to consider for migration. The Build
Plans page is organized in the following sections:
- Migration Plan Specification information identifies where the
Stage 1 migration tool is to read or write the migration plan file (or
files).
- Plan Directory. This is the target directory where you
want your migration plan file (or files) to be placed.
-
Plan File Name. An optional file name of the migration plan
file you are creating and using to load the migration database. You can
click the Plan File Name button to view existing plan files in your
plan directory. If you need to see details within a plan file, click
the View Plans button and expand the plan file to see the migration
sets.
- If you specify a file name, the migration tool creates a single file with
your specified file name. In this case, the single file lists all the
migration sets.
- If you do not specify a file name, the migration tool creates one plan
file for each migration set. In this case, the file names are of the
form migrationSetName_version.pln.
-
Repository Filters information enables you to control which
configuration maps and versions in your Smalltalk library are considered by
the Stage 1 migration tool. Limiting the configuration maps and
versions can greatly enhance the performance of the Stage 1 migration
tool. You can specify multiple filters.
The Stage 1 migration tool uses the Configuration Maps filter and the Version
Name or Version Depth filters as follows:
- The migration tool matches each configuration map name in the library
against the Configuration Maps filter.
- If the configuration map name does not match at least one of the
Configuration Maps filters, the configuration map is not considered for
further processing.
- If the configuration map name matches at least one of the Configuration
Map filters, the versions of the configuration map are processed as
follows:
-
If you specified any Version Name filters, then each version name for the
configuration map is matched against the list of Version Name filters.
If the version name matches any of the Version Name filters, then the version
is considered for further processing.
- If you specified the Version Depth filter and did not specify any Version
Name filters, then the most recent versions of the configuration map, up to
the number specified by the Version Depth filter, are considered for further
processing.
-
If the configuration map name and version name result in the configuration map
version being considered for further processing, the Stage 1 migration tool
does the following:
-
If the configuration map version is a high-level configuration map, then the
migration tool uses the configuration map version as the basis for creating a
migration set.
Each version of the high-level configuration map results in a different
migration set, assuming the version name matched the version filter.
- If the configuration map version is not a high-level configuration map,
the configuration map version is not considered for further processing.
The configuration map version might still be included in other migration
sets; there just will not be a migration set specifically for this
configuration map version.
Specify the Repository Filter information as follows:
-
Configuration Maps filter. The migration tool matches the
configuration map names in your library to the Configuration Maps filter (or
filters) that you specify. You can specify multiple Configuration Maps
filters. To add, change, or remove filters, right-click on a filter and
use the options on the context menu. The filters are not case
sensitive. You can use wildcards in the filters as follows:
- A configuration map filter of *xyz* matches any configuration
map name in the library that has the string "xyz" anywhere in its name.
- A configuration map filter of xyz* matches any configuration
map name in the library that begins with "xyz".
- A configuration map filter of *xyz matches any configuration
map name in the library that ends with "xyz".
-
Version Name filter. If a configuration map name matches the
Configuration Maps filter, the migration tool uses the Version Name filter to
determine which, if any, of the configuration map versions should be
considered for migration. You can specify multiple Version Name
filters. To add, change or remove filters, right-click on a filter and
use the options on the context menu. The filters are not case
sensitive. You can use wildcards in the filters as follows:
- A version name filter of *xyz* matches any configuration map
version name that has the string "xyz" anywhere in the version name.
- A version name filter of xyz* matches any configuration map
version name that begins with "xyz".
- A version name filter of *xyz matches configuration map version
name that ends with "xyz".
- If you leave the Version Name filters field empty, the migration tool uses
the Version Depth filter.
-
Version Depth filter. You can specify the number of previous
versions you want to migrate. The default is 1, in which case the
migration tool only processes the most recent version of the configuration
map. If any Version Name filters are specified, the Version Depth
filter is ignored.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.