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.

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

Required Oracle optimization parameter

To optimize performance, set the Oracle parameter optimizer_index_cost_adj to a value between 20 and 25. If this value is not set, the system can run exceedingly slowly, potentially blocking users from login.

Slow WebSphere performance on Mac platforms

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

-Djava.net.preferIPv4Stack=true

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.

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.