Performing Local IBM Aspera Connect Browser Plug-in Installation

Companies that need to host the IBM Aspera Connect Browser Plug-in SDK installers locally can download the Connect SDK file and configure IBM Aspera Faspex on Demand to point to a local copy of the Connect SDK that is hosted on the Faspex server itself, or some other non-standard location. This enables their customers to make their users download Connect from a server of their choice.

Download the Connect SDK zip file from the ADN. Unzip the Connect SDK zip file in /opt/aspera/faspex/connect.

Give Faspex permissions and ownership of the new Connect directory.

Chown the new Connect directory recursively using faspex:faspex, 
and then chmod it with 755. 

# chown -R faspex:faspex /opt/aspera/faspex/connect
# chmod 755 /opt/aspera/faspex/connect

Edit /opt/aspera/faspex/config/faspex.apache.linux.conf.

Add this section:

Alias /connect "C:/Program Files (x86)/Aspera/Faspex/connect" 
<Directory "C:/Program Files (x86)/Aspera/Faspex/connect"> 
   Options -Indexes -FollowSymLinks 
   AllowOverride none 
   Order allow,deny 
   Allow from all 
</Directory>

Change the location from which customers will download IBM Aspera Connect Browser Plug-in.

Edit /opt/aspera/faspex/public/javascripts/connect_auto_install.js.

Change the following line: 

var CONNECT_AUTOINSTALL_LOCATION = '//d3gcli72yxqn2z.cloudfront.net/connect/';

Replace d3gcli72yxqn2z.cloudfront.net with the FQDN that points to
your Faspex service in your environment.

Restart the Faspex Apache service.
```
asctl apache:restart
```