nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

EMC Documentum

stw

Hi,
EMC is working hard on the implementation of CMIS-compliance in Documentum. In the EMC Community Network you find a lot of information about the current status as well as some useful links around the CMIS-technology:
https://community.emc.com/community/labs/cmis?view=overview

Of course there's still a lot to do for the EMC-developers (performance issues https://community.emc.com/thread/106152?tstart=0 ) and there's not a final release yet. But I'm very optimistic that till the end of 2010 it will also be possible to run OpenWorkdesk against Documentum via CMIS. Please let us know if you're a Documentum developer and willing to test OpenWorkdesk against it. We'll be happy to work together with you.

By the way: did you know that we at WeWebU already implemented the prototype of a native adapter against Documentum? We decided not to productize it because of our CMIS-strategy, but if you want to use OpenWorkdesk together with Documentum right now, you don't have to wait and could start with our native implementation which should work fine for a project based solution.

🙂 stw - WeWebU CEO

Find more posts tagged with

Comments

stw

Finally: the CMIS-compliant version of Documentum (V6.7) is released with both SOAP and RESTful interfaces. I'm curious to see some test results running OpenWorkdesk against Documentum.

https://community.emc.com/community/edn/documentum/blog/2011/05/02/documentum-67-is-now-available

🙂 stw

unknown-user

Hi,

Do the wewebu community edition support documentum CMIS services ?

Thanks,
Michael

unknown-user

Hi,

    I am facing the below error when trying to login into OWD community edition.I configure EMC Documentum CMIS.

Note: I am able to connect and access Documentum CMIS services through standalone java client program.

java.lang.reflect.InvocationTargetException
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at com.wewebu.ow.server.ui.OwAppContext.handleRequest(OwAppContext.java:1268)
   at com.wewebu.ow.server.app.OwMainAppContext.handleRequest(OwMainAppContext.java:607)
   at com.wewebu.ow.server.ui.OwWebApplication.handleRequest(OwWebApplication.java:349)
   at org.apache.jsp.default20_jsp._jspService(default20_jsp.java:77)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
   at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393)
   at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
   at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
   at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
   at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
   at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
   at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
   at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)
   at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
   at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584)
   at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
   at java.lang.Thread.run(Unknown Source)
Caused by: com.wewebu.ow.server.exceptions.OwAuthenticationException: Login failed: Wrong user name or password!
   at com.wewebu.ow.server.ecmimpl.cmis.OwCMISNetwork.loginDefault(OwCMISNetwork.java:1351)
   at com.wewebu.ow.server.ecmimpl.cmis.ui.OwCMISLoginSubModul.onLogin(OwCMISLoginSubModul.java:142)
   … 26 more
Caused by: javax.xml.ws.soap.SOAPFaultException: com.sun.xml.wss.XWSSecurityException: The creation time is ahead of the current time.
   at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:189)
   at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:122)
   at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
   at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
   at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:130)
   at $Proxy125.getRepositories(Unknown Source)
   at com.wewebu.ow.server.ecmimpl.cmis.OwCMISNetwork.loginDefault(OwCMISNetwork.java:1317)

deko

Hi Michael,

this problem is/was caused by a wrong implementation of the CMIS security header used in the OpenWorkdesk CMIS adaptor for webservice communication between OpenWorkdesk and the underlying CMIS compliant repository. Good news is, that we can provide a fixed CMIS adaptor for this issue :ugeek:

Would you please download the file ow_adpcmis_3103.jar included in the zip file from Sourceforge?

To install the just downloaded fix please follow these 3 steps:

1. Stop your OpenWorkdesk Community Edition application server.

2. In your OpenWorkdesk hosting Tomcat go to <tomcat_install>/webapps/<OpenWorkdesk>/WEB-INF/lib, search for the file ow_adpcmis_3100.jar and rename the file to something similar like ow_adpcmis_3100.jar_backup

3. Copy the file ow_adpcmis_3103.jar from the downloaded zip file into <tomcat_install>/webapps/<OpenWorkdesk>/WEB-INF/lib and start the Tomcat server again.

Hopefully, you should now be able to login to your EMC Documentum installation via OpenWorkdesk Community Edition. I would be glad to hear some positive feedback if my provided solution could fix your issues.

Have a nice weekend.

[img_resize=420x150]http://jenshuebel.files.wordpress.com/2010/05/cmis_logo_small.png[/img_resize]

unknown-user

Hi depf,

Thanks for your reply

I couldn't get the ow_adpcmis_3103.jar file from sourceforge.Please give me the correct URl to download the jar.

Thanks,
Michael

deko

Hi Michael,

the URL from my latest post should work, you only must wait 5 seconds and the download will start automatically, but to be sure anyways, here is the URL once more:

https://sourceforge.net/projects/owd/files/owd%20releases%20binary/3.1.0.0/Final/ow_adpcmis_3103.zip/download

Download the ow_adpcmis_3103.zip here.

deko

You can find the fix also attached here:

[attachment=0]ow_adpcmis_3103.zip[/attachment]

ow_adpcmis_3103.zip.zip

unknown-user

Dear depf,

I am able to connect the documentum repository using the adaptor jar.Much thanks to you for the timely help.

Thanks,
Michael

deko

Nothing you would have to thank me for

:arrow: Nice to have you as part of the OpenWorkdesk community and thank you for sharing first experiences…

unknown-user

Hi,

I am trying to connect Documentum repository from WeWebU, thru CMIS.
Have done the basic configurations, logged into Documentum repository and able to view the list of available repositories in the Browse tab of WeWebU. Also, we are able to view the list of Cabinets and folder structure in the leftside Browser tree.

But we are not able to view any folder/documents in rightside Contents section. And if we click on any other tab in WeWebU, we are getting the following error.

Error Source: OECM
com.wewebu.ow.server.exceptions.OwObjectNotFoundException: Could not find repository/objectstore with ID = Main Repository.
   at com.wewebu.ow.server.ecmimpl.cmis.OwCMISNetwork.getResource(OwCMISNetwork.java:998)
   at com.wewebu.ow.server.ecmimpl.cmis.OwCMISNetwork.getObjectFromPath(OwCMISNetwork.java:917)
   at com.wewebu.ow.server.app.OwEcmUtil.createObjectFromString(OwEcmUtil.java:290)
   at com.wewebu.ow.server.plug.owrecord.OwRecordView.init(OwRecordView.java:361)
   at com.wewebu.ow.server.ui.OwEventTarget.attach(OwEventTarget.java:44)
   at com.wewebu.ow.server.ui.OwNavigationView.addView(OwNavigationView.java:89)
   at com.wewebu.ow.server.app.OwMainNavigationView.addPluginView(OwMainNavigationView.java:170)
   at com.wewebu.ow.server.app.OwMainLayout.addMasterPlugins(OwMainLayout.java:125)
   at com.wewebu.ow.server.app.OwMainLayout.init(OwMainLayout.java:188)
   at com.wewebu.ow.server.ui.OwEventTarget.attach(OwEventTarget.java:44)
   at com.wewebu.ow.server.ui.OwWebApplication.handleRequest(OwWebApplication.java:379)
   at org.apache.jsp.default20_jsp._jspService(default20_jsp.java:77)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
   at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393)
   at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
   at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
   at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
   at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
   at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
   at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
   at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)
   at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
   at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584)
   at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
   at java.lang.Thread.run(Unknown Source)

Could you please guide us to connect to Documentum from WeWebU.

Thanks,
Anandavalli

deko

Hi Anandavalli,

which version of Documentum are you using? If you can see the folders and cabinets in the browse tree, you should also be able to see the content in the result list to the right. To analyse this further, could you please enable debug mode and send more detailed stacktrace/log information when this browsing behavior occurs. Just open the file log4j.properties in WEB-INF/conf/cmis with a text editor and change the following entry

log4j.rootLogger=WARN,owd_console‍

log4j.rootLogger=DEBUG,owd_console‍

to enable DEBUG mode.

What exactly do you mean with switching to ANY other tab? Really any other tab? In general, there are only two possible mis-configuration issues, where exactly this exception/error can occur:

1. The exception can occur when clicking on the "Seach" master plugin or tab as you named it: Currently some of the included searches are configured for Alfresco and CMIS, where the term "Main Repository" is used for the main Alfresco repository.

Solution: If you delete (copy the files to some other location to have a backup)search_for_document_in_path.xml and search_for_folders_in_path.xml from WEB-INF/cmis/owsearchtemplates all Alfresco pre-configured search templates are gone and the error should not longer occur when clicking on the "Search" master plugin.

2. The error can also occur when clicking on the "Browse (register mode)" plugin/tab, as in owplugins.xml in WEB-INF/conf/cmis this plugin is configured to use

<StartupFolder>/Main Repository/Data Dictionary/</StartupFolder>‍

as it is preconfigured for Alfresco and CMIS again.

Solution: Changing the default entry to

<StartupFolder>/</StartupFolder>‍

should enable you to use this plugin also for Documentum.

:!: Please restart your application server after you changed any configuration and check it the error is still occuring after re-logging in to Documentum via OpenWorkdesk Community Edition and CMIS.

unknown-user

Hi Depf,

I am able to connect the documentum repository now. Thanks for the help.
But, the search functionality is not working.
We are unable to retrieve the documents in search results, even if they are stored in the repository. It displays 0 results.

Could you please guide us to achieve the Search functionality.

Thanks,
Anandavalli

deko

Hi Anandavalli,

have you written your own search template? If yes, could you please attach the search temmplate you have used for searching and describe your Search in detail.

Do you use one of our default search templates? If yes, which one, what is the name of the search? You would have to adopt this search template to your needs and your repository. The format and setting up of search templates is described in general in the OpenWorkdesk Configuration and Planning Guide in chapter 12.8.

What is your detailed use case for the search? Searching for all kind of documents just by title? Or searching for a defined type of object? Maybe I can help by nuilding the search template for your use case.