Published Release Notes

Tomcat log files moved to work directory

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.

Additional upgrade scripts for new columns

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

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

-Djava.net.preferIPv4Stack=true

Split schema systems require additional privileges

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

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

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.

Automatically update dependent applications to use the latest versions of built-on applications

You can now automatically update dependent applications to use the latest versions of built-on applications. When you import an archive that you created from a product rule, you can update all dependent applications to be built on the latest application versions in the archive.

For more information, see Updating dependent applications with the latest versions of built-on applications.

Alerts for long-running queue processor and job scheduler activities

Pega Platform™ now saves an alert in the performance alert log when a queue processor activity or a scheduled job runs longer than the configured threshold value. Use the alerts to identify potential performance issues with long-running processes.

The alerts are enabled by default. You can change the alerts for dedicated queue processors and job schedulers at the rules level. For standard queue processors, you can also set the threshold value for the Queue-For-Processing command in an activity. You disable the alerts in dynamic system settings.

For more information, see:

• PEGA0117 alert: Long-running queue processor activity
• PEGA0118 alert: Long-running job scheduler activity

Introduction of Search and Reporting Service

Pega Platform™ now uses Search and Reporting Service, which is an independent microservice. The new enhancement provides a convenient way to manage your application data, and is easier to maintain. For example, because of the cloud-based architecture of Search and Reporting Service, any bug fixes and performance improvements occur seamlessly, and have no impact on your overall experience in Pega Platform.

For more information, see Search and Reporting overview.

Ability to restrict access to the Import wizard

You can now restrict access to the Import wizard so that users implement an automated pipeline to deploy changes between environments such as staging and production. Deployment Manager is one method by which to create pipelines. By using pipelines to propagate changes, users can apply a standardized and automated deployment process for migrating their applications.

For more information, see:

• Ensuring that users migrate applications with a pipeline by restricting the Import wizard
• Understanding model-driven DevOps with Deployment Manager