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

  1. Use a text editor like Notepad or Notepad++ and open the 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=true
    license.hwu.hosted.authorization.password=
    license.hwu.hosted.authorization.token=<YOUR_TOKEN_HERE>
    license.hwu.hosted.authorization.username=
    license.hwu.uri=
    license.hwu.use_client_timezone=true
    license.mode=HWU

  3. To generate the token, log on to Altair One Marketplace and go to https://admin.altairone.com/dashboard, click User Profile and go to the tab Authorized Machines and click Generate Auth Code.

    For additional details, see Panopticon documentation.

  4. Save and close the Panopticon.properties file.

    NOTE:

    From the point where a new Altair One Managed License Token is created, the token must be used within 15 minutes, or otherwise it will become invalid and deleted. When the token gets used for the first time, it gets tied to the hostname and MAC-address of the machine using it. When the Panopticon Docker Compose package is mounted for the very first time, the four container images must be downloaded. In case you find that more than 15 minutes are required for downloading and mounting the containers and then log in at the Panopticon web interface, you will need to stop the containers, generate a new license token, and re-start the containers.

 

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-2024 Altair Engineering Inc. All Rights Reserved.

Intellectual Property Rights Notice | Technical Support