Editing Messages

Prerequisites

  • You have performed a search for messages in the message monitor, selected a message, and opened it.

    Note that you would be able to edit the selected message in the editor only when it matches all of the following criteria:

    • Asynchronous XI/PI messages

    • Not archived

    • Sent using the XI protocol

    • In any non-final error status

    In case the selected message does not meet any of these criteria, you would be only able to view its details.

    For more information about selecting a message, see Monitoring Messages and Reviewing Search Results .

  • The user account you use should be assigned to one of the Process Integration monitoring roles. Note that to view and download message attachments you should have permission to view the message payload. For more information about which roles allow you to view and modify messages, see Monitoring Roles .

Context

In case errors occurred during the processing of a message, you can edit it in the message editor. Depending of the type of message you can use this editor in the following ways:

  • When you use it for asynchronous messages in the Database tab with a certain status, you can edit the header, attributes, and the payload of the message.

  • When you use it for messages in the Archive tab you can only view message details.

  • You can have an integrated configuration where the message logging option is enabled, and at the same time the messaging.syncMessageRemover.removeBody parameter of the XPI Service: Messaging System service is enabled too. In such situation, you would not be able to view the payload and the attachments for messages for this configuration.

  • For asynchronous message for an integrated configuration configured to use both message logging and message staging, in the editor you can see both staged and logged versions of the message. Staged versions can be identified by their number, and logged version can be identified by their location displayed in the Version column.

When you open a message for editing you can modify its header data, create adapter-specific message attributes and change or delete existing attributes, modify the message payload, and download the attachments. The system locks the message for other users while you are editing it. You can delete the corresponding lock entries from the database. For more information, see Displaying Technical Data for the Adapter Engine .

Procedure


  1. Select a staged message version (not a logged version) with status Not Delivered to view its details.

    In case you have to edit the details, choose Edit .

  2. Choose the Message Header tab if you want to edit the message header data.

  3. Choose the Message Attributes tab if you want to edit the message attributes.

    You can create adapter-specific message attributes and change or delete existing attributes. You can also do this in the Integration Builder.

  4. Choose the Payload tab and use one of the following methods to view or edit the payload:

    • Edit the payload locally in the editor.

      The system recognizes the character format of the payload. It loads the payload in a predefined format in the editor, where you can edit it as necessary.

    • You can also use a separate editor to edit the payload. This is the case, for example, when one or more of the following applies:

      • The payload is too large for the message editor.

      • The payload contains characters that cannot be displayed in the message editor.

      • You prefer the user view of another editor.

      Proceed as follows:

      1. To load the message payload in a separate editor, choose Download .

      2. Edit the payload in the selected editor and save it as a file.

      3. To localize the changed payload in your file system, choose Browse in the message editor.

      4. To upload the payload to the message editor, choose Upload .

  5. Choose the Attachments tab to view and download the attachments for the selected message version.

  6. Save the message.

Results

Once you have edited and saved the message, the system automatically reloads it in the message editor. Then you can process the message again.

After you have edited a message, the mapping of this message is determined again:

  • If you change the header data of the message, the mapping can result from another interface determination. If no interface determination has been configured for the changed header data, there is no mapping. Therefore, a changed message should always have a configuration.

  • Changes to the payload can also influence which mapping is used, since the determination of the mapping can depend on conditions.

Next Steps

For more information about message versions, see Saving Message Versions in the Advanced Adapter Engine .