Two weeks ago I read interesting blogpost about Documentum future. Actually, the blogpost mentioned above is very controversial from a technical point of view, but it gave me idea to write this one. TSG guys are worried about non-existence of Documentum 8 roadmap, but when I have taken a look at “improvements” which were made in Content Server since 5.3 release (7 years have passed since 6.0 release), I found out that the count of new features, introduced in 6.x – 7.x releases, is hardly enough even for one major release. Below I have tried to combine all release highlights into one single list (let me know if I have missed something):
- fast and simple tomcat was initially replaced by weblogic and then by jboss – now time taken to start JMS is about 60-90 seconds, instead of previous 3-5 seconds
- FAST Search was replaced by xPlore – OK, but full-text search is still unusable for large repositories
- CREATE/UPDATE/DELETE DQL statements now honor TBO – totally useless
- LEFT OUTER JOIN in DQL – does not work properly
- RETURN_RANGE DQL queries – very limited syntax due to transformation to SQL. Why do not limit returned results at content server level?
- new privileged groups – OK, but not properly documented
- dynamic group enhancements – actually, I consider dynamic groups as an attempt to solve some design gaps in security model
- UTC dates in database – implementation is very crude
- LWSO – have never used before, need to investigate
- database partitioning – to get performance benefit you should permanently use “WITHIN PARTITION” clause in DQL statements (in Oracle such implementation is known as “System Partitioning”), very arguable solution
- Java Method Server high-availability support – Why do not improve stability of a single JMS?
- Kerberos support – OK, but setup is a challenge
- 64-bit builds – less than ten years have passed since Intel and AMD announced x86-64 processors 🙂
- Intelligent Session Management – not a CS feature 🙂
- Non-anonymous SSL communications between DFC and CS – breaks compatibility with old clients
- Aspects – very limited syntax in DQL
- Non-qualifiable attributes – very useful, but rarely used
So, After more than 7 years of development we have only two or three useful improvements in Content Server, i.e. one improvement per CTO :(, and I bet we won’t see anything useful in Documentum 8 too. In next blogpost I will try to describe what is really missing in Documentum.