How to Host Connect 3.x plugins and installers on your Connect Server

Description

You may want to host your own IBM Aspera Connect installers for your applications rather than having the downloads served from Aspera's CloudFront CDN. To host your own copies of the installers and Connect browser plugin on your IBM Aspera Connect Server, use the following instructions.

Requirements

These instructions require at minimum Connect Server version 3.5.4.

Note that if you have Connect Server version 3.5.4, you must apply a patch IF you will be using the Connect Server web UI. If you use your own custom web application, it is NOT necessary to patch your server. For instructions on how to patch Connect Server 3.5.4 for Connect 3.6 and above, see https://support.asperasoft.com/entries/93944558-How-to-patch-Connect-Server-for-Connect-3-6

Instructions

1. Download the latest Connect SDK 3.x from the Aspera Developer Network.

2. Create a folder named connect in the following location, based on your system:

  • Linux: /opt/aspera/var/webtools/connect
  • Mac OS X: /Library/Aspera/var/webtools/connect
  • Windows (64 bit): C:\Program Files (x86)\Aspera\Enterprise Server\var\www\connect
  • Windows (32 bit): C:\Program Files\Aspera\Enterprise Server\var\www\connect

3. Copy the contents of the Connect SDK to your new connect folder.

You could do this with the following command, using your path to the Connect SDK folder:

On Linux
cp -r /path/to/ConnectServerSDK/. /opt/aspera/var/webtools/connect/

On Mac OS X
cp -r /path/to/ConnectServerSDK/. /Library/Aspera/var/webtools/connect/

On Windows
xcopy /E C:\path\to\ConnectServerSDK\. "C:\Program Files (x86)\Aspera\Enterprise Server\var\www\connect\"

4. Open the connectinstaller-4.js file from the Connect SDK which should now be found at the following:

  • Linux: /opt/aspera/var/webtools/connect/v4/connectinstaller-4.js
  • Windows: C:\Program Files (x86)\Aspera\Enterprise Server\var\www\connect\v4\connectinstaller-4.js

Find the variable updatesURL, and ensure it is set to connectOptions.sdkLocation, as below:

var updatesURL = connectOptions.sdkLocation;

If it is not, set it as above. Older versions of the SDK (prior to 3.6.6) would require this change.

Save the file.

5. Edit your directory listing scripts.

The first script file may be found in the following locations based on your system:

  • Linux: /opt/aspera/var/webtools/scripts/aspera-dirlist.pl
  • Mac OS X: /Library/Aspera/var/webtools/scripts/aspera-dirlist.pl
  • Windows (64 bit): C:\Program Files (x86)\Aspera\Enterprise Server\var\www\user\default.asp
  • Windows (32 bit): C:\Program Files\Aspera\Enterprise Server\var\www\user\default.asp

For Linux and Mac OS X, open the file in a text editor and find the following line:

$CONNECT_AUTOINSTALL_LOCATION = "//d3gcli72yxqn2z.cloudfront.net/connect/v4";

Replace the line above with the line below. This will cause the Connect installers and plugins to come from your own server rather than from Aspera:

$CONNECT_AUTOINSTALL_LOCATION = "/aspera/connect/v4";

For Windows, open the file in a text editor and find the following line:

CONNECT_AUTOINSTALL_LOCATION = "//d3gcli72yxqn2z.cloudfront.net/connect/v4"

Replace the line above with the line below. This will cause the Connect installers and plugins to come from your own server rather than from Aspera:

CONNECT_AUTOINSTALL_LOCATION = "/aspera/connect/v4"

Save the changes to your file.

The next script may be found in the following locations:

  • Linux: /opt/aspera/var/webtools/aspera-dirlist.js
  • Mac OS X: /Library/Aspera/var/webtools/aspera-dirlist.js
  • Windows (64 bit): C:\Program Files (x86)\Aspera\Enterprise Server\var\www\user\aspera-dirlist.js
  • Windows (32 bit): C:\Program Files\Aspera\Enterprise Server\var\www\user\aspera-dirlist.js

Open the file in a text editor and find the following line:

CONNECT_AUTOINSTALL_LOCATION + '/connectinstaller-4.min.js',

Replace the line above with the line below:

CONNECT_AUTOINSTALL_LOCATION + '/connectinstaller-4.js',

 Save the changes to your file.

6. WINDOWS ONLY

With Internet Information Services (IIS) there may be certain settings in place that block the Connect installers from being accessible on your server. You will need to edit your IIS configurations to ensure your users can download the installers.

IIS 7 and above

i. First, create a file named web.config and open it in a text editor. Paste the following content:

<?xml version="1.0"?>
<configuration>
   <system.webServer>
       <security>
          <requestFiltering>
               <hiddenSegments>
                   <remove segment="bin" />
               </hiddenSegments>
           </requestFiltering>
       </security>
       <staticContent>
    <mimeMap fileExtension=".dmg" mimeType="application/octet-stream" />
</staticContent>
   </system.webServer>
</configuration>

The above remedies the common situation where the contents of bin folders on IIS servers are blocked. It also remedies the situation where DMG files are blocked by defining the MIME type for DMGs.

Save the file in the following location: C:\Program Files (x86)\Aspera\Enterprise Server\var\www\connect\v4\bin

ii. Second, create another file named web.config and open it in a text editor. Paste the following content:

<?xml version="1.0"?>
<configuration>
    <system.webServer>
        <staticContent>
            <mimeMap fileExtension=".nmf" mimeType="application/octet-stream" />
            <mimeMap fileExtension=".pexe" mimeType="application/octet-stream" />
        </staticContent>
   </system.webServer>
</configuration>

The above remedies the situation where lesser known file extensions are blocked (in this case .nmf and .pexe) by defining their MIME types. This configuration file fixes an issue with the Connect connection and installer being launched on Chrome.

Save the file in the following location: C:\Program Files (x86)\Aspera\Enterprise Server\var\www\connect\v4\plugin\chrome

IIS 6

i. Open the IIS manager and right click on the website being used for your Connect Server. Select Properties and click on the HTTP Headers tab.

ii. Select Mime Types, then click New. You will add 3 MIME types by filling in the Extension and the MIME type for each. The details for the types you will add are the following:

     a. Extension: .dmg Mime type: application/octet-stream

     b. Extension: .nmf Mime type: application/octet-stream

     c. Extension: .pexe Mime type: application/octet-stream

7. Your Connect Server is now hosting Connect 3.6 plugins and installers.

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk