Skip to Content

One of the most prominent new features PI 7.1 shows off is local processing of messages in the AAE. With PI 7.1 EHP1 this feature also allows content based routing and message splitting at the AAE. SAP Enhancement Package 1 for SAP NetWeaver Process Integration 7.1 – Details

 

One important factor I had to consider and re-think was how monitoring was possible if message processing was done locally in the AAE. Since messages are no longer sent to the integration engine – the classic transaction SXMB_MONI in the ABAP stack wouldn’t be an option. Evidently the only other option PI offers out of the box was using the RWB.

 

This is the option I choose. As you think about monitoring just with Message monitoring in the RWB, one thing strikes you the most, how can you view payload/ content of synchronous messages in RWB’s message monitoring? By default this parameter is turned off.

In this blog, I’d like to demonstrate how we can enable viewing of the payload content for synchronous messages in RWB’s message monitoring. (PI 7.1 and above)

image

image

In the Slides above, we see that by default – when we try to view the payload content of a synchronous message, we don’t have an option of viewing the payload.

Here are the steps to enabling viewing of payload content for synchronous messages in RWB’s Message monitoring.

1. Login to NWA.

2. Choose Configuration Management -> Infrastructure -> Java System Properties

image

3. On the Services Tab, Select XPI Service: Messaging System and then select Properties. Under Properties choose the parameter messaging.syncMessageRemover.removeBody and change its value to false.

image

image

We have now completed the configurations required to view the Payload of Sync. Messages in RWB’s Message monitoring.

Finally, let’s verify if the configurations worked.

image

We now are able to see another selection in the dropdown that can let us view the payload of the message.

image

Conclusion:

Viewing the payload of Sync Messages in the Message monitoring of RWB offers almost (not) all features of SXMB_MONI when processing messages locally in the AAE. We should certainly leverage it!

To report this post you need to login first.

7 Comments

You must be Logged on to comment or reply to a post.

  1. Sudharshan Aravamudan
    Hi,

    Superb piece of information. We were in dire need of this functionality.

    Does this setting have an impact on the performance gain of the AAE Processing.

    Thanks.
    ~Sudharshan N A

    (0) 
    1. Hanish John Post author
      Thank you Sudharshan,
      Changing the default parameter would definitely impact the performance, but to answer to your point “impact on the performance gain of the AAE Processing.”, I would say that the performance gain (4 fold ) is still much higher than the adverse effect of changing this default parameter, In terms of numbers – I am yet to roll out this approach on a larger scale to compare throughput.

      Hanish John

      (0) 
  2. Kenny Scott
    this may be required for business reasons or performance analysis but it should be noted that performance will be adversely affected by changing this value from the default
    (0) 
    1. Hanish John Post author
      Kenny,
      I agree, what other alternative do I have out of the box, if I decided to choose local processing of messages in the AAE?

      Hanish John

      (0) 
      1. Kenny Scott
        Hi John,
        if you need to view the synchronous message payload then that is the way to do it but the trade-off is the performance deterioration.

        Regards

        Kenny

        (0) 
  3. Woo-Je Chun
    Nice article… I wish I had read this earlier.

    In high volumn, this configuratio change result in more frequent OOM in adapter. So, you need to be carefule with this.

    Thanks

    (0) 

Leave a Reply