ColdFusion
supports two types of probes to monitor your local Web site:
Default probe. The default probe is a test program that verifies the availability of the ColdFusion Server or a specific URL.
Custom probe. The custom probe allows you to specify a test program to run as a probe. Depending on the program executable that you specify, you can use a custom probe to verify the availability of almost any part of your web site such as a database.
In order for a ColdFusion probe to verify the availability and integrity of a resource in your Web site, it requests a URL at a specified frequency. The probe then scans the returned HTML page for a match of a specified search string. Depending on the results of that scan and match, the probe test either succeeds or fails:
Test succeeds when the returned page contains the anticipated search string within the time-out interval specified. Inbound HTTP requests are then continuously sent to the server for which the probe exists and a green icon will appear in the Sever Configuration page.
Test fails when a probe validation test fails, as a result of a URL failure, a time out, or the anticipated search string does not match, you can instruct ColdFusion to do any or all of the following:
Restrict Web traffic to the failed server from a Cisco Local Director box.
Execute a script file to run.
Restart the ColdFusion Server (available for default probes only)
Log when the ColdFusion Server is restarted. (available for default probes only)
Redirect the HTTP traffic to another server if you have a Cisco Local Director box configured.