Change database passwords used by WebSphere Portal

1. Ensure that the administrative server for WAS is running.

2. If this is a clustered environment, start dmgr and nodes, and stop the WebSphere Portal server.

3. If the VMM is using the database, update the VMM database password.

4. Check if the database user has become disabled due to invalid login attempts. Re-enable the database user if necessary.

5. Log in to the WAS admin console and go to...
   Security | Global security | Java Authentication and Authorization Service | J2C Authentication Data

   ...and select the alias to change; for example...

   • wpsDBAuth
   • jcrDBAuth
   • fbkDBAuth
   • lmDBAuth
   • wcmDBAuth

6. Update the password accordingly.

7. Click Apply, and then click Save to save the configuration.

   You are informed that security.xml has been changed.

8. If we are an administrator and need to change the DB2 password, change the database administrator user password on the system.

   1. Stop the DB2 server.

   2. Use the passwd command to change the password.

   3. Restart the DB2 server.

   4. Verify the new password by running the task...
      db2 CONNECT TO WPSDB user db2admin using password

9. Restart the WAS admin console.

10. On the DB2 server, click...
    Administrative Tools | Services

11. Stop all running DB2 services.

12. For each service that the DB2 instance uses, display the menu and select Properties.

13. Select the Log On tab and change the DB2 administrator's user name and password.

    If you do not change the DB2 administrator's user name and password in the properties of each DB2 service, the DB2 database application will not start.

14. Repeat for each JDBC Provider, data source, and alias that is affected.

15. Verify the WebSphere Portal application server is running...
    http://hostname.example.com:10039/wps/portal

Parent: Update user ID and passwords