When you install Documentum Services, a WAR file is deployed as part of the process. This WAR file includes a dfc.properties file (located at WEB-INF/classes) that provides the configuration settings for the Documentum Foundation Classes runtime and it must be edited to provide the correct settings for the connector to be able to access the Documentum repository.
There are several ways to update the settings in this file:
- Include: Use an #include statement to point to another dfc.properties file that is located outside of the web application on the local file system. This operation enables easy access to the settings and allows you to modularize your configuration settings. For example, you can add the following line as the only entry in the dfc.properties file that is included in the WAR file:
- Copy: Copy the contents of the Content Server’s dfc.properties file (usu. located at C:\Documentum\config\dfc.properties) into your own dfc.properties file in the WEB-INF/classes folder.
Docbroker and Global Registry Properties
The dfc.properties file includes critical settings that are required for Documentum Services to reach a connection broker (also called a Docbroker) and connect to the Content Server. The following table summarizes the key DFC properties and a description of each:
The fully qualified hostname for the connection broker. You can add backup hosts by adding new properties and incrementing the index number within the brackets.
When you use a port for the connection broker other than the default of 1489, add a port key.
The global registry repository name.
The username of the global registry user. The global registry user, who has the default username dm_bof_registry, must have read access only to the objects that are in the /System/Modules directory and the /System/NetworkLocations directory.
An encrypted password value for the global registry user.
For the global registry username and password, you have the following options:
- Copy the username and encrypted password for the global registry user from the dfc.properties file on the global registry Content Server host, or
- Select another global registry user and encrypt the password using the following command:
java -cp dfc.jar com.documentum.fc.tools.RegistryPasswordUtils <password_to_be_encrypted>