Target payload is truncating file(XML) to proxy scenario

[Former Member]

Hi Experts,

We have a scenario file to proxy.

Here we are using XML file and Size of the Incoming file is around 20 MB.

Initially we had an issue of truncating the tail end records there we have increased the heap memory in the development landscape and tested, file has been successfully processed. Later we have applied the same to quality and production systems we have seen a successful execution we thought problem got resolved.

But from the past days again receiver pay load started truncating in the tail end records(but successful execution no fail in the message SXMB_MONI).

This time we are thinking of avoiding the issue permanently.

Could you please provide your valuable inputs/recommendations to achieve?

Note:

If there is any best way to change the design to achieve we will welcome to change the design.

But the situation is we have to send the pay load at one shot to the target.

Helpful solution will be highly appreciated.

Thanks in advance...

Regards,

Srihari.

[nabendu_sen]

Hi Srihari,

Do you have any job for Archiving and Deletion of messages?

Otherwise use Recordset per message option to minimize the message size in your adapter.

Please also go through the below Blog:

PI/XI: PI 7.3 processing of large files - teaser

[Former Member]

Adding to my original post, currently we are using PI 7.3 version.

So any advanced options available in PI 7.3 to achieve this issue?

Regards,

Srihari.

[Former Member]

I'm not sure this is your problem - but maybe the PI tries to read the file in the middle of its writing? (as the file is 20MB in size - this can take a while...)

try using the advanced option of Msecs to wait before modification check.

If PI checks and the size is not the same - it will wait and sample again later.

when the size stays the same during 2 checks - only then it will take the file.

regards,

Imanuel Rahamim.

[Former Member]

Hi Imanuel Rahamim,

Thanks for your response,

In our situation we are able to get the pay load from the source system.

But while sending the payload from PI to target system we are facing the issue.

Correct me if I am wrong, sender CC has a capability to get the complete payload.

Where as in PI internally pay load is truncating.

Am I right?

Regards,

Srihari.

[former_member192851]

Any errors on receiver side?

Maybe payload truncating on receiver side.

Sxmb_moni in the receiver tells that everything is ok?

[Former Member]

As Artem told you - it is a simple matter of checking in sxmb_moni.

look at the message payload (MainDocument) part after the mapping.

is the payload ok there?

Also - if you want to make sure, make a test and save the file in a different folder and see if the payload is ok.

As Artem told you - it might be the receiver that is reading the file before you manage to write it completely.

Regards,

Imanuel Rahamim.