| Author |
Message
|
| pottas |
 Posted: Wed Jan 16, 2013 4:58 am Post subject: Soap with Attachment |
 |
|
Disciple
Joined: 27 Oct 2005
Posts: 185
Location: South Africa
|
Guys, some details of my setup, we are running the following Broker version/configuration:
WebSphere Message Broker Toolkit - Message Broker
Version: 7.0.0.2
Build id: 7.0.0.2-20101130_1524
I have a new project coming my way where they want to send me a Soap message with Attachment. Never done a configuration like this before 
So, I thought, before the project really kicks off, let me see how easy (or difficult) this is...
I created a simple sample flow in Message Broker, SOAPInput --> Compute (OutputRoot = InputRoot) --> SOAPReply
I use Soap-UI to test to my sample flow. Without an attachment, it goes through fine (as expected), but then I tried attaching a simple text file to the Soap-UI input message.
But here is where I am stuck, it doesnt even parse my input message, in the debugger, it just displays 'problem creating SOAP tree from bitstream'.
So, is there something specific I need to set on my SoapInput Node, or perhaps something in the Input Message Header I need to set, etc?
I am missing something here, but I am not sure what exactly it is.
Please help.
Thanks in advance. |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Wed Jan 16, 2013 5:35 am Post subject: Re: Soap with Attachment |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| pottas wrote: |
Version: 7.0.0.2
Build id: 7.0.0.2-20101130_1524
I am missing something here, but I am not sure what exactly it is.
|
They call it a FixPack.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Jan 16, 2013 5:39 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| in the debugger, it just displays 'problem creating SOAP tree from bitstream' |
The message flow debugger is not the only way to diagnose problems. Please try a little harder to do the basics before posting a question on this forum. |
|
| Back to top |
|
|
| mgk |
| Posted: Wed Jan 16, 2013 5:40 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hi,
The Broker certainly handles SOAP With Attachments (SwA) inbound and outbound. For inbound there is no configuration required - the SOAPInput node simple places the attachments that have arrived into the SOAP Domain Tree as BLOBs for use within the flow. This article covers some of the details: http://www.ibm.com/developerworks/webservices/library/ws-soapnode2/index.html
If you still get problems, try posting what SOAP UI is sending on the wire including the HTTP Headers...
Kind regards.
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| pottas |
| Posted: Wed Jan 16, 2013 5:53 am Post subject: |
|
|
Disciple
Joined: 27 Oct 2005
Posts: 185
Location: South Africa
|
Thanks MGK for your valuable and useful response, I will read through all the info to get a better understanding of all of this.
I will try and get something from the IBM site that might be a example or a tutorial specifically related to SwA. |
|
| Back to top |
|
|
| visasimbu |
| Posted: Wed Jan 16, 2013 5:58 am Post subject: Re: Soap with Attachment |
|
|
Disciple
Joined: 06 Nov 2009
Posts: 171
|
| pottas wrote: |
So, is there something specific I need to set on my SoapInput Node, or perhaps something in the Input Message Header I need to set, etc?
I am missing something here, but I am not sure what exactly it is.
Please help.
Thanks in advance. |
Did you got chance to check the MIME parser ?
Hope this parser will help you to implement your requirement.
Last edited by visasimbu on Wed Jan 16, 2013 6:04 am; edited 1 time in total |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Jan 16, 2013 6:01 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| I will read through all the info to get a better understanding of all of this |
That's a useful thing to do. However, your first problem is that you don't know why the input message did not parse successfully.
You can obtain the full text of the error message from the Windows Event Viewer ( if on Windows ) or by taking a user trace. It is likely to be a lot more useful than the single-line summary that the debugger displays. |
|
| Back to top |
|
|
| mgk |
| Posted: Wed Jan 16, 2013 6:45 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
| Quote: |
Did you got chance to check the MIME parser ?
Hope this parser will help you to implement your requirement. |
Not with the SOAP nodes - they only use the SOAP parser. Also, they handle SwA automatically - the MIME parser only makes sense if using the HTTP nodes...
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| visasimbu |
| Posted: Wed Jan 16, 2013 10:40 am Post subject: |
|
|
Disciple
Joined: 06 Nov 2009
Posts: 171
|
| mgk wrote: |
| Quote: |
Did you got chance to check the MIME parser ?
Hope this parser will help you to implement your requirement. |
Not with the SOAP nodes - they only use the SOAP parser. Also, they handle SwA automatically - the MIME parser only makes sense if using the HTTP nodes... |
Hi mgk,
I didnt get the chance to create the working model of SwA using MIME parser in SOAP node.
But I got the chance to read about MIME parser.
SOAP tree view also contains MIME headers. |
|
| Back to top |
|
|
| kash3338 |
| Posted: Thu Jan 17, 2013 5:29 am Post subject: |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| visasimbu wrote: |
But I got the chance to read about MIME parser.
SOAP tree view also contains MIME headers. |
The same link posted above suggests this piece of information,
| Quote: |
Typically, the MIME parser handles the majority of uses of MIME in application-to-application messaging, including multipart MIME with a single part and non-multipart MIME documents. However, you should use the SOAP domain for SOAP with Attachments (SwA).
|
|
|
| Back to top |
|
|
| visasimbu |
| Posted: Thu Jan 17, 2013 8:53 am Post subject: |
|
|
Disciple
Joined: 06 Nov 2009
Posts: 171
|
| kash3338 wrote: |
| visasimbu wrote: |
But I got the chance to read about MIME parser.
SOAP tree view also contains MIME headers. |
The same link posted above suggests this piece of information,
| Quote: |
Typically, the MIME parser handles the majority of uses of MIME in application-to-application messaging, including multipart MIME with a single part and non-multipart MIME documents. However, you should use the SOAP domain for SOAP with Attachments (SwA).
|
|
Thanks for highlighting the information.  |
|
| Back to top |
|
|
| goffinf |
| Posted: Thu Jan 17, 2013 10:19 am Post subject: |
|
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
| visasimbu wrote: |
| kash3338 wrote: |
| visasimbu wrote: |
But I got the chance to read about MIME parser.
SOAP tree view also contains MIME headers. |
The same link posted above suggests this piece of information,
| Quote: |
Typically, the MIME parser handles the majority of uses of MIME in application-to-application messaging, including multipart MIME with a single part and non-multipart MIME documents. However, you should use the SOAP domain for SOAP with Attachments (SwA).
|
|
Thanks for highlighting the information. |
It is a good idea to use the SOAP nodes when using SwA but it certainly isn't essential. There is nothing special about SwA messages other than the first part must contain the SOAP message, with other parts holding the attachments. We don't use SOAP nodes but it's pretty easy to construct a compliant SwA message using the HTTP nodes and MIME. |
|
| Back to top |
|
|
|
|
