| Author |
Message
|
| Wildmq |
 Posted: Mon Feb 22, 2010 7:18 am Post subject: Validation not working |
 |
|
Newbie
Joined: 19 Feb 2010
Posts: 5
|
I wrote a very simple validation flow, with an MQInput routed to ab MQOutput flow, with the addition of a MQOutput connected to the Catch terminal of the MQInput
The MQInput has the following config:
Input Message Parsing Tab:
| Code: |
Message domain: XMLNSC
Message set: ZCUST |
Validation Tab:
| Code: |
Validate: Content and Value
Failure action: Local Error Log |
When I send message to the input queue, the messages always route to the output queue, whether the message is correct or not.
There are no errors in the Event View, application log
Am I missing something, and how can I debug this ? (I am using v7 on WIndows) |
|
| Back to top |
|
 |
| broker_new |
| Posted: Mon Feb 22, 2010 7:35 am Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
Have you selected Parser Options>>Parse Timing = Complete?
_________________
IBM ->Let's build a smarter planet |
|
| Back to top |
|
|
| Wildmq |
| Posted: Mon Feb 22, 2010 8:30 am Post subject: |
|
|
Newbie
Joined: 19 Feb 2010
Posts: 5
|
Actually, I had it set on default (On Demand)
However, when I changed it to Complete, it is still acting the same, sending it to the out queue no matter if I send a correct message or not, any ideas ? |
|
| Back to top |
|
|
| Wildmq |
| Posted: Mon Feb 22, 2010 10:37 am Post subject: |
|
|
Newbie
Joined: 19 Feb 2010
Posts: 5
|
My Appl log was incorrectly sorted before, now I see a problem
I get the following message:
| Code: |
( NHBRK2.exe7 ) The XMLNSC parser cannot find a deployed message set with name ''ZCUST''.
The XMLNSC parser is attempting to validate an XML message or a message tree, but the specified message set cannot be located in this execution group. This situation can arise for one of the following reasons:
- The message set has not been deployed to this execution group.
- In the message set properties, XMLNSC is not the 'Default message domain' and is not a 'Supported message domain'.
- The message set has been identified using its 13-character identifier; you must use the message set name.
- There was an error during the preprocessing of the XML schemas in the message set.
Check that the specified message set has been successfully deployed.
Check that the MessageSet property contains the name, not the identifier, of the message set.
In the message set, check that XMLNSC is either the default message domain or a supported message domain. |
I think it may be a problem with how the message set is defined
The MQINput is actually configured as follows (I was using a shortcut previouslY)
| Code: |
Message domain: XMLNSC
Message set: ZCUST (OFR2L78002001) |
I assume the message set name above violates the 3rd rule to examine above (set identified by its 13 digit ID).
This is a field that is selected.
How do I fix this particular problem (I tried deleting all of the characters except for ZCUST, but this did not work either ?
Thanks |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Feb 22, 2010 10:41 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You don't mention if you deployed the message set or not.
You don't mention if the bar file that deployed the message set included an xsdzip or only a dict. |
|
| Back to top |
|
|
| Wildmq |
| Posted: Mon Feb 22, 2010 11:20 am Post subject: |
|
|
Newbie
Joined: 19 Feb 2010
Posts: 5
|
I did deploy the message set (named ZCUST)
However, when I deployed to the exe group, it had the following contents:
| Code: |
+ exegroup1
- Validation1
- ZCUST
+ exegroup2 |
The Manage tab of the Bar file reports the following
| Code: |
+ Validation1.cmf
+ Validateion1
MQInput
MQOutput
MQOutput1
- ZCUST dictionary |
So it does not look like I have the xsdzip file
How do I get that in the BAR file ?
Thanks |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Feb 22, 2010 11:21 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Wildmq wrote: |
How do I get that in the BAR file ?
|
Include it like anything else.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Wildmq |
| Posted: Mon Feb 22, 2010 11:26 am Post subject: |
|
|
Newbie
Joined: 19 Feb 2010
Posts: 5
|
I just got it,
The ZCUST was configured for MRM
Thanks |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Feb 22, 2010 11:35 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Wildmq wrote: |
I just got it,
The ZCUST was configured for MRM
Thanks |
That's what it meant when it said
| Quote: |
| - In the message set properties, XMLNSC is not the 'Default message domain' and is not a 'Supported message domain'. |
|
|
| Back to top |
|
|
|
|
