TechSet 2012 Wrap Up (part 2)

This post will wrap up my comments and insights from TechSet 2012.

xCP 2.0: The Developer Experience (Dan Ciruli)

  • TaskSpace and WDK are being phased out and replaced with a generated ExtJS UI.  This will obviously cause some migration and upgrade issues.  Documentum hopes to provide some migration tools with the 2.1 release but states that the migration of the UI will be a manual process (i.e., rewrite).  For example, you should be able to open an xCP 1.x DAR file in the new xCP Designer tool (see below).
  • xCP 2.0 will sport a new, fully integrated, Eclipse-based  development and deployment tool that is not Forms Builder and not Composer (tentatively named xCP Designer).  The tool will feature the following capabilities:
    • Completely offline development environment.  No need to be connected to the Docbase to create a new xCP solution, and all objects are created locally in XMl files (similar to how Composer works now).  These files can be easily controlled by Subversion or other CM tool.
    • The tool will combine the features of: forms developer, process developer, Composer (data modeling and deployment), and RPS editor into a single, unified tool.
    • The goal is to make the xCP Designer experience feel like developing software.  (I guess it previously didn’t?).
    • The xCP Designer will generate the UI using XML and ExtJS.
    • Out of the box, there are fewer UI components than Forms Builder; however, custom components can be created.
    • One expression builder based upon SpEL instead of the various, inconsistent expression builders scattered throughout the xCP stack.
    • Backward compatibility with xCP 1.x DAR files.
  • The xCP 2.0 application stack will use the following technologies:
    • Spring – the generated application framework,
    • ExtJS – the generated application UI,
    • RESTful web services – out of the box generated services and APIs.
  • CIS seems to be part of the xCP stack now (I’m not sure it was previously) and can be leveraged in application building using the xCP Designer.
  • Built-in analytics.  Charts and graphs can appear on any screen, not just a dashboard.
  • Built-in federated search using xPlore and a new built-in document viewer (Brava! will still work if you need the extended capabilities Brava! supplies).
  • Business events.  This is a concept new to xCP 2.0.  Business events are system events triggered by a source, condition, or action.  They are policy-driven rules that allow the application to react intelligently to a situation.  They will leverage the new stateless processes introduced in D6.7.
    • SDTs have been eliminated!
    • Forms Adaptors have been eliminated!

If xCP 2.0 can really deliver this, in my mind the platform has finally arrived.  One outstanding question is what role/impact will D2 have on the platform?  Probably none, as previously discussed, xCP 2.0 and D2 will be divergent solution platforms.

Pervasive Governance (David Humby)

  • What is Pervasive Governance? “…the set of multi-disciplinary structures, policies, procedures, processes and controls implemented to manage information on all media in such a way that it supports the organizations immediate and future regulatory, legal, risk, environmental and operational requirements.”
  • EMC\Documentum Information Governance products fall into the following categories:
    • File Intelligence
      • CIS
      • Kazeon
      • TCS
    • Records Management
      • RPS
      • RM
      • PRM
    • Rights Management
      • IRM
  • EMC’s approach to information governance is pervasive because it exists throughout the EMC solution stack and in all stages of the information lifecycle, as well as those stages that occur outside of an EMC system.
  • Organizations keep information longer than they should.  This increases storage costs, discovery costs and presents liability.
  • The next release of RPS (6.7 SP2) will contain a scalability framework designed to distribute the application of retention policies (or holds, or dispositions, etc. called “work orders”) across multi-threaded processes to dramatically improve performance.

About Scott
I have been implementing Documentum solutions since 1997. In 2005, I published a book about developing Documentum solutions for the Documentum Desktop Client (ISBN 0595339689). In 2010, I began this blog as a record of interesting and (hopefully) helpful bits of information related to Documentum, and as a creative outlet.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your 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

%d bloggers like this: