Common problems

Some of the common problems that you may face while using IBM® Rational® Publishing Engine are listed along with its resolutions.

The following table lists the problems and its resolution.

Problem Resolution
Rational Publishing Engine does not start.
  • Check that the Rational Publishing Engine installation is not corrupt and that the JRE folder exists.
  • Check arguments in rpe-studio.ini and rpe-launcher.ini files from the studio and launcher folders and edit the following values.
  • vmargs
  • Xms56m
  • Xmx1024m
Lowering these values should help start Rational Publishing Engine on low resource machines or on Virtual Machines.
  • vmargs
  • Xms56m
  • Xmx512m
Cannot generate documents from IBM Rational DOORS® Data Sources
  • A Rational DOORS V9.1 or later client must be installed
  • Check that the data source is properly configured ( the module path, view name and baseline are case sensitive)
Cannot generate documents from IBM Rational Tau Data Sources
  • A Rational Tau V4.2.0.1 or later installation must be available
  • The path to Tau bin folder must exist in the PATH system variable
  • Check that the data source is properly configured
Cannot run Word macros
  • Microsoft Word needs to be installed
  • The macro must be defined in the stylesheet
Object Linking and Embedding (OLE's) are not displayed and macros are not run in the in the Microsoft Word output, when Rational Publishing Engine runs on remote engine (web services).

When Apache Tomcat is executed as an NT Service, it is not possible to run macros during Rational Publishing Engine remote engine generation on a Microsoft Windows 2008, 64 bit machine.

Cause: Microsoft does not support office automation without a Graphical User Interface.

Environment: Microsoft Windows 2008, Microsoft Office Word 2007.

  • On Microsoft Windows 2008 64 bit, create the folder Desktop under the location C:\Windows\SysWOW64\config\systemprofile
  • On Microsoft Windows 2008 Server x86, create the folder Desktop under the location C:\Windows\System32\config\systemprofile

See here for more information.

Debugging REST data sources In a web browser, enter the URL displayed by Rational Publishing Engine in its log view. If no errors occur, check if the content of the XML file is correct. (if the file contains all the data in a format matching the schema). The support teams can speed up the problem identification process using the .xml file saved from the browser.
Cancelling of a document generation process may not always be acknowledged Canceling a document generation ( local or remote) might not always be acknowledged by Rational Publishing Engine. Even if the progress dialog is cancelled, the output documents are successfully generated. This is because Rational Publishing Engine checks for the cancellation signal only at specified intervals. If the document generation job is small (few input elements) the cancel signal might not be checked by Rational Publishing Engine. This will not be an issue in most cases due to the size of the generated documents.
In a scripted filter/condition, when the left operand and right operand of a condition are from same attribute name, but belong to two different queries, the condition will not work. You have to set different aliases for the two attributes for the condition to work.

Cannot initialize TAU JAVA API in a scenario where the document generation is using Rational Publishing Engine web services on WAS (6.1 fixpack 35) with TAU as data source.

  • Ensure the path to tau bin is defined in the env variable or add the path and restart the WAS server.
Rational DOORS 9.x is not in secure mode but Rational Publishing Engine throws errors

Some examples of the errors are as follows:

  • "E- DXL: <Line3>could not open include file (source/DOORS/dxl/schema discovery/const.inc) (No such file or directory)"
  • -E- DXL: <D:\CAx\Rational\Publishing Engine\1.1.1.2\source\DOORS\dxl\doors driver\getDOORSVersion.dxl:>could not open include file (source/DOORS/dxl/doors driver/getDOORSVersion.inc) (No such file or directory)
  • Check if Rational DOORS is using command line arguments that override the add-ins path. If "yes" then either add the path to Rational Publishing Engine installation or copy the Rational Publishing Engine source folder to the path pointed by the add-ins command line flag.
  • Check if HKEY_CURRENT_USER\SOFTWARE\Telelogic\DOORS\9.3\Config\addins exist as that value overrides the HKEY_LOCAL_MACHINE\SOFTWARE\Telelogic\DOORS\9.3\Config\addins set by Rational Publishing Engine. If the HKEY_CURRENT_USER value exists add the path to the Rational Publishing Engine installation in it.
Rational Publishing Engine Client times out when creating complex document specification that are configured to use a remote publishing engine Increase the timeout value for the client.

Add the following parameter to the rpe-launcher.ini and rpe-studio.ini files, where newValue is the timeout setting in milliseconds: -Dcom.ibm.rational.rpe.wstimeout=newValue

In Rational Publishing Engine 1.1.2 and earlier, the default timeout value is 10000 milliseconds. In releases Rational Publishing Engine 1.1.2.1 and later, the default timeout value is 30000 milliseconds.


Feedback