• 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

Debugging Documentum ADTS Transformation Failures

You are here: Home / Documentum / Debugging Documentum ADTS Transformation Failures

July 27, 2017

A client recently encountered an issue with their Documentum 6.7 environment where PDF renditions for certain document types were not being created. The client’s environment was leveraging Advanced Document Transformation Services (ADTS) 6.7, 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 were tasked with figuring out exactly why these renditions were failing.

Our investigation of this issue began with viewing the ADTS instance’s log files located on the ADTS server at %ADTS HOME%/CTS/logs. Specifically, we looked at the CTS_log.txt. Unfortunately, yet all too common, we only encountered a generic set of errors that didn’t really shed light on exactly why documents were failing to rendition. The errors simply stated that the renditions were, indeed, failing.

ADTS error-log-1

After further testing, we were able to uncover that the documents that were believed to be failing to rendition were actually producing renditions after all. By viewing the cache folder that ADTS utilizes – located at %ADTS HOME%/CTS/cache and defined during installation of ADTS – we were able to find temporary PDF files whose content matched the files that Documentum was attempting to rendition.

ADTS temp-folder

So that posed the question: if the renditions were being successfully created, why weren’t they appearing in Documentum? And after a myriad of tests, we finally uncovered the root cause of the problem: timing.

By referring to the Adlib logs, a set of log files that are located outside of the CTS/logs location mentioned above within the %Adlib Express Directory%/logs directory, we confirmed that the documents were indeed being successfully renditioned. No errors were being thrown and the logs even indicated a success message:ADTS detail-log-2

We then referenced the AdvancedPDF_log.txt located back in the %ADTS HOME%/CTS/logs directory. This log is produced by ADTS and contains logs that pertain to ADTS’s communication with Adlib. Here, we were able to find an error that indicated a timeout was occurring during the renditioning process. This seemed odd. Why would ADTS be timing out when everything points to the rendition actually being successfully created? Our answer was found by comparing the timestamp of the Adlib logs with the timeout error thrown in the AdvancedPDF_log.txt.

ADTS timeout

It appeared that ADTS was timing out before Adlib completed its entire renditioning process. Notice how after the bolded success message in the Adlib logs above, the job continues to process before closing the ticket. Clearly, the renditioning process handled by Adlib includes more than just creating the rendition itself; it is also responsible for creating and setting any bookmarks that may be present in the word document (which, as it turned out, the template that was being used for the documents that were failing in our client’s environment, contained 80+ bookmarks), as well as any post processing that occurs. So it seems that while the PDF rendition was being created within the allotted timeout parameter set in ADTS, the entire renditioning process was taking longer than that and was therefore timing out and not completing the upload of the document’s rendition from the cached folder to the docbase.

We were able to alleviate this issue by increasing the timeout parameter located in %ADTS Install Home%/CTS/config/advancedpdf/advancedpdf.xml. (View the official Documentum ADTS Installation Guide for more information on configuring this timeout).

ADTS debugging can be a very cumbersome process given the lack of support and outdated engine (Adlib is no longer what’s used by Documentum in 7.x and beyond). Please refer to our previous blog for more options in regards to reliable transformation options.

Filed Under: Documentum, DTS, Tech Tip

Reader Interactions

Comments

  1. Tim Wikander says

    July 31, 2017 at 9:04 am

    It’s great to hear the customer was able to find assistance in this instance, however long term support will be challenging for them if they chose to remain on unsupported technology. Business disruptions can occur from any number of things, some are not preventable. What is preventable is ensuring your organization meets regulatory compliance and taking steps to reduce risk to your business, by using current and supported software. This is where Adlib Software comes in and we are ready to help Documentum customers restore support ability for their Advanced Rendering needs with Adlib PDF Enterprise and Documentum Connector. Please contact our Customer Success team (success@adlibsoftware.com) to learn about your options to move to PDF Enterprise today. Our team is ready to assist you with your transition to Adlib!

    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 Transformation Services (DTS) – Alternative Approaches with Adobe LiveCycle and OpenOffice
  • Documentum 6.7 and ADTS Extended Support Ending on April 30th, 2018
  • Documentum – End of Life for ADTS Dec 31, 2016 – Remove the risk of unreliable content transformation services
  • Documentum – Understanding DQL’s Performance Limitation with xPlore
  • Customize User Management Columns in Webtop's Administration Node
  • Documentum 6.5 to 6.7 Upgrade Lessons Learned
  • Debugging Documentum Java Method Server (JMS) Code in Eclipse
  • Documentum 5 vs. 6, Databases and Dates: Does Anybody Really Know What Time It Is?
  • Lifecycle Performance: Could DEVRANDOM be causing a problem?
  • Documentum Search Application Performance Tuning – Part 1

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