VisualAge Generator to Enterprise Generation Language Migration Guide


Chapter 8. Running migration in single file mode

An alternative to running migration using Stages 1-3 is running migration in Single File Mode. This process allows you to migrate one External Source Format file directly to an EGL file. To run migration in this mode, you must first export VisualAge Generator parts to an External Source Format file, and then import that External Source Format file into WebSphere Studio. During the import process, the External Source Format file is migrated into one or more EGL files, depending on your preferences.

To export parts from VisualAge Generator, do the following:

  1. Start VisualAge Generator on Java (or VisualAge Generator on Smalltalk) and open the VAGen Parts Browser.
  2. Select the parts you want to export and right-click the selection.
  3. From the context menu, select Import/Export --> VAGen Export (or VAGen Export with Associates).
  4. Type a name for the External Source Format file in the box and click the Save button. (If you type the name of an existing file, you will be asked if you would like to add parts to the file or overwrite it. Choose whichever is appropriate for you.)

To set up WebSphere Studio for single file mode, do the following:

  1. Start WebSphere Studio and point to your workspace. (For example, d:\workspaces\myworkspace)
  2. Set your migration preferences. See syntax migration preferences for information on how to do this.
  3. From the Workbench window, select Window -> Preferences -> VAGen Migration. In general, you should always ensure that the Separate parts into EGL files preference is selected. When you select this preference, each program, map group, and table is placed in its own file. This adheres to the EGL requirement of one generatable part per file. If you do not select Separate parts into EGL files, all the parts are placed in the same EGL file. See Overview of Single File Migration for specifics of the parts placement algorithm for single file mode.
  4. Change to the EGL perspective. Switch to the Navigator view.
  5. Create a new EGL Project. (For example, MyProject.) Alternatively, you might want to create an EGL Web project if you are planning to develop new EGL page handlers.
  6. Under the EGLSource directory for the EGL project, create a new EGL package. (For example, my.pkg)
  7. See the section Running single file migration using the user interface for details on running in online mode or Running single file migration using batch mode for details about creating a batch command file to process multiple External Source Format files with a single command file.


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