| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Converting XML Message to Tag Delimited Message |
« View previous topic :: View next topic » |
| Author |
Message
|
| venugopal |
 Posted: Wed Nov 12, 2003 5:30 pm Post subject: Converting XML Message to Tag Delimited Message |
 |
|
Newbie
Joined: 12 Nov 2003
Posts: 2
|
Hi,
I am new to this WMQI 2.1 . I am facing problem while converting XML Message after importing dtd in Control Center . After creating MessageFlow and mappings, i am getting error 'path doest not match any of the following messages' after clicking 'check message flow' option.The message structure with compound types and elements as per the dtd is automatically created by tool.
After deploying this i am getting empty message in my output.
I will be thankful who can suggest me the solution.
Thanks in advance
Venu. |
|
| Back to top |
|
 |
| skn |
| Posted: Thu Nov 13, 2003 8:20 am Post subject: |
|
|
Centurion
Joined: 21 May 2003
Posts: 112
Location: Dallas
|
why dont you use the debugger or add a trace node to check if any exceptions are generated.you might as well paste the compute node code.
What csd are you on .I think there might be some problems with dtd imports . |
|
| Back to top |
|
|
| venugopal |
| Posted: Thu Nov 13, 2003 11:54 am Post subject: |
|
|
Newbie
Joined: 12 Nov 2003
Posts: 2
|
Hi,
Thanks for the reply .I have following code defined in ComputeNode.I am using CSD05.
-----------------
SET OutputRoot.Properties.MessageSet = 'DUT2VRS08U001';
SET OutputRoot.Properties.MessageType = 'SMPLE_XML';
SET OutputRoot.Properties.MessageFormat = 'TDStag';
SET "OutputRoot"."MRM"."FILENUMBER1" = "InputBody"."DATA"."FILENUMBER1";
SET "OutputRoot"."MRM"."FIRSTNAME1" = "InputBody"."DATA"."FIRSTNAME1";
SET "OutputRoot"."MRM"."LASTNAME1" = "InputBody"."DATA"."LASTNAME1";
----------------------------------------
After deploying to the broker the i found the error in trace log.
--------------------------------------------
2003-11-13 12:44:21.062788 218 UserTrace BIP2537I: Node 'TEST_VENU_XML_MSG.Compute1': Executing statement 'SET OutputRoot.MRM.FILENUMBER1 = InputBody.DATA.FILENUMBER1;' at (15, 1).
2003-11-13 12:44:21.062880 218 UserTrace BIP2538I: Node 'TEST_VENU_XML_MSG.Compute1': Evaluating expression 'InputBody.DATA.FILENUMBER1' at (15, 40).
2003-11-13 12:44:21.063674 218 UserTrace BIP2543E: Node 'TEST_VENU_XML_MSG.Compute1': (15, 52) : Failed to navigate to path element because it does not exist.
2003-11-13 12:44:21.064056 218 UserTrace BIP2567I: Node 'TEST_VENU_XML_MSG.Compute1': Assigning NULL to 'OutputRoot.MRM.FILENUMBER1', thus deleting it.
2003-11-13 12:44:21.064198 218 UserTrace BIP2537I: Node 'TEST_VENU_XML_MSG.Compute1': Executing statement 'SET OutputRoot.MRM.FIRSTNAME1 = InputBody.DATA.FIRSTNAME1;' at (16, 1).
2003-11-13 12:44:21.064290 218 UserTrace BIP2538I: Node 'TEST_VENU_XML_MSG.Compute1': Evaluating expression 'InputBody.DATA.FIRSTNAME1' at (16, 39).
2003-11-13 12:44:21.064366 218 UserTrace BIP2543E: Node 'TEST_VENU_XML_MSG.Compute1': (16, 51) : Failed to navigate to path element because it does not exist.
2003-11-13 12:44:21.064484 218 UserTrace BIP2567I: Node 'TEST_VENU_XML_MSG.Compute1': Assigning NULL to 'OutputRoot.MRM.FIRSTNAME1', thus deleting it.
2003-11-13 12:44:21.064610 218 UserTrace BIP2537I: Node 'TEST_VENU_XML_MSG.Compute1': Executing statement 'SET OutputRoot.MRM.LASTNAME1 = InputBody.DATA.LASTNAME1;' at (17, 1).
2003-11-13 12:44:21.064736 218 UserTrace BIP2538I: Node 'TEST_VENU_XML_MSG.Compute1': Evaluating expression 'InputBody.DATA.LASTNAME1' at (17, 3 .
2003-11-13 12:44:21.064812 218 UserTrace BIP2543E: Node 'TEST_VENU_XML_MSG.Compute1': (17, 50) : Failed to navigate to path element because it does not exist.
2003-11-13 12:44:21.064924 218 UserTrace BIP2567I: Node 'TEST_VENU_XML_MSG.Compute1': Assigning NULL to 'OutputRoot.MRM.LASTNAME1', thus deleting it.
-------------------------------------------------------
I could not figure out what could be the problem , will it be the way the message was built?
Venu. |
|
| Back to top |
|
|
| skn |
| Posted: Thu Nov 13, 2003 2:29 pm Post subject: |
|
|
Centurion
Joined: 21 May 2003
Posts: 112
Location: Dallas
|
By the look of that it is not able to resolve the input references in the compute node.try to change the SET statements to refer to the InputRoot
rather the InputBody.
SET "OutputRoot"."MRM"."FILENUMBER1" = InputRoot.MRM.DATA.FILENUMBER1;
And what is FILENUMBER1 in the XML ,an element or an attribute.Thay have different ways of being referred to. |
|
| Back to top |
|
|
| EddieA |
| Posted: Thu Nov 13, 2003 4:42 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
You could also drop in a Trace node in before the Compute with ${Body} to validate the MRM data names are what you think they are.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| 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
|
|
|
|
