| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem with the mapping node |
« View previous topic :: View next topic » |
| Author |
Message
|
| satyasheel15 |
 Posted: Wed Jun 16, 2004 10:36 am Post subject: Problem with the mapping node |
 |
|
Voyager
Joined: 04 Mar 2003
Posts: 86
|
Hi,
I have created a DTD and imported into the message set.
After that I have create on message flow and where I have used the mapping node. Using the mapping node, I have done the mapping between the CWF format (source) and XML format (Target). I just done the drag and match.
But the output message are not coming out.
Please advise. |
|
| Back to top |
|
 |
| Nizam |
| Posted: Wed Jun 16, 2004 11:09 am Post subject: |
|
|
Disciple
Joined: 10 Feb 2004
Posts: 160
|
| Please post the error messages you get.. |
|
| Back to top |
|
|
| satyasheel15 |
| Posted: Wed Jun 16, 2004 11:37 am Post subject: |
|
|
Voyager
Joined: 04 Mar 2003
Posts: 86
|
Following is the trace node generated:
________________________________
Timestamps are formatted in local time, 300 minutes before GMT.
2004-06-16 13:20:36.882274 5141 UserTrace BIP4040I: The Execution Group 'CHASECreditCard' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2004-06-16 13:20:36.882865 5141 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'SQAT0260'. The MQCC was '0' and the MQRC was '0'.
2004-06-16 13:20:36.882881 5141 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'SQAT0260'.
2004-06-16 14:33:45.379123 5141 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2004-06-16 14:33:45.379261 5141 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-06-16 14:33:45.379310 5141 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
2004-06-16 14:33:45.379661 5141 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '270' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.
2004-06-16 14:33:50.297462 5141 UserTrace BIP2267I: Message flow 'TEST' (uuid='642d922e-fd00-0000-0080-c5a2e446e26f') successfully deleted.
The message broker received a configuration message containing an instruction to delete the message flow 'TEST' (uuid='642d922e-fd00-0000-0080-c5a2e446e26f'), and successfully performed this action.
No user action required.
2004-06-16 14:33:50.352088 5141 UserTrace BIP7080I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node with Subscription Point '' has received a message of type Publish.
The Publication Node with Subscription Point '' has started processing a message.
No user action required.
2004-06-16 14:33:50.352447 5141 UserTrace BIP7085I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node has propagated a message to its output terminal for subscription point ''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
2004-06-16 14:33:50.352821 5141 UserTrace BIP7080I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node with Subscription Point '' has received a message of type Publish.
The Publication Node with Subscription Point '' has started processing a message.
No user action required.
2004-06-16 14:33:50.353126 5141 UserTrace BIP7081I: The Publication Node has matched 1 subscriptions to topic '$SYS/Broker/sbat0260/Status/ExecutionGroup/CHASECreditCard' for subscription point ''.
The Publication Node has matched subscriptions for the current publication and topic.
No user action required.
2004-06-16 14:33:50.353221 5141 UserTrace BIP7085I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node has propagated a message to its output terminal for subscription point ''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
2004-06-16 14:33:50.353744 5141 UserTrace BIP2638I: The MQ output node 'PubSubControlMsgFlow.ListOutputNode' attempted to write a message to queue 'SYSTEM.BROKER.ADMIN.REPLY' connected to queue manager 'SQNT0260'. The MQCC was '0' and the MQRC was '0'.
2004-06-16 14:33:50.353763 5141 UserTrace BIP2622I: Message successfully output by output node 'PubSubControlMsgFlow.ListOutputNode' to queue 'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'SQNT0260'.
2004-06-16 14:33:50.354293 5141 UserTrace BIP7080I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node with Subscription Point '' has received a message of type Publish.
The Publication Node with Subscription Point '' has started processing a message.
No user action required.
2004-06-16 14:33:50.354579 5141 UserTrace BIP7085I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node has propagated a message to its output terminal for subscription point ''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
2004-06-16 14:33:50.354965 5141 UserTrace BIP7080I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node with Subscription Point '' has received a message of type Publish.
The Publication Node with Subscription Point '' has started processing a message.
No user action required.
2004-06-16 14:33:50.355224 5141 UserTrace BIP7081I: The Publication Node has matched 1 subscriptions to topic '$SYS/Broker/sbat0260/Status/ExecutionGroup/CHASECreditCard' for subscription point ''.
The Publication Node has matched subscriptions for the current publication and topic.
No user action required.
2004-06-16 14:33:50.355327 5141 UserTrace BIP7085I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node has propagated a message to its output terminal for subscription point ''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
2004-06-16 14:33:50.356021 5141 UserTrace BIP2638I: The MQ output node 'PubSubControlMsgFlow.ListOutputNode' attempted to write a message to queue 'SYSTEM.BROKER.ADMIN.REPLY' connected to queue manager 'SQNT0260'. The MQCC was '0' and the MQRC was '0'.
2004-06-16 14:33:50.356098 5141 UserTrace BIP2622I: Message successfully output by output node 'PubSubControlMsgFlow.ListOutputNode' to queue 'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'SQNT0260'.
2004-06-16 14:33:50.369869 5141 UserTrace BIP4040I: The Execution Group 'CHASECreditCard' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2004-06-16 14:33:50.370391 5141 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'SQAT0260'. The MQCC was '0' and the MQRC was '0'.
2004-06-16 14:33:50.370407 5141 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'SQAT0260'.
2004-06-16 14:33:51.093410 5141 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2004-06-16 14:33:51.093509 5141 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-06-16 14:33:51.093551 5141 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
2004-06-16 14:33:51.093826 5141 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '202' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.
2004-06-16 14:33:51.097026 5141 UserTrace BIP4040I: The Execution Group 'CHASECreditCard' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2004-06-16 14:33:51.097640 5141 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'SQAT0260'. The MQCC was '0' and the MQRC was '0'.
2004-06-16 14:33:51.097705 5141 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'SQAT0260'.
2004-06-16 14:34:04.616487 5141 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2004-06-16 14:34:04.616623 5141 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-06-16 14:34:04.616674 5141 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
2004-06-16 14:34:04.617018 5141 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '73326' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.
2004-06-16 14:34:04.658109 5141 UserTrace BIP2264I: Message flow 'TEST' (uuid='ae9ff32e-fd00-0000-0080-c5a2e446e26f') successfully created.
The message broker received a configuration message containing an instruction to create the message flow 'TEST' (uuid='ae9ff32e-fd00-0000-0080-c5a2e446e26f'), and successfully performed this action.
No user action required.
2004-06-16 14:34:04.707869 5141 UserTrace BIP7080I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node with Subscription Point '' has received a message of type Publish.
The Publication Node with Subscription Point '' has started processing a message.
No user action required.
2004-06-16 14:34:04.708250 5141 UserTrace BIP7085I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node has propagated a message to its output terminal for subscription point ''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
2004-06-16 14:34:04.708664 5141 UserTrace BIP7080I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node with Subscription Point '' has received a message of type Publish.
The Publication Node with Subscription Point '' has started processing a message.
No user action required.
2004-06-16 14:34:04.709633 5141 UserTrace BIP7081I: The Publication Node has matched 1 subscriptions to topic '$SYS/Broker/sbat0260/Status/ExecutionGroup/CHASECreditCard' for subscription point ''.
The Publication Node has matched subscriptions for the current publication and topic.
No user action required.
2004-06-16 14:34:04.709765 5141 UserTrace BIP7085I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node has propagated a message to its output terminal for subscription point ''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
2004-06-16 14:34:04.710538 5141 UserTrace BIP2638I: The MQ output node 'PubSubControlMsgFlow.ListOutputNode' attempted to write a message to queue 'SYSTEM.BROKER.ADMIN.REPLY' connected to queue manager 'SQNT0260'. The MQCC was '0' and the MQRC was '0'.
2004-06-16 14:34:04.710561 5141 UserTrace BIP2622I: Message successfully output by output node 'PubSubControlMsgFlow.ListOutputNode' to queue 'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'SQNT0260'.
2004-06-16 14:34:04.824977 5141 UserTrace BIP4040I: The Execution Group 'CHASECreditCard' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2004-06-16 14:34:04.825558 5141 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'SQAT0260'. The MQCC was '0' and the MQRC was '0'.
2004-06-16 14:34:04.825574 5141 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'SQAT0260'.
2004-06-16 14:34:09.095174 5141 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2004-06-16 14:34:09.095297 5141 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-06-16 14:34:09.095347 5141 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
2004-06-16 14:34:09.095658 5141 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '345' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.
2004-06-16 14:34:09.713669 5141 UserTrace BIP2265I: Attribute in message flow 'TEST' (uuid='ae9ff32e-fd00-0000-0080-c5a2e446e26f') successfully changed.
The message broker received a configuration message containing an instruction to change an attribute in the message flow 'TEST' (uuid='ae9ff32e-fd00-0000-0080-c5a2e446e26f') and successfully performed this action.
No user action required.
2004-06-16 14:34:09.722669 5141 UserTrace BIP4040I: The Execution Group 'CHASECreditCard' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2004-06-16 14:34:09.723216 5141 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'SQAT0260'. The MQCC was '0' and the MQRC was '0'.
2004-06-16 14:34:09.723233 5141 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'SQAT0260'.
2004-06-16 14:34:17.564941 5930 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'TEST.MQInput'.
2004-06-16 14:34:17.565093 5930 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'TEST.MQInput' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-06-16 14:34:17.565259 5930 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'TEST.MQInput' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
2004-06-16 14:34:17.565454 5930 UserTrace BIP6061I: Parser type 'MRM' created on behalf of node 'TEST.MQInput' to handle portion of incoming message of length '425' bytes beginning at offset '364'. Parser type selected based on value 'MRM' from previous parser.
2004-06-16 14:34:17.565572 5930 UserTrace BIP2538I: Node 'TEST.Trace': Evaluating expression 'Root' at (, 1.3).
2004-06-16 14:34:17.592233 5930 UserTrace BIP4067I: Message propagated to output terminal for trace node 'TEST.Trace'.
The trace node 'TEST.Trace' has received a message and is propagating it to any nodes connected to its output terminal.
No user action required.
2004-06-16 14:34:29.596599 5141 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2004-06-16 14:34:29.596721 5141 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-06-16 14:34:29.596771 5141 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
2004-06-16 14:34:29.597169 5141 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '241' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.
2004-06-16 14:34:29.600412 5141 UserTrace BIP4040I: The Execution Group 'CHASECreditCard' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2004-06-16 14:34:29.601074 5141 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'SQAT0260'. The MQCC was '0' and the MQRC was '0'.
2004-06-16 14:34:29.601089 5141 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'SQAT0260'.
2004-06-16 14:34:29.837272 5141 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2004-06-16 14:34:29.837381 5141 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-06-16 14:34:29.837430 5141 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
2004-06-16 14:34:29.837739 5141 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '307' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.
2004-06-16 14:34:32.640663 5141 UserTrace BIP2265I: Attribute in message flow 'TEST' (uuid='ae9ff32e-fd00-0000-0080-c5a2e446e26f') successfully changed.
The message broker received a configuration message containing an instruction to change an attribute in the message flow 'TEST' (uuid='ae9ff32e-fd00-0000-0080-c5a2e446e26f') and successfully performed this action.
No user action required.
2004-06-16 14:34:32.646785 5141 UserTrace BIP4040I: The Execution Group 'CHASECreditCard' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2004-06-16 14:34:32.647357 5141 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'SQAT0260'. The MQCC was '0' and the MQRC was '0'.
2004-06-16 14:34:32.647373 5141 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'SQAT0260'.
2004-06-16 14:34:33.739780 5141 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2004-06-16 14:34:33.739891 5141 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-06-16 14:34:33.739940 5141 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
2004-06-16 14:34:33.740238 5141 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '239' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.
Threads encountered in this trace:
5141 5930 |
|
| Back to top |
|
|
| TonyD |
| Posted: Wed Jun 16, 2004 2:44 pm Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
| I think it might be useful if you spent some time reading the Help re tracing....this is the second time that you have supplied partial trace output that does not include suitable tracing of the activity where you say you have a problem. The bulk of the trace is deploy activity. It appears that Thread 5930 may be the execution of your flow (input queue 'TEST.MQInput') but there is no activity shown after processing in node 'TEST.Trace', including the input message itself if that is what this node is intended to display, so it is impossible to 'advise' based on this information. |
|
| 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
|
|
|
|
