Author |
Message
|
prithvik |
Posted: Wed Apr 17, 2013 1:26 am Post subject: MQHRF2 header is coming |
|
|
Novice
Joined: 17 Apr 2013 Posts: 11
|
using WPS with MQ, in mediation flow MQHeader -control-Format , we are setting to MQSTR , but still message is going to queue with MQHRF2 header
and following properties are going
<usr><JMSXDeliveryCount dt="i4">1</JMSXDeliveryCount><JMSXAppID dt="string">Service Integration Bus</JMSXAppID><JMSXUserID dt="string">SCA</JMSXUserID></usr> How to remove these and MQHRF2 should not come, what i need to do in SMO mediation flow or any setting is needed in Import |
|
Back to top |
|
|
fjb_saper |
Posted: Wed Apr 17, 2013 2:32 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003 Posts: 20729 Location: LI,NY
|
Add the property targetClient=1 to the Destination at the message producer ?
Or change the propctl property of the queue?
As I would expect you to be using JMS, you should not be doing anything as the JMS client will handle the RFH header for you.... _________________ MQ & Broker admin |
|
Back to top |
|
|
prithvik |
Posted: Wed Apr 17, 2013 3:02 am Post subject: |
|
|
Novice
Joined: 17 Apr 2013 Posts: 11
|
Thank you very much for reply. We are not using JMS any way will try this option |
|
Back to top |
|
|
prithvik |
Posted: Wed Apr 17, 2013 3:06 am Post subject: |
|
|
Novice
Joined: 17 Apr 2013 Posts: 11
|
I have not able to see propctl property of the queue in process server admin console. Where else we can set this property. We are using SMO mediation to place the message to queue. Thanks in advance. |
|
Back to top |
|
|
fjb_saper |
Posted: Wed Apr 17, 2013 3:10 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003 Posts: 20729 Location: LI,NY
|
prithvik wrote: |
Thank you very much for reply. We are not using JMS any way will try this option |
What do you mean you are not using JMS? How else are you getting the message off the queue? _________________ MQ & Broker admin |
|
Back to top |
|
|
prithvik |
Posted: Wed Apr 17, 2013 3:14 am Post subject: |
|
|
Novice
Joined: 17 Apr 2013 Posts: 11
|
|
Back to top |
|
|
fjb_saper |
Posted: Wed Apr 17, 2013 3:18 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003 Posts: 20729 Location: LI,NY
|
prithvik wrote: |
we are using MQ not JMS. |
From within a J2EE app server? _________________ MQ & Broker admin |
|
Back to top |
|
|
prithvik |
Posted: Wed Apr 17, 2013 3:23 am Post subject: |
|
|
Novice
Joined: 17 Apr 2013 Posts: 11
|
in websphere process server , we configured the queues.., these queues are maintained by external vendor. they not process MQRFH2 headers, |
|
Back to top |
|
|
fjb_saper |
Posted: Wed Apr 17, 2013 3:30 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003 Posts: 20729 Location: LI,NY
|
prithvik wrote: |
in websphere process server , we configured the queues.., these queues are maintained by external vendor. they not process MQRFH2 headers, |
You can suppress the RFH header in JMS by passing the destination information in URI form:
queuename = "queue://qmgrname/qname?targetClient=1" or
queuename = "queue:///qname?targetClient=1"
Have fun _________________ MQ & Broker admin |
|
Back to top |
|
|
prithvik |
Posted: Wed Apr 17, 2013 3:37 am Post subject: |
|
|
Novice
Joined: 17 Apr 2013 Posts: 11
|
do not take me wrong... where we need to set this ? is it possible to set to SMO ? |
|
Back to top |
|
|
mqjeff |
Posted: Wed Apr 17, 2013 5:04 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Show us the code that is creating and sending the message. |
|
Back to top |
|
|
vmcgloin |
Posted: Wed Apr 17, 2013 5:06 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002 Posts: 560 Location: Scotland
|
prithvik wrote: |
do not take me wrong... where we need to set this ? is it possible to set to SMO ? |
Not in the SMO (service message object) but instead in WAS where you configure the outbound queue name. |
|
Back to top |
|
|
prithvik |
Posted: Thu Apr 18, 2013 10:40 pm Post subject: |
|
|
Novice
Joined: 17 Apr 2013 Posts: 11
|
This issue is solved and the solution is we added the property contextPropagationEnabled="false"
in the MQImport
<esbBinding xsi:type="MQ:MQImportBinding" contextPropagationEnabled="false">
Thanks all for your suggestion |
|
Back to top |
|
|
|