Published Release Notes

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.

Turn off saved connections in WebLogic

PRPC caches connections in thread-local storage. When using a WebLogic application server, set database/savedconnections to FALSE to avoid incorrectly saved, container-managed transactions. You can make this update through JNDI settings or by adding an entry to the prconfig.xml, for example:

<env name="database/savedconnections" value="false" />

Remove JVM settings from prior installations

JVM memory settings ​defined in the setupDatabase.properties file to support a prior installation need to be removed. 

Memory settings are now handled by the installation program. Duplicating these settings may cause installation or upgrade failures. 

IE8 hangs on large imports

IE8 users may experience a hung process when running the Designer Studio > Application > Distribution > Import wizard. This issue is related to low-capacity networks and large (300+ MB) archive files.

Although the processing symbol prevents you from proceeding to the next step in the wizard, the file is still imported to the server. As a workaround, you can:

1. Wait approximately eight minutes for the file to import.
2. Close and restart the wizard.
3. Click Next to skip the upload step.
4. Select the name of your file from the list of import files.
5. Complete the remaining steps in the wizard.

Required DB2 settings for LUW and z/OS

Installations on DB2 databases for LUW and z/OS require a minimum logging file size (4096) and a default table space page size (32K).

To set the table space page size to 32K:

1. Stop the system.
2. Rename one table (“TableX”) to backup (“TableXBackup”).
3. Create a new table space that uses a 32K page size.
4. Copy “TableXBackup” to “TableX” in the new table space.
5. Restart the system and test to verify there are no issues.
6. Drop the backup table (or keep it for future reference).

Additional information is available in the "Adjusting the log space size in upgraded databases" article: https://pic.dhe.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=%2Fcom.ibm.db2.luw.qb.upgrade.doc%2Fdoc%2Ft0023289.html

No direct upgrade to multitenant setup

It is not possible to upgrade directly to a multi-tenant setup. A Pega 7 application may be exported and then imported into a multi-tenant system, with the administrator making the decision as to whether this then becomes a tenant system or a shared system.

Applications developed in versions prior to Pega 7 must be upgraded to a Pega 7 standard system, and then exported and imported into a multi-tenant system. See the Multitenancy Administration Guide for full details.

Upgrade changes system name

As of Pega 7.1.7, the following renaming behavior no longer occurs.

The upgrade process renames your system to “PRPC” and modifies any custom requestor rules in your application to use this name. After the upgrade completes, you must apply these changes to revert your system:

1. Identify all custom requestor rules (browser, batch, app, portal) with access groups that point to prior versions of PRPC.
2. Open the relevant access groups (for example, PRPC:Unauthenticated and PRPC:Agents) and update the name and version fields to point to the current PegaRULES application.
3. Reset your system name to its original value. You can set the Dynamic System Setting prconfig/identification/systemName/default or use the Designer Studio > System > Settings > System Name landing page.
4. Restart the system.

Required DB2 settings

For customers using the DB2 Version 4 drivers (“db2jcc4.jar”), it is necessary to set the custom connection property useJDBC4ColumnNameAndLabelSemantics to “false”.   

For customers using DB2 with WebSphere, the useJDBC4ColumnNameAndLabelSemantics property in the DB2 data source needs to be changed from a Boolean to an Integer and set to "2". 

Using Kerberos authentication with your database

Pega 7 supports Kerberos functionality. Kerberos is a computer network authentication protocol which allows nodes communicating over a non-secure network to prove their identity to one another in a secure manner. 

To use Kerberos for authentication, you must use the command line to install or upgrade Pega 7.

To use Kerberos authentication:

1.  Change the setupDatabase.properties file.

a.  In the “Uncomment this property section” of the file, uncomment the jdbc.custom.connection.properties property.  Based on your security infrastructure, different properties may be required as parameters to this property; provide the needed properties as semicolon-delimited name/value pairs:
 

jdbc.custom.connection.properties=prop1=val1;prop2=val2;prop3=val3;
 

Example:  For an installation on a MSSQL database server from a Windows client machine (where both machines belong to the same Windows domain), using the Microsoft JDBC driver, the property may be set as follows:
 

jdbc.custom.connection.properties=integratedSecurity=true;

b.  Comment out all the username and password properties where they occur in the jdbc.custom.connection.properties file, so that they appear as follows:

# pega.jdbc.username db username
# pega.jdbc.password db password

[lines removed here]

# pega.jdbc.username=ADMIN
# pega.jdbc.password=ADMIN

2.  Set up your database to enable Kerberos functionality.  This may include additional vendor-specific JDBC driver configuration, or other setup procedures.  Check the documentation from your database vendor to determine what Kerberos setup is needed for your database.

3.  Run the command line installation or upgrade by following the instructions found in the Pega 7 Deployment guides.

Run cleanup.bat/sh script only before upgrading

Prior to upgrading the rulebase, you can optionally run the cleanup.bat/sh script to remove older rules from the database.

Run this script before you upgrade your rulebase, or the script may delete needed rulesets. For more information about running the cleanup.bat/sh script, refer to the Upgrade Guide specific to your release version.