Show TOC

Saving Message Versions in the AAE (Dual Usage Type Message Processing)Locate this document in the navigation structure

Use

You can save asynchronous messages that are processed in the Advanced Adapter Engine (AAE) at specific steps within the pipeline. You can then edit the message and restart processing of the changed message.

Note

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

This section covers scenarios where in addition to the AAE also the Integration Engine is involved at runtime during message processing. Technically, both ABAP and Java stack are involved at runtime, therefore, they are referred to as “dual usage type” scenarios.

For dual usage type scenarios you can store messages after the following processing steps within the AAE 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.

Note

Note that after this step, it is evaluated whether dual usage type message processing involving the Integration Engine (as referred to in this section) or local message processing on the AAE is configured.

In case configuration settings for the incoming message are stored in sender agreements, receiver determinations, interface determinations and collaboration agreements, dual usage type message processing is configured.

In case configuration settings for the incoming message are stored in an integrated configuration, local message processing (technically using only the Java stack) is configured.

After scenario-lookup step (parameter MS)

The scenario (local or dual usage type processing) is evaluated.
Note

Messages can be rescheduled after being stored after a specific step.

The following figure shows the sequence of processing steps and also indicates where message versions can be stored in the AAE pipeline for scenarios where also the Integration Engine is involved:

Figure 1: Processing Steps for Dual Usage Type Message Processing
Note

For reasons of simplicity, the figure outlines only those dual usage type scenarios where a sender adapter of the AAE and a receiver adapter of the Integration Engine is used.

You can use parameters VI, BI, and MS 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.

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

Procedure

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

  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.

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

    • If you only enter one value (for example, BI=1), the configuration setting is only valid for message processing using the Advanced Adapter Engine “locally” (bypassing the Integration Engine). To specify staging behavior for dual usage type message processing (where also the Integration Engine is involved), you need to do the following: put 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 AAE; the second variable set applies to message processing using the Integration Engine.

    Example

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

If a message is not delivered, the last saved message version is used for an automatic restart in case of subsequent processing errors. 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.