Posted: Thu Sep 29, 2011 8:30 am Post subject: Is it possible to have WMB ignore the MQHRF2 format?
Master
Joined: 03 Nov 2004 Posts: 211
Hi, I don't think this is as crazy as it sounds in the subject title.
We have a message flow that we route messages to in order to log messages into a database, our message warehouse. Our message warehouse consists of a table that contains the MQMD attributes as the parent that has a foreign key relationship to a payload table.
We have introduced a JMS application and when we process the message through our logging flow only the actual payload that follows the RFH is logged which makes sense since the RFH is really not part of the application payload.
What I'd like to do is log then entire message buffer from a WMQ perspective so that would include the RFH. So I am trying to figure out how to get WMB to ignore the MQHRF2 format.
The only thing I can think of is a non-WMB MQ app that would preprocess the message before we route it to the WMB logging flow that sets the MQMD.Format to something other that MQHRF2 (i.e. MQFMT_NONE) but I'd like to see if we can do it in WMB so I avoid having this application external to the broker.
Any suggestions? is it even possible to do in WMB or does WMB always recognize the MQHRF2 format if it is set?
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
Broker follows whatever MQ tells it.
IF the MQMD.Format = MQSTR then everything after the end of the MQMD is reated as the message payload.
If the MQMD.Format contains something else (eg MQRFH2) then the header is chained to the MQMD.
And so on thein there is something in the .Format field that says, 'The next thingy is the payload data and not another header'.
broker will read the WMQ message and format the various headers automatically.
When I've been storing in a DB messages that may or may not contain an MQRFH2 header I've always allocaed a BLOB (or similar) for both the MQMD, the MQRFH2 and the Unparsed data.
Bear in mind that if the MCD folder contains message set data then broker in its infinite wisdom will try to parse the message with that rather than the model defined in the input node. _________________ 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.
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