Show TOC

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

Context

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

When you have configured local message processing using the AAE (using integrated configuration), you can store messages at the following stations within the pipeline:

  • Before inbound schema validation (parameter VI)

  • Before scenario look-up step (parameter BI)

    At this step, it is evaluated whether local message processing on the AAE (as referred to in this section) or dual-stack message processing involving the Integration Engine is configured.

    Note

    In case configuration settings for the incoming message are stored in sender agreements, receiver determinations, interface determinations and collaboration agreements, dual-stack 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.

  • Before mapping step (parameter MS)

  • Between mapping and outbound schema validation (parameter AM)

  • After outbound schema validation (parameter VO)

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:

  • 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.

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

Procedure

  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 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-Stack Message Processing)

      Example

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

    • Only set parameters AM and VO for local message processing in the Advanced Adapter Engine.

    • 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.

Results

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.