Cameo DataHub Versions 18.4 beta and later introduce the capability of connecting to HP Application Lifecycle Management (ALM) Data Sources. In the Driver drop-down list, you can click HP Application Lifecycle Management to add HP Application Lifecycle Management Data Sources.

To add an HP Application Lifecycle Management Data Source

  1. Click on the DataHub Explorer toolbar. The Add Data Source dialog opens. From the Driver drop-down list, select HP Application Lifecycle Management.

    Add Data Source dialog for adding an HP ALM data source
  2. Enter the Authentication URLlogin name, and password. Click to verify the user credentials.
  3. Choose the Domain and Project from the Domain and Project  drop-down list.
  4. Click . An HP ALM Data Source appears in DataHub Explorer.

    HP ALM data source in DataHub explorer 


  • An HP ALM Data Source has four parts: Defects, Requirements, Test Lab, and Test Plan, as in the figure above. DataHub operations, e.g., Copy Data and Copy Data with Sync, can still be carried out. Either one-way or two-way synchronization is possible, similar to other Data Sources.
  • ALM projects are grouped by domains. A domain contains a group of related ALM projects and assists you in organizing and managing a large number of projects. Each domain contains a Projects folder and a Template Projects folder to organize your ALM projects and template projects.


  • A single HP Data Source represents a single HP project from a particular Domain. An HP user connecting via their web interface has the same options.
  • HP ALM does not have incoming links for Defect elements. Regardless of how you create the links, Defect nodes can only link to other elements as outgoing links. If you create an incoming link for a Defect element in MagicDraw and synchronize it back into HP, it will be ignored.
  • In HP ALM, a Requirement Trace can link only two requirement nodes. If you create a Trace between a requirement element and a non-requirement element, e.g., Defect or Test, in MagicDraw, it will be ignored by DataHub synchronization.