Test your patches in QA before deployment on live systems
Suggested QA process for patch management w/ZIP files Because the patching process involves a lot of manual work (which includes running of scripts) it's important to make sure the patch process is repeatable and tested. In complex patch processes just missing one file can be the difference between a few minutes of down time and hours or days. All patches should be applied first to a QA environment. Copy the active profile from production to an isolated system Apply patch to QA environment and conduct tests that all applied functionality is still running If you plan to deploy the patches via JBoss Operations Network, create a script that follows the guide. The script has to include all steps except for the download itself. Test the script by applying it to a second test system, and compare the manual patched and tested system to ensure that the automatic patch does not produce a different result. A script is a good way to create a reproducible result on production even without JBoss Operations Network.