The anniversary 10th Documentum release will be written on Java

Today I had a private conversation with IIG ECD semi-god:

Actually, John did want to present Documentum 10 roadmap on the upcoming EMC World, but I’m not going to attend with event, so, I’m sharing Documentum 10 roadmap in this blog. EMC realized that Content Server is a black sheep in their Documentum product stack because it is written on C/C++ (all other products are written on Java) which causes a lot of issues related to development, maintenance, performance, security, etc. And now they are going to completely rewrite Content Server on Java. What we should expect from this renovation? I bet you cannot event imagine all advantages of upcoming changes, the brief description of some of them is:

  • REST and DFS will be a part of Content Server – no more dedicated servers for these services
  • Content Server will include a generic HTTP-gateway for content transfer operations – no more ACS and thumbnail servers
  • you will be able to work with Documentum objects using EJB API
  • no more client-side TBOs – all custom logic will be proceeded on Content Server side
  • embedded scripting language for server-side customization – no more dmbasic, method server, etc
  • Quartz-based job scheduling – more flexible job scheduling
  • instant processing of workflow activities
  • on-demand content transformations
  • the grammar of DQL will be greatly extended, for example you will able to write something like: grant read to ‘user/group_name’ on dm_document objects where …

etc, etc …

8 thoughts on “The anniversary 10th Documentum release will be written on Java

  1. Does this imply that Documentum falls behind than Alfresco? Because what has been mentioned above are already implemented in it.

    Like

  2. Andrey,
    I think, it’s time for a completely new information server with less or, better, zero compatibility with past Documentum versions: this is the only way to make real innovation. I think that if ECD does not do that, Documentum will be used “just” for niche (but riche) vertical markets like engineering and life sciences; in remaining markets customers will replace Documentum with newer ECM players and newer technologies. I hope ECD will have a second life and the economy to continue to release newer products and real innovation, as did in the past (btw, where is the NGIS? http://artika.biz/2011/12/next-generation-information-server-traits-explained/)

    It would be interesting to read more ideas about Documentum X from other customers / partners.

    Interesting post, as usual Andrey!
    Yuri Simione, @artika4biz

    Like

  3. Yuri,

    I can’t agree with “less or, better, zero compatibility” point because it’s a hard to determine what technologies are obsolete or wrong, let me provide some example.

    Since D6 global registry is a mandatory part of all Documentum deployments, but currently the only role of global registry is to store SBOs, and now I even can’t call to mind when I was coding SBO last time, but for weird reason some documentum products do use SBOs. So, in my opinion, SBOs are definitely useless, but is global registry useless as well? In think that the answer for this question is “No”. I already demonstrated you how it’s possible to use config service api and global registry to configure third-party DFC-based services, unfortunately EMC does not share documentation about config service api in DFC, and so nobody does know about this perfect technology, moreover, instead of having common config api for all Documentum products EMC prefers to invent square wheels every time.

    I think that the first step for happiness is a global review of product stack, bug tracker issues, support issues, competitors solutions and best practices. Unfortunately, instead of doing right things EMC is doing something weird, for example, last EMC’s feature requests initiative (https://iigers.zendesk.com/hc/en-us/requests/new) gave EMC support (and developers) a right to close bugs on support portal with a simple explanation: “fuck off, we do think that it is a feature request (and we do not care that you appeal to best practices and common sense),so, we are not going to implement that”

    Like

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 )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s