manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Thomas (JIRA)" <>
Subject [jira] [Commented] (CONNECTORS-1535) Documentum Connector cannot find
Date Fri, 18 Jan 2019 06:18:00 GMT


James Thomas commented on CONNECTORS-1535:

{quote}Can you put in the same directory as the other DFC files and have it
be found?
It doesn't appear so. I experimented with that approach when I first reported the issue, but
here's what I've just tried as a quick check for you...

(FYI, I did this using MCF 2.12)


I reverted my to have CLASSPATH=""

Then I did the following to (a) confirm the location of dfc.jar and (b) put
in the same place

$ ls ../processes/documentum-server/lib-proprietary/dfc.jar

$ cp ../processes/documentum-server/ ../processes/documentum-server/lib-proprietary{code}
I restarted the ManifoldCF server and made a new Documentum repository connector. On save,
the UI shows, as before:

Connection failed: Documentum error: [DM_DOCBROKER_E_NO_DOCBROKERS]error: "No DocBrokers are
Reverting to CLASSPATH="."  in document-server/, restarting MCF, and then in the UI
refreshing the connector I just made brings back
Connection workin{noformat}

> Documentum Connector cannot find
> -----------------------------------------------
>                 Key: CONNECTORS-1535
>                 URL:
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Documentum connector
>    Affects Versions: ManifoldCF 2.10, ManifoldCF 2.11
>         Environment: Manifold 2.11
> CentOS Linux release 7.5.1804 (Core)
> OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode)
>            Reporter: James Thomas
>            Assignee: Karl Wright
>            Priority: Major
>             Fix For: ManifoldCF 2.13
> 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/
script before the call to Java:
> {code:java}
> Until I do this, attempts to save the connector will result in this output to the console:
> {noformat}
> 4 [RMI TCP Connection(2)-] ERROR com.documentum.fc.common.impl.preferences.PreferencesManager 
- [DFC_PREFERENCE_LOAD_FAILED] Failed to load persistent preferences from null
>         at com.documentum.fc.common.impl.preferences.PreferencesManager.locateMainPersistentStore(
>         at com.documentum.fc.common.impl.preferences.PreferencesManager.readPersistentProperties(
>         at com.documentum.fc.common.impl.preferences.PreferencesManager.<init>(
>         at com.documentum.fc.common.DfPreferences.initialize(
> ..{noformat}
> and this message in the MCF UI:
> {noformat}
> Connection failed: Documentum error: No DocBrokers are configured{noformat}
> 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 script I get this in the console, showing that (for whatever
reason) the change is significant:
> {noformat}
> Reading DFC configuration from "file:/opt/manifold/apache-manifoldcf-2.11/processes/documentum-server/"
> {noformat}

This message was sent by Atlassian JIRA

View raw message