VisualAge Generator to Enterprise Generation Language Migration Guide
After you have finished editing your preferences, you are ready to run the
Stage 1 migration tool to extract your source code from the Smalltalk
library. To do this, perform the following steps:
- Start the EGL Migration Driver View using one of the following
techniques:
- If you modified the preferences by starting the Preferences Editor, start
the EGL Migration Driver View from the Systems Transcript by selecting
EGL Migration Tools -> Migration Driver.
- If you modified the preferences by starting the EGL Migration Driver, then
when you saved the preferences file, you are positioned back at the EGL
Migration Driver View.
-
Ensure the File Name for the Migration Preference File points to the file in
which you stored your preferences. Use the
Browse... button to point to a different
preferences file. Use the Edit...
button to review or make final modifications to your preferences.
- When you are satisfied with your preferences, select the Execution Options
that you want to use. The Execution Options control the output of the
Stage 1 migration tool as follows:
-
Overwrite PLN controls the migration plan file or files as
follows:
- If you select Overwrite PLN, the Stage 1 migration tool does
the following to files in the Plan Directory that you specified in your
preferences:
- If your preferences file does not specify a file name for your .pln
file, the migration tool deletes all the .pln files in the specified
Plan Directory and creates new files.
- If your preferences file specifies a file name for your .pln file,
the migration tool only deletes a file with the same name from the specified
Plan Directory before creating a new .pln file.
- If you do not select Overwrite PLN, the Stage 1 migration tool
does not create any new migration plan files. Instead, the Stage 1
migration tool runs based on the Plan Directory and Plan File Name you
specified in your preferences:
- If your preferences file does not specify a file name for your .pln
file, the migration tool runs using all of the plans in the specified Plan
Directory.
- If your preferences file does specify a file name for your .pln
file, the migration tool runs using only that .pln file.
-
Generate Report controls whether the migration tool creates the
report specified in the Verification section of the preferences file.
If you do not select this option, the report is not created. If you
select this option, the migration tool creates the report using the Report
File Name that you specified in your preferences.
The report shows how your configuration maps, applications, and VAGen parts
will be assigned to EGL projects, packages, and files during migration.
You might deselect this option initially so that you can review the
.pln files to ensure that the migration tool is planning to process the
configuration map versions that you want. If you are not satisfied with
the configuration map versions that are being selected, you can refine your
preferences and run Overwrite PLN again. When you are satisfied with
the configuration map versions that will be processed, run Stage 1 again with
the Generate Report option selected.
- Note:
-
- Generating the report can take some time, therefore it is best to review
the .pln files to be sure that the migration tool will process the
configuration map versions that you intend.
-
If you select the Generate Report option, the Stage 1 migration tool
automatically deletes any existing report files from the report
directory. If you want to save previous report files, you must move the
report files to a different directory or point to a new directory for your new
report. Because the report files link to other files, renaming the
report files will cause links to be lost and the files to become
unviewable.
-
Update Database controls whether the migration tool updates the
migration database with the migration plan information. If you do not
select this option, the migration database will not be updated. If you
select this option, the migration database you specified in your preferences
will be updated with information from the migration plan, including the
External Source Format for every VAGen part in the migration plan.
You might deselect this option initially so that you can review the report to
see how your configuration maps, applications and VAGen parts will be placed
into EGL projects, packages, and files. If you are not satisfied with
the placement, you can refine your preferences and run the report
again. When you are satisfied with the placement, you can run Stage 1 a
final time with Update Database selected so that the migration tool will put
the results into the migration database.
- Note:
-
-
If you select the Update Database option and a migration set already exists in
the database, the Stage 1 migration tool automatically deletes the old
information about migration set from the database and then adds the new
information for the migration set. There is no need for you to clean up
a migration set from the database.
-
The migration tool does not automatically clean up an entire migration
plan.
-
After you have selected your Execution Options, click OK to run
Stage 1 of the migration tool. The migration tool writes messages to
the log file you specified in your migration preferences. The tool also
puts the same messages in the System Transcript.
At this point, if you ran the Stage 1 migration tool and selected the Update
Database option, your migration plan information, including your VAGen code in
External Source Format, is stored in the migration database. After
reviewing your report and the Stage 1 messages, you might decide to make
changes to your code in VisualAge Generator and run Stage 1 again.
After you are satisfied with the results of Stage 1 and have your final
External Source Format code stored in the migration database, you are ready to
perform Stage 2 of the migration. To run the Stage 2 migration tool,
you use the WebSphere Studio product. See Stage 2 - Conversion to EGL syntax for information about continuing your migration process.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.