• 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 Webtop 5.3 running on Documentum Content Server 6.x

You are here: Home / Documentum / D2 / Documentum Webtop 5.3 running on Documentum Content Server 6.x

March 15, 2012

We stumbled across a pretty vague reference in the cross-product dependency guide for Documentum 6.7 SP1 (on page 245) for Webtop (emphasis ours)

“Note: Documentum Collaborative Services 5.3 DAR is installed with Content Server 6.7 SP1 repository so Webtop 5.3 & 5.3 SPx will work with Content Server 6.7 SP1.   If Documentum Collaborative Services (formerly Documentum Collaborative Edition) 6.7 SP1 DAR is installed with Content Server 6.7 SP1 repository, Webtop 6.7 SP1 is required.”

As we have mentioned on this site before, the core underlying docbase architecture (APIs, structure…) of Documentum hasn’t changed between D5 and D6.  Based on client queries, we attempted to hook up a Webtop 5.3 SP6 instance to a D6.7 content server and were successful (including full-text search).  This post will explain why this might be a temporary alternative for clients looking to gradually move away from their Webtop 5.3 environment.

Why Documentum Webtop 5.3 on a Documentum Content Server 6.x environment?

Back in the 2006-2008 years, many of our customers developed extensive customizations within the Webtop 5.3 SP6 environment only to be disappointed by Webtop 6 as their customizations proved to not be easily transferable.  Many Documentum users have chosen to stay on their Webtop 5.3 platform, and potentially pay for extended maintenance and support, despite the arrival of D6.x versions of Webtop and Content Server.  Reasons for staying on Webtop 5.3 could include:

  1. Difficulty of moving existing customizations to a new version of Webtop – For Clients that spent the hours to develop and test/validate extensive customizations, the desire to port these to a new interface was often deemed a rewrite and very expensive and probably the top reason for staying on Webtop 5.3.
  2. With the multiple announcements ( EMC World 2010, EMC World 2011) that Webtop would be replaced with something new, clients wanted to “wait it out” to see if they could move to the newer product and skip a release rather than upgrade to a Webtop 6 version that might be not supported shortly in the future.
  3. Neither xCP or D2 provide any significant differences as an alternative to Webtop (see Tony’s reviews – search – contributor – for more detail).  Clients that purchased Webtop licenses also had concerns about being able to move those licenses to other products.

With the above being said, clients should consider upgrading their back-end content server while keeping their Webtop 5.3 for the following reasons:

  • Support – When things go badly wrong in Documentum environments, critical support items are not at the Webtop layer but more often at the content server/database level.  Webtop support is needed during the development and testing stages and typically doesn’t cause critical business errors in production.
  • Stack Upgrade – All of the underlying components of a Documentum 5.3 content server can also be upgraded (hardware, database, operating system).  Getting the right combination on the content server will drive requirements for the underlying components as well.  For clients that might have gone Sun or HP Unix varieties, the ability to leverage VMware with Linux combined with a newer version of the database and operating systems will provide a better performing and supportable infrastructure.
  • New Functionality – A new content server architecture allows clients to take advantage of back-end improvements in regards to reliability and performance.  One obvious advantage is the ability to leverage xPlore (and Lucene) as opposed to the old FAST architecture.
  • Avoiding the “Big Bang” – For clients that want to eventually upgrade to the latest version of WDK apps, this approach could be a good stop gap for getting the Content Server back to a supported stack first, then upgrading WDK application(s).  This would avoid the “big bang” risk issues with WDK apps and Content Server upgrade at the same time

Summary

The ability to move Webtop 5.3 users to a D6.7 backend might be something users want to consider to provide for better back-end support, infrastructure and performance, while gradually moving away from their Webtop customizations.

Filed Under: D2, D6, D6.5, D6.7, Documentum, News, Webtop, xCP, xPlore

Reader Interactions

Trackbacks

  1. Documentum Upgrade to 6.7 – a simple approach « TSG Blog says:
    November 29, 2012 at 12:54 pm

    […] allowed him to simplify the upgrade process.  We recommended, in another post, that some clients consider running their older applications on an upgraded backend to get support without the hassles of the front-end […]

    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 Upgrade to 6.7 – a simple approach
  • EMC World 2012 – May 23rd – What’s Next? ECM Documentum Family Roadmap – Aaron Aubrecht
  • Documentum – EMC World 2015 – Overall ECD Product Vision and Roadmap – Ahson Ahmad and Mark Arbour
  • Documentum Content Server 6.7 – Primary Support Ending April 30, 2015 – What should clients do?
  • Documentum Search – How to get around the user request of “I just want a search like Google”
  • Documentum and Momentum EMC World 2010 Recap
  • Documentum – EMC World 2015 – Meet the Executives
  • Documentum and Alfresco – What are some of the bigger differences?
  • Enterprise Content Management Predictions – 2015
  • Documentum – Momentum EMC World 2014 Recap – Some bunts, hits as well as some swings

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