Posted by: alessandro.panzetta
Active Server Pages, Bandwidth, Database, Intranet, Intranet portal, IT support, Security, self-service
As described in the last post, the Download Center relies on a Microsoft Access database that will be described in this post.
So, first create a new MSAccess database and then create a table called “Packages” like the following:
ID: Auto increment
PackageDesc: Contains a short description of the file (E.g. Microsoft FrontPage)
PackageName: Is the filename, avoid using spaces (E.g. “MSaccess.exe” better than “MS Access.exe”) because this will be used to construct the download link
PackageType: Can be Special or Standard or Goodie. Standard/Goodie will be available for download to everyone while Special will be only for the users that are members of given groups.
NeededGroup: In case of Special package the visiting user must be part of this group in order to download the package.
Then create another table called “Sites” as the following:
Country: Short name of the Country (E.g. ITA=Italy, GER=Germany)
Subnet: The third octet of the country/site’s IP address range (E.g. ITA= 192.168.39.x)
Distrib_Point: The web server in the given country (E.g. websrv_ITA)
The first table will handle information on the packages themselves and whether they’re freely accessible or not; the second table instead will be used in order to redirect the user to his/her local web server in order to save bandwidth. This is applicable only in environments in which the IP subnets are correctly set for country level and where in every country or site there is a local IIS web site.
In the next post I’ll be showing you how to build the homepage for this site and the techniques used for it….keep on reading!