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. |
|
Cannot generate documents from IBM Rational DOORS® data sources |
|
Cannot generate documents from IBM Rational Tau data sources |
|
Cannot run Microsoft Word macros |
|
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.
|
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:
|
|
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. |