| Author |
Message
|
| psandip |
 Posted: Thu May 16, 2013 9:28 pm Post subject: Parser exception for SOAP Input node |
 |
|
Novice
Joined: 11 Aug 2006
Posts: 17
|
Hello all..
We are trying to develop a message flow with SOAP Input node as the receiver. The requirement is to have the SOAP Input node operate in the gateway mode, i.e., not binded to a particular WSDL. This way the message flow can act as a SOAP gateway for all downstream message flows. However we are concerned about what if there is a Parser exception. Consider if the incoming mesage is not a well-formed one. We have a need to capture the actual bitstream in this case. But when message is coming out of failure terminal of SOAP Input node, the bitstream is missing. Also we may not be able to use HTTP Input node since requesting system is implementing security as per WS-Security procedure.
Please suggest if there is anyway the bitstream can be captured in case of parser exception in SOAP Input node.
_________________
With Best Regards,
Sandeep |
|
| Back to top |
|
 |
| psandip |
| Posted: Thu May 16, 2013 10:02 pm Post subject: |
|
|
Novice
Joined: 11 Aug 2006
Posts: 17
|
Sorry...forgot to mention that we are using Message Broker version 7.0.0.2
I came across a link http://www-01.ibm.com/support/docview.wss?uid=swg1IC85234 which says that content and value validation failure will be fixed. In our scenario we do not have 'Content and Value' validation enabled. Even so it will, as expected, throw parser exception for ill-formed XML. So will the 7.0.0.6 fix solve the issue of capturing bitstream even for Parser exceptions due to improper input xml structure?
_________________
With Best Regards,
Sandeep |
|
| Back to top |
|
|
| huwgb |
| Posted: Fri May 17, 2013 2:34 am Post subject: |
|
|
Novice
Joined: 07 May 2013
Posts: 21
|
Have you tried a ResetContentDescriptor (reset to Blob) straight after the failure terminal?
It is likely that the message is still there in all its glory, but the parser is unable to handle it...
Just a thought bubble, may not be relevant to your situation |
|
| Back to top |
|
|
| kash3338 |
| Posted: Fri May 17, 2013 4:07 am Post subject: |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
Just to get to know, why do you need the message which is not well formed? Cant you just reply back saying, the message is ill-formed? What gain do you get in capturing this ill-formed message?
Is it for any audit purpose? |
|
| Back to top |
|
|
| ghoshly |
| Posted: Mon May 20, 2013 3:04 am Post subject: Definitely audit |
|
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
Definitely the incoming message should be audited as CLOB.
This would be helpful for the support folks as well, in case if they need to manually edit the file and resubmit the message, to process it quickly. |
|
| Back to top |
|
|
| kash3338 |
| Posted: Mon May 20, 2013 4:14 am Post subject: |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| In general, in a request-reply scenario, the actual payload is not captured as a whole. Instead some part of key data in the payload can be captured for audit, just to identify the message. |
|
| Back to top |
|
|
|
|
