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
of the Output Data Format field
in the Properties tab of the transition. Use
the Output Data Mapping window to map a constant, expression, 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 Input Data Mapping window opens when you click the Browse icon
of the Input Data Format field
in the Properties tab of the transition. Use
the Input Data Mapping window to map a constant, expression, 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 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:
- Indexed collections are displayed with its structure (without
all of its elements) because it is the kind of contents that will
be necessary when mapping data.
- The left Context panel of the Input Data Mapping window and the
right Context 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 supposed to be the
one with type=”session”.
- Root context (the one 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 supposed to be the one with type=”session”.
- Root context (the one 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 supposed to be the one with type=”session”.
- Root context (the one 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 is supposed to be the one with type=”session”.
- Root context (the one with type=”root”)