Published Release Notes

PEGA0055 alert detects clock drift in a multi-node clustered environment

Clocks in most of the hardware platforms run at different rates, and the PEGA0055 alert detects the clock drift on any of the nodes in a multi-node cluster. The alert is triggered when the clock drifts from the average time of the clocks in the cluster by an amount that exceeds the time threshold configured in the prconfig.xml file. You can use a network time protocol service or daemon to correct the clocks by referring to a standard external Internet time service, for example, nist.gov.

For more information, see PEGA0055 alert: Clock drift exceeded the configured time threshold.

PEGA0056 alert monitors PR_SYS_LOCKS defragmentation performance

The System-Locks class contains information about locks, and the PR_SYS_LOCKS table can now be periodically de-fragmented. Accordingly, any increase in the time taken to defragment the table associated with this class results in an increase in the time taken by a requestor to acquire or release a lock.

The PEGA0056 alert indicates that the defragmentation exceeds the time threshold that is configured in the prconfig.xml file. When the alert is triggered, you can modify the defragmentation interval or disable defragmentation.

For more information, see PEGA0056 alert: Defragmentation of the table associated with class System-Locks exceeded the configured time threshold.

Schema not found error when importing a Rule-Admin-Product file

If you import a Rule-Admin-Product file (RAP) file that includes a schema that has a view, grammar parsing changes can mean that the Pega 7 Platform is unable to find the schema.

To enable the Pega 7 Platform to find the schema:

1. Review the error message that indicates that the schema was not found and identify the following items:
   • The name of the schema that is causing the error
   • The table name in the format: wrong_schema_name.table_name...
   • The DDL that the Pega 7 Platform is trying to apply
2. Use the table name to identify the correct schema name in your system. This schema is usually your data schema, but might also be an external database.
3. Download the DDL.
4. Correct the schema name and save the DDL.
5. Manually apply the DDL.

Identify, install, and manage hotfixes with the Hotfix Manager

Hotfixes are packages of files that address issues in Pega 7 and in participating Industry Applications. With Hotfix Manager, you can:

• Scan your system for installed and missing critical hotfixes and create a report that you can provide to Pegasystems Support for diagnostic purposes.
• Review the descriptions and contents of hotfixes.
• Install, rollback, and commit hotfixes.
• Manage hotfixes that include schema changes or require other special handling.

The Hotfix Manager replaces the Update Manager Hotfix Installer and System Scanner, both of which are deprecated. For more information, see Hotfix Manager identifies, installs, and manages hotfixes to Pega 7 and participating Industry Applications.

End of support for Netscape Plugin API in Google Chrome 45

Beginning with Chrome 45, which is expected to be available in September 2015, Google is ending support for browser plug-ins that rely on the Netscape Plugin API (NPAPI) architecture. These plug-ins include Microsoft Silverlight, Adobe Flash Player, and Java.

The Pega 7 Platform includes several optional features that use these plug-ins. For a detailed overview of these features, see Client-side technologies.

Updates to the Business Intelligence Exchange (BIX) product

The Business Intelligence Exchange (BIX) add-on has been updated with several new features. BIX 7.1.8 fully supports extraction of data from a Pega 7 multi-tenant instance. BIX can also now be run on Pega Cloud instances. Additionally, the new pxExtractDataWithArgs activity can be used by on-premises customers to schedule BIX runs by using Pega Platform agents.

For more information, see the BIX 7.1 User Guide.

WebSphere log error with Java 8 for Enterprise JavaBeans

For environments that are deployed by using Java 8 on IBM WebSphere Application Server version 8.5.5.9 through the last 8.5.5.x fix pack, the log might report that a class was not found when the application server attempts to start Enterprise JavaBeans. If Java EE functionality is not needed, no further action is required. However, to use Enterprise JavaBeans, see WebSphere log error with Java 8 for Enterprise JavaBeans.

Enhanced product rule form for easy application packaging

The enhanced product rule form allows you to add applications in Delta mode, which includes only the patch version of the rulesets that comprise the application rule. You can also use Global exclusions to exclude one or more rules that are not associated with a ruleset version.

These enhancements allow easy packaging of non-versioned rules that are often deployed separately and reduce the need to manually add them later.

For more information, see Product rules - Completing the Contents tab.

Custom PL/Java Modules for PostgreSQL 9.3

To install Pega 7 for PostgreSQL 9.3, you must first install the version of PL/Java included in your resource kit. Follow the installation instructions located in:

<Pega 7 installation directory>\ResourceKit\ResourceKitREADME.txt.

Note that if you do not install PL/Java before you attempt to install Pega 7, then the Pega 7 installation fails.

Custom database (DB) triggers are dropped during upgrade

The latest version of Pega 7 improves performance by no longer using database triggers to assist with System Pulse and Data-Rule-Summary processing, which is now done within the Pega 7 engine. As a result, DB triggers are no longer installed on either the pr_sys_updatescache or pr4_rule_vw tables.

When upgrading to the latest version of Pega 7, if you had previously implemented a custom database (DB) trigger on these tables, or a custom DB trigger that refers to these tables, it is removed during the upgrade process. No custom triggers are removed unless they reference these tables.

If you have custom DB triggers that reference the pr_sys_updatescache or pr4_rule_vw tables and perform other processing, those triggers must be reimplemented. When doing so, you must be careful to not modify the pr_sys_updatescache or pr4_rule_vw tables.

For more information, see Startup check removes custom DB triggers.