.NET 和 Documentum 5.3 集成
我需要实现自定义 .NET 应用程序与 Documentum 5.3 的集成。 .NET 应用程序应提供在配置的 Documentum 5.3 中管理文件夹、文档、元数据和搜索的功能。
我发现 Documentum 5.3 中提供了以下集成选项：
- Documentum ADO.NET 服务
- Documentum 基础类（包括 PIA 和 Web 服务支持）
- WDK
我想对于 .NET 应用程序来说，更好的变体是 DFC PIA。但在这里 - http://forums.contology.com/index.php?showtopic=23639< /a> - 大家正在讨论 DFC PIA 已被弃用并且很快不会得到支持（我知道这对于 5.3 来说已经足够了 - 但我想如果客户需要覆盖集成部分升级其 Documentum）。
至于 ADO.NET 服务和“用于访问业务对象的 Web 服务框架” - 您能否向我提供更多信息 - 我是否能够使用这些选项执行上述任务（管理文件夹、文档、元数据、搜索）？我可以使用 ADO.NET 服务访问文档内容还是仅使用文档元数据？
最后一个问题是我错过了其他选择吗？ 您是否认为这里最好的选择是使用 DFC 在 java 中编写自定义 Web 服务，然后将 .NET 应用程序与该 Web 服务集成？ （类似于“访问业务对象的Web服务框架”的方法 - 但我不确定这个框架是否可以提供我需要的所有功能）
I need to implement integration of a custom .NET application with Documentum 5.3. .NET application should provide functionality of managing folders, documents, metadata and search in configured Documentum 5.3.
I've found the following integration options are available in Documentum 5.3:
- Documentum ADO.NET Services
- Documentum Foundation Classes (including PIA & Web Services support)
- WDK
I guess for .NET application preferable variant is DFC PIA. But here - http://forums.contology.com/index.php?showtopic=23639 - guys are discussing that DFC PIA is deprecated and will not be supported soon (I understand that it is sufficient for 5.3 - but I guess it'll require to overwrite the integration part if customer upgrades its Documentum).
As for ADO.NET Services and "Web Services Framework for accessing Business Objects" - could you please provide more information to me - will I be able to perform tasks above (manage folders, documents, metadata, search) using these options? Could I access document content using ADO.NET Services or only document metadata?
The final question is are there any other options I missed?
And do you think the best option here is writing custom web service in java using DFC and then integrate .NET application with this web service? (approach similar to "Web Services Framework for accessing Business Objects" - but I'm not sure if this framework could provide all the abilities I need)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
听起来您对网络服务没有特别的要求。我读过与您有关 DFC“最终”被弃用的相同内容，但它仍然活跃且活跃。
Documentum Foundation Services (DFS) 是每个人都应该使用的“新”公共 Web 服务 API，从 6.5 开始（实际上是 6.0，但他们做了很多更改）。它基于 SOAP，其中一些功能也可通过 REST 获得。
基本上，DFS 是 DFC 之上的一层，因此实际上它是在运行 DFC。 DFS 的优点是您不必被迫使用 Java 或 .Net，会话管理得到简化，并且有一些操作更易于执行，但如果您坚持使用 5.3 那么我认为没有理由不使用 DFC 。
您仍然可以对 6.5 或 6.6 存储库使用 DFC。谁知道当7.0、8.0、9.0出来时EMC会说什么，但我的猜测是他们很难完全摆脱DFC。即使他们这样做了，如果您的客户等到从 5.3 开始升级，他们将面临的升级挑战将比仅仅担心迁移到 DFS 更大。
仅供参考，两年前我将 5.3 DFC 应用程序转换为 DFS，从那时起我就一直愉快地使用 DFS。转换只是痛苦的，因为我当时对应用程序或 DFS 本身一无所知，但老实说，这比困难更乏味。
It doesn't sound like you have a requirement for web services specifically. I've read the same stuff that you have about DFC getting deprecated "eventually" but it is still alive and kicking.
Documentum Foundation Services (DFS) is the "new" public web services API that everyone is supposed to use, starting with 6.5 (6.0 really, but they made a LOT of changes). It is SOAP-based with some of the functionality also available via REST.
Basically, DFS is a layer on top of DFC, so really it is DFC running anyway. The advantages of DFS are that you are not forced to use Java or .Net, session management is simplified, and that there are some operations that are simpler to perform, but if you are stuck with 5.3 then I see no reason not to use DFC.
You can still use DFC against a 6.5 or 6.6 repository. Who knows what EMC will say when 7.0, 8.0, 9.0 come out, but my guess is it will be difficult for them to completely get rid of the DFC. Even if they do, the upgrade challenges your client will face if they wait until that happens to move from 5.3 will be bigger than just worrying about moving to DFS.
Just FYI, I converted a 5.3 DFC application to DFS two years ago, and have been happily using DFS ever since. The conversion was only painful because I did not know anything about the application or DFS itself at the time, but honestly it was more tedious than difficult.
Wingspan (http://wingspan) 公司有一个 Documentum 集成服务器，支持 5.3（以及一直到 4.2.x 的所有其他版本）。它称为 DocWay 服务器，具有 Web 服务 API 和单独的内容传输设施。它在某些方面与 DFS 类似，但比 DFS 早很多年，并且自 2002 年起就已经发布。
我在那里工作，我确信推销产品会因为堆栈溢出而受到皱眉，所以我就将其留在那里。如果您想了解更多信息，请PM我或直接联系Wingspan。
如果没有这一点，我会按照您的建议进行操作，“使用 DFC 在 java 中编写一个自定义 Web 服务，然后将 .NET 应用程序与此 Web 服务集成”。
但是，如果您需要公开大量 DFC，那将是一个艰难的过程攀爬。您可以访问 Content Server 5.3 SP6 吗？我相信这包括 DFS，它更容易从 .NET 访问。
The company Wingspan (http://wingspan) has an integration server for Documentum that supports 5.3 (and everything else going all the way back to 4.2.x). It's called the DocWay Server and it has a Web Service API and separate Content Transfer facility. It's similar in some ways to DFS, but predates it by many years and has been shipping since 2002.
I work there, and I'm sure pitching products is frowned upon on stack overflow, so I'll just leave it there. PM me or contact Wingspan directly if you want more information.
Absent that, I would do just what you suggested and "[write a] custom web service in java using DFC and then integrate .NET application with this web service"
If you need to expose a lot of the DFC though, that's a tough hill to climb. Do you have access to 5.3 SP6 of Content Server? I believe that includes DFS which is more accessible from .NET.