Rational Developer for System z

Migrating a service flow project to the latest level

This topic describes how to migrate a service flow project to the latest level of functionality.
This topic contains the following subtopics:

General information about migrating a service flow project

You can migrate a service flow project to the latest level using either of the following two methods:

a) Automated method:

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:

  1. Find the service flow project where it is listed in the EST Project Explorer.

    Note: A service flow project that is not at the latest level is displayed in the EST Project Explorer but is no longer expandable.
  2. 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.

  3. In the EST Project Explorer window:

    • Select Yes if you want to migrate the service flow project to the latest level.

      1. The EST Project Explorer migrates the service flow project to the latest level and opens the service flow project.

      2. 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.

      3. The workbench opens the build status window to show the progress of rebuilding the workspace.

      4. When the workbench successfully rebuilds the workspace and closes the build status window then the migration process is complete.

        Note: You can now work on the migrated service flow project using the new features of the latest level of the service flow project tools.
    • 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.

        Note: You cannot work on the artifacts of a service flow project that is at a previous level using the latest level of the service flow project tools.

b) Explicit method:

To use the explicit method:

  1. Find the service flow project in the EST Project Explorer.

    Note: A service flow project that is not at the latest level is displayed in the EST Project Explorer but is no longer expandable.
  2. Right-click the service flow project.

  3. Select Migrate Service Flow Project.

    1. The EST Project Explorer migrates the service flow project to the latest level and opens the service flow project.

    2. 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.

    3. The workbench opens the build status window to show the progress of rebuilding the workspace.

    4. When the workbench successfully rebuilds the workspace and closes the build status window then the migration process is complete.

      Note: You can now work on the migrated service flow project using the new features of the latest level of the service flow project tools.

Migrating from Version 7.0 or from Version 7.1

This subtopic describes the effects of migrating a service flow project that was most recently modified by someone using the Enterprise Service Tools component in either of the following products:
  • Rational® Developer for System z® Version 7.1
  • Rational Developer for zSeries® Version 7.0
Note: You can use either the automated method or the explicit method to migrate the service flow project to the latest level of functionality (see General information about migrating a service flow project).

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:

b) Changes to data in ESQL files:

The migration process makes the following changes with respect to data in ESQL files:

c) Changes to file extensions:

The migration process makes the following changes to file extensions (see Table 1):

Table 1. Changes to file extensions
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

Migrating from WebSphere Developer for zSeries Version 6.0

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:

Note: You can use either the automated method or the explicit method to migrate the service flow project to the latest level of functionality (see General information about migrating a service flow project).

This migration occurs in two steps:

  1. 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.

  2. Then the service flow project is converted to the latest level (see Migrating from Version 7.0 or from Version 7.1).

Saved copies of files at the previous level

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).


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)