Show TOC

Designing and Configuring Multi-MappingsLocate this document in the navigation structure

Use

In standard mapping use cases, a single source message is transformed into a single target message. This kind of mapping is also referred to as a 1:1 transformation .

A multi mapping allows you to override this restriction. In particular, a multi-mapping gives you the following options:

  • Designing a 1:n transformation for a message split

  • Designing 1:n, n:1, and n:m transformations to be used in integration processes (cross-component Business Process Management)

Procedure

Designing 1:n Transformations for Message Splits (Interface Determination)

You can use a 1:n multi-mapping to map a message to multiple different (and generally smaller) messages during logical routing (mapping-based message split). To set up a message split scenario, you have to perform the following steps:

  1. ES Repository: Create the necessary multi-mapping and assign it to an operation mapping.

    More information: Developing Multi-Mappings for Message Splits

  2. Integration Directory: Select the operation mapping in the corresponding configuration object.

    • For Integration-Engine-based communication, you do this assignment in an interface determination.

    • For local message exchange using the Advanced Adapter Engine or in case you use the Advanced Adapter Engine Extended, you do this assignment in an integrated configuration.

    The inbound interface operations will be evaluated based on the multi-mapping.

    More information: Defining an Interface Determination

For more information on this technique, read section Defining Message Splits .

Designing 1:n, n:1, and n:m Transformations to Be Used in Integration Processes

You can use a multi-mapping in a transformation step of an integration process.

This is the summary of steps:

  1. ES Repository: Create the necessary multi-mapping and assign it to an operation mapping.

    Note

    It is a prerequisite that the message schemas for the messages to be mapped exist in the ES Repository and that they are assigned to asynchronous, abstract service interfaces. You can only use this interface type in integration processes.

    More information: Developing Multi-Mappings for Integration Processes

  2. ES Repository: Create an integration process and enter the operation mapping in a transformation step in an integration process.

    More information: Transformation Step