Yet Another Documentum Export Tool

How about we start the new year with another Documentum export tool, DeepExport?  This a very simple Java/DFC-based tool that logs into a Documentum repository and exports the content of any folder (recursively) to the local hard drive, preserving the folder structure.  The log file snippet below demonstrates how the folder structure is preserved.  Note that metadata is NOT exported; this is a content-only tool.  If you need to export content and metadata, check out the QuikDIE export tool.

To run the DeepExport tool, use the export.bat file. You will need to adjust the and in the /config folder to be appropriate for your environment.

The DeepExport tool expects to read a file in its root directory with the following information: name of the Documentum repository
docbase.user= name of the Documentum user to logon to the repository
docbase.password= password for the Documentum user
export.source= the cabinet/folder to export.  For example, /Temp, or /News/2014/. the local directory to receive the export.  For example, c:/temp/export.

In addition to the properties file, you can supply DeepExport with two additional command line parameters:

-version will export all versions of all documents found and avoid file name collisions in the target folder.
-help will display a brief screen

DeepExport creates a time-stamped log file to track all of the files it exports. For example:

Documentum Deep Export 2015-01-02 17:08:18
(C) 2014 MSRoth -

Base export path = c:/temp/export
Found 55 folders to export
Found 6457 documents to export
  Not a document -- skipping test_query (0801e4538000f520)
  Exporting TargetSetup.Result --> c:\temp\export\Temp/TargetSetup.Result.txt (0901e45380000220)
  Exporting sysobjectContent.pdf --> c:\temp\export\Temp/sysobjectContent.pdf.pdf (0901e4538000597b)
  Exporting Copy of TargetSetup.Result --> c:\temp\export\Temp/Copy of TargetSetup.Result.txt (0901e45380005a54)
  Exporting Copy (2) of TargetSetup.Result --> c:\temp\export\Temp/Copy (2) of TargetSetup.Result.txt (0901e45380005a55)
  Exporting Walmart.txt --> c:\temp\export\Temp/Walmart.txt.txt (0901e4538000dd17)
  Exporting Walmart.rtf --> c:\temp\export\Temp/Walmart.rtf.rtf (0901e4538000e9aa)
  Exporting HP-DeskJet-MFP-5100_userguide.docx --> c:\temp\export\Temp/HP-DeskJet-MFP-5100_userguide.docx.docx (0901e4538002f990)
  Exporting --> c:\temp\export\Temp/ (0901e4538002fd65)
  Exporting --> c:\temp\export\Temp/ (0901e4538002fd66)
  Exporting Folder: /Temp/Jobs
  Exporting Folder: /Temp/Jobs/dm_DataDictionaryPublisher
  Exporting 11/14/2014 3:28:12 PM dm_DataDictionaryPublisher	--> c:\temp\export\Temp\Jobs\dm_DataDictionaryPublisher/11-14-2014 3_28_12 PM dm_DataDictionaryPublisher.txt	(0901e4538002b50c)
  Exporting 11/14/2014 3:44:37 PM dm_DataDictionaryPublisher	--> c:\temp\export\Temp\Jobs\dm_DataDictionaryPublisher/11-14-2014 3_44_37 PM dm_DataDictionaryPublisher.txt	(0901e4538002b564)
  Exporting 11/14/2014 4:12:38 PM dm_DataDictionaryPublisher	--> c:\temp\export\Temp\Jobs\dm_DataDictionaryPublisher/11-14-2014 4_12_38 PM dm_DataDictionaryPublisher.txt	(0901e4538002b5b2)

It seems to work well enough for me; I’ve had occasion to use it a few times. Let me know what you think.


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.

6 Responses to Yet Another Documentum Export Tool

  1. Cool, thanks, I’ll check it out.


  2. Piyush Raanjan says:

    This works well, thanks. But how to export all version?


  3. Pingback: Links to All of My Source Code | dm_misc: Miscellaneous Documentum Information

  4. I know you can’t troubleshoot my system but just curious if you might know why I am getting “ERROR: com.qumas.doccompliance.xploresearch.DmDocumentFTCustomData___PROXY cannot be cast to com.documentum.fc.client.IDfDocument” when I try to run this tool?


    • Scott says:

      Hmmm… you’re right, I can’t troubleshoot for you but maybe I can give you some hints. Are there TBOs on this custom object type that could be interfering with it? The custom type doesn’t seem to be an IDfDocument, or more importantly, a DfDocument. I suspect the custom type implements the IDfDocument interface but is not actually a DfDocument.


Leave a Reply

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

You are commenting using your 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: