Changing the Database Schema Passwords

If you must change the PPM database schema passwords, be sure to change them both in the database and in the server.conf file.

What to consider before you change all the database schema passwords

  • Check your environment definitions to determine whether any contain a password that is to be changed. You can use the tool <PPM_Home>/bin/kEnvUpdatePassword.sh 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. (Open an environment on the Environment page, and then, 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.

Changing the PPM database schema passwords

  1. Make sure that all users are logged off the system.

  2. Stop the PPM Server. (For information about how to stop PPM Servers, see Starting and Stopping the PPM Server on a Single-Server System.)

  3. Change passwords, as necessary in the database.

  4. To change the passwords in the server.conf file, run the kConfig.sh script to set the DB_PASSWORD,CONC_REQUEST_PASSWORD, and RML_PASSWORD server parameters.

    Note: When changing the passwords, do not edit the server.conf file directly. To encrypt password values correctly, use the kConfig.sh script.

  5. Restart the PPM Server.