Tomcat log files moved to work directory
Valid from Pega Version 7.1.2
For Tomcat application server users, the default path for PRPC logs has been changed to the "work" directory for Catalina. For example:
<tomcat>\work\Catalina\localhost\prweb
This directory can be cleaned up during administration. To avoid loss of files, you can redirect logging to a different directory after installation:
- Navigate to the <tomcat-home>\webapps\prweb\WEB-INF\classes directory.
- Open the prlogging.xml file.
- Locate the "appender" definitions section that contains the "@{web.tmpdir}" string
- Update the FileNamePattern values to point to the new directory.
For more details, refer to the “Change the default path to PRPC logs” section in the Tomcat installation guide for your database.
Real-time pulse processing for multinode systems
Valid from Pega Version 7.1.9
Multinode development environments now use real-time pulse processing. Previously, when a change was made on one node, the pulse processing interval could take a minute or more for that change to be reflected on another node. Now, when a rule is changed on one node, that change is immediately reflected on all the other nodes in the cluster. This change helps to ensure that users are running a rule on the same node as where the rule was changed.
Verifying that a Pega 7 Platform instance is running
Valid from Pega Version 7.1.9
You can verify whether a Pega 7 Platform instance is up and running by entering this URL: http://<<hostName:port/contextName>>/PRRestService/monitor/pingservice/ping
The Pega 7 Platform Engine responds with HTTP Response Code 200 if the instance is available. The response contains JSON text in the format { "duration":"<time in milliseconds>" }. Any other response codes or timeout indicate that the instance is unavailable.
Enabling historical compliance score data
Valid from Pega Version 7.1.9
Project stakeholders can now track the compliance score for an application over time to better understand and manage ongoing development adherence to Pega 7 Platform guardrails. The compliance score history can be displayed on a line graph on the Compliance Score tab of the Application Guardrails landing page. The data is collected daily and displayed in weekly increments, up to four weeks prior to the current date.
For more information, see Guardrails compliance score, Enabling compliance score history, and Compliance score trend reporting.
Application Sizing Wizard worksheet template now includes business impact
Valid from Pega Version 7.1.9
A column for business impact has been added to the project sizing template used by the Application Sizing Wizard. Project owners can now incorporate this assessment into their project sizing.
New Business impact optimization dashboard
Valid from Pega Version 7.1.9
On the Analysis tab of the Application Profile landing page, you can now enable historical specification count and implementation progress by complexity and business impact. On the Business impact optimization dashboard, you can view counts of specifications by complexity and business impact. You can also view counts, by business objective, of specifications that have been implemented and for those not yet implemented. You can filter specifications by release and iteration.
For more information, see Viewing specifications by complexity, impact, and business objective, and Associating project specifications with business impact and complexity.
Database storage used for passivation in High Availability mode
Valid from Pega Version 7.1.9
When an application is running in High Availability mode, the value attribute for initialization/persistrequestor/storage in the prconfig.xml file or the Dynamic System Settings now defaults to "database."
Previously, applications running in High Availability mode required shared passivation, where either initialization/persistrequestor/storage was set to “OnTimeout” or a custom passivation mechanism was used. The change to using database by default provides persistent storage for passivation, and provides control for the landing page for High Availability.
For more information, see Understanding passivation and requestor timeouts and the High Availability Administration Guide.
Enhanced date circumstancing option
Valid from Pega Version 7.2
The date range and as-of date circumstancing features have been merged into a single feature called date circumstancing. Accordingly, the new Property and Date circumstancing option provides more flexibility when you circumstance a rule. For more information, see Specializing a rule.
Renaming a system creates the required data requestors
Valid from Pega Version 7.2
When you rename a system, either from the System Name landing page or by updating the prconfig.xml file, any missing data requestors are automatically created by the Pega 7 Platform. The Data Admin System Setting is also created, if it is missing.
Configure Elasticsearch index nodes to ensure availability of index files
Valid from Pega Version 7.2
You can now configure Elasticsearch index host nodes in a Pega cluster outside of the Search landing page. This change ensures that search index files are always available by eliminating the need for manual configuration on the Search landing page. Use the new index.directory=<index_directory> command-line setting during JVM startup to indicate that this node is an index host node and to specify the directory where the index files will be hosted.
In addition, offline Elasticsearch index nodes can now be removed by using a new prpcUtils command-line option. For more information, see Managing Elasticsearch index host nodes outside of the Search landing page.