Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

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:

  1. Navigate to the <tomcat-home>\webapps\prweb\WEB-INF\classes directory.
  2. Open the prlogging.xml file.
  3. Locate the "appender" definitions section that contains the "@{web.tmpdir}" string
  4. 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.

Required Oracle optimization parameter

Valid from Pega Version 7.1.3

To optimize performance, set the Oracle parameter optimizer_index_cost_adj to a value between 20 and 25. If this value is not set, the system can run exceedingly slowly, potentially blocking users from login.

Slow WebSphere performance on Mac platforms

Valid from Pega Version 7.1.2

Use the following JVM setting to improve WebSphere performance on Mac platforms:

-Djava.net.preferIPv4Stack=true

Synchronized database and application server settings

Valid from Pega Version 7.1.3

Configure your database and application server to use the same time zone and character encoding to avoid conflicts.

Extract data from Pega Cloud to an on-premises database

Valid from Pega Version 7.4

You can now use Pega® Business Intelligence Exchange (BIX) to extract data from Pega Cloud to an on-premises relational database management system. Extracting data from Pega Cloud directly to an on-premises database improves efficiency by eliminating the need for file extraction and the development of a file extraction infrastructure.

For more information, see Extracting data from Pega Cloud to an on-premises database.

Improved connection pooling performance

Valid from Pega Version 7.4

HikariCP is now used for connection pooling for databases that are configured by using a URL. HikariCP improves connection pooling performance; however, more database connections might be used than in previous versions of Pega® Platform.

As a result of the switch to HikariCP, you cannot use the System Management Application (SMA) to get diagnostic data from your application. For instructions about how to get diagnostic data by using REST services, see Obtaining connection pool diagnostic data by using REST services.

System state data is saved for 90 days

Valid from Pega Version 7.4

System state data is now saved to the database for 90 days and can be downloaded as a JSON file. Having previous system state data available is useful for debugging system problems. Operators with the pzSystemOperationsObserver privilege can download system state data from the Cluster Management landing page for either the entire cluster or a single node. In addition, the PersistClusterState and PersistNodeState agents have been added to the Pega-RulesEngine ruleset for persisting system state data to the database.

For more information, see Downloading the system state.

Node classification replaces NodeID-based configuration

Valid from Pega Version 7.4

For simpler cluster administration and better application resiliency, Pega® Platform is moving toward a node classification model. Although agents will continue to work by using NodeIDs for several upcoming releases, use node types instead of NodeID configuration for agents, listeners, and decisioning services for more efficient operations and upgrades.

For more information, see Node classification.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us