Choosing a mapping action
You can add different parts of the message tree to the map input, to the map output, or to both. You can also add the local environment tree. Depending on how you add a message assembly component, this component can be deleted, initialized, or transformed.
Procedure
Identify the action that you want to achieve in your message map to find out how to add a message assembly component into the message map:
Results
The following table summarizes the mapping engine behavior when you add the local environment tree to your message map. The same behavior applies when you add any of the header folders, such as the folder, to your message map.
Input element | Output element | Transform defined between the input element and the output element | Mapper behavior |
---|---|---|---|
Local environment tree | Local environment tree | A transform operation such as Move is defined between the input local environment tree and the output local environment tree. Additional transforms are defined between some elements of the local environment tree within an Override function to change the value of those elements. | The input local environment tree is copied into the output local environment tree. The elements whose transforms are defined within the Override function have output values different from the input values based on the transformation. The elements outside the Override function maintain the same values in the output local environment tree. |
Elements from other message assembly components, database elements whose values are obtained by doing a database read, or a combination of both | Local environment tree | A Move transform is defined between each parent input message assembly structure and its corresponding output message assembly structure. Additional transforms are defined between input elements and the output local environment tree. Note: If you do not define the Move transform between an input and an output message assembly structure from which you use values to set the local environment output elements, then you will lose the message assembly structure in the output message, although your map will perform the transformation correctly.
|
Each input message assembly structure is copied into its corresponding output message assembly structure. The output local environment variables are defined as per the additional transforms using values from the input elements. |
Local environment tree | Local environment tree | None | Delete the original local environment tree. An empty local environment tree is created for the output message. |
Local environment tree | None | None | Delete the original local environment tree. An empty local environment tree is created for the output message. |
None | Local environment tree | None | Delete the original local environment tree. An empty local environment tree is created for the output message. You might populate some of the fields by using transforms between other input map components such as the message body and the new local environment structure. |
Local environment tree | Local environment tree | A transform operation such as Move can be defined between one element from the input local environment tree and one element from the output local environment tree. The rest of the local environment elements do not have transforms defined that specify how to move the input value to the output value. | The output local environment tree is initialized and only the element that has the transform defined has a non default value set. |
Local environment tree | Local environment tree | A transform operation such as Move is defined between the input local environment tree and the output local environment tree. | The input local environment tree is copied into the output local environment tree. |
What to do next
Configure the message map to include the local environment tree or a message header. For more information, see Customizing a message map to include a message assembly component.