Momentum 2010 – Documentum Architecture

So the Documentum Architecture session has traditionally been one of the busiest at the Momentum conference, and in spite of the 8.45 am start this was the case in Lisbon as well. The session was presented by Rohit Ghai and Jeroen van Rotterdam. Rohit started by saying that the session wasn’t at the right time as it was going to provide more detail on the technical keynote which had not yet been given. (Note to conference schedulers, put the sessions in order and give this highlight session the slot it deserves).

Rohit put some context onto the development of the products, some Business and some Technical. He explained that they had identified three waves of focus in each of these. The Business Context was Collaboration, Compliance, Content and IT. The Technical Context was Datacenter Architecture, Application Architecture, Web and UI and Endpoints. For each of these Contexts Rohit described how the world has evolved and what this means – so for example content has moved from paper digitisation, through word docs to rich and social media.

Rohit then introduced the new stack:

UI Layer – Modular User Interfaces

Composite Application Layer – Case based applications

Information Services Infrastructure – Cloud, Information Types

Interestingly Rohit mentioned that EMc want to provide the compliance layer for all information, and he touted the idea of using EMC as the Compliance tool for information such as Googledocs, I’ve mentioned in the past how Googledocs could do with this…didn’t think EMC could play in this area but nice idea.

Jeroen then took to the stage and said he wanted to give us a sneak preview of where they are heading, this was not intended to be a roadmap. Currently EMC provide a centralised architecture, they want to move away from this:

– to be the platform for hybrid cloud deployment;

I’ve heard cloud mentioned a few times at the conference and sometimes too many people think cloud is virtualisation, Jeroen was clear on this…it is more than that, and yes we need multi tenancy.

Xplore

Jeroen then gave a brief introduction on XPlore, GA on 1st November! He talked about the current architecture and how the new architecture is very similar and the existing XML extraction technology will be used as well as the existing DFTXML format. Interestingly XPlore has been built as a standalone search engine, it will not need Documentum to run. Lucene is heavily embedded into the architecture, but is deep within the architecture. For more info on XPlore Jeroen recommended one of the XPlore sessions.

UI

After a quick recap on the Centerstage architecture Jeroen confirmed that xCP 2.0 will be built on the RCMP model, however he did note that they will not forget their WDK users and will look to achieve backwards compatibility…although this will be a challenge. He talked about the performance challenges in Centerstage 1.0 but these have now been resolved. MediaWorkspace and Centerstage will in the future work on the same technology and with data tables now in Centerstage they will look to help customers migrate from eRoom to Centerstage. Basically it looks as though we will finally see a rationalisation of the user interfaces which EMC provide. The Long Term UI strategy is:

– Client – Native RIA

– Developer – Spring IDE (Eclipse)

– Admin – Hyperiv + vCenter

Jeroen then described the EMC Cloud Information Services Strategy, and for this cloud means:

– scale out;

– multi-tenancy;

– no 3rd Party SW components, yep thats right, no more reliance on Oracle or MS for the DB or on other vendors for the App Server…simplification and cost reduction, yay!

– no downtime;

– dynamic provisioning;

– virtualisation;

– billing & metering;

Unfortunately at this stage Jeroen had ran out of time, despite a whole host more material to cover, some things I picked up on were XACML in xDB11 and even more interesting is the end of the Content Server, it will be the Information Server in the future. If this means the ability to do true structured and unstructured in one repositoy with one set of policies to manage this…well that is exciting.

Overall this was an excellent session and for anyone who has worked with Documentum for a long time should be enough to give the taste of the future, and it sounds incredibly bright. I will do more to write my opinion on the session in coming days but its been a busy day and I still need to write up the morning keynote from Mark Lewis.  I won’t get all my write-ups done this week so some will need to wait, and I look forward to reading other people’s views on the conference. Day 2 is now done and I am pleased with what I have seen thus far. So in answer to the question posted here, the thing I most enjoyed about Momentum on Day 2, for me, was the passion and excitement which the EMC team demonstrated in their vision for the future of IIG and a realisation that there will be change, and it will be a change for the good. If EMC can demonstrate and maintain this passion while delivering these changes then as a partner I can help to get customers excited and help to get them investing in EMC solutions. Good stuff.

Advertisements

3 thoughts on “Momentum 2010 – Documentum Architecture

  1. Pingback: Momentum 2010 – Keynote « Observing Content Management

  2. Pingback: Momentum 2010 – Summary « Observing Content Management

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