Faspex and Connect Server on one Windows system through a single HTTP Server

Faspex and Connect Server on one Windows system through a single HTTP Server

by Arnd Kohrs (arnd@asperasoft.com)

Goal

This article describes how to setup Connect Server on a Windows together with Faspex so that both applications are accessible via a single HTTP server for web interaction from the outside world. The Faspex Apache HTTP server is configured as a reverse-proxy for the Connect Server's IIS. This facilitates deployment in hosted and firewalled environments: I.e.:

Preparation

Install Faspex and Connect Server on the same Windows system. Follow the installation guides.
The Connect Server uses Internet Information Server (IIS) as an HTTP server. IIS should be configured to use port 10080 (or any other free port) for incoming requests. 
Faspex is installed together with an Apache web server which uses port 80/443.

What to do

  1. Bind the IIS web server to the localhost address (127.0.0.1).   Open the IIS Manager and edit the Bindings for the Default Web Site.  Add 127.0.0.1 with port 10080 without hostname.
  2. Add the following lines at the end of the file
    C:\Program Files\Aspera\Faspex\config\faspex.apache.template.conf using notepad:

    ProxyPass /aspera http://127.0.0.1:10080/aspera
    ProxyPassReverse /aspera http://127.0.0.1:10080/aspera
  3. Restart Faspex - execute the following commands in a shell:

    cd \Program Files\Aspera\Faspex
    asctl faspex:uri_namespace /faspex
  4. Edit the following ASP file:
    [Connect Server 2.5 or higher] "C:\Program Files\Aspera\Enterprise Server\var\www\user\default.asp"
    using notepad:
    Override the appURL assignment:
     'appURL = protoScheme & Request.ServerVariables("HTTP_HOST") & Request.ServerVariables("URL")
    appURL = Request.ServerVariables("URL")
    Override the strServerName assignment:
     'strServerName = LCase(Request.ServerVariables("SERVER_NAME"))
    strServerName = "aspera.my-domain.com"
  5. In the file C:\Program Files (x86)\Aspera\Enterprise Server\etc\aspera.conf
    Make sure that in the block there is an enry AsperaServer, i.e.:
    <WEB 
    ...
    AsperaServer="aspera.my-domain.com"
    ...
    />
  6. Disable "Windows Integrated Authentication" for the /aspera/user/ folder using IIS Manager, so that IE is forced to use "Basic Authentication", since "Windows Integrated Authentication" does not work for proxied IIS servers.

Done.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk