DOORS and DOORS Next Generation Enlightenment Series 2016

I’ve received this from Nancy Rundlet and I’d like to share it here. I’m glad to see that at least one of the sessions will cover document generation with RPE.

We are very pleased to announce the DOORS and DOORS Next Generation Enlightenment Series  for April through June 2016.

Each month, the DOORS Next Generation webinars will be held on the 1st Thursday, and DOORS 9.x will be on the 3rd Thursday at  11:00 AM ET (8:00 AM PT).  Details with abstracts and registration links for each of the webinars are in the attached Word Document or you can register by clicking on the registration link below.

The abstracts for the session are provided in the attached document. DOORS Abstracts Q2 2016

Date Webcast series –  Thursday 11:00 ET for approximately 1 hour        DNG on 1st Thursday and DOORS 9.x on 3rd Thursday Speaker Registration Link
3/17/2016 Creating Traceability in DOORS and Beyond – The Various Methods Jim Marsh, IBM Register

4/7/2016 Importing and Exporting with DOORS Next Generation Carlos Ramirez, IBM Register

4/21/2016 An Automated Method for Collecting Metrics Kori Haynes, Crane Aerospace Register

5/5/2016 Exploring Navigation in DOORS Next Generation Ed Gentry, IBM Register

5/19/2016 DOORS 101: An Introduction to DOORS 9.6 Rick Learn, IBM Register

6/2/2016 Rational Publishing Engine (RPE) for Custom Reports Across the Lifecycle (DNG, RQM, and Rhapsody) Don Cunningham, IBM Register

6/16/2016 Customizing DOORS and Web Access to Speed up Reviews and Save Lives Cliff Sadler, Brockwell Technologies (US Army) Register

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

Rational DOORS Enlightenment Series

The http://ibmfederal.us/DOORS-Enlightenment/ offers a large number of recorded webinars on DOORS 9 and DOORS Next. To highlight just a few:

  1. Understanding Search, Queries and Views in DOORS Next Generation
  2. Data Migration from DOORS to DOORS NG
  3. Requirements Configuration Management — Product Line Engineering
  4. What’s New for Reporting and Document Generation
    (Supporting in DOORS and DOORS NG)

You can access these and you can register for upcoming sessions on http://ibmfederal.us/DOORS-Enlightenment/.

One more technique for debugging DNG document generation

In addition to the methods described in Troubleshooting DNG document generation with RRDG there is one more technique you can use to debug document generation in DNG: replicate the DNG document generation in a standalone RPE installation but the using RPE templates deployed on the DNG server and the DSX files created by DNG.

NOTE if the RRDG engine in DNG and the RRDG version in your standalone RPE are different the results you obtain in the two environments can be very different. Still this method remains valid and useful to understand the inner workings of RRDG in DNG.

When you use the “Generate a Document-Style report” function DNG will use all the selections you make in the wizard in order to build a document specification ( dsx) which it then passes to DNG. The DSX file are stored in <SERVER_INSTALLATION>\server\tomcat\temp\rrc_reports

Continue reading “One more technique for debugging DNG document generation”

Use Word stylesheets and run macros in DNG

The Word and RPE templates examples used in this article are available in the CLM Templates Page of the RPE DevWorks wiki.
Download…

Using Word Stylesheets with DNG templates

Using Word stylesheets with your template allows you to keep a consistent look&feel and simplify the design and maintenance of the RPE templates.

To use Word stylesheets with the templates deployed in DNG you need to:

  1. use the same name for the stylesheet and the dta file. Use doc extension for the stylesheet
  2. copy the stylesheet in <Server Installation>\server\conf\rm\reporting\initialization\templates\word
    dng_stylesheetLocation
  3. reinitialize the DNG publish service by making a request to https://clmserver:port/rm/publish/initialize

Continue reading “Use Word stylesheets and run macros in DNG”

Troubleshooting DNG document generation with RRDG

When DNG’s “Generate a document style report” feature misbehaves you should go through the following actions:

  1. check rrdg.log for additional information. The log file is location is <SERVER_INSTALL>\server\logs\rrdg.log.
  2. delete/move the rrdg folder located in C:\Program Files\IBM\JazzTeamServer\server\tomcat\temp\rrc_reports\ See this technote for scenarios where this also helps. You do not need to stop the DNG server for this.
  3. create C:\Program Files\IBM\JazzTeamServer\server\tomcat\temp\rrc_reports\rrdg\ if missing and step #2 did not help. You do not need to stop the DNG server for this.
  4. reinitialize the RM Publish Service http://server:9443/rm/publish/initialize

One more thing to be aware of is the UAC Data Virtualization trap.  If you use Document Studio to edit the DNG templates directly in the server installation make sure you run Document Studio.

A problem that I troubleshooted and resolved recently using the above techniques was DNG not running macros on my machine despite everything being in place for that. The rrdg.log gave the first clue:

Continue reading “Troubleshooting DNG document generation with RRDG”

Deploying templates in RRC/DNG

Once you have a report that works well in RPE and produces a great document the next question for a report designer is how to make that template available to the end users. This is especially important for users of Web based tools like DNG/QM/RTC .

The solution is to deploy the RPE template in the point product and have it generated using RRDG.  See RRDGvsRPE for an introduction of RRDG and how it relates to RPE.

The main advantage of deploying RPE templates in point products is that end users do not need to know about RPE, templates, data sources, URI and other technical details. Instead they will use the point product’s reporting UI for docgen, UI that should be more user friendly and use a terminology that is specific to the point product.

NOTE: you do not need to have RPE installed to deploy or use a template in DNG.

This article documents how to deploy an RRDG template that prints the content of a DNG module. The configuration used is  RPE 1.2.1.1 with DNG 4.0.6

Continue reading “Deploying templates in RRC/DNG”