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.
When starting with DNG and document generation or when deploying new reports on the server the RRDG log is an invaluable resource for troubleshooting problems on the RRDG server. As expected the log provides detailed information on errors and additional information including performance data.
All the DNG logs can be access at https://server:9443/rm/logs. The log for document generation is rrdg.log which is located towards the end of the list.
By default the RRDG log is set on WARN level which means only warnings and errors will be logged. This is the recommended setting for most production servers but if you need to troubleshoot document generation you should increase the level and set it to INFO.
If you are using the document generation UI in DNG’s 5.0.x and older to generate PDF documents the default option is to use RRDG’s so called “performance driver“. This driver is legacy and has far fewer capabilities than the alternative “sophisticated formatting” driver.
Considering the performance and quality of the output produced by the “sophisticated driver” you should always use that driver. This is enforced in DNG 6.0 by making “sophisticated formatting” the default option for the PDF output.
In this article I describe how to generate a document with RPE that contains DM resources and their linked DNG requirements. While the example uses DNG as a target the technique is applicable to other CLM sources or even DOORS 9 with slight changes.
Unlike other Rational data sources links are not stored in the representation of a DM resource. This means that if you request the Reportable REST representation of a Package there will be no links inside it. The links are stored separately and access via the the “collaboration/links” Reportable REST URI.
So in order to build a document that contains DM resources and linked requirements you have to perform these 3 steps:
retrieve the DM resource.
retrieve the links for the DM resource
access the linked artifacts
The anatomy of the template reflects these 3 steps:
I will skip step 1 and describe step 2 and 3
#2 Retrieve the links for a DM resource
The links for a DM resource are retrieved from the the collaboration/Link service. The dmResourceID and the dmContextID properties are available in the resource you’ve got at step 1.
Now that you have the link href all you need to do is access the information. Assuming all the links are for DNG text artifacts all you need is to convert the OSLC URL stored in DM to a Reportable REST form using a script like this and then access the DNG data through a Dynamic Data Source.
DNG modifies the Word templates used, specifically the paper size. DNG uses by default the paper size is “Letter” and every time that the publish service is initialized it will update Word templates paper size to “Letter”.
To avoid this behavior you need to remove current value for “publish.PaperSize” property so that the initialize process does not change the paper size set in the Word templates.
“What is the RRDG version in DNG 4.0.6 or 5.0.2 or … ?” This is a very common question we get for RRDG and DNG and this is also the first question one asks when trying to debug a DNG document generation issue or understand what RPE capabilities can be used with that version.