| Author |
Message
|
| vivekkooks |
 Posted: Wed Jun 11, 2003 12:26 pm Post subject: About Triggering the application |
 |
|
Voyager
Joined: 11 Jun 2003
Posts: 91
|
Hello,
Is it possible to run a remote application(on another system) from MQServer?
vivek |
|
| Back to top |
|
 |
| vennela |
| Posted: Wed Jun 11, 2003 12:49 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I think yes. But you will have to have a client on the remote machine nad run a client trigger monior.
-------
Venny |
|
| Back to top |
|
|
| vivekkooks |
| Posted: Wed Jun 11, 2003 11:10 pm Post subject: About Trigger mechanism |
|
|
Voyager
Joined: 11 Jun 2003
Posts: 91
|
Hello,
Is it possible to have more than one triggers and more than one process definition objects on a single application queue?
Can an independent application(running on another system) connect to MQServer or MQClient is required to be installed on that machine in order to connect to MQServer?
I am new to MQSeries. Please tell me where can i get detailed triggering documentation.
vivek |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Jun 12, 2003 12:28 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
It's in the IBM manuals, or in some cases the support pac documentation.
Remember - triggering is NOT the normal method of MQ operation - it is useful for applications that only run infrequently. For continuously running applications processing messages every few seconds then code a long-running MQ adapter or interface. Do NOT trigger.
Triggering is INEFFICIENT as an additional message is put and get to the initiation queue and also the application has to be loaded each time.
Always process a queue until empty in an application (even if triggered) and use trigger type FIRST not EVERY. Also assume that triggering may fail and run the application on a schedule as well for safety. We find the IBM trigger monitor fails about once a month. |
|
| Back to top |
|
|
| looloo |
| Posted: Thu Aug 07, 2003 6:23 am Post subject: |
|
|
Novice
Joined: 27 May 2002
Posts: 11
|
Hi,
[quote]then code a long-running MQ adapter or interface. Do NOT trigger[/quote]
Could you give me links about "MQ adapter or interface"
thanks |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Aug 07, 2003 9:09 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| looloo wrote: |
Hi,
| Quote: |
| then code a long-running MQ adapter or interface. Do NOT trigger |
Could you give me links about "MQ adapter or interface"
thanks |
You should start with the manuals.
All he's really talking about is a normal mqseries application that is coded to run all the time, instead of stopping after it has processed every message currently on a queue.
These are some facts about triggering that relate to your questions:
- Triggering requires a trigger monitor and an initiation queue.
- The presupplied trigger monitors can't start applications on a different machine than they are running on.
- No application can get data from MQSeries unless it is running on a machine with either the MQServer on it or the MQClient.
- Triggering is not the best choice for high-volume or rapid-response processing.
- You can only define one process definition for a single queue.
|
|
| Back to top |
|
|
|
|
