Viewing or modifying the repository configuration

You can modify some, but not all, of the repository configuration values. This section describes the values that can be modified using Documentum Administrator.

To view or modify the repository configuration:

Start Documentum Administrator and connect as a superuser to the repository you want to modify.
Navigate to Administration > Basic Configuration > Repository to access the Repository list page.
Select the repository name and then select View > Properties > Info.
The Repository Configuration Properties - Info page displays.
Modify the values that you want to change, as described in Table 2.2.
If you are running the repository on a UNIX host, you can enable Windows domain authentication.
Click the Synchronization tab to manage the repository synchronization with Documentum Offline Client.
For more information, refer to Modifying repository synchronization.
Click OK to accept the changes or Cancel to discard the modifications.

Table 2.2. Repository Configuration Properties

Field label	Value
Database	The name of the RDBMS vendor. Read-only.
Repository ID	The repository ID number assigned during installation. Read-only.
Federation	Specifies if the repository is a member of a federation. Read-only.
Security	The security mode of the repository. ACL and None are valid values. None means repository security is disabled. ACL means access control lists (permission sets) are enabled. Read-only.
Index Store	The name of the tablespace or other storage area where type indexes for the repository are stored.
Partitioned	Indicates whether the repository is partitioned. When a repository is created or updated with partitioning enabled, the Content Server sets the flag to True. The Partitioned field is: Not selectable or changeable. Available only in 6.5 repositories.
Crypto Mode	Displays the type of cryptography used by Content Server.
Crypto Key Store	Indicates the encryption key stored on the Content Server.
Dormancy Status	Indicates the dormancy status of repository. Note The Dormancy Status label is only visible for 7.0 and later versions of repositories.

Update Configuration Changes
Re-Initialize Server	Select to reinitialize the server to which you are connected. This is necessary for changes to objects to take effect.

Configuration Changes
Folder Security	Specifies whether folder security is enabled. Select to enable folder security. The server performs the permission checks required by the repository security level and for some operations, also checks and applies permissions on the folder in which an object is stored or on the objects primary folder.
Rich Media	Specifies whether the server processes rich-media content. This feature only works if Media Server is installed in the repository. If you enable the Rich Media feature, you must re-initialize the server for the changes to take effect.
Workflow Packages	Specifies whether the object names of workflow package components are displayed. By default, the object names are displayed. Select this option to not display the object names.
Data Dictionary Locales	Specifies the locale of the data dictionary. The default local is en (English). Click Edit to configure a different locale. The server must be reinitialized for any changes to be visible.
Oldest Client Version	Specifies which DFC version is used for chunked XML documents. The value must be changed manually. If the field is left blank, the DFC format is compatible with client versions earlier than the current DFC version. If a particular DFC version is specified, clients running an earlier DFC version cannot access the chunked XML documents. Set the property value to the client version number in the format XX.YY, where X is the major version and Y is the minor version.
Modifications Comment	This field is optional. It can be used to add a comment about any modifications made to the repository configuration.
Default Application Permit	The default user permission level for application-controlled objects accessed through an application that does not own the object. Valid values are: 2: Browse 3: Read 4: Relate 5: Version 6: Write 7: Delete The default value is 3, Read permission.
Fulltext Install Locations	Specifies the Verity versions installed and their locations in pre-5.3 repositories.
Content Storage Services Enabled	Specifies whether Content Storage Services were enabled during Content Server installation. If the value is true, Content Storage Services are enabled.
Minimum Owner Permission	Specifies the minimum permission for an object owner after all ACL rules have been applied. The permission applies to the entire repository. Valid values are: Browse Read Relate Version Write Delete The default value is Browse.
Minimum Owner Extended Permission	Specifies the minimum owner extended permissions for an object owner after all ACL rules have been applied. One or more extended permissions can be selected. By default, no extended permission is selected. Valid values are: Execute Procedure Users with superuser privileges can change the owner of an item and run external procedures on certain types. Change Location Allows the object owner to move the object in the repository. Change State Allows the object owner to change the state of a lifecycle attached to the object. Change Permission Allows the object owner to modify the basic permissions associated with the object. Change Ownership Allows the object owner to change the object owner. Extended Delete Allows the object owner to delete the object. Change Folder Links Allows the object owner to link or unlink the object to a folder.

Authorization Settings
MAC Access Protocol	The file-sharing software type in use for Macintosh clients. Valid values are: None NT Ushare Double The default value is None. If you change the value from NT, Ushare, or Double to None, existing resource forks are no longer be accessible. To change the value from or to NT, Ushare, or Double, you must first change the value to None, save the configuration, and then change it from None to the new value.
Authentication Protocol	Defines the authentication protocol used by the repository. On Windows, if set to Domain Required, it indicates that the repository is running in domain-required mode. If a repository is running in domain-required mode, the login domain value in the login ticket generated for a user attempting to log in using an inline password defaults to the domain of the superuser even if the user on the login ticket belongs to a different domain. Users from a different domain must specify the their login domain name when logging into the repository. If a repository is running in no-domain required mode, users can login with only their user name and inline password. It is also possible to prepend the user name with a backslash (\). A backslash specifies an empty domain. On UNIX platforms, choose between UNIX authentication or Windows domain authentication.
Cached Query Effective Date	Used to manage the client query caches. The default is NULLDATE.
Run Actions As	The user account that is used to run business policy (document lifecycle) actions. Options are: Session User (default) Superuser Lifecycle Owner Named User If selected, click the Select User link to access the Choose a user page to select a user.
Login Tickets	Specifies that all other repositories are trusted and login tickets from all repositories are accepted by the current repository. If selected, Allow login tickets from repositories is not displayed.
Allow login tickets from repositories	This field is only displayed if Allow all login tickets is not selected. Click Select to access the Choose Repositories page to designate repositories whose login tickets are permitted in the current repository (the trusted repositories).
Designate Login Ticket Expiration	Specifies the earliest possible creation date for valid login tickets. Tickets issued before the designated date are not valid in the current repository. Select one of the following: Null date: Specifies that there is no cutoff date for login tickets in the current repository. This is the default value. Expire login tickets on the following date and time: Specifies the earliest possible creation date for valid login tickets. Use the calendar control to choose the correct date and time. Login tickets created before that time and date cannot be used to establish a connection. Currently connected users are not affected by setting the time and date.
Maximum Authentication Attempts	The number of times user authentication can fail for a user before that user is disabled in the repository. Authentication attempts are counted for logins and API methods requiring the server to validate user credentials, including the Changepassword, Authenticate, Signoff, Assume, and Connect methods. By default, the installation owner’s account is not subject to the failure threshold and is not disabled when it reaches the maximum number of attempts. You can modify the installation owner account from the User pages. A value of zero (0) means that the feature is not enabled. Requires the server to be reinitialized for changes to take effect.
LDAP Synchronization On-Demand	Used to synchronize LDAP directory users with the repository between scheduled runs of the LDAP synchronization job: When cleared, LDAP directory users who do not exist in the repository cannot log in. When selected, if an LDAP directory user attempts to log in and is found not to exist in the repository, Content Server searches all active directory connections for the user. If the user is found and can be authenticated, the user is created in the repository.
Privileged Clients	Boolean. If selected, indicates that the repository is accessible to privileged clients only. This checkbox is only available if a DFC client exists in the repository and is approved to perform privilege escalations.

Viewing or modifying the repository configuration

Note