Saving Message Versions
You can store versions of messages at runtime in the Advanced Adapter Engine (AAE) and the Integration Engine (IE). You can specify at which processing step in the pipeline of the AAE and the IE the message version is to be stored. Later, you can edit the message, for example, in order to correct faulty data in the payload, and then restart and process the message again.
This function is only available for asynchronous messages.
Message versioning is configured globally. That means, the configured settings are valid for all integration scenarios.
Configuring Message Versioning on the IE
For more information on how to configure message versioning on the Integration Engine, see Displaying Message Versions (Integration Engine).
Configuring Message Versioning on the AAE
When you use the standard (dual-stack) implementation option of SAP NetWeaver PI, you can configure message versioning on the AAE for the two different kinds of message processing scenarios:
-
Dual-stack message processing including the IE
This kind of message processing is referred to as “dual-stack message processing” because, technically, AS ABAP and AS Java are involved for message processing at runtime. This kind of message processing has been available in the very first releases of SAP NetWeaver PI. It is configured using the configuration objects receiver determination , interface determination , and sender/receiver agreement in Integration Directory.
More information: Saving Message Versions in the Advanced Adapter Engine (Dual-Stack Message Processing)
-
“Local” message processing on the AAE
This kind of message processing is set up using the integrated configuration object in Integration Directory. It involves only the Advanced Adapter Engine at runtime, the ABAP stack is not involved at all.
More information: Saving Message Versions in the Advanced Adapter Engine (Local Message Processing)