| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| system default objects on wmq |
« View previous topic :: View next topic » |
| Author |
Message
|
| prince_mq |
 Posted: Tue Apr 14, 2009 11:37 pm Post subject: system default objects on wmq |
 |
|
Voyager
Joined: 10 Aug 2006
Posts: 76
|
Hi,
I want to install wmq7 on a unix platform and every queue manager that i create should have certain parameters like MAXMSGLEN to have 100MB.
Actually, I do not want to run ALTER QMGR COMMAND to modify MAXMSGLEN value. While creating queue manager itself, i want the value of certain parameters like MAXMSGLEN to have 100 MB (by default).
Is there any file or configuration setting that we can change in WMQ so that all queue managers that we create by default have custom values for parameters like MAXMSGLEN?
Thanks,
V |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Apr 14, 2009 11:42 pm Post subject: Re: system default objects on wmq |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| prince_mq wrote: |
| Is there any file or configuration setting that we can change in WMQ so that all queue managers that we create by default have custom values for parameters like MAXMSGLEN? |
Not that I'm aware of, and I wait to be amazed by someone who knows better.
If not, I think a simple script will solve your problem.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Wed Apr 15, 2009 5:36 am Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
Accoring to this, I think you cannot provide the QMgr and its objects attributes during creation time.
Thanks. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Apr 15, 2009 5:44 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9471
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| I think a simple script will solve your problem. |
A best-practice is to leave vendor-supplied things alone. In this case, don't modify the SYSTEM* objects.
Rather, create template objects that are specific to your organization or application, and use these as the templates for the creation of new objects.
For example, you can create PAYROLL.DEFAULT.LOCAL.QUEUE, and set the attributes to match your application requirements; then create your new objects with this:
DEFINE QL(NEW.QUEUE) LIKE(PAYROLL.DEFAULT.LOCAL.QUEUE).
_________________
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 |
|
|
| exerk |
| Posted: Wed Apr 15, 2009 6:36 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| bruce2359 wrote: |
| ...A best-practice is to leave vendor-supplied things alone. In this case, don't modify the SYSTEM* objects... |
This is one one of those rare occasions where I have to disagree with you, as it is possible to restart a queue manager, and have the SYSTEM objects redefined. In principle your suggestion is good, but if the LIKE is omitted...
I know that tightly controlled procedures should prevent this, but in the heat of the moment, i.e. business line screaming to 'get it fixed - now!', that may not happen.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Apr 15, 2009 6:43 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| exerk wrote: |
| it is possible to restart a queue manager, and have the SYSTEM objects redefined. |
And redefined at their installation defaults I believe. So in the case quoted, back to 4Mb from 100Mb. So you could end up with inconsistent objects.
It's a balancing act - the odds of someone recreating the system objects v the odds of someone forgetting to use LIKE. All depends where you want your risk, and how good your controls are.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Apr 15, 2009 7:48 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9471
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| In principle your suggestion is good, but if the LIKE is omitted... |
Nothing is foolproof. Using MQSC scripts with LIKE for all user objects will isolate us from the omni-present and dreaded SYSTEM.DEFAULT objects.
If not a best-practice, then a pretty good habit to get into.
_________________
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 |
|
|
| mqjeff |
| Posted: Wed Apr 15, 2009 7:50 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| You should still probably alter a number of SYSTEM objects, to enhance the security of your qmgr... Things like MCAUSER, etc. etc. etc. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Apr 15, 2009 8:01 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9471
Location: US: west coast, almost. Otherwise, enroute.
|
I agree 100.3%. This should also be scripted AND sysadmins need to create and start a new qmgr, followed immediately by running the script that does all this. Or, create a perl or whatever script that does all this.
_________________
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 |
|
|
|
|
|
| |
|
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
|
|
|
|
