If so, return with user has read access.
If not, return with user has no read access.
If not, return with user has no read access.
If one deny entry matches $user or one group in $groups, return with user has no read access.
If at least one entry matches $user or one group in $groups, return with user has read access.
Note:
Specific Documentum document level security examples can be found here
Example exception is: [DFC_DOCBROKER_REQUEST_FAILED] Request to Docbroker "DocumentumServer:docBrokerPort" failed; ERRORCODE: ff; NEXT: null
This error occurs because Aspire could not connect to the Documentum repository. This occurs because one or more of the necessary services aren't running. To fix this, make sure the following 4 services are running on the server that hosts Documentum:
If not, manually restart them by clicking on each in the Services panel (in Windows, click on Control Panel and do a search for "Services", then click on View local services). Highlight each service and then click Start the Service. Then try starting the connector again.
This error occurs when the dfc.properties file is not in the path specified on the DFC Properties File field.
This error occurs when the dfc.keystore file is not in the path specified in the dfc.properties file. To specify paths in the dfc.properties on a Windows system use this format: C\:/folder/folder/dfc.keystore.
This error is related to the dfc.keystore.
This error occurs because Aspire could not locate the dfc.properties file. Please make sure:
This error occurs when the dfc.keystore is not matching with the user being used to authenticate against the Documentum Server. Follow the usageInstructions.txt in File:Bug147071 pre60SP1 engr fix.zip to recreate the dfc.keystore.
This means the Documentum URL you typed contains errors. Be sure it has the correct format (dctm://server:port/docbase/cabinet/folder).
The following exception is thrown in the Aspire Console but not in the UI:
2016-10-19T21:36:48Z ERROR [/Documentum/ScanPipelineManager/Scan]: Error scanning java.lang.IllegalStateException: Stream handler unavailable due to: null at org.apache.felix.framework.URLHandlersStreamHandlerProxy.openConnection(URLHandlersStreamHandlerProxy.java:311) at java.net.URL.openConnection(Unknown Source) ... |
If this happens upgrade the felix.jar to the new version in case this issue comes up. Click here to download the latest version.