Posted: Tue Oct 02, 2007 2:19 pm Post subject: Best practice managing WMB developers
Chevalier
Joined: 31 Mar 2006 Posts: 411 Location: New York
Today, by copying my workplace and giving it to a developer, I almost ruined a production environment when he deleted the production broker from admin view - thinking it's just a view, durding "play around".
This incident demonstrates the importance of a suitable practice in giving developers access to broker domain resources.
Years back with MQSI, I used to create an execution group for each developer to play with. Under v6, I wonder if a user can be restricted to accessing only an execution group he/she is assigned.
Is there a known recommended best practice for managing developers?
thanks for sharing any insight. _________________ pcelari
-----------------------------------------
- a master of always being a newbie
mqsisetaclentry gives you very tight control over who can do what to what.
There's no reason for anyone who is not an admin to have any access at all to a production broker. There's no reason for the network that developers workstations live on to have any connection to the production network.
At least, in the U.S. under Sarbanes-Oxley.
At a minimum, developers should only have View access to production servers as granted by mqsisetaclentry. _________________ I am *not* the model of the modern major general.
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