Year: 2014

Getting social with EMC Documentum?

EMC World 2014 and the sub conference for EMC:s Information Intelligence Group called Momemtum is hours from kicking off here in Las Vegas. In the light of last week’s announcement from Cisco that it is dropping their WebEx Social (formerly Cisco Quad) product and instead partnering with Jive Software make me want to examine this space in relation to EMC Documentum. We are all talking Enterprise Social or Enterprise 2.0 of course and when it comes to Enterprise Content Management systems that is something we like to see as a social layer on top of established technologies to store unstructured information that makes interaction and collaboration more seamless.

What is this enterprise social thing then?

I would argue that what we need is support for asynchronous or non-realtime collaboration added to the features we can offer enterprise users. However, not only offering that as some separate silo of information often run in the cloud but as an integrated solution (with an on-premise option for some of us) where we can collaborate asynchronously around documents that we already have stored in ECM-systems like EMC Documentum.

  • Enterprise Social = Asynchronous collaboration = Non-realtime collaboration

Why does it matters for enterprise content management?

ECM is all about storing unstructured information in a way that provides context around it so it can be used efficiently in our business processes. That context includes metadata based on various taxonomies, security, lifecyles, workflow capabilities, alternative formats but also extracting information from the content that allows for “discovered metadata”, classification and of course search. To me Enterprise Social is just about adding an additional set of context around information based on people collaborating around it not seldom without any formalized workflow support. That context is then so helpful in providing additional perspectives or views on the information based on what people have thought if it rather than what it is actually containing.

What kind of feature are we talking about then?

The social features that we usually expect when it comes to enterprise social applications are not just the pieces of added collaborative context but also the visualization views based on those attributes which includes:

  • Comments
  • Sharing (links to content in ECM or general links which is social bookmarking in a sense)
  • Likes
  • Favorites
  • Tags (ad hoc metadata)
  • Tag clouds
  • Status updates
  • Questions/answers
  • Wikis
  • Blogs
  • @messaging
  • Private messaging (hence replacing email)
  • Document collections (again based on links to ECM)
  • Activity Streams (both based on social actions but also from ECM like recently uploaded documents, workflow tasks, versioned documents etc)
  • Ideas and Thanks
  • Related content (others have also viewed or similar content to this)

What about synchronous or real-time collaboration?

Having some kind of asynchronous collaboration features in place of course make it natural to include integration to realtime collaboration support with features like:

  • Presence
  • Text chat
  • Audio chat (or VOIP)
  • Video chat
  • Desktop sharing
  • Meeting rooms with text, audio, video, presentation sharing

An ability to provide a seamless integration from seeing a comment around a document from a specific user, noticing the green presence icon next to the name and seamlessly launch a text or audio chat is of course powerful an helpful instead of relying in three different applications to do the same (ECM, Social and chat).

What have EMC Doumentum done in the social area before then?

Quite a lot to be honest but also to some degree to much in terms of not having a coordinated product effort over the years. First of all eRoom was/is a product based on just that, collaboration. It provided a way to set up spaces for collaboration often used for projects. After it was bought an integration effort was made to make eRoom use the same repository technology as the rest of the Documentum stack which made a lot of sense for those wanting to eliminate the information silo. A popular feature in that also included data tables even though their social nature is not that obvious but providing “basic Excel” on a web page is a useful feature.

Second, application-based on Web Development Kit (WDK) and especially Digital Asset Manager included a fairly cool set of additions called Documentum Collaborative Services. What it did was to provide that asynchronous collaboration layer inside both the user interface and in the information model of Content Server. It included features like:

  • Rooms (basically supercharged folders)
  • Rich media formatted texts that appeared as “banners” on top of every folder view (could be used to explain the purpose of the folder)
  • Discussion threads
  • Data tables
  • Calendars

After that came the first true effort to provide a modern social layer for Documentum in its Centerstage client which provided a modern AJAX-based interface with features like:

  • comments
  • tags
  • tag clouds
  • activity streams
  • new way of previewing content inspired by coverflow in iTunes.
  • wikis
  • blogs
  • discussions

In addition to that it also feature a new search capability based on Xplore and a nice facetting based on discovered metadata. From a technology standpoint so called Centerstage spaces included document libraries, discussion components which placed in a Spaces cabinet which in other clients looked like folders. Even more powerful these collaboration objects could be set up as a result from a an activity in a process.

Finally we are now in the era of the next-generation client called Documentum D2 with an even more modern architecture with configurable workspaces that can be set up differently for different groups of people. It actually includes some social capabilities like being able to view collaborative workspaces created in Centerstage but also doing comments and favorites on pieces of content. Another collaborative feature is support for annotation on/in documents which are even more enhanced if using any of the third party provided viewers that work with Documentum D2. Finally the feature which allows you to subscribe to changes to a document is back again (was available in Webtop/DAM) which actually is a powerful collaboration feature.

So there have been a fair set of collaborative features in the Documentum product over the years. The catch is however, that not all are available today in the current set of products.

What about Documentum and other provides of social platforms?

In May 2011 there was an announcement from EMC and Cisco about teaming up around social features by providing an integration between Documentum and what was then called Cisco Quad. In essence it meant being able to connect to documentum to document library sets within Cisco Quad using the CMIS interface. Cisco Quad then provided seamless integration to Cisco’s support for real-time collaboration such as WebEx Meeting and Jabber.

Around the same time it was announced that VMWare acquired the microblogging platform called Socialcast which provides an internal activity streams to customers but without features likes wikis and blogs. We have also seen a few official signs of that Socialcast technology is making its way into the platform and even seen prototypes of Socialcast-power activity streams within Documentum D2. CMS-wire have in fact publicly requested Chairman Joe Tucci to give Socialcast to the Information Intelligence Group which has been discussed again this weekend in a new article from CMS-Wire.

Finally it is worth mentioning that EMC the company is using social software from Jive Software to power its own socially-enables community called ECN which means that experience around that product is within EMC, although not necessarily in the Information Intelligence Group where Documentum belong. The hard part is to be able to both surface Documentum content in Jive and provide social interface components in D2 and xCP.

What is IBM and Alfresco doing then?

I spent last week at IBM Impact 2014 and had the opportunity of speaking with some executives around both their Enterprise Content Management software based on IBM Filenet and their collaboration software IBM Connections and IBM Sametime.  They currently provide an integration between both their Content Navigator product and Case Manager where social features like comments can be made on content stored in Filenet. There is also presence and chat integration from Content Navigator to Sametime as well as a possibility to go to Sametime Meetings directly from Connections. A lot of the integration is based on CMIS but there is of course possible to use REST-integration for all these three clients. I guess that is also the interesting observation that even if the integration exists there are still three (or four if you count Case Manager) web interfaces for ECM, Social and Real-time collaboration.

Since Cisco is now abandoning WebEx Social an integration with a product like IBM Connections (and therefore also IBM Sametime) make a lot of sense if this thing with VMWare Socialcast does not plays off. All these have REST-interfaces which would make integration feasible.

I guess I have to mention Alfresco as well here since it has a tendency to surface as an alternative to Documentum and Filenet from time to time. Alfresco is sometime marketed as Social ECM and the community edition offer a basic set of social features on top of the documents. You can favorite, like and comment (without notifications) and there is an activity stream to let you see what has happened in sites you are a member of. In addition to that each site contains support for discussions, wikis, bookmarks and data lists (similar to data tables). Finally you can do “Dropbox”-like sharing of content but their integration with Desktop and mobile apps are nowhere near where EMC has come with syncplicity. A decent benchmark for social features in ECM but also not a dedicated Social interface like Socialcast, WebEx Social, Connections and Jive. Also no integration with enterprise real-time collaboration tools like WebEx, Lync and Sametime. Still Alfresco seem like things you use if you can leverage other web/cloud-based services.

What’s new and next with Documentum D2 (old notes from EMC World 2013 & Momentum 13)

Found these notes from EMC World 2013 and decided to publish them even though the next EMC World is coming up soon.

This session was presented by Sunil Sharma, Principal Product Manager D2.

D2 4.1 has been released.

Talks about the move away from coding towards configuration. Move from efforts share of 20% configuration and 80% development to the opposite.

Highligthing the following benefits:

  • Faster delivery (from weeks to hours)
  • Lower risk (avoid long build & test cycles)
  • More responsiveness (Deploy/Configure/Run)
  • Expanded foot print (broader use)
  • More Compelling personalized and streamlined applications

Value for Documentum D2:

  • Productivity
  • Intelligence (content rules without coding)
  • Agility (easy to build and deploy)

Focus for the D2 4.1 release:

  • Enhanced usability (a broader set of advanced document management and content control capabiliites
  • Integration and interoperability
  • Search
  • Collaboration (on content using discussions on content and native annotation capabilities in MS Word.
  • Extensibiity (custom widgets with two-way applications)
  • Ënterprise focus (link admins to a limited set of applications)

Distribution is similar to quickflow from Webtop/DAM.

Features that I like are managing relationships, mass update of properties, saved search, faceted search, virtual document editing and document comparison.

Custom widgets can be developed. Listeners can be developed by customers around widgets provided by EMC. Make it possible to “catch” certain criteria of what is happening in an EMC Widget.

Example of custom PDF viewer where clicking on a Word-document shows the PDF rendition in a viewver. Also an example of showing diagrams and pie charts based on data in the repository such as values of certain attributes.

Cool example of creating a virtual folder structure based on attributes. Also example with maps where clicking on a document repositions the map and where searching for a city in the map updates the list of documents based on selected geolocation.

Possible to leverage the D2 rules engine in other application through D2FS API.

What is coming in 4.2:

  • Advanced doc management (drag & drop, extracting properties from email, advanced “email as link” with possibilities to pass queries and settings in the URL, content linking, bulk import with metadata in either .csv or .xml)
  • Search (nested facets, search summaries and term hit-highlighting)
  • Usability (iPad support)
  • Enterprise focus (HTTP transfer of files, context sensitive widgets)
  • Enterprise configuration (new abilities to secure a configuration from unwanted changes and preserving configurations using version control.

Simplified content creation process to be able to skip certain parts of the import process if you have a default configuration for each step or silent it.

Themes for future releases:

Pervasive Business Rules

Solution Platform Harmonization – D2 is the UI for content-centric applications. The idea is to use xCP to compose widgets and use them in D2. The page in xCP can be exposed in D2 either as a widget or a workspace.

Collaboration (D2 will replace Centerstage and eRoom).

Project Workspace

 

Documentum REST Services (old notes from EMC World 2013)

Realized that I had this draft från Michael Mohens session at EMC World around Documentum REST and decided to publish it even though time have passed and the REST-interface has been shipped and now we are waiting for xCP 2.1

REST mimics the way users use the Internet.

Everything is a resource and it is stateless – the server does not need to know where you come from and where you are going.

REST Services are programming/language/framework independent. Any language which has an HTTP framework. No SDK required.

If it is stateless it is much easier to scale. No session to replicated since the state is not persisted on the server side.

No SDK also means that there are no clients to upgrade so also scalability from an IT management perspective.

Acknowledges that EMC IIG have talked about that for a while but now they are ready to deliver.

Technology Preview 1 for Core Platform  announced on March 2013.

TP1 for xCP (generated by the actual application that you developed)

  • Business Objects
  • Content
  • Folders
  • Relationship

REST also coming for Captiva and D2 so D2FS is going away in the long run.

REST is shipping early Q3 2013 for Documentum 7 with the following features:

  • Authentication
  • Repository services
  • Object Services
  • Version Services
  • Schema Services

What is not in the first release (end user services had prioritization):

  • Lightweight object services
  • Access control (you can’t create a new ACL)
  • Lifecycle services
  • Virtual document services

xCP REST GA will be part of xCP 2.1 in Q1 2014

  • The concept is to automatically generated (almost everything will get a REST interface).

Spring is the biggest framework in the Java world.

Still deploy REST as w WAR-file just like Webtop or Media Workspace. API is stateless for HA and deployment flexibility. Previously it was bound to a host name.

Simple JSON and XML representations.

Authentication

  • HTTP basic authentication (great for inline passwords, make sure HTTPS is used!)
  • SPNEGO-based Kerberos (great for users in AD domain. (Can be done across multiple domains but be in the same forest with two-way forest)

Pushing for SAML later on.

Default response is XML but butting objects.json? will switch to JSON representation.

The REST War-file is designed to live outside the content server. Important if you want to place it in another part of the DMZ to allow mobile access.

DQL is right now read-only operations. Done using HTTP GET.