Momentum 2016 Hands-On Labs Available

It’s been a while since I’ve posted anything here, so I thought I would pass along the announcement and link to the Momentum 2016 Hands-On Labs.  For those that were unable to attend EMC World 2016 or unable to attend the Hands-On labs due to scheduling, they are provided here.  Enjoy.



EMC World/Momentum 2015 Quick Hits

It was a busy week at EMC World/Momentum 2015  and it may take me a little while to digest it all. However, here are a couple of quick notes I think you will find interesting:

  • Look for the core Documentum platform to be certified on CentOS and Postgres later this summer, for non-production use. This is essentially the Documentum Developer Edition, but certification now means support for this platform. It will be interesting to see if D2 can be installed on the this combination of OS and DB. See here for reasons why it doesn’t work on the Developer Edition (search the page for “42601”).  D2 does work on CentOS and Postgres, but you have to install it like this.
  • Documentum and Docker got a lot of air time this week, partly because it’s really cool, and partly because it ties into ECD’s new Project Horizon vision (see below). Docker is an open-source project that automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization on Linux. I saw a demo this week where Docker was used to deploy Documentum, Oracle XE, Tomcat, and DA on a new image in 30 Sec. This could revolutionize deployment and support of Documentum. This demo code should be available on the EDN shortly.  See some preliminary xCP Docker efforts here.
  • A new Spring Data API was announced also. Spring Data is an umbrella framework for easy data access.  The goal of the documentum Spring Data API is to significantly reduce the amount of boilerplate code needed to implement data access layers.  At Momentum, a custom JSP client was demonstrated written using Spring Data as the API to the Content Server; it looked nice and was fast. The Spring Data API has full CRUD (create, read, update, delete) capabilities but lacks workflow and lifecycles.  This API will be released as open source in the Fall 2015 to encourage users, partners, and developers to help build it out further.  It is solidly based on the DFC.  This code too should be on the EDN shortly.
  • There was a lot of discussion about RESTful APIs, including D2FS “D2 REST”) and RM.  With the D2FS REST web services (expected end of year with “Falcon” release of D2), it will be possible to build a “D2” application that uses on the API and not the framework.  Interesting.
  • Project Horizon also got a lot of air time this week, I think every Momentum session I attended at least paid homage to it if not tied specifically to this new effort. My understanding of Project Horizon is that it is the next generation ECM platform and marketplace.  The project is all about micro-apps and micro-services (this is where Docker comes in) build on the Pivotal Cloud Foundry.  Project Horizon projects will be composed of micro apps/services deployed in Docker, giving incredible flexibility for collaboration, composition, and continuous update and deployment.  Stay tuned, I’m sure we will be hearing much more about Project Horizon in the coming months/years.

TSG always does a great job summarizing the event, I encourage you to see their blog posts for more analysis. Additionally, you can follow the #EMCWorld and #MMTM15 hashtags on Twitter.  Storify also has some fun pics and tweets.

UPDATE:  Here is a good discussion of Project Horizon from TSG.

UPDATE: Here is the application to get involved with the Project Horizon Co-Innovation Program.

UPDATE:  Another compilation of the days’ events

UPDATE:  A more detailed discussion of Project Horizon and ECD’s future plans.

UPDATE:  Project Horizon landing page.

Documentum Road Map 2014

Here is a brief road map of coming releases and features I was able to assemble from various blogs and Tweets from EMC World / Momentum 2014.

Documentum SharePoint Connector

  • Q1 2015 – v7.1 SP1
  • Q4 2015 – collaboration, linking, federated search along with ties to xCP, D2


  • Q1 2014 (past) – v2.1
  • Q3 2015 – collaboration, some case management, mobile support along with deeper RPS integration


  • Q3 2014 – v4.5 SP1: fill-able PDFs, normalized HTML
  • Q4 2015 –  “Aria”: UI enhancements, sysadmin enhancements


  • Q1 2014 (past) – v4.2
  • Q4 2014 – performance improvements, admin enhancements
  • Q1 2015 – D2 Advanced Publishing: support for publishing and virtual document enhancements


  • Q4 2014 – v6.8?: new platform/browser certifications

Content Server

  • Curiously missing from the discussion…
  • Other than NGIS will be EMC’s (with Pivital) first APaaS later this year.  I need to hear more about this. On the surface, it sounds like EMC | Documentum will be leaving a lot of customers behind.

If you have any additions or corrections please suggest them. Instead of one big “road map” session at Momentum this year, each product announced its own road map. Therefore, I am relying on attendees’ notes from each product session to assemble this road map.

News from EMC World 2014

Though I didn’t attend this year, I did my best to stay abreast of the highlights from EMC World and Momentum 2014 via Twitter and blogs.  Here are a few that I followed:

Of course, EMC and attendees spewed out so many Tweets they were too numerous to follow.  If you’d like to review them, you can find them here:

One of the most exciting bits of news I heard was that in coming months, we can expect two new Documentum Developer Editions:

  • D2 – May 30, 2014
  • xCP – June 30, 2014 (with a Linux port of CTS)

See the evidence here.

If you know of other good sources for recaps of the events at EMC World, let me know in the comments.  Thanks.

xCP2.0 Tidbits from Momentum DevCon 2012

Here are some interesting tidbits I gleaned while working through the xCP2.0 hands-on sessions at Momentum DevCon.  My impression of xCP2.0 is very favorable.  The xCP Designer looks nice, functions well (though not always intuitively), and produces very good applications.  The goal — as it has been for some time — is “compose, don’t code” applications.  xCP2.0 goes a long way toward making that a reality for the masses, not just for simple applications.  We talked through what we thought were some corner cases during the sessions and in most cases, we determined what needed to be done could be accomplished with the tools in xCP and the xCP Designer without coding.  There were some exceptions, but not many.

Here are some important bullet points I recorded during the conference:

  • Because the source files are all just XML files, they can easily be controlled with a source code control system.
  • xCP Designer is a completely off-line modeler, meaning you don’t need to be connected to a repository to develop an application, and when you change or delete objects, you are only affecting your local hard drive.
  • There is absolutely no use of WDK in xCP2.0.  xCP applications use extJS, JavaScript, Java classes, REST web services, and HTML5.
  • xCP2.1 will include migration tools to help move xCP1.x applications into xCP2.x.  This does NOT include the UI, which will need to be recreated from scratch.  Ouch!  Note that in xCP2.0 you can’t import object models, workflows, anything, these will all need to be recreated until the migration tools are released in xCP2.1.
  • xCP2.0 has unified the expression language used everywhere in the environment.  Yea!
  • xMS is used for deployment of applications regardless of whether VMware is used or not.  xMS does a great job of deploying files to the application server that constitute the UI, and objects to the repository that constitute the DAR.  UI pages, actions, etc. are converted to RESTful web services, class files, and JSP and deployed as WAR files to the application server.  There is no more middle-layer framework like there was in TaskSpace for rendering the UI.
  • xCP2.0 produces applications that are very fast.  Some of this speed can be credited to general performance improvements in the D7 core platform.
  • Uninstalling an xCP2.x application is possible, and the procedure will be published as a white paper in Q1 2012.  Eventually a tool will be produced to uninstall xCP2.x applications.
  • Composer is still the tool of choice (the only choice?) for creating and installing BOF objects.
  • xCP2.0 does not handle virtual documents and there is no plan to ever support them.  Most virtual document structures can be modeled in xCP using relationships.
  • Per- and post-installation routines will be handled by the xCP2.1 installer (xMS).
  • Stateless processes called from the xCP2.0 UI run on the application server, not in the Process Engine on the Content Server.  Stateless processes called from a stateful process run on the JMS.
  • xCP2.0 does not use the UCF.  All content transfer is native HTML5 transport.  This means on checkin, you must specify the file to checkin, Documentum will no longer magically know where it resides.
  • No Single Sign On support in xCP2.0.
  • No hot key support in xCP2.0, which means it will not be 508 compliant.  It is planned for xCP2.1.
  • xCP2.0 has 6 well designed extension points which will likely allow you to do anything you can imagine inside the framework.   POJOs can be used in stateless processes (without including DFC interfaces), custom auto activities, custom functions and expressions, 3rd-party DB drivers, JavaScript custom widgets, and themes.
  • xCP2.0 is shipping without the Process Builder debugger.  Bummer! , that was an awesome and useful tool.  It should resurface in xCP2.1, and EMC is trying to develop an application-level debugger.  The new xCP Designer does have a Problems tab (like most IDEs) that can catch a lot of design-time errors.
  • xCP2.0 applications and DA cannot run in the same instance of the application server due to JAR conflicts.  BTW, Tomcat and TCServer (commercial Tomcat) are the only supported application servers for xCP2.0.

Tidbits from Momentum DevCon 2012

I attended the Momentum DevCon in Pleasanton this week.  I learned a lot about D2, xCP, and D7, which I will relay to you over the next few posts.  However, to begin with, I want to pass on some interesting tidbits and insights from the opening day’s Ask the Product Managers session.

  • There are no plans to upgrade Composer to a newer version of Eclipse.  The xCP Designer will become the development tool of choice moving forward.
  • If you have a solution working on Webtop, there is no rush to replace it with a D2 or xCP solution.  There are no plans to end-of-life Webtop, it will continue to be supported with updates and bug fixes.  There will not be any new innovation added to Webtop though, all innovation will be focused on D2 and xCP.
  • The long-term plan is that the D2 configuration layer will be extended to xCP and then MyDocumentum clients, uniting the client layer.
  • All service and server APIs are moving toward a RESTful implementation (D7.1), adding greater cross-platform support, scalability, etc..  DFC and DFS will continue to be supported, but no new innovations will be added to those code lines.  The only changes will be conversion to native 64-bit.
  • xMS (the xCelerated Management System), the new D7 deployment tool, will only work on VM environments employing vSphere, otherwise the install processes is same as it ever was.
  • EMC recommended using SDL Tridion to replace WebPublisher.
  • Neither xCP 2.0 or D2 v4.0 expose custom Aspects.  This was a surprise to most at the conference.  xCP is likely to add the functionality at a later date; D2 will not.  So, those of you using Aspect behavior or metadata will still be writing custom interfaces to expose them. I showed you how to do this in Webtop here.
  • xPlore still doesn’t support proximity searches and there are no plans to do so.  (Proximity searches let you search for words that are near each other, or in the same sentence, or paragraph.  Verity used to do this well.).  To be fair, the xPlore PM was not present.  The other PMs were not certain but didn’t recall that capability being on the road map.
  • The UCF is not going away, but its implementation is changing.  In D7, the UCF will leverage HTML 5 document transfer capabilities and not be implemented as the problematic applet it is today.
  • D2 does not provide a way to directly apply retention policies.  D2 can attach retention policies to content through a document life cycle (see comments for details).
  • D2 and xCP will move toward integration next year.  No one knows what this means, although it was previously stated that xCP controls would be able to run in D2.
  • D6.7 SP2 (due Q1 2013) clients will be pre-certified for D7, meaning they will run on Content Server 7.  This means you can upgrade your Content Server in advance of your UI stack (which always takes longer and is more complicated because of your customizations).
  • D7 is the largest single platform release in Documentum history, refreshing nearly every product associated with Documentum.

Post-EMCWorld 2012

I did not attend EMCWorld this year (bummer!), and am just now catching up on the events that transpired there.  To do that, I am living vicariously through the blogs of those that did attend and were kind enough to blog about their experiences.  If you were unable to attend and would like to catch up on the events of the week, these are the blogs I have been reading.  Do you know of others?  Let me know and I will add
them to the list.

Finally, you might checkout some of the virtual sessions hosted by EMC.  These are almost as good as being there (almost),

%d bloggers like this: