Common issues

Review some of the common issues that you might experience while using IBM® Rational® Publishing Engine and find troubleshooting suggestions.

For information about determining which output type to use for a template elements you are using, see Specifying output properties.

Issue Troubleshooting suggestion
Rational Publishing Engine client does not start.
  • Verify that the Rational Publishing Engine installation is not corrupted.
  • Verify that the Java Runtime Environment (JRE) folder exists in the correct location.
  • Review the arguments in rpe-studio.ini and rpe-launcher.ini files from the studio and launcher folders. Try changing the values for the following arguments:
    • vmargs
    • Xms56m
    • Xmx1024m
  • If you are using a computer that is low on disk space or you are using a virtual machine, you can decrease the values for these arguments:
    • vmargs
    • Xms56m
    • Xmx512m
Cannot generate documents from IBM Rational DOORS® data sources
  • A Rational DOORS V9.1 or later client must be installed.
  • Confirm that the data source is properly configured. Remember that the module path, view name, and baseline are case-sensitive values.
Cannot generate documents from IBM Rational Tau data sources
  • Confirm that Rational Tau V4.2.0.1 or later is installed.
  • Confirm that the filepath to Tau bin folder is listed in PATH system variable.
  • Confirm that the data source is properly configured.
Cannot run Microsoft Word macros
  • Ensure that Microsoft Word is installed.
  • Verify that the macro is defined in the style sheet.
Object Linking and Embedding (OLE) does not display and macros do not generate the Microsoft Word output when Rational Publishing Engine runs on the web services remote engine.

When Apache Tomcat is executed as an NT Service, you cannot run macros during Rational Publishing Engine remote engine generation on a Microsoft Windows 2008 64-bit computer.

Environment: Microsoft Windows 2008, Microsoft Office Word 2007.

Microsoft does not support office automation without a graphical user interface.

  • On Microsoft Windows 2008 64 bit, create the folder Desktop in the directory: C:\Windows\SysWOW64\config\systemprofile
  • On Microsoft Windows 2008 Server x86, create the folder Desktop in the directory: C:\Windows\System32\config\systemprofile
See Excel 2007 automation on top of a Windows Server 2008 x64.
Debugging REST data sources In a web browser, enter the URL displayed by Rational Publishing Engine in the log view. If no errors occurred, review the content of the XML file to verify that there are no errors and that the data format matches the schema data format.

If you call IBM Support, save the .xml file to help them identify the problem.

Canceling of a document generation process might not always be acknowledged Canceling a local or remote document generation might not be acknowledged by Rational Publishing Engine. Even if the progress dialog is canceled, the output documents generate successfully. This issue occurs because Rational Publishing Engine checks only at specified intervals for the cancelation signal. If the document generation job is small and has few input elements, the cancel signal might not be checked by Rational Publishing Engine.
In a scripted filter or condition, when the left operand and right operand of a condition are from same attribute name, but belong to two different queries, the condition does not work. You have to set different aliases for the two attributes for the condition to work.
Cannot initialize Rational Tau Java API in a scenario where the document generation is using Rational Publishing Engine web services on WebSphere® Application Server 6.1 fix pack 35 with Rational Tau as data source. Ensure the path to the Rational Tau bin is defined in the env variable. If the path is not specified, add the path and restart the WebSphere Application Server server.
Rational DOORS 9.x is not in secure mode but Rational Publishing Engine displays errors such as:
  • "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)
  • If Rational DOORS is using command-line arguments that override the add-ins path, 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.
  • See if the environment variable HKEY_CURRENT_USER\SOFTWARE\Telelogic\DOORS\9.3\Config\addins exists. If that environment variable exists, it overrides the HKEY_LOCAL_MACHINE\SOFTWARE\Telelogic\DOORS\9.3\Config\addins environment variable set Rational Publishing Engine. In the HKEY_CURRENT_USER value, add the path to the Rational Publishing Engine installation.
Rational Publishing Engine Client times out when creating complex document specifications 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.

Templates that include filtered elements cause the output generation to perform slowly If you are using Rational Publishing Engine filters in your template, Rational Publishing Engine is processing the data from the integrated product. Instead, use native filters to reallocate the filtering work to the data service adapters rather than Rational Publishing Engine.
Tables do not fit to the page. The autofit to window has no effect. If you set the resize to fit contents property for a table element in a template to false, then autofit to window property is ignored. Set the resize to fit contents to true to use the autofit to window property.

Feedback