Boomi Tip: Attachment Cache

Boomi has introduced a new feature in the Web Service SOAP framework, called Attachment Cache. This feature allows you to post a SOAP request envelop together with an attachment data in a multipart MIME format. This is often useful if the endpoint application handles the SOAP message data and the attachment data separately. To use this feature, you will just need to configure the document cache to be used in the SOAP Client operation in Boomi

Below is the sample on how the SOAP message looks like when the Attachment Cache is enabled in the SOAP operation:

POST /ws/soap HTTP/1.1
Content-type: multipart/related;start="<rootpart*eea27dfe-0b97-4da8-a3a4-d639a66e9b50@example.jaxws.sun.com>";type="application/xop+xml";boundary="uuid:eea27dfe-0b97-4da8-a3a4-d639a66e9b50";start-info="text/xml"
Soapaction: "createOpAtt"
Accept: text/xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
User-Agent: JAX-WS RI 2.1.5-b03-
Host: wdci-milo:9090
Content-Length: 786

--uuid:eea27dfe-0b97-4da8-a3a4-d639a66e9b50
Content-Id: <rootpart*eea27dfe-0b97-4da8-a3a4-d639a66e9b50@example.jaxws.sun.com>
Content-Type: application/xop+xml;charset=utf-8;type="text/xml"
Content-Transfer-Encoding: binary



        Test

--uuid:eea27dfe-0b97-4da8-a3a4-d639a66e9b50
Content-Id: 
Content-Type: text/xml; name="824bd8d5-0337-402e-98c8-50136d645c58"
Content-Transfer-Encoding: binary

Test
--uuid:eea27dfe-0b97-4da8-a3a4-d639a66e9b50--