| Author |
Message
|
| sclarke |
 Posted: Thu Oct 29, 2009 9:04 am Post subject: Broker support model |
 |
|
Apprentice
Joined: 05 Jan 2002
Posts: 39
|
I am curious to hear how various organizations model their support structure for the running of the broker and the configuration manager. Is it the middleware staff who may also support the application servers - WAS, JBOSS etc? Or a separate team that just supports the broker and it's components? Or does the team that actually develops flows and applications?
Our organization has a small team that develops broker flows which also supports the broker itself (upgrades, regular operation issues etc). I am trying to move the support to the middleware team (which also currently supports MQ itself) but would like to hear what other companies are doing.
Thanks. |
|
| Back to top |
|
 |
| MK8570 |
| Posted: Thu Oct 29, 2009 10:08 am Post subject: |
|
|
Apprentice
Joined: 18 Jul 2007
Posts: 26
Location: PA, USA
|
We have a middleware team which support MQ , WAS and WMB administration.
We have setup aix groups and acl for WMB development team. |
|
| Back to top |
|
|
| jbanoop |
| Posted: Thu Oct 29, 2009 11:31 am Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
My 2 cents...
At the client locations I have worked on, typically code artifacts (the actual deployed components) are supported by a support team comprising of MB designers/developers.
The infrastructure (MQ, Broker) is supported by 1 or more infra teams (sometimes MQ support is a separate team and MB support is separate but both may be supported by the same team as well).
When issues are raised the ticket is owned and the issue driven to resolution by the group owning the ticket (app support/ MQ support / MB support). |
|
| Back to top |
|
|
| sclarke |
| Posted: Mon Nov 02, 2009 5:09 am Post subject: |
|
|
Apprentice
Joined: 05 Jan 2002
Posts: 39
|
Thanks for the feedback - I would like to hear from a couple more companies out there if possible. Anyone else want to share your running broker support model?
Thank you very much.... |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Nov 02, 2009 5:16 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It's generally viewed as a poor idea for developers to deploy things all the way to production
Particularly by regulations like SOX. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Nov 02, 2009 5:58 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| mqjeff wrote: |
It's generally viewed as a poor idea for developers to deploy things all the way to production
Particularly by regulations like SOX. |
Agreed. It is usually a very bad idea to let developers anywhere near production except to explain why their code can't work despite spending hours if not days/weeks/months in testing.
Developers & Support people tend (being general) to have completly different mindsets.
_________________
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 |
|
|
| Vitor |
| Posted: Mon Nov 02, 2009 7:11 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
My experience is that components (WMB, WMQ, WAS, Dbase, box support) are supported by 1-n teams depending on organisational size & skill diversity. So Dbase is nearly always a team by itself, WMB & WMQ may or may not be lumped together and all of these are different from the teams that run production.
Certainly it's a general rule that development & support are 2 separate functions no matter how many people run support. I can't speak to SOX but accept the word of my associate, and it's a common sense split. Like having production separated from the development process. If only to have the developed code reviewed/processed/signed off/etc from different people (and there was a whole thread recently on how to work that).
My 2 cents.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
