This was going to be part of my post, Documentum and LDAP, Time to Grow Up, but I decided to pull it out as a short post in the Tips section. Partly because I haven’t posted a Tip in a while, and partly because I think this deserves a little more attention.
The issue? A Federation and multiple LDAP definitions. The solution, simple, but poorly documented.
[Edit: See Comments for details on the “Why” of the edits.]
I’ve spent the last several weeks working on LDAP issues. Some have been simple, others, not so much. Suffice it to say, if you have Documentum 6.0 sp1, get the hot fixes for LDAP. They are readily available from EMC. Most of these are rolled up into D6.5 sp1.
Those issues aren’t isn’t what I want to talk about today. What I want to talk about is the advent of large systems and the need for applications, like Documentum, to accommodate the broader reality of some of today’s environments.
Before I go much deeper, I want to state that some vendors handle this worse than EMC, and some handle it better. I’m not going to name names. I do know at least one major player that does a much worse job, and I am pretty sure I can accurately pick one that handles it better.
ALL vendors need to understand this problem.
Word of Pie 