Developing Multi-Mappings for Integration Processes 

Purpose

This section describes how to develop a multi-mapping for a transformation step in an integration process. In this case, the mapping runtime supports 1:n, n:1, and n:m transformations.

Prerequisites

The procedure described below requires that the message schemas for the messages to be mapped already exist in the ES Repository (see also Features in Multi-Mappings) and that they are assigned to asynchronous, abstract service interfaces. You can only use this interface type in integration processes.

Furthermore, all objects (integration process, operation mapping, and all objects referenced by the operation mapping) must be in the same software component version. If you want to reference objects from underlying software component versions, you must access the objects from the Basis Objects branch (in the navigation tree or using an input help) (see also: Underlying Software Component Versions).

Process Flow

Developing Multi-Mappings as Message Mappings

...

...

       1.      Create a message mapping.

       2.      In the mapping editor, switch to the Messages tab page.

       3.      Reference a (fault) message type, an IDoc, the request, response, or fault part of an RFC or an external message (External Messages originate from external definitions).

       4.      Specify the occurrence for each message.

       5.      Switch to the Design tab page and edit your message mapping as usual. The rules that apply to message mappings also apply here.

       6.      Create an operation mapping and reference the operations of the asynchronous abstract service interfaces that use these message schemas. Enter your operation mapping in your message mapping.

Developing Multi-Mappings Externally

Message mappings are not the only means of implementing multi-mappings. Develop the mapping program using the same approach that is described in Multi-Mappings:

...

       1.      Create an operation mapping and reference the operations of the asynchronous abstract service interfaces that reference the message schemas that are relevant for the multi-mapping.

       2.      Export the schema of the request message from the operation mapping.

       3.      Develop the multi-mapping by using the exported schema. The resulting target structure must be structured as is described in Multi-Mappings.

       4.      If the mapping is an XSLT or Java mapping (see: Imported Archive (XSLT/Java)), import the mapping program to the ES Repository and reference it from the operation mapping.

Result

You have developed a multi-mapping program and included it in an operation mapping. You can now enter the operation mapping in a transformation step in an integration process.