Data schema requires update after multitenant upgrade
Valid from Pega Version 7.2.2
After an out-of-place, multitenant upgrade to Pega 7.2.2 from Pega 7.2 or later, the PR_DATA_TAG_RELEVANTRECORD table that is in the existing data schema is not present in the new rules schema. The table must be present in the rules schema for the upgrade to the rules schema to work. Copy the PR_DATA_TAG_RELEVANTRECORD table from the existing data schema to the new rules schema, and then upgrade the new rules schema. The PR_DATA_TAG_RELEVANTRECORD table is not required to be in the rules schema. After the rules schema upgrade is finished, drop the copy of the table that is in the new rules schema before you upgrade the data schema.
Upgrade/update fails if PostGIS is applied to PegaRULES or PegaDATA schema
Valid from Pega Version 7.2.1
If you use the PostGIS extension to a PostgreSQL database, upgrading or updating the Pega 7 Platform fails if the extension has been applied to either the PegaRULES or PegaDATA schema. PostGIS can be applied to any other schema.
Primary key constraint error when using JBoss
Valid from Pega Version 7.1.9
A primary key constraint violation exception might occur in the following situation: you use JBoss EAP 6.4 and SQL Server 2012 with a JDBC 4 driver, and you use two or more file listeners or JMS MDB listeners with concurrent threads that create work objects that use multiple files. If a primary key constraint violation exception occurs in this situation, update the data source configuration file to set the jta parameter to true. For example, set <datasource jta="true" jndi-name-"java:/jdbc/PegaRULES>.
Node types renamed after upgrade from Pega 7.2.2 to Pega Platform 7.3
Valid from Pega Version 7.3
If you used node classification in Pega® 7.2.2, when you upgrade to Pega 7.3, node type names are automatically changed to a new name when you start a node with a node type.
- UniversalNode becomes Universal
- WebUserNode becomes WebUser
- BackgroundProcessingNode becomes BackgroundProcessing
- BIXNode becomes BIX
- SearchNode becomes Search
If you created agents in Pega 7.2.2, agent schedules are also automatically updated with a new name during the upgrade. For more information, see Customized agent schedules for standard Pega Platform agents must be updated after Pega 7.2.2 to Pega Platform 7.3 upgrade and the appropriate Deployment Guide.
Rollover policy for log files
Valid from Pega Version 7.3
The rollover policy for log files is now based on time (daily) and file size (maximum file size is 250 MB). Log files are rolled over daily or when the maximum file size is reached. Current (not rolled over) log files do not have a time stamp. The time stamp is added when the log file is rolled over. In addition, the log file name for the current log file does not include the date. You can add the date to the current log file; however, the log file will not be rolled over. In addition, the web.temdir variable for setting the log file location is no longer supported; use the pega.logdir variable instead.
For more information, see Pega Platform logging with the Log4j 2 logging service.
Customized agent schedules for standard Pega Platform agents must be updated after Pega 7.2.2 to Pega Platform 7.3 upgrade
Valid from Pega Version 7.3
If you used node classification in Pega® 7.2.2, when you upgrade to Pega 7.3, node type names are automatically changed to a new name when you start a node with a node type. Agent schedules for standard Pega Platform agents are deleted and re-created with the new node type name, but any customization that you made in Pega 7.2.2 is not saved. You must manually update the agent schedules for standard Pega Platform agents in Pega 7.3.
For more information, see Node types renamed after upgrade from Pega 7.2.2 to Pega Platform 7.3 and the appropriate Deployment Guide.
Push notifications and Oracle WebLogic Server 10.3.6
Valid from Pega Version 7.2.2
Pega® Platform push notifications can use WebSockets and long polling. However, for WebLogic Server 10.3.6, the push notifications feature does not work. To disable the feature, contact Pegasystems Global Customer Support.
Load balancing: HTTPD does not support WebSockets by default
Valid from Pega Version 7.2.2
If you use a load balancer with HTTPD (Hypertext Transfer Protocol Daemon), HTTPD does not support fully functional WebSockets and sticky sessions. By default, HTTPD does not support sticky sessions, because if it did, after a session was started, the same server would serve all requests for that session.
WebSphere log error with Java 8 for Enterprise JavaBeans
Valid from Pega Version 7.1.8
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.
Rules Assembly cache is deprecated
Valid from Pega Version 7.3.1
Rules Assembly (RA) cache and custom settings for its corresponding fua/assemblyCacheModeprconfig.xml file setting are deprecated because they are obsolete. A warning is logged at startup if a custom (non-default) value is specified for fua/assemblyCacheMode in the prconfig.xml file. The functional behavior of the system is not affected.