Show TOC

Procedure documentationConfiguring the Enhanced Settings for Saving Messages Locate this document in the navigation structure

 

For messages that are processed using this integration configuration, you can create settings for saving message versions at runtime. In this way you specify the processing steps according to which messages are to be stored on the Advanced Adapter Engine at runtime.

Note Note

This option is of interest for administrators who monitor the running of integration scenarios and have to take action in cases of errors.

End of the note.

There are two options for saving message versions:

  • Staging: You can save message versions, edit them and restart the processing of the changed message.

  • Logging: You can save message versions for logging purposes. In this mode you only have read-only access to the message version.

For more information, see the SAP NetWeaver Library under   SAP NetWeaver Process Integration   Administrative Tasks   Saving Message Versions  .

Procedure

  1. Select the Enhanced Settings tab page.

  2. Specify if you want to save message versions for staging or logging.

    Irrespective of the communication mode, decide which option you want to make the settings for:

    • For asynchronous message processing you make the settings for staging or logging.

      Note Note

      Note that staging can have a negative impact on performance. You should therefore only employ staging when you need to Edit or Restart functions.

      End of the note.

    • For synchronous message processing you make the settings for logging.

  3. Specify if you want to configure staging or logging globally or scenario-specifically.

    • Using Global Configuration

      If you choose this option, those settings are effective that were configured using Java system properties with SAP NetWeaver Administrator globally for all scenarios. For more information, see the documentation as referenced above.

      Note Note

      If you selected this option, you can skip the next step.

      End of the note.

    • Using Scenario-Specific Configuration

      If you select this option, the settings that you configured specially for this integrated configuration are effective for staging or logging.

  4. If you have selected the scenario-specific configuration, you must enter for staging or logging the steps after which the message versions are to be saved. For each step you can specify what is to happen with the message at runtime.

    For staging you can select the following processing steps:

    Processing Step

    Description

    Message Preparation (Step BI)

    The message version if saved after it was forwarded from the sender adapter to the messaging system.

    Inbound XML Validation (Step VI)

    The message version is saved after the inbound XML validation.

    Receiver Determination (Step MS)

    The message version is saved after the receivers have been determined for the message.

    Mapping (Step AM)

    The message version is saved after the mapping has been executed.

    Outbound XML Validation (Step VO)

    The message version is saved after the outbound XML validation.

    For every step you have the following options to specify more accurately what is to happen with the message at runtime:

    • None

      Message version not saved.

    • Save on error

      Message version saved when the following step has errors.

    • Save

      Message version is saved and the processing is continued with the next step.

    For logging you can select the following processing steps:

    Processing Step

    Description

    Message Preparation (Step BI)

    The message version if saved after it was forwarded from the sender adapter to the messaging system.

    Receiver Determination (Step MS)

    The message version is saved after the receivers have been determined for the message.

    Mapping (Step AM)

    The message version is saved after the mapping has been executed.

    For every step you have the following options to specify more accurately what is to happen with the message at runtime:

    • None

      Message version not saved.

    • Log

      Message version saved for logging.

    • Log on error

      Message version saved for logging in case of errors.

    • Log without payload

      Message version saved for logging. Payload cannot be displayed.

    • Log without payload on error

      Message version saved for logging in case of errors. Payload cannot be displayed.

    Note Note

    You can combine the selection of multiple processing steps both for staging and for logging.

    For more information on the processing steps, see the documentation specified above.

    End of the note.