DFC_BOF_GLOBAL_REGISTRY_UNAVAILABLE

Cause

This error indicates that the client cannot connect to the Global Registry. The issue may be due to missing or incorrect entries in the client dfc.properties file.

Resolution

1. On the global registry repository host, locate the Content Server installation directory.

On Windows hosts, the default installation directory is C:\Documentum.

On UNIX hosts, this directory is specified by the environment variable $DOCUMENTUM.

2. Open the file dfc.properties that is located in the config subdirectory.

3. Copy the following keys and their values from the file:

dfc.docbroker.host[0]=host_name

dfc.docbroker.port[0]=port_number

dfc.globalregistry.repository=repository_name

dfc.globalregistry.username=username

dfc.globalregistry.password=encrypted_password

* The docbroker values should match the entries of the server.ini and dfc.properties on the Content Server.

4. Unpack the application WAR file from the from the client host.

5. Open the dfc.properties file located in WEB-INF/classes within this expanded WAR file directory.

6. Paste in the values that you copied from the global registry dfc.properties.

7. Use a text editor to configure additional properties in this file or make any changes to it.

8. Save the dfc.properties file and deploy the application.

If the problem persists following the above changes, add additional entries to the dfc.properties file to use the IP Address of the docbroker to ensure proper connectivity:

dfc.docbroker.host[0]=host_name

dfc.docbroker.port[0]=port_number

dfc.docbroker.host[1]=IP for docbroker host

dfc.docbroker.port[1]=port_number

dfc.globalregistry.repository=repository_name

dfc.globalregistry.username=username

dfc.globalregistry.password=encrypted_password