Installation owner is logged in when Documentum content server is installed. It is very rare situation when you change the installation owner. Follow below steps to change the installation owner.
- First, get new installation owner login credentials. Make sure, new installation owner account has following privileges:
- Act as part of the operating system,
- Create a token object,
- Increase quotas,
- Log in as a service,
- Log in locally,
- Replace a process‑level token.
- Login to DA as dmadmin. For the <repository> and the <global registry repo>:
- Click Storage in the navigation tree and select the storage_01 object.
- Right-click the storage_01 object and select Properties.
- Note the File System Path.
- Log out.
- Log onto Documentum server as <old install owner>.
- Stop all Documentum services:
- Documentum Docbroker Service,
- Documentum Docbase Service for selected <repository name>,
- Documentum Docbase Service <global registry repo>, if there is any,
- Documentum Java Method Server.
- Change the logon user for each Documentum process listed in step 4 to the <new install owner>.
- Open the Services control panel.
- Right-click the service, and choose Properties.
- Switch to the Log on tab.
- Enter new installation owner credentials.
- Click Apply, and then OK.
- Edit the install_owner parameter in the %DOCUMENTUM%dbaconfig<repository name>server.ini file to reference the new installation owner.
install_owner = <new install owner> - Repeat step 6 for the <global registry repo> if necessary.
- Change permissions on the %DOCUMENTUM% directory and all subdirectories.
- In Windows Explorer, select the %DOCUMENTUM% directory.
- Right-click and choose Properties.
- Switch to Owner tab.
- Click the ‘Other Users or Groups’ button, add the <new install owner>. Click OK.
- Select <new install owner>, check ‘Replace owner on subcontainers and objects’, and click the Apply button.
- Switch to the Security tab.
- Click the Advanced button.
- Click the Add button, add the <new install owner> and give it Full Control permissions. Click OK.
- On the Permissions tab, select the <new install owner>, check the ‘Replace permission entries on all child objects with entries shown here that apply to child objects’ checkbox, and click the Apply button.
- Click Yes on the warning dialog.
- The system will update the security definitions for all files and folders in the %DOCUMENTUM% directory. This could take while.
- Click OK and close the Properties dialog.
- Repeat step 8 for the File System Paths noted in step 2 if they are not included in the %DOCUMENTUM% folder structure.
10. Update Registry entries.
- Open the Registry using RegEdit.
- HKEY_LOCAL_MACHINESOFTWAREWin6432NodeDocumentumServer6.6
- Change the value of DM_DMADMIN_USER to <new install owner>.
- HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices<repository name>
- Change the value of ImagePath to contain –install_owner <new install owner>.
- HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices<global registry repo>
- Change the value of ImagePath to contain –install_owner <new install owner>.
11. Change security settings on each of the following Registry keys.
- For each key under HKEY_LOCAL_MACHINESOFTWAREWind6432NodeDocumentumDOCBASES
- Right-click the repository name and choose Permissions….
- Click the Add button and add <new install owner> to the list of users.
- Select <new install owner> and give it Full Control.
- Click the Apply button, and then OK.
- For key HKEY_LOCAL_MACHINESOFTWAREDocumentumServer6.6
- Right-click the repository name and choose Permissions….
- Click the Add button and add <new install owner> to the list of users.
- Select <new install owner> and give it Full Control.
- Click the Apply button, and then OK.
- For keyHKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesEventLogApplicationDocumentum
- Right-click the repository name and choose Permissions….
- Click the Add button and add <new install owner> to the list of users.
- Select <new install owner> and give it Full Control.
- Click the Apply button, and then OK.
12. Open database management tool and login as the database administrator.
13. Run the following SQL query to update the install owner attributes of the server config objects.
- UPDATE <repository name>.<dbo>.dm_server_config_s SET r_install_owner = ‘<new install owner>’
- UPDATE <global repository repo>.<dbo>.dm_server_config_s SET r_install_owner = ‘<new install owner>’
14. Restart the Documentum services stopped in step 4.
15. Log into DA as the <new install owner>.
- Ensure the <new install owner> account privileges are identical to <old install owner> account.
- Select <old install owner> and choose Tools – Reassign User.
- Select the <new install owner>
- Configure the job to run Now, to Unlock All objects, and to Save changes and report results.
- Click OK. This could take a while.
- Note that this process will remove the <old install owner> account from the Docbase.
- To monitor the progress of the reassignments, enter the following query in the DQL Editor, and re-run it often. When the result is zero (0), the reassignment is complete.
select count(*)from dm_sysobject where owner_name = ‘<old install owner>’
16. Run the State of the Docbase report and review for anomalies and/or errors.
17. Run the Consistency Checker and review for anomalies and/or errors. You may have to compare it with a previous report to determine if any reported inconsistencies are due to the changes you made, or were pre-existing.
18. Publish the Data Dictionary and check for errors.
19. From DA, checkout/checkin files.
You can also download pdf version of this post here
1,538 total views