| Author |
Message
|
| dotaneli |
 Posted: Tue Sep 09, 2008 3:48 am Post subject: Changing the user that runs the broker |
 |
|
Voyager
Joined: 19 Oct 2005
Posts: 99
Location: Israel
|
Hey everyone.
My wbiadmin user gets locekd all the time, and we can't find why.
We decided to create a new user, and change the broker to work with that user.
Any implications to consider before performing this act?
DB wise? MQ wise?
10x. |
|
| Back to top |
|
 |
| MrSmith |
| Posted: Tue Sep 09, 2008 4:38 am Post subject: |
|
|
Master
Joined: 20 Mar 2008
Posts: 215
|
Well yes and no.
Firstly what platform is it?
Secondly - User profiles don't normally just get locked out unless they are being attempted for login and fail or something equally administrative like that.
Thirdly - there is no guarantee that your new user will not do the same thing based on the second point.
MQ wise - er yes the new profile will need to be in the mqm group.
Broker - the profile will need to be part of the mqbrkrs group
This is all standard setup stuff!!
But otherwsie it will partially depend on your configuration, there will of course be the broker to change for its service profile and password (-i -a option on broker creation) and the new profile will need to be added to the database you used for the broker and its corresponding odbc DNS connection (if windows) unless you used a different user on broker creation to that of the service (i.e. -u -p options). This will generate an error in the event viewer for windows and log on unix if you now don't have authority with your new profile to the DB.
Personally i would be more likely to try to resolve the issue of why your original profile keeps locking though |
|
| Back to top |
|
|
| dotaneli |
| Posted: Sat Sep 13, 2008 11:14 pm Post subject: |
|
|
Voyager
Joined: 19 Oct 2005
Posts: 99
Location: Israel
|
Thanks.
Unfortunately, it's not my enterprise 
It's a client of mine. And they insist on changing the user since about a week of work was not sufficent to solve the problem.
They say here that random locks occur...
One of them thinks it may be do to the DB2 managment consule..
So to save more consulting hours they decided to change the user... |
|
| Back to top |
|
|
| dotaneli |
| Posted: Sat Sep 13, 2008 11:27 pm Post subject: |
|
|
Voyager
Joined: 19 Oct 2005
Posts: 99
Location: Israel
|
P.S. - Platform is Win 2003 server.
DB is DB2.... (god pnly knows why they chose it...) |
|
| Back to top |
|
|
| dotaneli |
| Posted: Sat Sep 13, 2008 11:44 pm Post subject: |
|
|
Voyager
Joined: 19 Oct 2005
Posts: 99
Location: Israel
|
Guys - another issue...
mqsichangebroker does not allow me to change the DB2 user, only its password..
Now let's say that in creation time no DB2 user specified...
Now i alter the broker's user - does it say that the broker's db2 user will automaticlly change to?
thanks. |
|
| Back to top |
|
|
| yaakovd |
| Posted: Sun Sep 14, 2008 2:40 am Post subject: |
|
|
Partisan
Joined: 20 Jan 2003
Posts: 319
Location: Israel
|
| MrSmith wrote: |
Secondly - User profiles don't normally just get locked out unless they are being attempted for login and fail or something equally administrative like that.
Thirdly - there is no guarantee that your new user will not do the same thing based on the second point. |
In case you created DB with same user as MB service - you have a proble. You cannot change user of DB because it also schema where MB creates all internal tables.
1. Recreate the broker.
2. Fix problem of locking user (I'm completelly agree with MrSmith).
Check if have "Password never expired" for this user. Check Domain policy if any.
_________________
Best regards.
Yaakov
SWG, IBM Commerce, Israel |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sun Sep 14, 2008 4:00 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| dotaneli wrote: |
P.S. - Platform is Win 2003 server.
DB is DB2.... (god pnly knows why they chose it...) |
Because that's what's supplied by IBM with the Broker software. Why pay for another DB software package?
If your client has IDs locking it and they can't figure out why...oh boy. I'm with Mr Smith - ask them what's going to prevent the new ID from behaving the same way if they can't tell you why the first ID is doing it? Is it a local ID or a domain ID? What do your Active Directory System Admins say about this?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
