Before you start:
Before you
can define your mappings, you must have defined the message or database formats
for both the source and the target that you want to use.
Defining the mapping involves a number of possible options and
operations:
- Direct assignment of a source field to a target field
- Assignment based upon some condition, or set of conditions, having
been met
- Assignment that needs to have a function applied to the source
before it is assigned to the target
- Assignment that is made after some ESQL is executed, qualifying
the assignment
- Assignment of a literal value to a target
The mappings are defined using the Message
Brokers Toolkit for WebSphere Studio.
Note: If a message element is of a type that extends a base type,
only the elements or attributes explicitly defined in the extended type can
be mapped in the Message Flow Mapping editor. To access elements or attributes
defined in the base type, either use the Compute node, or define a type that
contains the content of the base type, instead of deriving the elements or
attributes from the base type.