manifoldcf-dev mailing list archives

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

    [ https://issues.apache.org/jira/browse/CONNECTORS-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16745820#comment-16745820
] 

James Thomas commented on CONNECTORS-1535:
------------------------------------------

One other thing: I don't believe I have evidence that it's necessary, but it is now my practice
to edit the CLASSPATH initialisation in the documentum-registry/run.sh script in the same
way as documentum-server/run.sh, again to parallel the Windows run.bat scripts.

In the experiment I just described, I reverted to CLASSPATH="" in both scripts initially,
but only changed documentum-server/run.sh before restarting MCF.

> Documentum Connector cannot find dfc.properties
> -----------------------------------------------
>
>                 Key: CONNECTORS-1535
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1535
>             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/run.sh
script before the call to Java:
>  
> {code:java}
> CLASSPATH="$CLASSPATH""$PATHSEP""$DOCUMENTUM"{code}
> Until I do this, attempts to save the connector will result in this output to the console:
>  
> {noformat}
> 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)
> ..{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 run.sh 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/dfc.properties"
> {noformat}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message