DRX v2.1 Released

Brian Yasaki and I released DRX (Documentum Reporitory eXplorer) v2.1 this past week on SourceForge.  http://drxproj.sourceforge.net.  This is the first update to the software since it was released to the open source community a year ago, and we are really pleased with it.  The update includes a few bug fixes, a few tweaks and enhancements, a new module for the Audit Trail, and the ability to cancel the tool mid-run.  I encourage you to give it a try.

For those of you unfamiliar with DRX, here is a brief introduction:

DRX is a powerful exploration, auditing, and documentation tool that allows Documentum administrators and developers to quickly document vital information about their repositories and environments. DRX provides a simple UI to facilitate logging into the Documentum repository, configuring and running specific reporting modules, and viewing the resultant reports. DRX reports are generated in HTML for easy viewing and XML for more complex processing.

DRX is distributed as an EXE file that contains all of the code, requisite libraries, JVM and the DFC required to run the program. Its compact distribution and simple installation (simply unzip it!) make it easy to run from a memory stick or move from one computer to another.

We have found DRX to be very helpful for:

  • Documenting the final delivery of a system;
  • Creating As-Built documentation for a system;
  • Comparing different environments (e.g., DEV and QA, QA and PROD);
  • Exploring a new or unknown environment;
  • Auditing a Documentum installation;
  • Creating an inventory of installed components, document types, users, etc.

DRX v2.1 offers the following reporting modules:

  • Environment – report on the Connection Broker, server configuration, product licensing, the OS and Java.
  • Configuration – report on server, repository, client, full-text server, LDAP and session configuration objects, as well as server configuration files.
  • Custom Types and Hierarchy – describe all custom types and the entire object hierarchy. The report does not detail objects with names beginning with: ‘dm_’, ‘d2_’, ‘c6_’, or ‘bpm_’. However, these objects are included in the hierarchy report.
  • Maintenance Jobs – include the most recent maintenance job reports: State of the Docbase, Consistency Checker, Update Stats, DMClean, and DMFilescan.
  • ACLs – describe all regular ACLs, Template ACLs, and Public ACLs, including extended permissions.
  • Cabinets and Folders – depict the entire cabinet and folder hierarchy of the repository including folder sizes and object counts. This report can take a very long time to run if your cabinet – folder structure is deep.
  • Users and Groups – report all active, inactive and locked users as well as all groups, roles and aliases. All users, groups and roles include explicit membership listings.
  • Lifecycles – describe all document lifecycles.
  • Jobs and Methods – describe all Documentum and custom jobs, methods and procedures.
  • Workflows – describe all workflow templates, instances, and activities.
  • File System – report on Documentum’s use of the file system including storage locations, directory sizes, and file counts. This report must be run from the
    Content Server to report on the actual use of the file system.
  • Registered Tables – describe all database tables registered with the Content Server and produce SQL scripts to recreate the tables if necessary. The report
    excludes registered tables with names like: ‘dm_%’, ‘cya_%’, ‘wcm_%’, ‘%_r’, ‘%_s’, and ‘adm_turbo_size’.
  • Document Templates – list and describe all document templates found in the /Templates cabinet.
  • TaskSpace – report on all TaskSpace applications and components found in the repository.
  • DocApps and DARs – report all DocApps and DARs installed in the repository.
  • BOF – describe all TBOs, SBOs and Aspects found in the repository.
  • Retention Policy Services – describe all retention policies installed in the repository.
  • Physical Records Manager – reports on physical records management configuration, and lists label templates.
  • Records Manager – describes record management configuration and lists cabinets and folders under formal records management.
  • Web Publisher – describe the WebPub configuration including templates, channels, and site caching sources/targets.
  • Audit Trail – report the size of the audit trail, the number of entries grouped by event type, and the events that are registered for auditing.

Check it out and let us know what you think.  See a module that is missing?  Join the DRX Project Team.


About Scott
I have been implementing Documentum solutions since 1997. In 2005, I published a book about developing Documentum solutions for the Documentum Desktop Client (ISBN 0595339689). In 2010, I began this blog as a record of interesting and (hopefully) helpful bits of information related to Documentum, and as a creative outlet.

2 Responses to DRX v2.1 Released

  1. Doesn’t seem to be reading the dfc.properties file that I placed in the config directory. I’m assuming that is where it goes? Also, can it be a link to another location. Also, about does not pop up a dialog.


    • Scott says:

      Mark, thanks for the feedback. DRX creates its own dfc.properties file in the DRX/config directory based upon the Docbroker host name you enter in the UI. It is overwritten everytime the app runs. As for the About box…it isn’t working for me either. I’ll take a look.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: