Hi All,
Our PI system is 7.31 SP15. We are facing a strange issue in our system for SOAP Sender Adapter with HTTP protocol.
The payload is getting corrupted while entering our PI system. Most often its the ending tag which gets corrupted. Due to this the Mapping step fails in PI. The source system is also PI system and the payload in the Source PI system is well formed. This does not happen to all messages and the behavior is not predictable. The issue cannot be replicated.
Payload in Our PI System: Additional characters after the end tag.
Payload in the source PI system: The ending tag is as expected.
We had a similar issue for another interface. It was again SOAP sender adapter and the message was coming from SAP system. Since the message flow in this case was very less we used the XML validation feature to reject the messages in PI and make it fail in the source system itself. When these failed messages were reprocessed from source system they were successfully processed in our PI system.
We are avoiding XML validation for the above interface since the message flow is very high.
Please provide your suggestions how to resolve this issue.
Regards,
Mohit Hosmani