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.
Additional upgrade scripts for new columns
Valid from Pega Version 7.1.4
In Version 6.2, additional columns (Major, Minor, and Patch) containing ruleset Version information were added to 15 tables in the PRPC database. When upgrading from a pre-Pega 7 release, scripts must be manually run after the upgrade to populate these columns.
These scripts are located in the Resource Kit, under Additional Upgrade Scripts.
- If upgrading to a single schema, run both scripts.
- If upgrading to a split schema, run the _data script against the data schema and run the _rules script against the rules schema.
Choose the scripts for your database type:
- db2zos_rulesetversion_columns_data.sql
- db2zos_rulesetversion_columns_rules.sql
- mssql_rulesetversion_columns_data.sql
- mssql_rulesetversion_columns_rules.sql
- oracle_rulesetversion_columns_data.sql
- oracle_rulesetversion_columns_rules.sql
- postgres_rulesetversion_columns_data.sql
- postgres_rulesetversion_columns_rules.sql
- udb_rulesetversion_columns_data.sql
- udb_rulesetversion_columns_rules.sql
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.
Database
Valid from Pega Version 7.1.4
Improvements to data handling were made for search indexing, agent processing, and filtering. Scripts were provided for proper population of the database tables.
- Importing data from shared obj-external tables is now supported.
- A validation warning will now display when an unexposed property is used in filter or join conditions.
- A Global Search index may now be created across two databases.
- Agent processing on multiple nodes has been improved.
- Improvements were made to controls in Report Definition pages which are used in a dynamic grid.
- Filtering functionality involving special characters has been enhanced.
- Scripts have been provided to populate the RuleSetVersion Major, Minor, and Patch columns.
System Management
Valid from Pega Version 7.1.4
Refinements were made to out-of-place upgrade documentation and processes, as well as for how handling is performed for all of the database vendor specific nuances related to a deploying into a split schema environment.
- A script was created to run the data schema upgrade for z/OS systems.
- In a split-schema configuration, indexing has been enhanced.
- The product installer has been enhanced.
- The stand-alone Static Assembly Utility does not require a password for its process.
- The UpdateManager tool has been improved.
Support for Apache Cassandra
Valid from Pega Version 7.3.1
The Pega® Platform can now read data from and write data to an Apache Cassandra database. Apache Cassandra is a NoSQL database that you can use when a NoSQL database better meets your scalability and processing requirements.
For a list of supported and unsupported features, see Apache Cassandra support.
Requestor pools management in Designer Studio
Valid from Pega Version 7.3.1
On the new Requestor Pools landing page, you can view and manage requestor pools across the cluster, including on the current node and remote nodes. By using this landing page, you can tune the requestor pools to improve the performance of services. You can clear the requestor pool for a service package and view the requestor pool basic metrics and configured thresholds.
For more information, see Requestor pools management, Clearing a requestor pool, Viewing details for a requestor pool, Tuning a requestor pool configuration.
Module version report generated from Designer Studio
Valid from Pega Version 7.3.1
From the new Class Management landing page, you can generate the module version report that provides information about classes in your system, module versions, and version creation dates. You can generate the report for all the nodes in the cluster or for a selected node that is either current or remote. The report is useful for debugging system problems because it helps identify the module version that is causing problems on a specific node.
For more information, see Module version report.
Rules Assembly cache is deprecated
Valid from Pega Version 7.3.1
Rules Assembly (RA) cache and custom settings for its corresponding fua/assemblyCacheMode
prconfig.xml file setting are deprecated because they are obsolete. A warning is logged at startup if a custom (non-default) value is specified for fua/assemblyCacheMode
in the prconfig.xml file. The functional behavior of the system is not affected.