| Author |
Message
|
| mrgate |
 Posted: Mon Jan 28, 2008 11:59 am Post subject: MESSAGE EXPIRY AT REGULAR INTERVALS. |
 |
|
Centurion
Joined: 28 Feb 2007
Posts: 141
Location: India
|
Hello All,
I am working with websphere MQ on wnidows platform.
In my interface, there is a need for deleting messages after a specified interval when the message enters into a queue. Is there any possibility for this without programming.
_________________
MQSeries terrorist |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Jan 28, 2008 12:22 pm Post subject: Re: MESSAGE EXPIRY AT REGULAR INTERVALS. |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mrgate wrote: |
| there is a need for deleting messages after a specified interval when the message enters into a queue. Is there any possibility for this without programming. |
Well you're right - setting message expiry will delete a message after a specified interval! 
No additional programming is needed after the MQMD field has been set. The queue manager will deal with it internally.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mrgate |
| Posted: Mon Jan 28, 2008 12:42 pm Post subject: |
|
|
Centurion
Joined: 28 Feb 2007
Posts: 141
Location: India
|
Thanx Mr vitor. The actual requirement for me is that setting expiration for every message in the queue after message was entered into queue
_________________
MQSeries terrorist |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jan 28, 2008 12:44 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The only way to adjust a message "entered into queue" is to GET it and then PUT it again.
The only way to do that is with a program.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mrgate |
| Posted: Mon Jan 28, 2008 12:48 pm Post subject: |
|
|
Centurion
Joined: 28 Feb 2007
Posts: 141
Location: India
|
Thanx Jeoff, Final conclusion about my interface is that rather than doing my interface using IBM's technologies like WBI message broker and websphere mq, I should go to websphere process server.
_________________
MQSeries terrorist |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jan 28, 2008 12:50 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
That's a ridiculous conclusion to draw from the few facts you have mentioned.
You could, for example, write a message flow in WMB that would do this.
but that would still count as "a program".
And anything you wrote in WPS would count as "a program".
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mrgate |
| Posted: Mon Jan 28, 2008 12:55 pm Post subject: |
|
|
Centurion
Joined: 28 Feb 2007
Posts: 141
Location: India
|
jeoff, I have already posted about my roblem using message broker. You can see from http://www.mqseries.net/phpBB2/viewtopic.php?t=41539. Instead of setting that one in MB I thought of having any possibility in websphere mq. But here I did not find any solution. Thats why I have given the previous statement.
_________________
MQSeries terrorist |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jan 28, 2008 1:01 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Regardless of any other thread, nothing you have posted here says anything that justifies using WPS - or even says that you can fix things using WPS.
If some application is sending messages without an expiry, the only way to change the expiry is to change the message. The only way to do that is with a program of some kind.
A simple example would be an MB message flow that had an MQInput->Compute->MQOutput, that changed the expiry.
If you are concerned with trying to clean up responses that arrive after a timeout interval, you can for example send a message to another flow that contains enough information on how to pluck out the "orphaned" response.
Or you can log the same information into a db or etc. and have a process that runs periodically to clean those up.
Or you can do the right thing, and configure the responding side to set an Expiry.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mrgate |
| Posted: Mon Jan 28, 2008 1:09 pm Post subject: |
|
|
Centurion
Joined: 28 Feb 2007
Posts: 141
Location: India
|
| jefflowrey wrote: |
Regardless of any other thread, nothing you have posted here says anything that justifies using WPS - or even says that you can fix things using WPS.
If some application is sending messages without an expiry, the only way to change the expiry is to change the message. The only way to do that is with a program of some kind.
A simple example would be an MB message flow that had an MQInput->Compute->MQOutput, that changed the expiry.
If you are concerned with trying to clean up responses that arrive after a timeout interval, you can for example send a message to another flow that contains enough information on how to pluck out the "orphaned" response.
Or you can log the same information into a db or etc. and have a process that runs periodically to clean those up.
Or you can do the right thing, and configure the responding side to set an Expiry. |
jeoff, my target system is SAP. To interact with SAP, I have used SAP adapter. Now, I am getting the response set with the given value in input but after the message was inserted into queue, I could see expiry set to -1 i.e., unlimited. How can I resolve this.
_________________
MQSeries terrorist |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jan 28, 2008 2:34 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Check out the SAP adapter information. Likely you are not going to be able to do this without some flow. Most messages to/from SAP are persistent and do not expire.
I would question on an architect level why you would want your SAP messages to expire...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
