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 » General IBM MQ Support » Why does this trigger configuration not work?

Post new topic  Reply to topic
 Why does this trigger configuration not work? « View previous topic :: View next topic » 
Author Message
guenter1978
PostPosted: Mon Jan 24, 2005 7:57 am    Post subject: Why does this trigger configuration not work? Reply with quote

Novice

Joined: 21 Jan 2005
Posts: 12
Location: Austria

Hello,

I tried to configure a trigger in MQ Series. Sadly this trigger does not work the way I think it should.

I am using WebSphere 5.3 service level 8 on Windows 2000.

I installed Server and Client on the same win2000 host.

I installed a queue manager named QM_gspc and created to local queues. One named applicaktion.queue and the other initiation.queue.

The queues was created by following command:
Quote:
DEFINE QLOCAL('application.queue') REPLACE LIKE(SYSTEM.DEFAULT.LOCAL.QUEUE) DESCR(
'appl queue description') INITQ(INITIATION.QUEUE) TRIGGER TRIGT
YPE(every)

DEFINE QLOCAL('initiation.queue') REPLACE LIKE (SYSTEM.DEFAULT.LOCAL.QUEUE) DESCR(
'initiation queue description')


I used the api testprogram provided by the installation of WebSphere MQ for putting messages into the application.queue. I supposed that there will be a message created in 'initiation.queue', but when I looked into this queue (using MQExplorer) its empty.

Did I miss something?
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Mon Jan 24, 2005 8:00 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

There is a long set of conditions that must be met before a trigger message is created.

The one you are most likely missing is that you have to have a trigger monitor running against the initiation queue, to cause the initiation queue to have an Open Input Count that is greater than 1.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
guenter1978
PostPosted: Mon Jan 24, 2005 8:08 am    Post subject: Reply with quote

Novice

Joined: 21 Jan 2005
Posts: 12
Location: Austria

Thank you for your fast answer.

I tried to hold the 'initiation.queue' OpenInputCounter greater than 1 by using the api test program. I simply opened this queue and started a second instanz of this test program and putted message on 'application.queue', but sadly still nothing happened to 'initiation.queue'.

Is there any way to test this, without implementing a trigger monitor or is there a simple one already supplied by WebSphere MQ?
Back to top
View user's profile Send private message
Nigelg
PostPosted: Mon Jan 24, 2005 8:26 am    Post subject: Reply with quote

Grand Master

Joined: 02 Aug 2004
Posts: 1046

There is a simple trigger monitor already supplied, called runmqtrm.

The syntax is
Code:
runmqtrm -m QMGR -q INITQ

The app runs in the foreground, writing status messages to its concole.

I did notice a problem in your definitions. The local queue has a the INITQ attribute defined as INITIATION.QUEUE, but you have defined the queue with a name ''initiation.queue'.

Correct your queue defs, so that the INITQ attribute on the app queue matches the name of the defined initiation queue
Run the trigger monitor as above.
Back to top
View user's profile Send private message
guenter1978
PostPosted: Mon Jan 24, 2005 8:35 am    Post subject: Reply with quote

Novice

Joined: 21 Jan 2005
Posts: 12
Location: Austria

Thank you for your answer.

I tried it out and corrected my queue definitions for using all queues with uppercase letters.

I started the trigger monitor you mentioned by typing:
Quote:

runmqtrm -m QM_gspc -q INITIATION.QUEUE


Then I tried to put some messages with the api testprogram into 'APPLICATION.QUEUE', but nothing happened to the 'INITIATION.QUEUE'. Also the console with the trigger monitors gaves no additional output.

Output of trigger monitor:
Quote:
5724-B41 (C) Copyright IBM Corp. 1994, 2002. Alle Rechte vorbehalten.
WebSphere MQ-Auslösemonitor gestartet.

__________________________________________________
Warten auf Auslösenachricht.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Mon Jan 24, 2005 8:46 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

You also need to define a PROCESS, and assign it to the triggered queue.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
guenter1978
PostPosted: Mon Jan 24, 2005 8:49 am    Post subject: Reply with quote

Novice

Joined: 21 Jan 2005
Posts: 12
Location: Austria

That was it

Thanks very much.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Why does this trigger configuration not work?
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.