RPE 126.96.36.199 and older allowed in certain circumstances to create invalid queries and invalid data source references ( a property used in a context where it did not exist). This would happen most often when performing copy/paste or when replacing schemas.
The biggest problem is that the 188.8.131.52 and older RPE Studio/Launcher/RRDG would not detect these issues and would load and use these template. The results at run time range from a failed document generation to a document generation that apparently succeeds.
RPE 1.2.1 no longer allow creating corrupted templates and also improves the verification made when a template is loaded. This means that with the added verification RPE Launcher and RRDG will refuse to load corrupted templates. Document Studio allows loading these templates so that you can correct them but warns the user of the detected problems.
This post describes how to use Document Studio to correct these errors.
When reporting a problem via support or asking for help via the RPE Dev Works forum one of the first questions you will be asked is to provide the XML data used for your report. Getting a hold of the XML data is also interesting for testing your templates while avoiding/reducing the need for server requests.
This post describes 3 ways of getting the XML data that RPE uses for the document generation.
RPE ships with an example for using its Java API. See Using the Java API for more information on the RPE Java API and how to use it. Since we ship only the source code for the example before using it you need to build the example using the libraries from the %RPE_HOME%\lib folder. For convenience I’m providing a binary version of this example here.
One of the longest standing wishes for RPE was to be able to generate documents where the Table of Contents and other fields are immediately visible (or calculated). For a very long time this was not possible and macros were required to finalize the documents by updating their fields. With RPE 1.2.1 is now possible to generate documents that have all their content calculated without needing macros.
RPE_1.2.1_Overview is an introduction to RPE’s 1.2.1 main new features, changes in existing features and defect fixes. For more details please check the RPE Infocenter and you can always request for more information on the DevWorks forum.
Late in the 1.2.1 development cycle, several customers identified defects that they encountered in previous versions of Rational Publishing Engine. These issues affected mainly the Document Studio and Rational Reporting for Document Generation (RRDG) components ( and indirectly the RPE Web Service too) and were significant enough to warrant publishing an update immediately after version 1.2.1 was released rather than waiting until the next release. We also took this opportunity to address a number of problems our QA teams discovered in the same time frame.
RPE 1.2.1 comes with a brand new Info Center: http://pic.dhe.ibm.com/infocenter/rpehelp/v1r2m1/index.jsp?re=1&topic=/com.ibm.rational.pe.nav.doc/helpindex_rpe.html&scope=null
The 1.2 version of the Info Center is still available and is valid but it applies to RPE 1.2 and 184.108.40.206 and only contains information relevant to those RPE versions. And similarly the 1.1 version Info center is still available.
Please update your bookmarks and make sure you use the Info center version matching your RPE release.