Configuring the general properties of a message map

You can configure the general properties of a message map in the Graphical Data Mapping editor.

About this task

You can optionally configure the general properties of a message map:
  • You can add documentation.
  • You can configure prefixes for your XML namespaces.
  • You can explicitly define references to Java™, ESQL, and XSD resources that the map can refer. Note the Graphical Data Mapping editor will normally add these automatically while editing.


Complete the following steps to configure the general properties of a map:

  • Open the Properties tab of a map by using any of the following methods:
    • Select a map by focusing on the map canvas, rather than on an individual item in the map. Then, select the Properties tab.
    • Right-click the map canvas, and then select Show in > Properties view.

      View of the context menu where you select Properties view.

    • Use the appropriate keyboard combination, which, by default, is Alt+Enter.

      You can configure these shortcut keys by selecting Window > Preferences > General > Keys.

  • In the Properties tab, add, modify, or remove resources:
    1. Select the General tab to view the namespace where the map is available.
    2. Select Java Imports to add or remove Java classes.

      If you add a Java call in the General tab of the Properties page of a Custom Java transform, an import is automatically added in the map to refer to the package qualified Java class, and a prefix based on the class name is added. All the public static methods in this Java class are then available in content-assist when building expressions in other transforms.

      If you only plan to use Java in XPath expressions on other transforms, you must first manually import the Java class into the map. You configure the Java imports tab in the Properties page of the map.

      For more information, see Mapping an element by using a Custom Java transform.

    3. Optional: Select ESQL Imports to add or remove ESQL files that Custom ESQL transforms can refer to in the message map.

      When you include a Custom ESQL transform, an import is added to refer to the ESQL file, defining a prefix based on the file name. If you need to use custom ESQL only in condition or filter expressions, you can add ESQL imports to your ESQL file so that the applicable modules are available through content assist when you are composing an expression.

    4. Select Scope to add or remove XSD files that you can refer to in the message map.
    5. Select Cast to obtain the list of input and output wildcard elements that are cast to a specific type or global element in the message map. You can remove any entry that is not required anymore.
    6. Select Namespaces to add, edit, or remove user-defined namespaces in the message map.
    7. Select Documentation to provide a description of the message map, or other relevant usage notes.

What to do next

Continue editing the map, and define transformations between the input message and the output message. For more information, see Editing message maps.