| Author |
Message
|
| santy |
 Posted: Wed Jul 23, 2008 10:31 pm Post subject: Message Set not getting deployed in 6.1 |
 |
|
Centurion
Joined: 03 Nov 2006
Posts: 141
|
Hi,
I created a message set with message domain property as XMLNSC in WMB 6.1.
I build the bar file and when I tried to deploy it to 6.1 broker , deployment failed with following error.
Jul 23 13:59:02 dkssp033 WebSphere Broker v6101[1877]: [ID 702911 user.error] (BMTSIS08.MRM_EG1)[244]BIP4041E: Execution group 'MRM_EG1' received an invalid configuration message. See the following messages for details of the error. : BMTSIS08.c9c72421-1b01-0000-0080-d96466aee1c0: /build/S610_P/src/DataFlowEngine/ImbConfigurationNode.cpp: 396: ImbConfigurationNode::evaluate: ComIbmConfigurationNode: ConfigurationNode
Jul 23 13:59:02 dkssp033 WebSphere Broker v6101[1877]: [ID 702911 user.error] (BMTSIS08.MRM_EG1)[244]BIP5024E: The creation and preprocessing of the XML schemas in message set 'IS_MS_IMXML.xsdzip' has failed. : BMTSIS08.c9c72421-1b01-0000-0080-d96466aee1c0: /build/S610_P/src/DataFlowEngine/PluginInterface/com_ibm_broker_plugin_CMbService.cpp: 1840: ImbJavaExceptionUtils::throwableToNativeException: :
Jul 23 13:59:02 dkssp033 WebSphere Broker v6101[1877]: [ID 702911 user.error] (BMTSIS08.MRM_EG1)[244]BIP4395E: Java exception: 'com.ibm.broker.schemadeploy.MbXSDInternalError'; thrown from class name: 'com.ibm.broker.schemadeploy.MbXSDDeployDirector', method name: 'compileMessageSetSchemas', file: 'MbXSDDeployDirector.java', line: '525' : BMTSIS08.c9c72421-1b01-0000-0080-d96466aee1c0: /build/S610_P/src/DataFlowEngine/PluginInterface/com_ibm_broker_plugin_CMbService.cpp: 1858: ImbJavaExceptionUtils::throwableToNativeException: :
Does any body know where I'm wrong ?
Do I need to associate the XMLNSC parser with MRM parser ?
Thanks,
Santosh |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Wed Jul 23, 2008 10:36 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Jul 23 13:59:02 dkssp033 WebSphere Broker v6101[1877]: [ID 702911 user.error] (BMTSIS08.MRM_EG1)[244]BIP5024E: The creation and preprocessing of the XML schemas in message set 'IS_MS_IMXML.xsdzip' has failed. :
what is this all about,
how did you create the XMLNSC message set?
if you are having an XSD then it has to be set as MRM
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| santy |
| Posted: Wed Jul 23, 2008 10:56 pm Post subject: |
|
|
Centurion
Joined: 03 Nov 2006
Posts: 141
|
I created a message set with XMLNSC by setting message domain property as XMLNSC. I did this beacuse first this message domain was set as XML , now as XML parser is deprecated we choose as XMLNSC.
We don't have any XSD.
We set XMLNSC in the MessageSet.mset file for that message set. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Jul 24, 2008 2:42 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Gaya3 : santy is doing the right thing here. MRM XML should not be used in new v6.1 message flows. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Jul 24, 2008 2:53 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| I created a message set with XMLNSC by setting message domain property as XMLNSC. I did this beacuse first this message domain was set as XML , now as XML parser is deprecated we choose as XMLNSC. |
OK- looks as if there's some confusion here.
- If you want to change from XML to XMLNSC, you need to change the Domain on the input node of your message flow.
- The XMLNSC domain does not need a message set.
- If you want XMLNSC to validate your messages against your XSDs, you need to create a message set, and then create message definition files from your XSDs.
- XMLNSC does not use the XML physical format in the message set. It only uses the XSDs which are deployed in the xsdzip.
- You should raise a PMR for the internal error. Please reference this thread when you describe the problem, so that IBM service can see that I have already been involved via this forum.
Hope that helps. Please post again if you are still confused. |
|
| Back to top |
|
|
| santy |
| Posted: Wed Aug 20, 2008 1:26 am Post subject: |
|
|
Centurion
Joined: 03 Nov 2006
Posts: 141
|
Hi Kimbert, Sorry for late reply.....
As per your suggestion I have created message set from the xsd, but still we are facing the issues like MRM bitstream longer than expected. I have selected Message Domain as XMLNSC while creating message set. |
|
| Back to top |
|
|
| vairavan |
| Posted: Wed Aug 20, 2008 4:02 am Post subject: |
|
|
Apprentice
Joined: 22 Apr 2008
Posts: 42
|
Hi Santy,
Your problem looks like pretty minor.
Just ensure that you have checked following conditions...
1. domain could be selected as XMLNSC (No harm if you have selected as MRM also, as it can handle all formats.) This is in .mset file.
2. Now in the Input node, along with the domain, the message set also needs to be specified. That is mandatory.
3. And check your Messages in Message definition file once again that you have done correct parsing.
4. Check your Input file whether it is having all the tags properly or not.
Hope this helps you. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Aug 21, 2008 3:34 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| santy: 'Bitstream longer than expected' is a completely different error. It is issued by the MRM parser when parsing a message. You need to specify the Domain as 'XMLNSC' on your input node. Setting MRM as the default domain it in the message set does not affect the runtime in any way. |
|
| Back to top |
|
|
|
|
