MOSS and Documentum

MOSS and Documentum

I’ve had some time lately to think more about the question of integration, or unification, between MOSS and Documentum; or any other ECM system for that matter. This came about as a result of a couple of situations where I found organisation looking closely at how to integrate the two producs; plus some reading of Andrew Chapmans blog.

Taking a big step backwards for a while I started to get a little concerned the way things are moving here, it feels as though there is a great deal of momentum behind the movement to have both systems operating together. Is this really the best way to serve an organisation’s requirements, in fact what are the organisation requirements?

It is not pushing things too hard to suggest that an organisation would like to capture, store, manage, use, distribute and possibly archive some of their content. I doubt there is any requirement to have these things met by having two repositories of information so what is it that one gives that the other does not?

MOSS

One of the key arguments in the pro MOSS brigade is the UI and the level of collaboration available within MOSS. I’ve asked a few people a number of times and if anyone out there has any suggestions but what collaborative features are people looking for which MOSS provides which Documentum cannot? With regards UI, if people move down the approach of Webparts then at the end of the day the UI they use to access Documentum through MOSS is the same as using Webtop basically.

Documentum

The weight here is usually behind the issues of compliance and scalability. Compliance is something which MOSS is starting to deal with and I expect it to be comparable in the near future. Scalability remains a concern for MOSS implementations, however I’d expect this to be resolved in the next 12-24 months.

Perhaps I am missing something here but it does seem that the approaches being proposed are not actually going to solve the business problems but will instead justify the need for having two ECM systems when one will do. We should be evaluating the systems against the requirements of the business and deciding which one is the best fit.

About these ads

2 thoughts on “MOSS and Documentum

  1. But simply playing devils advocate, MOSS is NOT an ECM system, its a glorified portal, and as such it is fit to sit ontop of Documentum (or Filenet or Livelink) as the interface layer. So your right about the web parts, but EMC provides JSR168 compliant portlets for use with BEA, IBM and other portal software.

    We have thought (not very seriously) about stuff MOSS in at the interface layer above our very broad scoped Documentum implementation because we have problems with the 5.3 PS3 Office Connectors (they will only use an old version of .Net and it causes a clash with another app which needs the latest version). So the nice Office to MOSS integration might solve this, and its a use case I have seen suggested in many places – MOSS for ‘work in progress’ and “real ECM” system behind it as the ‘system of record / archive’.

    To complicate things further where does eRoom sit as competitor to MOSS on the collaboration front ?

  2. In considering MOSS as a glorified portal I completely agree, my problem is those who consider it an ECM system or even a collaboration tool and have a desire for it to work with Documentum. In fact this relates to the Use Case mentioned where ‘work in progress’ is handled in MOSS and ‘records’ in Documentum; I see little value in introducing an additional store for this purpose…or rather I remain to be convinced. As a standard flow it sounds great but the problems arise with the exceptions or alternate flows where the document becomes ‘live’ again, does the document move back into MOSS for this purpose

    With regards eRoom, I don’t see a future for it. EMC are moving all the collaborative features into the core Content Server, when this is complete they will move customers away from eRoom into core Documentum. There are enough reasons for this move.

    Thanks for the input.

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