Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.
Hello Team,
I am trying to implement MTOM compression for attachments which are sent via webservices. I try to read a file convert it into bytes and pass the same to base64Encoding service.
However, I dont see any option in webMethods 8.0.1 version to how to enable MTOM compression and the documentation for the same is fuzzy at the best.
Has anyone ever tried MTOM compression before or is there another way to do it? Any help is appreciated.
Have not you checked WmWebServicesSamples . I think there is MTOM help.
Hello Suresh, Hope you are good!!! Thanks for the tip, will check it.
Hello , I tried the example in the package. Its getting errord out saying
[ISS.0088.9133] Error while encoding RPC output
java.lang.NullPointerException
anything missing in the configuration perspective?
<SOAP-ENV:Envelope xmlns:SOAP-ENV=“http://www.w3.org/2003/05/soap-envelope” xmlns:SOAP-ENC=“http://www.w3.org/2003/05/soap-encoding” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance” xmlns:xsd=“XML Schema”> SOAP-ENV:Body SOAP-ENV:Fault SOAP-ENV:Code SOAP-ENV:ValueSOAP-ENV:Sender</SOAP-ENV:Value> </SOAP-ENV:Code> SOAP-ENV:Reason <SOAP-ENV:Text xml:lang=“”>[ISS.0088.9133] Error while encoding RPC output</SOAP-ENV:Text> </SOAP-ENV:Reason> SOAP-ENV:Rolehttp://hostname:5555/ws/poc.webService.Provider:provideMTOMServices/POC_webService_Provider_provideMTOMServices_Binder</SOAP-ENV:Role> <SOAP-ENV:Detail xmlns:webM=“API Integration Platform | Software AG”> webM:exception webM:classNamejava.lang.NullPointerException</webM:className> <webM:message xml:lang=“”/> </webM:exception> </SOAP-ENV:Detail> </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope>
[ISS.0088.9133] Error while encoding RPC output. Cause: The message coder could not XML?encode the parameters associated with a SOAP remote procedure call. Response: See the detail element in the SOAP fault for information about the specific failure that occurred
SCG_7-1-2_G11N_Fix2 Or