VisualAge Generator to Enterprise Generation Language Migration Guide


Running single file migration using the user interface

To import the External Source Format file into WebSphere Studio, do the following:

  1. Using the EGL perspective, in the Navigator view, select the EGL package in which to put the resulting EGL file.
  2. Right-click the package. From the context menu, select Import.
  3. Select VAGen External Source Format File and select Next.
  4. In the Input File Name field, enter the name of the External Source Format file you want to import.
  5. In the Source Folder field, enter the name of the project and source folder in which to put the EGL file. (For example, MyProject\EGLSource)
  6. In the Package Name field, enter the name of the package to be used in the package statement within the EGL file. (For example, my.pkg)
  7. In the EGL File Name field, enter the name of the EGL file that will be created from your External Source Format file. By default, the EGL file name will be the same as the External Source Format file, but with the .egl file extension. See Overview of Single File Migration for information about how the migration tool uses the Separate parts into EGL files preference and the type of parts in the External Source Format file to determine what files to create during migration in single file mode.
  8. In the Log File Location field, enter the drive and directory where the migration log file is to be placed. In the Log File Name field, enter the name for the migration log file. The Log File Name defaults to match the name of the External Source Format file that you specified. The migration log file contains any messages written during migration.
  9. Click Finish. If the file name you specified in the EGL File Name field already exists in the container you specified in the Container field, you are prompted to append or overwrite to the file.
  10. When the migration completes, you should notice the following:
  11. Select the project and then select Project --> Rebuild Project. This causes validation to run so that the Tasks list reflects the most current messages for all files in the project.


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