Skip to Content
Technical Articles

Do not log Payloads on CPI with MPL – use Persist Message instead

As an integration consultant and SAP Trainer (CLD900) I see many developers using groovy scripts to store the payload to the MPL (message processing logs).

This is not a reliable approach to log payloads in production tenants and should be used for testing and special purpose only, not as a general approach.SAP has added a circuit breaker to stop writing MPL attachments if 1 GB data is stored in 24 hours, see SAP note 2593825.

Use the correct integration pattern instead: Persist Message! This puts the payload (incl. headers and attachment(s) into the message store (database) for 90 days.

As SAP does not (yet) provide a UI to open those payloads from the tenant management node, we are delivering the tool for free in the mean time: WHINT MessageStore Viewer.

Feel free to download it and deploy on your CPI tenant within minutes.

6 Comments
You must be Logged on to comment or reply to a post.
    • Hi Daniel,

      Storing the full message (payload, header and attachments) is a standard feature here.

      The only missing part is the UI to access the message store (which is just another place in the database). It does not relate to the data store, but is easily accessible from the OData API.

      I would usually recommend to stay in the standard as much as possible (as always in the SAP world). Using a (free) add-on is acceptable here, as it is not invasive (at iFlow runtime), but simply providing a read access after processing. In addition, I am pretty sure this will be offered by SAP in the standard UI…

      • Agreed it is best to stay at standard published interfaces.

        It is not like you have the ability to make changes if SAP make a modification in next months release.

         

  • Thank you for this, I tried to persist messages before, but was unable to retrieve them 🙂

    Do you know of any size limits when using the message store?

     

    As a side note, it was SAP who recommended to use the groovy scripts when we started with CPI (as you probably know). Only later did they restrict the storage to 1 Gb.

    • Dear Martin, I am not aware of any restriction per message, but there is (currently) an overall disk space limit of 32 GB for each tenant…

      • That certainly still makes us have to think about the amount of messages (and thus data) we want to store in the message store, considering that we run into the 1 Gb limit daily and the fact that the messages are kept for 90 days in the message store.

        Thanks, Adam.