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 … Continue reading “RPE Java API example built for 1.2.1”
RPE ships with an example application built on the java API. The source code for the application is found in %RPE_HOME%\lib\api\examples\com.ibm.rational.rpe.examples.zip
One of the key aspects in creating a successful report with RPE is a good understanding of the problem domain and the reportable API used. Guess working your way while creating the template relying only on the schema information can be a very frustrating process.
RPE 2.0 can use old templates and document specifications created by all previous RPE versions. New templates and document specifications created with RPE 2.0 can be used by RPE versions 1.3.x and 1.2.x. In both cases the output for 2.0 and the output from the older RPE release may be different given the defect fixed … Continue reading “RPE 2.0 Compatibility”
There are 3 IBM provided ways of producing documents from DOORS 9 using RPE: RPE Launcher DOORS Publish Wizard RRDG based File->Export NOTE: I have listed only solutions provided by IBM. There are other RPE based solutions provided by IBM partners such as GebsReporting, Baselines Inc, River North Solutions and more.
Update 2015.02.03: another cause for a slow Launcher/Studio start is an invalid RPE WebService URL. Check your ini files to determine if the -Dcom.ibm.rational.rpews.url is set and verify the URL is correct and accessible. If RPE Launcher/Studio take more than a few seconds to start it is possible that your license configuration is sub-optimal. A … Continue reading “Troubleshooting slow RPE Launcher/Studio start”