The ProTop update is designed to be non-destructive. In fact ProTop goes as far as to create a backup of the most often changed directory in a protop installation, the "etc" directory. A backup is made and stored in the PROTOP/tmp directory named etc.[month].[day of month].tar.
Beyond that, the update will never remove or overwrite any custom-named files you have created in your ProTop directories. It will simply add new and overwrite existing files that are part of ProTop. If someone did change a default ProTop file it will be reverted during an update. So, do you have a backup?
Unix / Linux
NOTICE: If you are upgrading an older version (3.14*, 3.3*) to 315 or newer, you will need to run pt3upd.sh first, and then run "pt3upd". In version 315 and newer pt3upd.sh itself has been replaced with just "pt3upd". The first update uses your pre-315 pt3upd.sh to download the new pt3upd. Then running pt3upd fully synchronizes your version of ProTop.
Log into your server as the owner of the ProTop files and run:
Pre-315: $PROTOP/bin/pt3upd.sh then
$PROTOP/bin/pt3upd
Log into your server as an administrator with a command window using elevated privileges and run:
%PROTOP%\bin\pt3upd
Once you have upgraded to 315 or newer, add the following line to your $PROTOP/etc/schedule.*.cfg file to have ProTop update itself to the latest public release on a regular basis. For example, this will update ProTop every Sunday morning at 3 AM:
00 3 * * 0 pt3upd > ${PTTMP}/pt3upd.err 2>&1
NOTE: Your next scheduled run of dbmonitor (set up during your ProTop installation) will restart ProTop after the update.
In the last year alone ProTop Real Time has been enhanced with many new features:
Visit help.wss.com and search for "notes" or any keyword of interest to learn more.