EMC BOF White Paper

EMC published a BOF white paper last month that contains some informative explanations and tips for implementing TBOs, SBOs, Aspects, and Modules.  For example, this paper contents that you can create a TBO for dm_document as long as you do not implement the IDfDynamicInheritance interface (though it is still not recommended).  That’s news to me; I may have to try it.  Read through the paper for other interesting and helpful tidbits of information about BOF.

It the link doesn’t work for some reason, EMC whitepapers can be accessed from PowerLink:  Support -> Technical Documentation and Advisories -> White Papers -> All White Papers.


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 EMC BOF White Paper

  1. Thanks for this. I will read it thoroughly since I’m trying to optimize my BOF development process now and this sounds like just what I was looking for. Still, while I’m here maybe you can help me. I have a question that you may have already solved:

    I can’t seem to figure out how to organize my Documentum projects in composer so that it does not require me to install my SBOs to every content server. If I understand correctly, only the global repository needs the SBOs and they will only ever be deployed from the global repository.

    However, If I create a project that contains a TBO and that TBO requires the use of an SBO then I must reference the project that contains the SBO and in doing so commit to installing both projects into every content repository that needs the application.

    Any suggestions?


    • Scott says:

      Thanks for the comment. I feel your pain and have been exactly where you are with your SBO/TBO deployment situation. Unfortunately, I can’t say that I have solved it. In fact, I sort of punted on the whole situation and just installed the TBOs and SBO everywhere — including the Global Registry — just for good measure. If you find a solution, please let me know. I am sure others would be interested as well.


      • This is exactly what my solution has been. Just install the SBOs to every docbase, though from everything I’ve read they should only ever need to be deployed to the global repository. I wish I could find some answer to this. I’m trying to structure my projects so I can teach others here and I can hardly teach them if I don’t know how and why it works myself. It is also very inefficient since I now must deploy my changes to multiple locations. I’ve tried the forums but got no response, I’ll try again and maybe I’ll also try powerlink.


      • Scott says:

        Those interested in following Mark’s discussion on EDN, here is the link: https://community.emc.com/thread/144975.


  2. I was just about to post that. Thanks, it has been solved. See the thread for more information.


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 )

Google+ photo

You are commenting using your Google+ 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 )


Connecting to %s

%d bloggers like this: