In case you didn't see them, installation instructions for UNIX and Windows can be found here: http://demo.wss.com/help/.
Usually when people get tripped up, it's because of a proxy server or permissions issues. The first thing to try, always, is to run ProTop from the command line:
$PROTOP/bin/protop <full path DB or friendlyName>
If that doesn't work, then nothing else will either.
Still having trouble? Post your questions here.
If you happen to be running Windows, and for some mysterious reason don't want to install The Linux Patch, you should try running ProTop from a PROENV command line:
proenv> cd /d %protop%
proenv> protop d:\db\dbname
If this works then you have at least installed the ProTop core properly.
If you allowed databases to be discovered when you installed or have otherwise configured a db list then you should also be able to use a "friendly name" rather than a full path name.
You can see if you have setup db "friendly names" with the following command:
proenv> cat etc\dblist.cfg
This ought to produce output similar to:
# note: please do NOT append .db to /dbpath/dbName
dblist.cfgfile similar to above you should then be able to use the friendly name to start ProTop:
proenv> protop s2k
You should also be able to create a shortcut icon on your desktop for that database:
proenv> mkscut s2k
The field after SERVERNAME indicates databases that you want to have monitored in the background with the ProTop portal. If you have at least one such database it should be communicating with the portal. You should see various files in your %LOGDIR% and %TMPDIR% with names like
pt3agent.s2k.flg. There may be clues in those files revealing why the agent is not running or why communications are unsuccessful.
If there are no log files the next debugging step is to verify that there is a service running called "ProTop3 DB Monitor". If this service is configured, but not running, start it. If it is not configured you will need to RUN AS Administrator:
%PROTOP%\nssm_setup.bat. (I find it easiest to do this using Windows Explorer, right clicking on the .BAT file and choosing "run as administrator").
Once the service is running you should see various files in your %LOGDIR% and %TMPDIR% with names like
dbmonitor.flg. There may be clues in those files revealing why the agents are not starting or why communications are unsuccessful.