System category — Settings page
Resource URLs, Compiler, Security Policies, System Name and
Project Management tabs

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/prsysmgmt. 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. 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 tab has three sections: Index Administration, Agent Administration, Index Host Node Settings.

Use the Index Administration settings to enable or disable indexing for classes under Rules-, Data-, and/or Work-.

Through a checkbox labeled Exclude this class from search? on the Advanced tab of the Class form, you can cause full text searching to skip over instances of a specific class. Search results then exclude any instances of that class.

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. Enable this capability only if your applications provide full-text searching of work objects. In a production system, building and maintaining search indexes for work objects is typically more costly in performance impact than building and maintaining search indexes for rules or data instances. Work object search is not available in the Designer Studio portal. Indexed number of work items appears to the right of the button in green. Index File Size of recently indexed work items. 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 item attachments. PDF, Microsoft Office, and text attachments are indexed and will be full-text searchable. However, if your application saves work item file attachments in an external enterprise content management system accessed through Connect CMS rules, such file attachments are not included in PRPC 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 item.

You can check or clear any of the boxes above while a PRPC 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 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 tab. During installation or upgrades, the help index file is automatically extracted from a binary file rule named HelpIndex.pxHelpIndexBinary.zip.

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

In a multinode cluster system, the indexes that support search may be maintained only on one node. When a user connected with another node performs a full text search, an HTTP service request is sent from that node to the node with indexes. The search results are returned to the requesting node and displayed to the user.

Messages pertaining to search indexing appear in this area.

The Security Policies tab is visible to operators who have the pzViewAuthPoliciesLP privilege in their Access Roles. This privilege is part of the role PegaRULES:SysAdm4.

The tab controls the appearance and functions of a CAPTCHA, a test that verifies that a human, not a computer process, is attempting to log in or change an operator password. The user must enter the characters that appear above an image that makes it difficult for a machine to read the characters. If you cannot read the characters, click the Refresh button to get a different image and character set.

A CAPTCHA may appear on the login screen when the user first attempts to log into the system from a given computer or after an authentication failure, and on the password-change screen. The goal is to counter "brute-force" automated attacks on system security.

The tab offers a checkbox, a button, and a series of settings that allow the operator to fine-tune CAPTCHA behavior. Each setting has default, minimum, and maximum values.

Check the Enable Security Policies checkbox to enable the settings the tab displays. Uncheck the checkbox to prevent the CAPTCHA functions from operating.

Click Display Audit Log to display the log that can record login attempts. Audit log behavior is governed by The Audit log level policy setting, described below.

A Report Definition report displays the "Security Audit Log" report, with a default filter to display all audit events (the filter is set to ".pxCreateDateTime is Less or Equal to Current Month"). Click the link to the right of "Filters in the report header to adjust the date range.

For each logged event, the log captures:

• Create Date/Time — the time of the attempt.
• Remote IP Address — The IP address of the system from which the attempt was made.
• Remote Host — The name of the computer involved.
• User Name — The operator ID used in the login attempt.
• Message — The status message returned during authentication of the login.
• Browser (User-Agent) — HTTP Request Header "User-Agent".
• Referrer — HTTP Request Header "User-Agent".
• Via — Records proxies through which the request was sent.

Click View History to see a report of changes to security settings, including the date, the operator who made the change, and what change was made.

You can set the following policies:

For an example, see PDN article 26428 How to configure login security and password policies.

More advanced customizations are possible. See PDN article 26451 Customizing CAPTCH presentation and function.

Use this page to change the System Name of your PRPC system. A PRPC 'system' in this context is all PRPC instances (nodes) that share a single database and the same system name. When you use this page to change the system name, PRPC clones the current system name record, the node name of the other nodes in the system that use the current name, and all associated Data instances that reference this name and applies the new system name.

If your organization has multiple PRPC systems, it is a best practice to set a distinct system name for each of the systems. For example, you may want to distinguish between development, test, UAT and production systems. When you create, or update a rule or a data instance, the current system name is added to the History tab. When you import a ZIP archive containing a rule or data instance, the system name is on the History tab (which may be the source system on which the ZIP archive was created). Using distinct system Names can help identify the source systems when rules or data objects are moved from one system to another.

To change the system name,

1. Enter the new name in the New Name field. Enter a System Name that starts with a letter and contains only letters, digits, and the underscore character, no longer than 32 characters.

   By default the system name is pega.

   The system names prpc and iwm are reserved; do not use except as advised by Global Customer support.

2. Click Submit

   PRPC makes an exact copy of the current system name record, the node name of the other nodes in the system that use the current system name and all associated data instances, including requestor type data instances (Data-Admin-Requestor class), the Dynamic System Settings indexing/hostid, and applies the new system name. PRPC also updates any listeners with the new Node IDs.

3. Restart all nodes in the system.

   The table All Affected Nodes on the System Name page lists the nodes whose name will be changed by this action.

   If the Required Action column for a node is Update prconfig.xml and Restart you must update the prconfig.xml file entry Identification/SystemName for that node to reference the new name before restarting the node. For example:

   <env name="Identification/SystemName" value="mycoProd" />

   Complete this step for each node.

When the system starts with the new name, it creates new Agent Schedule instances for each node. Review these new instances and update, if necessary, the access group (on the Security tab) to match the value in the older Agent Schedule instance.

See also:

• System ID — definition
• Atlas — Standard Dynamic System Settings

Use this tab when you have an instance of the Project Management Framework to set up the URL connections between applications and the framework, test that connectivity, and enable project tracking for operators who perform development work in the applications they can access.

Field	Description
Connection Details	Section of the tab where you set the value for URLs that establish connectivity between your application and the Project Management Framework and then test the connection.
PMF URL	The URL for your framework instance; populates the Data > Admin > System > Settings > ProjectManagementURL instance when you click Save.
PMF SOAP URL	The SOAP URL that passes project tracking data to/from an application to the framework instance; populates the Data> Admin > System > Settings > ProjectManagementFW instance when you click Save.
Test Connectivity	Click to test that the PMF SOAP URL connects to the framework. A Connection Successful message displays if connectivity is established; an error message displays if not.
Save	Click to save the URLs and update the corresponding Data Admin System Settings rules.
Application Project Settings	Expandable section of the tab where you enable and disable project tracking for applications you can access.
Application (Version)	The applications and versions you can access. appears next to the application name if the application is locked and requires a password to enable.
Project Tracking Enabled	Check the box to enable project tracking for all operators who have development access to the application. Uncheck the box to disable project tracking.
Save	Click on a row to save that application setting and update the corresponding PMF Integration value displayed on the Application Overview Landing page and Enable Project Management field in the Application rule.
Supply Password	Appears in a pop-up window when you click if the application is locked. Enter the password and click OK to continue the save action.