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 MQ Java / JMS » MQRFH2 vs MQSTR

Post new topic  Reply to topic
 MQRFH2 vs MQSTR « View previous topic :: View next topic » 
Author Message
70033
PostPosted: Fri Sep 10, 2010 1:52 pm    Post subject: MQRFH2 vs MQSTR Reply with quote

Apprentice

Joined: 22 Dec 2008
Posts: 27

I understand that MQRFH2 is to be used when the target client is JMS and the MQRFH2 adds JMS specific fields like JMSDestination,etc to the message.

My question is if i were to send it in this format and if i have a MDB listening on the queue when it does a get will it get the message without all the header information . I am referring to some extra characters that i see in the MQ explorer when i browse the message. If consumed by a java MDB consumer will i still see this extra characters or will i get the message that i originally put..
Back to top
View user's profile Send private message
Gaya3
PostPosted: Fri Sep 10, 2010 2:37 pm    Post subject: Re: MQRFH2 vs MQSTR Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2350
Location: Boston, US

70033 wrote:
I understand that MQRFH2 is to be used when the target client is JMS and the MQRFH2 adds JMS specific fields like JMSDestination,etc to the message.
..


I do not agree completely with you, as you can even pass in MQRFH2 information for different business scenarios as well.

say you would like to pass user id, or file name details to the target location or even to another broker flow a kind of

70033 wrote:

My question is if i were to send it in this format and if i have a MDB listening on the queue when it does a get will it get the message without all the header information . I am referring to some extra characters that i see in the MQ explorer when i browse the message. If consumed by a java MDB consumer will i still see this extra characters or will i get the message that i originally put..

you can configure your MDB to fetch only the payload
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Sep 10, 2010 6:37 pm    Post subject: Reply with quote

Grand Poobah

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

Read up if you can about linked headers and experiment more with JMS.
A little experimentation would immediately answer your question...
And lucky for you, to prove a concept and experiment you can use JMS in a standalone little app.

Yes there are a few caveats of standalone vs J2EE appserver, but looking at the big picture you can model nearly everything in a standalone app.

Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
70033
PostPosted: Mon Sep 13, 2010 7:56 am    Post subject: Reply with quote

Apprentice

Joined: 22 Dec 2008
Posts: 27

I shouldnt have specified mdb in this question actually.. if i had a java consumer(a JMS program doing a get) then would the JMS program need to worry whether the request was send in a MQRFH2 or a MQSTR format?
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Sep 13, 2010 8:06 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 21407
Location: Ohio, USA

70033 wrote:
. if i had a java consumer(a JMS program doing a get) then would the JMS program need to worry whether the request was send in a MQRFH2 or a MQSTR format?


Yes. If the application doing the get is using JMS and the message doesn't have a MQRFH2 header many of the JMS properties will be missing. How the receiving application reacts to that is a question of coding; assuming the JMS layer would even pass the message to the consuming application (a question I'll leave to more experienced posters).

Answering your original question, the format of the message (extra characters or not) is opaque to the reading application.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Sep 13, 2010 12:14 pm    Post subject: Reply with quote

Grand Poobah

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

70033 wrote:
I shouldnt have specified mdb in this question actually.. if i had a java consumer(a JMS program doing a get) then would the JMS program need to worry whether the request was send in a MQRFH2 or a MQSTR format?

It really depends now on the content of the MQFRH2 format field, doesn't it?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere MQ Java / JMS » MQRFH2 vs MQSTR
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.