How to fix broker instance after password change?

12Oct09

Hello all,

My current company has a policy that expires passwords every month, therefore DB2 and WMB services that are tied to this  account to Log On needs to be changed as well. Also the broker instance(s) need to be updated with the new password for the data store. Here is a quick checklist to fix the situation. Please note that this list is not exhaustive;

1. Fix DB2 services – The easiest way to do this is switch to services view in Windows and spot the services that are failing to start. Next right click these services and from the context menu select properties. Select the Log On tab and change the password used for these services. Please note that some services use the local system account while others use a selected account and it is these services which use a selected account that fail. (I don’t know why services use a different approach as of now so if you know I would appreciate if you can tell me)

2. Next you need to fix the service password for your configuration manager. For this you need to issue amqsichangeconfigmgr <config_mgr_name> -a <password>. Start your configuration manager by issuing a mqsistart command following this.

3. The last piece you need to fix is your broker instance. For this you need to fix both service password and data source password. Issue a mqsichangebroker <broker> -a <password> -p <password>. Start your broker instance by issuing a mqsistart command.

Environment: WMB 6.1.0.4 and DB2 v9.1 on Windows XP

Advertisement

Filed under: WMB   |  Leave a Comment
Tags: IBM, WMB, Websphere Message Broker