DRX Is Now Open Source

I am pleased to announce that the Documentum Repository eXplorer (DRX) is now an open source project hosted at SourceForge.  Flatirons Solutions has generously released this internal R&D project to the open source Documentum community.  The project is managed by Scott Roth and Brian Yasaki, the tool’s original developers.

DRX is a Java/Swing application that utilizes DQL and the DFC to explore a variety of Documentum repository configurations and customizations.  The executable contains everything necessary to run DRX — no additional Java libraries are necessary to install.  The executable even contains its own JVM and a copy of the DFC to increase its portability.  The application can easily be run from a memory stick!   Users not running the application on Windows can execute the non-Swing  interface using Ant and still generate the same output.

To download the application, visit the project’s home page at Source Forge:  http://www.sourceforge.net/projects/drxproj.  Users interested in adding to or extending the reporting mechanisms of DRX can join the SourceForge project.

Current DRX modules include:

  • 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.
  • Maintenance Jobs – include the most recent maintenance job reports:  State of the Docbase, Consistency Checker, Update  Stats, DMCleam 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.
  • 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.
  • Registered Tables – describe all database tables registered with the Content Server and produce SQL scripts to recreate the tables if necessary.
  • 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 –report on physical records management configurations
  • Records Manager – describe records management configurations
  • Web Publisher – report all Web Publisher configurations and templates.
Advertisements

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 Is Now Open Source

  1. Michal Boron says:

    Hi Scott,
    thanks for this post and for open sourcing the DRX tool.
    I tried to download the source code from sourceforge SVN repository, but it seems to be empty. Also the “browse code” link on sourceforge does not show any files in SVN.
    Is it really so or did I missed something?
    Thanks for your reply.
    Michal

    Like

    • Scott says:

      Michal, I just downloaded both archive file — DRX2.0.zip (executable) and DRX_GUI.zip (the source code) — and both seem to be fine. The SVN repo has not been populated yet. We will be getting that and a customized project homepage setup ASAP. Sorry for any confusion this caused you.

      Like

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 )

Twitter picture

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

Facebook photo

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

Google+ photo

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

Connecting to %s

%d bloggers like this: