Detailed error message in sxmb_moni

[Former Member]

Hi guys,

is it possible to get detailed error information in sxmb_moni like the error information in the integration repository when using the test tag

sample error message in test tab

+ns0:ZMOZPRUCK_envelope_update/ns0:ZMOZZFZT_update[4]/ns0:dbTableName/ns0:access/ns0:SPRAS.+

in sxmb_moni the error message is truncated

sample

+During mapping com/sap/xi/tf/_JDBC_ZPRUCK_2_ZMOZPRUCK_envelope_u~ a RuntimeException occurred. com.sap.aii.utilxi.misc.api.BaseRuntimeException:RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:ZMOZPRUCK_en~</+

This will save myself for copy/paste the payload in the test tab. In case of big message the Java GUI of the ESR lacks and it is impossible to test the mapping with such big messages.

any suggestions on that?

Thanks

[Former Member · Accepted solution]

Hey

You can check the complete error messages in "Trace" option in sxmb_moni.

Thanks

Aamir

[markangelo_dihiansan]

Hi Jochen,

I agree with Aamir. As to the level of trace, this would entirely depend on the hardware your system is running. I suggest that you consult with your IT guys as they are most likely familiar of the impact this could cause when turning the trace on in production.

Hope this helps,

[Former Member]

Hi @ll,

thanks for this information.

For now I will keep trace level 0 and when the next mapping error occurs I will try to restart the message and in the upcoming popup I try to increase the trace level for getting the detailed error information in the trace section.

Kind regards

Jochen

[markangelo_dihiansan]

Hi,

Adding to what Aamir says,

You can see your LOGGING, TRACE settings in tcode SXMB_ADM. Trace Level '3' provides the most information but consumes the most system resource.

Hope this helps,

[Former Member]

Hi guys

thanks for sharing this information.

this trace level on our production system is 0 (disabled)

If an error occurs, during restart of the messsage the trace level could be increased temporarily, is that correct?

What trace level is recommended for production system?

Kind regards

Jochen

[Former Member]

Gugel,

Check this thread and the blog:

/people/michal.krawczyk2/blog/2005/05/10/xi-i-cannot-see-some-of-my-messages-in-the-sxmbmoni

Usually 1 should be good in prod.

Regards,

---Satish

[Former Member]

>>If an error occurs, during restart of the messsage the trace level could be increased temporarily, is that correct?

Yes,thats correct

Trace would be set to 0 so that the trace log files don't overload the Production syste it can affect performance of interfaces.

as you mentioned,you can increase it temporarily for any failed message and see if it gives you more information.

Thanks

Aamir