Deleting/Disabling TBOs

This post expands upon a note at the end of the TBOs – Part 2 post.

You can temporarily disable a TBO by simply renaming the dmc_module folder in /System/Modules/TBO that contains the TBO.  For example, if your TBO is named my_custom_type, it is likely installed in /System/Modules/TBO/my_custom_type.  If you rename the dmc_module folder  my_custom_type to my_custom_type-disabled, the Content Server can no longer associate your TBO with the my_custom_type object type; you have effectively disabled your TBO.  To reinstate the TBO, simply rename the dmc_module folder back to my_custom_type.

To permanently delete at TBO, delete the dmc_module folder in /System/Modules/TBO and all of its contents.  Remember to clear the Documentum cache (/Documentum/cache) as well as the app server and Java Method Server caches.

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 Deleting/Disabling TBOs

  1. John says:

    Note that if you do this, and if you installed it via a docapp, the next time the docapp is opened you’ll get a lot of barking about missing objects from the application. It’s perfectly fine, just something to know about.

    I’m not sure how this affects composer projects.

    Like

    • Scott says:

      True enough. A deletion like this can really upset your system. I probably should have caveated this post with a warning that you should really only do this in a DEV environment. You should really never need to do this at all except under dire circumstances. The exception to this is during a massive content import or migration. I have found that TBOs can really mess up content migrations and mass imports depending upon how the migration/import mechanism works and the nature of the migration/import. In cases where the TBO really disrupts the migration/import, I have temporarily disabled it (as described here) and included any validation or metadata inheritance that the TBO enforced in the migration application.

      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: