Earlier this week, we wrote about the Documentum Platform Roadmap. We, along with many other attendees, mistook the first day’s session as the overall roadmap rather than just the Documentum Platform. This post will describe the overall Roadmap and present our thoughts.
Retrieving data from a Documentum Repository using DQL is a common and robust process with Documentum. With addition of the xPlore search engine, there are some challenges that experienced DQL users may find unique. This post will discuss our experience with DQL and xPlore.
Many experienced Documentum customers have attempted to leverage the Google appliance as an alternative to Documentum Search or as part of an Enterprise Search effort. One of our clients presented their experience at our user group meeting. This post will discuss their findings. Continue reading
Back in July, we wrote a lessons learned post regarding upgrading from Documentum 6.5 to Documentum 6.7. We have a client that recently completed, by himself, a Documentum upgrade from 6.5 SP3 to 6.7 SP1. While TSG often assists clients in the Documentum upgrade process, some clients are very capable of performing upgrades on their own if they chose a simple approach. This post will share some of the client’s thoughts on the upgrade and how the combination of TSG products as well as good knowledge of his environment made the upgrade relatively painless. The only issue the client had was due to some bad documentation in regards to the xPlore upgrade that will be shared as well.
TSG recently assisted a client with upgrading their Documentum 6.5 environment to 6.7. Products included Content Server, xPlore, Business Process Manager (BPM), Content Transformation Services (ADTS, AVTS, MTS), DA, Webtop, Records Manager, Retention Policy Services (RPS), Archive Services for Reports (ASR), and TaskSpace. The client also runs TSG’s High Performance Interface (HPI) and OpenContent products. Continue reading
I was talking to a client last week that was struggling with their Documentum system performance. This client had recently brought in Documentum Consulting, and having been unsuccessful in improving performance, was concerned that there might be nothing left to do. This post will focus on innovative things TSG has done for clients in regards to Documentum performance that are probably outside of the norm of typical database/server tuning particularly focused on Search, Document Retrieval and Inbox viewing.
We’re working with a large Pharmaceutical company to install Documentum xPlore as a replacement for FAST. We’ve just finished the QA environment deployment, and we’re planning for the Production deployment in mid-April. For this post, we are going to discuss the cutover strategy as well as some lessons learned from the project.
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.” Continue reading
I was at a Documentum client this week that is reviewing their ECM strategy as part of planning for 2012 and 2013. Given a somewhat difficult relationship with EMC due to a contentious software audit, the client wanted to review alternatives and consider a Documentum migration to a new ECM system as an alternative to the Documentum upgrade. For this post I will share some of the discussion of Documentum Alternatives as well as thoughts on ECM disruptors, Alfresco and SharePoint.
Attended another roadmap session focused on next 18 months. This post will try to summarize and present TSG thoughts.