| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| select XMLNSC as additional parser in IIB9.0.0.2 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Armageddon123 |
 Posted: Wed Aug 05, 2015 8:32 am Post subject: select XMLNSC as additional parser in IIB9.0.0.2 |
 |
|
Acolyte
Joined: 11 Feb 2014
Posts: 61
|
Could you please provide your thoughts on this issue.
When we are migrating the MsgSets from WMB 6.1 to IIB 9, it fails to deploy with error
| Quote: |
BIP3949E:
Unable to resolve deployed resource for Qname:null, ,location: something.msxd,
type:xsdnull' internal error number: '2' |
The generation of the map has failed
As advised greatly in the link,
http://www.mqseries.net/phpBB2/viewtopic.php?t=69167&sid=a2badc582634f70eed1cd7bc7b627dc4
selected 'XMLNSC' as additional parser in the message set and it is deploying fine. I havent got a chance to verify the flow runtime if this is making any changes to the parser assigned in runtime in flow. But should not, because no change was done in message flow. only change was 'select XMLNSC as additional parser' in messageset.
Can you please advise what is the reason for this change in IIB9. tried enabling trace for deployment. But it gives no additional info except this same error message.
there is one iib9 fixlist in link here
http://www-01.ibm.com/support/docview.wss?uid=swg1IT07457
this has the same error. But the root cause given here is not matching with the issue which i am facing. So I think , though error message is same, the issue is different from this technote.
Can you please advise on the reason for selecting XMLNSC as additional parser in IIB9.
Thanks |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Wed Aug 05, 2015 10:11 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Quote: |
| The generation of the map has failed |
does this mean that you are using a V6.1 mapping node?
If so what does the release notes/documentation say about migrating V6.1 mapping nodes to V9?
As for message sets, You should be able to import the 6.1 message set into the IIB 9 toolkit if you have the original project. You could build a bew bar file and try deploying jut that to an empty Execution Group.
I've done this very thing (no mapping though) on a couple of projects.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Armageddon123 |
| Posted: Wed Aug 05, 2015 10:41 am Post subject: |
|
|
Acolyte
Joined: 11 Feb 2014
Posts: 61
|
Hi smdavies99
yes, i removed the old mapping node from 6.1, replaced with iib9 mapping node and selected the .map file which was migrated from .msgmap file.
The message set alone deploy has no issue. The issue is when it is used with the mapping node. Then it fails to deploy the bar file containing the msgflow and the msgset projects.
I am thinking there is something in mapping node which dictates that xmlnsc should also be selected in the message set. but i am not sure. I am still investigating
Thanks |
|
| Back to top |
|
|
| stoney |
| Posted: Wed Aug 05, 2015 11:27 am Post subject: |
|
|
Centurion
Joined: 03 Apr 2013
Posts: 140
|
You need to select XMLNSC as a parser on the message set as selecting this option causes the XML schemas within that message set to be deployed to the integration server as a set of .xsd files. If you look in the BAR file after selecting this option, you will see that an additional .xsdzip file is created that contains those .xsd files.
You need the .xsd files in the BAR file because the new mapper can only use .xsd files as a description of the inputs and outputs to a map. If you do not select this option, then those XML schemas are deployed in a format suitable only for use with the MRM parser. The new mapper cannot work with XML schemas in an MRM message set when those schemas are only available in the MRM format.
This is described in the product documentation - see the section "Behavior changes during the deployment phase" on http://www-01.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/br40815_.htm (the topic is called "Changes in behavior in message maps converted from legacy message maps"). |
|
| Back to top |
|
|
| Armageddon123 |
| Posted: Wed Aug 05, 2015 12:03 pm Post subject: |
|
|
Acolyte
Joined: 11 Feb 2014
Posts: 61
|
Hi Stoney
Thank you for the explanation. very clear now. |
|
| 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
|
|
|
|
