Enterprise
Edition

 

Installing FileUpEE for ASP

Upgrading to a New Version of FileUpEE

If you are upgrading to a new version of FileUpEE, before installing the new version, remove the old version.

Automatic Installation

To create 3-tier upload and 3-tier download applications, you must install FileUpEE on both the web server and the file server.

To run the automatic installation, double-click FileUpEE.exe, and follow the InstallShield instructions.

During installation you will be asked if the machine on which you are installing is a web server or a file server. If you are installing on a development machine that functions as both a web server and a file server, select "Web server."

Manual Installation

To create 3-tier upload and 3-tier download applications, you must install FileUpEE on both the web server and the file server.

FileUpEE includes two sets of dll files in the folders COM and DotNet. The dlls in COM work only with ASP. The dlls in DotNet work with both ASP and ASP.NET, and cannot be installed on a server that does not have the ASP.NET Framework. If you are installing FileUpEE for ASP only and do not have the ASP.NET Framework, register the dlls in the COM folder. For instructions on installing the ASP/ASP.NET version of FileUpEE, see Installing FileUpEE for ASP.NET.

To install FileUpEE the first time, run the automatic installation. Once InstallShield has unpacked the dll files that contain FileUpEE, you can re-install FileUpEE manually (if, for example, you are moving FileUpEE to a different server):

  1. Open a command prompt window and move to the directory FileUpEE\COM.
    For example, enter cd Program Files\SoftArtisans\FileUpEE\COM.


  2. Enter regsvr32 FileUpEE.dll. A dialog box will inform you that FileUpEE.dll registered successfully; click Ok.


  3. Enter regsvr32 MimeClient.dll. A dialog box will inform you that MimeClient.dll registered successfully; click Ok.


  4. Enter regsvr32 FileUpEEProgress.dll. A dialog box will inform you that MimeClient.dll registered successfully; click Ok.


  5. Enter iisreset to reset IIS.


Top

Installing the ISAPI Filter

For security reasons, FileUpEE's automatic installation does not automatically install the ISAPI filter in IIS. To install the filter in IIS:

  1. Open IIS, right-click the machine name icon, and select Properties.

    FileUp's ISAPI filter must be installed at the machine level, not the web site or web application level.

  2. Select the Internet Information Services tab.


  3. From the Master Properties drop-down list, select WWW Service, and click Edit.


  4. Select the ISAPI Filters tab.


  5. Click Add.


  6. In the Filter Properties dialog box, enter the filter name FileUpEE, browse to FileUpEEIsapi.dll, and click Ok.


  7. Restart IIS to load the filter: right-click the machine name icon, select Restart IIS..., select Restart Internet Services from the drop-down list, and click Ok.

Top

Allowing ASP to Process Files with the .upl Extension

FileUpEE's ISAPI filter will intercept requests to files with the extension .upl. After the filter handles a request to a .upl file, the request is forwarded to ASP. To allow ASP to process files with the extension .upl, you must add a script map to IIS (for security reasons, FileUpEE's automatic installation does not add the script map automatically).

In the Windows XP IIS console, the Web Sites and Default web Site nodes have identical properties dialogs. The script maps can be installed in the Web Sites properties, but they will be ignored by IIS. The script maps must be installed from the Default web Site node.
  • Add .upl to the Default web Site's App Mappings
    1. Open IIS, right-click the Default web Site, and select Properties.

    2. Select the Home Directory tab.


    3. Click Configuration.


    4. Select the App Mappings tab.


    5. Click Add.


    6. Browse to asp.dll (typically in C:\WINNT\System32\inetsrv\).


    7. In the Extension field, enter upl.


    8. Select All Verbs.


    9. Check Script Engine, and click Ok.


    OR

  • Add .upl to the Application's App Mappings
    1. Open IIS, right-click your application's virtual directory, and select Properties.


    2. Select the Virtual Directory tab.


    3. Click Configuration.


    4. Select the App Mappings tab.


    5. Click Add.


    6. Browse to asp.dll (typically in C:\WINNT\System32\inetsrv\).


    7. In the Extension field, enter upl.


    8. Select All Verbs.


    9. Check Script Engine, and click Ok.


Top

The ISAPI Filter Temp Directory

The ISAPI filter caches request data before it is processed by ASP or ASP.NET. The location of the cache files can be configured in the Windows registry. By default, the cache location is the system's default directory for cached files, which is determined by the system environment variable TEMP. To set a different ISAPI filter temp directory:

  1. Open the Start menu, and select Run.
  2. Enter regedit and click Ok.
  3. Open HKEY_LOCAL_MACHINE\SOFTWARE\SoftArtisans\FileUpEe\Parameters.
  4. Right-click FileUpEETempDir and select Modify.
  5. In Value Data, enter the path and folder name.

The ISAPI filter temp directory must be on a local drive, not on a network shared drive. The ISAPI filter writes to the server hard drive as the local SYSTEM account and this account does not have access to network drives.

To change the system's default directory for cached files, reset the TEMP environment variable, as follows:
  • Open the Control Panel.
  • Select System.
  • Select the Advanced tab.
  • Click Environment variables...
  • Select TEMP from the System Variables list.
  • Click Edit.
  • Enter a new Variable Value, and click Ok.

Top

The Resumable Upload Status Databases

In a resumable upload, FileUpEE saves information about the upload in two upload status databases, one on the web server and one on the file server. If the upload from web server to file server is suspended, and the Resume method is called, FileUpEE will get the status of the upload - the number of bytes uploaded to the file server - from the file server database. FileUpEE will then resume the upload from the point at which it stopped.

There are two ways to set the connection string for an upload status database:

  • Set the ResumeConnectionString property for the specified upload database (Web server or file server).

    OR


  • Set the web server and file server connection strings in two udl files. On the web server, in WINNT\system32\fileupee.udl, save the web server's status database connection string. On the file server, in WINNT\system32\fileupee.udl, save the file server's status database connection string.

    To store a database connection string in a udl file:

    1. Go to C:\WINNT\system32.
    2. Right click within the system32 directory and select New -> Text Document.
    3. Name the file fileupee.udl.
    4. Double-click fileupee.udl to open it.
    5. Select the Provider tab.
    6. Select Microsoft Jet 4.0 OLE DB Provider, and click Next.
    7. Browse to FileUpEEWS.mdb if you are at the web server, or FileUpEEFS.mdb if you are at the file server.
    8. Click Test Connection.
The Internet user account must have Read, Write, and Modify access the directories containing the status databases. For the FileUpEE samples, that directory is FileUpEE\doc-samples\samples\features\resume. For resumable uploads in ASP, make sure that the IUSR_MACHINENAME account has Read, Write, and Modify access to this directory. For security reasons the FileUpEE install package does not grant this access.

Top

Copyright © 2005, SoftArtisans, Inc.