PeopleTools and Lifecycle Management - PSFT (MOSC)

MOSC Banner

Sending MTOM SOAP message to integration broker is returning error MTOMUtility: getInputStringForMto

edited Oct 10, 2019 6:07PM in PeopleTools and Lifecycle Management - PSFT (MOSC) 3 commentsAnswered

Hello Everyone,

I'm trying to send a picture file as an attachment in a MTOM SOAP message, but the integration broker is returning this error:

MTOMUtility:getInputStringForMtomEnabledConnector : unable to extract MimeMultipart

The service is Asynchronous, message is non-rowset based and MTOM is enabled in the Gateway properties. The raw message im sending is this one, im using SOAP UI:

POST http://soter.eafit.local:8300/PSIGW/PeopleSoftServiceListeningConnector/PSFT_CS HTTP/1.1

Accept-Encoding: gzip,deflate

Content-Type: multipart/related; type="application/xop+xml"; start="<rootpart@soapui.org>"; start-info="text/xml"; boundary="----=_Part_10_26116430.1569332911262"

SOAPAction: "EA_PRUEBA_MTOM_ASYNC2.v1"

MIME-Version: 1.0

Content-Length: 2246

Host: soter.eafit.local:8300

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center