Changing the database password for a WebSphere Lombardi Edition Version 7.1 or 7.2 full installation

Answer

Note: The information that is contained in this document has been moved to dW Answers at this location. The new format will allow you to ask questions of the community to better understand the information. This technote will be archived in 60 days. Please bookmark the new location.

Follow these steps:

1. Stop the Process Center or Process Server, Performance Data Warehouse, and the deployment manager/server1.
   
   
2. Encrypt your new password.
   
   
1. Review the Characters that are valid for user IDs and passwords information in the WebSphere Application Server 7.0 documentation.
   
   
2. Navigate to the WLE_HOME/twinit/lib directory.
   
   
3. Run the following command:
   ../../AppServer/java/bin/java -cp utility.jar com.lombardisoftware.utility.EncryptPassword "<new_password>"
   
   
3. Change the password in the following files to the encrypted value returned in the previous step.
   
   
• WLE_Home/internal-provider/98Database.xml
  The change is in line 9. Back up the original and do NOT leave .xml as the file extension on the backed up version.
  
  
• WLE_Home/internal-provider/securitydb.jocl
  The change is in line 6. Back up original and do NOT leave .jocl as the file extension on the backed up version.
  
  
• WLE_Home/process-center/config/100Custom.xml
  Override the 98Database.xml file, as follows:
  <properties>
   <server merge="mergeChildren">
     <databases merge="mergeChildren">
       <database merge="mergeChildren">
         <encrypted-password
         merge="replace">encrypted_password
         </encrypted-password>
       </database>
     </databases>
    </server>
  </properties>
  
  
• WLE_Home/performance-data-warehouse/config/100Custom.xml
  Override the 98Database.xml file, just like the previous list item.
  
  
• WLE_Home/twinit/resources/PerfDB.properties
  The change is in line 7. Back up original and do NOT leave .properties as the file extension on the backed up version.
  
  
• WLE_Home/twinit/resources/ProcDB.properties
  The change is in line 7. Back up original and do NOT leave .properties as the file extension on the backed up version.
  
  
• WLE_Home/twinit/resources/config/100Custom.xml
  Override the 98Database.xml file, as in the previous examples.
  
  
• WLE_Home/language-packs/manageLanguagePacks.properties
  The change is in line 7. The clear text password is also in line 6. Back up original and do NOT leave .properties as the file extension on the backed up version.
  
  
• WLE_Home/upgrade/ProcessServerDB.properties
  The change is in line 5. Back up original and do NOT leave .properties as the file extension on the backed up version.
  
  
• WLE_Home/upgrade/PerformanceServerDB.properties
  The change is in line 5. Back up original and do NOT leave .properties as the file extension on the backed up version.
  
  
4. Disable the WebSphere Application Server administrative security. Complete the following steps:
1. Run the AppServer/bin/wsadmin.bat -conntype NONE command.
2. At the wsadmin prompt, type securityoff. You receive a message confirming that administrative security is off.
3. At the wsadmin prompt, type exit.
   
   
5. Start the your server, which is server1 by default, or start the deployment manager if you are using a clustered runtime. Only start the server that hosts the WebSphere Application Server administrative console.
   
   
6. Log on to the WebSphere Application Server Administrative Console (http://server:port/ibm/console, where port is typically 9060, and complete the following steps for each of the four Teamworks data sources:
   
   
1. Navigate to Resources > JDBC > Data sources.
   
   
2. Click Custom Properties.
   
   
3. Navigate to the second page and click password.
   
   
4. Modify this value to your match new unencrypted password.
   
   
5. Click OK and then click Save. This value is encrypted after saving.
   
   
   If you are running in a cluster with Oracle as your database, modify the data sources for your secondary nodes' SIB schema, if they were changed.
   
   
7. On the WebSphere Application Server Administrative Console, complete the following steps to update the J2C authentication data:
   
   
1. Navigate to Security > Global Security.
   
   
2. Select Administrative security if it is not selected.
   
   
3. Navigate to Java Authentication and Authorization Service > J2C authentication data.
   
   
4. Enter the unencrypted passwords for performancedblogon and processdblogon.
   
   
   If you are running in a cluster with Oracle, modify the passwords for your secondary nodes' SIB schema, if they were changed.
   
   
8. Start your WebSphere Lombardi Edition servers.
   
   
9. Test the configuration changes using the WebSphere Application Server Administrative Console:
   
   
1. Navigate to Resources > JDBC > Data sources.
   
   
2. Check one of the modified data sources and click Test connection.
   
   
10. Restart your server or deployment manager.
    
    
11. Start the WebSphere Lombardi Edition server (Process Center or Process Server and performance data warehouse).
    
    
12. Ensure that you can log into the WebSphere Lombardi Edition portal.