You need to figure out the repository owner for a repository. What do you do?
dmadmin is the conventional installation owner. Indeed, it is possible that there is no user named
dmadmin in a repository.
So, maybe use the installation owner – the user id on OS used for installing the Content Server. Well, installation owner is separate from repository owner and there is no requirement for the two to be the same. Actually, they should be kept separate – in many organizations installation responsibilities are separated from day-to-day administration responsibilities.
Hmmm, is it same as the repository name? Maybe. When you configure a new repository, you have a choice to set up the database beforehand or to let the configuration script set it up for you. If you let the script do this work, it defaults the DB account to be the same as the repository name. In this case, this guess would be valid. However, it is not required to be so. If the database is already set up, you can provide this information to the configuration script and it uses the provided DB user to create the corresponding user in the repository. This user becomes the repository owner.
Then, is there an attribute on
dm_docbase_config which identifies the repository owner? We are getting close. There isn’t an attribute called docbase_owner or repository_owner. However, the owner of the docbase config object (identified by
owner_name) is the repository owner. If you are looking for the exact DB login name for the repository owner then look at the
user_db_name attribute on the user object for the repository name. For the repository owner, it is same as the
user_name by default.
operator_name on a
dm_server_config object defaults to the repository owner name. Remember that this is just a default. Further, there can be multiple content servers serving one repository.