Procedure documentation Displaying XML Message Versions Locate the document in its SAP Library structure

Use

You can display individual XML messages for evaluation purposes from a list of processed or archived XML messages and compare existing versions with each other.

By comparing versions of individual XML messages you can see what changes to the XML message were made by the individual processing steps of a pipeline. You can compare entire XML messages and parts of a message.

Prerequisites

You chose the corresponding options in the monitoring menu and the system now displays a screen with a list of processed or archived XML messages.

Procedure

...

       1.      Click the message ID of the XML for which you want to display the message versions, or select the corresponding line and choose Display or Display Archived Versions (This graphic is explained in the accompanying text).

The system navigates to the screen XML Message Versions or Archived XML Message Versions. It contains a list of all existing message versions, including their status in the navigation area and the current message version in each case.

Note

Choose Legend (This graphic is explained in the accompanying text) to display a list of the different message statuses. For more information see the Processing Status section.

The upper display area (window 1) contains the message header and body. The lower display area (window 2) contains the message payload (or the error header for message with errors).

Note

If the payload is too large to be displayed, the lower display area remains empty and a corresponding message is displayed.

The individual parts of the XML message are grouped together and displayed as one document in window 1. <SOAP:Envelope> is inserted as the surrounding tag. This makes the XML document syntactically correct but it is not part of the actual XML message.

Depending on whether you are displaying an original message or a message version, the system displays Inbound Message or the description of the pipeline processing step that generates the version, as a comment in the XML message. This information is also not part of the actual XML message.

The Inbound Message identifies the first processing step in the respective Integration Engine at this point.

       2.      To compare complete XML message versions, select the line Inbound Message or the name of the respective processing step, for example Response and specify for each selection whether the system should display the message in the upper part of the screen (Display Contents in Window 1) or in the lower part of the screen (Display Contents in Window 2).

The display containers are not mutually exclusive. This means that you can display parts of messages in the containers that cannot be compared.

       3.      To compare the header, body or payload of a message, double-click the corresponding line under SOAP Header, SOAP Body or Binary Payloads in the navigation area. Alternatively, select the line and choose Display Contents in Window 1 or Display Contents in Window 2, depending on whether you want to display the parts at the top or the bottom of the screen.

       4.      To display a complete XML message, double-click the corresponding line in the navigation area or select the line and choose Display Contents in Window 1 or Display Contents in Window 2 (This graphic is explained in the accompanying text).

       5.      To save the contents of a window to your local file system, choose Download Window 1 or Download Window 2.

Note

To display the contents of a window in unformatted XML format in your notepad, choose View Source from the context menu.

       6.      To save the complete XML message (including the payload) to your local file system, choose Save Complete XML Message to File.

       7.      To display the error long text for an XML message with errors, choose Further Information on Error (This graphic is explained in the accompanying text). The error long text contains possible error causes as well as information for troubleshooting.

Note

This option is only available for XML messages with errors (This graphic is explained in the accompanying text).

       8.      To edit a message with errors to correct the error, choose Edit Message Part (This graphic is explained in the accompanying text).

Note

This option is only available for asynchronous XML messages with errors (This graphic is explained in the accompanying text).

       9.      To reschedule a message with errors having corrected the error, choose Reschedule XML Message After Error (This graphic is explained in the accompanying text).

Note

This option is only available for asynchronous XML messages with errors (This graphic is explained in the accompanying text).

   10.      To confirm a message with errors and to mark it for deletion, choose Confirm Error (This graphic is explained in the accompanying text).

Note

This option is only available for XML messages with errors (This graphic is explained in the accompanying text).

You require the authorization object S_XMB_DSP here because the displaying of message contents must be controlled individually. Unless the user has administrator authorization (S_XMB_ADM), the system only displays XML messages for the current client.

 

 

Leaving content frame