Composer Reference Projects

Composer comes with the DocumentumCoreProject reference project included.  This project is a non-buildable project that describes most of the core “dm_” objects so that you can include, extend and manipulate them in your Composer project.  However, if you want to include or extend non-core objects, such as a TaskSpace application (dmc_taskspace), you need to include the reference project that defines those object types in your Composer project.

EMC/Documentum supplies the following 10 reference project for you to use in Composer:

  • WebPublisher
  • Page Builder
  • Documentum Compliance Manager (DCM)
  • TCM (includes artifacts for TaskSpace, Forms Builder, Process Builder, & Business Activity Monitor)
  • Digital Asset Manager (DAM)
  • Documentum Reporting Services (DRS)
  • Retention Policy Services (RPS)
  • Documentum Federated Records
  • CTS Transformation
  • CTS Rich Media Transformation

All of these reference projects are available for download from the Download Center from their respective application links (e.g., the WebPublisher reference project can be found in the WebPublisher download folder).

Once you have downloaded the reference projects, install them into separate folders in your Composer workspace so they can easily be added as references to your Composer projects.  From the New Project wizard in Composer, include the appropriate reference project as a reference, or you can include them later from your project’s Properties -> Java Build Path -> Projects screen.

One interesting caveat that I have discovered for the RPS reference project that may hold true for others as well: just because you include a project doesn’t mean you can import or install those types of objects.  For example, with RPS project referenced, Composer does not magically add the ability to import retention policies into your project.  You can import them as sysobjects (if you can find them) and Composer does seem to be smart enough to define them as dmc_rps_policy objects.  However, you cannot install them into another repository.  Creating portable retention policies is a long-standing feature request for RPS.  Therefore, I find little use for the RPS reference project.  Maybe it’s just me….  Are there other equally dysfunctional reference projects?

There is a very helpful page about reference projects on the EDN at  You can also read about them in the Documentum Composer User Guide -> Managing Projects -> Documentum Supplied Reference Projects


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 Composer Reference Projects

  1. Thanks for the great article. I just stumbled into the RPS problem. Wish I had seen this article sooner.

    I hope that EMC do away with the reference projects. It seems really clunky, as does the tight binding to Eclipse – bootstrap Eclipse to run an Ant build? WTF?! I was really hoping for a bunch of documented core Composer classes wrapped by a thin Ant/Maven layer and by a thin Eclipse layer. That way we could check into SVN, Hudson would detect the change and grab the source code then build a DAR and deploy the DAR to a Maven repository and/or Documentum repository.



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: