| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| strmqbrk or runmqbrk in custom service |
« View previous topic :: View next topic » |
| Author |
Message
|
| tleichen |
 Posted: Thu Mar 20, 2008 7:28 am Post subject: strmqbrk or runmqbrk in custom service |
 |
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
On a Windows system when defining a custom service, is there any difference using runmqbrk vs. strmqbrk? 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
 |
| EddieA |
| Posted: Thu Mar 20, 2008 9:04 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
I think runmqbrk is designed to run as a "foreground" application, in that it's started from a window/console, and writes information there, as opposed to strmqbrk which starts the broker in the "background" and doesn't interact with a window/console.
My guess would be hat you have to use strmqbrk.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| tleichen |
| Posted: Mon Mar 24, 2008 7:42 am Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
But, there is a predefined service in V6 that is set up to start and stop the pub/sub broker. The main differences in the way it is defined from what I normally do is that it is a server type, rather than a command type service and that it uses runmqbrk, rather than strmqbrk. It seems to run the broker the same way, so I'm just trying to find out "what's the diff?"
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 25, 2008 1:38 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The nice thing about canned services presupplied with MQ is that you can just lie back and trust them.
The difference between strmqbrk and runmqbrk is what EddieA says - one is background and one is foreground.
This is created as a Server type to ensure that you only ever have one, and that the aliveness of the process can be monitored.
You can think of the difference between Server and Command services as the difference between not adding an & and adding a & to the end of a Unix command (or prepending with start on Windows). The Command service process is going to be detached from the queue manager, and thus "invisible" to the queue manager. The Server process won't be.
Using a Command service and strmqbrk would end up dispatching a shell to execute strmqbrk, which would end up dispatching a shell to runmqbrk.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
