OSLC API and POX Profile simplifies CLM traceability

Further to OSLC + POXProfile post, RPE 2.1 with CLM 6.0.2 simplifies the data source configuration; especially while configuring dynamic data source for traceability reports.

Use OSLC / Permanent link for configuring the data source URL without having to modify the URL manually or through JavaScript. This simplifies the data source configuration to a great extent as the Permanent / OSLC links are available to the user from the product UI.

Watch video, created by Dragos, on requirement (DNG) to use case design (DM) traceability document generation using Permanent / OSLC links from DNG and DM without having to go through building Rest URL. Continue reading “OSLC API and POX Profile simplifies CLM traceability”

No PhD required

CLM 6.0.2 comes with the server side implementation for the Plain Old XML profile or POXProfile. You can test this feature using one of the recent milestone builds.

Based on the name you might think “great, one more reporting “feature” that requires a PhD just to get a PDF of my data” but the Plain Old XML Profile is designed to remove much of the complexity associated with creating traceability documents in RPE.

In essence the POX profile allows a client (RPE, browser addon, curl etc) to request and receive Reportable REST XML from OSLC URLs. The feature is designed for document generation but you can use it whenever you need to access the XML representation of your data.


The image above shows using the POX Profile to get Reportable REST XML from DNG using the FireFox Poster addon. The is URL obtained from DNG’s “Share link” dialog.

For document generation this essentially means that URL manipulation or additional server requests are no longer required for following links. See below for examples. This in turn translates into simpler templates that produce documents faster.

The POX profile complements well using JRS as it simplifies fetching additional data attributes which are not available to JRS such as images and rich text. For such properties you need to request the data from the point product itself starting from the OSLC URLs returned by JRS.

Below are some examples of the document generation flows with and without the POXProfile.  Please note that the client side implementation is not available in the RPE GA but we are working on it.

Continue reading “No PhD required”

Traceability with DOORS 9 and RQM

Continuing the series of articles on the topic of creating traceability documents I have arrived at an interesting use case:  traceability from DOORS 9 and RQM.


In this article I will describe how to create a document with requirements from DOORS 9 and their associated test cases from RQM.

Continue reading “Traceability with DOORS 9 and RQM”

Adding Quality Management data to the traceability mix

Continuing the Assemble traceability documents from reusable building blocks I want now to add QM data in the mix. I will be using the same DM model as a starting point and I will follow links to QM Test Cases.

As you read this I  recommend also going through Geoff Rosenthal’s the excellent Rational solution for Collaborative Lifecycle Management Traceability Templates with Rational Publishing Engine tutorial.

The artefacts for this tutorial are available on the Unclassified & Cross Domain Templates section of the RPE Wiki Community at #15  DM to CLM Traceability.

Getting the DM link information is already covered in  Assemble traceability documents from reusable building blocks so I will skip it here. This article starts from the point where you have your DM and DM link data in place in your template.

How QM linking works

But before I go there I want to explain how QM linking works and what are the various schemas you will encounter in the process.

QM, just like all the other CLM products has an OSLC API that is used for linking. A QM Test Case will be referenced from another product using a URL that looks like this:


For the example I am presenting you can get these URLs from the link page of the DM artifact.  And if you access these URLs from a tool like Poster and specify “application/xml” for the “accept” header you can see the data available. One thing you will notice is that even though the data is not in the form you are used to when reporting on QM with RPE which is the QM’s Reportable REST API.


Unlike DNG there is no way to convert from the RQM OSLC v2 URL to the Reportable REST URL but for QM the OSLC representation of the QM artifact contains the link to the RQM Reportable REST URL.

So to get from the OSLC URL to the Reportable REST URL you firsy need to access the OSLC resource, read the Reportable REST URL and then accesses the data there.

How QM linking works – TL;DR version

When you want to access linked QM data you need to:

  1. access the OSLC representation of the artifact
    • you need to use RPE’s Reportate REST v2 schema discovery to find the schema form QM’s OSLC representation. The starting point for the schema discovery process is https://server:port/qm/oslc_qm/catalog
  2. read the URL to the Reportable REST representation of the QM artefact
  3. access the Reportable representation of the artefact
  4. Use the data as needed

Suggested reading:

  1. RQM OSLC v2 REST API – for linking data
  2. RQM Reportable REST API – for document generation

Get linked QM Data from DM

  1. Insert the QM_TC_Snippet.dta in the indicated position
  2. Edit the condition on the QM Container such that you are only processing QM Data. I have used the “link type” property  to only accept “Validated By” links
  3. Connect the QM snippet to your template by specifying
    1. A data source to have the QM_OSLC_TC inherit from
    2. The data property that holds the OSLC QM URL
  4. Make a test run to verify all the pieces fit together. Just like with the RTC example you only need to specify the entry point and credentials for accessing the DM UML project.

NOTE: You will need to replace the QM schema from my snippet with your particular QM schema so that you can use the custom attributes defined in your particular QM instance.


You now have 2 RPE snippets for accessing RTC and QM linked data that you can reuse in your traceability documents. I recommend evaluating your existing templates to identify other sections in your templates that you use on a regular basis and transform them in reusable snippets.

RPE and DOORS Web Access

I’m writing this as a response to what seems to be a surge in interest for reporting on DOORS 9 data through the DOORS Web Access, or DWA. This integration is documented in the RPE Infocenter here and on my blog here.

The main point of this article is the scope and limitations of this integration. The RPE-DWA has been added to support exclusively traceability reports  that start from other products (ex: RQM) and use DOORS 9 requirements through DOORS’ OSLC API. As such the RPE-DWA integration is only meant to support retrieving a single requirement at a time through it’s DWA URL.

For all and any scenario where multiple requirements are needed, such as getting the content of a module/view, the traditional DOORS 9 route is the only supported method.

As a rule of a thumb you should you should never use DWA as the starting point for a report. These URLs must be obtained dynamically from other data  sources in your report.

It has to be noted as well that the DOORS OSLC API is not reportable which has two main implications for RPE and document generation. First this API lacks support for OLEs and images which means that only text content will be served correctly. Second there is no XML schema provided with the API (there is not a ?metadata=schema URL) nor there is a way to “discover” such a schema as we have for DOORS 9. The DWA example schema we have provided has been created manually from instances of the data.

To summarize the above for all scenarios other than the one explicitly stated above the RPE-DWA integration is not a viable nor is a supported alternative to the traditional RPE-DOORS 9 integration.