Hi @mft
Setting the Content-Type to application/xml must ensure that the input is treated as an XML, and based on the watt property for xmlFormat you should be getting one of the following possible values - node, xmlStream, xmlBytes.
If you are getting contentStream, then it appears that the HTTP header is somehow not reaching the Integration Server.
Next steps:
-
To confirm, I would suggest you increase logging. Set the facility for HTTP Header ( 0038 ) to Trace in the server logging and retrigger the postman request. Then check the server logs. This should confirm if the Content-Type header reaches as expected.
-
You could also try with a different client to compare.
-
If the header is correct, then please check if you are on the latest core fix levels for 10.3. If you are still getting this error, then this is a bug, and I would suggest you raise a support ticket.
-
If you have access to newer versions of the Integration Server you could also try to repro the scenario in the newer versions.
Note: you may want to reset the facility back to Info again, since there will be a lot of logging generated logging headers for every request.
-NP
#rest-call#node#webMethods#Integration-Server-and-ESB