
Testing a Message Mapping
Purpose
You can check whether a complete message mapping functions at runtime once you have described it, by using the Test tab page. For this purpose, the mapping editor generates, compiles, and then executes Java source code for the message mapping.

The Integration Builder can not yet access the value-mapping table at this point. When using the ValueMapping function (Conversions category), the value mapping is merely estimated as text output in the test results.
Prerequisites
The defined message mapping must be complete. This means that each mandatory target field must be assigned to one or more source fields. Furthermore, there must not be any unassigned arguments when using functions.
If you used two XSD files for the message mapping description, you must create an XML instance for the source structure. Using this instance, the mapping editor executes a transformation to the target structure in accordance with the mapping described.
Process Flow
On the Test tab page the left-hand side is used to view the Source XML Instance and the right-hand side to view the result of the transformation (Target XML Instance). You have the same display options as for the Design tab page.
Result
If you are testing the message mapping for the first time or have modified it since the last test, the mapping editor compiles the generated Java source code. The result of the transformation is displayed on the right-hand side. Any errors that occurred during compilation are displayed in the lower text frame for Status Messages. An error may occur because a user-defined function was not syntactically correct, for example.