1. In Application.cfm ...
    
   
   1. Give your application a unique name in the cfapplication statement  Since SitePeeker uses an application variable to determine status on the test server, it is essential that your application name is unique in case you are testing multiple targets, or someone else is also running SitePeeker on a shared server.
       
   2. Specify the database platform on Line 17.
       
   3. Specify the datasource name on Line 18.
       
       
2. Enable your datasource ...
    
1. Either enable a new datasource in the ColdFusion Administrator or use an existing one.
    
2. Run /admin/index.cfm.  This is the centralized admin template.  It calls all of SitePeeker's administrative functions.  Create the SitePeeker database table from the list of supported platforms (Access, MS SQL, mySQL, Oracle 8i, Oracle 9i).
     
    
3. Create your Scheduled task ...
    
   1. From the admin template, choose "Create Scheduled Task" (your host must allow CFRegistry for this to work)
       
   2. Name your scheduled task, again taking care to give the task a name guaranteed to be unique. A syntax of ''sitepeeker_domainname'', where domainname is the domain you are testing, ought to be sufficient.
       
   3. List the fully qualified url to schedule. The default is http://yourdomainnamehere/tagcaller.cfm.
       
   4. List an appropriate start date and time. You can leave the existing settings as-is if you like.
       
   5. Specify the testing interval in seconds.  A value of 300 (5 minutes) is usually a sufficiently close watch, but you can set it for less, or more as desired.
       
   6. Specify the timeout value.  We use 10, but that is because we know our server is reliable and has a reliable upstream connection. You may need to experiment to find the ideal setting.
       
4. in TagCaller.cfm: Specify values for every parameter EXCEPT the data source name. Specifics on each parameter are located directly inside TagCaller.cfm
    
5. Download GridMonger and unzip it into the /admin/ folder, so that gridmonger.cfm and gridmonger.css are located in the /admin/ folder, with gridmonger's subfolders directly underneath /admin/.

If you are testing multiple targets...

1. You only need to create one data source to manage all of your targets.
    
2. Starting with version 1.2, you can simply install SitePeeker once to monitor any number of server targets.
    
3. The example tagcaller.cfm makes five calls to the SitePeeker tag, one test each for HTTP, web mail, HTTPS, SMTP and POP3. Use it as your guide to setting up your own single-or multi-target tests.  Note that you can have numerous files like tagcaller.cfm scheduled, and each file can have any number of tests set up inside.