| Author |
Message
|
| dkiu |
 Posted: Mon Dec 16, 2013 9:36 pm Post subject: Verifying the user details of the execution group |
 |
|
Apprentice
Joined: 28 Feb 2013
Posts: 25
|
Hi,
Someone is creating too many EG's in the broker.I want to track the user -ID of those who are creating the EG in broker. Is there any mqsc command to track such ID's ? |
|
| Back to top |
|
 |
| Simbu |
| Posted: Tue Dec 17, 2013 12:42 am Post subject: |
|
|
Master
Joined: 17 Jun 2011
Posts: 289
Location: Tamil Nadu, India
|
| have you considered activating admin security for the broker? It is the best way to deal with this type of issue. I don't think there is any mqsc or mqsi command to track the user IDs. |
|
| Back to top |
|
|
| dkiu |
| Posted: Tue Dec 17, 2013 3:22 am Post subject: |
|
|
Apprentice
Joined: 28 Feb 2013
Posts: 25
|
No cannot do anything with admin security.
I only have sudo access to the remote broker ....so just keen to know if there is any way to track the users using particular EG as many have started creating EG haphazardly. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Dec 17, 2013 3:29 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I guess that this isn't a production broker so why not delete the EG's and see who screams.
Put out a message (easy if the system is Unix/Linux with /etc/motd) saying that no one it to create EG's without permission and any that are will be deleted forthwith.
Sit back and wait.
In the long term you really need to implement a proper security access to the system even if it is a dev box.
_________________
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 |
|
|
| hcinko5 |
| Posted: Tue Dec 17, 2013 3:44 pm Post subject: |
|
|
Novice
Joined: 12 Apr 2010
Posts: 21
|
| Quote: |
| In the long term you really need to implement a proper security access to the system even if it is a dev box. |
+1
In addition to the already made comments, you could check your syslog or the MBExplorer Admin Log. |
|
| Back to top |
|
|
|
|
