Apr 27, 2017 | by Antje Dwehus | 2 Comments

Despite the ongoing discussion about the prospects of new web technologies, progressive clients or even the need of an unmitigated new user experience, many enterprises are still using the “good old Documentum Webtop” quite contentedly. In general, Webtop applications integrate smoothly with other systems that have spawned over time such as Jive, Jira, CRM and others.

Nevertheless, let’s be honest. There have been some flaws and one of them has always been the content transfer mechanism UCF which can be hard to maintain especially in complex network settings and which causes an annoying dependency on the client’s Java Runtime Environment. With modern browser vendors reducing plugin support and the decision of Oracle to deprecate the Java browser plugin in Java 9, a new content transfer mechanism was long overdue.

read more

Apr 19, 2017 | by Mark Deckert | 0 Comments

Today we are back with a new issue of our blogseries on the development of our product migration-center 4. In this post I would like to focus on the “Analyze” part and show you again some screenshots of our new migration-center client.

As I have described in the first article of this series, the new user interface emphasizes our step-by-step migration approach of Analyze, Organize, Transform and Validate, and finally Import:

read more

Apr 12, 2017 | by Maik Uhlenberg | 0 Comments

train connector, waggon

Every document management system’s core is a database.

I do not know if that is true for 100% of all the systems out there but it is definitely true for all DMS I have worked with. Beside, as a content migration consultant, I can tell that nearly every company has data (somewhere) inside a database.
Very often, I face the case that we have to migrate a legacy ECM system (based on a database) for which our product migration-center does not have an out-of-the-box-connector (see our target platforms). Such an OOTB connector is often the best solution for feature rich ECM systems because native connectors are typically able to support the features of an ECM system as best as possible. This applies in particular to features like relations, version, virtual documents, comments, renditions, annotations etc.

read more