Documentum Renewal: Architecting Content Applications


Of all my posts in this series, this is the one that is probably the least needed.  I say this because it looks like EMC is some of this now.  It does need to be said though, just so EMC know that we still care, and in case I am guessing wrong.  The themes for the Architecting of Content Applications is closely related to the Application Separation topic and in many ways, is the complement to the Focus on the Core edition.

I’m going to stay away from some specific feature requests for applications.  I would want to do complete run-downs on any app before I did that.  I want to be a little more strategic in my advice.

As always, please feel free to add/comment.

Continue reading

EMC World 2009: Documentum Performance, Scalability, and Sizing, Part 1


This is the first of two sessions by Ed Bueche. His sessions are must-attends.  His sessions last year, part one and part two, are useful references, but as always, this year’s information takes precedence. Some information that Ed is presenting is available in the Architecture session notes.

Continue reading

Sailing with EMC’s Magellan


I’ve been debating on whether to talk about Magellan or SharePoint next. It was a heck of a decision, but I quickly resolved it when I decided to do both. I pulled out my notes, did a little research, and remembered the disclaimer. This is unreleased software. Things may change before the Magellan Beta, much less the final release.

Shall we set sail…

Continue reading

DQL versus SQL


James has often compared DQL and SQL, assigning the security weaknesses of one to the other. While there may be valid concerns for some ECM query languages, DQL is actually fairly secure from this type of attack. Don’t get me wrong, it isn’t foolproof, but it isn’t an apples to apples comparison. Let’s compare and look. Be sure to add comments to question or add.

Continue reading

Inciting Insight or Panic?


Normally when I read a post by James McGovern, I understand that he is trying to get under people’s skins in order to provoke a response. Some people respond to this by attempting to give the type of information that James is looking for in a post of their own. Others view it as a form of harassment and try their best to ignore it, though James just looks on that as a form of encouragement. Both reactions are perfectly fine.

I, and pretty much every blogger, are not compensated for writing our blogs, much less for responding to James. It is optional. When I blog, I do so as me, myself, and I. Not as an employee of any company or organization.

Continue reading