DRX 2.3 Released

Brian Y. and I are pleased to announce the release of DRX (Documentum Repository eXplorer) version 2.3.

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 Java 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 thumb drive, or move from one computer to another.

Here are the highlighting and new features in version 2.3:

  • Added additional stats for WF (terminated and halted)
  • Separated SCS from WebPub reporting (still in same module)
  • Added additional product/feature checks in the EnvInfo Module
  • Distribute config/dfc.keystore file to avoid endless hangs in certain conditions
  • Tweaked queries for custom object types to eliminate stock BOF classes
  • Corrected bug in role query
  • Corrected bug in TCS detection
  • Add “top user” queries to users and groups module
  • Expanded role reporting to match group reporting
  • General code cleanup and standardization
  • Added drx.exclude_types property to config/dfc.properties. These entries will be object types excluded from the Custom Types and Hierarchy report.
  • DRX no longer overwrites the config/dfc.properties file (required for drx.exclude_types).
  • Added Webtop Presets module (user must copy dfc.globalregisty.* entries from the Content Server dfc.properties to the DRX confg/dfc.properties file.

DRX v2.3 is available for download here:  http://sourceforge.net/projects/drxproj/files/

If you haven’t tried DRX yet, I encourage you to download it and give it a try. For a brief explanation of DRX, see here .  And, as always, if you have any feedback or feature requests, please log them here.  Enjoy.

Qit 3.1 – New Documentum Open Source Tool

If you aren’t using Qit yet, you should be.  Qit is an awesome alternative to repoInt from Belgian company Qtree. Qit provides developers and admins easy access to the tools they need to manage and troubleshoot Documentum repositories.  For example:

  • Tree navigation of cabinets/folders as well as administrative nodes (e.g., users, ACLs, jobs),
  • DQL editor,
  • API editor,
  • Properties editor for any object selected in results panel, and
  • Search.

I have found it to be a solid and indispensable tool.  Check out the screen shot!

Qit-UI

In addition, Qit is  extendable with custom actions.  Just for fun, I wrote an extension to produce an SHA-256 hash for a selected object’s content (see image below).  It was super simple.  Code here.

QitSHA

Qit is built on the Eclipse framework and is available for Windows, Linux, and Mac.  Check it out, www.qtree.be/qit!

DRX v2.2 Released

Brian Y. and I are pleased to announce the release of DRX (Documentum Repository eXplorer) version 2.2.  We made this release only a “point” update (i.e., from 2.1.1 –> 2.2), even though it contains some exciting new features — not the least of which is its ability to run against D7 repositories.  This release of DRX is compatible with Documentum 5.3 – 7.0 Content Servers.

Here is a quick list of additions, enhancements, and features included in this release of DRX:

  • recompiled to work with D7 repositories;
  • updated JRE to 1.6_43;
  • expanded the list of Documentum housekeeping reports included in jobs report;
  • include list of users who have superuser or admin privileges in user report;
  • added list of top 20 ACLs according to the number of objects to which they are applied. (This helps gauge ACL coverage.);
  • include JMS, BOCS, and ACS in configuration report;
  • added count of inbox items to user report;
  • general improvements, corrections, and tweaks.

DRX has enjoyed over 1,300 downloads in the past year.  If you haven’t tried DRX yet, I encourage you to download it and give it a try. For a brief explanation of DRX, see here .  And, as always, if you have any feedback or feature requests, please log them here.  Enjoy.

CMIS 1.1 Open Comment Period

OASIS has recently recommended CMIS 1.1 be advanced as a Candidate OASIS Standard, and has thus opened a 60-day public comment period (22 February 2013 – 23 April 2013).  OASIS is soliciting input from potential users, developers and others for the sake of improving the interoperability and quality of this specification.  If you are a CMIS user or have any interest in CMIS and the benefits it offers, now is the time to make your voice heard.

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.

%d bloggers like this: