Change database schema passwords

This section provides details on how to change the database schema passwords.

Before you change the database schema passwords

Consider the following before you change all the database schema passwords:

If you must change the OpenText PPM database schema passwords, be sure to change them both in the database and in the server.conf file.
Check your environment definitions to determine whether a contain password can be changed. You can use the <PPM_Home>/bin/kEnvUpdatePassword.sh tool to automatically change all occurrences of a specific password for a particular host and user name.
Note: This functionality is also available from the Environments section of the PPM Workbench.
1. Open an environment on the Environment page
2. On the Environment menu, click Update Password.
- Check both server and client passwords, as well as database passwords.
- Check passwords associated with application codes.
Although it is not a recommended practice, you can hard-code passwords into commands in workflow steps, requests, and object types.
There is no need to change commands that use tokens for passwords (that is, SOURCE_ENV.DB_PASSWORD), as long as the password is changed in the respective environment definitions.

To change the PPM database schema passwords:

Make sure that all users are logged off the system.
Stop the PPM Server.

For details about how to stop PPM Servers, see Start and stop the PPM Server on a single-server system.
Change the required passwords in the database.
To change the passwords in the server.conf file, run the kEncrypt.sh script to encrypt the password, and then copy the encrypted password to the DB_PASSWORD,CONC_REQUEST_PASSWORD, and RML_PASSWORD server parameters in the server.conf file.
Run the kUpdateHtml.sh script to regenerate the server.conf file and apply your changes. For details, see kUpdateHtml.sh.
Restart the PPM Server.