Ben There, Done That

Rich,
     Thanks for the comment, it is great to hear that you have both of them working together successfully and are pleased with your implementation and how you were able to marry the two products together.  The "good points that people should be careful of" have less to do with one product or the other and more to do with proper planning and implementation of their chosen environment.

1.  Make sure the interface is something your end users will adopt.  This company didn't look to that, and the users rejected the interface
2.  Make sure the system performs as required.  A requirement was to integrated with Outlook, and this never happened.
3. Plan for growth.  The implemented SharePoint as the front end, all the documents ended up being stored there, it mushroomed and now they have a SharePoint mess as well b/c they didn't plan for the growth, or even plan the solution well so Documentum could do the heavy lifting, or the SharePoint environment could be properly planned for scaling.

Those are the big three for me.  Again, I'm a big SharePoint guy, I would say just do it all in SharePoint.  Your company has been SharePoint and Documentum working great together to meet your needs.  But, it sounds like you followed all three of the principles I outlined above.  You thought about your end users, and chose SharePoint to increase user adoption.  You must have delivered on requirements or people would have screamed.  You planned for the growth and found Documentum to be better for your heavy lifting.

As a result of all of those, you have a very succesfully SharePoint and Documentum platform running and aren't experiencing any of the nightmare with either SharePoint or Documentum that were outlined in the article above.

Thanks again for the post and I hope that clarifies what I took from that article a little better and clears up any confusion about the points I was trying to make.

Ben, I read the article several times, what are the good points that people should be careful of? I didn't find any. We're in the middle of a very large MOSS and Documentum project and the two products have been working great together. Documentum is doing all the heavy lifting, and Sharepoint gives the consistent look and feel our end users are familiar with. This article has too little detail on why the project went wrong. Incompetent or untrained IT folks, employee turnover, etc... who knows for sure, the article too me appears to be a sales hype as to why someone should contact Alan Pelz-Sharpe to help with their CMS solution