Cadzow Knowledgebase


Welcome
Contact Us
Professional
Services

Consulting
Knowledgebase/
Site Search

Remote Support

Print Friendly

Cadzow 2000 Weblink — Decommissioning Tips

Cadzow 2000 Weblink consists of two components:

  1. A database hosted by SQL Server;

  2. Scripts (ASP.NET) and other resources that sit under Windows Internet Information Services (IIS). Some of these files are standard Cadzow 2000 files, and others are site-specific files such as documents and images.

“Decommissioning” can take many forms, from simply making the website inaccessible to the public, to complete removal from the system.

Here are a few tips:

  1. Remove it from search engines. If the site is Internet-facing, add a robots.txt file to the site which excludes the entire site from indexing. Then re-submit the URL to the major search engines.

    It's easier to remove a site from the search engines while it is still running. If the site simply goes dark, the search engines will take much longer to realise the site is no longer active.

    Another way to remove a site from the search engines is to create a blank site on the same URL with a robots.txt and eventually the search engines will find it and remove the content.

    (Note that by default, most pages which contain data or which sit behind a login prompt are excluded from search-engine crawls by per-page instructions. However many other pages are designed to be indexed by search engines. You can verify the data indexed by the search engines with the “site:Domain” command.)

  2. Remove it from the web. When you can verify the search engines have removed the site from their caches, public access can be removed (ie via inbound firewall rules or website binding rules). If the site needs to be removed from public access immediately, use firewall rules to allow only the various search engine crawlers to access the site via their IP addresses.

  3. Back up the website files. The site will contain many site-specific files, in addition to standard Cadzow 2000 code. In theory you do not need to back up the Cadzow 2000 code, as this can be supplied anew if required. However the files are small and it's generally too fiddly to pick out site-specific files for archiving. The backup is simply a copy of all the files. (Also note Cadzow 2000 does not register any website logic outside the root.)

  4. Back up the database. Use SQL Server Management Studio or a command-line script to make a backup of the database file.

  5. Decommission database. Either delete it from the system, remove relevent bindings or remove access to all but administrative users as required.

If the site is being left online for archival purposes, it simply needs to be removed from search engines and made inaccessible to the public web. If the purpose is to remove it completely, we recommend an orderly process to first remove it from the search engines, then backup the files and remove from the system.

Copyright © 1996-2018 Cadzow TECH Pty. Ltd. All rights reserved.
Information and prices contained in this website may change without notice. Terms of use.


Question/comment about this page? Please email webguru@cadzow.com.au