Finally got Documentum successfully installed on an Ubuntu platform.
- The Content Server software got installed with no issues.
- Keep in mind to run the dm_root_task before configuring any repositories
When configuring a new repository, the installation fails to execute the scripts after creating the database for the repository. Failure – Authentication failure for the repository owner with a blank password. Follow the following steps to turn off authentication, until the repository is successfully installed:
- Change directory to the Documentum dba location ($DOCUMENTUM/dba in a default installation):
cd $DOCUMENTUM/dba
- Create a script that will be called by the server to validate passwords and always return success. Create a file named ‘dm_nocheck_password’ with the following lines:
#!/bin/sh
exit 0 - Change permissions on this file so it is executable and read/write by the dmadmin account:
chmod 4750 dm_nocheck_password
- If the headstar.dql, formats.dql and wsconfig.api script have been executed (or a custom version of them) then skip to the next step. Otherwise, execute these scripts now. The script ‘dm_apply_headstart’ in DOCMENTUM/dba/config/
will execute all three. If you cannot connect to the docbase, log into the UNIX host machine directly as the docbase owner. You will then not have to supply a password for IDQL or IAPI since you already did logging into the server. - In IDQL execute the following DQL as the Docbase owner or dmadmin superuser:# Substitute in the full path for the file_system_path directory
create dm_location object
set object_name=’novalidate_user’,
set path_type=’file’,
set file_system_path=’<file_system_path>/dba/dm_nocheck_password’
goupdate dm_server_config object
set user_validation_location = ‘novalidate_user’
goexec reinit
go - This changes the user validation location in the server config object to point to a new location object which is the file we created in step 2.
To turn the password validation back on, do the following:
- In IDQL execute the following DQL as the Docbase owner or dmadmin superuser:
update dm_server_config object
set user_validation_location = ‘validate_user’
goexec reinit
go
Note: Sometimes the validation does not work as expected! You will have to keep logging into the repository using IDQL or IAPI so you could keep a session active for the installer to use. Try re-executing the scripts until success.