• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer
TSB Alfresco Cobrand White tagline

Technology Services Group

  • Home
  • Products
    • Alfresco Enterprise Viewer
    • OpenContent Search
    • OpenContent Case
    • OpenContent Forms
    • OpenMigrate
    • OpenContent Web Services
    • OpenCapture
    • OpenOverlay
  • Solutions
    • Alfresco Content Accelerator for Claims Management
      • Claims Demo Series
    • Alfresco Content Accelerator for Policy & Procedure Management
      • Compliance Demo Series
    • OpenContent Accounts Payable
    • OpenContent Contract Management
    • OpenContent Batch Records
    • OpenContent Government
    • OpenContent Corporate Forms
    • OpenContent Construction Management
    • OpenContent Digital Archive
    • OpenContent Human Resources
    • OpenContent Patient Records
  • Platforms
    • Alfresco Consulting
      • Alfresco Case Study – Canadian Museum of Human Rights
      • Alfresco Case Study – New York Philharmonic
      • Alfresco Case Study – New York Property Insurance Underwriting Association
      • Alfresco Case Study – American Society for Clinical Pathology
      • Alfresco Case Study – American Association of Insurance Services
      • Alfresco Case Study – United Cerebral Palsy
    • HBase
    • DynamoDB
    • OpenText & Documentum Consulting
      • Upgrades – A Well Documented Approach
      • Life Science Solutions
        • Life Sciences Project Sampling
    • Veeva Consulting
    • Ephesoft
    • Workshare
  • Case Studies
    • White Papers
    • 11 Billion Document Migration
    • Learning Zone
    • Digital Asset Collection – Canadian Museum of Human Rights
    • Digital Archive and Retrieval – ASCP
    • Digital Archives – New York Philharmonic
    • Insurance Claim Processing – New York Property Insurance
    • Policy Forms Management with Machine Learning – AAIS
    • Liferay and Alfresco Portal – United Cerebral Palsy of Greater Chicago
  • About
    • Contact Us
  • Blog

Documentum – End of Life for ADTS Dec 31, 2016 – Remove the risk of unreliable content transformation services

You are here: Home / Adlib / Documentum – End of Life for ADTS Dec 31, 2016 – Remove the risk of unreliable content transformation services

November 10, 2016

Update: Read Adlib’s thoughts on the upcoming EOL of ADTS here.

Documentum has announced the end of life for support for the Advanced Document Transformation Services as Dec 31, 2016.  One of the little known changes between the Documentum 6.7 and 7.x versions was that Documentum changed the underlying transformation engine.  Formerly based on Adlib (an industry leader in transformation), the new product, named Content Transformation Services (CTS), is based on Aspose.  This post will discuss our client experience with CTS, highlight some of the differences between representative documents transformed with CTS and the old ADTS as well as present thoughts on how to remove the risk of both Documentum and CTS moving forward.

Documentum Document Transformations – A short history

One of the strengths of Documentum has always been the ability to store a rendition of the document.  Typically, most clients have relied on PDF as a means to preserve the original document in an editable format with PDF being used for viewing and annotations.  In building our own High Performance Interface (HPI)  for Documentum, we heavily rely on PDF renditions as a way to quickly show the content of the document within a browser window without having to load a bloated file format (example Microsoft Word).

Early on in Documentum’s history, the transformation was produced by a product called “AutoRender”.  As an initial basic approach, AutoRender ran on a separate Windows PC, would launch the file in Word (or Excel or PowerPoint) and initiate a “print to PDF” that would store the file back in Documentum as a rendition.  Plagued with reliability issues, I distinctly remember John Newton fielding questions from the Documentum community at the first Momentum (in Miami) as we all complained about the stability of the PC’s that ran AutoRender.

As Documentum grew and matured, Documentum partnered with Adlib, an advanced rendering company, to power Advanced Document Transformation Services.  With the announcement of 7.x, some readers might have noticed that a new engine was picked.  In working with the new tool, our clients have noticed:

  • ADTS 6.7 will not work with a 7.x repository
  • The installation is not straightforward – we had to engage with EMC support to obtain a patch just to get it to install, and even then, it is not a simple install
  • Certain files are renditioned differently (more detail below).

In our discussions, it seems apparent that Documentum changed the renditioning service to use Aspose as its renditioning engine; not to provide a better service but to save the money they would have had to pay without reducing the price of document transformation.  As we have been saying about Documentum for quite some time and would continue to state with the OpenText purchase, the profit motive around Documentum products continues to drive many of the technical decisions.  The decision to change renditioning engines seems to be another example.

File Rendition Differences

The below image shows an example of what a client has seen being transformed in the new 7.0 version of CTS vs what they previously had in 6.7 ADTS. See if you can guess which version was from Adlib vs what was produced by CTS 7.0 (hint, it is the one that isn’t cropping information, adding random lines or changing borders). From our experience so far, it seems like CTS takes many liberties with font sizing and spacing of tables that are prone to cutting off information and otherwise changing the actual content of the document in unexpected ways.

adlib-compare

Derisking transformation services – Adlib Transformation Services for Documentum

From our discussions with Adlib, Documentum recognized some of the issues with CTS and had been in discussions to again offer Adlib as the engine behind CTS for Documentum 7.x customers.  With the purchase of Documentum by OpenText, these discussions have been put on hold.  For clients looking to remove the risk of Documentum, we would recommend considering adding Adlib as a separate product rather than CTS.  Some advantages to Adlib over CTS include:

  • Shared service—Deploy as a shared service across multiple enterprise applications, lines of business, departments or geographic locations to ensure rendering consistency across the enterprise.
  • Massive scalability—Scale easily for added capacity to meet growing conversion and transformation job volumes with maximum uptime and zero job loss.
  • Centralized management console—Monitor, report and troubleshoot via web-based management console to ensure enterprise-wide rendering demands are met.
  • High availability—Maintain high reliability and availability with intelligent redundancy to ensure no single point of failure and maximize uptime.
  • Performance oriented load balancing—Ensure high utilization of Adlib resources for optimal performance.
  • Job management—Route jobs intelligently to appropriate resources based on resource availability, job priority, and proximity to content. Job monitoring ensures successful job completion.
  • Compliance-ready—Ensure all corporate information is ICH compliant and delivered with consistent quality across the organization.
  • Rules Creation & Processing—Gives organizations the ability to configure processing of documents based on metadata.

For some of our clients, we have even considered building out Adlib as a cloud renditioning services to remove the cost of the separate server.

Summary

With ADTS end of life coming up on December 31, 2016, clients upgrading to 7.x or looking for alternative approaches and taking some of the risk out of the new CTS should consider adding Adlib transformation services as a standalone product to their Documentum environments.

Filed Under: Adlib, D6.7, D7, Documentum, DTS, OpenContent Management Suite

Reader Interactions

Comments

  1. Marko Sillanpaa says

    December 15, 2016 at 11:34 am

    Thanks for invoking flashbacks. My first project in ECM was to develop a better AutoRender product. Our Render Server needed to ensure fidelity of the documents. It was a challenge that AutoRender had before the turn of the century. It would seem the old saying is true, those that don’t learn from the past will repeat it.

    I like the screen shot you show but it seems the change is minimal. Have you seen issues where the font changes which line on the page a word appears? That was our challenge. We had to ensure that if the Word document had ten words on a line that those same ten words were on a line in the PDF as it could have caused concerns in the legal department.

    Reply
  2. Ben Allen says

    December 15, 2016 at 11:41 am

    We have seen another use case recently of the 7.1 version of ADTS that the Word document had 39 pages, but the PDF that was generated is 40 pages (shocker: this is a big problem). This was due to line breaking and font changes that materially changed the output PDF.

    Reply

Trackbacks

  1. Debugging Documentum ADTS Transformation Failures says:
    July 27, 2017 at 8:00 am

    […] which utilizes Adlib as its underlying renditioning engine for rendering PDFs. As we discussed in a previous blog post, Documentum had announced end of life for support for ADTS at the end of 2016, and thus we at TSG […]

    Reply

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Primary Sidebar

Search

Related Posts

  • Documentum 6.5 to 6.7 Upgrade Lessons Learned
  • Documentum 6.7 and ADTS Extended Support Ending on April 30th, 2018
  • Documentum Content Server 6.7 – Primary Support Ending April 30, 2015 – What should clients do?
  • Enterprise Content Management Predictions – 2015
  • Documentum – Momentum EMC World 2014 Recap – Some bunts, hits as well as some swings
  • Documentum – EMC World/Momentum 2013 – TSG Recap
  • Documentum – EMC World 2013 Momentum – Day 1 – Rick Devenuti Keynote
  • Documentum Upgrades – Handling eSignatures in Documentum 6.6+
  • Documentum D7 – Initial Thoughts
  • Miami-Dade County and OpenContent win Sustainability Award

Recent Posts

  • Alfresco Content Accelerator and Alfresco Enterprise Viewer – Improving User Collaboration Efficiency
  • Alfresco Content Accelerator – Document Notification Distribution Lists
  • Alfresco Webinar – Productivity Anywhere: How modern claim and policy document processing can help the new work-from-home normal succeed
  • Alfresco – Viewing Annotations on Versions
  • Alfresco Content Accelerator – Collaboration Enhancements
stacks-of-paper

11 BILLION DOCUMENT
BENCHMARK
OVERVIEW

Learn how TSG was able to leverage DynamoDB, S3, ElasticSearch & AWS to successfully migrate 11 Billion documents.

Download White Paper

Footer

Search

Contact

22 West Washington St
5th Floor
Chicago, IL 60602

inquiry@tsgrp.com

312.372.7777

Copyright © 2023 · Technology Services Group, Inc. · Log in

This website uses cookies to improve your experience. Please accept this site's cookies, but you can opt-out if you wish. Privacy Policy ACCEPT | Cookie settings
Privacy & Cookies Policy

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Non-necessary
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
SAVE & ACCEPT