Testing of very large XML payload

[Former Member]

Hi there

I have this extremely huge XML document about 100MB in size which falls over due to a mapping issue. I'd like to know is there an easier way to load this payload in the message mapping testing tool? If I paste or import the payload the whole system freezes.

Thanks,

Jan

[Former Member]

Hi Lange,

Notepad has certain limitation. So if you put in notepad or in message mapping test it will freeze. The best option in your case is to test end to end only.

Regards,

---Satish

[Former Member]

Good Day

I have tried several places and techniques to test the mapping with an un-usually large payload. The results are the same for every test. So yes the only way to debug some issue in a payload of this size would be the message monitoru2019s trace. Itu2019s just a shame that the message monitor is so inaccurate. Or at least there is just so little descriptive information regarding the specific issue. Maybe SAP will update their testing tools in the next XI release.

Regards,

Jan

[Former Member]

Hi Jan,

100 megs is a lot of data for Message Mapping to handle. Try to test the mapping with max of 1 meg record.

Test in Message mapping is designed to validate the mapping and whether the target structure is coming up as desired. It is not suitable for a stress testing.

Cheers'

Neetesh

[former_member192295]

Hi,

In Mapping window testing tab we can test complete data idoc. First copy idoc data between <idoc> to <idoc/> tags and past into mapping window test tab <idoc> to <idoc/>. After that we can do testing. But meanwhile in moni window trace tab first check what is the error, we can sort out esily.

[Former Member]

Hi Jan,

I guess the total 100 MB XMl file is made up of multiple records. If so, then copy paste a 100-1000 records at a time and then test it.

You just need to alter the XML source code in IR by adding the </root> node of the XML.

Another important thing to help such cases is "Trace" Use the trace node in SXMB_MONI and try to narrow down the possibility of the error. You can even increase the Trace level to debug (I hope this is non productive system)

Regards

Jai

[prateek]

Have you also tried RWB -> Component Monitoring -> Adapter Engine -> Test Message?

Regards,

Prateek