Recover Your Password

Return to Product Support > Learning Center > Developer References > Installation and Setup > Site Lifecycle Considerations

Site Lifecycle Considerations

When Contensive has been installed and the website integration is complete, you need to consider site lifecycle issues. These include site monitoring, database management, file system management, and log monitoring.
Site Monitoring
These are several ways to monitor your site. Contensive includes a status method, and a monitoring service. You can also setup a third-party monitor to hit any dynamic page.
  1. Contensive status method with a third party monitor
    Contensive includes several special 'methods' from the website URL. One is the status method. To call the status method, use the URL:
    The expected response from the site is an HTTP response "Errors 0". Any other response indicates a problem with the site.
  2. Contensive Monitor service
    One of the services installed with Contensive is the Monitor Service. The monitor periodically checks the status method of each Contensive site on the server, as well a few other important checks like Contensive log size (an indicator of other site or Database problems) and current drive space availability.

    The monitor is controlled by the monitor.txt file in the Contensive program files directory. After changes, the monitor service must be stopped and restarted.

    The Monitor can be configured to automatically IISReset the system on error conditions. It also has an HTTP port 80 status screen at port 4532. When the monitor service is running, a hit to this page returns an HTML page with the results of the last checks the monitor ran.
    If you have several sites on a server, you can setup a third party monitor or monitoring service to check the Contensive Monitor periodically (every 5 minutes). An error condition two cycles in a row may indicate a problem that IISReset could not recover.
  3. Hit any dynamic page with a monitor
    Another simple monitor is to setup a website monitor or monitoring service to hit any page on your site. We recommend hitting the status method, as it will report database and other process errors that may occur even when a physical page returns.

This page was last reviewed 4/4/2009 11:57:55 AM