System category — Settings page
Resource URLs, Compiler, and Search gadget

Complete these three URLs as follows. Do not use "localhost" as the node name; use the server name or an IP address.

• Online Help URL — Optional. Enter the URL to this help system (which may be deployed on any node), in the form http://nodename:portnumber/prhelp. This value may be set initially during installation.
• Public Link URL — Optional. Used for Directed Web access, typically in the form http://nodename:portnumber/PRServlet. See How to provide external assignments through directed Web access.
• SMA URL — Optional. Enter the URL to the System Management application (which may be deployed on any node), in the form http://nodename:portnumber/prsysmgt. See About the System Management Application. This value may be set initially during installation.

Click Submit to save these changes into the corresponding Dynamic Systems Settings data instances. Log out and log in again, or wait up to 10 minutes, for the new values to be available in this server. See Atlas — Standard Dynamic System Settings.

Optionally, complete two fields to make information available to the Java compiler on your system:

• Default paths — The list in this field supports Service Java rules and other handcrafted Java code. B-19195 Enter a list of jar files, separated by semicolons, that are added to the compile-time classpath for the compiler used to compile the generated Java. This allows service activities to call the classes in external JAR files.
• Default classes — The list in this field supports Service Java rules and other handcrafted Java code. Enter a list of Java classes that are added to the compile-time classpath for the compiler used to compile the generated Java, separated by semicolons. This allows service activities to call such classes.

The Search gadget is divided into three sections: Index Administration, Agent Administration, Index Host Node Settings.

Use these settings to enable or disable indexing for all classes under Rules-, Data-, and/or Work-.

Field	Description
All Rule-, Data- and Work- Classes	Turn on/off all search indexing.
Rules	Turn on/off search indexing for all Rule- classes.
	Click Re-Index to build or rebuild indexes for rules. Indexed number of rules appears to the right of the button in green. Index File Size for current Rules- index files. Last Updated lists month, day, and year of the best index update. Rules created after this date, and rules changes made after this date, will not appear in search results.
Data	Turn on/off search indexing for all Data- classes.
	Click Re-Index to build or rebuild indexes on Data- class instances. Indexed number of data instances appears to the right of the button in green. Index File Size for current Data- index files. Last Updated lists month, day, and year of the best index update. Rules created after this date, and rules changes made after this date, will not appear in search results.
Work	Turn on/off the Re-Index button to build or rebuild indexes on Work- class instances. Indexed number of work objects appears to the right of the button in green. Index File Size of recently indexed work objects. Last Updated lists month, day, and year of the best index update. Rules created after this date, and rules changes made after this date, will not appear in search results. To enable: Click Submit to save the change. Re-start PRPC. Go back to the Search landing page, and click the Re-Index button next to the Work box.
Index Attachments	Click this checkbox to index work object attachments. PDF, Microsoft Office, and text attachments are indexed and will be full-text searchable. However, if your application saves work object file attachments in an external content management system accessed through Connect CMS rules, such file attachments are not included in Process Commander search results.

Click one of the three Re-Index buttons to rebuild the complete index file for the selected type. You normally only need to perform these actions following initial installation, or if the search index files are accidentally deleted or corrupted.

Perform these one at a time; each starts processing that may require several minutes to complete. Progress messages appear at the bottom of the page during the rebuild. Each responds with a success message when processing is complete. Additional details and progress messages appear in the system console log. Building or re-building indexes naturally requires reading every rule, data instance, or work object.

You can check or clear any of the boxes above while a Process Commander server node is operating, but such index processing can affect system performance if the indexes are large.  As a best practice, choose a time when the server is down (that is, Process Commander is not available) or is up but less busy to perform these one-time processor-intensive operations. 

The Designer Studio search facility also allows search of Application Developer help topics. The Help search capability depends on a static index and is unaffected by the settings you record in this gadget. During instllation or upgrades, the help index file is automatically extracted from a binary file rule named HelpIndex.pxHelpIndexBinary.zip.

Displays the status of the two indexing agents that incrementally update the search index files as changes are made to Rules-, Data-, and/or Work- instances and also provides Start and/or Stop buttons to manually enable or disable these agents.

Messages pertaining to search indexing appear in this area.