Defining data mappings

This section describes how to define data mappings for a data formatter by using the Data Mapping window.

About this task

IBM® WebSphere® Multichannel Bank Transformation Toolkit provides the following two data mapping windows for you to define data mappings:
  • The Output Data Mapping window opens when you click the Browse icon The Browse icon of the Output Mapping field in the Properties tab of the transition. Use the Output Data Mapping window to map a constant, expression, global function, or the context of the source state to the flow context. Figure 1 shows the Output Data Mapping window.
    Figure 1. The Output Data Mapping window
    The Output Data Mapping window.
  • The Input Data Mapping window opens when you click the Browse icon The Browse icon of the Input Mapping field in the Properties tab of the transition. Use the Input Data Mapping window to map a constant, expression, global function, or the flow context to the context of the target state. Figure 2 shows the Input Data Mapping window.
    Figure 2. The Input Data Mapping window
    The Input Data Mapping window

The procedures for using the Input Data Mapping window and the Output Data Mapping window are the same.

Note: If you are mapping contexts, the items in the Context panels of the Data Mapping windows will be displayed as described in the following list:
  • The Mapping Context panel of the Input Data Mapping window and the Mapping Target panel of the Output Data mapping window displays the following items:
    • Local context (if it exists)
    • Session context (if it exists) and all of the parent contexts of the session context. The session context is the context with type=”session”.
    • Root context (the context with type=”root”)
  • The right Context panel of the Input Data Mapping window and the left panel of the Output Data mapping window displays the following items:
    • For a subflow state:
      • Subflow context
      • Local context (if it exists)
      • Session context (if it exists) and all its parent hierarchy. Session context is the context with type=”session”.
      • Root context (the context with type=”root”)
    • For a target operation state:
      • Operation context (in case it exists)
      • Local context (if it exists)
      • Session context (if it exists) and all its parent hierarchy. Session context is the context with type=”session”.
      • Root context (the context with type=”root”)
    • For all other target states:
      • Local context (if it exists)
      • Session context (if it exists) and all its parent hierarchy. Session context the context with type=”session”.
      • Root context (the context with type=”root”)

Procedure