Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
ManifoldCF 2.10, ManifoldCF 2.11
-
None
-
Manifold 2.11
CentOS Linux release 7.5.1804 (Core)
OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode)
Description
I have found that when installing a clean MCF instance I cannot get Documentum repository connectors to connect to Documentum until I have added this line to the processes/documentum-server/run.sh script before the call to Java:
CLASSPATH="$CLASSPATH""$PATHSEP""$DOCUMENTUM"
Until I do this, attempts to save the connector will result in this output to the console:
4 [RMI TCP Connection(2)-127.0.0.1] ERROR com.documentum.fc.common.impl.preferences.PreferencesManager - [DFC_PREFERENCE_LOAD_FAILED] Failed to load persistent preferences from null java.io.FileNotFoundException: dfc.properties at com.documentum.fc.common.impl.preferences.PreferencesManager.locateMainPersistentStore(PreferencesManager.java:378) at com.documentum.fc.common.impl.preferences.PreferencesManager.readPersistentProperties(PreferencesManager.java:329) at com.documentum.fc.common.impl.preferences.PreferencesManager.<init>(PreferencesManager.java:37) at com.documentum.fc.common.DfPreferences.initialize(DfPreferences.java:64) ..
and this message in the MCF UI:
Connection failed: Documentum error: No DocBrokers are configured
I mentioned this in #1512 for MCF 2.10 but it got lost in the other work done in that ticket. While setting up 2.11 from scratch I encountered it again.
Once I have edited the run.sh script I get this in the console, showing that (for whatever reason) the change is significant:
Reading DFC configuration from "file:/opt/manifold/apache-manifoldcf-2.11/processes/documentum-server/dfc.properties"