Reading SOAP attachment in Sonic ESB

Posted by chetanparekh on 28-Oct-2010 00:48

We have a requirement where SonicESB process will invoke external Web Service. This external Web Service will return SOAP response having CSV file an attachment.
How to read SOAP attachment in Sonic ESB?

Technology Partner - Forum

All Replies

Posted by Bill Wood on 29-Oct-2010 12:52

MTOM support for SOAP was added in Sonic 8.0.  Check the documentation for Sonic Connect and MTOM.

Posted by chetanparekh on 01-Nov-2010 00:42

Thanks Williams for replying. We are going to use v7.6.2. Does it supports MTOM?

Posted by tsteinbo on 01-Nov-2010 10:48

7.6 does not support MTOM, but Soap with Attachements, e.g the broker is able to send and receive multipart messages using the HTTP Direct for SOAP protocol handler.

Thomas

Posted by chetanparekh on 03-Nov-2010 07:24

Thanks Thomas!

Posted by chetanparekh on 08-Nov-2010 03:01

Is HTTP Connect a separate application? Does it included with Sonic Workbench license?

Posted by Bill Wood on 08-Nov-2010 03:16

chetanparekh wrote:
Is HTTP Connect a separate application? Does it included with Sonic Workbench license?


There are two things referred to in the responses... Sonic Connect, and HTTP Direct.  There is no "HTTP Connect"

Sonic Connect is the new Web Service and RESTful Service connector that is available in Sonic ESB 8.0.  It provides direct access to and from ESB Processes without going to a Broker Acceptor, and also supports new SOAP-related specifications (MTOM, SOAP 1.2, etc) and REST.

HTTP Direct is the term used for the HTTP protocol acceptors on a Sonic MQ messaging broker, and is the same in versions of SonicMQ and Sonic ESB (v6.x, v7.x, v8.x).  In thomashe above case, Thomas was recommending using the HTTP Direct Basic acceptor and processing the XQMessage manually.  In this case, the HTTP message with attachments would convert to multipart JMS message with the SOAP part as Part[0] and attachments as following parts.

Neither HTTP Direct Basic, nor Sonic Connect, are licenced separately from Sonic ESB.  That is, they are included with the runtimes of the product (which are in turn included in Sonic Workbench).

This thread is closed