Documentum Health Check

Hi all,

I am interested in learning best practices and approaches people are taking in monitoring the health of documentum and underlying RDBMS and file storage system.

Is there anything built into documentum that could be used?

One approach I have is to execute a DQL statement (select * from dm_server_config) and if everything is fine then show the documentum system as available on the monitoring page. Any negatives on taking this approach?

Thanks!

Find more posts tagged with

Comments

msroth

There are a number of administrative jobs that come with Documentum to monitor the health of a Docbase. In particular you might want to look at the Consitency Checker job and the State of the Docbase Report. There are others that monitor database health and file space. Check the Admin Guide for more info. Note that most of these jobs are off by default. This document might also be of use: https://community.emc.com/docs/DOC-2495

christineadcock

Hi.

The jobs are the best way to monitor the health of the system. It might also be useful to set up a script file that executes the most common functions your users perform. Then you can periodically run the script to see if performance is still acceptable.

There is some good information out there about how best to use the Documentum jobs. I know a FlatIrons consultant wrote a white paper on the jobs. If you have some development time, you might want to think of a dashboard-like web page. The company I work for created a simple OpenDashboard that can be downloaded and installed on a web server. It does some basic monitoring. I know there is also another company that makes a full recovery/self-healing kind of product for Documentum but the name escapes me at the moment. We had a client looking at it.

Generally, you should keep an eye on the consistency checker job and if you are running Webtop you should also monitor your jvm environment. I've used remote monitoring with jconsole to do that. If you have a custom java web app, you might want to look at jmx enabling it so you can monitor it better with jconsole. Also, don't forget to clean your filestores and then delete the orphaned files! A lot of people clean, but then forget to delete.

Just a couple of suggestions. I hope they help.

Christine