XML Length Limit

[#1]

Hi Experts:

I wonder is there any limit of XML length during PI interface processing.

I have an RFC-PI-SOAP interface which transports a large table that over 60M. Since the interface was triggered by an external system, there is no such an operation like dividing the table into small entity for several times of sending. I also found out the max request size of ICM http in our PI and SAP system is 100M, which is totally larger than the table data.(Learning from Max XML length of XI)

However, when the external system request for the table data, they got an error like: 'XML document structure must start and end within the same entity' or 'element type must be terminated by the matching end-tag',

which apparently shows the end part of the xml data was missing.

Please give me some advice to solve this problem, thanks so much.

[former_member607993]

Hi Joy,

Since integration is moving to Cloud Platform- CPI which could be better option in handling these large volume files 🙂

Coming to PI if a large file size is processed it is considered a Long running job and creates a heap dump and SOAP Threads gets occupied with maximum and message gets stucked with status 'Delivering' or 'To be delivered'.

To avoid these kind of issues there is methods to handle for example: additional java server nodes for parallel processing, web dispatcher for load balancing, single queuing(max parallelism receiver) with doesn't impact other SOAP related interfaces, dedicated Decentral PO engine to handle high payload messages etc.

You can test the scenario in Pre-production with request file size of 10M and increase gradually(<50M). Also it is based upon your database, hardware, application memory as well.

Note: I'm expecting valuable suggestion from other experts as well. Thank you 🙂

Thanks and Regards - Rajesh PS

[Former Member]

Hi Rajesh,

It's really nice to see your advice, I'll try to comprehend CPI if I got time and chance(Actually I am an ABAP developer).
As for my problem, we give the same interface to other WS Consumer for testing the error, and it turns out that all other WS Consumer getting the right response, everything works fine.So we believed that the problem isn't on the SAP PI side or ECC side.

Still very grateful for your answer 🙂