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.
SystemCleaner agent is split into node-level and cluster-level agents
Valid from Pega Version 7.3
The Pega-RULES:SystemCleaner agent has been split into node-level and cluster-level agents to avoid database performance issues. The new node-level agent, Pega-RulesEngine:NodeCleaner, runs on all the nodes in the cluster, while the new cluster-level agent, Pega-RulesEngine:ClusterAndDBCleaner, runs on only one node in the cluster. If you customized the agent schedules of the Pega-RULES:SystemCleaner agent, you must manually update the agent schedules of the new agents because customized schedules are not retained.
For more information, see Agent schedule data instances – Completing the Schedule tab.
Greater cluster stability with client-server clustering topology
Valid from Pega Version 7.3
You can now deploy Pega® Platform in the new client-server clustering topology that uses Apache Ignite, which increases stability in large clusters and provides independent scalability for both servers and clients. This technology separates the client nodes, which are responsible for Pega Platform processes, from the server nodes, which are responsible for cluster communication and distributed features. If your production environment consists of more than five nodes in the cluster, it is recommended that you switch to the new client-server topology.
For more information, see Apache Ignite client-server clustering topology and the appropriate Deployment Guide.
Create pre-import and post-import steps
Valid from Pega Version 7.3
To take specific actions based on archive metadata, add pre-import and post-import action steps to collections. For example, you can configure a pre-import activity to automatically verify that an archive meets certain criteria before you import the archive. If the archive does not meet the criteria, Pega® Platform does not import the archive.
For more information, see Pre-import and post-import collections.
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.
New Pega0086 alert and enhanced Pega0019 alert
Valid from Pega Version 7.3
The PEGA0086 alert is generated when the maximum number of attempts to acquire a lock on a requestor has been exceeded and a thread fails to obtain a lock on the requestor, and as a result, displays the RequestorLockException message. The Pega0019 alert has been enhanced and now contains additional information such as a user name, an application name, and a thread stack trace, which are associated with the long-running requestor.
For more information, see PEGA0086: Requestor locked by a busy thread and PEGA0019 alert: Long-running requestor detected.
Performance enhancements to the Strategy rule
Valid from Pega Version 7.3
Strategy designers can create globally optimized strategies to increase the performance of existing strategies. Globally optimized strategies reduce computation time and memory consumption when you run large-scale batch data flows and simulations. Improvements to the Strategy rule performance are the result of decreased run time and quality changes to the code generation model.
For more information, see Introduction of globally optimized strategies.
X-Forwarded-Host field is optional for HTTP proxy servers
Valid from Pega Version 7.3
Prior to Pega® Platform 7.3, the X-Forwarded-Proto and X-Forwarded-Host fields were both required to deploy Pega Platform instances behind an HTTP proxy server. Some proxy servers or load balancers (for example, Amazon ELB) do not support the X-Forwarded-Hostfield. Starting with Pega 7.3, only the X-Forwarded-Proto field is required. For more information, see Deployment behind a reverse proxy.
Upgrades and updates from Pega 7.3 on MSSQL fail with column name mismatch
Valid from Pega Version 7.3
This failure applies only to upgrades and updates from Pega® Platform 7.3 on systems running Microsoft® SQL Server®. In Pega 7.3, the capitalization for the column name pc_work_agile.pzPvStream is incorrect. The correct capitalization is pzPVStream. To prevent upgrade and update failures, before you upgrade or update, run the following command from the Microsoft SQL Server Management Studio (SSMS) to rename the column:
EXEC sp_rename ‘data-schema-name.pc_work_agile.pzPvStream', 'pzPVStream', 'COLUMN'