Published Release Notes

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. 

Automated Unit Testing is unavailable

Automated Unit Testing (AUT) is unavailable in 7.1.1 - 7.1.5.

Starting in 7.1.6, users can access AUT features from supported browser versions of IE.

Privilege required for Recent Explorer

Users with custom roles defined must add the pxUpdateRecents privilege to see work in the Recent Items Explorer. 

Deprecated end user portals

The following portals are no longer be supported:

• SysAdmDD
• WorkUserDD
• WorkManagerDD

As a best practice, customize standard, supported portals rather than update your existing portals to include new features.

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.

Split schema upgrade instructions missing properties

If you upgraded from 5.x, 6.x, or 7.x using the instructions in previous versions of the upgrade guide, you may have neglected to set the properties below in your migrateSystem.properties file when you migrated your upgraded schema to the source system:

pega.rules.objects.generate=true

pega.rules.objects.apply=true

If these properties were not set during an upgrade that splits the schema, your environment does not have the indexes, triggers, and primary keys on the rules tables.

To check for this issue, see if the pr4_base and pr4_rule rules tables in your existing rules schema are missing primary keys. If they are, use the SQL scripts in the ResourceKit\MigrationRecoveryScripts directory of the release to cleanup duplicate rules that were created due to this issue. Follow the steps below to run the scripts.

To run the scripts on Microsoft SQL, Oracle, or PostgreSLQ

1. Take down any app servers using the affected schema.
2. Backup your database.
3. Replace all instances of @RULES_SCHEMA in <database>_cleanDups.sql with the name of the schema that contains the pr4_base table.
4. Run the <database>_cleanDups.sql script on the database with vendor tools (sqlPlus, SQL Server Management Studio, etc).
5. Replace all instances of @RULES_SCHEMA in <database>_fix_vw_table.sql with the name of the schema that contains the pr4_base table.
6. Run the <database>_fix_vw_table.sql script on the database with vendor tools (sqlPlus, SQL Server Management Studio, etc).
7. Generate and apply the ddl using the command line generateDDL command. Check the installation guide for your database or the upgrade guide for details about how to use the generateDDL command line script.
8. Rebuild the indexes for the tables in your rules schema using vendor tools. This is necessary so that your system runs at an optimum speed.
9. Optionally upgrade to the latest release, at this point your database is ready to be upgraded or used depending on your needs.

To run the scripts on DB2 for LUW or z/OS

1. Take down any app servers using the affected schema.
2. Backup your database.
3. Run the <database>_cleanDups.sql script on the database with vendor tools (UDB CLP, Data Studio, etc) to create the CLEANSE_RULES_DUPS stored procedure.
4. Run the query Call CLEANSE_RULES_DUPS(‘<rulesSchema>’); where <rulesSchema> is the name of schema that contains the pr4_base table.
5. After the previous step is complete drop the CLEANSE_RULES_DUPS procedure.
6. Replace all instances of @RULES_SCHEMA in <database>_fix_vw_table.sql with the name of the schema that contains the pr4_base table.
7. Run the <database>_fix_vw_table.sql script on the database with vendor tools (UDB CLP, Data Studio, etc).
8. Generate and apply the ddl using the command line generateDDL command. Check the installation guide for your database or the upgrade guide for details about how to use the generateDDL command line script.
9. Rebuild the indexes for the tables in your rules schema using vendor tools. This is necessary so that your system runs at an optimum speed.
10. Optionally upgrade to the latest release. At this point your database is ready to be upgraded or used depending on your needs.

Synchronized database and application server settings

Configure your database and application server to use the same time zone and character encoding to avoid conflicts.

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.

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