| Author |
Message
|
| bdaoust |
 Posted: Mon Dec 29, 2014 1:42 pm Post subject: WMB to IIB9 Error : Text Unable to resolve deployed resource |
 |
|
Centurion
Joined: 23 Sep 2010
Posts: 130
|
Hello all:
I'm converting all of our message flow projects from WMB 7.0 to IIB9.
I did all the conversion that is required for maps (like convert the old messagemap to the new version) and subflows and don't show any warnings/errors within the IIB9 toolkit. BAR file deployed fine.
However, I'm getting the following error on a mapping node:
Text Unable to resolve deployed resource for Qname: null, location: /ClientRequestXML/ClientRequestMsg.mxsd, type: xsdnull
Here is what I did :
a) rebuilt the bar file ensuring all messagesets are in the bar.
b) deployed BAR file.
c) confirmed that the message before going into the mapping node in IIB9 is the same as the message before the mapping in WMB7.
Here are the specifics on my toolkit:
WMB - 7.0.0-20091028_2100
IIB9 - 9.0.0.2-20140515-1210
Any help would be appreciated.
Thanks,
Brian |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Dec 29, 2014 2:02 pm Post subject: Re: WMB to IIB9 Error : Text Unable to resolve deployed reso |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| bdaoust wrote: |
However, I'm getting the following error on a mapping node:
| Quote: |
| Text Unable to resolve deployed resource for Qname: null, location: /ClientRequestXML/ClientRequestMsg.mxsd, type: xsdnull |
Here is what I did :
a) rebuilt the bar file ensuring all messagesets are in the bar.
b) deployed BAR file.
c) confirmed that the message before going into the mapping node in IIB9 is the same as the message before the mapping in WMB7.
Here are the specifics on my toolkit:
WMB - 7.0.0-20091028_2100
IIB9 - 9.0.0.2-20140515-1210
Any help would be appreciated.
Thanks,
Brian |
Well Brian looks to me that for whatever reason (maybe namespace??) the defined mapping is hitting a null value and null might not be admissible? see /ClientRequestXML/ClientRequestMsg.mxsd
This looks very much still like a message set. Have you graduated to message models yet? :innnocent:
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bdaoust |
| Posted: Tue Dec 30, 2014 9:24 am Post subject: |
|
|
Centurion
Joined: 23 Sep 2010
Posts: 130
|
Thanks fjb_saper.
Like I said, what is throwing me is that I compared the message from both environments (one WMB7 and one IIB9) and they are identical. So, when I did IIB9's map conversion, it changed something. I wish the exception was a little more specific as to where exactly it's failing. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Dec 30, 2014 12:07 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| bdaoust wrote: |
Thanks fjb_saper.
Like I said, what is throwing me is that I compared the message from both environments (one WMB7 and one IIB9) and they are identical. So, when I did IIB9's map conversion, it changed something. I wish the exception was a little more specific as to where exactly it's failing. |
A run with user log level set to debug should pinpoint to you where the error is. My guess would be that the message set is missing... like it cannot find the relevant msxd file. Is the message set still referenced correctly by the flow project ?
Remember the deployment differences between independent resources, and applications. No more deploying parts and let the runtime assemble all... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bdaoust |
| Posted: Tue Dec 30, 2014 12:12 pm Post subject: |
|
|
Centurion
Joined: 23 Sep 2010
Posts: 130
|
| User traces are tricky for me because I don't have access to the broker. I can only do trace nodes. =( |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Dec 30, 2014 12:16 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| bdaoust wrote: |
| User traces are tricky for me because I don't have access to the broker. I can only do trace nodes. =( |
Bad for you, because if it is not a reference and deployment issue, the only way you will be able to pinpoint the problem is via a user trace...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bdaoust |
| Posted: Tue Dec 30, 2014 12:27 pm Post subject: |
|
|
Centurion
Joined: 23 Sep 2010
Posts: 130
|
Ya, I'm working on getting access to at least the development box. :fingers crossed:
-Brian |
|
| Back to top |
|
|
| bdaoust |
| Posted: Wed Dec 31, 2014 8:09 am Post subject: |
|
|
Centurion
Joined: 23 Sep 2010
Posts: 130
|
SOLVED!
So, in the message sets used by the mapping node, I needed to select XLMNSC as an additional parser. I checked my project in WMB7 and this was NOT checked and it worked.
Anyways thanks for the guidance and Happy New Year.
-Brian |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Dec 31, 2014 8:33 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| bdaoust wrote: |
SOLVED!
So, in the message sets used by the mapping node, I needed to select XLMNSC as an additional parser. I checked my project in WMB7 and this was NOT checked and it worked.
Anyways thanks for the guidance and Happy New Year.
-Brian |
Thanks for sharing the solution. I'm sure a number of other folks will hit this same problem and be grateful for it. Happy New Year
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bdaoust |
| Posted: Mon Jan 05, 2015 8:05 am Post subject: |
|
|
Centurion
Joined: 23 Sep 2010
Posts: 130
|
So, I thought it was solved.
I'm able to get passed the mapping node.
Here is the situation:
The incoming message to the mapping node is in the MRM domain, but it looks like an XML message.
In WMB7, for the messagsets, I noticed the default message domain is set to : MRM : For binary, text or XML messages (namespace aware, validation, low memory use).
For IIB9, I noticed that the default message domain is this:
MRM : For binary or text messages that are modeled in a message set
So, I selected XMLNSC as a support message domain and was no longer getting the "unable to find the deployable resource" error.
However, the values are not mapping - the values on the output of the mapping are blank (null).
I thought it was a namespace issue, but I tried to declare the namespaces (on the message set) and still no luck.
So looks like there is some difference between WMB7 and IIB9. Any suggestions what to look at? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jan 05, 2015 8:07 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| If you change the parser used on the input message, you have to update the map to reflect that. |
|
| Back to top |
|
|
| bdaoust |
| Posted: Mon Jan 05, 2015 12:16 pm Post subject: |
|
|
Centurion
Joined: 23 Sep 2010
Posts: 130
|
Thanks Jeff.
I don't see any obvious options to update.
Do I just rebuild the map completely and it picks up the new parser?
-Brian |
|
| Back to top |
|
|
|
|
