• 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 Business Continuity – A Cached Content Approach

You are here: Home / Documentum / Documentum Business Continuity – A Cached Content Approach

July 8, 2011

One of the more successful applications we see long-term Documentum customers implement successfully is a business continuity solution based on caching approved content to a separate “read-only” repositories.  This post will discuss the reasons for business continuity solutions and integration options for Documentum as well as business continuity war-stories from selective clients.

Defining Business Continuity

In regards to business continuity for Documentum or other document management systems, the key component needs to focus on answering the question:

“What documents (ex: manufacturing, operating…) would the business need access to, should the primary content management system become unavailable?”

Developing a cost effective business continuity solution requires an understanding the parts of the business that can have some flexibility in regards to system availability.  Typically clients will say that, given delays in typical approval cycles, document authoring and approval are not critical and could be postponed in the case of a short-term system outage. 

For most of our customers, 24 hour access can be described as:

“I need access to the latest approved documents for view and printing at all times.  I need to make sure that obsolete documents are not available when no longer current”. 

Business Continuity is more than just a mirroring

Unfortunately, Business Continuity is an easy buzzword for a hardware or software sales representative to use in regards to selling their solution.  Typically paired with “How much is it worth to insure that your business isn’t interrupted for X hours” to justify the price tag for a variety of hardware and software products.    Most of these solutions involve some type of mirroring of data between redundant servers or storage products.  Keep in mind that we are defining mirroring somewhat different than replication in that it is at the drive/disk level.  Replication is more at the application/server software level.

In helping to evaluate business continuity solutions, we wanted to share some of our war stories from different Documentum clients for reference where mirroring storage didn’t address the business continuity solution.  For ECM customers, how does your current business continuity solution address these issues?

  1. Unix Admin Error – A Unix Admin (not TSG) accidentally deleted a directory that included multiple storage areas for Documentum.  The business continuity solution real-time “mirrored” the deletion onto the redundant storage area, deleting that one as well.  The Client needed over 5 days to completely recover.
  2. Water – Another client had their server room in the basement in a newly updated building.  During a rain storm, water leaked down an A/C vent onto the server shorting out some key components.  The client used their staging server for parts during the first downtime.  Unfortunately, the client didn’t or forgot to either move the server or fix the leak.  During the next rainstorm, you guessed it, server was drenched again.  Replacements parts were ordered for both staging and production with the system down waiting for the parts.
  3. Database – Too many clients have suffered from a database issue – table space, corruption… that has left them down working on a fix.  It is important to remember that mirroring solutions will not address this fairly common ECM continuity issue as the bad data will be mirrored to the other system.
  4. Server Access – Through either power outages/surges, weather or data connectivity (we have seen router configuration issues), sometimes access to the server can be interrupted either at the data center or from the end-user location.  Mirrored solutions that rely on connectivity between the servers or are in the same data center would not be protected from this interruption.
  5. Upgrades and Migrations – Typically, upgrades will require Documentum to be down for some time while the server is upgraded or content moved to a new instance.   This relates to the mirrored storage solution as well.

Caching for Consumers – a smarter approach for business continuity

Based on the above scenarios, many customers have chosen not to have a completely redundant infrastructure for Documentum authors but have instead developed a solution focused on caching content outside of Documentum for consumers of approved documents.  This is almost a light version of a fully replicated solution.  The solution involves pushing the content out to a read-only “cache” once the document is approved.  It also involves updating content (attribute changes, obsolete…) when approved documents are changed.  The approach has several benefits for business continuity including:

  • Redundant, but cheap, servers – the cache is typically some type of index/database as well as the PDF rendition of the content.  The index database doesn’t have to be as full-featured as Documentum with clients typically choosing either MySQL or Lucene and Solr (for full-text searching as well as attributes).
  • Location – servers can be placed outside of the data center where it best benefits the user.  This would include potentially placing servers overseas to reduce the data transmission as well as the risk of the transmission being interrupted.
  • Multiple Servers – read-only servers can be placed around the network to provide for redundancy.

 

Other benefits for this solution include:

  • Performance – with consumers performing expensive searches outside of Documentum, authors will not find their performance of everyday activities impeded by consumer searches.  With a smaller, more nimble infrastructure on the cache, we have seen performance dramatically improve for consumer search and retrieval.
  • License costs – depending on licensing arrangements, groups or external parties that just need access to approved documents won’t require licenses to Documentum just like they wouldn’t for approved documents published to the web.
  • Upgrade and Integration – With multiple clients, we see difficulties in performing a Documentum upgrade due to the amount of other systems that rely on Documentum for content.  By integrating other systems to the cache repository rather than Documentum, the upgrade is greatly simplified.
  • Content Control – typical solutions will only cache PDF renditions rather than original documents offering both better control of the authoring documents as well as reducing costs of distributing authoring applications for view only consumers.

Caching More than Documentum – Enterprise Search versus a  “Push” approach

 Once clients have established a successful cache, many have started to look at other ECM tools that can leverage the cache for approved content such as SharePoint.  This is a substantially different approach than typical system integration or enterprise search efforts where a “crawler” looks to index content from different repositories and the search would attempt to retrieve the content from the repositories.  For this approach, content is “harvested” or synched from different systems into one main retrieval system.  The benefits of the approach for enterprise search initiatives include:

  • Security – Enterprise search can be very difficult to coordinate security across multiple secured systems and repositories.  A “push” approach allows the pushing application to only push out those documents that can be seen by a wider audience when the content is ready.
  • Performance – Systems owners can be rightly concerned that a “crawler” will be accessing their content throughout the day.  The push allows the system owners to schedule publish times with reduced overhead in regards to performance.
  • Business Continuity – as mentioned throughout, with content in multiple locations, systems can be down or unavailable but content is still available.

TSG Product Offerings

Given the number of clients that have implemented these types of solutions, TSG offers several open source products that can give clients a jump start to this type of solution.  All have been validated as part of our life-sciences practice.

  • OpenMigrate – Provides for the real-time push/synch between Documentum and the external cache.  A small footprint component can be configured to monitor (not crawl) the Docbase looking for new approved content to push to the cache or to delete content from the cache if obsolete.  OpenMigrate can be configured for either a light database or other cached repository.  OpenMigrate has had considerable success with a Lucene Solr approach cached repository for both attribute and full-text search requirements.  See a comparison of OpenMigrate to Site Caching Services in this post.
  • High Performance Interface (HPI) – Provides for a configurable and efficient search and retrieval interface (whitepaper search comparison available here).   Based on OpenContent, our web services interface, HPI can execute searches against either Documentum or a variety of cached repositories.
  • OpenOverlay – Provides for real-time watermarking of the documents (based on open source iText solution) with date/time and potentially user information.

If you have any additional thoughts or other approaches, please add your comments below.

Filed Under: Documentum, OpenContent Management Suite, OpenMigrate, OpenOverlay

Reader Interactions

Comments

  1. Paras Jethwani says

    July 12, 2011 at 9:46 pm

    How would you provide ‘access control’ and also auditing in the ‘read-only’ cache?

    usually, even when clients only need read-only access to the latest approved version of a document they still want to enfoce some access control.

    regards

    Reply
    • TSG Dave says

      July 13, 2011 at 6:45 am

      Paras,

      Great question. Typical clients will control access to the application and implement a light, group-based security based on document types. Nothing like the ACL security in Documentum. For some types of documents (we see SOPs alot), there isn’t a real need for security as, if you have ever seen the old manual way, are typically printed into binders and scattered around the organization.

      In regards to audit trail – we haven’t seen the need for this type of content. Nothing says that you couldn’t add in an audit table to show who is looking at what content.

      Dave

      Reply

Trackbacks

  1. Documentum Migrations – Interview with OpenMigrate Product Manager « TSG Blog says:
    September 21, 2011 at 7:16 am

    […] source goals with Alfresco.   For Documentum, OpenMigrate is either also used for bulk import, replacement for site caching services to support business continuity or as part of a Documentum Upgrade.  (see D6.5+ upgrade guide […]

    Reply
  2. Documentum Top Tips for 2012 « TSG Blog says:
    December 1, 2011 at 2:50 pm

    […] interface has consistently been a big win for Documentum users.  See our related posts on how to make a consumer successful with Documentum, specifically for search and […]

    Reply
  3. Documentum, Mobile and the Cloud for Third Party and Remote Approval « TSG Blog says:
    February 28, 2012 at 2:00 pm

    […] when connectivity is restored.  We have found this approach very successful with our search and retrieval cache approach and wanted to leverage the same approach […]

    Reply
  4. Documentum Performance – Search, Retrieval and Inbox « TSG Blog says:
    May 9, 2012 at 12:27 pm

    […] Business Continuity – Documentum can be down (for an upgrade or other reasons) and search can continue.  See related post on Documentum Business Continuity. […]

    Reply
  5. Documentum, Mobile and IMAP – A standard and open source approach for email archiving and mobile access « TSG Blog says:
    May 31, 2012 at 2:03 pm

    […] IMAP folders could be created for individuals or projects/cases.  Our approach is to use OpenMigrate to copy or mirror emails from an IMAP folder into a Documentum folder similar to how we cache content from Documentum to a file store for business continuity. […]

    Reply
  6. Documentum – Replacing External SharePoint Sites with a Simple Cached Approach « TSG Blog says:
    September 14, 2012 at 10:10 am

    […] we have discussed previously, many clients leverage either Web Caching Services or our OpenMigrate product to push approved documents out of Documentum.  Many of our clients deploy this type of […]

    Reply
  7. Documentum Maintenance – 21% and rising…. « TSG Blog says:
    October 3, 2012 at 2:34 pm

    […] Documentum for consumers using either Site Caching Services or other tools like our OpenMigrate.  Lots of posts on this topic discuss the benefits besides reduction of licensing and maintenance including business […]

    Reply
  8. Predictions for EMC Documentum in 2013 « TSG Blog says:
    December 10, 2012 at 2:17 pm

    […] these costs by retiring products they are not using, caching consumers out of Documentum (Click HERE), and retiring products that can be replaced with open source offerings such as OpenAnnotate and […]

    Reply
  9. Alfresco for Life Sciences – Response to Client Questions « TSG Blog says:
    January 23, 2013 at 9:31 am

    […] is the idea of a “published” consumer interface.  You can read more about it in this post.  For our pharmaceutical or nuclear clients, this approach provides a way to have access to […]

    Reply
  10. Documentum to Alfresco Migration – SaaS and the Cloud | TSG Blog says:
    February 26, 2013 at 1:05 pm

    […] outside the firewall means re-wiring these other systems.  A couple of innovative customers are leveraging a consumer cache for business continuity and wiring their other systems to this published vault rather than […]

    Reply
  11. Documentum, SharePoint, Alfresco – Document Control for Life Sciences | TSG Blog says:
    April 22, 2013 at 8:54 am

    […] Documentum Business Continuity – A Cached Content Approch […]

    Reply
  12. Documentum – EMC World 2013 – Day 1 – Life Sciences D2 Solutions | TSG Blog says:
    May 7, 2013 at 4:57 pm

    […] the subset of SOPs that they need (I tend to think a simple offline search and retrieval app like HPI would work better for this use […]

    Reply
  13. Documentum Webtop Migration – xCP, D2 and other thoughts | TSG Blog says:
    July 15, 2013 at 12:39 pm

    […] (typically 70%).   We often see clients move even farther away from Webtop and Documentum to a business continuity approach to publish content out of Documentum to make sure more neutral when updating Webtop.  Recently we […]

    Reply
  14. Documentum Cross-Repository Searching – an integrated open source approach | TSG Blog says:
    January 15, 2014 at 3:04 pm

    […] – We have seen this many times with our complete Caching model, but typically performance of Webtop and Documentum in general can be tied back to expensive […]

    Reply
  15. Top 5 Differences between Records Management and Document Management – Technology Services Group says:
    September 22, 2016 at 2:32 pm

    […] Large View Only Population – Document Management applications can quickly get complex allowing for authors to create documents, relationships between documents, initiate workflows, etc. However, like an RM application, many of the users just require read-only access to the content stored by the application. To reduce training requirements, system load, as well as user licensing, our DM clients have found lots of success in implementing a read-only application that provides quick and easy access to content. Learn more about the benefits for this approach by reading our blog post. […]

    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 – EMC World/Momentum 2013 – TSG Recap
  • Documentum Client Briefing – Final Agenda – June 7th – University of Chicago Gleacher Center in Chicago
  • Alfresco Consulting – Documentum Disruptor #2
  • Third Annual TSG Client Briefing – June 3rd – 2010
  • Documentum Consulting and Open Source
  • Documentum Open Source Software
  • TSG Open Source Product Plans
  • Increase in downloads of Documentum Open Source from TSG
  • Migrating to Alfresco – Reducing Risk, Stress and Cost with a Rolling Migration
  • Redaction for AWS, Alfresco, Documentum and Hadoop – Bulk Redaction upon Ingestion or Migration

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