| Author |
Message
|
| Chandra Mohan |
 Posted: Wed Nov 29, 2006 5:10 am Post subject: Difference between MQ developer and administrator. |
 |
|
Acolyte
Joined: 26 Jul 2006
Posts: 53
|
Hi ,
I am bit confuse for the responsbilites lying wth MQ developer and Administrator could any one of you explain wat is the diff. in between developer and admin.
Is a knowledge of MQ developer is helpfull to administarte MQ if yes so, please suggest me the docs to read.
Till now i know about the MQ admin.(deals wth channel, queues, QM's recovery/migration/failover/creation).
I want to grow my self in the field of MQ administration Please suggest me wat wud b the next step for me to achieve my goal.
Thanks in advance.
_________________
Chandra Mohan |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Nov 29, 2006 5:23 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Occassionally you have to be both... 
Developers develop code that produces and consumes messages. To be an MQ developer you need to understand the messaging paradym and the features that MQ offers, as well as the nuts & bolts of connection to the MQ layer.
Administering MQ is easier if you have some idea of what the developers are doing. Helps with queue placement, definition, that sort of thing. Also problem solving & promotion of best practice. Cast your eye over the Application Programming Guide.
To be a better administrator - practice, experiment, innovate. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Nov 29, 2006 5:40 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The difference between "MQ developer" and "MQ administrator" is the difference between "developer" and "administrator".
If you don't know this difference, you are not qualified to be either one.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Chandra Mohan |
| Posted: Wed Nov 29, 2006 5:58 am Post subject: |
|
|
Acolyte
Joined: 26 Jul 2006
Posts: 53
|
| jefflowrey wrote: |
The difference between "MQ developer" and "MQ administrator" is the difference between "developer" and "administrator".
If you don't know this difference, you are not qualified to be either one. |
Thanks for u r comments Jeff. However i know the diff. in dev and admin. but i asked this question to know abt is developr's knowledge really helpfull for the person to administrate the MQ or not.
As i mentioned my work profile please suugest me wat wud b my next step to grab a full knowledge abt MQ.
_________________
Chandra Mohan |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Nov 29, 2006 6:00 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The less you know about development, the more you are at the mercy of your developers.
The less your developers know about administration, the more they are at your mercy.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Nov 29, 2006 10:50 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Look at it like looking at a car. Which would you rather be: the driver or the mechanic?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Nov 29, 2006 10:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| fjb_saper wrote: |
| Look at it like looking at a car. Which would you rather be: the driver or the mechanic? |
And which would you rather do? Repair the same fender every day, or teach the drivers not to back into the flagpole?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Wed Nov 29, 2006 11:30 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
A wise man once said to me....
| Quote: |
| MQ is not an cure for poor application design |
MQ developers need to fully understand what the business requirements are, what the techology delivers, and then code the solution accordingly.
Personally I always have the most trouble trying to convince people that the application design is really not up to me, nor is it up to the programmer to 'make something up'. It requires that the business needs drive the design. I don't particulary like pigeon-holing roles as developer/administrator as both need to understand the others 'kingdom' to a large degree.
If you want to grow your own skills then the best was (IMHO) is to go down the IBM certification path of MQ specialist, then solution expert. (if they still exist). These require a broad but fairly in depth cross-disipline understanding of MQ.
Just my 2 cents worth.  |
|
| Back to top |
|
|
|
|
