Author |
Message
|
fitzcaraldo |
Posted: Wed Mar 31, 2004 5:17 pm Post subject: RFH2 mcd issue |
|
|
Voyager
Joined: 05 May 2003 Posts: 98
|
We have a series of flows that pass context information via the RFH2.
For example we have a generic split flow that breaks large messages into smaller parts and then forwards them to a separate flow for further processing.
We want the secondary flow to pick up the message and parse according to a nominated Domain. For this reason we want the split flow to be format neutral (or more specifically - set the RFH2 mcd field to be empty).
The assumption was that if we generate the outgoing split messages as BLOB then the mcd field will be empty and the following input node would parse according to the provided Domain. However, the mcd field is always set to 'none' which is interpreted by the input node to be BLOB.
Is there any way in MQOutput processing that we can either remove the mcd folder of the RFH2 or set it to ' '? |
|
Back to top |
|
 |
Michael Dag |
Posted: Wed Mar 31, 2004 11:23 pm Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
|
Back to top |
|
 |
MiLi |
Posted: Thu Nov 24, 2005 2:12 am Post subject: |
|
|
Acolyte
Joined: 07 Oct 2005 Posts: 51
|
Am I Correct if that didnt solve your problem!
I have the same problem
I have a flow that has an Input node thats connected to a Message Set.
But if a use an RFH2 header and send an xml to this flow it will ignore the message set on input and be treated as XML.
So I want to be able to use the RFH2 header without the feature that it will overide the MQInput properties.
I tried to remove the mcd field but it didnt work!
Pleas post you solotion if you solved this! |
|
Back to top |
|
 |
Tibor |
Posted: Thu Nov 24, 2005 5:45 am Post subject: |
|
|
 Grand Master
Joined: 20 May 2001 Posts: 1033 Location: Hungary
|
|
Back to top |
|
 |
MiLi |
Posted: Mon Jan 30, 2006 7:04 am Post subject: Solution |
|
|
Acolyte
Joined: 07 Oct 2005 Posts: 51
|
Solution:
Just send the message in the BLOB domain. That will make the input node act like "normal". _________________ IBM Certified System Administrator - WebSphere MQ V6.0
IBM Instructor - WebSphere MQ, WebSphere Message Broker |
|
Back to top |
|
 |
MiLi |
Posted: Fri Feb 17, 2006 4:35 am Post subject: |
|
|
Acolyte
Joined: 07 Oct 2005 Posts: 51
|
Sorry!
This is not working as I thought.
If someone have a solution to this problem, please post!
The issue I'm having is how to add message properties to a message like in the mqrfh2 usr, except getting the mqrfh2 behaviour that the next broker flow will parse the message according to mqrfh2 mcd rather than the inputNode properties.
Is there any way to set the outgoing message to 'jms_text' ? _________________ IBM Certified System Administrator - WebSphere MQ V6.0
IBM Instructor - WebSphere MQ, WebSphere Message Broker |
|
Back to top |
|
 |
MiLi |
Posted: Fri Feb 17, 2006 6:43 am Post subject: |
|
|
Acolyte
Joined: 07 Oct 2005 Posts: 51
|
Allright, another try on a soultion
Just like in:
http://www.mqseries.net/phpBB2/viewtopic.php?t=21477&highlight=jmstext
Use a ContentRestetDescriptor to jms_text and the following flow will parse the incoming message accoring to its node properties. _________________ IBM Certified System Administrator - WebSphere MQ V6.0
IBM Instructor - WebSphere MQ, WebSphere Message Broker |
|
Back to top |
|
 |
|