| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| XML to CWF convert in 6.1? |
« View previous topic :: View next topic » |
| Author |
Message
|
| tanishka |
 Posted: Sun Jul 12, 2009 8:13 pm Post subject: XML to CWF convert in 6.1? |
 |
|
Centurion
Joined: 24 Nov 2008
Posts: 144
|
All,
I am new to MB and trying to convert sample XML to CWF message and was not able to process it. i develoed message flow and message set with xml and cwf physical properties and message definition file?I configured everything fine. Can anyone send me sample message flow for this? |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Sun Jul 12, 2009 10:23 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Several Points
1) Have you looked at the samples available in the toolkit?
2) Have you looked at the 'sticky' post at the top of this forum. Even though it is aimed at TDS, many of the same operations will apply to CWF
3) Finally, Take a user trace of the message as it passed through the flow. Please post the bits that describe the error here.
Without more information we can't point you in the right direction.
_________________
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 |
|
|
| Vitor |
| Posted: Mon Jul 13, 2009 12:41 am Post subject: Re: XML to CWF convert in 6.1? |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| tanishka wrote: |
| I am new to MB and trying to convert sample XML to CWF message and was not able to process it. |
Why not? What happened? Error messages? Wrong output? Large explosion?
| tanishka wrote: |
| I configured everything fine. |
Well clearly something's configured wrong!
| tanishka wrote: |
| Can anyone send me sample message flow for this? |
There are samples in all the usual places.
It's also worth pointing out that WMB is not the most straightforward product to learn and if you're new it's worth pushing your management for formal training. This forum is not suitible to provide such training really, nor are we really geared up walk you through your first flow.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| tanishka |
| Posted: Mon Jul 13, 2009 6:16 am Post subject: |
|
|
Centurion
Joined: 24 Nov 2008
Posts: 144
|
Well . below is ESQL code i used
CREATE COMPUTE MODULE XTOCW_Compute
CREATE FUNCTION Main() RETURNS BOOLEAN
BEGIN
-- CALL CopyMessageHeaders();
CALL CopyEntireMessage();
SET OutputRoot.MRM = InputRoot.XMLNSC.Customer;
SET OutputRoot.Properties.MessageType = 'Customer';
SET OutputRoot.Properties.MessageSet = 'GB77QOG002001';
SET OutputRoot.Properties.MessageFormat = 'CWF';
RETURN TRUE;
END;
and below is mqsichangetrace outut
UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'XTOCW.MQInput'.
2009-07-12 23:26:07.464509 3152 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'XTOCW.MQInput' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2009-07-12 23:26:07.464581 3152 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'XTOCW.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.
2009-07-12 23:26:07.464735 3152 UserTrace BIP6061I: Parser type ''MRM'' created on behalf of node 'XTOCW.MQInput' to handle portion of incoming message of length '232' bytes beginning at offset '364'. Parser type selected based on value ''MRM'' from previous parser.
2009-07-12 23:26:07.464964 3152 UserTrace BIP2537I: Node 'XTOCW.Compute': Executing statement ''BEGIN ... END;'' at ('.XTOCW_Compute.Main', '2.2').
2009-07-12 23:26:07.465046 3152 UserTrace BIP2537I: Node 'XTOCW.Compute': Executing statement ''CopyEntireMessage();'' at ('.XTOCW_Compute.Main', '4.4').
2009-07-12 23:26:07.465373 3152 UserTrace BIP2538I: Node 'XTOCW.Compute': Evaluating expression ''CopyEntireMessage()'' at ('.XTOCW_Compute.Main', '4.9').
2009-07-12 23:26:07.465414 3152 UserTrace BIP2537I: Node 'XTOCW.Compute': Executing statement ''BEGIN ... END;'' at ('.XTOCW_Compute.CopyEntireMessage', '1.39').
2009-07-12 23:26:07.465472 3152 UserTrace BIP2537I: Node 'XTOCW.Compute': Executing statement ''SET OutputRoot = InputRoot;'' at ('.XTOCW_Compute.CopyEntireMessage', '2.3').
2009-07-12 23:26:07.465525 3152 UserTrace BIP2539I: Node 'XTOCW.Compute': Evaluating expression ''InputRoot'' at ('.XTOCW_Compute.CopyEntireMessage', '2.20'). This resolved to ''InputRoot''. The result was ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2009-07-12 23:26:07.465558 3152 UserTrace BIP2568I: Node 'XTOCW.Compute': Copying sub-tree from ''InputRoot'' to ''OutputRoot''.
2009-07-12 23:26:07.465785 3152 UserTrace BIP2537I: Node 'XTOCW.Compute': Executing statement ''SET OutputRoot.MRM = InputRoot.XMLNSC.Customer;'' at ('.XTOCW_Compute.Main', '6.4').
2009-07-12 23:26:07.465826 3152 UserTrace BIP2543I: Node 'XTOCW.Compute': ('.XTOCW_Compute.Main', '6.25') : Failed to navigate to path element number '2' because it does not exist.
2009-07-12 23:26:07.465865 3152 UserTrace BIP2539I: Node 'XTOCW.Compute': Evaluating expression ''InputRoot.XMLNSC.Customer'' at ('.XTOCW_Compute.Main', '6.25'). This resolved to ''InputRoot.XMLNSC.Customer''. The result was ''EMPTY ROW''.
2009-07-12 23:26:07.465908 3152 UserTrace BIP2567I: Node 'XTOCW.Compute': Assigning NULL to ''OutputRoot.MRM'', thus deleting it.
2009-07-12 23:26:07.465954 3152 UserTrace BIP2537I: Node 'XTOCW.Compute': Executing statement ''SET OutputRoot.Properties.MessageType = 'Customer';'' at ('.XTOCW_Compute.Main', '8.4').
2009-07-12 23:26:07.466351 3152 UserTrace BIP2566I: Node 'XTOCW.Compute': Assigning value '''Customer''' to field / variable ''OutputRoot.Properties.MessageType''.
2009-07-12 23:26:07.466417 3152 UserTrace BIP2537I: Node 'XTOCW.Compute': Executing statement ''SET OutputRoot.Properties.MessageSet = 'GB77QOG002001';'' at ('.XTOCW_Compute.Main', '9.4').
2009-07-12 23:26:07.466461 3152 UserTrace BIP2566I: Node 'XTOCW.Compute': Assigning value '''GB77QOG002001''' to field / variable ''OutputRoot.Properties.MessageSet''.
2009-07-12 23:26:07.466505 3152 UserTrace BIP2537I: Node 'XTOCW.Compute': Executing statement ''SET OutputRoot.Properties.MessageFormat = 'CWF';'' at ('.XTOCW_Compute.Main', '10.4').
2009-07-12 23:26:07.466544 3152 UserTrace BIP2566I: Node 'XTOCW.Compute': Assigning value '''CWF''' to field / variable ''OutputRoot.Properties.MessageFormat''.
2009-07-12 23:26:07.466588 3152 UserTrace BIP2537I: Node 'XTOCW.Compute': Executing statement ''RETURN TRUE;'' at ('.XTOCW_Compute.Main', '12.3').
2009-07-12 23:26:07.466692 3152 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'XTOCW.Compute'.
2009-07-12 23:26:07.528137 3152 UserTrace BIP2638I: The MQ output node 'XTOCW.MQOutput' attempted to write a message to queue ''D'' connected to queue manager ''''. The MQCC was '0' and the MQRC was '0'.
2009-07-12 23:26:07.528190 3152 UserTrace BIP2622I: Message successfully output by output node 'XTOCW.MQOutput' to queue ''D'' on queue manager ''''.
2009-07-12 23:27:01.705924 5804 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2009-07-12 23:27:01.706009 5804 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'.
2009-07-12 23:27:01.706033 5804 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.
2009-07-12 23:27:01.706086 5804 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '244' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
Threads encountered in this trace:
3152 5804 |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Jul 13, 2009 6:33 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
There are a number of things that are fairly obvious to identify.
CWF should be the Physical Format name you have specified when creating your message set. This is usually CWF1.
THe error message says
| Quote: |
2009-07-12 23:26:07.465826 3152 UserTrace BIP2543I: Node 'XTOCW.Compute': ('.XTOCW_Compute.Main', '6.25') : Failed to navigate to path element number '2' because it does not exist.
|
after the statement
| Code: |
SET OutputRoot.MRM = InputRoot.XMLNSC.Customer;
|
And after you have copied the entire message. Hmmmmm. This is wrong. You already have a fully populated set of folders in OutputRoot.
I think you certainly need to get some training in message broker. These are pretty elementary errors.
The field InputRoot.XMLNSC.Customer plainly does not exist as is shown in the next two lines in the trace
| Quote: |
2009-07-12 23:26:07.465865 3152 UserTrace BIP2539I: Node 'XTOCW.Compute': Evaluating expression ''InputRoot.XMLNSC.Customer'' at ('.XTOCW_Compute.Main', '6.25'). This resolved to ''InputRoot.XMLNSC.Customer''. The result was ''EMPTY ROW''.
2009-07-12 23:26:07.465908 3152 UserTrace BIP2567I: Node 'XTOCW.Compute': Assigning NULL to ''OutputRoot.MRM'', thus deleting it.
|
I think you certainly need to get some training in message broker.
_________________
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 |
|
|
| tanishka |
| Posted: Tue Jul 14, 2009 7:17 am Post subject: |
|
|
Centurion
Joined: 24 Nov 2008
Posts: 144
|
| Yes. I have to take training.Thanks.. |
|
| 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
|
|
|
|
