Developing Multi-Mappings for Message Splits

Use

This section describes how you develop a multi-mapping for a message split (1:n transformation). You can specify the multi-mapping program directly in the logical routing using an operation mapping. In a case such as this the operation mapping defines not only the mapping program (but also the target operation) that the target message is to be sent to at the logical routing. Therefore, it is also true to call it a Mapping-Based Message Split .

Prerequisites

A prerequisite for multi-mappings are that the interfaces involved are asynchronous. In addition there are also no restrictions for the outbound operation of the operation mapping.

For a mapping-based message split, the messages that are generated from the message split are sent using one Adapter Engine. The Java proxy runtime is not supported. This means that the selection of the possible target interfaces is restricted to the related adapter types. In particular, none of the target messages can be sent to an integration process.

The process flow described here assumed that the message schemata to the messages to be mapped to each other already exist in the ES Repository (you can find further information in the Function Scope section under Multi Mappings ).

The following restriction applies to the outbound and target messages that you map to from a message mapping: The outbound and target messages can be in another software component version like the message mapping, but must come from a software component version (and underlying software component versions, if necessary).

This restriction is also valid for the export function of the operation mapping described below that you use for the external development of multi-mappings.

Process

Developing Multi-Mappings as Message Mapping

  1. Create a Message Mapping .

  2. Switch to the Messages tab page in the Mapping Editor.

  3. Reference to a ( Fault ) Message Type , an IDoc, request, response, or fault part of an RFC or an external message (external messages come from external definitionen ).

  4. Enter the frequency for every message.

  5. Switch to the Design tab page and edit your message mapping as normal. The same rules apply as for normal message mappings.

  6. Create an Operation Mapping and refer to the operations that use this message schemata. Enter your message mapping in the operation mapping.

External Development of Multi-Mappings

You can implement multi-mappings not only using message mappings. You must only develop the mapping program using the same approach as described under Multi-Mappings :

  1. Create an Operation Mapping and refer to the interfaces that refer to the message schemata relevant for the multi-mapping. Only target operations of those adapter types that support message packaging are supported.

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

  3. Develop the multi-mapping by using the exported schema. The created target structure must be built as described under muli-mappings.

  4. If you are dealing with an XSLT or Java mapping (more information: Imported Archive (XSLT/Java) ), then import the mapping program into the ES Repository and reference to it from the operation mapping.

Result

You have developed a multi-mapping and integrated it into an operation mapping. You can now specify the operation mapping in an interface determination (in the Integration Directory) to configure a message split.