The Aspera License Entitlement Engine (ALEE) is used to license an Aspera Enterprise Server with a license entitlement. The entitlement acts as a license, licensing your server (deployed on-premise, or in the cloud) against the entitlement where the license is based upon volume of data consumed, measured in GBs.
The ALEE engine depends on making an outbound connection from the machine, on port TCP/443 to Aspera's backend licensing platform. In some cases the port TCP/443 is blocked outbound from your environment. If your environment allows you to connect outbound to port 443 but via forward HTTP proxy, there is a way to make ALEE connect through such a proxy.
To use ALEE you first need to ensure the ALEE service is installed.
You need to know the details of your forward proxy server for HTTPS.
You must have Enterprise Server version 3.6.2 or newer.
Stop the Aspera License Entitlement Engine service [it may not be running]
Open up an elevated (Administrator) command prompt on your Windows server.
Navigate to C:\Program Files (x86)\Aspera\Enterprise Server\alee\bin
Note your install directory may be different, for example e:\ instead of c:\
Inside the \bin directory, remove the service by issuing this command:
License Type: Uses License Server
Local license server last reached in the hour of 2013-07-26 16:00
Remote license server last reached in the hour of 2013-07-26 16:00
Another option is to simply go to https://pdx02-cloud.prod.sentinelcloud.com/ from a browser on the machine. Ensure that your browser makes connections through your proxy server, when testing this.
Turn on debug logging
The asperalee logs are located in c:\Program Files\Aspera\Enterprise Server\var\log\alee
To turn on debugging edit the file C:\Program Files(x86)\Aspera\Enterprise Server\alee\etc\logback.xml
<logger name=”com.sfnt” level=”DEBUG”>
Then restart the Aspera Entitlement Engine Service.
Do not forget to change back to WARN level after you have finished your troubleshooting.