The Keynote is always the real beginning of the Momentum conference. Rohit Ghai is the new leader of the renamed Enterprise Content Division (formerly Information Intelligence Group) that includes Documentum. This post will share our thoughts about the keynote.
Whenever we give a demo of OpenAnnotate, clients always ask, “What happens when multiple users need to review a document at the same time?” OpenAnnotate has always supported having multiple users annotating a document at the same time, but a recent client has added functionality which broadcasts “live” the annotations and comments that users are making. This makes the review process in OpenAnnotate more collaborative. This post will outline some things to look for when evaluating your options for annotating/reviewing documents in your ECM repository.
Many of our clients have end of year deadlines for projects. One of our newest clients contacted us with an unprecedented challenge – could we upgrade them from 32-bit Documentum 6.5 SP1 to 64-bit Documentum 7.0 Patch 12 by early December given availability of certain funds. This post will present the project and some best practices in regards to the upgrade. Continue reading
One of the better roadmap presentations was given by Aaron J. Aubrecht and Patrick Walsh. Some great useful and candid information. Continue reading
Starting in Documentum Content Server 6.6, using the eSignature mechanism uses iText rather than PDF Fusion to create the electronic signature page. Documentum made this move to iText in order to be able to support creating eSignatures when the content server was running on a Unix/Linux environment, which was previously unsupported. Using the eSignature mechanism still requires a TCS (Trusted Content Services) license from EMC.
As many Documentum customers know, the end of 2012 saw the initial official release of Documentum D7, something that was announced back at EMC World in May. We have recently been evaluating the release to determine what’s new, what’s changed, and what the potential impacts could be for our clients as they plan for the future. We will be posting to the blog over the next weeks as we proceed through our evaluations and test upgrade paths so be sure to stay tuned, but we wanted to share some initial thoughts as well.
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
With Documentum 6.5 SP3 going out of support this year (August 31, 2012), we’re running several Documentum upgrade projects for clients this quarter. Unlike in the past where upgrades promised fantastic new functionality, this round of upgrades is trending more towards maintaining supported configurations and upgrading to new hardware. In addition, rather than simply upgrading the OS, companies are virtualizing servers and rolling out 64-bit hardware wherever possible. Continue reading
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.