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.
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.
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
When DNG’s “Generate a document style report” feature misbehaves you should go through the following actions:
check rrdg.log for additional information. The log file is location is <SERVER_INSTALL>\server\logs\rrdg.log.
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.
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.
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 18.104.22.168 with DNG 4.0.6