We are using XI 3.0/PI 7.0 here, I think it's either SP 15 or 25, SAP_BASIS has SP 25, PI_BASIS has SP 15.
We have the need to send uncode characters inside IDOC's from our SAP sytem to another non-SAP system. From SAP to XI is IDOC's - from XI to the remote system is SOAP.
The SAP to XI part appears to be fine. The data shows up and we can see the data properly in both SXMB_MONI and SXMB_IFR's Runtime Workbench ( RWB ).
The part where we are having an issue is the XI to remote system end. It's defined as a SOAP adapter, transport protocol is HTTP, message protocol is SOAP 1.1, adapter engine is Integration Server".
We didn't understand at first what was going wrong ( and it's been going wrong for a long time, I recently was put in charge of supporting this ), so I enabled error logging. Whenever an invalid character got sent, here's what we get as an error as follows ( some parts changed for security reasons ) in blue
Alert ID: ##46411##
Error: : The sender of the concerned message is <SENDER>.
The erronous message belongs to <interface name> interface to interface.
The receiver service of this message is .
The Adapter type used for this message is SOAP and the error reported by the adapter is SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML .
Use transaction SXMB_MONI in the XI System to see the erronous transaction.
Possible Subsequent Activities
Message Monitor <some long IP address for RWB>
Message Monitor (Secure Connection) <some long secure IP address for RWB>
Communication Channel Monitoring on <development system ID>
What we tried to do for this was to be very sneaky and add CDATA to the fields. That got rid of the above, but then the adapter engine decided to take revenge on us and convert our leading and trailing < and > to < and > thus ruining the idea
I have been told to update to PI 7.1, but currently that is not possible.
Anyone have any idea how to do this? I'm open to writing some code to fix this and the CDATA trick would have worked