Well, actually the answer to the second question should be Yes as well…
You have several options:
-
In the HTTP POST just use a Content-Type that the IS does not know. A good choice would be application/octet-stream. The IS will then put the HTTP body into the pipeline as an Object of type java.io.InputStream with the name “contentStream” and you can read the contents in binary format from the stream. (Should not be much harder than working on a byte.)
-
If you can’t influence the HTTP client’s Content-Type, then you can “de-register” the Integration Server’s content handler for text/xml. Afterwards the IS will no longer “recognize” the Content-Type text/xml and will give you a “contentStream” object for that Content-Type as well.
All you need for this is a Java Service with the following code:
ServerAPI.removeContentHandler("text/xml");
(Under “Imports” add the line
com.wm.app.b2b.server.ServerAPI
)
and define this Service as a “Startup Service”, so it gets executed whenever the IS starts. However, be aware that the IS will then do no XML parsing of incoming requests anymore… 
Lanzelot
#webMethods#Integration-Server-and-ESB#webmethods-Protocol-and-Transport