By comparing versions of individual messages you can see what changes to the message were made by the individual processing steps of a pipeline. You can compare entire messages and parts of a message.
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 messages for the current client.
The screen displays a list of processed or archived messages.
Click the message ID of the message for which you want to display the message versions, or select the corresponding line and choose Display orDisplay Archived Versions ().
The Display XML Message Versions or Display Archived XML Message Versions screen appears.
● The navigation area of the Display Archived XML Message Versions screen contains a list of existing message versions and their status.
● The navigation area of the Display XML Message Versions screen is divided into two areas. The upper area displays the selected message and all messages related to it, and their status, hierarchically. The lower area displays the versions of the message selected in the upper area.
To display the individual status of a message, choose Legend (). For more information, see Processing Status.
Both screens display the current message version in the display area, which is divided into two areas. The upper area (window 1) displays the message header and message body. The lower area (window 2) displays the message payload (or the error header for messages with errors).
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 message are grouped together and displayed as one document in window 1. <SOAP:Envelope> is inserted as the surrounding tag. This makes the 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 message. This information is also not part of the actual message.
The Inbound Message identifies the first processing step in the respective Integration Engine at this point.
● To compare complete 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.
● To compare the header, body, or payload of a message, double click the corresponding line under SOAP Header, SOAP Body, or 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.
● To display a complete 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 ().
● To save the contents of a window to your local file system as a file, choose Download Window 1 or Download Window 2 ().
To display the contents of a window in unformatted XML format in your notepad, choose View Source from the context menu.
● To save the entire message version (including the payloads) to your local file system, choose Save Entire XML Message to File ().
● To display the error text for a message with errors, choose Additional Information About Error ().
This option is only available for messages with errors.
The following options are only available for asynchronous messages with errors:
● If you want to edit a message with errors to correct the errors, in the navigation area, select the part of the header or body that you want to correct and choose Edit Message Part ().
This takes you to an editor where you can edit and save the message.
This editor is purely for text and you can only change this particular message. As a rule, you should correct errors where they are caused (for example, in the Integration Directory).
● To execute a message with errors again once you have corrected the error, choose Schedule XML Message Again After Error ().
When you restart, the last productive version of a message is automatically rescheduled. Consequently, it is possible that not all processing steps are performed again.
● To cancel the further processing of a message with errors, choose . The message can then be either archived or deleted.