Welcome to this EMC Support Community Ask the Expert conversation. This discussion will focus on using EMC Documentum Connector for Microsoft SharePoint.
By complementing SharePoint with Documentum you can provide a flexible solution that lets your users stay in their familiar SharePoint environment but at the same time use Documentum process management and document control features to get their job done faster and comply with industry and company standards. A Documentum integration could also help your IT department reduce operating cost and simplify SharePoint upgrades by avoiding the customization treadmill.
This session is to help answer questions around Microsoft SharePoint integration with Documentum.
|Tara Shaw is a Product Manager at EMC. She's been working with Documentum since 1998, specializing as a developer and architect in both email and SharePoint integration with Documentum over the last 8 years prior to becoming a Product Manager. Currently in her role she works with Documentum Connector for Microsoft SharePoint, Documentum for Microsoft Outlook, Documentum for Desktop, and Documentum Application Connectors.|
|Jeff Goodrich is a Technical Product manager at EMC. He is experienced in the entire IIG solution set at EMC, in particular: Documentum, xCP, D2, Captiva, Documentum Connector for SharePoint, Document Sciences. Jeff has worked as Systems Engineer and Product Manager for several different companies.|
This discussion begins on March 31 and concludes on April 7. Get ready by following this page to receive updates in your activity stream or through email.
Share this event on Twitter:
>> Join the next Ask the Expert: EMC Documentum Connector for Microsoft SharePoint, 3/31 - 4/7 http://bit.ly/1rMRzWL #EMCATE <<
This discussion is now open for questions. We look forward to a lively and informative event.
What is happening in the interoperability to Office365? Or is only onpremise sharepoint supported?
Currently the connector is based on an installation in the secure area of SharePoint (GAC).
This area is not acceable within Office365, so the connector will not work in Office365, as you are not allowed to install it.
It is an interesting topic. Office365 is a real cloud (public) solution. As Documentum is not (yet) available as a public cloud solution, are companies interested in a solution that will connect their private (cloud) solution to the (public) cloud??
who has an opinion???
Is it possible to have a seemless integration e.g. when you click on a document or select View option for a document in a browse webpart (or any other webpart) instead of being asked to open or save the document it would be better that the action is performed using the native application?
I have a DC4SP 7.1 instance and still have experience the same behavior.
This has to do with the ucf function of Documentum. As SharePoint out of the box does not know anything about where the document is stored it normally cannot use this.
Especially for this there is the ufc.net solution. This is a part of the dc4sp package.
It needs to be installed on the client and has the same challenges as normal ucf, but once you have it working, it will give you the same editting experience you have with webtop, but now in SharePoint.
Beside the client install, you need to change a setting in the properties file. This is written in the manual, about the donwload option.
Thank you Jeroen, well one of the reason to use this connector is the non-dependence on ucf so will have to live with the extra click. I guess the same reason would be applicable when one has to browse to a document explicitly to check it in?
Totally agree with you. UCF is something you prefer to avoid 🙂
but when you want to edit a document via the browse webpart it will take more that one extra clicks to do so, as you always have to make sure you know where you downloaded the document to, as the standard check-in will ask you to browse throught you local system to select the document.
when you often edit documents via SP or have standard SharePoint users work with the connector I don't think the standard way is acceptable and you should go for the ucf option. It is often a painful process but once it works my experience is that it will remain working. The ucf.net version has the advantange that it does not need java on the client machine and the dependency of the java version and the ability of java to go through your client firewall is not a problem!