This topic has not yet been written. The content below is from the topic description.
Applying Patches Each patch comes with it's own set of instructions. Some patches may have scripts that needs to be run, others just requires files to be copied others again may require both. It's therefore important to have read and tested the instructions associated with the patch (see Suggested QA process for patch management w/ZIP files for more details). In this case, the instructions say: Replace the existing $JBOSS_HOME/server/$JBOSSCONF/deploy/jboss-web.sar/jbossweb.jar with the new jbossweb.jar. In this example we are assuming JBOSSCONF is “default”. The process is the same for each profile and should be repeated for all of them. IMPORTANT! Make sure the server is stopped before continuing. Any file you are preparing to overwrite should be backed up first. In case the patch fails you can then revert back to the old setup. If the patch is massive, backing up the whole profile is the best approach. $ cd $JBOSS_HOME/server/default/deploy/jboss-web.sar $ sha256sum jbossweb.jar 0696b1a9c2694dabe7ca39f2cd7e4bfe410578888fb6073bb64a4b910620891f jbossweb.jar $ mv jbossweb.jar jbossweb.old $ cp ~/Downloads/jbossweb-2.1.10.jar jbossweb.jar Once the file has been copied, verify with sha256sum that it is the modified JAR file – or compare the file to the original downloaded from the customer portal. You can now start the server and continue running with a freshly patched server. Or continue with the next patch until all patches have been applied.