Documentum Digital Asset Manager [EOL] Reviews

Technical EDMS for construction (for different types of construction) plans of geological assets.

Mainly for studies (design office) and construction (plans for mechanical components), e.g., responsible for documentation.

• A very powerful rules engine
• A D2 Client, which is very powerful and stable. 
• The content server is able to accept a lot of users with a huge amount of documents and reviews on it.
  

The main work to do concerns cloud integration because our customers want to go to the cloud. 

They need a new way to do their pricing and licensing.

I've been working on the architecture of big Documentum installations, and I've experienced pros and cons of the whole stack in different places, starting from the Content Server, going through mid pieces like workflow engine or CAS storage, and finally opening the infinite box of web applications it has. But technical support guys have been always there, trying to help me when I've been stuck at any point.

It's a product with a swarm of different applications, each one answers the needs of a specific part of the business. They collaborate one with each other relatively smoothly.

I would say scalability is a hot point to improve.

No issues. In my opinion, out of the box it is a pretty stable product.

One special point of difficulty was when I wanted to install a two-cluster-nodes Content Server and wanted to use a REST API to connect third-party applications with the cluster. 

The problem was that we wanted to secure the whole thing with token sessions, and we found that their persistence is not shared between different content servers in a cluster, leading to potential problems. For example, when a process client starts a session with Content Server "A", it receives a session token that is only known by Content Server "A". If, by any chance, the next query of this client goes to Content Server "B", his token session will not be recognized and he'll receive a challenge login screen.

I worked around this issue creating a REST endpoint that managed and delivered cluster tokens instead of using those from the Content Server.

Wonderful people, excellent professionals. Actually, I've got a lot of friends there, as I worked one and a half years with them in Brentford, UK. I've been opening service requests that have been pretty well resolved. Keep doing it that way, guys.

I did not have a previous solution in production, but I've used other solutions in PoCs to further my understanding of them.

Setting up even an all-in-one machine requires some technical expertise, e.g. Linux or Windows operating system. But EMC's documentation team has put a lot of effort into its literature, and the documentation and installation guides are simply superb.

It's absolutely not a product for small companies, but for middle sized or large companies it is not expensive. You pay for what you get, and there are a lot of benefits.

On two occasions, customers asked me to evaluate different solutions: Alfresco or FileNet.

I've been using Documentum products for seven years, starting from version 6.5 SP1.

In my experience, the starter product of Documentum is xCP 2.x. It allows you to create amazing Documentum-based applications with just a few clicks on its workbench, no need to write a single line of code.

It's an excellent solution, I totally recommend this product if you need a content management solution. But make sure your revenue will cover the investment in licenses.