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.
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
Split schema systems require additional privileges
Valid from Pega Version 7.1.2
On Oracle split schema systems, add the following database privileges:
- Grant DROP ANY INDEX to the Admin User.
- Grant UNLIMITED TABLESPACE to the Rules User.
Use the Oracle Enterprise Manager to add these privileges or refer to the 7.1.3 Upgrade and Installation guides for Oracle.
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.
No longer supported translator configuration options
Valid from Pega Version 7.4
The following translator configuration options are not needed and are no longer supported. If you previously configured any of these system settings, remove them from the system settings to avoid a warning message. For example, if you set translator/useparserfamily, the following message is displayed at startup: "Translator option, 'translator/useparserfamily' is not needed and no longer supported. Remove this from the system settings."
- translator/useparserfamily
- translator/usecodegenerator
- translator/usenativedouble
- translator/optimization/use71BlockAnalysis
- translator/optimization/use71ConstantFolding
- translator/optimization/use71AssignmentTypeSimplification
- translator/optimization/use71IntrinsicFunctions
- translator/use71PropSetGeneration
- translator/use71ParserAssignment
- assembly/model/useBlock4ContiguousSets
- /translator/pandc/comparepandcalgorithms
- /translator/pandc/use6xalgorithms
- /Compatibility/CheckForTopLevelClassMismatch
In addition, the com.pega.pegarules.generation.parseoverride bootstrap option is no longer supported. Remove this option from the system settings.
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.
PegaDATA connection settings now required in the prconfig.xml file
Valid from Pega Version 7.4
If you use the default prconfig.xml file that is included with Pega® Platform, and you have not removed the PegaDATA connection settings, no action is required. If you use a custom prconfig.xml file, for example, for running tests, ensure that the database connection settings for PegaDATA are not blank.
For more information about the connection settings, see PegaDATA connection settings in the prconfig.xml file.
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.