xCP environment registration Part III

The xMS Agent reffered to the xms-env-registration-ui.bat file. In this user-interface you can add all your available Documentum components (eg.: Repository, CTS, CIS, BAM, etc).

The manual registration is only necessary if you don’t use the xMS Server and the blueprint installation.

This Agent make your xCP application in your do-it-yourself-environment available.

If the utility is accessing the xMS Agent for the first time, it prompts you to set a password for the
default admin user. Use this password for subsequent access to the utility.

You do not have to create additional system accounts, because there can be only one SERVICE account per environment.

You can use the SERVICE_ENDPOINT system account type, if you want to create a generic account for use across several vDCs. SERVICE_ENDPOINT is specific to each environment, and you need to specify it in the environment profile XML file for each environment.xms_app_registration_detail_000065

This screenshot was taken from the xMS Agent environment registration utility.

Register your environment manually. Create a new environment blueprinte file and register all the recommended Documentum components:
Repository: Content Server Ver.7.0
BAM: BAM-Server 2.0
App Host: Tomcat Server 7.0.29
Documentum Administrator: DA 7.0
Search: xPlore 1.3
BPS: Process Integrator 2.0
Content Intelligence Server: CIS 7.0
Content Transformation Server: CTS 7.0
(optional) Thumbnail Server 7.0

This screenshot displays the registration of the primary repository. You can add as many repositories you like.

Save your settings and restart the xMS Agent. Remember: the agent is part of the app server (Tomcat) webapps. Please restart the Tomcat services on your host windows server.
Wait until all webapps was successfully (re)deployed.

D7 xMS preparation

xCelerated Management System Version 1.0

My first impression about IIG’s xMS technology was great: automate environment provisioning sounds good and automate xCP application deployment  into a VM infrastructure sounds much better. Blueprint deployments, custom environment profiles and reduceing of deployments from weeks to hours were too tempting. Meaningful features like automated monitoring and environment reporting let me be curious.
But be carefull, you need at least one ESXi Server and one vCenter Server to create a VM infrastructure. And the VMware vFabric tc Server is requiered to create and manage Documentum deployments. For monitoring and environment the VMware vFabric HypericEnterprise Software is required.


  • Microsoft Windows Server 2008 R2 SP1 – 64 bit (other operating systems are not supported)
  • VMware ESX Server 4.1 or ESXi Server 5
  • VMware vCenter Server or vCloud Director
  • VMware vFabric tc Server Standard Edition 2.8.0 (Version 2.9.X is not supported)
  • VMware vSphere 5 Client


  • disable firewall and antivirus software
  • disable User Account Control (UAC)
  • enable Remote Desktop Connection
  • install JAVA 64 bit JDK version 1.6.31 (Version 1.7 is not supported)
  • put base VM into windows domain (recommended)
  • download and extract xms-tools.zip
  • copy the installs folder to a shared storage (NAS or file server)

Documentum product requirements:

Documentum Administrator (DA)7.0
Documentum xPlore1.2 / 1.3
xMS Tools1.0
Documentum Content Server7.0
xMS Agent
(to deploy xCP applications)

xCP product requirements:

Documentum Business Activity Monitor (BAM)2.0
Documentum Content Intelligence Services (CIS)7.0
Documentum Content Transformation Services (CTS)7.0
Documentum Document Image Services (DIS)7.0
Documentum Foundation Classes (DFC)7.0
Documentum Process Engine2.0
Documentum Process Integrator2.0
Documentum Thumbnail Server7.0
Documentum xCP Designer2.0
Documentum xCP Runtime2.0
Documentum xCP Viewer Services2.0

The major changes of xCP 2.0

The xCelerated Composition Platform version 2 is nearly a new development. There are so many changes between the first and the second version.  Some features are not compatible to the old version. The following table displays the major changes including a small description.

xCP 1.x xCP 2.0
Structured Data Types* Business Objects replaced SDT
* BO are flexible, have relationships, events and are persist after the process completes
Types-bayed ObjectsTBOs will still supported but unnecessary
User Interface* old WDK will be unsupported
* new ExtJS interface
* RESTful Service interaction
* Browser independent, becasue GUI based on HTML 5 (best performance with google Chrome)
Forms Adaptors* Adaptors from the FormsBuilder are not longer supported
* Data Services will be used
they are more flexible (realtime, historical/ external) Queries
Taskspace* Taskspace not longer GUI of xCP
* Native xCP viewer
* Zero footprint technology on all Browsers and Devices
* Big Data Services with Greenplum
* Syncplicity (data synchronization between many devices and the repository with permission sets for each object)
* easy connection to additional EMC Products (Captiva 7, xPression , etc)
Process DebuggerThe ProcessBuilder Debugger the will not be included in the 2.0 release. Dan said on the Momentum this year that the Debugger must be completely rewritten and this will take some time. But the deployment on the test environment is very fast and should not be a big obstacle.


Momentum Vienna 2012

Momentum Vienna 2012


The xCP 2.0 Interface

The xCP 2.0 Interface

Personal impressions of EMC’s hands-on LAB in Vienna.
The second lab session called “Advanced” on wednesday, 7th November 2012 was a deep preview of the new xCP user interface.

The new interface of the xCP Designer

The xCP Designer is the new unified tool to build applications on top of the Documentum 7 environment.

The xCP Navigator

  • The Application Settings includes Model, Role, Parameters, Endpoints, Permission Sets, Email Templates and (general) settings. This folder has the functionality of the TaskSpace Configuration-Page and Documentum Composer.
    Very helpful is the new “Endpoints” functionality where all connection parameter to external system or repositories are stored. In xCP2.0 exists only one central page to administrate all login and connection data.
  • The Object Models and Processes represents the ProcessBuilder and Composer features.
    The Object Models area includes the Business Objects, Content, Folders, Picklist and Relationship function.
  • The User Interface and Data Services replaces the FormsBuilder and the awful Adaports from xCP 1.x.
    The User Interface section includes the functionality to create and manage a default Master page and runtime Application UI, Business Object UI, Content UI, Folder UI or Process UI. The Master UI has the same functionality like the master page in Microsoft’s Power Point.
    Data Services is a collection of queries to create data-based widgest. It’s possible to gather objects from the repository (realtime), historical data, indexed content and tasks.