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 » IBM MQ Java / JMS » Design issue related to MQ Trigger

Post new topic  Reply to topic
 Design issue related to MQ Trigger « View previous topic :: View next topic » 
Author Message
rraam75
PostPosted: Tue Apr 04, 2006 11:30 pm    Post subject: Design issue related to MQ Trigger Reply with quote

Novice

Joined: 18 Mar 2006
Posts: 14

Hello All,
We have webspheremq6 version to be run in windows2000. We expect to get 20000 messages perday in our queue. My question is

1. Is it good, to design in such a way to make queue as a trigger queue that will invoke an application to pick the message from the queue and reformat the message and put in a another remote queue. (or) to write an infinite program which keeps on monitoring the queue depth and gets the message from the queue process it and loop it back again to get the message again?

2. Let's say at a time 50 messages are populated in my local queue, then would 50 instances of my application will be running?

3. Is there is any impact if more and more instances are running even if the triggering program goes to end after it completes it job like processing the message and putting to another queue?

4. What precaution we have to take while writing the trigger program?

Thanks a lot in advance.
Back to top
View user's profile Send private message
fschofer
PostPosted: Wed Apr 05, 2006 12:20 am    Post subject: Reply with quote

Knight

Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany

Hi,

rraam75 wrote:
to write an infinite program which keeps on monitoring the queue depth and gets the message from the queue process it and loop it back again to get the message again?

for this look here on "Waiting for messages"
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/topic/com.ibm.mq.csqzal.doc/waitmsg.htm

Greetings
Frank
Back to top
View user's profile Send private message Send e-mail
wschutz
PostPosted: Wed Apr 05, 2006 1:38 am    Post subject: Reply with quote

Jedi Knight

Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)

jeff had put together a nice summary on "triggering topics", it would be good for you to browse some of that, I think you'd get some good ideas:

http://www.mqseries.net/phpBB2/viewtopic.php?p=112118
_________________
-wayne
Back to top
View user's profile Send private message Send e-mail AIM Address
vennela
PostPosted: Wed Apr 05, 2006 4:26 am    Post subject: Reply with quote

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India

Quote:
2. Let's say at a time 50 messages are populated in my local queue, then would 50 instances of my application will be running?

No
If you set it up right, only one will be running
Back to top
View user's profile Send private message Send e-mail Visit poster's website
rraam75
PostPosted: Wed Apr 05, 2006 4:55 am    Post subject: Reply with quote

Novice

Joined: 18 Mar 2006
Posts: 14

Thanks All for the suggestion.

venella, I think that we will have 50 instance running when i set the trigger type as "EVERY". If iam not right pls correct me.

From all your experience, do you think to have trigger type as "EVERY" is right decision with a expectation of 20000 messages in a 12 hrs period
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Apr 05, 2006 4:59 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

rraam75 wrote:
From all your experience, do you think to have trigger type as "EVERY" is right decision with a expectation of 20000 messages in a 12 hrs period


TriggerType Every is almost never the right decision in any circumstances.

That doesn't mean I haven't implemented it... just that it wasn't the right idea...
_________________
I am *not* the model of the modern major general.


Last edited by jefflowrey on Wed Apr 05, 2006 6:44 am; edited 1 time in total
Back to top
View user's profile Send private message
zpat
PostPosted: Wed Apr 05, 2006 6:39 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

Trigger on First, then have that program process the messages in the queue until it is empty.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Apr 05, 2006 12:01 pm    Post subject: Reply with quote

Grand High Poobah

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

Or trigger on type every and have the program share an area and check how many instances are active and limit the number of those instances by config. This will limit the amount of resources involved but allow parallel processing of your queue.

Enjoy
_________________
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 » IBM MQ Java / JMS » Design issue related to MQ Trigger
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.