XI/PI: Personalized logging & tracing

[MichalKrawczyk]

If you follow any standard XI best practices one of them will for sure be: Turn off logging of sync messages
on your production server!...also don't use Trace Level = 3!

Reminder:

If you want to find out how to turn it on (or off) have a look at my weblog:
XI: I cannot see some of my messages in the SXMB_MONI

But the question some of you may ask yourself is: is there any way I can log my message
without changing the global parameter LOGGING_SYNC ? As you probably can imagine - there is a standard way.
You can use Error Analisys Settings to do that. You can access them via transaction SXMB_ADM

Example:

Step 1

I disabled LOGGING_SYNC paramter on my XI server. As you see the logging is swiched off.
(the reason why I see this message in SXMB_MONI is that is has a mapping error)



Step 2

Next we can open Error Analisys Settings and create a condition for which logging will be swiched on.
In my case this will be username as I will start the message via http test HTML page and use my user.



As you see there are a few more options you can choose from.



Step 3

Next we need to choose an action - this is place where we can specify that our message needs to be logged.
When configuring your settings here remember to set expiry date so your rule will become inactive
if you forget to disactivate it youself.



Now when we run our flow we will see that he message was logged even though the LOGGING_SYNC parameter is not set.



Even though this is avery basic setting it's not very commonly used but if SAP gives us such tools why not use it ?

In one of my next blogs I will try to describe one more parameter (probably more intereting for those who like
ABAP debugging - and who doesn't) from those error settings - DEBUGSTRING