Installation

Quick Guide
System Requirements
Installation Components
Procedure

Quick Guide

To Install:

1.Unzip this file under c:\inetpub\wwroot
2.Run \setup\setup.exe
3.Register the 2 components in \component
4.Copy filemanager.dsn from \db to C:\Program Files\Common Files\ODBC\Data Sources
5.Setup \filemanager as an Application

To test go to:

http://www.yoursite.com/filemanager
login as user "bill" pass "uno"

If that fails start by reading the word document \document\filemanager.doc This was written for the full ASP version however it should help determine some problems with the component version.

 

 

System Requirements

1. Server
   NT server with IIS 4.0 or greater
   Win98 with PWS
   
   
2. Client
   Netscape 3.0 or greater
   Explorer 4.0 or greater
   Other browsers are not excluded but must support the File input type for file upload. Cascading Style Sheets are used which may result in a poor appearance in other browsers.

Installation components

1. ASP files
   
2. Images The application makes extensive use of GIF images throughout the pages. All images used by FM are stored in a common directory. The default location is: /filemanager/images
   This directory should be placed in the root directory of the site.
   To customize this location edit the global.asa file and change the following line:
   Session("dir_fm_images") = "/filemanager/images"
   
3. FileManager.dll This component has been generated from a number of key asp scripts so that the source code is protected. It should operate in the same way as the scripts.
   
4. Getup.dll is distributed with this application for the purpose of demonstrating file upload. However it is not recommended that it is used for commercial/critical applications as its capabilities with all file types/sizes and systems has not been fully tested. It is recommended that you purchase and use a third party utility. The Persists.ASPUpload component has been tested to work with these scripts. The ASPUpload file is a dynamic Link Library which is accessed by the ASP script to upload and save a file as requested by the user.

Procedure

Planning

It is important to ensure that all files are located in the correct directories so that IIS can locate all the necessary files. Depending on your specific site requirements and existing software you may want to modify the scripts.

The ZIP file will install into c:\inetpub\wwwroot\filemanager.  It is recommended that you use this directory initially to ensure that everything works.  You may then want to move the application under a more appropriate directory.The following items need to be considered before making modifications.

• Script Location. The ASP scripts distributed need to be located in the same directory as each other. However this directory name and location can be set as required. One suggested location is c:\inetpub\wwwroot\mysite\scripts\fm
  
• Image Location. The images used by the scripts should be located in a common directory. The default location is /filemanager/images however you may need to change this if that directory name is already in use. Edit the global.asa and replace the reference to /filemanager/images.
  
• Templates. Template files can be created to allow users to more quickly create files. The default location for the template files is /filemanager/templates. This can be found in the global.asa
  
• Upload Component. These scripts use Getup.dll (distributed with the application) If the installation site already uses another upload component then it may be preferable to modify the ASP scripts to use the alternate component. The effort required to modify the scripts should be minimal. The file __FileManager__Upload__Component__.asp is the only effected script. A second script exists which has already been customized for the Persists.ASPUpload. It is named Persists__FileManager__Upload__Component__.asp. Simply rename this file to __FileManager__Upload__Component__.asp to use the persists component.
  
• Database. The database for this application is used to store user logon details and user preferences. The database distributed with this application is a Microsoft Access .MDB file. To use an alternative OBDC database a system DSN will need to be created to specify that database.

Implementation

File copy

The implementation process is simply a matter of copying the required files to their respective directory locations as chosen in the planning stage. (or just unzip all files into their default location, Default paths are shown below:

• Scripts - c:\inetpub\wwwroot\filemanager\scripts\
• Database - c:\inetpub\wwwroot\filemanager\db
• Images - c:\inetpub\wwwroot\filemanager\images
• Templates - c:\inetpub\wwwroot\filemanager\templates
• Components - c:\inetpub\wwwroot\filemanager\components

Database DSN

To allow the ASP scripts to access the database, a DSN will need to be created. This is done by creating an OBDC connection. This can be done using the OBDC settings in the Windows Control Panel. The DSN should be named "FileManager"

If you prefer you can copy FileManager.dsn to C:\Program Files\Common Files\ODBC\Data Sources
This should enable the filemanager to connect to the database. The __login__.asp and __filemanager__preferences__.asp scripts are the only scripts which access the database.
 
 

Create Users

Creating user accounts will allow successful logon and use of the scripts. Users are defined in the tbl_Admin and tbl_FileManager tables of the database.

Both tbl_Admin and tbl_FileManager will need to be populated with user information to ensure correct login and operation.
The access database comes with some sample data