Show TOC

Background documentationRuntime Locate this document in the navigation structure

 

The business process is executed in the system landscape at runtime, which means that the process is executed and messages are exchanged between the systems involved. In mediated scenarios, messages are processed by a central instance — or: runtime engine — that interconnects the systems.

This section provides detailed information on how a message is processed by the involved runtime engines.

At runtime, a message passes through the following steps:

  1. Sender adapter processing

    Based on the configuration of the sender adapter, the message is transformed technically to the XML message format the PI runtime can process (“XI message format”). In case also additional security-related configuration settings apply, the message is handled accordingly.

  2. Runtime engine pipeline processing

    Processing of the message in the pipeline contains the following steps:

    1. Inbound XML validation

      Based on the configuration settings, the inbound message is checked with regard to validity of its XML schema.

    2. Receiver determination

      Based on the configuration setting (routing configuration) that is found in the runtime cache for the message, the receivers of the message and the routing conditions are evaluated. The receiver is written into the message header. In case multiple receivers are configured, for each receiver, a separate message is created.

    3. Mapping

      Based on the configuration setting (mapping configuration) that is found in the runtime cache for the message, the assigned mapping program is performed and the content of the message transformed accordingly.

    4. Interface determination

      Based on the inbound interface configuration that is found for the message, the assigned inbound interface (at the receiver side) is evaluated.

      Note Note

      More sophisticated scenarios can be configured where a message is sent to multiple inbound interfaces or where a large message is split into several “message chunks” which are then sent to different inbound interfaces. For sakes of simplicity we do not consider these cases here. .

      End of the note.

    5. Outbound XML validation

      Based on the configuration settings, the outbound message (to be sent to the receiver) is checked with regard to validity of its XML schema.

  3. Receiver adapter processing

    Based on the configuration of the receiver adapter, the message is transformed technically from the “XI message format” to the format the receiver can process. In case also additional security-related configuration settings apply, the message is handled accordingly.