| Author |
Message
|
| pkbab |
 Posted: Fri Sep 04, 2009 4:04 am Post subject: need of default QM |
 |
|
Novice
Joined: 08 Aug 2009
Posts: 16
|
Hi am new to websphere MQ
COULD PLZ ANYONE TELL XACTLY
what is the need of DEFAULT QM?
IN INFOCENTER THEY MENTIONED THE DEFINITION
ONE ANSWER I CAME TO KNOW IS APPLICATIONS CONNECT TO DEFAULT QM |
|
| Back to top |
|
 |
| JosephGramig |
| Posted: Fri Sep 04, 2009 4:13 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
There is no NEED of a default QMGR.
You can declare one to be the default.
imho, I think it is a bad idea to rely on that type of convention. Eventually, you or your teammates will commit the sin of typing a command meant for one system and it will accidentally run in production because you were looking at production to get an idea of what you needed to do...
Then, disaster strikes because you didn't design it out.
Always be specific about which QMGR you want to use. |
|
| Back to top |
|
|
| sumit |
| Posted: Fri Sep 04, 2009 5:36 am Post subject: Re: need of default QM |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
| pkbab wrote: |
| ONE ANSWER I CAME TO KNOW IS APPLICATIONS CONNECT TO DEFAULT QM |
Application can connect to any queue manager you want it to connect. It just means that if you are not mentioning a queue manager name in your application, only then it will connect to default queue manager.
Mention the queue manager name if you want to connect to a queue manager which is not default.
_________________
Regards
Sumit |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Fri Sep 04, 2009 7:01 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| Quote: |
| ... if you are not mentioning a queue manager name in your application, only then it will connect to default queue manager.... |
If there is any, in that system. 
Agree with JosephGramig.
{If you are using the unix flavor then try hitting the runmqsc without the name of the queue manager... you'll get the answer.}
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| pkbab |
| Posted: Sat Sep 05, 2009 1:13 am Post subject: |
|
|
Novice
Joined: 08 Aug 2009
Posts: 16
|
i understood
thank u guys |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Sun Sep 06, 2009 3:43 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
Best practise is to not have a default queue manager. The application should always connect to a named qmgr. That way, they can always be sure of what MQ resource they are using. It also avoids the problem of an app connecting to the incorrect default qmgr when someone creates a new qmgr and accidentally makes it the default.
_________________
Glenn |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sun Sep 06, 2009 10:17 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| gbaddeley wrote: |
| Best practise is to not have a default queue manager. The application should always connect to a named qmgr. That way, they can always be sure of what MQ resource they are using. It also avoids the problem of an app connecting to the incorrect default qmgr when someone creates a new qmgr and accidentally makes it the default. |
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
