Show TOC

Background documentationRouting Locate this document in the navigation structure

 

The routing specifies how a message is forwarded from the Integration Server or Advanced Adapter Engine to one or more receivers.

SAP NetWeaver Process Integration supports the following routing types:

  • Forwarding a message to one or more receiver systems (simply called Receivers from now on)

  • Forwarding a message to different inbound interfaces of a receiver

  • Dividing a message into multiple submessages

Forwarding the Message to Different Receivers

The message coming from the sender is forwarded from the Integration Server or Advanced Adapter Engine to one or more receiver systems.

This graphic is explained in the accompanying text.

Forwarding a Message to Three Different Receivers

There are several variants for this type of routing:

  • Content-based routing

    The forwarding of the message to a receiver is connected to conditions that relate to the content of the message.

    Example Example

    All messages that have the value 0001 for the customer number element are forwarded to the receiver system ABC.

    End of the example.

  • Dynamic routing

    The receivers of a message are determined dynamically at runtime by a mapping program.

    Note Note

    Dynamic routing is not currently supported if the message is processed by the Advanced Adapter Engine.

    End of the note.

You configure the forwarding of the message to different receiver systems in a receiver determination. For the configuration to be complete, you must also define an interface determination. You use this to determine which inbound interface the message is to be sent to for each receiver. If a mapping is also to be executed, specify this in the interface determination.

More information:

Forwarding the Message to Different Inbound Interfaces

For this type of routing, the inbound message is forwarded from the Integration Server or Advanced Adapter Engine to different inbound interfaces of a receiver. You can also define a mapping for each inbound interface.

This graphic is explained in the accompanying text.

Forwarding a Message to Three Different Inbound Interfaces of a Receiver

There are several variants for this type of routing:

  • Content-based routing

    The forwarding of the message to a specific inbound interface is connected to conditions that relate to the content of the message.

You configure the forwarding of a message to different inbound interfaces (and, if required, assign mappings) in an interface determination.

More information: Defining an Interface Determination

Dividing a Message into Multiple Submessages

An outbound message is divided by a multi-mapping into multiple submessages for this type of routing. This is referred to as a message split.

Note Note

Mapping-based message splits are currently not supported if the message is processed by the Advanced Adapter Engine.

End of the note.

This graphic is explained in the accompanying text.

Dividing a Message into Three Submessages

You can also connect this type of routing with conditions that relate to the content of the message.

To configure a message split, define an interface determination. As a prerequisite you need a multi-mapping that maps the outbound message to the submessages.

More information: Configuring Mapping-Based Message Splits