One of the better roadmap presentations was given by Aaron J. Aubrecht and Patrick Walsh. Some great useful and candid information. Continue reading ‘Documentum – EMC World 2013 – Momentum – Day 1 – EMC Documentum 7.0 Roadmap’
Archive for the 'Content Server' Category
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.
Continue reading ‘Documentum Upgrade to 6.7 – a simple approach’
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 ‘Documentum 6.5 to 6.7 Upgrade Lessons Learned’
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 ‘Documentum 6.7 Upgrades and Hardware Changes’
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.
One of the big challenges with working with Documentum is debugging code that is deployed to the Content Server’s Java Method Server (JMS). Deploying code updates to the JMS can be tedious because it the JMS is typically on a remote server for developers, and it usually takes a long time to restart when code changes are deployed. The Java Method Server is also shared by all repositories on the content server, so continuously restarting the server for debugging can impact other repositories. Logging for the JMS can also be tricky to configure, and log files can be difficult to locate.
This article will describe how to set up remote debugging in Eclipse for code that runs on the Documentum Java Method Server.