| Author |
Message
|
| hellobond070 |
 Posted: Mon Jun 07, 2010 3:13 pm Post subject: Output XML message Error |
 |
|
Centurion
Joined: 18 Nov 2009
Posts: 118
|
I have the below flow
MQinput -> Compute -> ResetContent Descriptor -> MQoutput
I first build the XML message in Compute node in XMLNSC format. Then I try to parse it against a message set in a ResetContent Descriptor. It throws a below error.
I previously tried setting the message format, message set, all in compute node esql but could not get it correctly. So I thought of building the XML message and then later parsing against the schema I have .
Please let me know if anyone has faced the below errror or any suggestions.
| Code: |
Time >>>>>>>>>>>>> 2010-06-07 19:06:12.223284
Exception List >>>>>>> >( ['MQROOT' : 0xd1aea50]
(0x01000000:Name):RecoverableException = (
(0x03000000:NameValue):File = 'F:\build\S610_P\src\DataFlowEngine\BasicNodes\ImbResetContentDescNode.cpp' (CHARACTER)
(0x03000000:NameValue):Line = 609 (INTEGER)
(0x03000000:NameValue):Function = 'ImbResetContentDescNode::evaluate' (CHARACTER)
(0x03000000:NameValue):Type = 'ComIbmResetContentDescriptorNode' (CHARACTER)
(0x03000000:NameValue):Name = 'LMN_MTO_MTOMILESTONE#FCMComposite_1_1' (CHARACTER)
(0x03000000:NameValue):Label = 'LMN_MTO_MTOMILESTONE.ResetContentDescriptor' (CHARACTER)
(0x03000000:NameValue):Catalog = 'BIPv610' (CHARACTER)
(0x03000000:NameValue):Severity = 3 (INTEGER)
(0x03000000:NameValue):Number = 2230 (INTEGER)
(0x03000000:NameValue):Text = 'Caught exception and rethrowing' (CHARACTER)
(0x01000000:Name ):RecoverableException = (
(0x03000000:NameValue):File = 'F:\build\S610_P\src\DataFlowEngine\BasicNodes\ImbResetContentDescNode.cpp' (CHARACTER)
(0x03000000:NameValue):Line = 355 (INTEGER)
(0x03000000:NameValue):Function = 'ImbResetContentDescNode::evaluate' (CHARACTER)
(0x03000000:NameValue):Type = 'ComIbmResetContentDescriptorNode' (CHARACTER)
(0x03000000:NameValue):Name = 'LMN_MTO_MTOMILESTONE#FCMComposite_1_1' (CHARACTER)
(0x03000000:NameValue):Label = 'LMN_MTO_MTOMILESTONE.ResetContentDescriptor' (CHARACTER)
(0x03000000:NameValue):Catalog = 'BIPv610' (CHARACTER)
(0x03000000:NameValue):Severity = 0 (INTEGER)
(0x03000000:NameValue):Number = 0 (INTEGER)
(0x03000000:NameValue):Text = 'Message has no folders' (CHARACTER)
(0x01000000:Name ):Insert = (
(0x03000000:NameValue):Type = 5 (INTEGER)
(0x03000000:NameValue):Text = 'Root' (CHARACTER)
) |
|
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Jun 07, 2010 5:07 pm Post subject: Re: Output XML message Error |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| hellobond070 wrote: |
| I previously tried setting the message format, message set, all in compute node esql but could not get it correctly. |
Not correct in what way?
| hellobond070 wrote: |
| So I thought of building the XML message and then later parsing against the schema I have . |
Why did you believe this would help? Why are you attempting to parse a message you've just built?
| hellobond070 wrote: |
| Please let me know if anyone has faced the below errror or any suggestions. |
Old advice is good advice; put a trace node after the compute node, take a user trace and examine the result.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Jun 08, 2010 12:36 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| What is your message flow doing? Why do you want to parse this message against a message set? Are you really *parsing* it, or are you attempting to output an XML message from your flow? |
|
| Back to top |
|
|
| hellobond070 |
| Posted: Tue Jun 08, 2010 10:13 am Post subject: |
|
|
Centurion
Joined: 18 Nov 2009
Posts: 118
|
Yes Kimbert you are right. the whole idea is to populate a schema XSD. To generate the output xml with the fields I don't populate with default value.
So I map a few fields of the schema and the rest are default values. I am not able to use MRM for this. The auto completion doesn't work. I have done this before for CWF and TDS fixed formats. But this is the first time I am trying to use MRM for XML.
Hence I tried building the XMLNSC message and then sending it throught the XSD.
Please correct me if I am wrong. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Jun 08, 2010 10:36 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Hi hellobondo70,
| Quote: |
| the whole idea is to populate a schema XSD |
Er...did it not seem like a good idea to mention that before? Seriously, it's hard to help you if you don't explain what you're trying to do.
| Quote: |
| I am not able to use MRM for this. |
Well, not MRM XML anyway. But you shouldn't be using that anyway these days. MRM CWF and TDS do apply default values, but only when ouputting a field in a fixed-length structure.
The XMLNSC parser does apply default values, if you tell it to use the schema when parsing. That means that you need to enable validation in your flow - otherwise the XMLNSC parser will never look at the schemas, and won't know about the default values. |
|
| Back to top |
|
|
| hellobond070 |
| Posted: Tue Jun 08, 2010 1:00 pm Post subject: |
|
|
Centurion
Joined: 18 Nov 2009
Posts: 118
|
I apologize..i should have mentioned what I am trying to achieve.
Well, I can use XMLNSC parser validation in Compute node. But where do I mention the output message set.
I have a message set built using the XSD. The input SAP IDOC needs to be mapped to this XSD creating a XML file. |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Tue Jun 08, 2010 1:03 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
using the output root properties you can set the message set / message type and message format.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jun 08, 2010 8:06 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Looks to me you may be doing something inherently wrong...
SAP Idocs should not be that difficult.
You may want to seek help with that. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| hellobond070 |
| Posted: Wed Jun 09, 2010 7:42 am Post subject: |
|
|
Centurion
Joined: 18 Nov 2009
Posts: 118
|
No. Sap adapters is okay. I am receiving data and I am able to see this data in debug mode. I believe the problem is with the output Message set which I am using.
I would like to know something about a message set. This particular message set which I am using has various references within it as in one message is referring to another message in the same message set.
Please let me know if the message set gets created properly even if some reference in the msessage is not present or does the toolkit validate the whole message set before creating it. |
|
| Back to top |
|
|
| hellobond070 |
| Posted: Wed Jun 09, 2010 7:48 am Post subject: |
|
|
Centurion
Joined: 18 Nov 2009
Posts: 118
|
Just to further add, what I meant by one message calling other message in the same message set is the same message set has a lot of mxmd. When I open the message under a mxmd which I am trying to use, it has a includes in the mxmd property which includes other mxmd. Manually checking them is not possible because it's a big message set.
When I try using a Reset Content Descriptor in the flow with this message domain, message set, message type and message format I get RM dictionary not found in the visual debug mode provided by the toolkit version 6.1.
Please advise. Thanks. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Jun 10, 2010 1:07 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| ust to further add, what I meant by one message calling other message in the same message set is the same message set has a lot of mxmd. When I open the message under a mxmd which I am trying to use, it has a includes in the mxmd property which includes other mxmd. Manually checking them is not possible because it's a big message set. |
The toolkit checks all refs, whether in the same mxsd or a different one. So that's not the reason for this (or any other) problem.
| Quote: |
| When I try using a Reset Content Descriptor in the flow with this message domain, message set, message type and message format I get RM dictionary not found in the visual debug mode provided by the toolkit version 6.1. |
That error message comes from the MRM parser when it cannot find a deployed dictionary ( message set ). The MRM parser cannot do what you require - so why are you still trying to use it? You should use XMLNSC with validation enabled, as suggested earlier. |
|
| Back to top |
|
|
|
|
