HTTP Commander 6.0 (Standard
version) installation
Server's system requirements:
Installation 1-4 steps:
1. Creating application:
-
For package with Windows Installer (Setup.exe file): run
Setup.exe, Click "Next" and install HTTP Commander to HTCOMNET virtual
directory. After that setup creates virtual C:\Inetpub\wwwroot\HTCOMNET folder,
copies all files to this folder and creates web-application in it.
For package without Installer: Copy HTCOMNET folder to your
web server's wwwroot\ folder (in most cases it is C:\Inetpub\wwwroot\) ,
Also you need to create "Application" in vitrual HTCOMNET folder in IIS
console: See screeshots at HTCOMNET\WebApp.htm
Description: Open Control panel->Administrative tools->
Internet Information Services->Expand "Default web site", right mouse click
at the "HTCOMNET" folder and select "Properties" in context menu.
In the HTCOMNET properties dialog box open "Directory" tab and click "Create"
button (create Application), click "ok" .
-
Set content expiration for HTCOMNET application. It is needed for fast upload
images and .js files from users browser's cache. It is very important becouse
HTTP Commander has a lot of images and Java Script functions (in .js files) and
this data must be stored in cache and dont checked for new versions!
See screenshots at HTCOMNET\ContentExpiration.htm
Description: Open Control panel->Administrative tools->Internet
Information Services->Expand "Default web site", right mouse click at the
"HTCOMNET" folder and select "Properties" in context menu.
In the HTCOMNET properties dialog box open "HTTP headers" tab, check "Enable
content expiration", select "Expire on" and enter date 1.1.2010, click "ok".
-
For Windows 2003 Server you need to allow ASP.NET running. Open Control
Panel->Add and Remove programs->Add/remove Windows Component->Select
Application Server in list, click "Details" button. In new window check ASP.NET
and click Ok.
Check that ASP.NET execution enabled on server. Open Control
panel->Administrative tools-> Internet Information Services->Web
Sirvices Extensions-> Select "ASP.NET v #.#" in list and click "Allow"
button.
2. Settings: Open HTCOMNET\web.config
file in XML editor or Windows Notepad or WordPad. This is XML based file and it
stores most part of settings for application. Keep in mind that XML is case
sensitive , data between <!-- --> tags are comments.
We are strongly recommend to make backup copy of web.config file before modify
it!
- Find <add key="ADMIN_NAME" value= "A" /> element and change default
name "A" for Administrator. Only Administrator will have access to Admin panel
of HTTP Commander.
- Find <add key="ADMIN_PASSWORD" value="A" /> element and change default
password for Administrator.
Run HTCOMNET/HashPassword.aspx to hash password.
Don't use here name and password of real Administrator on server! It is
not secure!
- Find <add key="DATABASES_DIR" value="C:\HTCOMNET_DATA\" /> element.
DATABASES_DIR is folder that will store databases and log files. By default
it is C:\HTCOMNET_DATA\, Change it if you want to use another folder.
Create DATABASES_DIR folder and Set NTFS "Modify", "Read and execute", "List
folder contents", "Read", "Write" permissions for ASPNET and IUSR_MACHINENAME
users to this folder! Keep in mind that
ASPNET user is member of "Users" group. So permissions seted for
"Users" can replace permissions for ASPNET.
- Find <add key="TEMP_DIR" value="C:\HTCOMNET_TEMP\" /> element. TEMP_DIR
will store temporary files for Upload operations. By default it is C:\HTCOMNET_TEMP\,
Change it if you want to use another folder.
Create TEMP_DIR folder and Set NTFS "Modify", "Read and execute", "List folder
contents", "Read", "Write" permissions for ASPNET and IUSR_MACHINENAME users
to this folder! Keep in mind that
ASPNET user is member of "Users" group. So permissions seted for
"Users" can replace permissions for ASPNET.
- Find <add key="HCADSI_USER_NAME" value="" /> and <add key="HCADSI_USER_PASSWORD"
value="" /> elements.
Name and password of account under which role will execute hcADSI module(See
project in HTCOMNET\hcADSI ). hcADSI module creates FTP folders(if USE_FTP_UPLOAD_DOWNLOAD
key seted to "Yes").
Sometimes hcADSI module needs higher permissions than it has guest IUSR_COMPUTERNAME
user.
hcADSI module can work under any specified user's role. Therefor you can set
name and password of user that have permissions to create FTP folders. If
user name equal with emty string hcADSI will work under IUSR_COMPUTERNAME
user role. Format of HCADSI_USER_NAME: DOMAINNAME\Username
if USE_FTP_UPLOAD_DOWNLOAD key seted to "No" set Name and Password to empty
strings.
- To make FTP Upload/Download feature find group of USE_FTP_UPLOAD_DOWNLOAD,
..., FTP_FOLDER_NAME keys.
To turn on feature set USE_FTP_UPLOAD_DOWNLOAD value to "Yes". Set
FTP_SERVER_NAME equal with your server name there FTP site installed. Set
FTP_SERVER_GLOBAL_NAME equal to your FTP site's global name. And FTP_SITE_INDEX.
You can find index of your FTP site running script "C:\Inetpub\AdminScripts\adsutil.vbs
ENUM MSFTPSVC". See index at the bottom line. something like [/MSFTPSVC/1]
- site index is 1
- Find <httpRuntime maxRequestLength="1048576" executionTimeout="3600"
/>. Set executionTimeout's value (in seconds) greater than the amount of
time you expect uploads or downloads to take.
Also find <sessionState timeout="60" /> and set timeout's
value (IN MINUTES!) greater than the amount of time you expect uploads or
downloads to take.
- Also you can set some other values. See comments for all settings in web.config
file (between <!-- --> tags).
3. Administration:
-
Run http://localhost/HTCOMNET/adminpanel.aspx to login to Admin Panel. At HTTP
Commander authentication form enter Administrator's name and password (defined
by ADMIN_NAME and ADMIN_PASSWORD parameters).
-
Click "Users and Groups" link to add users and groups. If you already have
users database on web site and don't want to make extra please contact with
developer.
-
Click "Set folders for user or group" link to setup folders for users and
groups.
4. Run:
- Your users should run http://localhost/HTCOMNET/Default.aspx in their browsers
to run HTTP Commander. Change "localhost" with "computername" or "www.yoursite.com"
if your users running HTTP Commander from Local Network or Internet.
5. Upgrade version 5.1 to 6.0
- web.config files are not compatible. You need to set values in web.config
file of 6.0 version again. Set the same DATABASES_DIR and TEMP_DIR as in 5.1
version
- Databases compatible except for one new "Properties" field. Open
file DATABASES_DIR\FoldersST.xml of 5.1 version in Notepad. Under each <user>
node add "<properties />" or "<properties>|</properties>"
if 2 folders defined for user or "<properties>||</properties>"
if 3 folders defined, etc. Save file and run. If records added correct 6.0
version will work with this database.
Troubleshooting:
- To Restart application! 1) Close all w3w procceses. 2) Delete C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary
ASP.NET Files\HTCOMNET folder 3) Open file HTCOMNET\web.config in NotePad
and save it without changes.
- Error like "Column 'properties' does not belong to table user."
after user login. You are running version 6.0, but it uses database of old
5.1 version. Change DATABASES_DIR key in HTCOMNET\web.config file or upgrade
your database (See section 5.).
- Error like "Access to path '...' is denied." while running
or working with application. Check that ASPNET and IUSR_MACHINENAME users
has READ, WRITE, MODIFY NTFS permissions to specified path. Keep in mind that
ASPNET user is member of "Users" group. So permissions seted for
"Users" can replace permissions for ASPNET.
- You got page with top "<%@ Page Language="vb"
AutoEventWireup="false" Codebehind="adminpanel.aspx.vb" Inherits="Academic.adminpanel"%>
If you see this label then you need to install .NET Framework 1.1 on the server
for correct running .ASPX pages. See ReadMe.htm"
while running adminpanel.aspx then you don't have .NET framework installed
or need to allow ASP.NET run on web server.
- Error "Access is denied"
while first running any page of HTTP Commander.
How to fix: 1. Open the Domain Controller Security Policy from the Administrative
Tools folder. 2. Navigate through Security Settings / Local Policies / User
Rights Assignment. 3. In the right-hand pane, double-click Impersonate a client
after authentication. 4. Select Define these policy settings in the Security
Policy Setting dialog. 5. Press Add. 6. Press Browse. 7. In the Select Users
or Groups dialog, select the IWAM_MASHINENAME account name and press Add.
8. Press OK, OK, and OK. 9. Restart server.
Optional:
-
You can translate all messages of HTTP Commander to your own language. See
HTCOMNET\Languages\Readme.txt
-
In HTTP Commander Standard users can run HTTP Commander using fomat of URL:
http://localhost/HTCOMNET/Default.aspx?user=usernamehere&password=passwordhere.
You can use this format if your users already authenticated on other page of
your web site. HTTP Commander will check name and password and willn't ask it
if they are correct.
-
Your users can run HTTP Commander using fomat of URL:
http://localhost/HTCOMNET/Default.aspx?path=locationhere
Users will have access to path automaticaly if it is enabled for them in
Admin Panel . You can use this format to make direct access or link on other
pages to folder.
-
You can add extra file types that users can to Edit or View in
HTCOMNET\Data\Properties.xml file.
-
You can add extra icons for files in HTCOMNET\Data\Properties.xml file and
HTCOMNET\Images\EXT folder.
-
You can use your own Text files Editor (See HTCOMNET\Editfile.aspx for deatils)
Extra modifications:
-
Please write to developer if you need to have extra features of to fix
something. Extra customizations costs 20$/hour or free in some cases. We
are always ready to help.
HTTP Commander.
WEB: http://www.http-com.com
Support E-mail: sprunsky@http-com.com