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 » MIME parser works differently for MQInput and HttpInput node

Post new topic  Reply to topic
 MIME parser works differently for MQInput and HttpInput node « View previous topic :: View next topic » 
Author Message
patodiay
PostPosted: Fri Jun 07, 2013 12:44 am    Post subject: MIME parser works differently for MQInput and HttpInput node Reply with quote

Newbie

Joined: 06 Jun 2013
Posts: 2
Am facing an issue while parsing a MIME message by HTTPInput node .
A MIME message being sent to a HTTPInput node gets parsed incompletely (the individual part level headers do not get parsed appropriatly).
Noteworthy, the same message when posted via a MQ input node is parsed completely.
I observed this behavior in MWB 7.0.0.0 and v8 both.

Below is the corresponding tree that gets generated in debug mode after parsing the same message .
Note: If the input is received from MQInput node the Part level header/payload are segrregrated but if the msg is recieved by HTTPInput node the Parts.Part[*].BLOB.BLOB
contains the header & payload values both.
I am looking for a solution by which the httpinput node parses the message properly. Can someone please help me .
Thanks


***********************************
MSG POSTED IN HTTP INPUT NODE
***********************************
Message
Properties
MessageSet:CHARACTER:
MessageType:CHARACTER:
MessageFormat:CHARACTER:
Encoding:INTEGER:546
CodedCharSetId:INTEGER:1208
Transactional:BOOLEAN:false
Persistence:BOOLEAN:false
CreationTime:TIMESTAMP:java.util.GregorianCalendar[time=1370570417393,...DST_OFFSET=?]
ExpirationTime:INTEGER:-1
Priority:INTEGER:0
ReplyIdentifier:BLOB:[B@fbc0fbc
ReplyProtocol:CHARACTER:SOAP_HTTP
Topic:UNKNOWN:null
ContentType:CHARACTER:Multipart/form-data; boundary=XbCY
IdentitySourceType:CHARACTER:
...
IdentityMappedIssuedBy:CHARACTER:
HTTPInputHeader
X-Original-HTTP-Command:CHARACTER:POST http:/*localhost:7080/abc HTTP/1.1
Accept-Encoding:CHARACTER:gzip,deflate
Content-Type:CHARACTER:Multipart/form-data; boundary=XbCY
User-Agent:CHARACTER:Jakarta Commons-HttpClient/3.1
Host:CHARACTER:localhost:7080
Content-Length:CHARACTER:476
X-Remote-Addr:CHARACTER:127.0.0.1
X-Remote-Host:CHARACTER:127.0.0.1
X-Server-Name:CHARACTER:localhost
X-Server-Port:CHARACTER:7080
X-Scheme:CHARACTER:http
MIME
Content-Type:CHARACTER:Multipart/form-data; boundary=XbCY
Parts
CHARACTER:MIME-Version: 1.0
Content-Type: Multipart/form-data; boundary=XbCY
Part
Data
BLOB
BLOB:BLOB:[B@2a462a46
Part
Data
BLOB
BLOB:BLOB:[B@2c942c94
Part
Data
BLOB
BLOB:BLOB:[B@2ede2ede
Part
Data
BLOB
BLOB:BLOB:[B@312e312e


***********************************
MSG POSTED IN MQ INPUT NODE
***********************************

Message
Properties
MessageSet:CHARACTER:
MessageType:CHARACTER:
MessageFormat:CHARACTER:
Encoding:INTEGER:546
CodedCharSetId:INTEGER:437
Transactional:BOOLEAN:true
Persistence:BOOLEAN:false
CreationTime:TIMESTAMP:java.util.GregorianCalendar[time=1370570575530,...,DST_OFFSET=?]
ExpirationTime:INTEGER:-1
Priority:INTEGER:0
ReplyIdentifier:BLOB:[B@36e036e
ReplyProtocol:CHARACTER:MQ
Topic:UNKNOWN:null
ContentType:CHARACTER:Multipart/form-data; boundary=XbCY
IdentitySourceType:CHARACTER:
IdentitySourceToken:CHARACTER:
...
IdentityMappedIssuedBy:CHARACTER:
MQMD
SourceQueue:CHARACTER:IN
Transactional:BOOLEAN:true
Encoding:INTEGER:546
CodedCharSetId:INTEGER:437
Format:CHARACTER:
Version:INTEGER:2
Report:INTEGER:0
MsgType:INTEGER:8
Expiry:INTEGER:-1
Feedback:INTEGER:0
Priority:INTEGER:0
Persistence:INTEGER:0
MsgId:BLOB:[B@19a019a0
CorrelId:BLOB:[B@1a481a48
BackoutCount:INTEGER:0
ReplyToQ:CHARACTER:
ReplyToQMgr:CHARACTER:QMD01
UserIdentifier:CHARACTER:248499
AccountingToken:BLOB:[B@1e4a1e4a
ApplIdentityData:CHARACTER:
PutApplType:INTEGER:11
PutApplName:CHARACTER::\softwares\ih03\rfhutil.exe
PutDate:DATE:java.util.GregorianCalendar[time=1370543400000,...,DST_OFFSET=?]
PutTime:TIME:java.util.GregorianCalendar[time=-62167471024470,...DST_OFFSET=?]
ApplOriginData:CHARACTER:
GroupId:BLOB:[B@26362636
MsgSeqNumber:INTEGER:1
Offset:INTEGER:0
MsgFlags:INTEGER:0
OriginalLength:INTEGER:-1
MIME
MIME-Version:CHARACTER:1.0
Content-Type:CHARACTER:Multipart/form-data; boundary=XbCY
Parts
Part
Content-Disposition:CHARACTER:form-data; name="PayloadType"
Data
BLOB
BLOB:BLOB:[B@33d033d0
Part
Content-Disposition:CHARACTER:form-data; name="ProcessingMode"
Data
BLOB
BLOB:BLOB:[B@37043704
Part
Content-Disposition:CHARACTER:form-data; name="PayloadID"
Data
BLOB
BLOB:BLOB:[B@3a263a26
Part
Content-Disposition:CHARACTER:form-data; name="TimeStamp"
Data
BLOB
BLOB:BLOB:[B@3d4e3d4e

***********************************
Code:
[url][/url]
Back to top
View user's profile Send private message
McueMart
PostPosted: Fri Jun 07, 2013 12:51 am    Post subject: Reply with quote

Chevalier

Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
Have you tried with the latest fixpacks (7.0.0.5 / 8.0.0.2) ? That should be your first course of action.
Back to top
View user's profile Send private message
exerk
PostPosted: Fri Jun 07, 2013 1:40 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339
Moving this to the Broker forum...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Fri Jun 07, 2013 5:41 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447
It sounds as if the MIME parser is only parsing those fields it needs to, until some demand is made for it to parse other fields...

as if it was an On Demand parser...
Back to top
View user's profile Send private message
AkankshA
PostPosted: Fri Jun 07, 2013 6:22 am    Post subject: Reply with quote

Grand Master

Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
just a quickie Have you set the Message Domain to MIME in HTTPInput node?
_________________
Cheers
Back to top
View user's profile Send private message Visit poster's website
patodiay
PostPosted: Sun Jun 09, 2013 10:01 pm    Post subject: Reply with quote

Newbie

Joined: 06 Jun 2013
Posts: 2
mqjeff - the behaviour is same even with other other 2 parse options.
AkankshA - Yes I did set the parser to MIME, thus was able to get the MIME tree. My point of focus is 'difference' in the way, the MIME parser behaves with MQInput and HttpInput node.

Thanks
Back to top
View user's profile Send private message
arunkumar1989
PostPosted: Mon Oct 28, 2013 11:39 pm    Post subject: Differences...! Reply with quote

Voyager

Joined: 21 Nov 2012
Posts: 98
Location: Chennai
Difference between MQ , HTTP and SOAP Protocols.
_________________
Being in a crowd when you are alone is ignorance. Enlightenment is being alone in a crowd; a feeling of oneness in a crowd.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MIME parser works differently for MQInput and HttpInput node
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.