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 » General IBM MQ Support » MQ in leagcy and JMS compliant mode

Post new topic  Reply to topic Goto page Previous  1, 2
 MQ in leagcy and JMS compliant mode « View previous topic :: View next topic » 
Author Message
IvanPetroff
PostPosted: Fri Jan 20, 2012 12:37 pm    Post subject: Reply with quote

Newbie

Joined: 07 Jan 2012
Posts: 7

Hi guys,

How can I validate that the message meta-data of on sending side is the same as the meta-data on the receiving side, i mean is there any MQ message viewer or message dumper that also shows/dumps message with the meta-data.
The queue browser shows only basic information. I found the dumper that is located in mq_root_dir/tools/c/samples but the tool dumps the same information.

Thanks and Regards
Back to top
View user's profile Send private message
bruce2359
PostPosted: Fri Jan 20, 2012 12:45 pm    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.

Meta-data? Are you talking about message properties?

If so, these should be perfectly displayed with amqsbcg on Windows and UNIX.

Please post an example of what you do see, and which utility you executed to see it.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
IvanPetroff
PostPosted: Sat Jan 21, 2012 3:39 am    Post subject: Reply with quote

Newbie

Joined: 07 Jan 2012
Posts: 7

That is the message dump on the MQ side:
AMQSBCG0 - starts here
**********************

MQOPEN - 'QUEUE_TEST'


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

StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 273 CodedCharSetId : 1208
Format : 'MQSTR '
Priority : 4 Persistence : 1
MsgId : X'414D5120616C7068612E71756575652EF4810D4F206D9203'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'saturn.queue.manager '
** Identity Context
UserIdentifier : 'Administrator'
AccountingToken :
X'1601051500000087BC9944533A8875A137AEDBF401000000000000000000000B'
ApplIdentityData : ' '
** Origin Context
PutApplType : '28'
PutApplName : 'WebSphere MQ Client for Java'
PutDate : '20120121' PutTime : '11303812'
ApplOriginData : ' '

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

**** Message ****

length - 136 bytes

... Some text ...
... Some text ...
... Some text ...


No more messages
MQCLOSE
MQDISC



The problem is that some properties that are set to message on the sending side missing on the receiving side.
e.g. On sending side i set a custom message property
CustomCorrelationID=ABCD1234

but as you can see, the dump shows that this property is missing
Back to top
View user's profile Send private message
mvic
PostPosted: Sat Jan 21, 2012 8:20 am    Post subject: Reply with quote

Jedi

Joined: 09 Mar 2004
Posts: 2080

IvanPetroff wrote:
e.g. On sending side i set a custom message property
CustomCorrelationID=ABCD1234

but as you can see, the dump shows that this property is missing


Maybe it's encoded somewhere in the

Code:
   ... Some text ...
   ... Some text ...
   ... Some text ...

You certainly shouldn't expect that something called "CustomCorrelationID" should end up in the MQMD.
Back to top
View user's profile Send private message
Vitor
PostPosted: Sat Jan 21, 2012 9:54 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

The amqsbcg is a sample that predates the WMQv7 message properties so probably has no code to display them. Certainly (as my worthy associate points out) they're not in the MQMD. Thankfully as it's a sample you can easily modify it to meet your needs.

One of the sample pacs that's been modified to include v7 message property support (and I'm too lazy to research if any of them have) would be an alternative.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Esa
PostPosted: Wed Jan 25, 2012 3:39 am    Post subject: Reply with quote

Grand Master

Joined: 22 May 2008
Posts: 1387
Location: Finland

RFHUtil
Back to top
View user's profile Send private message
IvanPetroff
PostPosted: Sat Feb 25, 2012 1:34 pm    Post subject: Reply with quote

Newbie

Joined: 07 Jan 2012
Posts: 7

Hi guys,
Thanks to everyone for their help!
Thanks and Regards
Back to top
View user's profile Send private message
IvanPetroff
PostPosted: Sat Mar 10, 2012 4:00 pm    Post subject: Reply with quote

Newbie

Joined: 07 Jan 2012
Posts: 7

mvic wrote:
IvanPetroff wrote:
e.g. On sending side i set a custom message property
CustomCorrelationID=ABCD1234

but as you can see, the dump shows that this property is missing


Maybe it's encoded somewhere in the

Code:
   ... Some text ...
   ... Some text ...
   ... Some text ...

You certainly shouldn't expect that something called "CustomCorrelationID" should end up in the MQMD.

@mvic:
Where I should expect this property?
Any idea how I can check that the property exists?
I have tried to find it with the RFHUtil but without any success.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sat Mar 10, 2012 4:21 pm    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.

IvanPetroff wrote:


**** Message ****

length - 136 bytes

... Some text ...
... Some text ...
... Some text ...


Message properties are part of the application message data payload - the
... Some text ...
... Some text ...
... Some text ...

and should look xml-ish, with <hdr> and </hdr> bracketing.

Look here: http://www-01.ibm.com/support/docview.wss?uid=swg27017014

I commend you to google. Ask it 'mq+how to view message properties'
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sun Mar 11, 2012 2:24 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

If you are not yet on V7 it would have to go onto the RFH2 header, and I believe you are suppressing it... Is SAP XI doing anything to set the customcorrelid on the MQ message?

The latest version of RFHUtil (support pack IH03 IIRC) will be able to show you the properties in V7 style or RFH style... depending on queue settings.

Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
mvic
PostPosted: Sun Mar 11, 2012 1:24 pm    Post subject: Reply with quote

Jedi

Joined: 09 Mar 2004
Posts: 2080

IvanPetroff wrote:
Where I should expect this property?

Read through the page bruce gave. Probably it answers this.
Back to top
View user's profile Send private message
IvanPetroff
PostPosted: Mon Mar 12, 2012 2:39 am    Post subject: Reply with quote

Newbie

Joined: 07 Jan 2012
Posts: 7

fjb_saper wrote:
If you are not yet on V7 it would have to go onto the RFH2 header, and I believe you are suppressing it... Is SAP XI doing anything to set the customcorrelid on the MQ message?

The latest version of RFHUtil (support pack IH03 IIRC) will be able to show you the properties in V7 style or RFH style... depending on queue settings.

Have fun


I'm still using MQ v6.2 and you are right - the RFH2 is suppressed.
Maybe I shouldn't use MQSTR format and I'll remove these settings:
MQDestination.setTargetClient(JMSC.MQJMS_CLIENT_NONJMS_MQ)
MQConnectionFactory.setTargetClientMatching(true)
I'll test this changes now.

Is SAP XI doing anything to set the customcorrelid on the MQ message?
Yes, the system add this correlationid to the JMS message header part.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » General IBM MQ Support » MQ in leagcy and JMS compliant mode
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.