When performing a Portal upgrade, one common administrative task is determining which customized or added JSP files have been overwritten by defaults during the upgrade. Here is a simple approach to solving this problem:
Maintain a list of customized/added JSPs (or any other file type) as a simple text file that contains the full path of the JSP, one per line
When you do any kind of install, you can build a list of modified files to compare against your static list of customized files
Any matches will indicate a file that needs to be replaced or for which the customizations need to be reapplied
In this example, jsps.log is the static file. The -mtime -1 parameter only matches if the file was modified in the last day, so you'd run this immediately after the install or adjust the time increment, as necessary.
Administrator@mario /cygdrive/c/IBM/WebSphere/AppServer/profiles/wp_profile/installedApps$ find `pwd` -name *.jsp -mtime -1 -print > jsps_new.log
Administrator@mario /cygdrive/c/IBM/WebSphere/AppServer/profiles/wp_profile/installedApps$ grep -f jsps.log jsps_new.log