| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message broker problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| Kateel |
 Posted: Fri Nov 06, 2009 7:49 pm Post subject: Message broker problem |
 |
|
Novice
Joined: 01 May 2006
Posts: 17
|
Is there anyway to check the deploymant history? Like who all deployed a particular message flows to a broker recenlty? And the time etc?
Sorry, I just couldnot find any relevant info anywhere.
Thankyou,
Kateel. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Fri Nov 06, 2009 11:59 pm Post subject: Re: Message broker problem |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Kateel wrote: |
Is there anyway to check the deploymant history? Like who all deployed a particular message flows to a broker recenlty? And the time etc?
Sorry, I just couldnot find any relevant info anywhere.
Thankyou,
Kateel. |
Can't find the info anywhere eh?
Pretty well the same question was asked just 4 days ago.
http://www.mqseries.net/phpBB2/viewtopic.php?t=51424
_________________
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 |
|
|
| Kateel |
| Posted: Sat Nov 07, 2009 9:24 am Post subject: |
|
|
Novice
Joined: 01 May 2006
Posts: 17
|
thansk SM,
I am looking for the history from investigation point of view. We have a couple of new just out of college developers here. And recently there was a couple of cross deploys resulting in chaos. And no one took the blame. I actualy don't need the code(bar) that is deployed. But recent 5-10 deployment history like which user and time. Is it stored somewhere in Broker database or so? (all i know is getting the latest deploy time). Or if there is something i can setup that will log every deployment to syslog? (syslog we made as root owned so no one fiddled with it)
The one you suggested to use script is good one but we have to assume that the guy ran the script didn't delete the history before we saw it.
Thanks, |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sat Nov 07, 2009 10:37 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Three things
1) make the output log include a timestamp
2) Capture the name of the user who ran the script
3) store the log in a common directory.
If you want to be really paranoid, add code to the script around the deploy to add info ro a database.
You can only go so far to log stuff in such a way that would stop an errant developer from covering their tracks if they really want to. I'm looking forwar to seeing what changes have been made in V7 in this area.
Why not give each developer their own broker?
As a developer of nearly 40 years you really need to educate you developer to 'fess up' when they make mistakes. As your team is fresh out of Uni then they probably think they know it all. I certainly did at their age.
I can remember forgetting where my current directory was and doing an 'rm -fr .' The only problem that this was a production & I was logged on as root and my current directory was /. Ouch. I fessed up and we got on with restoring the backups. Much egg on face and I owed a few SysAdmins more than a pint or two but we got over it and carried on. If I hadn't admitted my mistake then I would probably have been fired on the spot.
_________________
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 |
|
|
|
|
|
| |
|
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
|
|
|
|
