Show TOC

Saving Message Versions in the AAE (Local Message Processing)Locate this document in the navigation structure

Use

You can save asynchronous messages that are processed in the Advanced Adapter Engine (AAE) either before or after processing steps.

You can then edit the message and, in special cases, restart processing of the changed message.

Note

This kind of saving message versions is also called staging (in contrast to message logging where synchronous messages are saved and only can displayed).

When you have configured local message processing using the AAE (using integrated configuration), you can store message versions after the following processing steps within the pipeline:

Processing Step

Description

Message preparation (parameter BI)

After sender adapter processing, the message is handed over to the messaging system and prepared for further processing.

Inbound XML validation (parameter VI)

The inbound message is validated against a schema.

Receiver and interface determination (parameter MS)

The receivers of the messages and the inbound interfaces are evaluated based on the configuration settings in the corresponding integrated configuration in Integration Directory.

Mapping (parameter AM)

The mapping is performed based on the configuration settings in the corresponding integrated configuration in Integration Directory.

Outbound XML validation (parameter VO)

The outbound message is validated against a schema.

The following figure shows the sequence of processing steps for local message processing in the Advanced Adapter Engine and also indicates where message versions can be stored:

Figure 1: Processing Steps Within the AAE

You can use parameters BI, VI, MS, AM, and VO to define whether a message version is to be saved and how further processing is to proceed. You have the following options to define the mode of further processing for each step:

  • 0 (MODE_NO_STORE)

    The processor does not save message versions; it continues with the next processing step.

  • 1 (MODE_STORE_ON_ERROR)

    The processor only saves a message version if an error occurs in the next processing step.

  • 3 (MODE_STORE_AND_RETURN)

    The processor saves the message and continues with the next processing step.

Note

At least one of the steps must be configured with value 3.

To configure the saving of message versions, use parameter xiadapter.stage.conf , which belongs to the service XPI Adapter: XI .

Procedure

Global Configuration of Staging

  1. Call SAP NetWeaver Administrator.

    You can use the following address: http://<host>:<port>/nwa

  2. Choose Start of the navigation path Configuration Management Next navigation step Infrastructure Next navigation step Java System Properties End of the navigation path.

  3. On the Services tab, select XPI Adapter: XI .

  4. Enter values for the xiadapter.stage.conf property.

    • You can enter 0, 1, or 3 for each processing step ( BI, MS, and so on).

    • Enter the values in the following format: BI=1, MS=3, ...

    • You can make additional entries for dual usage type scenarios where also the Integration Engine is involved in message processing by putting the variable set in parentheses and add a second variable set, also in parentheses. The first variable set applies to local message processing in the Advanced Adapter Engine; the second variable set applies only to those scenarios that include also message processing on the Integration Engine.

      More information: Saving Message Versions in the Advanced Adapter Engine (Dual Usage Type Message Processing)

      Example

      (BI=1,MS=3) (MS=3)

    • The parameters AM and VO cannot be used for dual usage type scenarios (second variable set). These parameters only apply to local message processing using the AAE.

    • If you do not make any entries, the message is saved in the Advanced Adapter Engine after receiver determination.

      This corresponds to the entry MS=3.

Scenario-Specific Configuration of Staging

You can also configure staging for specific scenarios that are covered by the integrated configuration.

For more information, see the documentation of the Integration Directory in SAP NetWeaver Library under Start of the navigation path SAP NetWeaver Library: Function-Oriented View Next navigation step Process Integration Next navigation step Integration Directory Next navigation step Defining the Integrated Configuration End of the navigation path.

Result

If a message is not delivered, the last saved message version is used for an automatic restart. If the time limit for an automatic restart has been exceeded and the message has the status Not Delivered , you can use each saved message version for a manual restart.

If you use a message version for the manual restart and later message versions exist, the message version number is increased to distinguish it from the other message versions.

Note

Note that when a message is restarted, it will be scheduled in a queue again. As a result of this, the processing time of a message might be extended when staging is applied. The message is rescheduled within the pool of messages already available in a queue.