This manual provides instructions and reference information for using the Application Programming Interface (API) of FlexNet Manager for Engineering Applications to set up and configure the following system components:. FlexNet Agents. License servers. License files. This document comprises the following chapters. To obtain FlexNet Licensing downloads (platform SDK, tools, licenses and documentation): Sign in to the Flexera Product and License Center using the appropriate credentials assigned to you in your 'Welcome to Flexera Software Product and License Center' email. Oct 24, 2011 The license file should be placed in the following folder location: C:Program Files FLEXnet Publisher License Server Managerlicensesadskflex You will have to create the necessary folder structure before placing the file. You can also place any. If the license server was modified in the.env file and difficulties connecting to the license server arise, then trying the points discussed below may resolve the issue. Check whether the license server is running. This can be done by opening FLEXnet licensing utilities on the server. The FlexNet ConnectC XT Application Programming Interface reference describes the modules and functions of the C libraries that comprise the FlexNet ConnectC XT kit. This reference is not available as a PDF. Rather it is delivered as HTML-based online documentation archive. FlexNet Connect.
- Flexnet Licensing Service
- Flexnet Licensing Programming And Reference Guide Free
- Flexnet Licensing Programming And Reference Guidelines
- Flexnet Licensing Documentation
- Flexnet Licensing Error 96 7
Original author(s) | GLOBEtrotter and Highland |
---|---|
Developer(s) | Flexera Software |
Initial release | 1988; 32 years ago |
Stable release | 2018 R3 (11.16.1) / October 8, 2018; 23 months ago[1] |
Written in | C/C++, Java |
Operating system | Windows, macOS, Linux, and various UNIXes |
Platform | Cross-platform |
Available in | English |
Type | Software license management |
License | Proprietary |
Website | www.flexera.com/producer/products/software-monetization/flexnet-licensing/flexnet-publisher/ |
FlexNet Publisher (formerly known as FLEXlm) is a software license manager from Flexera Software which implements license management and is intended to be used in corporate environments to provide floating licenses to multiple end users of computer software.[citation needed]
Computer software can be licensed in a variety of ways. A license to use a piece of software may be associated with a specific machine (node-locked), permitting it to only run on that machine (node in a network); alternatively, a company may buy a pool of floating licenses and these licenses may be allocated dynamically to machines, a license being checked-out when a user begins using the software on any given machine and checked-in when the user finishes using the software. In this way, for example, a company might buy a pool of 50 licenses but support a user community of hundreds of occasional users of the software (so long as no more than 50 users ever want to use the software simultaneously).[original research?]
![Server Server](https://image.slidesharecdn.com/sqlserver2012licensingreferenceguide-130909010535-/95/sql-server-2012licensingreferenceguide-4-638.jpg?cb=1378689231)
History[edit]
FLEXlm was originally a joint development by GLOBEtrotter Software and Highland Software in 1988. Highland's rights to the FLEXlm product were acquired by GLOBEtrotter in 1994; Highland continued as a reseller of 3rd party software. GLOBEtrotter was then acquired by Macrovision in 2000. Combining features from the Safecast protection system and FLEXlm, FlexNet featured product activation and executable wrapping, supporting floating licensing and node locked licensing models. Macrovision subsequently renamed FLEXlm to FLEXnet Publisher.[citation needed]
The original FLEXlm development team moved on to develop the Reprise License Manager (RLM) at Reprise Software in 2006.[citation needed]
On 1 April 2008 Macrovision's Software Business Unit, which included FLEXnet Publisher, was sold to the private equity company Thoma Cressey Bravo and subsequently relaunched as Acresso Software. It was a cash transaction valued at approximately $200 million.[2]
In October 2009 Acresso Software announced its name change to Flexera Software and FLEXnet Publisher was changed to FlexNet Publisher.[3]
A July 2011 announcement said that Teachers' Private Capital, the private investment department of the Ontario Teachers' Pension Plan, had agreed to acquire a majority stake in Flexera Software from Thoma Bravo, LLC, a private equity firm.[4]
The product is currently marketed by Flexera Software as FlexNet Publisher.[5]
Issues with bootloaders[edit]
Due to the way the digital rights management (DRM) works in FlexNet Publisher, FlexNet affects bootloaders; this makes FlexNet Publisher incompatible with drives encrypted with TrueCrypt[6][7] and renders Linux-based systems unable to boot.[8][9] The TrueCrypt developers also state that 'the issue is caused by inappropriate design of the third-party activation software.'[10]
Other license management software[edit]
- Reprise License Manager(RLM)
References[edit]
- ^'FlexNet Publisher End-of-Life Announcements'. Flexera. Retrieved 2019-02-03.
- ^'Acresso Software Press Release'. Flexerasoftware.com. Retrieved 27 October 2014.
- ^Eric Lai (10 October 2009). 'Acresso who? Macrovision spinoff changes name, again (Computerworld article)'. Computerworld. Retrieved 27 October 2014.
- ^'Teachers' Private Capital to Acquire Majority Stake in Flexera Software'. Marketwire. Retrieved 27 October 2014.
- ^Centralized Management Eases License Server Administration. flexerasoftware.com. Retrieved 2016-11-21
- ^'Freeze when you reboot a Windows system that has TrueCrypt Disk Encryption software and Adobe applications installed'. Kb2.adobe.com. Retrieved 27 October 2014.
- ^'TrueCrypt'. Kb2.adobe.com. Archived from the original on 16 April 2013. Retrieved 27 October 2014.
- ^'Colin Watson'. chiark.greenend.org.uk. Retrieved 27 October 2014.
- ^'Bug #441941 'grub fails after running Windows' : Bugs : 'grub2' package : Ubuntu'. Bugs.launchpad.net. Retrieved 27 October 2014.
- ^'TrueCrypt'. Truecrypt.org. Archived from the original on 16 April 2013. Retrieved 27 October 2014.
External links[edit]
- Official website
Retrieved from 'https://en.wikipedia.org/w/index.php?title=FlexNet_Publisher&oldid=935764947'
Open Inventor is protected by a license key mechanism limiting its usage to specified computers or network environments based on commercial agreements. In this chapter, we explain how to setup the licensing for the different licensing cases.
Note: temporary licenses can be sent for evaluation purpose. These licenses are not locked to a specific computer but are time limited. Please go to the trial version request page for getting a trial license.
Licensing overview |
Your license(s) of Open Inventor and associated extensions have been designed to run on a specific hardware configuration and used by a specified number of users. You might have purchased either node-locked licenses, which are individually bound to identified equipment, or a floating license, which is to be installed on a specified number of single computers driven by a license server.
Each type of license requires a specific License Key (so called password) to be activated. In order to get this password, we need you to provide us with the hostID of your computer for node-locked licenses, or the hostID and hostname of your license server for floating licenses.
The Open Inventor licensing mechanism uses the FLEXnet technology, by Flexera.
Note: the hostID was called the ComputerID in versions of Open Inventor prior to 8.6.
Node-locked licenses are licenses which allow you to use Open Inventor on an identified computer. Designated equipment(s) are identified by a hostID.
Getting the hostID
To activate your node-locked license, we need the hostID of your computer.
- Open a command console on Windows or a command shell on a Unix platform
- Disable all temporary network connections (wlan card, bluetooth, docking station, …)
- Go to the directory (depending on the language binding and platform installed):
<OIV_home>/license/
or
<OIV_home>/arch-<OIV_arch>-release/license/
(where <OIV_arch> is the platform architecture for instance Linux-x86_64-gcc41) - To get the hostID, execute the command ‘lmhostid’
Note: The ComputerID displayed in the Open Inventor V8.x License Manager (Ladmin) does not match the FlexNet hostID. Do not use this value as hostID. The Ladmin tool is now deprecated.
Requesting your license key
Once you have the hostID, go to our online password delivery center and fill in your details, Open Inventor and extensions license numbers, along with your hostID.
Installing the license key
You will receive the license keys by email as well as the installation instructions. The provided license file must be copied in the <OIVHome>/License/password.dat or <OIVHOME>/arch*release/license/password.dat directory in order to unlock the product.
Where OIVHome is the installation path of the Open Inventor package.
Overview
Read this section only if you have purchased a floating license for your site where a single license server provides the license key for several users located on other machines of the same network environment. Standalone licenses also called nodelock licenses, application password licenses and temporary licenses are not managed using this mechanism.
FEI uses the FLEXnet licensing option to support floating licenses. In this scenario, a site purchases a specific number, N, of Open Inventor licenses. The FLEXnet license server tracks the licenses being used and allows simultaneous use of up to N instances of the Open Inventor software. The advantage of this approach is that, unlike standard Open Inventor licensing, Open Inventor is not locked to a specific computer, but can be run on any computer that can communicate with the license server.
A small set of FLEXnet-related files are provided for managing the FLEXnet licensing. These files must be copied onto the system to where the license server will be run. The license server can be run on the same system where Open Inventor is installed, but it doesn't have to be.
One of the supplied files, lmgrd ('license manager daemon'), is a FLEXnet executable that is responsible for starting the vendor daemon, which does the actual checking in and out of licenses specific to that vendor. The supplied vendor daemon, mcslmd ('FEI license manager daemon'), handles the requests for licenses from the Open Inventor application programs.
There is a FLEXnet license file that is read by the server. This license file contains information indicating which products are licensed and how many licenses are allowed for each.
In addition, each Open Inventor installation has a separate license file which indicates the name of the FLEXnet license server.
The sections below will provide the basic technical details of installing and managing a FLEXnet license server.
For complete technical details regarding FLEXnet itself, see the Web site of Flexera Software, supplier of the FLEXnet licensing software (www.flexerasoftware.com):
Getting Started
The first thing to do is decide on which computer you wish to run the FLEXnet license server. This system should be 'visible' from any system that might want to request a license. It should also be highly reliable.
The server can be installed on a computer on which Open Inventor is installed, but it does not have to be.
It is possible to do FLEXnet licensing in a heterogeneous environment. That is, the server and Open Inventor can be running on different operating systems. For instance, the FLEXnet server could be on a Linux box, with the Open Inventor users running Open Inventor on a Windows platform.
If your site already has a FLEXnet license server running that is used for licensing other vendors' products, this may affect where and how you decide to configure the Open Inventor license server. The FLEXnet documentation from Acresso can help you with this decision. See, for example, the chapter 'Managing Licenses from Multiple Vendors' in the FLEXnet Licensing End User Guide.
For the rest of this discussion, we will assume that you will be setting up a license server used only for licensing Open Inventor.
Once you have selected the server machine, if you are not going to run the server from the Open Inventor installation directory (i.e., from <oiv_install_dir>/<architecture>/license), you will need to copy the FLEXnet-related files provided by FEI to that system into an empty directory.
Suggested server directory name:
The FLEXnet files are provided in:
On the Open Inventor download pages, FLEXnet files are also available for platforms other than the one on which you will be running Open Inventor.
Open Inventor 9.9.x requires FLEXnet tools 11.14.0.0.
Open Inventor 10.x to 10.2.x requires FLEXnet tools 11.14.0.0.
Open Inventor 10.3.x and above requires FLEXnet tools 11.16.0.0.
Open Inventor 10.x to 10.2.x requires FLEXnet tools 11.14.0.0.
Open Inventor 10.3.x and above requires FLEXnet tools 11.16.0.0.
Instructions for installing and configuring the server are provided in below.
Getting the hostID and host name
In order for FEI to generate a FLEXnet license, we will need the following information about the system on which the license server is running/will run:
- its host name (or IP address), and
- its host ID.
Unix
- On the system where the server is running/will run, in a command shell, go to the directory where the server will be installed:
- To get the host ID, execute the lmutil program as follows:The output will look like:
- To get the hostname, you can use any of the following commands:
- To get the IP address (optional):
- Save the lmhostid output and the hostname (or IP address).
Flexnet Licensing Service
Windows
- On the system where the server is running/will run, run LMTOOLS. It should be located in:
- Click on the Systems Settings tab.
- The Computer/Hostname field contains the required host name.
- The Ethernet Address field contains the required host id.
- The IP Address field contains the optional IP address.
- Save those values
Requesting your license key
Once you have the hostID and host name, go to our online password delivery center and fill in your details, Open Inventor and extensions license numbers, along with your hostID and host name.
Installing the FLEXnet Server (UNIX)
At this point, we assume that the FLEXnet files are in their desired location:
- either in the default location, <oiv_install_dir>/<architecture>/license
- or have been copied to <some_path>/oiv_flexnet directory on the system where the server will run.
Flexnet Licensing Programming And Reference Guide Free
The vendor daemon mcslmd must be in the same directory as lmgrd.
The command to start the server looks like:
where:
- <server_license_file> is the full path to the server license file, and
- <debug_log_path> is the path to the debug log file.
Prepending the + character the the log file name causes log entries to be appended.
The following is the suggested command to use:
TIP: It can be convenient to set up the server so that it is started automatically upon system reboot. This would involve editing the system boot script. See the FLEXnet Licensing End User Guide, chapter 'The License Server Manager' for details.
Installing the FLEXnet Server (Windows)
At this point, we assume that the FLEXnet files are in their desired location:
- either in the default location, <oiv_install_dir><architecture>license
- or have been copied to <some_path>oiv_flexnet directory on the system where the server will run.
FLEXnet uses a program called lmgrd to manage licenses. On Windows, FLEXnet provides a GUI called LMTOOLS that allows one to configure lmgrd to run as a service. This is the preferred method of configuring FLEXnet and is outlined below.
NOTE: To configure a license server as a service, you must have Administrator privileges.
The vendor daemon mcslmd.exe must be in the same directory as lmgrd.exe.
|
|
Starting the Server (Windows)
Once the license manager service is configured, lmgrd is started by starting the service from the LMTOOLS interface:
|
The OIV License Manager license server should now be started and writing its debug log output to <oiv_install_dir><architecture>licenseflexnet.log. NOTE: Any time you make a change to the server configuration, you should stop the server then restart it in order for the changes to take effect. NOTE: Any time you make a change to the server password file, you should use the Start/Stop/Reread tab, and press the ReReadLicenseFile button. If the first time you press it, the operation fails, wait briefly (a minute or less), and try pressing it again. Hazard snow leopard amd install guide. |
Installing the Server License File
Flexnet Licensing Programming And Reference Guidelines
You should have received an email containing FLEXnet server license file from the FEI's License administrator.
Here's an example of server license file: Print key download for windows 10.
Here's an example of server license file: Print key download for windows 10.
Unix
Flexnet Licensing Documentation
On UNIX, the server license file is specified when the server is started.
- Decide where you want to place the server license.Recommended location:
- Using a text editor, copy the server license strings into that file.
Start the server:
Windows
Flexnet Licensing Error 96 7
- Decide where you want to place the server license file.Recommended location:
- Using a text editor, copy the server license strings into that file.
- Run LMTOOLS, click on the Config Services tab, then specify the 'path to the license file'.
- For this change to take effect, stop and restart the server using the Start/Stop/Reread tab.
Installing the Client License Files (All Platforms)
Each system that might request an Open Inventor license from the FLEXnet license server must have an Open Inventor license file.
Here's an example client license file:
On each client system, copy the client license info to the Open Inventor license file.
The default (and recommmended) location is:
This can be changed by setting the VSG_LICENSE_FILE environment variable to a new path, including the file name. Once this variable is set, Open Inventor automatically looks for the license file in the specified location. If Open Inventor cannot find the license file, the user is presented with a dialog that asks for the license information.
Nomad Licensing / Borrowing
To use a FLEXnet floating license on a system that is not always connected to the license server, you will need to 'borrow' a license while you are connected to the server, then disconnect from the server. This kind of licensing is what we call 'nomad' licensing. Below are the detailed instructions. We will assume that standard FLEXnet licensing, i.e., not borrowing, is already working correctly.
Unix
- On the client machine, in a command shell, go to the directory where the FLEXnet utilities are installed. By default, these utilities are found on the client machine in: <oiv_install_dir>/<architecture>/license.cd <oiv_install_dir>/<architecture>/license
- To initiate borrowing, execute the lmutil program on the client as follows:lmutil lmborrow mcslmd <enddate> <time>where:<enddate> <time> Enddate is the date the license is to be returned in dd-mmm-yyyy format. Time is optional and is specified in 24-hour format (hh:mm) in the FLEXenabled application local time. If time is unspecified, the checkout lasts until the end of the given end date.For example:lmutil lmborrow mcslmd 16-jan-2007 13:00
To print information about borrowed features, issue the following command on the machine from which they are borrowed:
lmutil lmborrow -status
Windows
- Run LMTOOLS on the client machine. By default, LMTOOLS is found on the client machine in: <oiv_install_dir>/<architecture>/license.
- Click on the Borrowing tab.
- Specify a return date.
- Optional, specify the vendor name (mcslmd).
- Press the Set Borrow Expiration button.
- Start your Open Inventor Application, then use all of the extensions that you want to borrow.
- Disconnect from the network.
- Exit your Open Inventor Application and confirm that you can restart it and use all of the borrowed modules.
2001 chevy astro van repair manual download. You can check how many licenses are checked-in or out by pressing the List Currently Borrowed Features button of the Borrowing tab of the LMTOOLS application.
Additional controls can be set directly into the license string. The most important are:
- Limit the number of token that can be borrowed:
Examples: The customer want to keep 60 tokens over his 100 tokens, so only 40 tokens can be borrowed.
Add a BORROW_LOWWATER line:
- Limit the number of token that can be borrowed:
BORROW_LOWWATER | Product | 60 |
- Limit the number of days a token can be borrowed:
Examples: One week (7days x 24hours = 168hours). Add a MAX_BORROW_HOURS line:
MAX_BORROW_HOURS Product 168
Notes: If not specified, default value is one year. - Specify who is allowed to borrow:
- a user
INCLUDE_BORROW Product USER Jim - a group of users
INCLUDE_BORROW Product GROUP project_dev - a computer
INCLUDE_BORROW Product HOST hots_name - a group of computers
INCLUDE_BORROW Product HOST_GROUP computer_group
- a user
- Specify who is not allowed to borrow:
- a user
EXCLUDE_BORROW Product USER Jim - a group of users
EXCLUDE_BORROW Product GROUP project_dev - a computer
EXCLUDE_BORROW Product HOST hots_name - a group of computers
EXCLUDE_BORROW Product HOST_GROUP computer_group
- a user
Defining groups
- Group of users:
GROUP project_dev Jim Mike Bob - Group of computers:
HOST_GROUP computer_group host1 host2 host3
- Group of users:
Reserving tokens
Tokens can be reserved for specific users groups or computers.
- Reserve 10 tokens for an user:
RESERVE 10 Product USER Jim - Reserve 10 tokens for a group of users:
RESERVE 10 Product GROUP project_dev - Reserve 10 tokens for a computer:
RESERVE 10 Product HOST host1 - Reserve 10 tokens for a group of computers:
RESERVE 10 Product HOST_GROUP computer_group
- Reserve 10 tokens for an user:
Setting Access Permissions
You can control who is allowed to use a product using the INCLUDE EXCLUDE commands.
- Who is allowed to use a product :
INCLUDE Product USER Jim
Can be used for GROUP, HOST and HOST_GROUP as described above. - Who is not allowed to use a product :
EXCLUDE Product USER Mike
- Who is allowed to use a product :
Troubleshooting
Refer to the FLEXnet documentation. The FLEXnet Licensing End User Guide contains a troubleshooting appendix.
Finally if you need assistance getting your FLEXnet licenses installed and operational, please contact the technical support.