Proxy Server Configuration

When using Managed Licensing, where the Altair License Manager server is hosted by Altair in the cloud, it is possible to let Panopticon go via a proxy server when communicating with the ALM. For example, this can be useful when the Panopticon server needs to be isolated from general internet connections.

Scenario 1: Transparent proxy. This does not require any special configuration.

Scenario 2: Traditional proxy. Using Altair License Utility (ALMutil) and filling in details on the Managed Licensing tab, the proxy server details are written to a configuration file in the home directory of the user, from where the Altair Licensing SDK (ALSDK) that is embedded in Panopticon, will read them. This is part of the Panopticon license checkout, and the proxy server details are used for communication with the license manager. This means that Altair License Utility must be run under the user that also runs Tomcat and Panopticon.

Using CLI ALMutil, there is also the option of setting up a system-wide configuration file of the same kind.

 

Using a command with the following format:

almutil -proxy -system -host <host> -port <port> [-user <user ID> -passwd <password>]

You will produce the following configuration files which on a Linux system by default are saved under /usr/local/altair:

  • altair_hostedhwu.cfg
  • altair_hostedhwu_ex.cfg

NOTE:  If the proxy requires no credentials, the second file is empty. These .CFG files are created in /usr/local/altair unless the environment variable ALM_HHWU_CONFIG is defined. If you would like these files to be created in a different directory, define the variable ALM_HHWU_CONFIG before running almutil. For example: export ALM_HHWU_CONFIG=/apps/altair/license

To test the connectivity with the Altair One cloud license servers, run the following command:

almutil -conntest

Next, authorize the Panopticon host machine by running the command below. Here NNNN should be replaced with the Auth Code generated from the Altair One account.

almutil -a1auth -system -anyhost -code NNNNN

Finally, configure Panopticon in Panopticon.properties with the following values:

license.hwu.hosted.authorization.password=
license.hwu.hosted.authorization.token=<auth code>
license.hwu.hosted.authorization.username=
license.hwu.hosted=true
license.hwu.uri=<proxyport>@<proxyhost>
license.hwu.use_client_timezone=true
license.mode=HWU

 

 

 

(c) 2013-2024 Altair Engineering Inc. All Rights Reserved.

Intellectual Property Rights Notice | Technical Support