The Web services mapper is an IBM® WebSphere® Multichannel Bank Transformation Toolkit formatter that is used by the Web services access operation when a Web service is invoked. The Web services mapper is required for data to be exchanged between the WebSphere Multichannel Bank Transformation Toolkit context and the Java objects from the Web services provider.
The Web services mapper is required because the data model of WebSphere Multichannel Bank Transformation Toolkit applications is different from the data model of Java Web services. For WebSphere Multichannel Bank Transformation Toolkit applications, data is described by using data fields, keyed collections (kColl), and indexed collections (iColl). Data in WebSphere Multichannel Bank Transformation Toolkit applications are then organized into contexts according to their business functions. However, Java Web services require Java objects as input parameters and send outgoing messages as Java objects. To enable data to be exchanged between WebSphere Multichannel Bank Transformation Toolkit applications and Java Web services, the Web services mapper is required by the Web services access operation to create data element mappings between the WebSphere Multichannel Bank Transformation Toolkit data model and the Java Web services data model
To enable WebSphere Multichannel Bank Transformation Toolkit applications to invoke Web services and receive data from Java Web services, Web services mappers are defined for every data element that is required by the WebSphere Multichannel Bank Transformation Toolkit application to invoke Web services. Data between the WebSphere Multichannel Bank Transformation Toolkit application and Java Web services cannot be exchanged until Web services mapper definitions for every message to and from Java Web services have been configured.
The Web services mapper can be defined in the format.xml file as a global scope entity. The Web services mapper can also be defined in a self-defined operation or a self-defined processor flow as a local scope entity.
For a Web services mapper to be identified by a Web services access operation, the Web services mapper must have a unique id defined in the externalized file.