VisualAge Generator to Enterprise Generation Language Migration Guide


Migration plans and high-level configuration maps

A migration plan file is simply an XML file that specifies the names of one or more migration sets and, for each migration set, one high-level configuration map and version that specifies the applications and their versions for the migration set. The high-level configuration map can also specify other configuration maps and their versions as required maps. However, only one high-level configuration map version can be specified for a migration set. The Stage 1 migration tool is designed to automatically create a migration plan file for you based on your Repository Filters preferences for configuration map and version names. The Stage 1 tool uses these filters to select the configuration map versions that should be reviewed to determine which ones are high-level configuration map versions. The Stage 1 tool uses each high-level configuration map version as the basis for a migration set.

If you use high-level configuration maps when generating your VAGen source code, then these high-level configuration maps are the same ones you should use for migration. This is because each high-level configuration map provides a grouping of parts that are used together during generation and therefore has all the associated parts for a set of programs.

If you do not currently use configuration maps at all, you must create a configuration map to use for migration. In this situation, the easiest technique is to create one configuration map version that includes all the application versions, including common application versions, that you want to migrate as a group. See Creating a high-level configuration map for details. After you have created the configuration map, you can use the Stage 1 migration tool to automatically create the migration plan for you.

If you currently use configuration maps, you might not have high-level configuration maps. For example, you might have a configuration map for common applications and another configuration map for a subsystem. At generation time you determine which version of each configuration map to load into your image. In this situation, you can do one of the following to specify what you want to migrate as a group:


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