IBM Rational – FlexNet Token based licensing

Posted on January 22, 2012 by orik

IBM Rational license management using FLEXnet

The IBM Rational License Server uses FLEXnet for licensing IBM Rational products.

FLEXnet main components

The four main components of FLEXnet are:

  • The License Manager Daemon, lmgrd

  • The Vendor Daemon, telelogic

  • The client application program, in this case any IBM Rational application

  • The license file, license.dat

Mode of employment

  • When an IBM Rational product is started, the program uses the TELELOGIC_LICENSE_FILE system variable to find out the name of the computer that’s running the FLEXnet license server and the port that it’s using.

  • The program contacts the license manager on the FLEXnet license server, using the specified port. It requests a floating license and makes the request for the Telelogic vendor daemon.

  • On the FLEXnet license server, the license manager sends the request to the Telelogic vendor daemon. The Telelogic vendor daemon checks to see if any licenses are available.

  • If there are free licenses, the Telelogic vendor daemon grants a license and the program runs. If there aren’t any licenses available, the Telelogic vendor daemon refuses the request, and the program fails to start and displays a denial message.


Token-based licensing

Token licenses are in fact a form of floating license, only that instead of having a pool of licenses – it has a pool of tokens. When a feature is checked-out, a certain amount of tokens are consumed. The number of consumed tokens is specific to each feature, and is apparent in the feature/Increment line in the license file. When the application is closed, the tokens are returned to the pool for other end users to use.

Advantages of Token licensing

Having the ability to apply the acquired licenses to multiple products is an appealing concept:

  • Customers are not always aware of the full array of features they may acquire. having a token based license scheme ensures customer satisfaction from the license acquisition.

  • As development stages progress, customer needs change. They may require different licensed features, and eliminate the charge of “unused” software.

  • The entire license purchasing method is simplified. Customer can add/try new software during project, without new PO or evaluation process

Rational tools’ token-based licensing

IBM Rational license types

IBM Rational includes the following license types:

DOORS, Synergy, Change, Tau, System Architect, Focal Point, Rhapsody, Publishing Engine, Logiscope and Team Webtop

IBM Rational token license file examples

  • The Increment/Change line marks the number of tokens to be consumed:

INCREMENT Change telelogic 2015.04302 30-apr-2015 1 …

VENDOR_STRING=T10-999999:t,TLSTOK,1.0,Change,5  … // 5 Tokens worth.

  • This is an INCREMENT line indicating the total number of Tokens in the license

file. In this case, it is 200:

INCREMENT TLSTOK ibmratl 2.0 30-apr-2015 200 ISSUER=IBM

Rational License Server 8.1.1

Rational License Server 8.1.1 incorporates all vendor daemons (telelogic, rational, and ibmratl) into one. This change has also been incorporated into multiple Rational products such as ClearCase and ClearQuest.


References

http://publib.boulder.ibm.com/infocenter/rational/v0r0m0/index.jsp?topic=/com.ibm.rational.license.doc/topics/r_lic_log_file.html


http://www-01.ibm.com/support/docview.wss?uid=swg27023414&aid=1

Posted in OpenLM | Tagged , , , , , | Leave a comment

Application Note1023: OpenLM Agent Silent installation

Posted on January 16, 2012 by orik

Scope

This post details the silent install and uninstall commands for the OpenLM Agent Software

 

General

“Silent installation” is a form of software installation that does not display messages during its progress. This type of installation is specifically required for client applications such as the Active Agent, which need to be dispatched over a large number of workstations. The Active Agent silent installation utility facilitates installation of the Active Agent on client PCs, without showing user interfaces and without requiring user interaction (that is: no “next->next->…->finish” procedure).


In order to perform the Silent installation, please do the following:

  1. Download the Openlm Agent from the OpenLM site,

  2. Run the silent install / uninstall procedure through a command line, as elaborated below.

Download and install the OpenLM Agent

The OpenLM Active Agent and Utilizer Agent are available in the Downloads section on the OpenLM site.

OpenLM Utilizer Agent

The OpenLM Utilitzer Agent is the end user tool of the OpenLM system.

OpenLM Active Agent

The OpenLM Active Agent includes all the capacities of the OpenLM Utilizer Agent. On top of that,  he OpenLM Active Agent enables system administrators to define a timeout policy. In this manner, system administrators can save, close or suspend idle applications, in order to make more efficient use of licenses.

Silent Uninstall:

Format:
Open a command line prompt, and enter the following command line:
msiexec /x  <Product code> /quiet.

Notes:

  • Replace the product code, with the relevant product code as described in the section “OpenLM Product Code”.
  • The parameter /x uninstalls a product.

Example:
run: msiexec /x {E1E35EA8-6C9E-458E-8902-E36474186B14} /quiet
in order to silent uninstall OpenLM agent version 1.7.0.

Silent install:

Command format:

msiexec  /I  <msi installation file path> /quiet /norestart  <parameters>

Command Parameters:

SERVERNAME: OpenLM server name.
SERVERPORT: OpenLM server port number.
Note:  OpenLM server port is set to 7012 by default.

SHOW_NOTIFICATION_ICON(true/false):
False: Hides OpenLM Agent icon from the user. (This option is not recommended)
True : Show the notification icon at the taskbar.
Note: SHOW_NOTIFICATION_ICON is true by default.

ERROR_LEVEL: error level options: ALL/DEBUG/INFO/WARN/ERROR/FATAL/OFF
recommended logging level -> Error
Note: ERROR_LEVEL is set to ERROR by default.

TARGETDIR: specify the root destination directory for the installation.
Note: if no destination is specify, the default root destination directory is:
“C:\Program Files\OpenLM\OpenLM Agent”.


SHUT_WHEN_NOT_ACTIVE(true/false): Shutdown Active Agent automatically when an application is monitored as inactive for a certain period of time. this period is defined in the INACTIVITY_TIME parameter.
Note: SHUT_WHEN_NOT_ACTIVE is “false” by default.

INACTIVITY_TIME(seconds): Inactivity time in seconds. Meaningful only when SHUT_WHEN_NOT_ACTIVE = ”true”.

LANG: Choose the OpenLM language and direction.
Possible values: ”en-US”(English) ”ru-RU”(Russian) ”es-ES”(Spanish) ”de-DE”(German) ”fr-FR”(French)
”zh-CHS”(Chinese).
Note: LANG is set to “en-US” by default.

Installing extensions(only for the Openlm Active Agent):

The OpenLM Extension is a software module that enables OpenLM to provide dedicated services to specific software platforms (Please consult the OpenLM support page for information on supported platforms). The Save and Close mode is only applicable if the OpenLM Agent extension was installed as part of the OpenLM Agent installation.

Version 1.6.0 onwards
INSTALL_ARCGIS(1\0)
1: Install the ArcGIS extension.
0: Do NOT install the ArcGIS extension.

INSTALL_AUTOCAD(1\0)
1: Install the AutoCAD extension.
0: Do NOT install the AutoCAD extension.
Note:
1. In silent installation mode, both extensions (ArcGIS & AutoCAD) are not installed by default.
2. ArcGIS and Autocad extensions will not be installed in case the ArcGIS or Autocad applications are not installed regardles of their respective installation flags.

Version 1.7.XX onwards:

INSTALL_PLUGIN(1/0)

This plugin enables selecting the ArcGIS  license level to ArcInfo/ ArcEditor/ ArcView.

This plugin is relevant only for ArcGIS users.

1: Install the Plugin.

0: Do NOT install the Plugin.

Note: The Plugin is installed by default.

Examples

OpenLM Utilizer Agent

  • msiexec  /I  openlm_utilizer_agent_win.msi /quiet /norestart SERVERNAME=”145.13.4.121″ SHOW_NOTIFICATION_ICON=”false”
  • msiexec  /I  openlm_utilizer_agent_win.msi /quiet /norestart SERVERNAME=”145.13.4.121″ SHOW_NOTIFICATION_ICON=”true” ERROR_LEVEL=”ERROR”

OpenLM Active agent

  • msiexec  /I  openlm_active_agent_win.msi /quiet /norestart SERVERNAME=”olm_server” SERVERPORT=”7777″  ERROR_LEVEL=”ALL” LANG=”de-DE”
  • msiexec  /I  openlm_active_agent_win.msi /quiet /norestart SERVERNAME=”localhost” SHUT_WHEN_NOT_ACTIVE=”true” INACTIVITY_TIME=”20″ TARGETDIR=”D:\program files\OpenLM\OpenLM Agent”
  • msiexec  /I  openlm_active_agent_win.msi /quiet /norestart SERVERNAME=”localhost” SERVERPORT=”7012″  ERROR_LEVEL=”ALL” INSTALL_AUTOCAD=”1″

OpenLM Product Code

Version

Product Code

1.5.0

{ADF83757-EF49-474B-9A9B-BAC16E95BBB0}

1.5.1

{158B8FDC-A6A3-417B-BED1-51822C01EBAA}

1.5.1.1

{DC307335-161B-4FE9-95E6-BAB3DBEFCD19}

1.5.1.2

{51D28FA0-0AAB-4878-BCAD-48F2655F5785}

1.5.2

{EFD61272-3D32-40FB-965A-B1D2F65117FE}

1.5.3

{28D31048-EFA6-4B70-827A-D693FF616435}

1.5.4

{6E1E935C-A530-4D43-A4E3-9DCA859C03C6}

1.5.5

{C4A40345-6F9F-4D46-A5B1-BE06EF9A2C69}

1.6.0

{C6AED4C5-BC00-408F-B596-D3203C30A095}

1.6.0.1

{E29A0775-1F39-41FE-A2FC-A61F049D3C16}

1.6.0.2

{2E53D661-F6DD-45F6-83FF-F7ED3C5DEE34}

1.6.0.3

{5087491B-BE3E-489C-BAA7-60A99C851AA5}

1.6.0.4

{433F7B75-3913-4806-80EF-EC47A157BA6D}

1.6.0.5

{2EBF7B7D-E51E-49BB-A2E1-33D7098F145D}

1.7.0

{E1E35EA8-6C9E-458E-8902-E36474186B14}

1.7.0.1

{23654FAD-0160-4B49-907A-3C29E31083DA}

1.7.0.2

{375F711D-89CB-4686-81AB-0B996055215D}

1.7.03

{CC189C5C-86C3-450F-A701-60EC94E20CB4}

1.7.0.4

{CE361C51-90B9-4D26-95F9-7508EAC3C104}

1.7.05

{B0CF2536-B47E-4E7D-ADAE-905A0BC956A4}

1.7.0.6

{9699D6AB-AB79-4723-9F4D-0D8B1EADF508}

1.7.0.7

{AB1842F3-3125-494E-B511-90AF0298E633}

1.7.0.8

{50451FB5-62E0-4AFA-B29D-F200927B7CA2}

Revision Table

Revision

Author

Date

Notes

0.1 – Preliminary

Mira

Jan 16, 2012

Preliminary
Posted in OpenLM | Leave a comment

New introductory video for OpenLM

Posted on January 12, 2012 by oren
Posted in OpenLM | Leave a comment

Application Note 1022: Products and Packaged licenses in OpenLM

Posted on January 5, 2012 by orik

Scope

This Article deals with two adjacent subjects: Renaming features as products, and gathering these features into licensed packages.

  • Many features are only named as serial or coded strings, which bear little or no meaning for the end user. Renaming features is required in order to enhance readability and improve the understanding of EasyAdmin reports.
  • Package or Suit licenses are, as their name implies, a set of features which are licensed together as a package. These kind of licenses should be dealt differently than individual licenses, in order to avoid confusion.

The Products/Packages window

The interface for handling Product names Packages in EasyAdmin is the “Products/Packages” window. Open this window:
Click the OpenLM ‘Start’ button, and select ‘Administration’. The ‘Administration’ window opens.

Click the “Products/Packages” icon. The “Products/Packages” window opens.


Product names

The “Products/Packages” window enables users to define a meaningful product name to be displayed alongside a feature name. For example, the feature “40300MAP_5_0F” corresponds to the product “Map R5″ in the image above. In order to edit the product name, click the Product name column for the row of that feature. There the product name is editable. Click the Save icon to commit your changes. The Add and Delete buttons at the top right can be used to insert or remove feature/product name combinations.

The “Products/Packages” window provides an interface to OpenLM’s translation table between Feature Names and Product Names. If this translation table is well maintained then the data reported on the EasyAdmin screens will be more comprehensible.

Setting up a Package in EasyAdmin

Here is a frequently asked customer question:
“We subscribed our application as a design Suite / Package. Each suite license includes licenses to several products. OpenLM indicates that we have a lot more licenses than we actually have. Moreover: having drawn a certain number of licenses, OpenLM indicates a smaller percentage of license usage than expected.”
This kind of complaint directly indicates a misconfiguration of packaged licenses.

Autodesk case study

In order to organize licensed features in packages, use the “Products/Packages” window. In this example, we’ll study the case of the “Autodesk Design Product Suite Ultimate 2012” Package.

  • In  the “Products/Packages” window, select the “Autodesk Design Product Suite Ultimate 2012″ and check the “Is Package” checkbox.
  • Click the “Save” button.
  • Close and reopen the “Products/Packages” window. It is necessary to close and reopen the window after marking a product as a package.

  • Add each product in the suit to the list:
    • Select an item in the list, or click “Add” to add the product if you can’t find it there.
    • Select “Autodesk Design Product Suite Ultimate 2012″ as the “Parent Package”. In the example below, the product suit corresponds with feature # 85796PDSU_2012_0f.
    • Click the “Save” button.
    • Repeat this for each item in the Package.



Revision Table

Revision Author Date Note
0.1 – Preliminary Orik Jan05, 2012 Preliminary

Posted in OpenLM | Tagged , , , , | Leave a comment

OpenLM supports DSLS license management monitoring

Posted on January 2, 2012 by orik

OpenLM has been dedicated to providing precise license usage monitoring and statistics data gathering for a wide variety of license management tools.

In the passed several months, we have witnessed the transition of Dassault Systemes’ license management system from IBM LUM to Dassault’s proprietary DSLS (Dassault Systemes License Server) system. Moreover, The IBM LUM system is meant to become unsupported by the year 2014.

This shift has produced a new requirement for the OpenLM Utilizer tool: Support of DSLS license management monitoring and data gathering, with the same level of service as with the predecessor IBM LUM.

We are happy to announce that OpenLM has produced the required modules to interface the current OpenLM release version (1.7), and support DSLS license management monitoring. This is in conjunction with the existing License managers in its arsenal, namely FLEXlm, Sentinel RMS, Sentinel HASP, RLM, LMX, and other leading license managers.

Following a short survey of the market, it is our opinion that DSLS license manager monitoring solutions are a scarce commodity, and that this new OpenLM feature is a unique character indeed.

Posted in OpenLM | Leave a comment

Application Note 1021: Interfacing OpenLM to a DSLS license manager

Posted on January 2, 2012 by orik

scope

In order to check the interface of OpenLM to a DSLS license manager, the Administrator should apply several configurations to the OpenLM Server and OpenLM Broker. This document elaborates these required operations.

General

The Broker is installed on the same machine as the DSLS License Server. It runs the Data inquiry command on that machine, and retrieves the answer from the DSLS license manager. This text is then parsed and rearranged in a standard XML format. The answer is henceforth sent to the OpenLM Server, which in turn gathers and display the DSLS usage statistics.

Additional files:

Running a DSLS interface to the OpenLM Server requires three additional pieces of code. These need to be saved on the DSLS license manager machine, and are used in the OpenLM Broker “Data Inquiry” command line:

  • OpenLM_License_Output_Converter.exe : this is the conversion program.
  • log4net.dll: This DLL needs to be located under the same directory as the OpenLM_License_Output_Converter.exe file, on the DSLS license manager machine.
  • input.txt : This is a text file which is an argument for the DSLS DSLicSrv command. The contents of the command input file should be edited as follows: (without the remarks, of course)

    • connect <server> <port> // Connect the administration tool to // the license server. Type in the License // server name and port

    • getConfig // Get license server configuration

    • getLicenseInfo // Get license information

    • getLicenseUsage -all // Show current license usage

    • disconnect // Disconnect from the license server.


OpenLM Broker Configurations

  1. Install the latest OpenLM Broker version. At the time of writing this revision (Rev 0.1), the OpenLM Broker version is 1.7.1.7. Refer to this document for General information regarding Broker download, installation and configuration.
  2. In the Broker Configuration form, set up a license server according to the “License Servers – Add a license server“ section in the Application Note mentioned above.
  3. Set up the DSLS designated License Manager Port according to the “License Servers – License Manager Port” section. Note: The port number should match the one that interfaces the OpenLM Server (See below).
  4. Set the Port type to “Other”.
  5. Set the “Data Inquiry” command line for the DSLS designated port. The format of this line should be as follows:


OpenLM_License_Output_Converter DSLS <command> <arguments> .
For example:  OpenLM_License_Output_Converter.exe DSLS DSLicSrv.exe “-admin -I input.txt”

    1. OpenLM_License_Output_Converter.exe should have a full path, enclosed by parentheses.
    2. DSLS
    3. The DSLicSrv command should have a full path, enclosed by parentheses. This command has 3 arguments. The arguments should be enclosed by parentheses.
      1. -admin
      2. -I
      3. input.txt file; should have a full path enclosed by parentheses. If the path includes spaces, it should be enclosed by slashed parentheses, i.e.: \” fullpath\”

Here is an example for a “Data Inquiry” command line: “C:\fullpath\OpenLM_License_Output_Converter.exe” DSLS “C:\fullpath\DSLicSrv” “-admin -I \”C:\My Full Path input.txt\”"

  1. Set the Vendor name (e.g.: Dassault Systemes)

OpenLM Server Configuration

  1. Install the latest version of the OpenLM Server. At the time of writing this document the latest version is 1.7.1.8.
  2. Set up the OpenLM Server to interface the DSLS license server:
  • On the “License Servers” tab, click the “Add” button.
  • Check the “Enabled” check box
  • Select the “Other” Type.
  • Give the license server a descriptive name, e.g.: DSLS demo
  • Type in the Host name (Or IP) as was set in the Broker configuration form, e.g: license-server1. This should be exactly the same name (Or IP) as the one used for Broker Configuration.
  • Type in the License server port; e.g.: 27002.



Conclusion

This sums up the required configuration of OpenLM components in version 1.7.1.7 to interface DSLS license managers.
In order to verify its activity, open the EasyAdmin web application to see the added DSLS server.

Posted in OpenLM | Leave a comment

OpenLM Newsletter December 2011

Posted on January 1, 2012 by orik

Dear Valued Customers,

We would like to take this opportunity to send you warm greetings for the upcoming holiday season, and wish you all a happy and peaceful new year.

We would also like to sincerely thank you for your trust and choice of OpenLM’s software, as the product to monitor and manage your valuable licensed applications.

This year has been an exciting one for us at OpenLM. It has seen many developments and much progress in the evolution of our products. Much of this progress is due to our growing circle of faithful customers, who through their continuous feedback and attentiveness helped us push this product forward, to what it is now. For this – Thanks again.

We have officially released OpenLM Version 1.7 at the beginning of July 2011 and since then it has been installed on many customers’ sites. This version has integrated many new features that were required by our customers, and many fixed bugs – without which our job wouldn’t be so interesting ( (; ).

Version 1.7 also features improved performance and an enhanced user interface. Additional European and Asian language support has also been introduced in this version. All these are subject to continuous improvement, through customer feedback.

2011 has also seen the kick start of OpenLM’s Mobile interface. This application runs on mobile devices such as Android, Blackberry and Apple’s iOs. We are still looking for customers that would participate in a beta program for the new interface. If you are interested, please contact us at: orik(at)openlm(dot)com.

We are currently working on a new web site for OpenLM (Finally !) that would be clearer, more intuitive and graphically nicer than the old one. It would also include enhanced linking to relevant sites and tutorials. It should be ready for a preliminary launch in the upcoming days.

We are also vigorously working on the development of OpenLM’s version 1.8. We are always happy to receive requests for new features for the product. Please don’t hesitate to report any new required feature or problem on our issue reporting system bug.openlm.com, or contact our support team at support(at)openlm(dot)com .

Sincerely,

Oren Gabay, CEO

OpenLM Team

 

Posted in OpenLM | Tagged , , , , , | Leave a comment

Application Note 1020: Manually Removing Licenses Using the EasyAdmin web application

Posted on January 1, 2012 by orik

Scope

OpenLM’s main Administrative interface, the EasyAdmin web application, enables administrators to manually retrieve licenses via designated action buttons on the “Active Products” window. This option has proven to be very useful, however it seemed to have raised certain inquiries by customers. This document sums up the properties and limitations of the system’s license removal capabilities.

The “Active Products” window

The “Active Products” window displays data about licenses that are used at the current time.
Each line of the display represents a user who is momentarily using a specific license. It shows specific details about the software session such as start time and duration. Some of the information presented in this window originates in the OpenLM Agent module, so a proper installation of the OpenLM Agent (Active Agent or Utilizer Agent) on each client workstation is a prerequisite to obtaining this data.

With the “Active Products” window,  administrators can monitor individual workstations that run licensed applications. They can detect idle applications, and shut down such applications with a mouse click. In order to retrieve licenses and shut down applications, an OpenLM Active Agent module must be installed on each client workstation.

User Idle

If the user has not been actively using the license, the idle time period would be shown in the “User Idle” column. This information is sampled by OpenLM Agent modules (Active Agent or Utilizer Agent) on each client workstation, and sent to the OpenLM server. The sample period is set by the Agent policy’s “Agent report” period, as in the example below (set to 60 sec).

Removing licenses

Administrators have the option to manually remove a license from a specified workstation. This is done by highlighting the user row on the Active Products window and clicking the “Remove License” icon (See image below).
There are several constraints that are specific to this feature:

  • The end user must have been inactive for a minimum period of time in order for his license to be retrieved.
  • If the license is not really associated with any real product activity on the specified workstation (as happens when a license gets artificially “frozen” on a computer), then the license will be freed and will be returned to the pool of available licenses.
  • If the worker is actually using the product, then re-obtaining a license would be automatically attempted. If this happens the license for that product and workstation will re-appear on the active products screen, with a new handle number.
  • Retrieval of licenses may only be accomplished once a minimal period of time has elapsed since the license was checked out. This value is set by default to 5 minutes in compliance with FLEXlm license manager’s limitations.


Closing applications

In order to actively close an application on the workstation,  an administrator should highlight the relevant row, and click the Close Application icon (See image below).
This operation will retrieve the license back to the license pool, save the open project,  and the application itself will be shut down.
There are some constraints that are specific to this feature:

  • It requires a proper installation of the OpenLM Active Agent module.
  • It works only extension-based active agents. At the time of writing this revision (Rev 1.0), these include ArcGIS and AutoCAD.


Common Constraints

There are several constraints that are common to both the License Removal and Application Closure features.These are as follows:

  • At the time of writing this revision (Rev 1.0), These features are only available when working with the FLEXlm license manager.
  • An OpenLM Agent module must be properly installed on each Client workstation. The Application closing feature requires the Active Agent. The License Removal feature may use either the Active Agent or the Utilizer Agent.
  • Borrowed licenses (AKA Linger licenses) may not be retrieved via the EasyAdmin application.


Revision table

Revision Date Author Note
0.1 – Preliminary Jan 01, 2012 Orik Preliminary
1.0 Jan 01, 2012 Orik Revised

Posted in Agent, Autocad, EasyAdmin, ESRI, OpenLM | Tagged , , | Leave a comment

Autodesk cascade licensing and the PLIST

Posted on December 14, 2011 by orik

Autodesk cascade licensing and the PLIST.

Feature codes

When you start the network version of an Autodesk product, a request is made to the network for a license. The Network License Manager controls the licenses that are issued and handles license requests through feature codes. Feature codes are specific to the networked application; Each network version of an Autodesk product has a specific FLEXnet® feature code.

Cascade Licensing

Cascade Licensing allows a product to obtain a license from a network license manager pool when that license manager is servicing more than one product. Cascading was implemented primarily to address mixed-product environments where both suite and base products co-exist.

PLIST

For Autodesk products that are included in a product suite and are also sold as an individual product, licenses are allocated based on a sequence of priorities defined in a PLIST (priority list).
The PLIST increment section defines the search order and priority for network licensed products sold as a series or bundle.

This PLIST increment was included in the license file and needs to exist there only once. It should always include the most recently released Autodesk products; Deleting or editing this PLIST increment is not supported by Autodesk.

PLIST example:

The VENDOR_STRING is split into groups denoted by a letter and a number. For example, A07.
The groups contain feature codes for the applicable series or sets of products. These groups are subject to change as new product offerings are released.
At the present time the following groups are included in the PLIST VENDOR_STRING:
Autodesk® Land Desktop, Autodesk® Civil 3D®
A07:51600ACDLAND_2007_0F:52200CIV3D_2007_0F
AutoCAD® Mechanical, Autodesk Inventor® Series, Autodesk Inventor® Professional
B07:51900AMECH_PP_2007_0F:51300INVBUN_11_0F:52900INVPRORS_11_0F:53000INVPROSIM_11_0F:51400INVPRO_11_0F
AutoCAD®, Autodesk AutoCAD® Revit® Series—Building, Autodesk AutoCAD® Revit® Series—Structure
C07:51200ACD_2007_0F:52500REVITS_9_0F:53700REVSU_3_0F
Autodesk® Revit® Building, Autodesk AutoCAD® Revit® Series—Building
D07:52600REVIT_9_0F:52500REVITS_9_0F
Autodesk Internal Test Increment – not used by customer products
E07:51200ACD_2007_0P:51300INVBUN_11_0P
Autodesk® Building Systems, Autodesk AutoCAD® Revit® Series—Systems Plus
F07:51800BLDSYS_2007_0F:53100REVSYP_1_0F
Autodesk® Revit® Structure, Autodesk AutoCAD® Revit® Series—Structure
G07:53400REVITST_3_0F:53700REVSU_3_0F

ProductInformation.pit

For the 2010 products, the PLIST increment is no longer include in the license file but is now stored in a new external file named ProductInformation.pit. License files will still include PLIST increments for legacy products, however 2010 products will reference the ProductInformation.pit file for the required PLIST information.
The ProductInformation.pit file is automatically created on the local machine when a product gets installed and there will only be one ProductInformation.pit file, shared by all installed products. The file is created when the first 2010 product is installed and is appended to with each subsequent product installation. Likewise, when a product is uninstalled it unregisters itself from the ProductInformation.pit file. When the last product has been unregistered from the file, ProductInformation.pit is automatically removed from the machine.

With the exception of the PLIST, the ProductInformation.pit file does not contain PACKAGE information or any other information that is normally included in the license file.

Location

The ProductInformation.pit file is created on the workstation in the following locations:
XP: C:\Documents and settings\All Users\Application Data\Autodesk\ADLM\ProductInformation.PIT
Vista: C:\ProgramData\Autodesk\ADLM\ProductInformation.PIT

Constraints

Just as with other licensing components, the ProductInformation.pit file should not be moved from its default location. In addition to the PLIST increment, the ProductInformation.pit file contains other licensing information for the installed products and a 2010 product will not run correctly without this file.
Since the ProductInformation.pit file is encrypted and unreadable, One could no longer inspect the PLIST to determine the cascade order for 2010 products.

Combining license files example

To add additional product licenses to the Network License Manager, you must combine the separate licenses into one license file and configure a single service in LMTOOLS to use this combined license file. This action involves the PLIST VENDOR_STRING, and as such is an example for its role in the license file.

To combine license files for Autodesk products into one license file, you must edit the existing license file and add lines from the new license file. Do not configure a separate service for the new Autodesk product.
To edit the existing license file, copy all of the lines from the additional product license file starting at the line beginning with PACKAGE.
The following is an example of how to add AutoCAD 2007 licenses to an existing AutoCAD 2006 license file:

Existing license file for AutoCAD 2006:
SERVER servername 0123456789ab
USE_SERVER
VENDOR adskflex port=2080
INCREMENT 48800ACD_2006_0F adskflex 1.000 permanent 5 \
VENDOR_STRING=nfr:permanent BORROW=4320 SUPERSEDE DUP_GROUP=UH \
ISSUED=01-Sep-2006 SN=123-45678900 SIGN=”06DE F4C2 998E ABD3 \
2413 D3A0 77EB 0CCE 203C 7BEA 73A3 25F5 0A8D EA5E E26D 1C18 \
968B BE2E 966D C293 AEF0 97F5 9776 057F 652C 6050 D904 A755 \
5A35 7909″ SIGN2=”1A49 5DFA 4C92 D6DC BD74 7D15 6B3F 730D A342 \
EEBC C63F 1838 FFBC 2CD8 B6E0 0113 0E3D 540F AE73 C8B4 C90C \
BA1F 049D             9464 0477       8D53 06AD 0992 5B16 3A92″
License file received for AutoCAD 2007:
SERVER servername 0123456789ab
USE_SERVER
VENDOR adskflex port=2080
INCREMENT 51200ACD_2007_0F adskflex 1.000 permanent 5 \
VENDOR_STRING=nfr:permanent BORROW=4320 SUPERSEDE DUP_GROUP=UH \
ISSUED=01-Sep-2006 SN=123-45678900 SIGN=”19DA F1B9             2187 1910       \
10DB 61CD 4013 BC85 40EE 6AAC F11C 8AA8 9E49 3833 FBDB 0E68 \
1172 C1FE 704F 611C EAF3 E008 14DC C713 35AB 6D33 7C06 0DE2 \
0A47 BDC2″ SIGN2=”0B1B 3967 DC25 1AA2 3DBA 4F29 E076             4472 9716       \
5A38 9CA2 1A3E 2001 68CC 59D4 05CB 0699 9B5A F358 56B7 5056 \
DE42 7FBB ED04 AF77 CDB4 AC31 4564 88A4 5132″
INCREMENT PLIST adskflex 1.000 permanent 1 \
VENDOR_STRING=A07:51600ACDLAND_2007_0F:52200CIV3D_2007_0F;B07:51900AMECH_PP_2007_0F:51300INVBUN_11_0F:52900INVPRORS_11_0F:53000INVPROSIM_11_0F:51400INVPRO_11_0F;C07:51200ACD_2007_0F:52500REVITS_9_0F:54100REVITS_9_1F:53700REVSU_3_0F:54200REVSU_4_0F;D07:52600REVIT_9_0F:52500REVITS_9_0F;E07:51200ACD_2007_0P:51300INVBUN_11_0P;F07:51800BLDSYS_2007_0F:53100REVSYP_1_0F:54500REVSYP_2_0F;G07:53400REVITST_3_0F:53700REVSU_3_0F;H07:54300REVIT_9_1F:54100REVITS_9_1F;I07:54400REVITST_4_0F:54200REVSU_4_0F \
SUPERSEDE ISSUED=01-Sep-2006 SIGN=”140B 330F 51E2 F3C7 BDCF \
F34F 4FC6 40C5 1303 82A3 83EA 905B 975D 8E99 BACC 1843 6904 \
C47E 3C16 8806 F386 8BD5 BA5E 283E 1568 D2F0 4CFE 223C DF91 \
1A38″ SIGN2=”0C71 73DD 721F F07E 7202 CBB9 CBAB E834 99F1 2C45 \
2719 3F00 58EF 63E6 B9F1 11C3 687F 4861 70F4 ABE5 B9FF F23A \
53F1 71D7 CD26 E984 145A A86B 62C2 5F6F”
Combined license file for AutoCAD 2006 and AutoCAD 2007:
SERVER servername 0123456789ab
USE_SERVER
VENDOR adskflex port=2080
INCREMENT 48800ACD_2006_0F adskflex 1.000 permanent 5 \
VENDOR_STRING=nfr:permanent BORROW=4320 SUPERSEDE DUP_GROUP=UH \
ISSUED=01-Sep-2006 SN=123-45678900 SIGN=”06DE F4C2 998E ABD3 \
2413 D3A0 77EB 0CCE 203C 7BEA 73A3 25F5 0A8D EA5E E26D 1C18 \
968B BE2E 966D C293 AEF0 97F5 9776 057F 652C 6050 D904 A755 \
5A35 7909″ SIGN2=”1A49 5DFA 4C92 D6DC BD74 7D15 6B3F 730D A342 \
EEBC C63F 1838 FFBC 2CD8 B6E0 0113 0E3D 540F AE73 C8B4 C90C \
BA1F 049D             9464 0477       8D53 06AD 0992 5B16 3A92″
INCREMENT 51200ACD_2007_0F adskflex 1.000 permanent 5 \
VENDOR_STRING=nfr:permanent BORROW=4320 SUPERSEDE DUP_GROUP=UH \
ISSUED=01-Sep-2006 SN=123-45678900 SIGN=”19DA F1B9             2187 1910       \
10DB 61CD 4013 BC85 40EE 6AAC F11C 8AA8 9E49 3833 FBDB 0E68 \
1172 C1FE 704F 611C EAF3 E008 14DC C713 35AB 6D33 7C06 0DE2 \
0A47 BDC2″ SIGN2=”0B1B 3967 DC25 1AA2 3DBA 4F29 E076             4472 9716       \
5A38 9CA2 1A3E 2001 68CC 59D4 05CB 0699 9B5A F358 56B7 5056 \
DE42 7FBB ED04 AF77 CDB4 AC31 4564 88A4 5132″
INCREMENT PLIST adskflex 1.000 permanent 1 \
VENDOR_STRING=A07:51600ACDLAND_2007_0F:52200CIV3D_2007_0F;B07:51900AMECH_PP_2007_0F:51300INVBUN_11_0F:52900INVPRORS_11_0F:53000INVPROSIM_11_0F:51400INVPRO_11_0F;C07:51200ACD_2007_0F:52500REVITS_9_0F:54100REVITS_9_1F:53700REVSU_3_0F:54200REVSU_4_0F;D07:52600REVIT_9_0F:52500REVITS_9_0F;E07:51200ACD_2007_0P:51300INVBUN_11_0P;F07:51800BLDSYS_2007_0F:53100REVSYP_1_0F:54500REVSYP_2_0F;G07:53400REVITST_3_0F:53700REVSU_3_0F;H07:54300REVIT_9_1F:54100REVITS_9_1F;I07:54400REVITST_4_0F:54200REVSU_4_0F \
SUPERSEDE ISSUED=01-Sep-2006 SIGN=”140B 330F 51E2 F3C7 BDCF \
F34F 4FC6 40C5 1303 82A3 83EA 905B 975D 8E99 BACC 1843 6904 \
C47E 3C16 8806 F386 8BD5 BA5E 283E 1568 D2F0 4CFE 223C DF91 \
1A38″ SIGN2=”0C71 73DD 721F F07E 7202 CBB9 CBAB E834 99F1 2C45 \
2719 3F00 58EF 63E6 B9F1 11C3 687F 4861 70F4 ABE5 B9FF F23A \
53F1 71D7 CD26 E984 145A A86B 62C2 5F6F”

Once the license files are combined, click ReRead License File on the LMTOOLS Start/Stop/Reread tab to make the changes effective.  Sometimes it may be necessary to stop and restart the license manager before the new license file will be read.

References:

The information in this paper was gathered from the following Autodesk links:
Without a Net
PLIST Increment Vendor_String
How to combine license files for multiple Autodesk products

Posted in Autocad | Tagged , , | Leave a comment

OpenLM Maintenance Release Version 1.7.1.6

Posted on December 8, 2011 by orik

OpenLM Maintenance Release Version 1.7.1.6

Version 1.7.1.6

Version 1.7.1.6 is a maintenance release to version 1.7. It contains some bug fixes to problems found in previous versions. We  recommend that users to whom these problems may be relevant to upgrade their system to this version.

Upgrading

In order to upgrade to version 1.7.1.6:

  1. Backup your DB file (Typically located in: C:\Program Files\OpenLM\OpenLM Server\db)
  2. Stop the OpenLM Server service
  3. Make sure ALL windows are closed; especially the services window.
  4. Install the new version on top of the existing one.

What’s new in version 1.7.1.6?

OpenLM Server:

  1. Sometimes Flexlm sends temporarily inaccurate license reports. In EasyAdmin, this was experienced as duplicate overlapping license draws. The problem was avoided by implementing a time-wise filter, to ensure that changes in the license are consistent for an hour. This change impacts the system’s operation:
    1. Momentary changes are ignored
    2. Latency of true changes’ display has increased.
  2. Two problems reading Option files; Option file may contain some unusual characters (like &) at the title. To fix that we also made a change at the OpenLM Broker. The second issue we had was in reading option file lines with a comment at the middle of the line.
  3. Fixed the repetitive “Please select time zone” bug in EasyAdmin, when running Internet Explorer IE8 & IE9. This bug stems from the limitation that these browsers impose on the amount and size of stored cookies. The workaround for IE8 & IE9 users is giving up on some of the cookies in IE8 & IE9; such as the ones that save the recent size and location of the window. Users of FF and Chrome are not impacted by this change. On the upcoming version 1.8, the the cookies mechanism would be replaced, and again there would be no difference in user experience between browsers.

OpenLM Broker (version 1.7.1.7):

  1. Add pane to installation , explaining about the configuration tool, to prevent confusion.
  2. Fix some type in configuration tool.
  3. Fix automatic detection of ports on windows 64bit. read the Wow6432Node registry key.
  4. Improved Option file reading. See item #2 in the OpenLM server section, above.
Posted in Broker, EasyAdmin, FLEXlm, OpenLM, Server | Tagged , , | Leave a comment