Disable logging & tracing for a specific scenario

[Former Member]

Hello XI experts,

we have a new synchronous scenario where we exchange very sensitive payload. It is a requirement that some of the payload must not be stored anywhere, including logs. With SAP XI, every message's payload appears in SXMB_MONI and also in the message monitoring in RWB.

Is there any way we can disable persistence & logging just for this scenario so that the messages do not appear in SXMB_MONI nor in RWB nor anywhere else? Running processes must not be affected, so it's not an option to turn off persistence & logging completely.

Any help is appreciated!

Best regards,

Matthias

[Former Member]

Matthias

I am working on several highly sensitive interfaces for a third party.

Access is heavily restricted and we have all had to sign Non-Disclosure Agreements before starting work.

You may not be able to restrict access to sxmb_moni, but the Runtime Workbench holds this information, and has full aduit log.

[Former Member]

Hello all,

thanks for your answers. We were already aware of these options, but unfortunately this won't be enough. Some of the data must not be stored anywhere, even in encrypted form.

The online help for XI Logging & Tracing under http://help.sap.com/saphelp_nw04/helpdata/en/d6/49543b1e49bc1fe10000000a114084/frameset.htm mentions the possibility to set the parameter <SAP:Logging> in the message header in order to activate or deactivate explicitly the logging. Has someone experience with this?

Thanks in advance!

Best regards,

Matthias

[Former Member]

hey , why not remove the "logging" from the runtime category in the integration engine configuration (sxmb_adm)?

Message was edited by:

Raghavendra K.B

[Former Member]

Hello Raghavendra,

this would disable Logging for all processes...as I already said, the other processes must not be affected.

Regards,

Matthias

[Former Member]

Fueller,

You can go for message level security. Check this document on how to do this:

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b2e7020d-0d01-0010-269c-a98...

If this doesnot work for you then you can restrict access to the message in sxmb_moni. Check this michals weblog for this:

/people/michal.krawczyk2/blog/2006/01/02/xi-sxmbmoni--controlling-access-to-message-display

Also check these threads for some more information on this:

Regards,

---Satish

[Former Member]

Hi,

It is not possible to stop tracing and logging for a particular scenario.

In your case, you can use authorization objects concept of SAP XI to hide or restrict access to the payloads in SXMB_MONI and you can use XOR encoding/decoding of the message to encode it so that it is not visible in the runtime work bench. This is the approach that we have implemented successfully in our project.

You will have to write a java mapping for encoding and then use it in the interface mapping and in the adapter modules, you can use the decoding part (has to be a bean) of it to decode it and send it to the call adapter bean.

reward if helpful,

Sarath.