Troubleshooting
— Development tools
|
|
Operation of the Find Content features of the Advanced Search tool depends on index files defined through Dynamic System Settings rules and initially generated through the System Management application. Thereafter the indexes are updated automatically during system pulse processing. In a multinode cluster, standard SOAP services access the index files, which area stored on a single node.
If your search results appear to be incomplete, use the System Management application to confirm that the Pega-RULES agent executes the system pulse processing regularly.
See Understanding the Find Content Search facility.
The Tracer has a fixed buffer to hold traced events that it has not processed. In some complex tracing situations, this limit is reached and the Tracer discards additional arriving events. A message appears:
Event queue is overflowing on server, events will be discarded.
To avoid this limitation, select fewer RuleSets or event types and then repeat the operation to be traced.
Installation of a new JVM version on the server after
Process Commander is installed can interfere with the operation
of the Clipboard tool. See the Pega Developer Network article
PRKB-15992 Troubleshooting: Clipboard
tool fails after JVM change (Tomcat).
In some WebSphere 6 installations, the default location of
the jaxrpc.jar file can interfere with the
Clipboard tool operation. This file can be removed or moved;
Contact Pegasystems Global Services for a remedy.
The Application Documentation tool depends on a Microsoft
Dynamic Linked Library file MSXML.DLL that has
limitations and known issues. If the generated Word document
appears incomplete or incorrect, try these troubleshooting
tips:
MSXML.DLL dynamic library from Microsoft .For technical information about the
XMLHTTPRequest DOM object supported by MSXML.DLL,
see the following Microsoft Knowledgebase article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;237906.
On IBM WebSphere 5.1, the Rules Inspector may fail unless an IBM patch (5.1.1.4) is applied.
If help links are not working, check to confirm that the Application Developer help system is installed and started. The help system is an optional Web application.
Verify that the URI path to the help system, recorded in a Dynamic System Settings data instance named Pega-ProCom.ProComHelpURI, is correct. Changes to Dynamic System Settings rules take effect when you next log in.
If the System Management application cannot be started, check to confirm that the war file was installed. This is a Web application.
Verify that the URI path to this application, recorded in a Dynamic System Settings data instance named Pega-ProCom.SystemManagementURI is correct. Changes to Dynamic System Settings rules take effect when you next log in.