License Variable for NX9?
License Variable for NX9?
(OP)
We recently started upgrading to NX9 and noticed that the familiar UGS_LICENSE_BUNDLE environmental variable is no longer used. Internally, we have a custom program written to display who currently has licenses, and toggle buttons so users can easily select an unused license. Previously, new license were selected by altering the UGS_LICENSE_BUNDLE variable, but since it is no longer used, this is not possible. I tried creating a variable that adheres to the new 'SPLM_' convention, but it doesn't appear to work. Anyone know where NX9 stores what license bundles you currently have selected?
Bruce
Bruce





RE: License Variable for NX9?
The bundle data is persisted in the Windows registry.
There are two interfaces.
%UGII_BASE_DIR%\ugflexlm\LicenseTool.exe (Interactive GUI)
%UGII_BASE_DIR%\ugflexlm\lictool.exe (command line)
The --setbundle or --unsetbundle options could be used by the script that is currently setting en environment variables.
Hopefully this is helpful,
Joe
Usage:
Siemens License Tool CLI [ 6.1.3.1 ]
Copyright (c) 2012 Siemens PLM Software Inc. All rights reserved.
Allowed Options:
-h, --help Print Help (this message) and exit
-v, --version Print version information and exit
-c, --copyright Print copyright information and exit
--getbundle [--components] Get information of all bundle(s) and
component(s)
--setbundle <name> Set bundle(s), example:
--setbundle "BUNDLE1" "BUNDLE2"
--unsetbundle --all | <name> Unset bundle(s), example:
--unsetbundle --all
--unsetbundle "BUNDLE1" "BUNDLE2"
--getborrowable Get borrowable license(s)
--getborrowed Get borrowed license(s)
--borrow <name> [--days <num_of_days>]
Borrow license(s), example:
--borrow "LICENSE1" "LICENSE2"
--borrow "LICENSE1" "LICENSE2" --days 30
--return <name> Return license(s), example:
--return "LICENSE1" "LICENSE2"
--getcid Get composite host ID
--getid Get host ID
--getclientinfo Get the following information from client
side:
Host name
User name
FNP SDK version
License server
--getserverinfo Get the following information from server
side:
Sold to ID
Webkey
Issuer
Version
Toolkit version
RE: License Variable for NX9?
This makes my life more difficult. I hate registry settings.
Now our install script needs to modify the registry when the users themselves perform the NX install.
I can't understand why Microsoft is so obstinate in mixing the OS with the applications.
Sooner or later the registry is corrupted and a complete reinstall is required.
Regards,
Tomas
RE: License Variable for NX9?
The registry does provide a 'hidden' location for applications to store settings, but it is not required. Application settings can be set in files with that applications folder structure.
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
RE: License Variable for NX9?
RE: License Variable for NX9?
[HKEY_CURRENT_USER\Software\Siemens_PLM_Software\Common_Licensing]
"NX_BUNDLES"="NX12100N"http://www.eng-tips.com/
RE: License Variable for NX9?
NX 6.0.5.3, NX 9.0.2.5
NX 10 (Testing)
Windows 7 64 (Windows 8.1 Tablet)
RE: License Variable for NX9?
Then import into the registry in your script by doing:
regedit.exe /s c:\name_your_exported_reg_file.reg
Anthony Galante

Senior Support Engineer
NX5.0.6, NX6.0.5, NX7.5.5, NX8.0.0 -> NX8.0.3
NX8.5.0 -> NX8.5.3, NX9.0.0 -> NX9.0.2, NX10 Beta
RE: License Variable for NX9?
And to "return" bundles using the registry ?
NX 6.0.5.3, NX 9.0.2.5
NX 10 (Testing)
Windows 7 64 (Windows 8.1 Tablet)
RE: License Variable for NX9?
Anthony Galante

Senior Support Engineer
NX5.0.6, NX6.0.5, NX7.5.5, NX8.0.0 -> NX8.0.3
NX8.5.0 -> NX8.5.3, NX9.0.0 -> NX9.0.2, NX10 Beta
RE: License Variable for NX9?
I guess a registry key setting "NX_BUNDLES"="" would work.
NX 6.0.5.3, NX 9.0.2.5
NX 10 (Testing)
Windows 7 64 (Windows 8.1 Tablet)
RE: License Variable for NX9?
You can specify a maximum of two, so specify their normal one and then add the ADVDES or DESIGNER as a secondary.
It will then be used if the first one is unavailable or if there is a missing function in the first bundle that is in the second.
Anthony Galante

Senior Support Engineer
NX5.0.6, NX6.0.5, NX7.5.5, NX8.0.0 -> NX8.0.3
NX8.5.0 -> NX8.5.3, NX9.0.0 -> NX9.0.2, NX10 Beta
RE: License Variable for NX9?
However if you don't use that tool and set the UGS_LICENSE_BUNDLE variable manually, either by setting it in the environment variables or through a script or env file, NX will work.
This will only work if the registry setting doesn't exist though, so don't use the Licensing Tool.
Anthony Galante

Senior Support Engineer
NX5.0.6, NX6.0.5, NX7.5.5, NX8.0.0 -> NX8.0.3
NX8.5.0 -> NX8.5.3, NX9.0.0 -> NX9.0.2, NX10 Beta
RE: License Variable for NX9?
NX 6.0.5.3, NX 9.0.2.5
NX 10 (Testing)
Windows 7 64 (Windows 8.1 Tablet)
RE: License Variable for NX9?
then if you set the variable manually it won't read it because the registry setting exists.
Anthony Galante

Senior Support Engineer
NX5.0.6, NX6.0.5, NX7.5.5, NX8.0.0 -> NX8.0.3
NX8.5.0 -> NX8.5.3, NX9.0.0 -> NX9.0.2, NX10 Beta
RE: License Variable for NX9?
http://www.tlmgi.com/licenseusage/licenseusage.asp...
I have been using this for NX7.5 & 9.0 works great and the price is right.
John Joyce
N.C. Programming Supervisor
Barnes Aerospace, Windsor CT
NX6, NX7.5,NX8.5, NX9.0
Vericut7.3