| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ objects vs MQ services |
« View previous topic :: View next topic » |
| Author |
Message
|
| jeevan |
 Posted: Mon Sep 07, 2009 1:27 pm Post subject: MQ objects vs MQ services |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
In order to administer a MQ network, it does not matter whether we call a listener a service or an Object. But some time it is confusing whether to call a component an object or a service.
Specially, while going through documentation, sometime is it so confusing ( just terminology, though it does not make a difference in working or administering mq network as said above).
Do we call an object when we can define it with define command or can create it with OS command line utility eg crtmqm? Or are we following OOPS definition?
To be an object, if we are follwoing object Orientated Programming (OPS) terminology, it has to have an attribute and a state. From that point, the follwoing coud be termed as an objects
1. authinfo ( does it have a state? but has attribute)
2. queue manager( has state and attribute)
3. queues (does have state and attribute)
4. channel ( has a state and attr)
5. listener( has both)
6. namelist( does it have a state?)
7. process (does it have state?, definitely has attributes)
8. service (has attributes and state eg. SVSTATUS)
9. topic ( seems to have both)
Questions:
what about namelist and process? We call them objects but do they have a state?
What about SUB, and CONN? Is connection a services ? an object? none? I think SUB can be an object as we can create it
and has a state.
What about a command servder? We can not define a command server.Does not this mean it is still a service?
The main question is what is the basis of categorizing an object and a service in MQ ? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Sep 07, 2009 2:04 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I think the easy way to go about services is:
Anything that could be defined under either listener or services using runmqsc or the OS (Windows services) can be looked at as a service.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Sep 07, 2009 3:20 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
I would not extrapolate WMQs use of the term object with all of its meanings to the greater OO world of objects. This will lead you (and countless others) away from WMQs use of the term.
WMQ objects are objects in the (more limited) sense that objects have attributes, and attributes have values.
WMQ objects are (with the exception of the qmgr) created with MQSC (or equivalent). I try to avoid using the term instantiated here because it has a very different meaning in the OO world, like inheritance. (I suppose it could be argued that DEF QL(BOB) inherits its attribute values from the SYSTEM.DEFAULT.LOCAL.QUEUE.) Note that the official doc doesn't use instantiate.
Your example of listeners is more accurately a comparison of a standalone program or utility or service vs. a listener object created by MQSC. Again, no exact match for the OO world.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Mon Sep 07, 2009 3:40 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
In MQ parlance, almost every defineable thing is regarded as an OBJECT (queues, channels, namelists, queue managers etc, more than 20 types in total), although messages are not objects. MQ v6 introduced a new concept of a defineable SERVICE, so that programs could be started and stopped in concert with the queue manager.
OBJECTS can have static "attibute" information, as well "state" or "status" information which dynamically changes as they are used.
The bottom line is that the design and terminology of MQ should not be compared to object oriented priniciples as it has does not have a great deal in common.
_________________
Glenn |
|
| Back to top |
|
|
| jeevan |
| Posted: Mon Sep 07, 2009 4:10 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| gbaddeley wrote: |
In MQ parlance, almost every defineable thing is regarded as an OBJECT (queues, channels, namelists, queue managers etc, more than 20 types in total), although messages are not objects. MQ v6 introduced a new concept of a defineable SERVICE, so that programs could be started and stopped in concert with the queue manager.
OBJECTS can have static "attibute" information, as well "state" or "status" information which dynamically changes as they are used.
The bottom line is that the design and terminology of MQ should not be compared to object oriented priniciples as it has does not have a great deal in common. |
My only intention of this discussion was to look for what mq community of users agrees what they call an object or a service.
I only refer OOPS for an example but I did not say we should follow the same principle here in mq world. However, I think there should be some sort of logic or basis to call a mq components an object or a services.
Last edited by jeevan on Mon Sep 07, 2009 4:52 pm; edited 3 times in total |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Mon Sep 07, 2009 4:14 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
The term used to describe the MQ Listener, Channel Initiator and Command Server is debatable. They all separate executing processes. The MQSC manual calls the Listener an OBJECT, but doesn't use any specific term for the chinit or cmdserv.
_________________
Glenn |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Sep 07, 2009 4:29 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
For (lack of) clarity, the WMQ System Admin manual refers to control command runmqchi:
Run a channel initiator process to automate starting channels.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| jeevan |
| Posted: Mon Sep 07, 2009 4:35 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
|
| Back to top |
|
|
| gbaddeley |
| Posted: Tue Sep 08, 2009 4:59 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
hmm, that Infocenter page implies that MQ SERVICES are also MQ OBJECTS. 
_________________
Glenn |
|
| Back to top |
|
|
| jeevan |
| Posted: Tue Sep 08, 2009 5:36 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| gbaddeley wrote: |
hmm, that Infocenter page implies that MQ SERVICES are also MQ OBJECTS. |
I think that is the SERVICE object which could be defined using DEFNE SERVICE(xxxxx) etc |
|
| 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
|
|
|
|
