Documentum’s out of box Webtop allows for its administrative users to manage groups, and the users that belong to each group, while within Webtop’s user management section. As a default, the groups and its users are presented in a datagrid along with individual descriptions, if provided. Sometimes, however, clients will find it useful to expose additional user information on the datagrid (such as an email) to accompany the name and description columns already implemented. Such a task is possible with a few tweaks to the GroupList component and its dependent files.
Archive for the 'Tech Tip' Category
Tags: Webtop, WDK, Administration, Column Preference, Customization, Development
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.
Four of us are out at the Alfresco Developer conference in San Diego this week. Look for a write-up on DevCon later this week. This post will present a number of thoughts gleaned from multiple discussions over drinks with other Alfresco partners regarding collaboration and ECM.
Tags: D6, Documentum, Documentum Upgrade, OpenMigrate
When EMC revealed Documentum 6 a few years ago, they made a subtle—yet important—change to the way Documentum would store dates and times in the database. While most clients would never even notice the change, some of us would. In particular, when it becomes necessary to access the underlying database tables, like OpenMigrate can when preserving modification dates, confusion can be the order of the day.
Continue reading ‘Documentum 5 vs. 6, Databases and Dates: Does Anybody Really Know What Time It Is?’
Documentum lifecycles are time consuming functions since they require a call out to the Java Method Server to perform their actions. We recently ran into an issue on a project where the lifecycle actions were taking an inordinate amount of time. We did some investigation along with our client and discovered an OS setting in Linux that was impacting performance, DEVRANDOM. Continue reading ‘Lifecycle Performance: Could DEVRANDOM be causing a problem?’
Typically Documentum users will have heard Ed speak at Momentum or EMC World in the past in regards to system performance and Documentum. For this post, we are going to take a different approach and talk about Documentum Search APPLICATION Tuning for system and USER performance. All of the concepts relate to our Alfresco and SharePoint clients as well as the Documentum users. The experience is based on a recent client but we will try to bring in best practices from other clients as well. Continue reading ‘Documentum Search Application Performance Tuning – Part 1′
Special Note: Anyone that is planning an upgrade from Documentum 5.3 to 6.5 should look closely at this note as some types of upgrades (clone or in-place) could result in content that was retrievable from 5.3 not being available in 6.5.
This post was developed based on recent work for a major pharmaceutical client. The client, on Documentum 5.3, was developing a consumer interface application leveraging Lucene. As we mentioned in a previous post, the client chose Lucene over FAST based on benchmarking results for over 150,000 documents.
For the application, the client was leveraging OpenMigrate with DFC 6.5 to retrieve content and metadata for nearly 1,000,000 documents from their 5.3 docbase to be indexed in Lucene. Per the product release notes, using DFC 6.5 to access a 5.3 repository is a supported configuration. An issue was identified when around 5,000 documents failed to migrate. In reviewing the error logs from OpenMigrate, the DFC call IDfSession.getObject() to retrieve documents from the repository resulted in errors. After reviewing the stack trace, it was apparent that the error was being thrown from within the DFC code. The team was surprised by the error since the documents were able to be retrieved without a problem using client applications working with a 5.3 DFC, such as Webtop and Samson. The DFC error messages that were encountered are shown below:
For many clients, one of our first projects is a Documentum Health Check. This is typically a 2-3 day project where one of our technical architects will visit onsite to review all the different components of the Documentum environment. We encourage this type of project as it allows us to be more pro-active with identifying possible issues rather than re-active when issues surface. This post will describe the typical activities of a Documentum Health Check engagement as well as typical findings to give readers an idea of things to monitor in their own environments.
I recently had the opportunity to work with a defense company who was looking to migrate data out of FileNet using our OpenMigrate solution. Compared to the other FileNet migrations we’ve done, at first this seemed much simpler, considering they only had 3 doc classes that they wanted to migrate, but pretty soon, we realized we had some challenges ahead of us.
Challenge One: A Very, Very Old AIX Server
First we found that the FileNet server they were using was a very old AIX machine, and that the latest version of Java supported on that version of AIX was Java 1.1. OpenMigrate (OM), on the other hand, had only been run on Java 1.4 and Java 1.5. It would have been a stretch, but we could have tried updating OM to work with Java 1.3, but anything lower than that would probably not have worked since OM is built on the Spring framework. What we decided to do instead was take OpenMigrate’s FileNet logic and execute the steps manually. Continue reading ‘FileNet Migration Findings’
To give an update on the Active Wizard Enhancements we were working on last month, we recently finished up all development and testing of the Flex-based checkin/checkout interface against Documentum. We delivered to our client this week, but I wanted to share some of the challenges we ran into, specifically related to running an application using Flash.