Data mapping

Figure 11 shows different types of business objects at each application and at the collaborations. The IBM WebSphere InterChange Server system, therefore, must convert business objects into like forms so that it can send events and data across applications and collaborations. Data mapping is the process of converting business objects from one type to another. Data mapping is required whenever the IBM WebSphere InterChange Server system sends data between a source and a destination that does not exactly share the source's data model.

Unlike custom application integration solutions that map data directly from one application to another, InterChange server collaborations generally use the generic business object between the application-specific data models. The generic business object serves as a common, cross-application data set. If you change applications in the future, you need only get a new connector and map the new application-specific business object to the generic business object. Collaborations then continue to work as they did previously.

Whenever a collaboration transfers a business object across dissimilar applications, mapping transforms the business object to and from the common data set. Business object transformation takes place:

For example, in a collaboration that synchronizes Clarify_BusOrg data with SAP_CustomerMaster data, mapping occurs twice:

Figure 12. Mapping transformations


Each connector controller manages the mapping of business objects that pass between its connector agent and InterChange Server. To actually perform data mapping, however, the system invokes the use of the mapping tools-- Map Designer and Relationship Designer. These tools let you create and modify detailed mapping specifications and execute mapping at runtime.

A connector controller invokes the mapping function when it receives business objects that require mapping. Figure 13 illustrates the invocation of mapping from the connector controller.

Figure 13. Mapping control and execution


Copyright IBM Corp. 1997, 2004