| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem deploying MessageSet in 6.1 |
« View previous topic :: View next topic » |
| Author |
Message
|
| p.cradwick |
 Posted: Wed Sep 10, 2008 1:57 am Post subject: Problem deploying MessageSet in 6.1 |
 |
|
Acolyte
Joined: 16 May 2001
Posts: 56
|
Hi,
Have just started using Broker 6.1 (Toolkit 6.1.0) and having trouble deploying a message set.
The deploy seems to go ok and the bar file contains the *.xsdzip file created on the deploy, but when I used the message set to parse the input XML in MQInput node,
I get the exception: "BIP5304E: A runtime dictionary resource for message set ''WorkNetMessages'' cannot be found."
The workspace only has one message set so it must be the right one.
There is only one execution group, so can't have deployed to another one without the message set, as someone else did.
I opened the bar file and it contained the expected objects (3 jar files, 1 cmf, 1 xsdzip).
Also looked in the xsdzip file expecting to see the mxsd files, but it contained the xsd schema files and the mset file,
so I figured that was ok as the mxsd appear to be the xsd...
There are no problems reported in the xsd report files of the message set or the deploy logs.
The message set itself looks correct (mxsd file).
The msg properties has the right data...
Is there anything extra one has to do to deploy a messageSet in 6.1 compare to 6.0?
Any advice greatly appreciated
regards
Peter |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Sep 10, 2008 2:21 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You are using an XMLNS / XMLNSC parser and you did turn validation on? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Sep 10, 2008 6:35 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
- You are obviously using the MRM parser ( XMLNSC would not attempt to load a dictionary )
- Your BAR file does not contain a dictionary. This is because 'MRM' is not one of the 'supported domains' in your message set.
So that should give you a clue about how to avoid this particular problem.
Going a little bit beyond your question, you are obviously writing an XML processing flow in v6.1. You should be thinking about using XMLNSC for all XML processing in new message flows.
And yes, XMLNSC does support validation ( not sure whether fjp_saper meant to suggest otherwise, but it could be read that way  ) |
|
| Back to top |
|
|
| p.cradwick |
| Posted: Wed Sep 10, 2008 1:34 pm Post subject: |
|
|
Acolyte
Joined: 16 May 2001
Posts: 56
|
Thanks Kimbert that was the problem. When I added MRM a dictionary appeared in the bar file and all was well.
Just to clarify, in normal operation the flow accepts one of 2 xml messages and parses the input as XMLNSC. Once the message has been identified, it is reset in RCD for a mapping node. This (RCD) is where the problem appeared.
I changed the MQInput node to MRM temporarily simply to speed up testing and reduce the trace file size!
Thanks again
Peter |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Sep 10, 2008 1:35 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Sorry, I was just trying to make certain I understood correctly what he was trying to do. Using XMLNSC with xsdzip and validation should have worked in 6.1...
However as you identified he was trying to use MRM with a message set that did not have a declared MRM domain...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
