SPLMLicensing User Guide
SPLMLicensing User Guide
SPLMLicensing User Guide
Overview ............................................................................................................................... 4
Fundamentals of Siemens PLM Licensing ............................................................................... 4
What Defines Siemens PLM Licensing? ............................................................................................ 5
Overview
FlexNet Publisher (FLEX) is a software licensing package that allows a software application to be licensed
on a concurrent usage basis, as well as on a per-computer basis. Siemens PLM Licensing is based on FLEX.
Siemens PLM License Server has its own installation. For details on installing and starting Siemens PLM
License Server, please refer to the installation guide.
Siemens PLM Licensing features include the following:
1. Operation in a heterogeneous network of supported computer systems.
2. Transparent reconnection of an application when its license server process becomes
unavailable, including conditions of license server node failure.
3. Ease of configuration with a single license file per network.
4. Configuration controls for system administrators.
5. Administration tools for system administrators.
6. Independent features definitions.
7. License management on single, redundant and multiple server configurations.
Fundamentals of Siemens PLM Licensing
Siemens PLM Licensing manages licenses in a network and implements the concept of the license server.
The license server processes a license request and responds to the client. If a license is available, it is
granted and the application is allowed to continue. If not, the application is notified of an error and the
application reacts accordingly.
5
Note We recommend that the license file be placed on the license server node only.
Application Program
A software package that uses Siemens PLM Licensing for its license monitoring is usually run from the
client. The application program must be able to connect to the ugslmd daemon to be issued licenses.
Server Setting
The server setting must be set to run any Siemens PLM Licensing based application. The server setting
identifies the license server port (usually 28000) and hostname and is set initially by the installation
program when the application is installed. See the applications install guide for information on how to
change the server setting after installation.
6
# Server line
SERVER serverA COMPOSITE=08002b42b116 28000
# Vendor daemon line
VENDOR ugslmd
# Bundle
PACKAGE NX11110 ugslmd 26.0 \
COMPONENTS="NX11110_3d_to_2d_flattener NX11110_assemblies \
NX11110_c_p_p_runtime NX11110_dotnet_runtime NX11110_drafting \
NX11110_dxf_to_ug NX11110_dxfdwg NX11110_features_modeling \
NX11110_gateway NX11110_grip_execute NX11110_iges \
NX11110_nx_freeform_1 NX11110_nx_sheet_metal \
NX11110_pcf_package_file NX11110_pv_ugdatagenerator \
NX11110_sla_3d_systems NX11110_solid_modeling \
NX11110_step_ap203 NX11110_step_ap214 NX11110_ufunc_execute \
NX11110_ug_collaborate NX11110_ug_kf_checker \
NX11110_ug_kf_execute NX11110_ug_smart_models \
NX11110_ug_to_dxf NX11110_ug_web_express \
NX11110_ugopen_menuscript" OPTIONS=SUITE ck=81 \
SIGN="1BEC 143A A5FB 9942 E51D EB73 C77B E6DF 5085 \
8628 2893 D824 8DA1 7F70 1D89 17AA 08D7 E953 F4AB \
B837 00F2 7BD5 D33F 8A12 AD62 BEAB 2C1B 4D3F 2C55 A291"
# Floating Feature(s)
INCREMENT cam_base ugslmd 26.0 permanent 56 \
SUPERSEDE DUP_GROUP=UHD user_info="cam_base module" \
ISSUER="Siemens PLM Software" ISSUED=30-Aug-2007 ck=19 \
SIGN="11ED 1ABE 0ED4 853C 4F41 602B D7A9 A6A7 8511 77CE \
66E1 16E4 DFEF C891 7E7A 0480 FE0B 8D54 A7E9 29A8 DDE1 \
68CF B4AA 1DD5 53E8 F2DF 009D 9F7C 67AD 7BC9"
INCREMENT gateway ugslmd 26.0 permanent 56 \
SUPERSEDE DUP_GROUP=UHD user_info="gateway module" \
ISSUER="Siemens PLM Software" ISSUED=30-Aug-2007 ck=179 \
SIGN="21ED 1ABE C891 7E7A 0480 FE0B 8D54 A7E9 29A8 DDE1 \
68CF B4AA 1DD5 0ED4 853C 4F41 602B D7A9 A6A7 8511 77CE \
66E1 16E4 DFEF 53E8 F2DF 009D 9F7C 67AD 7BC9"
8
SERVER Line
EXAMPLE:
SERVER serverA COMPOSITE=08002b42b116 28000
The SERVER line specifies the node name and hostid of the license server and the port number of the
license manager daemon. Normally, a license file has one SERVER line. Three SERVER lines indicate that
you are using a redundant server configuration. No server line indicates you are using a Standalone Node-
Locked license file.
Note Do not delete SERVER lines from a license file because the hostids from the SERVER lines are
encrypted into the signature on every INCREMENT / FEATURE line.
VENDOR Line
EXAMPLE:
VENDOR ugslmd
The VENDOR line specifies the name of the vendor daemon supported by the license file.
PACKAGE Lines
EXAMPLE:
PACKAGE NX11110 ugslmd 26.0 \
COMPONENTS="NX11110_3d_to_2d_flattener NX11110_assemblies \
NX11110_c_p_p_runtime NX11110_dotnet_runtime NX11110_drafting \
NX11110_dxf_to_ug NX11110_dxfdwg NX11110_features_modeling \
NX11110_gateway NX11110_grip_execute NX11110_iges \
NX11110_nx_freeform_1 NX11110_nx_sheet_metal \
NX11110_pcf_package_file NX11110_pv_ugdatagenerator \
NX11110_sla_3d_systems NX11110_solid_modeling \
NX11110_step_ap203 NX11110_step_ap214 NX11110_ufunc_execute \
NX11110_ug_collaborate NX11110_ug_kf_checker \
NX11110_ug_kf_execute NX11110_ug_smart_models \
NX11110_ug_to_dxf NX11110_ug_web_express \
NX11110_ugopen_menuscript" OPTIONS=SUITE ck=81 \
SIGN="1BEC 143A A5FB 9942 E51D EB73 C77B E6DF 5085 \
8628 2893 D824 8DA1 7F70 1D89 17AA 08D7 E953 F4AB \
B837 00F2 7BD5 D33F 8A12 AD62 BEAB 2C1B 4D3F 2C55 A291"
The function of the PACKAGE line is to define a group of features that is specified in the component list.
The PACKAGE line in the license file, by itself, does not license anything -- it requires a matching
INCREMENT / FEATURE line to license the whole PACKAGE.
The INCREMENT / FEATURE line describes the license to use the product.
The vendor daemon (ugslmd) processes only the first FEATURE line for a given feature.
SYNTAX:
INCREMENT name vendor daemon version exp. date # of licenses \
HOSTID=hostid SUPERSEDE DUP_GROUP=UHD user_info="<Optional Text>" \
ISSUED=dd-mmm-yyyy BORROW=nnnn ck=nnn SIGN=”nnnn … nnnn”
name The name given to the license module by Siemens PLM Software.
vendor daemon The name of the Siemens PLM Software vendor daemon, ugslmd, that
serves this feature.
version The highest version of this feature that is supported by this license.
exp. date The expiration date. (If this field is set to "permanent", then the
license never expires.)
# of licenses The number of floating licenses for this feature.
HOSTID=hostid A host identifier supported by Siemens PLM Software. Used only if the
feature is to be bound to a particular host.
SUPERSEDE All licenses issued before the date specified in ISSUED= are
superseded by this line and become ineffective.
DUP_GROUP=UHD Allows a single user, host, and display combination to use only one
license seat.
user_info="<Optional Text>" Describes the licensed product in more detail.
ISSUED=dd-mmm-yyyy The date the product version was released.
BORROW=nnnn The maximum number of hours a feature can be borrowed.
ck=nnn A checksum value, useful with the "lmutil lmcksum" command, which
verifies that the license has been entered correctly.
SIGN=”nnnn … nnnn” A hexadecimal number that "authenticates" the readable license file
text, ensuring that the license text has not been modified.
10
Note All data in the license file is case sensitive unless otherwise indicated.
Hostname
This is the hostname for the license server. The hostname is limited to 1024 characters. The string
returned by the UNIX "hostname" or, on some systems, "uname -n" command. On Windows use the value
returned from the Command Prompt "hostname" command. If you don’t supply the hostname to Siemens
PLM Software when requesting a license file, "YourHostnameX" or "this_host" is used in the license file as
a place holder for the actual hostname and should be replaced with the real hostname. The proper
hostname value is used on the client side for setting the server setting to port@hostname.
Port Number
This is the TCP port number used by the client application to communicate with the license server. A port
number is required if the license file is a 3-server redundant license file. The initial value is 28000 but can
be changed. The proper port number value is used on the client side for setting server value to
port@hostname. The port 28000 has been reserved through IANA by Siemens PLM Software for this
purpose and it is highly recommended that this port value be used to avoid a conflict with another
software product.
user_info
The user_info field in the activating INCREMENT / FEATURE line is used to display a descriptive name for
the bundle. You can delete or edit this field to provide a different name. Do not exceed 20 characters for
this field. Do not change this field for the "server_id" license module, as this value is your WebKey access
code.
Do not use special characters such as quotes within the user_info field since they may corrupt the license
file. License file lines are limited to 4096 characters with a ‘\’ as a continuation character. Do not put a
continuation character in the middle of a user_info field. Instead, move a line continuation character
before the user_info field and place the field on the next line.
11
Floating / Concurrent Anyone on the network can use the licensed module, up to the limit
specified in the license file.
Node-locked The licensed module can be used only on one node.
Mixed Mixes node-locked and floating licenses in the same license file.
Node-Locked Licenses
Node locking means the license module can be used only on one node. A node-locked license has a
"HOSTID=" set to the hostid it is locked to on its INCREMENT / FEATURE line.
EXAMPLE:
SERVER serverA COMPOSITE=08002b42b116 28000
VENDOR ugslmd
INCREMENT gateway ugslmd 26.0 permanent 4 \
SUPERSEDE DUP_GROUP=UHD user_info="gateway module" \
ISSUED=30-Aug-2007 ck=179 SIGN="21ED 1ABE 009D F2DF \
C891 7E7A 0480 FE0B 8D54 A7E9 29A8 DDE1 68CF B4AA 1DD5 \
0ED4 853C 4F41 602B D7A9 A6A7 8511 77CE 66E1 16E4 DFEF \
53E8 9F7C 67AD 7BC9"
INCREMENT drafting ugslmd 26.0 permanent 1 \
HOSTID=12001234 SUPERSEDE DUP_GROUP=UHD \
user_info="drafting module" ISSUED=30-Aug-2007 ck=179 \
SIGN="31ED 1ABE 8511 77CE C891 7E7A 0480 FE0B 8D54 A7E9 \
29A8 DDE1 68CF B4AA 1DD5 0ED4 853C 4F41 602B D7A9 A6A7 \
67AD 7BC9 66E1 16E4 DFEF 53E8 F2DF 009D 9F7C"
INCREMENT drafting ugslmd 26.0 permanent 1 \
HOSTID=1700ab12 SUPERSEDE DUP_GROUP=UHD \
user_info="drafting module" ISSUED=30-Aug-2007 ck=179 \
SIGN="41ED 1ABE 8511 77CE C891 7E7A 0480 FE0B 8D54 A7E9 \
29A8 DDE1 68CF B4AA 1DD5 0ED4 853C 4F41 602B D7A9 A6A7 \
67AD 7BC9 66E1 16E4 DFEF 53E8 F2DF 009D 9F7C"
INCREMENT drafting ugslmd 26.0 permanent 2 \
SUPERSEDE DUP_GROUP=UHD user_info="drafting module" \
ISSUED=30-Aug-2007 ck=179 SIGN="51ED 1ABE 8511 77CE \
C891 7E7A 0480 FE0B 8D54 A7E9 29A8 DDE1 68CF B4AA 1DD5 \
0ED4 853C 4F41 602B D7A9 A6A7 67AD 7BC9 66E1 16E4 DFEF \
53E8 F2DF 009D 9F7C"
This allows for one use of drafting on nodes 12001234 and 1700ab12, but two licenses of drafting and
four licenses of gateway to be used anywhere else on the network. Nodes 12001234 and 1700ab12 can
also utilize the floating licenses.
12
Packages
Siemens PLM Licensing uses "packages" to group features. The license file contains a PACKAGE line for
each of these groupings. The COMPONENT field contains a list of all included features. An INCREMENT /
FEATURE line is required to activate a PACKAGE definition.
Siemens PLM Licensing recognizes two types of packages: non-suite packages and suite packages. Non-
suite packages are designed to simplify and shorten the license file. Suite packages are designed to tie
component features together to be checked out as a group. The presence of the OPTIONS field on the
PACKAGE line distinguishes the package types.
Non-suite packages do not use OPTIONS=SUITE in the PACKAGE definition line. The components of non-
suite package are independent of one another and act just like they would if they had their own separate
INCREMENT lines.
EXAMPLE:
PACKAGE ACME_GATE ugslmd 26.0 COMPONENTS="gateway \
solid_modeling features_modeling usr_defined_features \
free_form_modeling assemblies drafting iges dxf_to_ug \
ug_to_dxf sla_3d_systems" ck=183 SIGN="61ED 1ABE 8511 77CE \
C891 7E7A 0480 FE0B 8D54 A7E9 29A8 DDE1 68CF B4AA 1DD5 \
0ED4 853C 4F41 602B D7A9 A6A7 67AD 7BC9 66E1 16E4 DFEF \
53E8 F2DF 009D 9F7C"
EXAMPLE:
PACKAGE NX11110 ugslmd 26.0 \
COMPONENTS="NX11110_3d_to_2d_flattener NX11110_assemblies \
NX11110_c_p_p_runtime NX11110_dotnet_runtime NX11110_drafting \
NX11110_dxf_to_ug NX11110_dxfdwg NX11110_features_modeling \
NX11110_gateway NX11110_grip_execute NX11110_iges \
NX11110_nx_freeform_1 NX11110_nx_sheet_metal \
NX11110_pcf_package_file NX11110_pv_ugdatagenerator \
NX11110_sla_3d_systems NX11110_solid_modeling \
NX11110_step_ap203 NX11110_step_ap214 NX11110_ufunc_execute \
NX11110_ug_collaborate NX11110_ug_kf_checker \
NX11110_ug_kf_execute NX11110_ug_smart_models \
NX11110_ug_to_dxf NX11110_ug_web_express \
NX11110_ugopen_menuscript" OPTIONS=SUITE ck=81 \
SIGN="81ED 1ABE 8511 77CE 0ED4 853C 4F41 602B D7A9 A6A7 \
C891 7E7A 0480 FE0B 8D54 A7E9 29A8 DDE1 68CF B4AA 1DD5 \
67AD 7BC9 66E1 16E4 DFEF 53E8 F2DF 009D 9F7C"
Setting Bundles
The setting of bundles is done on the client side and should be documented in the application licensing
specific documentation. If the application is shipped with the Siemens PLM Licensing Tool see the section
Optional Features for more information.
License Borrowing
With License Borrowing, you can check out a single seat (a set of license modules) from a site license
server and use those license modules offline.
License Borrowing has the following limitations:
The duration of the borrowing is up to 120 days (2880 hours).
The client platforms that are supported are Windows and Mac OS X. The license server can be
on any normally supported platform.
To activate borrowing, you must contact your sales representative and order borrowing. Once ordered,
you will be sent a new license file containing the BORROW keyword on all features that can be borrowed.
Borrowing Licenses
The borrowing of licenses is done on the client side and should be documented in the application licensing
specific documentation. If the application is shipped with the Siemens PLM Licensing Tool see the section
Optional Features for more information.
EXAMPLE:
...
Users of gateway: (Total of 1 license issued; Total of 1 license in use)
"gateway" v26.0, vendor: ugslmd
floating license
nx_user1 nx_client1 nx_client10.0 (v26.000) (license_server/28000 101),
start Wed 9/1 13:33 (linger: 604740)
...
15
License Configurations
Siemens PLM Licensing is designed to support the following license configurations:
Single Server Configuration
Standalone Node-Locked Configuration
Redundant Server Configuration
Multiple Server Configuration
/LicenseFiles/splm.lic
Windows:
C:\LicenseFiles/splm.lic
You should verify that each license server has Siemens PLM Licensing installed on a local file system.
Proceed by starting each license server on each machine in the order they are listed in the license file,
starting with the server listed on the top line.
The redundant server configuration requires at least two of the three servers to be active for the licenses
to be available. No licenses are available until this quorum of two is met. A quorum of servers is defined
as a strict majority of servers listed in the license file, so the quorum in the three-server configuration is
two. If only one of the servers is available, the quorum is not satisfied and no licenses will be available.
One of the servers starts out as the master server and serves licenses. If the master goes down, another
server takes over as master. Once the issue that brought down the master server is resolved, you should
reset the license servers at your convenience. To reset the license servers, stop all three license servers
and then restart in the order they are listed in the license file, starting with the server listed on the top
line. See the sections on “Stopping the Siemens PLM Licensing License Server…” and “Starting the Siemens
PLM Licensing License Server…”, later in this guide, for instructions on resetting the license daemon.
Considerations
The following items should be considered relative to this specific type of server configuration:
This configuration should be maintained by a full time system administrator.
If one server goes down, the odds of a server failure become greater than that of a single server
system, since either of the other two servers failing will cause failure by not satisfying the
quorum.
All three redundant servers must maintain communications with each other.
The server settings on the client node should conform to the
port@hostname1,port@hostname2,port@hostname3 syntax.
Setup for a Redundant Server Configuration
The order in which the servers are listed is the order in which they are checked. If the first server is not
the master, the client will continue to search through the license servers until either a master server is
found or all three servers have been checked.
When asked for the license server by the installation software of a Siemens PLM Software application, use
the ports on the SERVER lines (28000, 28000 and 28000) and the hostnames on the SERVER lines (serverA,
serverB and serverC) in the following format:
28000@serverA,28000@serverB,28000@serverC
Effect on the License File
The license file will contain three SERVER lines for each of the license servers.
# Server line
VENDOR ugslmd
Note The port number is required in the license file for redundant server configuration.
19
When asked for the license server by the installation software of a Siemens PLM Software application use
the ports on the SERVER lines of both license files (28000 and 28000) and the hostnames on the SERVER
lines of both license files (license_server1 and license_server2) in the following format:
28000@license_server1;28000@license_server2
The order in which the servers are listed is the order in which they are checked. The first server listed
should be your primary and closest server.
In this example the client would normally get all of its licenses from license_server1. In the event that
license_server1 did not have the license or went down, the license request would move to
license_server2. You would receive a license not available message only if the license was not available
on any of the two license server configurations.
Administration Tools
The following administration tools are available for Siemens PLM Licensing:
lmcksum Prints license checksums. To be used when a license file is manually entered.
lmdiag Diagnoses license checkout problems.
lmdown Gracefully shuts down all license daemons (both lmgrd and ugslmd) on the license server
node(s).
lmhostid Reports the FLEX hostid of a system.
lmremove Removes a single user's license for a specified feature.
lmreread Causes the license daemon to reread the license file and start any new vendor daemons.
lmstat Helps you monitor the status of all network licensing activities.
lmver Reports the FLEX version of a library or binary file.
Location of Tools
The default location for these tools is:
UNIX and Linux
On the server
/usr/Siemens/PLMLicenseServer/
Mac OS
On the server
/Application/Siemens/PLMLicenseServer/
Windows
On the server
C:\Program Files\Siemens\PLMLicenseServer\
21
To configure your license service, click the Configuration using Services radio button to access the
Configure Services tab.
Refer to the Flexera License Administration Guide for additional information on LMTOOLS.
License Administration on Windows
Siemens PLM Licensing supports the following types of hostids:
Composite hostid (for license files only)
Ethernet Address (for individual licenses)
Hardware Key (for standalone node-locked licenses and individual licenses)
Siemens PLM Licensing has its own installation for more information please refer to the installation guide.
22
EXAMPLE:
SERVER serverA COMPOSITE=37B5ED1AC61D 28000
To obtain the CID, you will have to run a Siemens PLM Licensing utility called “getcid”. This utility is
provided in the license server media kit or can be downloaded via the Customer Support (GTAC) website
http://support.industrysoftware.automation.siemens.com/gtac.shtml. The utility must be executed on
the target license server or on all three servers in a redundant configuration. The output is a list of 12 digit
hexadecimal number that is the CID for that system. If a server has multiple physical addresses, multiple
CIDs will be displayed.
EXAMPLE :
C:\getcid.exe
Multiple composite hostids (CIDs) indicate you have multiple network
adapters. You should select the first CID or the most appropriate CID based
on the network adapter which is currently active. The Siemens PLM Software
licensing CIDs are:
On Windows, Linux and MacOS server the output is the CID for that system along with the information of
the network adapter it is associated with. By default the utility filters out any virtual network adapters or
other devices like Bluetooth and InfraRed. In case if CIDs for all the available network adapters on the
server are required, then the utility may be executed with -all flag.
The concept of multiple CIDs was introduced to allow the flexibility to use a CID associated with any
physical address. Previously, you were limited to just the CID associated with the device at the top of the
network binding. If you see multiple CIDs, select the first one in the list. If the selected CID changes or
disappears for any reason, use the next CID in the list.
When needing to get a CID with a script the “Press the ENTER key to continue...” can be a problem.
To turn off the pause use the flag -nopause.
EXAMPLE :
C:\getcid.exe -nopause
Multiple composite hostids (CIDs) indicate you have multiple network
adapters. You should select the first CID or the most appropriate CID based
on the network adapter which is currently active. The Siemens PLM Software
licensing CIDs are:
Once the CID information is obtained for a license server, this information must be entered into your
customer record to generate a permanent license file. The CID can be entered using your WebKey account
or by calling your customer service representative (CSR). After the CID has been entered into your
customer record you will be sent a permanent license file for you to install on your license server.
Cloud Hostid
The cloud hostid is a unique identifier for machines running on a cloud environment which can be used
reliably for licensing. Siemens PLM Software supports two major cloud computing service providers:
Amazon Web Services (AWS) and Microsoft Azure. Cloud hostids are identified by the keywords
“AMZN_ID=” and “AZRE_ID=” on AWS and Azure platforms respectively. On AWS, the hostid is the
machine’s instance id and on Azure it is the system’s UUID.
EXAMPLE:
SERVER AWSserver AMZN_ID=i-02aadbdb 28000
To obtain the cloud hostid, run the same “getcid” utility as mentioned above in the Composite Hostid
section. The utility is executed with -cloud flag to get the cloud identifier. It will automatically detect the
underlying cloud computing platform and generate the hostid.
EXAMPLE:
C:\getcid.exe -cloud
The Siemens PLM Software licensing cloud hostid for this host "AWSserver" is:
Licensing Terms
The following software licensing terms are used to describe Siemens PLM Licensing.
Bundle Consolidation The act of taking checked out license modules consisting of bundled and
floating features and replacing their licensing check outs with licensing
check outs from one single bundle.
CID Acronym for Composite Hostid
Client Any node on the network that requests a license from the license server.
Composite Hostid A 12 digit hexadecimal unique machine identifier distinguished from a
FlexNet hostid by the key word “COMPOSITE=”. It is used to lock a license
file to a machine.
Concurrent Licensing A software license that specifies a maximum number of users who can
use the software at the same time. Pricing is usually by seat or user. As
software is used, a license is verified and checked out through Siemens
PLM Licensing. When the user is finished with the software, the license is
checked in for use by another user.
Feature FEATURE represents any functionality that needs to be licensed.
FLEX FlexNet Publisher
Floating Feature Feature that is defined on an INCREMENT / FEATURE line or within a non-
suite package.
Hostid Used to uniquely identify a specific machine, if the license or license file is
to be bound to a particular host.
Increment An INCREMENT line can be used in place of a FEATURE line. It can also be
used to incrementally add licenses to a previous FEATURE or INCREMENT
line in the license file.
License The right to use a specific version of a software module. The license
specifies what version of the software can be used and how many users
can use that software. A license can also have a time period associated
with it.
28
License File A text file that stores the licensing data. This file contains information
about the server nodes and vendor daemons and at least one line of data
for each licensed product.
License Key A 12 character hexadecimal number that authenticates the readable
license file text, ensuring that the license text has not been modified.
License Server The node on a network where license requests are processed.
lmgrd The main license daemon that sends client application requests to the
correct vendor daemon.
Multiple Servers A way of listing more than one potential license server for the client
application program as defined by the server setting on the client side.
Package An efficient method of distributing a license file containing many features
that share the same FEATURE line arguments.
Redundant Servers A set of three redundant license servers that requires two of the three
license servers to be up and running in order to serve licenses.
Server ID The unique identifier of your license file configuration.
Server Node A computer system that is running the license server software. The server
node contains all the site-specific information on feature usage.
Siemens PLM Licensing The licensing toolkit and license daemon that some Siemens PLM
Products are using to provide consistent licensing functionality and
enabling the shipment of combined license files to customer using
multiple licensing products.
splm_ugslmd.log The debug log file for Siemens PLM Licensing. The splm_licensing.log file
contains the output from "lmgrd" and "ugslmd" and is used as a
debugging aid.
ugslmd The vendor daemon that Siemens PLM Licensing uses to dispense licenses
for the requested features.
Windows Supported Microsoft Windows Platform.
Optional Features
Siemens PLM Licensing Tool
The Licensing Tool is not provided with all Siemens PLM Software applications and therefore this
information may not be applicable to all Siemens PLM Software applications. There are two flavors of the
tool:
GUI – Graphical User Interface, available on:
a) Windows 32/64bit
b) Macintosh OS X 64bit
c) Linux: Red Hat 64bit and SUSE 64bit
CLI – Command Line Interface, available on all platforms supported by Siemens PLM Licensing.
29
The order in which the bundle names are listed is the order that the application will attempt to check out
any feature. The maximum number of bundles that you can select is two.
30
Borrowing Settings
The ability to borrow requires an extra feature to be added to your license file. Contact your Siemens PLM
representative for more information about purchasing the ability to borrow.
Note: The "License" value listed in the tool is the user_info field value on each license
module’s INCREMENT / FEATURE lines in the license file. These values correspond to the
short descriptions in the price book for each product. If two different products with
similar license modules end up on the same license file each license module that is
similar is combined into one INCREMENT / FEATURE line. The user_info field is
combined in the following format "Common to Adv Designer Plus and NX M-1 Dsgn
(FL)". Therefore if you are borrowing "Adv Designer Plus" you should also borrow all
the "Common to..." that contain it in order to get its full functionality.
31
Environment Settings
The tab displays various client and server environment settings, such as host name, license server,
Composite Host ID, toolkit version, etc.
If an application enables the changing of the current license server, you can update the license server via
the Edit option from the License Server panel:
32