Handling Multipart or Form Data
As a provider, you can have a native SOAP service that expects attachments in the SOAP body. The REST call to this service must be of type, multipart/form-data. The service can use any optimization technique (MTOM or SwA) based on the SOAP Optimization Method Endpoint Properties parameter configuration of the Straight Through Routing action in CentraSite.
Mediator uses the following rules to convert a multipart/form-data request to a request with SOAP attachments:
If the
multipart/form-data request contains an
application/json part, the JSON part is converted to SOAP and added to the body of the outgoing request.
If the request does not have an
application/json part,
Mediator checks for an
application/xml part and adds it to the SOAP body of the outgoing request.
If no
application/json or
application/xml parts are found in the request, an empty SOAP body with the operation element alone is added to the outgoing request.
If more than one
application/json or
application/xml parts are found in the request, the first part is taken and processed. The remaining parts are sent as attachments to the outbound requests.
