SoftArtisans FileUpEE Guide

Installing FileUpEE

Automatic Installation
Manual Installation
Installing FileUpEE for ASP.NET
Installing the ISAPI Filter
Allowing ASP.NET to Process Files with the .upl Extension
Allowing ASP.NET to Process Files with the .uplx Extension
The ISAPI Filter Temp Directory
The Resumable Upload Status Databases

Automatic Installation

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

Manual Installation for ASP

Note: 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.

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):

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

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

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

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

Enter iisreset to reset IIS.

Top

Installing FileUpEE for ASP.NET

FileUpEE's .NET assemblies are in SoftArtisans\FileUpEE\DotNet. The assemblies - FileUpEE.dll, MimeClient.dll, and FileUpEEProgress.dll - can be made accessible either globally or at the application level. If you would like the .NET assemblies to be available to all applications, install the dll files in the Global Assembly Cache (GAC). To make the assemblies available to a single application, include at the application's top level, a bin directory containing the dll files.

Installing FileUpEE for .NET Globally

To make FileUpEE available to all .NET applications on your machine:

Open a command prompt window and move to the directory FileUpEE\DotNet.

Enter gacutil /i FileUpEE.dll.

Enter gacutil /i MimeClient.dll.

Enter gacutil /i FileUpEEProgress.dll.

Open the file machine.config (in C:\WINNT\Microsoft.NET\Framework\v1.0.3705\CONFIG).

Add the following lines to the assemblies node of machine.config:

<add assembly="FileUpEE, Version=x.x.x.x, Culture=neutral, PublicKeyToken=f593502af6ee46ae"/>
<add assembly="MimeClient, Version=x.x.x.x, Culture=neutral, PublicKeyToken=f593502af6ee46ae"/>


<add assembly="FileUpEEProgress, Version=x.x.x.x, Culture=neutral, PublicKeyToken=f593502af6ee46ae"/>

Add the following line to the httpHandlers node of machine.config:

<add verb="GET,HEAD,POST" path="*.uplx" type="System.Web.UI.PageHandlerFactory" />

before

<add verb="GET,HEAD" path="*" type="System.Web.StaticFileHandler" />

<add verb="*" path="*" type="System.Web.HttpMethodNotAllowedHandler" />

The version attribute of the add assembly node must correspond exactly to the version of the assembly (dll file) added to the GAC. If you add a new version of FileUp to the GAC using the gacutil command, update the dll version attributes in machine.config. To get the exact version of the dll file, right-click the dll and select the Properties tab.

Installing FileUpEE for .NET at the Application Level

Within your application, include a top level direcory called bin that contains FileUpEE.dll, MimeClient.dll, and FileUpEEProgress.dll. The bin directory should contain the dll files you will find in FileUpEE\DotNet, not the files in FileUpEE\COM.

Create a text file containing the following lines, and save it as web.config. Save web.config at the top level of your application.

<configuration>
<system.web>
<compilation numRecompilesBeforeAppRestart="15">
<compilers>
</compilers>
<assemblies>
<add assembly="FileUpEE, Version=x.x.x.x, Culture=neutral, PublicKeyToken=f593502af6ee46ae"/>
<add assembly="MimeClient, Version=x.x.x.x, Culture=neutral, PublicKeyToken=f593502af6ee46ae"/>                
<add assembly="FileUpEEProgress, Version=x.x.x.x, Culture=neutral, PublicKeyToken=f593502af6ee46ae"/>
<add assembly="*" />
</assemblies>
</compilation>          
<httpHandlers>
<add verb="*" path="*.uplx" type="System.Web.UI.PageHandlerFactory"/>
</httpHandlers>
</system.web>
</configuration>

The version attribute of each add assembly node must correspond exactly to the version of the assembly (dll file) in the application's bin directory. If you update the dlls in the bin directory, update the dll version attributes in web.config. To get the exact version of the dll file, right-click the dll and select the Properties tab.

Top

Installing the ISAPI Filter

FileUpEE's automatic installation package will install the ISAPI filter in IIS. You can re-install the filter manually (if, for example, you move FileUpEE to a different machine), as follows:

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

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

Select the Internet Information Services tab.

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

Select the ISAPI Filters tab.

Click Add.

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

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.

If you are testing FileUpEE with a beta release of IIS 6.0 on Windows .NET Server, the Web site must be configured to run in IIS 5 mode. The filter cannot be installed properly if the site is in IIS 6 mode. To run IIS 6 in IIS 5 mode:

In IIS, right-click the Web site, and open Properties.
Select the Service tab.
Check Run Web service in IIS 5.0 isolation mode.

Top

Allowing ASP to Process Files with the .upl Extension

FileUpEE's ISAPI filter will intercept requests to files with the extension .upl. FileUpEE's automatic installation adds the appropriate script map to IIS so that requests for .upl files are handled by the filter and then forwarded to ASP. If you reinstall FileUpEE manually (if, for example, you move FileUpEE to a different server), you will need to add the following IIS script map:

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

Allowing ASP.NET to Process Files with the .uplx Extension

FileUpEE's ISAPI filter will intercept requests to files with the extension .uplx. FileUpEE's automatic installation adds the appropriate script map to IIS so that requests for .uplx files are handled by the filter and then forwarded to ASP.NET. If you reinstall FileUpEE manually (if, for example, you move FileUpEE to a different server), you will need to add the following IIS script map:

Add .uplx 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 aspnet_isapi.dll (typically in C:\WINNT\Microsoft.NET\Framework\v1.0.3705\).
7. In the Extension field, enter uplx.
8. Select All Verbs.
9. Check Script Engine, and click Ok.
OR
Add .uplx 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 aspnet_isapi.dll (typically in C:\WINNT\Microsoft.NET\Framework\v1.0.3705\).
7. In the Extension field, enter uplx.
8. Select All Verbs.
9. Check Script Engine, and click Ok.

Under ASP.NET, FileUpEE's progress indicator is handled by the ISAPI filter. So, to display accurate progress indication, upload to a file with the .uplx extension.

Top

The ISAPI Filter Temp Directory

The ISAPI filter caches request data before it is processed by ASP or ASP.NET.

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.

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:

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

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 ASP.NET, if impersonation is disabled, make sure that the ASPNET account has Read, Write, and Modify access to the directory. If impersonation is enabled for ASP.NET, set permissions as you would for ASP. For security reasons the FileUpEE install package does not grant this access.

Top