×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

License Variable for NX9?

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

RE: License Variable for NX9?

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

RE: License Variable for NX9?

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

RE: License Variable for NX9?

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

RE: License Variable for NX9?

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

RE: License Variable for NX9?

(OP)
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/

RE: License Variable for NX9?

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)

RE: License Variable for NX9?

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

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?

Thanks Anthony.

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?

Why would you want to?

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?

Most of our licensing is floating, but we have a couple of ADVDES and DESIGNER bundles that we "share" on an as needed basis. Once used, they need to be "returned".

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?

Are you specifying only one bundle then for a user?
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?

I just remembered and ran a test to check that if you use the Licensing Tool to set the bundle, it will set it in registry, not as a user variable (like in the previous releases of NX).
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?

I'm confused now, is UGS_LICENSE_BUNDLE still valid 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?

yes, just don't use the license tool to pick a bundle, otherwise it doesn't create the variable and sets in registry instead.
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?

If your trying to see who has the available licenses there is a free tool available from:

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

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Resources