Rational Developer for System z, Version 7.6

Renaming a mapping file

Use the contextual menu in the EST Project Explorer to rename a mapping file.

To rename a mapping file:

  1. In the EST Project Explorer, right-click the name of the mapping file that you want to rename.

  2. Select Rename. The Rename Resource window opens.

  3. In the Rename Resource window:

    1. The name of the mapping file that you selected is displayed in the input field. (To rename some other mapping file, type a different name into the input field.)

    2. Determine whether you want to update references to the mapping file after it is renamed:
      • If you want to update references, then select the check box Refactor result of rename within files?.
      • If you do not want to update references, then clear the check box.

      Determining whether to update references:

      Recall that a mapping routine can be referenced by an Assign node or by the input terminal or an output terminal of most types of Invoke nodes (see Artifacts from which mapping routines can be referenced) and that a reference to a mapping routine contains: (1) the name of the mapping routine; and (2) the name of the mapping file in which the mapping routine is located (see How mapping routines are accessed.)
      • If you rename a mapping file without choosing to update references, and any mapping reference in the service flow project includes the name of that mapping file, then that reference is no longer valid. The service flow project tools will try to resolve the reference but it will fail, because the mapping file specified in the reference no longer exists in the service flow project.

        For example, suppose that the input terminal of an Invoke nonterminal node named GetRegion contains the reference to an input mapping shown in Table 1:

        Table 1. Reference to the input mapping
        A reference to an input mapping:
        Name of mapping file: Flow10.sfmap
        Name of mapping: GetRegion_t_msg_CUSTOMERINFO

        Suppose now that you rename the mapping file Flow10.sfmap to Flow10_B.sfmap without choosing to update references. The reference shown in Table 1 is no longer valid, because the specified mapping file Flow10.sfmap no longer exists -- it has been renamed to Flow10_B.sfmap.

      • In contrast, if you rename the mapping file and choose to update references, then the renaming facility does the following:
        1. The renaming facility checks all Assign nodes and the terminals of eligible types of Invoke nodes in the service flow project for references that include the old name of the renamed mapping file.
        2. The renaming facility replaces the old name with the new name. (For example, in the reference shown in Table 1, the renaming facility changes the name of the mapping file to Flow10_B.sfmap.)
    3. Click OK.

The mapping file is renamed.


Terms of use | Feedback

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