Password change on a Jazz/DB2 system
Our build team just went through our quarterly password change, and we ran into issues on our Windows XP Jazz server. I changed the password on the admin ID, which is also the DB2 admin id. I also changed the password in the teamserver.properties file. I shut down the tomcat window, then rebooted the machine. When I did, the database didn't start automatically and wouldn't start manually (none of the possible errors displayed didn't seem to apply). Once I set the password back to the old one, everything came up ok. Does anyone have a comprehensive checklist of what to do to successfully change the passwords on a Windows Jazz server?
4 answers
If I'm reading your post correctly, your question is about how password
changes affect DB2 right? Did Jazz have any problems after the password
change?
Matt Lavin
Jazz Server Team
jcurtiss wrote:
changes affect DB2 right? Did Jazz have any problems after the password
change?
Matt Lavin
Jazz Server Team
jcurtiss wrote:
Our build team just went through our quarterly password change, and we
ran into issues on our Windows XP Jazz server. I changed the password
on the admin ID, which is also the DB2 admin id. I also changed the
password in the teamserver.properties file. I shut down the tomcat
window, then rebooted the machine. When I did, the database didn't
start automatically and wouldn't start manually (none of the possible
errors displayed didn't seem to apply). Once I set the password back
to the old one, everything came up ok. Does anyone have a
comprehensive checklist of what to do to successfully change the
passwords on a Windows Jazz server?
My main question was "Does anyone have a comprehensive checklist of what to do to successfully change the passwords on a Windows Jazz server?" The Jazz documentation was very helpful during installation, but it is silent on the topic of password change once the machine is installed and running. I also have a Build Forge server that uses a DB2 database, and it keeps the DB2 admin password in a file like Jazz does. I have never had a problem with the database on that machine after changing the system password and that file, but on Jazz I did. The database didn't come back up after a password change/reboot, thus while Tomcat could restart, it was brain dead because it couldn't get to its config on the DB.
jcurtiss wrote:
DB2 installs several windows services. One or more of these may also
have the old password in its settings. Take a look at those (Control
Panel->Administrative Tools->Services). Open the properties for each
service with a name like DB2* and check its Log On tab.
Steve Wasleski
Jazz Jumpstart
Our build team just went through our quarterly password change, and we
ran into issues on our Windows XP Jazz server. I changed the password
on the admin ID, which is also the DB2 admin id. I also changed the
password in the teamserver.properties file. I shut down the tomcat
window, then rebooted the machine. When I did, the database didn't
start automatically and wouldn't start manually (none of the possible
errors displayed didn't seem to apply). Once I set the password back
to the old one, everything came up ok. Does anyone have a
comprehensive checklist of what to do to successfully change the
passwords on a Windows Jazz server?
DB2 installs several windows services. One or more of these may also
have the old password in its settings. Take a look at those (Control
Panel->Administrative Tools->Services). Open the properties for each
service with a name like DB2* and check its Log On tab.
Steve Wasleski
Jazz Jumpstart
It would be very handy to have a command like:
and this would reprompt for each and every Database password used for JTS, CCM, QM, RM, DM, LQE, RELM, DW, etc. It would then update the teamserver.properties file for each app with the encrypted form of the new password.
This is handy for when you must let go for criminal reasons some employee who knew your db2 credentials.
./repotools-jts.sh -modifyDatabasePasswords teamserver.properties=conf/jts/teamserver.properties
and this would reprompt for each and every Database password used for JTS, CCM, QM, RM, DM, LQE, RELM, DW, etc. It would then update the teamserver.properties file for each app with the encrypted form of the new password.
This is handy for when you must let go for criminal reasons some employee who knew your db2 credentials.