| Author |
Message
|
| anil kumar |
 Posted: Wed Sep 20, 2017 3:47 am Post subject: Input Messsage is getting striped |
 |
|
Voyager
Joined: 22 Jan 2017
Posts: 98
Location: India
|
Hi All,
i m facing a problem my flow looks like
MQINPUT ==>compute==>MQOUTPUT
\\
\\
ErrorHandler
input and output both are XML formats only, i have prepared schema for both input and output. i have some mandatory and option nodes in the inbound which are validated at MQinput with content and value validation.
the problem is when ever a mandatory element is missing in the input the mq input wil route the message to failure node.we have developed a mechanisam in Error log like when ever there is a failure in processing the flow error handler will generate a email with failure reason and original message as attachment,
but these days im getting the email with exception description and attachment but the Original message is getting trimmed to the place where validation failed.
the whole input message is missing when i wanted to look into the failure reason.
can any one suggest what was wrong with interface
ref :IBM integration bus 9.0.0.8
IBM WebSphere MQ Explorer Version: 7.5.0.1 |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Sep 20, 2017 6:17 am Post subject: Re: Input Messsage is getting striped |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| anil kumar wrote: |
| can any one suggest what was wrong with interface |
| anil kumar wrote: |
when ever there is a failure in processing the flow error handler will generate a email with failure reason and original message as attachment,
but these days im getting the email with exception description and attachment but the Original message is getting trimmed to the place where validation failed. |
By definition, the input message can't be completely parsed. So how exactly do you expect it to parse the complete message into an attachment?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| timber |
| Posted: Wed Sep 20, 2017 7:00 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| To avoid this problem, it is common practice to use a ResetContentDescriptor node to change the domain to 'BLOB' on the exception handler flow. |
|
| Back to top |
|
|
| hotshot |
| Posted: Thu Sep 21, 2017 2:53 pm Post subject: |
|
|
Novice
Joined: 04 Jan 2013
Posts: 20
|
| timber wrote: |
| To avoid this problem, it is common practice to use a ResetContentDescriptor node to change the domain to 'BLOB' on the exception handler flow. |
Is that something that can also be coded in ESQL/Java with PARSE/createLastChildFromBitstream ? |
|
| Back to top |
|
|
| anil kumar |
| Posted: Thu Oct 12, 2017 5:30 am Post subject: |
|
|
Voyager
Joined: 22 Jan 2017
Posts: 98
Location: India
|
we have completed this scenario with a set up like
MQ input>>RCD >>Validation node
that is validating the inbound message at the same time able to get the whole message as attachment.but this set up is throwing exception in a different way where as when validation enabled at Input node has thrown most obvious error where are at validation node it thrown a generic error. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Oct 12, 2017 8:43 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| anil kumar wrote: |
we have completed this scenario with a set up like
MQ input>>RCD >>Validation node
that is validating the inbound message at the same time able to get the whole message as attachment.but this set up is throwing exception in a different way where as when validation enabled at Input node has thrown most obvious error where are at validation node it thrown a generic error. |
Typically the RCD is the first thing on the Failure path. This way you go back to the input node, parsing is set to on demand and you have not yet parsed anything on the failure path. You should get the full message... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| anil kumar |
| Posted: Mon Oct 16, 2017 12:40 am Post subject: |
|
|
Voyager
Joined: 22 Jan 2017
Posts: 98
Location: India
|
| Thanks All for the Quick support now we are able to get the full message as attachment. |
|
| Back to top |
|
|
|
|
