This section describes additional tasks to perform after the patch.
- Reconfiguring the application server
If you performed an out-of-place patch, you must reconfigure the application server to use the new rules schema. The process is different for each application server..
- Restarting Pega Platform
Restart Pega Platform to load the updated code and rules from the patched rules schema.
- For systems configured for High Availability: Reverting the cluster settings
If you enabled rule migration functionality before the patch, you must revert the cluster settings after the cluster restart to notify the system that the patch is complete.
- Reviewing log files
The patch creates a series of log files in the Pega-image \scripts\logs directory. Review the log files to ensure no outstanding issues were introduced during the patch process.
- Testing your applications
Pega rigorously tests each patch release to ensure that it has no known compatibility issues between patch versions. Pega recommends that clients perform their own sanity or smoke testing after reviewing the list of "Resolved Issues" to re-validate appropriate features or functions in your Pega application that a patch can affect.