ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Odd mcd/Msd folder in WMB V6.1.0.9

Post new topic  Reply to topic
 Odd mcd/Msd folder in WMB V6.1.0.9 « View previous topic :: View next topic » 
Author Message
murdeep
PostPosted: Thu Aug 04, 2011 12:44 pm    Post subject: Odd mcd/Msd folder in WMB V6.1.0.9 Reply with quote

Master

Joined: 03 Nov 2004
Posts: 211
Hello, before I open a PMR with IBM on this I thought I'd post here to see if I am doing something wrong. I'm playing with subscribing to WMB configuration change events.

I set up the following subscriptions:

$SYS/Broker/+/Status
$SYS/Broker/+/Status/ExecutionGroup/#
$SYS/Broker/+/Configuration/ExecutionGroup/#

I have a WMB flow that will read the messages that get published.

I then receive the following message (amsbcg dump):

MQGET of message number 1
****Message descriptor****

StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 546 CodedCharSetId : 1208
Format : 'MQHRF2 '
Priority : 0 Persistence : 0
MsgId : X'414D5120515348534254303220202020262E2F4E20005532'
CorrelId : X'414D51580000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'QMGRBT00 '
** Identity Context
UserIdentifier : 'userid '
AccountingToken :
X'16010515000000AB2BE9904788DC8456B5CD209B86030000000000000000000B
ApplIdentityData : ' '
** Origin Context
PutApplType : '26'
PutApplName : 'BKRBT00 '
PutDate : '20110804' PutTime : '19121990'
ApplOriginData : ' '

GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'

**** Message ****

length - 326 bytes

00000000: 5246 4820 0200 0000 D000 0000 2202 0000 'RFH ........"...'
00000010: B804 0000 2020 2020 2020 2020 0000 0000 '.... ....'
00000020: B804 0000 8800 0000 3C70 7363 3E3C 436F '....ê...<psc><Co'
00000030: 6D6D 616E 643E 5075 626C 6973 683C 2F43 'mmand>Publish</C'
00000040: 6F6D 6D61 6E64 3E3C 5075 624F 7074 3E52 'ommand><PubOpt>R'
00000050: 6574 6169 6E50 7562 3C2F 5075 624F 7074 'etainPub</PubOpt'
00000060: 3E3C 5075 624F 7074 3E4F 7468 6572 5375 '><PubOpt>OtherSu'
00000070: 6273 4F6E 6C79 3C2F 5075 624F 7074 3E3C 'bsOnly</PubOpt><'
00000080: 546F 7069 633E 2453 5953 2F42 726F 6B65 'Topic>$SYS/Broke'
00000090: 722F 4248 5342 5430 302F 5374 6174 7573 'r/BKRBT00/Status'
000000A0: 3C2F 546F 7069 633E 3C2F 7073 633E 2020 '</Topic></psc> '
000000B0: 1C00 0000 3C6D 6364 3E3C 4D73 643E 786D '....<mcd><Msd>xm'
000000C0: 6C73 3C2F 4D73 643E 3C2F 6D63 643E 2020 'ls</Msd></mcd> '
000000D0: 3C42 726F 6B65 7220 7575 6964 3D22 3662 '<Broker uuid="6b'
000000E0: 3432 6266 3762 2D31 3130 312D 3030 3030 '42bf7b-1101-0000'
000000F0: 2D30 3038 302D 6137 3064 3963 3331 3637 '-0080-a70d9c3167'
00000100: 3236 2220 6C61 6265 6C3D 2253 4853 4254 '26" label="BKRBT'
00000110: 3030 2220 7665 7273 696F 6E3D 2231 223E '00" version="1">'
00000120: 3C53 7461 7475 7343 6861 6E67 6520 6E65 '<StatusChange ne'
00000130: 773D 2253 7461 7274 6564 222F 3E3C 2F42 'w="Started"/></B'
00000140: 726F 6B65 723E 'roker> '

Notice the <mcd><Msd>xmls</Msd></mcd>. In my V7 WMB test bed this shows as <mcd><Msd>xmlnsc</Msd></mcd>. This is where I developed the message flow and as a result I coded the ESQL to be (InputRoot.XMLNSC.---) So when this runs in V6.1.0.9 it fails since the logical tree is now (InputRoot.XMLS.---)

Also, the <mcd><Msd> for messages that get published to the queue associated with the $SYS/Broker/+/Status/ExecutionGroup/#
subscription have the Msd set as xml i.e. <mcd><Msd>xml</Msd></mcd>. Which again is odd imo.

So I have a few questions. Is the setting of mcd/Msd by WMB here a bug? Is there a way to turn the creation of the mcd/Msd off via a sub option perhaps? Is there a way I force the message flow consuming these messages to ignore the mcd/Msd and use the parser I specify on the MQInput node to parse the data following the RFH?

Regards
Back to top
View user's profile Send private message
smdavies99
PostPosted: Thu Aug 04, 2011 9:32 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
Two points

1) You can easily test (in ESQL) for the broker version you are running on. Look at the bit of the infocentre that deals with things like BrokerName etc.
Then you can code a reference to use .XMLNS or .XMLNSC as appropriate

2) Instead of using InputRoot.XMLNSC or InputRoot.XMLNS how about using InputBody?

The problem you are seeing is not that difficult to overcome with a little thought.

Finally
Quote:
So I have a few questions. Is the setting of mcd/Msd by WMB here a bug? Is there a way to turn the creation of the mcd/Msd off via a sub option perhaps? Is there a way I force the message flow consuming these messages to ignore the mcd/Msd and use the parser I specify on the MQInput node to parse the data following the RFH?


Simply no there is not. The data in the mcf folder will always override the setting in the InputNode.
This allows you to define the exact message defs (MessageSet etc) in the message payload.
Personally, I don't like it due to the fact that you can cause a flow to barf by specifying a MessageSet that does not exist. As with almost everything, there are good and bad points about doing most things. I raised this point here some 5+ years ago.
_________________
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
View user's profile Send private message
murdeep
PostPosted: Fri Aug 05, 2011 7:48 am    Post subject: Reply with quote

Master

Joined: 03 Nov 2004
Posts: 211
Ok, using InputBody won't work in this example since I'm accessing attributes and how those are referenced in the ESQL is domain dependent (which I think is odd).

What I decided to do is simply preprocess the publication in a compute node to remove the RFH and just pass the body through. I then use a RCD to set the domain to XMLNSC and then process the message.

In any case I still think the Mcd of xmls is a bug. Has anyone ever seen any doc on a WMB xmls domain/parser? Only ones I know of are xml, xmlns and xmlnsc - but no xmls.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Odd mcd/Msd folder in WMB V6.1.0.9
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.