Step 3. Configuration of Altair Units License

Altair Panopticon requires a valid license. There are two options:

  • Managed Altair Units License, where units are provided from Altair One license servers
  • On-premises Altair License Manager and a valid license file added to the license manager

The license settings are entered in a configuration file which is part of the Panopticon Docker Compose package.

 

Managed Altair Units License

Configuration of Managed Altair Units License is done in the file pano-mount/data/panoviz/appdata/Panopticon.properties which you can edit with a text editor like Notepad or similar.

There are three different ways that you can make Panopticon obtain a Managed Altair Units License Token, and each one is described in the Using Managed Altair Units License Via Altair One section in Panopticon Real Time Installation and Reference Guide.

In brief, the three approaches are:

  • Option 1 - Use an authorization code generated through Altair One
  • Option 2 - Directly use your Altair One credentials in Panopticon.properties
  • Option 3 - Manually create a license authorization token using the ALMutil command line tool. This option lets you create a token of type ANYHOST, which is not bound to a specific MAC address. This is what you need for the purpose of being able to re-build (stop and start) your Panopticon docker container and still be able to continue using the same Managed Altair Units License Token.

 

On-premises Altair License Manager

  1. Use a text editor like Notepad or Notepad++ and open the following pano-mount/data/panoviz/appdata/Panopticon.properties file.
  2. Find the properties with names starting with “license” and set the values as follows:

    license.hwu.hosted=false
    license.hwu.hosted.authorization.password=
    license.hwu.hosted.authorization.token=
    license.hwu.hosted.authorization.username=
    license.hwu.uri=6200@host1:6200@host2
    license.hwu.use_client_timezone=true
    license.mode=HWU

  3. For the license.hwu.uri property, if you are running more than one Altair License Manager, you can enter them with colon sign as a separator. Colon sign is the required separator character in this context when running on a Linux operating system, and the Docker container is a Linux based container.

    For additional details, see Panopticon documentation.

  4. Save and close the Panopticon.properties file.

 

Best Practices When Referencing the Physical Host

When using Panopticon in a Docker Container, and you want to use an Altair License Manager installed on the same physical host that runs Docker, you must specify host.docker.internal in the settings, instead of localhost. 

Example:

license.hwu.uri=6200@host.docker.internal

Likewise, if you want to connect to a JDBC database running on the physical host, from Panopticon in a Docker container, you can do so by using a JDBC URL that specifies host.docker.internal instead of localhost.

Example, for PostgreSQL database:

jdbc:postgresql://host.docker.internal:5432/postgres

 

 

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

Intellectual Property Rights Notice | Technical Support