Managing Autodesk Licenses Effectively

Optimizing license usage is often overlooked at engineering companies, even when trying to contain costs in the IT budget. When times are tough, this is a quick and easy way to reduce costs. Even when the orders are rolling in, there is no need to spend money on licenses that are surplus to your requirements. Many of OpenLM’s customers have used our license management software to trim down their license portfolio of excess licenses, especially licenses from the Autodesk family.

The recent changes made by Autodesk to their licensing policy going forward have made it even more critical for customers to keep a tight control over their Autodesk license usage.

While Autodesk provide the Flexera license manager to customers, which does provide some information of how licenses are being used within the company, it has been designed from the vendor’s viewpoint of ensuring compliance. To get the transparency and control that every license administrator needs, a customer-centric software product is needed. OpenLM was originally designed by license managers who worked at a site that made extensive use of ArcGIS , and had the same challenges. Their success in building software that helped companies manage ESRI licenses next expanded to helping Autodesk customers with their AutoCAD, Revit and other software.

The  License Administrator’s Wishlist

The license manager needs deep insights into how any vendor’s licenses are utilized. This is needed on a daily basis for optimizing usage, periodically for management reporting and annually or on demand to plan and forecast license requirements for the next year or for an anticipated project. This is rarely available to the extent needed using a vendor’s license management tool, and it is recommended that license management software that is vendor-agnostic is investigated. The features that a good license management package should provide include:-

  • Visibility into license usage on at least a minute-by-minute basis
  • Minimising license denials to users
  • Easy identification of idle licenses
  • The ability to “harvest” idle licenses, either automatically or manually
  • Messaging options to inform users of license availability where they were denied
  • The ability to see a consolidated view of licenses where there are multiple pools and named users
  • Comprehensive reporting that can be used for management reporting to management
  • Financial reporting on usage across the organization  that supports chargebacks to cost centers and projects, based on their usage
  • Forecasting to indicate a need to purchase or dispense with licenses, both on a regular basis and for annual license renewals or new projects
  • A graphical interface that allows the license administrator to manage licenses for a product without having to log in to the vendor’s product to make changes.

To really understand and test for these features, the software should be evaluated on a trial basis. OpenLM is confident that they provide all these features for Autodesk  software products as well as thousands of other engineering software tools.

The Daily License Challenge

Most engineering software can be bought under a concurrent or network user model, which enables the company to buy the minimum of licenses needed to satisfy user demand. The license administrator has to perform a balancing act between keeping his users happy and productive by always having licenses available, while managing the license pool effectively and avoiding further purchases.

To do this, he needs to manage idle licenses. Users have a tendency to book out licenses at the start of day and not return them until the end of day, even when they are away attending meetings or on-site. Some users also will hang on to their licenses overnight, so that they do not need to book them out again when they come into work the next morning.

The license administrator needs to be able to take control over idle licenses and “harvest” them, releasing them back into the pool. The amount of time that a license is allowed to remain idle and whether the session is saved or not will depend on the individual requirements of the company and should have a defined policy and business rules.

He also needs an early warning system that licenses are being denied (although angry users phoning in will happen in any case). OpenLM, with their knowledge of what it is like to be in the driver’s seat, have built these features for Autodesk customers:-

  • License denial reporting
  • Real-time reporting on usage
  • Reporting on inactive, hanging or otherwise unavailable licenses
  • The ability to harvest idle and unused licenses and release them back into the pool
  • The option to suspend, save or terminate an idle session
  • The ability to automatically notify users who were denied that a license is now available for them
  • Distinguishing between “true” denials and denials where the software was available and booked out shortly after the denial
  • Extensions and other aids that allow the license administrator to build business rules, add alerts or otherwise customise OpenLM to fit the customer’s environment

The provision of all these features makes idle license management a breeze. For customers like Array Architects, they were able to confirm their suspicions that users were not releasing their software at and of day, and could now release all those licences, so that the entire pool was available at the start of the next business day.

Feedback and Reporting

OpenLM has fine-tuned the management of Autodesk software products to second-by-second visibility. Reports showing usage statistics, daily peaks and troughs of user demand and usage by group are all standard. There is also an extension that enables the license administrator to create custom reports.  Anything that needs to be known about AutoCAD licenses or any other Autodesk product can be reported on.

  • Consolidated views of multiple license servers, user groups is enabled
  • Heat maps and graphs on license usage come standard with the application
  • Forecasting for renewals is available
  • Financial reporting for chargebacks based on usage is a standard feature
  • Accurate reporting on usage, that can be compared against Autodesk’s calculations.

These reports can demonstrate to the executive how well license optimization is progressing, as well as quantifying cost savings and ROI. Many of our customers have achieved an ROI in under three months of use.  

Going Forward

The determination of Autodesk to discontinue all network licenses and offer only subscription licenses in the future is a headache for most customers who have a considerable investment in Autodesk products and use concurrent licensing to get the best value for their money.  Every organization will have to do an evaluation of what a conversion to subscription licenses will cost them and whether they should go ahead with the change while the discounted price is still available. OpenLM provides the intelligence to make a decision based on an accurate assessment of the situation.

Please follow and like us:

OpenLM monitoring of Aveva PDMS and Aveva Marine licenses.

Aveva PDMS and Aveva Marine environments

Aveva Marine is a comprehensive suite of software modules for offshore and shipping construction projects. It integrates several views and disciplines into a single project space for superior visualization and integrity between the project components.

Aveva PDMS provides similar capabilities for 3D plant designing. Users are able to select, place, assemble and check the integrity of complex 3D plant schemes.

Aveva licensing

  • Prior to the 12.1. series’ version, AVEVA Marine and AVEVA Plant (PDMS) employed the Flexera Flexnet manager (FlexLM) concurrent license manager to dispense and keep track of floating Aveva licenses. OpenLM fully supports FlexLM license monitoring.

  • In the 12.1 series, Aveva has drifted from the FlexLM solution to the Sentinel RMS license management tool to manage their floating licenses. They still kept the lmutil tools within their installation folders, but from our experience – running these lmutil lmstat commands produced empty results.

  • Instead, license usage information could be obtained by the Sentinel RMS command:  lsmon.exe (In fact – we needed to upgrade the lsmon.exe version to “Sentinel RMS Development Kit 8.5.3.0035 Application Monitor” in order to match our Aveva version). OpenLM fully supports Sentinel RMS license monitoring.

  • Another surprise Aveva 12.1 had stored for us was the license file, which was a type of hybrid between FlexLM and RMS. It was in XML format and contained the following headers:

<?xml version=”1.0″ encoding=”utf-8″?>

<CompositeLicenseFile xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns:xsd=”http://www.w3.org/2001/XMLSchema”>

<Hostname> … </Hostname>

<RMSlicenseFile> … </RMSlicenseFile>

<FlexLicenseFile> … </FlexLicenseFile>

<ProductFeatureMappingFile> … </ProductFeatureMappingFile>

<ARMS_ID> … </ARMS_ID>

<RevokeList> … </RevokeList>

</CompositeLicenseFile>

Please follow and like us:

FlexLM License file format

General

FlexLM license files are in effect an agreement between the license vendor and the end user; They elaborate the number of available licenses, the check – out policy for each license, validity and expiration date of each license etc. The FlexLM License Manager Daemon (lmgrd) interprets the license file to dispatch license requests to different license vendor daemons.

This document is a short account of the format and syntax of the license file, and its effect on licensed applications’ utilization.

SERVER line

License files usually begin with a single SERVER line, or three SERVER lines for Server triad configurations. The SERVER line specifies the license server’s

  • Hostname

  • Hostid (MAC address) of the and

  • TCP/IP port number of the license manager daemon (lmgrd). If no port is specified then the first available port in the range 27000 to 27009 will be used.

Syntax

Server line syntax is as follows:

SERVER <server name> <host id> <lmgrd port>

Example

SERVER my_server 001122334455 27000

USE_SERVER

VENDOR line

The VENDOR line specifies the

  • Vendor daemon name and path. lmgrd uses this line to start the vendor daemon.

  • Options file path

  • Vendor daemon TCP/IP port number (default 2080).

Syntax

VENDOR vendor [vendor_daemon_path][[options=]options_file_path] [[port=]port]

Example

VENDOR adskflex adskflex.opt port=2080

FEATURE / INCREMENT line

FEATURE / INCREMENT lines describe specific licenses. A single FEATURE (or INCREMENT) line may be followed by several INCREMENT lines, creating separate license pools.

Syntax

{FEATURE|INCREMENT} feature vendor feat_version exp_date num_lic SIGN=sign [optional_attributes]

Example

FEATURE MayaUnltdf sgiawd 7.000 17-aug-2005 2 001122334455

PACKAGE Lines

PACKAGE lines provide an outline to licensing product SUITEs, and facilitate distribution of features which largely share the same FEATURE line arguments. PACKAGE lines are ineffective on their own account; they require FEATURE / INCREMENT lines to effectively activate these licenses.

Syntax

PACKAGE package vendor COMPONENTS=pkg_list SIGN=pkg_sign

Example

PACKAGE suite_example vendor_name version SIGN=12345 COMPONENTS=”feature_1:version_1:3 feature_2:version_2:4″

FEATURE suite_example vendor_name version issue_date 2 SIGN=54321 SN=123

In this case, checking out either feature_1 or feature_2 will also check out the suite_example suite. The total number of available licenses is 3×2=6 for feature_1, and 4×2=8 for feature_2.

Please visit www.openlm.com for more information about software license management.

Please follow and like us:

Siemens PLM license analysis and license monitoring

OpenLM supports license monitoring of a wide, and ever growing variety of license managers. Among those are Flexera FlexLM (Flexnet publisher), IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, Reprise RLM, and LM-X.

This group of license management utilities encompass a great variety of licensed products. One group of such licensed products is the Siemens PLM (formerly UGS) 3D & 2D Product Lifecycle Management (PLM) group.

The OpenLM tool provides high level of application usage management and optimization for PLM licenses, providing clear and valuable usage information for Managers, License Administrators and End Users.

Siemens PLM Common Licensing

Siemens PLM employs the “Siemens PLM Software Common Licensing” tool in order to deliver a consistent licensing implementation to all PLM products. It is based on the Flexera FlexNet license management tool, and has incorporated some unique characteristics:

  • The PLM Common Licensing toolkit has adopted the Siemens PLM Software-wide licensing vendor daemon ugslmd. Consequently, all Siemens PLM products gain access to common licenses utilize this same daemon.
  • The PLM Common Licensing toolkit employs a unified license file for all PLM products.
  • The default port for the PLM ugslmd vendor daemon is 28000. That was decided in order to avoid conflicts with other applications, using the default FlexLM port 27000.
  • Composite ID (CID): This is a 12 digit hexadecimal unique machine identifier that is used as part of Siemens PLM Software licensing to lock a license file to a machine. The CID is distinguished from a FLEXnet hostid by the keyword “COMPOSITE=”.
  • NX bundles and Suite Packages: These are packages that Siemens PLM Software has predefined to meet the general needs of customers at a lower cost than purchasing individual floating licenses.

For more information on Siemens PLM Software Common Licensing, please refer to this PDF.

The OpenLM advantage

The OpenLM license monitoring tool incorporates many advantages in PLM software maintenance for members of all positions in an organization. In a nutshell:

  • Managers get a clear picture of their Software assets.
  • System Administrators are freed from managing licenses.
  • End users enjoy improved PLM license availability.

Additionally, OpenLM v 1.8 Automatically sorts NX suites, to clearly display Siemens PLM application usage measuring in its true context.

Please follow and like us:

Setting FlexLM port numbers statically

Flexnet / FlexLM ports numbers may be set statically by declarations made in the FlexLM license file. When remain undeclared, these ports would be set randomly every time the license manager is started.

1. In order to set the port connecting the license manager with the installed applications:

On the server side, on the license file (<license>.lic), add a port number to the end of the SERVER line, e.g.:

SERVER <ServerName> <HostId> <PortNumber>

On the client side, on the <license>.dat file add the same number to the end of the SERVER line, e.g.:

SERVER <ServerName> ANY <PortNumber>

2. In order to set the license manager to interface the Vendor over a predefined static port number, add this number in the end of the VENDOR line, in the license file on the license server machine, e.g.:

VENDOR <VendorName> PORT=<VendorPortNumber>

In order for these changes to take affect, you would need to reread the license file. You may do that by clicking the “Reread License file” button, under the “Start/Stop/Reread” tab in Flexera’s LMTOOLS application.

The OpenLM license monitoring tool interfaces these ports in order to extract license statistics, and reliable license usage reports.

For any further information about license management, please visit the new OpenLM site, or address us directly on support@openlm.com.

Please follow and like us:

How do I know the FlexLM license manager port number ?

OpenLM employs the Flexnet / FlexLM reporting mechanism to monitor and optimize concurrent license usage, and obtain license statistics. The FlexLM license manager interfaces licensed applications via predefined ports. You can verify that a port number is set correctly by:

1. Using Flexera’s LMTOOL utility: Select the “Server Status” tab, and click the “Perform Status inquiry” button. the port number would appear on the line that begins with “License server status:” e.g.:

License server status: 27000@My_server

2. You can also find the server name and port number (If defined as static) directly in the license file, in the SERVER line e.g.:

SERVER <ServerName> <hostId> <PortNumber>

USE SERVER

The path and name of the license file is set in the LMTOOLS, under the “Config Services” tab.

Please follow and like us:

IBM Rational – FlexNet Token based licensing

IBM Rational license management using FLEXnet

The IBM Rational License Server uses FLEXnet (FlexLM) 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 license 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

Please follow and like us:

Application Note 1007: Configuring FLEXlm FLEXnet Option File Using OpenLM Easy Admin

Application Note 1007: Configuring FLEXlm FLEXnet Option File Using OpenLM Easy Admin

General:

FLEXLM ( FlexNet publisher ) option files grant license administrators close control over various operating parameters within the constraints of the license model. Licensed features can be dedicated, denied or reserved to users or groups of users, according to the option file’s setting.

Employing FlexLM option files, the license administrator can:

1. For concurrent (floating) licenses:

  • Allow the use of features

  • Deny the use of features

  • Reserve licenses

 

Concurrent licenses can be held either in license files or in fulfillment records within trusted storage.

2. For all license types:

  • Restrict the number of licenses available

  • Control the amount of information logged about license usage

  • Enable a report log file

  • Control the automatic rereading of licenses

 

FLEXlm Option files are implemented as text files, located on the license server. Although  this method fits the licensing requirements well, the process of creating and maintaining option files is error-prone and difficult to maintain.

The OpenLM solution incorporates synchronization of License administration tools with the organization’s LDAP (Active Directory), keeping the FLEXlm option file up-to-date as users leave or join the organization, or move between groups.

 

Creating an Option File

1. The Option file should be placed under the same directory as the vendor daemon file, in order to enable FlexLM to read it automatically. Locating the Option file in a different folder is possible, but this requires FlexLM to be configured to search for it in that location.

2. The recommended name for the Option file is vendor.opt, where vendor is the vendor daemon name. Note that the name should not contain white spaces ( e.g.: Arcgis vendor: arcgis.opt,  Adsflex vendor: adsflex.opt ) “Vendor name.opt” is illegal.

FLEXlm option file editing

When configuring the option file using OpenLM, the configuration data is presented to the OpenLM Server, and forward by it to the OpenLM Broker, located on the license server machine. The OpenLM Broker updates the option file.

OPENLM SERVER CONFIGURATION

Check the “Enable OpenLM option file management” box

 

It is necessary to install the OpenLM Broker on the license server machine in order to edit the option file using the OpenLM EasyAdmin web application.

OPENLM BROKER INSTALLATION

  • Information about the OpenLM Broker and its installation process is available in Application Note #1004.

  • The latest OpenLM Broker version  is available for download for version 1.8. If you need a previous version please contact Support@openlm.com.

OPENLM BROKER CONFIGURATION

The next step after creating an option file on the license server machine, is to configure the OpenLM Broker to work with it.

 

1. Open the “OpenLM Broker configuration tool” installed on the license server machine

(“Start” → “Programs” → “OpenLM” → “Broker” → “Broker Configuration Tool”). The Broker Configuration Tool window appears.

 

2. On the Broker Configuration Tool window, Click the (+) button near the License server name in the configuration window.

 

 

3. Click the (+) button near “Vendors” (1).

 

4. Click the “Edit” button.

 

5. Check the “Watch Option File” box (2)

 

6. Type in the path to the Option file previously created. (3)

 

7. Restart the OpenLM Broker.

Editing Option Files

OPTION FILE TARGETS: USERS, USER GROUPS, HOSTS, HOST GROUPS AND IPS

Option Files apply license permission limitations to certain target categories; namely Users, User groups, Hosts, Host groups and IPs. Setting up and introducing these targets is beyond the scope of this article, but a short explanation on each of these target categories is attached at the end:

In order to edit option files, select a specific option file, and then apply changes to it.

OPTION FILE SELECTION

1. Open the OpenLM EasyAdmin web application.

2. Click Start → Opt. File Admin. The “Option File” dialog window appears.

3. Select the specific Option file to be edited (e.g.: Autocad Option File) and click “Set”.

 

GLOBAL SETTINGS OF THE VENDOR DAEMON

On the EasyAdmin web application click Start →  Option Files → Policy.

The “Policy of Option File” window appears.

This window comprises of several text boxes:

GROUPCASEINSENSITIVE (OFF / ON)

ON: User names and host names specified with the Options File GROUP and HOST_GROUP keywords respectively, are treated as case insensitive.

OFF (Default): User names and host names are treated as case sensitive.

NOLOG { IN | OUT | DENIED | QUEUED }

Suppresses logging of the selected type of event in the debug log file.  License administrators may use this option to reduce the size of the debug log file, however it can reduce the usefulness of the debug log when debugging license server problems.

  • IN / OUT: Turns off logging of license check-ins and check-outs respectively.

  • DENIED: Turns off logging of license check-out denials.

  • QUEUED: Turns off logging of queued license requests.

REPORTLOG

Specifies the report log file for this vendor daemon. It is recommended to precede the report_log_path with a ‘+’ character to append logging entries; otherwise the file is overwritten each time the daemon is started.

TIMEOUTALL

Specify the idle timeout for all features, after which an inactive license is reclaimed. The software publisher sets a minimum value. If a smaller value is set – it is ignored, and the publisher’s minimum value is used.

DEBUGLOG

Writes debug log information for this vendor daemon to the specified file.

Note that this affects output from only the vendor daemon associated with this options file. The debug log output of lmadmin or lmgrd and any other vendor daemons in the same license file is not captured in this file.

Click the ‘Save’ button in order to save the edited configuration.

FEATURE SETTINGS

On the EasyAdmin web application window click ‘Start’ →  ‘Option Files’ → ‘Features’.

The “Features of Option File” window opens, according to the option file selected before. This window enables the configuration of each feature separately, applying changes either globally or to specific Users, User groups, Hosts, Host groups and IPs.

1. Select a feature. The ‘Permission’ column is filled

2. Select a user (shown in the screenshot below):

2a. Select the Users tab

2b. Click the ‘Add’ icon. The “Users search” window appears.

2c. Mark users from the “Users search” window, and click the ‘Select’ icon. The selected users are added

3. Select a specific permission, and set its value as explained here:

BORROW_LOWWATER:

Sets the minimal number of BORROW licenses that cannot be borrowed, i.e: the minimal number of licenses that need to remain as Network licenses. For example, if FEATURE has a count of 10, borrowing is enabled in the application, and BORROW_LOWWATER = 7 then only 3 licenses may be borrowed. This option is used for licenses held in license files.

LINGER:

A lingering license stays checked out for a specified period of time beyond its checkin or FlexEnabled application exit, whichever comes first. This configuration enables users to extend the linger time for a feature beyond its check in.

Note:

  • The software publisher sets a minimum linger value. If a value smaller than the minimum is configured, the minimum value is used.

  • The linger time may be configured by the software publisher in the FlexEnabled application. When this is the case, the longer linger time is applied.

MAX_BORROW_HOURS:

Change the maximum borrow period for a specific feature. The new configured period value must be less than that in the license file. This option is used for licenses held in license files.

MAX_OVERDRAFT:

The overdraft policy allows a software publisher to specify a number of additional licenses which users are allowed to use, in addition to the licenses they have purchased. This allows your users to not be denied service when in a “temporary overdraft” state. The MAX_OVERDRAFT parameter Limits the overdraft usage to less than the amount specified in the license file.

TIMEOUT:

Specify the idle timeout for a feature, after which an inactive license is reclaimed. The software publisher sets a minimum value. If a smaller value is set – it is ignored, and the publisher’s minimum value is used.

SETTING PERMISSIONS ON SPECIFIC FEATURES

Some Option permissions may be applied according to the following categories: Users, Groups, Hosts, Host Groups and IPs as shown below.

These configurations include

  • Reserved: Reserve licenses for a User / User group / Host / Host group of users/hosts.

  • Included: Allow a user to use a feature.

  • Excluded: Deny a user access to a feature.

  • Borrow Included: Allow a user to borrow licenses.

  • Borrow Excluded: Deny a user the ability to borrow licenses.

  • Max: Limit usage for a particular feature/group—prioritizes usage among users.

ALLOW OR DENY THE ENTIRE VENDOR’S FEATURE SET

It is possible to Allow or Deny a category of users (user\group\host\host group\IP) the entire set of features that a specific vendor daemon serves. In order to do that:

  1. On the EasyAdmin web application window click ‘Start’ →  ‘Option Files’ → “All Features”.  The “All Features …” window appears.

1. Add a Category of users (User \ Group \ Host \ Host Groups \ IP)

2. Check the “Include All” or “Exclude All” radio button;

  • Include All: Allow a user to use all features served by this vendor daemon.

  • Exclude All: Deny a user access to all features served by this vendor daemon.

3.Click ‘Save’.

SAVING THE OPTION FILE ON THE LICENSE SERVER

Saving the changes made to the Option file back to the License Server is done as follows:

1. On the EasyAdmin web application window click “Start” → “Opt. File Admin.”

2. Select the specific Option File, and click “Set”.

3. Select “Save back to server”.

The Option file update mechanism

  • The OpenLM Server writes this request to a table on OpenLM db and waits.

  • Every 10-15 seconds the OpenLM Server checks that table for any new messages for sending to the OpenLM Broker.

  • If such messages are available, the OpenLM Server sends the option file back to the broker.

  • The OpenLM Broker receives the new option file. It creates a copy of the old option file and replaces it with the new one.

  • After that, the broker issues a re-read command to the license manager. If the re-read was successful, the process is complete.

This procedure refers to user permissions. The same permissions are applicable to Groups( a groups of users ), Hosts, Host Groups (defines a group of hosts) and IPs.

 

Appendix A: Users and Groups

There are two methods of introducing new users and user groups to the OpenLM system. One is through the EasyAdmin web application, and the other is by synchronizing with a company’s Active directory. Both these methods are elaborated below.

SYNCHRONIZING USERS AND USER GROUPS WITH AN ACTIVE DIRECTORY (AD)

The best way to add users and groups is to synchronize them with the AD. OpenLM supports such synchronization:

1. Open “OpenLM Server Configuration” (Start →  Programs → OpenLM →  OpenLM server configuration )

2. Select the “Active Directory” tab.

3. Enter The following information in order to connect to the AD and synchronize users:

3a. Domain name: The Active Directory domain name is the full Domain Name System (DNS) name of the domain.

3b. Active directory user name and password, in the respective fields.

4. From the LDAP Server drop-down menu select “ActiveDirectory”.

5. Check the “Synchronize users” checkbox.

Another method for adding users and groups makes use of the EasyAdmin “Users & Permissions” menu:

INTRODUCING A NEW USER

On The EasyAdmin window, Click Start → Users&permissions → Users. The User details window appears.

Insert the required data, Check the ‘Enabled’ box,  and click the ‘Save’ button.

INTRODUCING A NEW USER GROUP

  • In The EasyAdmin web application, Click “Start” → “Users & Permissions” → “Groups”. The Groups window appears.

  • Click the green “Add Group” icon in order to create a new group. Enter the new group name (e.g.: my_new_group), and click “OK”.

 

  • On the “Groups” window, select the newly created group (e.g.: my_new_group), and click the “Members” icon to add new members to the group. The “Users in my_new_group” window appears.

  • Click the green ‘Add’ button. The “Users search” window appears. Mark and select users from the “Users search” window to add to my_new_group.

Appendix B: Adding an IP

What is an IP?

An Internet Protocol (IP) address is a numerical label assigned to each device (e.g., computer, printer) participating in a computer network that uses the Internet Protocol for communication. An IP address serves two principal functions: Host or Network interface identification and location addressing.

Controlling the license usage of a specific computer is made possible by the “IPs” tab on the “Features of Option File” window. It is also possible to control the license usage of an IP range of computers. For example, typing in the IP:  123.123.123.* causes the feature configurations done in the “Features of Option File” window to be implemented on all user IPs in the range of 123.123.123.0 through 123.123.123.255.


Adding a specific IP:

1. On the EasyAdmin web application window click ‘Start’ →  ‘Option Files’ → ‘IPs’

2. Click The green “Add” button. “Add Ip” window will pop.

3. In the text box enter the Ip address you want to add.

Add a range of IPs

1. On the EasyAdmin web application window click ‘Start’ →  ‘Option Files’ → ‘IPs’

2. Click The green “Add” button. “Add Ip” window will pop.

3. In the text box enter the Ip range you want to add (as explained above).

 

Appendix C: Adding a Host Group

About Host Groups

Custom groups of virtual machine hosts may also be created, for grouping of hosts and their virtual machines in meaningful ways. For example, you may create a host group for every branch office in your organization. You can also use host groups to set aside resources on hosts in the host group for the use of the host operating system.

1. On the EasyAdmin web application window click “Start” →  “Option Files” → “Host Groups”. The “Host Groups” window appears.

2. Click the green ‘+’ sign, and add a group (e.g.: my_host_group1).

3. Select the newly added group, and click the “Members” icon. The “Memebers of my_host_group1” window opens (see image).

4. Select the computers that are required for grouping, and click the green “Select” button. The new Host group is ready for use.

Revision

Revision 1.3 (Revised)

Authors: Mira, Orik, Chen

May 20, 2013.

Please follow and like us: