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.

Supported JDBC drivers

Pega 7.1.1 supports Java 6 and Java 7 SDKs only. Ensure that the JDBC driver you are using supports those versions of Java. See your database installation or upgrade documentation for additional information.

* JDBC drivers are only available from the DB2 for z/OS product. Additionally, you need db2jcc_license_cisuz.jar in the same directory as db2jcc4.jar.

** The db2jcc.jar has been deprecated and may not be supported in future releases.

*** This .jar file is required for PostgreSQL version 9.1.x.

Customize your report headers

You can customize the way that the header for all of an application's reports will be displayed by overriding the section pyReportEditorHeader. Save a copy of this section into the application's ruleset, then edit it to display the information, images, and layout that you desire. Once changes are saved, each of your application's reports will automatically use the updated header.

Advanced inline report filters

You can create a custom section and use it to display report filter controls at the top of the report, replacing the default display. The custom section can include basic controls (such as a drop-down menu or text entry field), and the controls can only provide values for the filter functions established in the Edit filters section of the Query tab for the Report Definition.

EAR support for JBoss EAP 6

PRPC deployment in JBoss EAP 6 as an EAR archive is now supported. 

If you need to deploy the JBoss EAR file, go to My Support Portal and submit a Support Request. GCS can assist you with the procedure.

Small distribution kit

A new “small” release distribution format for Maintenance Levels (ML) is now available, designed to significantly increase adoption via: 

• Minimal package size and faster download time
• Minimal install time via tactical changes to the upgrade implementation and process

This kit contains streamlined installers (both UI and command-line installers) and specialized error handling for ML updates (for example, a “small” kit will only work if an existing version of the same release is already installed). 

The kit assembly has also been automated, which includes the construction of a PRPC_Rules.jar archive containing cumulative rules since the GA release. 

A “small” kit will work for any prior ML release within a major release (for example, the “small” ML5 distribution kit will update any customer on 7.1 ML1 through 7.1 ML4).

Improved data page performance

Improvements have been made with queueing and processing of asynchronously-loaded data pages to reduce the number of calls to the database and avoid generating performance problems because of unneeded asynchronous requests.

Use "alternate database" as report source

You can opt to use the the "alternate database" identified in the Reports Database field of the Data-Admin-DB-Table instance that supports the Applies To class of a report as the source for the report. This reduces the load on the database that serves your application when you run the report.

PRServlet not required in PRPC URLs

PRServlet is no longer required in a URL when accessing PRPC. A URL typically written like this:

http://example.com/prweb/PRServlet?[QueryString]

Can instead be written like this:

http://example.com/prweb/?[QueryString]

Adaptive Decision Manager installation changes to support delayed learning

To support delayed adaptive learning, Adaptive Decision Manager (ADM) has been enhanced with database schema changes and no longer relies on Hibernate. This change has an impact in the way ADM is set up in the Decision Management service layer: the jdbc/admDataSource resource is now superseded by jdbc/adm7DataSource.

Additionally, Pega 7.1.7 further simplifies the ADM deployment by providing a single enterprise application or web archive:

• Single EAR deployment archive that can used when deploying ADM on IBM WebSphere and Oracle WebLogic
• Single WAR deployment archive that can be used when deploying ADM on Tomcat and JBoss