When you try to open a service flow project that was most recently modified using an earlier level of the service flow project tools, the EST Project Explorer automatically prompts you to indicate whether you want to migrate the service flow project to the latest level. This is the automated method.
To use the automated method:
Find the service flow project where it is listed in the EST Project Explorer.
Try to open the service flow project by double-clicking it.
The EST Project Explorer window opens and displays a message asking whether you want to migrate the service flow project to the latest level.
In the EST Project Explorer window:
Select Yes if you want to migrate the service flow project to the latest level.
The EST Project Explorer migrates the service flow project to the latest level and opens the service flow project.
The Service Flow Migrate Plug-in window opens and displays the names of the subprojects or folders that were migrated.
Click OK to close this window.
The workbench opens the build status window to show the progress of rebuilding the workspace.
When the workbench successfully rebuilds the workspace and closes the build status window then the migration process is complete.
Select No if you do not want to migrate the service flow project to the latest level.
The service flow project is not migrated.
The service flow project is not opened.
To use the explicit method:
Find the service flow project in the EST Project Explorer.
Right-click the service flow project.
Select Migrate Service Flow Project.
The EST Project Explorer migrates the service flow project to the latest level and opens the service flow project.
The Service Flow Migrate Plug-in window opens and displays the names of the subprojects or folders that were migrated.
Click OK to close this window.
The workbench opens the build status window to show the progress of rebuilding the workspace.
When the workbench successfully rebuilds the workspace and closes the build status window then the migration process is complete.
The migration process makes three types of changes:
a) Changes to data in mapping files:The migration process makes the following changes with respect to data in mapping files:
Mapping routines from the old mapping files are converted to a new data format that is compatible with the Common Mapping component of Rational Developer for System z.
All the converted mapping routines for a single flow (for example, Flow_0001.seqflow) are stored into a new mapping file which has the same name as the flow and which has the new mapping file extension .sfmap (Flow_0001.sfmap).
The old mapping files are saved and are accessible from the Navigator view, but they cannot be used with migrated service flow projects (see Saved copies of files at the previous level).
The migration process makes the following changes with respect to data in ESQL files:
The ESQL code, which up to now has been stored inside ESQL modules in ESQL files, is converted to ESQL expression format.
The converted ESQL expressions for all the Switch nodes and While nodes for a flow are stored into the flow file itself (for example, Flow_0001.seqflow). ESQL files and ESQL routines are no longer required.
The old ESQL files are saved and are accessible from the Navigator view, but they cannot be used with migrated service flow projects (see Saved copies of files at the previous level).
The migration process makes the following changes to file extensions (see Table 1):
| Type of file: | Previous extension: | New extension: | Changes in data format: |
|---|---|---|---|
| ESQL file | .esql | .sfesql | Yes (see Changes to to data in ESQL files) |
| Generation properties file | .wsdl | .sfgen | No |
| Mapping file | .seqmap | .sfmap | Yes (see Changes to data in mapping files) |
| Message file | .mxsd | .sfmxsd | No |
| Message set file | .mset | .sfmset | No |
You can migrate to the latest level of functionality from a service flow project that was most recently modified using the Service Flow Modeler component in the following product:
This migration occurs in two steps:
First the service flow project is converted to the level used by the Enterprise Service Tools component in Rational Developer for zSeries Version 7.0.
Then the service flow project is converted to the latest level (see Migrating from Version 7.0 or from Version 7.1).
This subtopic describes the mapping files and the ESQL files that the migration process saves when it migrates service flow projects from Version 7.0 or version 7.1 of Rational Developer for System z (see Migrating from Version 7.0 or from Version 7.1).
The migration process saves a copy of each mapping file from the previous level with its contents undisturbed (still in the format used by the previous level). The saved file has the same name and extension that it had before the migration (for example, Flow_0001.seqmap).
You can do the following things with the mapping file from the previous level:
You can see the mapping file listed in the Navigator view in the seqmap folder.
You cannot do the following things with the mapping file from the previous level:
You cannot use the mapping file with migrated service flow projects
You cannot modify the mapping file with the new level of service flow project tools. (For example, you cannot open a mapping routine in the file from the flow editor.)
ESQL files are treated similarly to mapping files. The migration process saves a copy of each ESQL file from the previous level with its contents undisturbed (still in the format used by the previous level). The saved file has the same name and extension that it had before the migration (for example, Flow_0001.esql).
You can do the following things with the ESQL file from the previous level:
You can see the ESQL file listed in the Navigator view in the esql folder.
You cannot do the following things with the ESQL file from the previous level:
You cannot use the ESQL file with migrated service flow projects
You cannot modify the ESQL file with the new level of service flow project tools. (For example, you cannot open an ESQL module in the file from the flow editor.)