ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MTOM Issue - more than 1 attachment

Post new topic  Reply to topic
 MTOM Issue - more than 1 attachment « View previous topic :: View next topic » 
Author Message
ata_nitjsr
PostPosted: Wed Feb 08, 2012 12:02 am    Post subject: MTOM Issue - more than 1 attachment Reply with quote

Acolyte

Joined: 08 Apr 2007
Posts: 56

I need to pass more than one attachment as MTOM format through SOAP request node. I am able sucessfully pass 1 attachment. for more than one attachment I am geting some exception like

Quote:
The content of element 'AttachmentData64Binary' is not complete. One of '{"http://www.w3.org/2004/08/xop/include":Include}' is expected.


Code:


The part of xml is:-

<RequirementInfo id="RequirementInfo-0">
                  <ReqCode tc="655">Replaced Policy Funds</ReqCode>
                  <RequirementDetails>RoundRobin with attachment-manual test</RequirementDetails>
                  <ReqStatus tc="1">Pending</ReqStatus>
                  <DueDate>2012-02-14</DueDate>
                  <Attachment id="Attachment-0">
                     <DateCreated>2012-02-07</DateCreated>
                     <AttachmentBasicType tc="3">Attachment has a file Attached</AttachmentBasicType>
                     <AttachmentData64Binary>SGkgU2hhaXRr</AttachmentData64Binary>
                     <AttachmentType tc="65">759 Form</AttachmentType>
                     <MimeTypeTC tc="11">image/tiff</MimeTypeTC>
                     <TransferEncodingTypeTC tc="4">Base64 (binary)</TransferEncodingTypeTC>
                     <AttachmentLocation tc="5">XOP Include</AttachmentLocation>
                     <AttachmentHashValue>919ea91efeea78992aa38bea56da01113dae9ae3</AttachmentHashValue>
                     <AttachmentHashType tc="2">Secure Hash Algorithm 1</AttachmentHashType>
                  </Attachment>
                  <Attachment id="Attachment-1">
                     <DateCreated>2012-02-07</DateCreated>
                     <AttachmentBasicType tc="3">Attachment has a file Attached</AttachmentBasicType>
                     <AttachmentData64Binary>SGkgU2hhaXRr</AttachmentData64Binary>
                     <AttachmentType tc="1">Document</AttachmentType>
                     <MimeTypeTC tc="11">image/tiff</MimeTypeTC>
                     <TransferEncodingTypeTC tc="4">Base64 (binary)</TransferEncodingTypeTC>
                     <AttachmentLocation tc="5">XOP Include</AttachmentLocation>
                     <AttachmentHashValue>de0fd33e8d7935ff6f901f9cb8a3797224b14e41</AttachmentHashValue>
                     <AttachmentHashType tc="2">Secure Hash Algorithm 1</AttachmentHashType>
                  </Attachment>
               </RequirementInfo>


Please help [/quote]
Back to top
View user's profile Send private message
ata_nitjsr
PostPosted: Wed Feb 08, 2012 5:55 am    Post subject: Reply with quote

Acolyte

Joined: 08 Apr 2007
Posts: 56

still no solution

Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed Feb 08, 2012 6:17 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

We haven't exceeded the publiished SLA for this forum as yet.

Can you provide a section of the user trace that demonstrates this error?
Back to top
View user's profile Send private message
ata_nitjsr
PostPosted: Thu Feb 09, 2012 10:49 pm    Post subject: Reply with quote

Acolyte

Joined: 08 Apr 2007
Posts: 56

We have raised a pmr.
IBM told:-

I have researched and found IC74523 is an MTOM issue where the first attachment is treated properly but the 2nd is not.
IC74523: ONLY FIRST ATTACHMENT IS HANDLED AS MTOM WHEN ATTACHMENTS ARE IN ARRAYS.
When examining a SOAP message to look for elements suitable for
MTOM optimization, if there is an array of elements which match
the MTOM criteria then only the first element is added as a
MIME part. All other elements in the array are transmitted
inline within the outbound message.
The fix is included in fix for V6.1.0.10. You are running V6.1.0.8. You either can upgrade to V6.1.0.10 or if you would like I can request the fix for V6.1.0.8.


It looks like IBM has fixed this issue in the fix pack for 6.1.0.10.
Can you please take a look at the link
http://www-01.ibm.com/support/docview.wss?uid=swg1IC74523
Back to top
View user's profile Send private message
mqsiuser
PostPosted: Fri Feb 10, 2012 12:18 am    Post subject: Reply with quote

Yatiri

Joined: 15 Apr 2008
Posts: 637
Location: Germany

ata_nitjsr wrote:
We have raised a pmr.
IBM told:-

[...] is added as a MIME part.


What does MTOM give you over MIME? I am honestly curious (please someone explain me!)! It is just, that we have eMail since about 40 years, and someone implemented attachments properly for eMail and called it "MIME" - Multipurpose Internet Mail Extensions. And then the Web came along in 1991 and picked up this standard (even though it is called something with (e)Mail)... and then WebServices came along (2002) and all of a sudden we debate over how to attach things (again)?! You can use MIME with webservices (afaik) and I bet, that this will prevail because of maturity!

And do not come with that MIME is not xml or that you would need something else (than MIME) to encrypt the content.

The big upside of MIME is that it is all over the place: You use it in eMails and on the WWW (HTTP-downloads).... does it annoy anyone there ? - NO !

Wikipidia on the Benefits of MTOM wrote:
The efficiency claims of MTOM only refers to the size of the messages sent across the wire. Since SOAP uses XML, any binary data in the SOAP message will have to be encoded as text. This is usually done using Base64 encoding which increases the size of the binary data by 33%. MTOM provides a way to send the binary data in its original binary form, avoiding any increase in size due to encoding it in text. MTOM does not address the efficiency of serializing or deserializing the messages.


I like that they write "the efficiency claims of MTOM only" and "does not address the efficiency of serializing or deserializing". I tell you now that MIME uses base64 and in the wiki-snipped it says that "this increases the size of the attachment by 33%"... well, so what ?!... that is a fair trade for having something which is well understood (since 40 years) and actually working. I mean something that uses XML (WebServices!) complains somewhere else about waisting bits ?!

Binary data is transformed into readable characters, which are code page independent (base64) for easy transmission (and editing/debugging) at the sake of 33% bloat. Thats reasonably fair!
_________________
Just use REFERENCEs
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MTOM Issue - more than 1 attachment
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.