3 minute videos

We’ve recorded a number of short videos showing how to deploy RPE. They are just long enough to keep you entertained while boiling eggs for breakfast.

 

Advertisements

How to troubleshoot document generation in DNG

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.

rdng_rrdg_logs
Click to enlarge

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.

Changing the log level is done in the logger configuration page https://server:9443/rm/logs/config by setting the INFO/DEBUG level  to the com.ibm.rational.rrdg logger

rdng_rrdg_logs_configure
Click to enlarge

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.

doors2rqm_output

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”

A 4 step install guide for RPE 2.0.1

This post is a TL;DR version of it for Liberty and Tomcat. The installation procedure for the RPE WebServices 2.0 is described in detail in http://www-01.ibm.com/support/knowledgecenter/SS6RHZ_2.0.1/com.ibm.rational.pe.install.doc/topics/c_web_rpeng.html

RPE 2.0.1 Login Screen
RPE 2.0.1 Login Screen

 

WAS  Liberty Profile

Apache Tomcat

Ensure the TELELOGIC_LICENSE_FILE environment variable is set and points to a RPE license server.
Copy com.ibm.rpe.web.app.ear from %RPE_HOME%\remote-services into the apps folder of your Liberty server Copy rpeng.war and dgass.war from %RPE_HOME%\remote-services into the webapps folder of the Tomcat server
Ensure the JSP and Auth features are enabled for the Liberty server. Add the required users and roles for RPENG. See the example server.xml.  Add users and roles for RPENG. See the example tomcat-users.xml.
Start Liberty and navigate to  http://<server&gt;:9080/rpeng/home Start Tomcat and navigate to http://<server&gt;:8080/rpeng/home

Trouble shooting

  1. Examine rpeng.log and rpedgaas.log in %TEMP% folder
  2. Clear browser cache. This is mandatory when upgrading from 2.0 to 2.0.1
  3. Admin page – list of failed jobs
  4. View page – job details

More traceability – following links from RQM

Continuing the series of articles on producing traceability documents from IBM CLM I will describe today how to follow links from RQM.

If you examine the RQM schema for testcase for example you will notice entries for workitems and requirements.

qm_schema
Click on the image to enlarge it.

With these properties it should be fairly straightforward to build a template that retrieves CM and RM data associated with the QM artefacts.

However if you run your report on a test case feed URL like https://giediprime:9443/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/JKE Banking (Quality Management)/testcase?abbreviate=false there is no requirement or work item data in the document. And if you examine the XML returned by RQM for this request you will see that information is not present there either.

So what is the problem? The answer is in the Rational Quality Manager Reportable REST API Documentation.  For efficiency reasons RQM does not return the link information by default. If you want to create traceability documents you’ll have to explicitly ask for the link information using the calmlinks argument in the request URL.

qm_calm_links
Which means that the right URL to use in the RPE docspec will look like this https://giediprime:9443/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/JKE Banking (Quality Management)/testcase?abbreviate=false&calmlinks=true

Note that the URLs to RTC and DNG are OSLC links and you will need to convert them to Reportable REST API URLs before fetching RM and CCM data.

Examples showing how to follow links from individual testcase or from a test case feed are available in the RPE DevWorks – Cross Domains Templates Wiki.