License Variable for NX9? 1

lharrison · May 14, 2014

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

jpetach · May 14, 2014

Lharrison,

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

Toost · May 14, 2014

Oh, bad news.
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

looslib · May 14, 2014

Microsoft didn't write the license manager, so don't blame them for the application developer using the registry.

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

lharrison · May 14, 2014

Well that's sort of a bummer, a little more difficult than it used to be. Thanks for pointing me in the right direction!

lharrison · May 14, 2014

If anyone is curious, it seems like the registry settings live here:
[HKEY_CURRENT_USER\Software\Siemens_PLM_Software\Common_Licensing]
"NX_BUNDLES"="NX12100N"

http://www.eng-tips.com/

phillpd · Jul 29, 2014

If the client install does not include FLEXLM, how can the bundles be subsequently set by use of a script ?

NX 6.0.5.3, NX 9.0.2.5
NX 10 (Testing)
Windows 7 64 (Windows 8.1 Tablet)

Arkance/PhoeNX · Jul 29, 2014

Create a reg file by exporting the key from the registry.

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