How do I apply a SETINIT license key to Altair SLC on a Linux server?
Altair EmployeeThese steps can be followed to apply a new setinit license for the first time, or to replace an existing license that has expired or that needs to be superseded.
Please note that the legacy "setinit" (wpskey) license method has been phased out in favour of the Altair Units license method. Please refer elsewhere to information on how to apply Altair Units licenses to your SLC software.
Planning for downtime
A replacement setinit license can be applied without interrupting any existing running SLC processes. If any problems arise during the application of the new license file then it may take you a few moments to revert to the old license, and during those moments new SLC processes will not be able to start up. So on a busy production system (with a current non-expired working license) you may wish to schedule a few minutes of downtime so that you can apply the new license, check it is working, and revert to the old license if not.
Instructions for SLC 2023 and later versions
Either log in as root or use the sudo command to set the license for all users (otherwise the license will be applied only for a single user).
If you are replacing an existing license that has not yet expired then you may wish to make a backup of /var/lib/altair/slc/2023/setinit.dat in case there are any problems with the new license such that you might want to revert to the old license.
Your legacy license key can be applied using a command line of the form:
sudo /opt/altair/slc/2023/bin/wps -stdio -setinit < license.wpskey
The compiled key is typically stored at /var/lib/altair/slc/2023/setinit.dat. The file should have read permissions for all users (and the superdirectories must all have read and execute permissions for all users.)
If the license is in (for example) /home/gm/.config/altair/slc/2023/setinit.dat then it is only used by user "gm".
If you get "Permission denied" errors (e.g. "You do not have the relevant write permissions to apply a license to this computer") then it is possible someone else on that system created a previous license. Please rename or remove this setinit.dat file and re-apply the license key.
Instructions for WPS / SLC 4.x versions
Either log in as root or use the sudo command to set the license for all users (otherwise the license will be applied only for a single user).
If you are replacing an existing license that has not yet expired then you may wish to make a backup of /var/lib/worldprogramming/wps/4/setinit.dat in case there are any problems with the new license such that you might want to revert to the old license. Your legacy license key can be applied using a command line of the form:
sudo /opt/worldprogramming/wps-4/bin/wps -stdio -setinit < license.wpskey
The compiled key is typically stored at /var/lib/worldprogramming/wps/4/setinit.dat. The file should have read permissions for all users (and the superdirectories must all have read and execute permissions for all users.)
If the license is in (for example) /home/gm/.config/worldprogramming/wps/4/setinit.dat then it is only used by user "gm".
If you get "Permission denied" errors (e.g. "You do not have the relevant write permissions to apply a license to this computer") then it is possible someone else on that system created a previous license. Please rename or remove this setinit.dat file and re-apply the license key.