Mapping considerations (WebSphere ICS integration broker only)

In some TPI implementations, a company may have two or more trading partners receiving documents based on the same business object, Sales_Order, for example, but in different formats. This scenario requires a polymorphic map, which can output business objects in different formats depending on which trading partner is receiving the data.

A polymorphic map is essentially two or more separate submaps, one for each output type, that take the same input object but produce output objects of different types. These submaps are called by a single main map, which tests for a condition, such as an attribute value, to determine which submap to call. Once the submap has generated an output object, the main map returns the object to the connector.

One way of implementing this for TPI is to use the ReceiverID attribute value as the determining condition. Based on the ReceiverID in the input object, the main map calls the appropriate submap. It is the task of the submap to:

For more information on polymorphic maps, see the Map Development Guide.

Copyright IBM Corp. 1997, 2003