Archive

Posts Tagged ‘Documentum Administrator’

Utilities for Easy Handling of Administrator Work in Documentum

December 1, 2010 Comments off

Apart from installation and setting up of documentum server and client
environment, there are many important tasks which needs to be handled by an  Administrator in order for smooth and proper functioning of the set up.

Some of the tasks are mentioned below:
1. Modifying the configurations of servers, docbroker.
2. Creating new Docbases.
3. Maintaining Docbases.
4. Configuring, starting and shutting down servers.
5. Changing session configuration.
6. Managing content storage areas and content files.
7. Managing users and groups.
8. Managing security.

Utilities for Easy Handling of Administrative Task:

1.dm_error utility
We encounter various content server errors with just with an error code
without much information about it. Documentum has defined all the errors
with an expanded statement of the error, possible causes of it and
prescribes possible solutions for the error. Utility should be executed in the
command prompt of the content server.
Syntax: dm_error <error_code>

2.PreLoad Utility
Administrator operations include activities called Dumping and Loading Docbase.Dump and Load operations can be used to do the following activities:
a. Move a Docbase to one location to another.
b. Duplicate a Docbase.
c. Duplicate or move some portion of the Docbase.
A dump operation creates a binary file of objects dumped from a Docbase. If a dumped object has associated content files, the content files are either
referenced by full path or included directly in the dump file. The load operation loads the objects and content files into another Docbase.
PreLoad utility can be run on a dump file created to tell what all objects that
should be created in the new Docbase before loading the dump file. Utility can also be used to create a DQL script that you can edit and then run to create the needed objects.
Syntax:
preload docbase [-Uusername] -Ppassword -dump_file filename [-
script_file name]
The docbase is the name of the Docbase into which you are loading the dump
file. Filename is the name of the dump file, and name defines a name for the
output DQL script. If you do not include a username, the current user is
assumed.
Note: This utility does not report all storage areas in the source Docbase, but
only those that have been copied into the dump file.

3.dmclean Utility
Every Docbase requires a scheduled clean up need to be performed by
administrator. One such clean up includes removing orphaned content files.
When users delete a document, or any object that has a content file associated with it, the system deletes the object and marks the content as an orphan. The system does not delete the actual content file. This must be done using the dmclean utility. Dmclean can be run using:

a. Documentum Administrator.
b. A DQL EXECUTE statement.
Syntax:
EXECUTE do_method
WITH method = ’dmclean’,
arguments = ’-no_content -no_note -no_wf_template’
c. An Apply method
Syntax:
apply,session,NULL,DO_METHOD,METHOD,S,dmclean, ARGUMENTS,S,’-no_content -no_note -no_wf_template’
d. From Content Server command prompt
dmclean -docbase_name docbase -init_file init_file_name
-no_content -no_note -no_wf_template
Where wheredocbase is the name of the Docbase and init_file_name
is the name of the server.ini start up file for the Docbase’s server.

4.dmfilescan Utility
This utility is used to scan the one or more storage area and find any content
files that do not have associated content objects. The utility scans for orphaned files which are over 24 hours old.
Running the utility using EXECUTE statement:
EXECUTE do_method WITH method = ’dmfilescan’,
[arguments = ’[-s storage_area_name] [,-from directory1]
[,-to directory2]’]
The utility automatically saves the output to a document that is stored in
the Temp cabinet. FALSE.) The output is a generated script that includes
the informational messages generated by the utility.
Running the utility using Content Server command prompt:
dmfilescan -docbase_name name -init_file init_file_name
[-s storage_area_name][-from directory1][-to directory2]
The init_file_name is the name of Content Server’s server.ini file. This is
one of the server start up files.

5.dm_crypto_change_passphrase Utility
Every installation of a Content Server creates a key called Administration
Encryption Key (AEK). This is used to encrypt:
a. The Docbase keys.
b. Documentum passwords, such as those used by Content Server to
connect to the RDMS or any other Docbase.
This AEK is stored at: %DOCUMENTUM%\dba\secure\aek.key and this key also are encrypted using a default passphrase provided by Documentum. It is always advisable to change the default passphrase. To change the default passphrase we can use dm_crypto_change_passphrase Utility.
Syntax:
dm_crypto_change_passphrase [-location location][-passphrase
[old_passphrase]][-newpassphrase [new_passphrase]][-noprompt][-help]
Location is the place where AEK is placed for which we need to change the
passphrase.
old_passphrase is the old passphrase name.
new_passphrase is the new passphrase name.
-noprompt should be used if any one the argument mentioned above is not
used. It’s like the end specify mentioning the end of arguments.
-help returns help information for the utility.

6.IAPI Utility
IAPI Utility is used to issue direct method call to the server.
Running the utility from the server command prompt:
iapi32 [-Uusername|-ENV_CONNECT_USER_NAME]
[-Pos_password|-ENV_CONNECT_PASSWORD] [-Llogfile] [-X][-E]
[-V-][-Q] docbase|-ENV_CONNECT_DOCBASE_NAME [-Rinputfile]
[-Ftrace_level][-Sinit_level][-Iescape_character][-zZ]
[-Winteger][-Ksecure_mode]
Order of the parameter does not hold importance.
Username- Identifies the name who is starting the session.
ENV_CONNECT_USER_NAME- User name in looked in the environment
variable DM_USER_NAME.
Password- User’s operating system password.
ENV_CONNECT_PASSWORD- Password is looked in the environment
variable DM_PASSWORD.
-Llogfile – Directs the server to start a log file for the session.
You must include the file name with the argument. You can specify a
full path.
-X Allows prompt for domain.
-E Turns on echo.
-V- Turns verbose mode off. The utility runs in verbose
mode by default. If you turn verbose mode off, the
system does not display the IAPI prompt, error
messages, or any responses to your commands
(return values or status messages).
-Q Directs the utility to provide a quick connection test. The utility attempts to connect and exits with a status of zero if successful or non-zero if not.
It provides error messages if the attempt is not successful.
Docbase- Docbase name which is intended to access.
ENV_CONNECT_DOCBASE_NAM – finds the name of the docbase
from environment variable DM_USER_NAME.
-Rinputfile input file with API methods.
-Ftrace_level Turns tracing on.
-Sinit_level Defines the connection level established when you
start the API session.

-Iescape_character Defines an escape character for certain symbols
such as a forward slash (/).
-zZ Specifies Windows NT Unified Logon.
7.IDQL Utility
IDQL is also a useful as a tool for testing and other tasks that support an
application or installation because it allows you to run scripts and batch files.
Running the utility from the server command prompt:
idql32 [-n] [-wcolumnwidth]
[-Uusername|-ENV_CONNECT_USER_NAME]
[-Pos_password|-ENV_CONNECT_PASSWORD][-Ddomain]
docbase|-ENV_CONNECT_DOCBASE_NAME [-Rinput_file]
[-X][-E][-Ltrace_level][-zZ][-Winteger][-Ksecure_mode]
The parameter being the same as mentioned in above utility.

Changing Documentum’s Installation Owner

November 24, 2010 1 comment

When initially installing Documentum, the installation owner is set to the logged-in user that performs the Documentum installation. It is preferable to install Documentum and never change the installation owner. However, sometimes company policy dictates that the original installation must be changed. Reasons for the change may be that the user name does not conform to a new naming policy or that originally the user was not a domain user but now should be.Changing the installation owner involves changes to both the operating system and the docbase configuration. This is not a minor change within Documentum, so upfront planning and coordination between the Documentum System Administrator and Infrastructure Team is required.

To get the most from this article, you should already have:

  • A detailed knowledge of Documentum Content Server
  • A detailed knowledge of your company’s implementation of Documentum
  • A detailed knowledge of Windows 2000 Operating System

For purpose of this document, we are going to refer to the following users:

Original Installation Owner:

username = “dmadmin”

password = “dmadmin”

domain = “it”

New Installation Owner:

username = “new_dmadmin”

password = “new_dmadmin”

domain = “dctm”

How Documentum uses the installation owner ?

The Documentum installation owner is the operating system user that owns the server executable and other related files along with the OS process when the server is running. The installation owner is originally determined when the server is installed; it is the logged-in user that performed the Documentum installation. This user is given the following privileges:

  • Operating System:
    • ‘Log On As’ rights to start Documentum Services such as Docbase, Docbroker, Java Method Server and other installed Documentum products (i.e. Site Caching Services).
    • Permission to change the Content Server configuration (i.e. upgrade, create, and delete docbases)
    • Folder level permission to view data, configuration, and many log files located under the %DOCUMENTUM_HOME% directory.
  • Docbase & Content Server:
    • Superuser and System Administrator rights
    • Assignment to administrator (Web Publisher), docu, and admingroup groups
    • Set as the r_install_owner value in the dm_server_config object.
    • Set as the operating system user to run several Administrative jobs such as dm_DataDictionaryPublisher and dm_FulltextMgr

Preparing to Make the Change

Preparation is an important step when making any major change within your Documentum environment. The following are steps recommended to make your life easier when updating the installation owner.

  • Determine best approach for changing the installation owner. The three documented approaches are:
    1. Minimal Impact – Update only the operating system user and the user_os_name of the docbase user
    2. Medium Impact – Create a new user in the docbase to be the installation owner while letting the old installation owner continue to own any existing objects
    3. Largest Impact – Create a new user in the docbase to be the installation owner and reassign the previous installation owner’s objects to the new user.
  • Communicate and Make a Plan – Have your team ready and ensure everyone is aware of the plan. Communication is an important factor for success. Ensuring everyone is aware of their role will help make the change go smoothly.
  • TEST – Set up a test docbase to test updating the installation owner prior to making any change in a Production environment
  • Purge all old log files – Changing the installation owner requires updating permissions on Documentum data and log files. Reducing the amount of unneeded data will greatly speed up the process. This is especially important if you will be following Approach 3
  • Run the Consistency Checker – This report gives you a list of bad data within your system. Cleaning up inconsistent data before making the change will speed up the process and in the end make your life easier.
  • Back up all environments – Before performing any major change within Documentum you should ALWAYS back up your environment. This is a System Administration best practice. Work with your database administrators and infrastructure team to back up both the content server files and the database.
  • Set up the new installation user
    • Add the new installation user to the Administrator group on the Windows 2000 machine
    • Set the user to act as part of the operating system on the Windows 2000 machine. This setting can be found under Control Panel\Administrative Tools\Local Security Settings\Local Policies\User Rights Assignment\Act as part of the operating system
    • Update permission on all folders, subfolders and files under %DOCUMENTUM_HOME%> to remove the old installation owner and add new installation owner with full control

Approach 1: Updating only the installation user OS name  

The simplest way to change the installation owner is to change the existing docbase user’s user_os_name/user_domain. This is the recommended solution in most cases.

Pros

  • Simple way to change the installation owner. This solution does not require updating Documentum objects therefore it reduces the risk of error and amount of work required with large Docbases.

Cons

  • The user_name within Documentum remains the same therefore the previous installation owner name will appear as the display name within Documentum.

Steps

  1. Log into Documentum as an administrator
  2. Update the current Documentum installation user’s user_os_name to the new installation owner:
    update dm_user object set user_os_name = ‘new_dmadmin’, set user_domain = ‘dctm’ where user_name = ‘dmadmin’;
  3. Log onto the Windows 2000 server as current installation owner
  4. Stop Services for all Documentum services (i.e. Docbases, DocBroker, Java Method Server, Site Caching Services)
  5. Edit the install_owner and user_auth_target parameters in the server.ini file to reference the new installation owner and domain for each Docbase in the installation. The server.ini file is located in %DOCUMENTUM_HOME%\dba\config\docbase_name\server.ini or it can be accessed through the Documentum Server Manager.
  6. Within Windows Explorer, change permission to give the new installation user full control on the all directories, subdirectories and files under the Content Server installation root directory (%DOCUMENTUM_HOME%). To update permission within Explorer:
    • Select the directory and right click to display a menu; choose Properties from the menu
    • Select the Security tab on the Properties dialog box
    • Select ‘Add’ to add a new user; select the new installation owner
    • Check Allow for Full Control
    • Remove the previous installation owner from the list of users with permission on the directory; Click Ok

Many subfolders and files under %DOCUMENTUM_HOME% are not set out of box with the allow inheritable permissions from parent to propagate to this object checked. Therefore you cannot assume that a subfolder or file is inheriting permission from its parent and you must ensure that you update the permission on ALL files and subfolders located under %DOCUMENTUM_HOME%. %DOCUMENTUM_HOME% subfolders and files that need to be update because they are not inheriting permission from its parent include but may not be limited to: \data; \data\[docbase_name]\’all subfolders’; \dba; \dba\auth; \dba\config\[docbase name]\dbpasswd.txt; \dba\config\[docbase name]\webcache.ini; \dba\config\[docbase name]\webcache.ini.old; \dba\log\’subfolders’; \dba\secure; \dba\secure\aek.key; \fulltext; \product; \share; \share\data\common\’subfolders’; \share\data\events\’subfolders’; \share\temp\replicate\’subfolders’; \share\temp\dm_ca_store\’subfolders’

Note: If your content storage directories are not located under the %DOCUMENTUM_HOME%\data directory, change the permissions on each content storage directory as well.

  1. Edit the Windows Registry with new installation owner:
    • Update HKEY_LOCAL_MACHINE\SOFTWARE\Documentum\Server\version_no
      • Change the value of DM_DMADMIN_USER to the new installation owner user name
      • Change the value of DM_DMADMIN_DOMAIN to the new installation owner user domain
  2. Set up the appropriate start-up information for Documentum Services
    • Choose Control Panel -> Administrative Tools -> Services
    • Select Documentum Services (i.e Documentum Docbase docbase_name, Documentum Docbroker, Documentum Java Method Server, Documentum SCS_Source)
      • Right click on Service and select Properties
      • On the Log on Tab, enter the new installation name and password under Log On As: This Account
  3. Move any Documentum-related Programs in start menu (C:\Documents and Settings\old_user_name\Start Menu) to the new installation owner
  4. Restart Windows 2000 Server; Log in as the new installation owner
  5. Start the Docbases; View logs to check for errors

Approach 2: Creating a new Documentum installation user without Object Reassignment

This procedure is recommended if your policies require that the docbase user’s user_name be changed but do not requite that existing objects be assigned to the new user.

Pros

  • The user_name within Documentum is updated to the new installation owner therefore it will appear as the display name within Documentum (similar to how it would appear if the docbase had been installed originally as this user).

Cons

  • The old installation user remains within the docbase. However, if the old operating system user has been removed no one will be able to log in as this user
  • Tasks that were previously assigned to the old installation owner will not be accesible

Steps

  1. Log onto the Windows 2000 server as current installation owner
  2. Stop Services for all Docbases and the DocBroker.
  3. Edit the install_owner and user_auth_target parameters in the server.ini file to reference the new installation owner and domain for each Docbase in the installation. The server.ini file is located in %DOCUMENTUM_HOME%\dba\config\docbase_name\server.ini or it can be accessed through the Documentum Server Manager.
  4. Within Windows Explorer, change permission to give the new installation user full control on the all directories, subdirectories and files under the Content Server installation root directory (%DOCUMENTUM_HOME%). To update permission within Explorer:
    • Select the directory and right click to display a menu; choose Properties from the menu
    • Select the Security tab on the Properties dialog box
    • Select ‘Add’ to add a new user; select the new installation owner
    • Check Allow for Full Control
    • Remove the previous installation owner from the list of users with permission on the directory; Click Ok

Many subfolders and files under %DOCUMENTUM_HOME% are not set out of box with the allow inheritable permissions from parent to propagate to this object checked. Therefore you cannot assume that a subfolder or file is inheriting permission from its parent and you must ensure that you update the permission on ALL files and subfolders located under %DOCUMENTUM_HOME%. %DOCUMENTUM_HOME% subfolders and files that need to be update because they are not inheriting permission from its parent include but may not be limited to: \data; \data\[docbase_name]\’all subfolders’; \dba; \dba\auth; \dba\config\[docbase name]\dbpasswd.txt; \dba\config\[docbase name]\webcache.ini; \dba\config\[docbase name]\webcache.ini.old; \dba\log\’subfolders’; \dba\secure; \dba\secure\aek.key; \fulltext; \product; \share; \share\data\common\’subfolders’; \share\data\events\’subfolders’; \share\temp\replicate\’subfolders’; \share\temp\dm_ca_store\’subfolders’

Note: If your content storage directories are not located under the %DOCUMENTUM_HOME%\data directory, change the permissions on each content storage directory as well.

  1. Edit the Windows Registry with new installation owner:
    • Update HKEY_LOCAL_MACHINE\SOFTWARE\Documentum\Server\version_no
      • Change the value of DM_DMADMIN_USER to the new installation owner user name
      • Change the value of DM_DMADMIN_DOMAIN to the new installation owner user domain
    • Update – HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DmServerdocbase_name
      • Change the -install_owner parameter in the value for ImagePath to the new installation owner user name
  2. Set up the appropriate start-up information for Documentum Services
    • Choose Control Panel -> Administrative Tools -> Services
    • Select Documentum Services (i.e Documentum Docbase docbase_name, Documentum Docbroker, Documentum Java Method Server, Documentum SCS_Source)
      • Right click on Service and select Properties
      • On the Log on Tab, enter the new installation name and password under Log On As: This Account
  3. Move any Documentum-related Programs in start menu (C:\Documents and Settings\old_user_name\Start Menu) to the new installation owner
  4. Restart Windows 2000 Server; Log in as the new installation owner
  5. Start the Docbases; View logs to check for errors

 

Approach 3: Creating a new Documentum installation user with Object Reassignment

If the requirements around changing the installation owner include changing the Documentum Installation user_name and removing the old installation user from Documentum, then you must create a new installation Documentum user and reassign the previous user’s objects and tasks to the new user. This is the most complex, time consuming, and risky procedure and is not recommended unless completely necessary.

Pros

  • The user_name within Documentum is updated to the new installation owner therefore it will appear as the display name within Documentum
  • The previous Documentum installation owner will be removed from the Docbase

Cons

  • Reassigning the previous installation owner to the new installation is error prone and time consuming for large docbases. However, risk can be reduced by purging old log files prior to changing the installation owner

Steps

The steps are the same as in Approach 2 with the following steps required at the end:

  1. Log into Documentum Administrator as the new installation owner
    • Navigate to Administration -> User Management -> Users
    • Select the previous installation owner (’dmadmin’)
    • Select Tools -> Reassign User
    • Repeatedly run the following query: select count(*), acl_name from dm_sysobject where acl_domain = ‘dmadmin’ group by acl_name Note: The job may take a while to run depending on the amount of data. Once the query returns no rows the job is complete.

Smoke Testing the Change

After any major change to your Documentum infrastructure you should Test, Test, Test. Detailed test steps vary based on your Documentum application environment. It is important to have a test plan defined during your preparation. However, below are some brief smoke test steps which should prove helpful:

  • If you are using Web Publisher:
    • Log into Web Publisher as the new installation owner
    • Create content based on a template
    • Start a workflow; Log in as the workflow approver to ensure the task went to the correct user
    • Access Web View
  • If you are using Documentum Administrator:
    • Log into Administrator as the new installation owner
    • Spot check jobs (i.e. dm_DataDictionaryPublisher, dm_FulltextMgr , etc.) to ensure they are successfully running
  • If you are using Site Caching Services:
    • Log into Administrator as the new installation owner
    • Navigate to Site Publishing Configuration
    • Check a configuration; run an ‘End to End’ test
  • If you are using any other Documentum products:
    • Log into each application
    • Perform everyday user tasks
  • Run Consistency Checker (dm_ConsistencyChecker) Job. This report appears under System/SysAdmin/Reports

Common Issues/Helpful Hints

  1. Setting user permission on %DOCUMENTUM_HOME% can be cumbersome, is there an easier way to perform this task?
    Yes. It would be recommended to have a system administrator run a windows scripts to update all folders and files under %DOCUMENTUM_HOME%. Another shortcut would be to set the local Administrator group on the Windows 2000 with Full Control permission on all subfolders and files under %DOCUMENTUM_HOME%. Later, when updating an installation owner you would just need to add/remove users from the local Administrator group. Setting the Administrator group permissions in this fashion also eases backing up Content Server files.
  2. Can you update only the user domain?
    Yes. To update only the user domain you will need to:  

    • Add the new domain user to the Administrator group on the Windows 2000 server; Set up the user as act as part of the operating system
    • Update the user_domain attribute of the installation owner:
      update dm_user object set user_domain = ‘[new domain]‘ where user_name = ‘[installation owner]‘
    • Edit the user_auth_target parameters in the server.ini file to reference the new domain for each Docbase in the installation.
    • Update permission on all subfolders and files under %DOCUMENTUM_HOME% to use the new domain user.
    • Update Windows Registry – HKEY_LOCAL_MACHINE\SOFTWARE\Documentum\Server\version_no
      • Change the value of DM_DMADMIN_DOMAIN to the new domain
    • Set up the appropriate start-up information (Log on As: This Account) for Documentum Services to use the new domain user
  3. Can you update only the user password?
    Yes. Stop all Documentum services (Docbases, DocBroker, Java Method Server, Site Caching Services). Within the service properties under the Log on Tab, enter the new password under Log On As: This Account.
  4. What if after running the Reassign User job there are still objects referencing the old user?
    This sometimes happens if there are many objects (such as log files) owned by the old installation owner. A solution to this is to wait for the job to complete and then recreate the previous installation owner within Documentum then run ‘Reassign User’ again. Continue this until the following queries return 0 rows:
  5. select count(*), acl_name from dm_sysobject where acl_domain = '[old installation owner]‘ group by acl_name;
  6. select r_object_id from dm_sysobject where owner_name= ‘[old installation owner]‘;

Hope this experiment is useful .

Renaming Users Using Documentum Administrator

March 25, 2010 Comments off

While supporting Documentum, there can be a complex situation where we have to rename the user and reassign all objects where user was the owner or a participant to the new name. Following are the list of objects which needs to be changed.

  • ACL (Active control List)
  • Alias Set
  • Sysobjects
  • Workflow and related objects
  • Routers
  • Activities
  • Workflow
  • Workitem
  • dmi_queue_item
  • Groups
  • dm_registered
  • dm_type
  • dmi_type_info

All these things except last 3 can be changed at one shot using “Reassign” tool of Documentum Administrator. The last 3 items needs to be reassigned manually. The process for using reassign tool is as in below.

Process

The process which can be used to rename the user is described in below flowchart. It is a two step process. In step1, we will analyze the effects of renaming the user.

Step-1

 In step2, we will go ahead and rename the user.

Step-2

User Management using Documentum Administrator

March 24, 2010 Comments off

Documentum Administrator is the Web-based tool for administering Content Server. By Documentum Administrator all the administrative tasks for a single installation or a distributed enterprise can be performed from one location.

One of the administrative tasks of Documentum Administrator is User Management. To access a Docbase, a person must be defined as a user in that Docbase.

The Administration/User Management displays a list of users in the current Docbase. Search for users can be done by their user name in the Docbase, user OS name (name on the operating system), or default group.

How to locate users in Docbase

1.  Connect to the Docbase where we want to locate a particular user.

2.  In the left-hand pane, click Administration.

3.  Click User Management.

4.  Click Users.

5.  To search by user name, user OS name, or default group, type in the information and click   Go 

 How to create new users

One must have Sysadmin or Superuser privileges to create users.

1.  Connect to the Docbase where we want to create new users.

2.  Click Administration –> User Management.

3.  Click File –> New –> User. (Check Right Hand Side)

  4.  Indicate whether the user’s state is active or inactive. An active user can connect to a    

     Docbase whereas an inactive user cannot.

5.  In the Name field, type the user’s name.

6.  Select a User Source from the drop-down list.

  • UNIX Only: Select this for the default UNIX user authentication.
  • Domain Only: Select this if the Docbase has Windows domain authentication enabled and the user must be authenticated against a domain.
  • UNIX first: Select this if the Docbase has Windows domain authentication enabled and the user must be authenticated first against UNIX, then against a domain.
  • Domain First: Select this if the Docbase has Windows domain authentication enabled and the user must be authenticated first against a domain, then against UNIX.
  • LDAP: Select this if users are authenticated against an LDAP server.

7.  In the E-Mail Address field, type the user’s email address. This is the address to which  

     notifications are sent for workflow tasks and registered events.

8.  In the User OS Name field, type the user’s operating system user name. This is used by the 

     user to login to the docbase.

9.  In the Windows Domain field, type the user’s Windows domain.

10. Select a home Docbase for the user.

11. Designate the user’s default folder which is the default storage place for any object the  user creates. To use an  existing Docbase folder, click Choose existing folder and to create  a folder with the user’s name, click Choose/Create folder with user name.

12. Click Select Group and select a default group for the user.

13. Click Select Permission Set and select a default permission set for the user.

14. Select the user’s privileges from the drop-down list.

User privileges authorize certain users to perform activities that are required to administer and maintain the system. The privilege levels are:

  • None
  • Create Type
  • Create Cabinet
  • Create Cabinet and Type
  • Create Group
  • Create Group and Type
  • Create Group and Cabinet
  • Create Group, Cabinet, and Type
  • System Administrator
  • Superuser

15. Select the user’s client capability from the drop-down list.

 There are four types of users:

  • Consumer
  • Contributor
  • Coordinator
  • System Administrator 

16. Click Finish and new user is created.

How to delete users

We can remove users from the Docbase, but Documentum strongly recommends making users inactive rather than deleting them from the Docbase.

 When a user is deleted, the server does not remove the user’s name from objects in the Docbase such as groups and ACLs. Thus when we delete a user, we must also remove or change all references to that user in objects in the Docbase.

%d bloggers like this: