STEPS FOR CHANGING THE INSTALL OWNER PASSWORD

1. Login into the appropriate Content Server box using telnet.

NOTE: since our Application is Load Balancer we need to change for all the three content servers.

2. Stop all the process and services (follow the start/stop document).
3. Stop the Index Server & Index Agents.

NOTE: Stop all the server side Documentum related process/services. E.g.:
Docbrokers, docbases, method servers, thumb nail server etc... If 2DAM docbase resides in the same content server its safe that we stop DTS/MTS Boxes).

4. On the /lapps/docadm location, type the command “passwd”.
5. It will ask for the current password, give it and press enter.
6. It will ask for the new password, type the new password and click enter.
7. Repeat the steps 1 to 6 for the other content servers.
8. Restart all the Documentum server side process as per the start/stop document in all the three content servers.
9. Edit the DSCredentials.xml in the location cabinets/gdm/customizations folder by login in through DA.
10. Modify with the new installation owner password

NOTE: New GDM Env (GDM Clean & GDM_PT docbases does not require to update the DSCredentials.xml since the installation owner account credentials was not hard coded. But safer sides please check when this particular Operation is being performed).

11. update the business.xml using DA in the location cabinets/gdm/ (if available)

NOTE: New GDM Env (GDM Clean & GDM_PT docbases does not require to update the business.xml since the installation owner account credentials was not hard coded. But safer sides please check when this particular Operation is being performed).


12. Repeat the steps 8 and 9 for all the 3 applications.

NOTE: login to each docbase using DA and perform the operations (if applicable).

13. Do complete healths check of all the 4 Applications.
14. Select any of the default jobs and check its status by running it manually.

Note: Consistency Checker Job is the safe option to check the status of the password change as it won’t create/modify/ update/delete any objects.

NOTE: As we are unable to test the LDAP job in PSIC, we need to make sure that it is running in production when we perform this operation.