Skip to main content

Post-patch tasks

Suggest edit
Updated on April 12, 2022

This section describes additional tasks to perform after the new rules schema and the existing data schema have been updated.

Pega has reviewed the features and fixes in Pega Platform and has identified the areas where an update from Pega Infinity release 8.x to 8.y will have an update impact. An update impact occurs when a feature or enhancement imposes a noticeable or blocking change. Review the release notes with update impact to determine whether you need to perform additional steps before or after an update. For more information, see Pega Platform changes with update impact.

  • 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

    Rigorous tests of each patch release ensure that the update has no known compatibility issues between patch versions. Perform your own sanity or smoke testing after reviewing the list of Resolved Issues to revalidate appropriate features or functions in your application that a patch might affect.

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us