Currently, the following steps should be taken to change the “P2K” user password:
- Replace the normal link to get into the application with a “system temporarily unavailable” web page. This is an optional step. If you have an index.html file, it would be normally located in the \Apache\Apache\htdocs directory.
- Ensure that everyone is out of the system and that no one attempts to log in while changing the P2K password.
- Do not shut down any of the managed server while making changes to the P2K password. The follow steps require access to the application. However all managed servers will need to be restarted once completed.
- Change the user password within the application itself, using either the IMUS or IMRU screens.
- Change the password in the DB Login page. Each Personality EAR deployment maintain a separate file with the database connection information, including an encrypted copy of the P2K password. This is generated or altered by navigating to the adminConsole web page. If you have more than one instance connecting to the same database, all their password files will need to altered to ensure they are able to connect the database after the password has been change. The web page should have a URL structure similar to http://your.server.name/Personality/adminConsole - with Personality being the name of each managed server the application has been deployed into.
- Change the password in the HLCPooledDataSource within the WebLogic Server. Login into the WLS Administration Console and navigate to Services and Data Sources to find this entry.
- Shutdown and restart each managed server that connects to this database.
- Ensure you are able to log into the application with both Admin and Self-Service.
- Restore the normal links to the index.html file, if you have changed it.
Notes#
Click to create a new notes page
