Application note 1017: Changing ports numbers in OpenLM

Introduction

The OpenLM Utilizer is a licensing management software. It provides productivity tools for system administrators, managers and end users. OpenLM’s basic software package includes the core OpenLM Server module and its user interface; the OpenLM EasyAdmin module. In addition to these core components, the OpenLM software package includes modules and capabilities which provide additional functions. In order to interface these components and obtain full functionality of the OpenLM software, it is essential to open certain port numbers.

OpenLM license Server

The OpenLM Server is the core element of the OpenLM Utilizer system. It integrates the functionality of all other OpenLM peripheral system components, such as the OpenLM EasyAdmin, OpenLM Agent, OpenLM Alerts, and OpenLM Broker. It is responsible for collecting information from various system components and storing it in an embedded relational DB. External databases like Oracle or Microsoft SQL Server are also supported.

License manager: Default port 7016

The OpenLM Server interfaces the License manager over a dedicated port. this port’s default number is 7016.

Configuring the License manager Port:

In the “OpenLM Server” configuration window, select the “Port Settings” tab.
In the “License managers reporting port” text-box, type in the OpenLM server port number (e.g.: 7016).

The OpenLM Broker is an optional software component that runs on the license server machine. The Broker performs tasks as dictated by OpenLM Server. The Broker is required in order to provide advanced licensing information and capabilities; such as controlling license servers remotely, managing FLEXLM option files etc.

The OpenLM module interfaces the OpenLM Server via a dedicated port. This pot number is 7016 by default, and should be configured the same as the license manager port (see above). For additional information on the OpenLM Broker component, please refer to this application note.

Configuring the OpenLM Broker Port:

There are two methods for configuring the OpenLM Broker port: via the OpenLM Broker configuration tool, and via the broker.xml configuration file.

OpenLM Broker configuration

  1. Open the “OpenLM Broker configuration”.

  2. Choose an OpenLM Server from the OpenLM servers list and click “Edit” .
    Edit the “Port” textbox. Repeat this for all OpenLM Servers.

broker.xml configuration file

  1. Open the broker.xml file,  located on: “C:\Program Files\OpenLM\OpenLM Broker”

  2. Search for the line <Port>7016</port>.

  3. Edit the port number.

OpenLM Agent:  Default port 7012

The OpenLM Agent facilitates available license querying, among other functions. It connects to the OpenLM Server through another dedicated port: the OpenLM Agent default port number is: 7012. The OpenLM Agent port number should be configured the same on the OpenLM Agent configuration tool, and on the OpenLM Server configuration tool.

OpenLM Agent configuration tool

  1. Right-click on the Openlm Agent blue icon on the Windows taskbar,

  2. Open the ”OpenLM Agent configuration” tool. The “Agent Configuration” window pops.

  3. Type in the port number in the “Port” textbox (e.g.:7012).

  1. In the “OpenLM Server” configuration tool, select the “Port Settings” tab.
    Type in the Agent port in the “Agent reporting port” text-box (e.g.: 7012).

HTTP Server Port:  Default port 7014

This port enables EasyAdmin web application to send requests to the OpenLM Server.

This port number should be configured the same on the OpenLM Server configuration tool, and on the “config.js” file.

OpenLM Server configuration:

In the “OpenLM Server” configuration tool, select the “Port Settings” tab. Type in the HTTP Server port in the “User Interface http server port”  textbox (e.g.: 7014).

config.js file:

  1. Open the “config.js” file, typically located on:”C\Program Files\OpenLM\OpenLM Server\WeebApps\EasyAdmin2”
  2. Search for the number 7014.
  3. Edit the port number(Should be 7014).

OpenLM Alerts System:  Default port 7017

The OpenLM Alerts module produces alerts for system managers based on predefined conditions. These alerts may be directed to email messages, SMS text messages, the EasyAdmin web application or to a dedicated log file. Please refer to this application note for elaborated information on the OpenLM Alerts module.

Configuring the OpenLM Alerts port:

  1. In the “OpenLM Server” configuration tool, select the “Port Settings” tab.
    Type in the Alerts port in the “Alerts server checking port” textbox (e.g.: 7017).
  1. In the OpenLM Alerts configuration form, of the OpenLM Alerts Editor, type in the port number in the “Alerts Port” textbox.

OpenLM HTTP port Default port 7019

OpenLM installs the LightTPD web server with the installation of OpenLM Server. LightTPD is configured as a Windows Service and starts up with the machine. The use of web servers such as Apache or IIS or others is also supported.

Configuring the OpenLM LightTPD port:

  1. Open the “lighttpd-inc.conf” file,  located on: “C:\Program Files\OpenLM\OpenLM Server\WebServer”.
  1. Search for the line “bind to port (default: 80) server.port = <port number>”.
  2. Edit the port number (e.g: 7019).

Serve OpenLM EasyAdmin using Microsoft IIS 6 & 7

The OpenLM Software package is delivered with LightTPD; a built-in web server. The LightTPD web service starts upon installation or machine start-up. Users can either use LightTPD or choose a standard web server such as Microsoft IIS.

For additional information on how to serve OpenLM EasyAdmin using IIS6, please refer to this application note. For information on how to serve OpenLM EasyAdmin using IIS7, please refer to this application note.For information on how to serve OpenLM EasyAdmin using Apache webserver, please refer to this application note.

OpenLM Maintenance Release Version 1.7.1.5

OpenLM Maintenance Release Version 1.7.1.5:

Version 1.7.1.5 (Broker version 1.7.1.6)

Version 1.7.1.5 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.

This maintenance release includes a more advanced version (1.7.1.6) of the OpenLM Broker.

Upgrading

In order to upgrade to version 1.7.1.5:

  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. Some of our customers experienced “error 1001″ as a result of not closing this window.
  4. Install the new version on top of the existing one.

New in version 1.7.1.5:

OpenLM Server:

  1. Fixed in License activity: Counting produced an exception when the request contained a Vendor name.
  2. Fixed in OpenLM Server Configuration Form: Clicking the grid title when the servers’ grid was empty produced an exception.
  3. Fixed: Option file policy settings was not saved.
  4. Fixed: OpenLM Service doesn’t load on machine startup.
  5. Easyadmin – when there is only one option file it becomes the default.
  6. Error for SQL Server users when sorting by last user in workstations window (Bug #328).
  7. Easyadmin Active Agent window (EasyAdmin → Administration → Active Agent): fixed visualization problem in spinner field (Bug #329).
  8. Configuration form – crashed when deleting empty server (Bug #332).
  9. AD Synchronization feature – Users are enabled to select which attribute would be used as a synchronization field between LDAP and the licensing system (Active Directory, post or pre win 2000 username Bug #189)
  10. AD Synchronization bug fix: Synchronizing group names longer than 50 characters.
  11. Feature in EasyAdmin “License Usage” report: Show more details: server, vendor, feature. (Bug #323).
  12. Fixed: Multiple License draw for the same user and workstation is not reported correctly (Bug #335).

OpenLM Broker (1.7.1.6):

  1. Fixed Linux permissions problem in setup.
  2. Improved the interface of the license server detection process (Bug #278).
  3. Removed quote marks (“”) from the command line (Bug #27).
  4. A The broker command template is ready for the user at the beginning of the configuration (Bug #293).
  5. Use the term “OpenLM Server” instead of “Server” in the Broker configuration window (Bug #296).
  6. Feature: Facilitate global update of the Broker commands’ path to all the commands of a specific port.
  7. Fixed installation problem: Support installation on top of java 64 bit version. A 32bit version installation workaround is no longer required.
  8. Add pane to installation, explaining about the configuration tool, to prevent confusion.
  9. Improve the automatic detection of licese servers.

Note:
After upgrading the OpenLM Server version, you may experience problems with the “Licenses” window in the Easyadmin web application. In this case, open the “User Settings” window, click the “Clear Settings” button and “OK” for the problem to be resolved.

Application note 1013: OpenLM Alerts

Scope

OpenLM Alerts is designed to assure the stability and availability of your licensing system. The system allows the system manager to define conditions and what will happen when these conditions are met. The system is able to handle complex conditions on multiple license servers and features and is able to send alert by email or SMS.

This document presents the OpenLM Alerts software module. It elaborates the module’s installation process, and conveys basic information regarding the OpenLM Alert’s functionality and configuration options.

General

The implementation of OpenLM Alert system allows organizations to handle problems related to the licensing system even before the users experience the problems. The “OpenLM Alerts” tool provides the system administrator ability to closely monitor the licensing system through a set of predefined message rules.

These messages may be assigned different severity levels, i.e.: Alerts, Warnings and Notifications. The Alerts tool messages may be configured to be sent to the system administrator as an email, an SMS text message, as a notification in the EasyAdmin web application or redirected to an event log file.

OpenLM Alerts System Architecture

The Alerts system is implemented by a Windows service working in conjunction with the OpenLM Server.


The Alert Systems interface, OpenLM Alerts Editor allows the user to define a set of alerts that are written to an XML file. OpenLM Alerts service reads the alert and constantly checks the conditions against OpenLM Server.

When a condition is met, OpenLM Alerts checks the defined destinations and timelines, and sends the messages to the users using the SMTP and SMS gateway.

“OpenLM Alerts” is an optional component that requires additional licensing. It may be downloaded and installed for evaluation purposes for a period of up to 30 days. After that, a customer would have to contact sales@openlm.com for pricing.

Downloading and Installation

The Alerts tool can be installed on any Windows platform. It should be installed on the same machine as the OpenLM Server. The OpenLM Alerts installer requires .NET Framework 3.5.

The OpenLM System components are available for download on the OpenLM site. After filling in your name and email, you would be directed to the download section. Select the OpenLM Version 1.7 section:

Roll down to the bottom of the page, and click the “Download” button under the OpenLM Alerts label. Follow the standard Installation wizard commands to go through the installation process.

Note: The OpenLM Alerts component monitors your license servers (FLEXlm, IBM LUM, and Sentinel RMS) and it should not be installed on the same server as your license servers. Otherwise, the OpenLM alerting system will also stop running along with FLEXlm in case of any hardware or software failure.

At the end of the installation process, the Alerts Configuration Form will be displayed.

The Alerts Configuration Form

Open the Alerts Configuration from. Its image is shown below:

Fill in the required information to configure the Alerts module:

  • OpenLM server: Type in the OpenLM Server name or IP. In the example above, the Alerts module was installed on the same machine as the OpenLM server, hence OpenLM server was defined as localhost.

  • Alerts Port and UI Port: These are the OpenLM server ports that interface with the Alerts module. These should be the same ports as defined in the “OpenLM server configuration”  form under the “Port Settings” label, namely the “Alerts server checking port” and the “User interface http server port” respectively.

Click the “Check connectivity to OpenLM Server” buttons to ensure that the Alerts module interfaces the OpenLM server on both these ports.

  • Configure mail / sms services: The OpenLM Alerts may be sent email or SMS text message. In order to configure the alert to be send as an email:

  1. Click the Configure mail/sms services button. The Configuration widow opens on the Email tab.

      

  1. Type in the required information, and click the “Test account” button. A test message would be sent to the configured account.

  2. Click the “OK” button to finalize this configuration.

In order to set the Alerts module to send SMS text messages:

  1. select the SMS tab on the Configuration window.

  1. Contact OpenLM Sales (sales@openlm.com) in order to receive your SMS username and password.

  2. Type in the required data, and press the “Test account” button. An SMS text message would be sent to the configured account.

  3. Click the “OK” button to finalize this configuration.

The Alerts editor window

The OpenLM Alerts System features a visual and easy-to-use Alerts Editor. In order to access the editor: Click the Windows “Start” button, and navigate to “OpenLM” → “Alerts System Service” → “OpenLM Alerts Editor”. The Alerts Editor window opens.

To add a new alert, follow these steps:

  1. Click the “Add” button. The “Conditions Editor” window opens.


  1. Enter the “Query Name” text.
  2. Click the “Severity” drop down menu, and select the required severity level to be Alert, Warning or Notice.
  3. Select the condition type: OpenLM Alerts system uses conditions to help organizations locate failures or inefficient usage of licenses. The condition types are:
    1. Feature threshold – Checks the usage level of a feature.
    2. Check duplicate licenses – Checks whether a user uses the same features on multiple workstations.
    3. OpenLM server is down.
    4. Feature Expiration – Alert that a feature license expiration date is coming up.
    5. Monitored license manager that OpenLM fails to contact
    6. Users without default group
    7. Users without default project
  1. Configure one or more Alert destinations:
    1. Click the “Type” drop down menu, to select the Alert destination type. The optional types are:
      1. Email
      2. SMS text message
      3. EasyAdmin web application
      4. Event log
    2. Type in the Alert’s destination in the “Destination” text box.
    3. To customize the number of times an alert could be sent, click the “Limit Send Times” button. The “Select allowed sending times” window opens. Customize the alert’s sending times on this window.
  2. Click the “Add” button. A corresponding Alert line is added in the “Query Definition” frame (see below).


  1. Configure each alert line separately and click “OK”. A new alert is added to the Alerts List on the “Alerts Editor” window.
  2. In order to edit an alert, select a Query Name (e.g.: my_new_alert) on the “Alerts Editor” window, and click the “Edit” button. The “Conditions Editor” opens again, and the necessary changes may be applied.

Alerts Timing

There is a method for setting up the Alerts’ timing (e.g.: If the system administrator is reluctant to receive SMS messages at 3:00 AM). In order to do so, please configure the “Select allowed sending times” window.

This window is accessible through the “Conditions Editor” window’s “Limit send times” button. Configuration of timing may be done in two methods: via the “User Interface” or the “Custom Pattern”.

User interface configuration

The example below shows an email alert pattern configured to each working day of the week, between 08:00 and 20:00. Note the Regular expression for this pattern is “* 8-20 * * 1-5”

 

Custom Pattern configuration

The user may also set the alert according to the Regular expression pattern, in order to obtain more complex alert timing patterns. For example: setting the alert for each working day of the week on every whole hour would create the pattern 0 */1 * * 1-5. In order to combine the two patterns mentioned above, i.e: have an alert for each working day of the week on every whole hour AND between 08:00 and 20:00, we need to superimpose the patterns, i.e:
“* 8-20 * * 1-5” + “0 */1 * * 1-5” = “0 8-20/1 * * 1-5”

Implementation Tips

  • Every Alert query consumes resources from the OpenLM system, hence a good alerts’ system should contain the minimum number of checks that would assure a stable and effective licensing system. The frequency of queries can be configured on the “Select Frequency” dialog box (Click the “Frequency” button in the “Alerts Editor” window to access this dialog box).

  • The “Limit Send Time” button in the “Conditions Editor” window allows you to direct the alert to the desired destination. For example, an alert may be sent to an email during work hours and to SMS after work hours.

Revision Table

Revision Date Author Notes
0.1 – Preliminary Nov 10, 2011 Orik Preliminary
1.0 Mar 23, 2012 Orik Added Alerts’ timing

Trouble Shoot Form: Broker Item 003 (LUM licenses don’t show up in EasyAdmin)

 

Title LUM licenses don’t show up in EasyAdmin
Category Broker
Date Nov 11, 2011
Handled by
Relevant Links http://bug.openlm.com/view.php?id=225
Applies to license managers LUM
Applies to license model Floating licenses, Network licenses, Concurrent licenses, Node Locked
Symptoms LUM licenses don’t show up in EasyAdmin.
Observed during dubug 1. The Broker was not sending any information to the OpenLM Server
2. The Broker “test connectivity” button clicked: Broker saw the OpenLM Server OK.
Trouble shoot process 1. Upgraded Broker version.
2. Changed the I4BLT.EXE path from the OpenLM folder to one supplied by the application vendor.
Solution Found (Found/Pending/Known Issue)

Symptom

LUM licenses don’t show up in EasyAdmin.

Solution

1. Upgrade the OpenLM Broker on the license server machine. Refer to the Application Note for reference.
2. As part of the OpenLM package, the latest version of the I4BLT.EXE file is supplied. This file may not be inter-operable (version too new) with the licensed application version. If this is the case, please follow these steps:

Changing a single port’s configuration

  1. Open the OpenLM Broker configuration tool.
  2. Select the relevant License server.
  3. Check the “Update to the following path” radio button
  4. Click the “Edit” button. The text box becomes active.
  5. In the “Path” text box, type in the path of the I4BLT.EXE file in the LUM folder, originally supplied by the application vendor.

This configuration change may also be achieved by individually typing the I4BLT.EXE file path in each Broker command text box.

Changing all ports’ configurations

  1. Open the OpenLM Broker configuration tool.
  2. Click the “Advanced Settings” wrench icon. The Advanced settings window opens.
  1. Click the “Edit” button. The text boxes become active.
  2. In the “I4BLT Path” text box, type in the path of the I4BLT.EXE file in the LUM folder, originally supplied by the application vendor.
  1. Select a specific port’s “Commands” list item. The “Commands” window opens.
  1. Check the “Update according to advanced settings” radio button, and click the “Update” button. The I4BLT path of the specific port is changed.
  2. Repeat steps 5 & 6 for all ports.

Trouble Shoot Form: OpenLM Server Item 002 (Connection to FlexLM license server failed)

Title Unable to connect to FlexLM license server
Category OpenLM Configuration Form
Date Nov 03, 2011
Handled by
Relevant Links
Applies to license managers FLEXlm, FLEXnet publisher
Applies to license model Floating licenses, Network licenses, Concurrent licenses, Node Locked
Symptoms No activity reported on EasyAdmin for a specific FlexLM license server
Observed during investigation A License server’s  ‘LED’ on the EasyAdmin “License Servers” window is red.
Clicking the “Check” button for one of the license servers on the OpenLM Configuration Form resulted in an error.
Trouble shoot process Check License server connectivity configuration.
Solution Found (Found/Pending/Known Issue)

Symptom

The customer complained that there was no activity on the EasyAdmin web application regarding a specific license server.

Solution

1. Make sure the License server configuration is correct:

  • Open the LMtools utility on the “Server status” tab.
  • Click the “Perform status Enquiry”. Status text appears.
  • On the “License server status” line – extract the Server name and status (e.g.: olm_lm_acad and 27000)

2. Install the OpenLM Broker on each license server machine. Refer to the Application Note for reference.

Application Note 1000: OpenLM system structure overview

Application Note 1000: OpenLM system structure overview

Table of contents

OpenLM
OpenLM’s customer testimonials
The OpenLM solution
Components of the OpenLM system
Block Diagram
OpenLM Software Modules
OpenLM Server
OpenLM EasyAdmin
OpenLM Broker
OpenLM Alert
OpenLM Utilizer Agent
OpenLM Active Agent
OpenLM External Data Base (DB) Support
OpenLM Groups & Projects
OpenLM Role Based Security
OpenLM Option File Management
OpenLM Logs Uploader

OpenLM

OpenLM is a licensing management software company with an international install base. Companies that use OpenLM’s software range from global corporations and nation-wide companies to small offices. Our company’s commitment to innovation guarantees that our clients constantly receive updates with the most advanced technology.

OpenLM’s customer testimonials

Please review a partial list of OpenLM’s satisfied customers,

http://www.openlm.com/index.php/about-us-topmenu-3/customers

and their testimonials:

http://www.openlm.com/index.php/support/testimonials-topmenu-29

The OpenLM solution

OpenLM’s Software provides a comprehensive management solution for license management software such as FLEXlm, FLEXnet, Sentinel RMS, Sentinel HASP, RLM, IBM LUM and LM-X. The software provides productivity tools for system administrators, managers and end users. OpenLM’s software supports the major trends in the field of license management, e.g.: license consolidation, Usage charge back (usage billing), usage trend analysis etc. The software provides a comprehensive solution that combines the best of breed software, superior support, implementation and consulting services, in order to ensure your success.

OpenLM is proudly ISO9001:2008 certified by the ANAB (the U.S. accreditation body for management systems), and an ESRI business partner.

OpenLM’s solution is tailored according to specific customer needs, optimizing the licensing system and increasing software productivity.

Components of the OpenLM system

OpenLM’s basic software package includes the core OpenLM Server module and its user interface; the OpenLM EasyAdmin module.

In addition to these core components, the OpenLM Broker and the OpenLM Utilizer Agent modules are incorporated in the basic software package, but their installation is not mandatory; The Open LM system can function without the use of these two components.

The OpenLM software package also includes several optional modules / capabilities, which are commonly referred to as “OpenLM extensions”. These extensions provide additional functions such as:

  • OpenLM Active Agent (Active release of licenses)
  • External DB support
  • Groups and projects management
  • Role based security
  • Option file management
  • OpenLM Alerts
  • OpenLM Logs Uploader

The OpenLM Extensions are separately licensed:

  • Some of them are included within the OpenLM Server but require additional licensing
  • Others require the installation of an additional software module.

Block Diagram

Figure1 (below) shows a generalized block diagram of OpenLM’s license management solution:

OpenLM Software Modules

OpenLM Server

The OpenLM Server is the core element of the OpenLM system. It integrates the functionality of all other peripheral system components, such as the OpenLM EasyAdmin, OpenLM Agent, OpenLM Alerts, and OpenLM Broker. It is responsible for collecting information from various system components and storing it in an embedded relational DB. External databases like Oracle or Microsoft SQL Server are also supported.

The OpenLM Server is implemented as a Windows service and could be installed on any network machine. It enables monitoring and managing of multiple license servers, over LAN or WAN networks. Common OpenLM Server configurations may vary from one or more license managers nationwide to multiple license servers located worldwide, over different time zones.

OpenLM EasyAdmin

OpenLM EasyAdmin is the administrative interface of the OpenLM system. EasyAdmin’s control panel features a desktop interface that enables users to configure the OpenLM Server; OpenLM’s core component. Some of EasyAdmin’s main properties are listed below:

  • EasyAdmin Easily extracts statistical license usage information from all attached license servers.
  • EasyAdmin’s role-based security enables system administrators to grant varying degrees of access to different groups of users.
  • EasyAdmin can run on any standard web browser (e.g.: Mozilla FireFox, Microsoft Internet Explorer, Google Chrome) and be accessed from any machine in the organization.
  • EasyAdmin features a touch interface that is compatible with mobile operating systems like Android, IOS, Blackberry and Windows Mobile. The OpenLM EasyAdmin Mobile application is particularly useful for after-hours crisis management situations.
  • EasyAdmin’s streamlined user interface design promotes simple and effective use of its unique capabilities.

OpenLM Broker

The OpenLM Broker is an optional server component that runs on the license server machine. The Broker performs tasks as dictated by OpenLM Server, and is required in order to provide advanced licensing information and sophisticated abilities.

The Broker’s main task is to extract License Manager Servers’ debug log information and to push it to the OpenLM server. This action facilitates reading of license servers’ log files. Other capabilities provided by the broker are:

  • Controlling license servers remotely (e.g. start / stop the servers)
  • Managing FLEXLM option files.
  • Generating denial reports and
  • Support of complex configurations, e.g. license servers that work over WAN networks.

The Broker is an independent java based software module that can run on any license server operating system: UNIX, Linux or Windows.

OpenLM Alert

The OpenLM Alert is a dedicated alerting service for the OpenLM system. This module alerts system administrators when predefined conditions are met. Alert service users can set complex alert conditions on multiple license servers. For example, if the combined usage of a certain feature on servers A and B is above a certain threshold, an email message will be sent, alerting those concerned to the situation. The Alert service also supports adjustable timing for alert checking and message sending. Alert destinations are also configurable; Alerts could be sent to the EasyAdmin interface, over emails, as SMS text messages, or directed to a system event log.

OpenLM Utilizer Agent

The OpenLM Utilitzer Agent is the end user tool of the OpenLM system. It provides OpenLM users with the following capabilities:

  • Query license availability.
  • Check which users are holding required licenses.
  • View a user’s full set of details as they appear on the LDAP, and communicate with users regarding license availability.
  • Receive license availability notifications as soon as requested licenses become available.
  • Report the session’s active project (mainly for billing purposes).

OpenLM Active Agent

The Active Agent incorporates all the characteristics of the Utilizer Agent. On top of that, it supports an extension that enables system administrators to shut down open application either manually, or by defining a timeout policy. In this manner, system administrators can save, close, or suspend idle applications, in order to make more efficient use of licenses. The Active Agent features a user-friendly interface that enables users to quickly reopen closed applications, or resume suspended ones.

OpenLM External Data Base (DB) Support

This extension facilitates saving license usage information on an external Data Base such as an Oracle or MS SQL Server. By default, OpenLM uses an embedded DB. External DB support is recommended for management of large licensing systems.

OpenLM Groups & Projects

This extension enables collecting license usage information from Groups of users or projects. This capability is predominantly used by companies that charge back usage time to cost centers. The Groups & Projects extension synchronizes users’ data with its LDAP Data Base (Active Directory), keeping the data collection process fully automatic.

OpenLM Role Based Security

The OpenLM Server supports a role-based security feature that enables the implementation of customized access to OpenLM tools by setting access roles. This feature facilitates the implementation of OpenLM tools for diverse groups; e.g.: help desk, system administrators, managers and developers. The role based security system secures nearly all parts of the system entities, such as listed servers, fields and action buttons.

OpenLM Option File Management

The OpenLM Option File Management extension employs LDAP (Active Directory), to enable system administrators to manage Option Files easily from the EasyAdmin web based interface. This gives the system administrators easy control over the access of user groups and individuals to licenses.

OpenLM Logs Uploader

The OpenLM Logs Uploader extension enables loading of historical FLEXlm debug log files. This extension is essential for investigating historical license usage. Logs Uploader is also necessary for checking license usage in files received from customer sites, typically in order to charge per use.

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.

Enabling cookies

Enabling Cookies

Scope

This document describes the actions needed to enable cookies in each browser.
Enabling cookies allows OpenLM EasyAdmin to save personal data, for example: time zone and user settings.

Table of contents

Enabling Cookies
Scope
Table of contents
Cookies
What is a cookie?
Why is it important to enable cookies ?
Enabling cookies in your browser
Internet Explorer 9.0
Internet Explorer 8.0
Internet Explorer 7.0
Chrome
Netscape Navigator 7.0
Netscape Communicator 4.0
Mozilla FireFox 4 and above
Mozilla Firefox 3.5
Safari
Opera
Revision Table

Cookies

What is a cookie?

A very small text file placed on your hard drive by a Web Page server. It is essentially your identification card, and cannot be executed as code or deliver viruses. It is uniquely yours and can only be read by the server that gave it to you.

Why is it important to enable cookies ?

In order to store user settings, OpenLM EasyAdmin saves personal data on a cookie. This enables the system to remember its configuration and settings, and various data such as the time zone and session date (when permission is granted) and the EasyAdmin windows’ size and location.

Enabling cookies in your browser

Internet Explorer 9.0

  1. Click the Tools button Internet options.
  2. Click the Privacy tab, and then, under Settings, move the slider to the bottom to allow all cookies, and then click OK.

Internet Explorer 8.0

      1. Click on the “Tools” menu in Internet Explorer choose “Internet Options”.
      2. Click the privacy tab.
  1. Move slider to bottom to allow all cookies, and then click OK.

Internet Explorer 7.0

Click on the Tools popup-menu in Internet Explorer.

Click on  Internet Options item in the menu – a new window will pop.

Click on the privacy tab

under Settings, move the slider to the bottom to allow all cookies, and then click OK.

Chrome

  1. Click the wrench icon
  2. Select Options (Preferences on Mac and Linux; Settings on a Chromebook).
  3. Click the Under the Hood tab.
  4. Click Content settings in the “Privacy” section.
  5. Click the Cookies tab in the Content Settings dialog that appears
  6. Make sure “Allow local data to be set” is selected.

Netscape Navigator 7.0

On your Task Bar, click:
1. Edit → Preferences → Privacy & Security
2. Click on Cookies.
3. Set your “Cookies” preferences.

Netscape Communicator 4.0

On your Task Bar, click:
1. Edit → Preferences
2.Click on Advanced
3. Set your options in the box labeled “Cookies”.

Mozilla FireFox 4 and above

In order to check the version of your FireFox browser, click Help → About Mozilla FireFox

  1. Click the Firefox button on the top left corner of the browser window.
  2. Select the Options… tab. The Options window appears.
  3. On the menu bar, Select the Privacy tab
  1. In the Firefox will: drop down menu, select Use custom settings for history.
  2. Check mark Accept cookies from sites to enable Cookies.
  3. Choose how long cookies are allowed to be stored:choose the “They expire” option in the “Keep until” drop down . (Keep until they expire: Each cookie will be removed when it reaches its expiration date, which is set by the site that sent the cookie.)
  4. Click OK to close the Options window.

Mozilla Firefox 3.5

  1. Click on the Tools menu in Firefox.
  1. Click Options…
  2. Change to the Privacy Settings
  3. Set Firefox will: to Use custom settings for history
  1. Check mark Accept cookies from sites to enable Cookies.
  2. Choose how long cookies are allowed to be stored choose the “they expire” option.
    (Keep until: they expire: Each cookie will be removed when it reaches its expiration date, which is set by the site that sent the cookie.)
  3. Click OK to close the Options window.

Safari

  1. From the toolbar menu, select the Safari tab. A drop-down menu appears. Select the Preferences option.

  1. In the Security dialog box, in the Accept Cookies category, check the Always radio button.

  1. Click the red Close button on the top right corner of the Security dialog box.

Opera

  1. On the menu bar, select the Tools tab. A drop down menu appears.
  2. Select the  Preferences… option. The Preferences window appears.
  3. Select the Cookies section on the Advanced tab.
  4. Select Accept cookies.
  5. Ensure that Delete new cookies when exiting Opera is not checked.
  6. Click OK.

Revision Table

Revision Author Date Notes
0.1 – Preliminary Mira Sep 27, 2011 Preliminary

Generating custom reports using Excel spreadsheet

OpenLM system provides many built-in reports such as:
Group and Project usage
Usage level reports (report and chart)
License denial reports (supported for FLEXnet FLEXlm license manager)
Active users
And more…

Managers always require more reports and OpenLM provides an easy way to generate custom reports by using OpenLM EasyAdmin ability to export information in a CSV format and to process the information using a spreadsheet software.

The process starts by creating the query that will define which information will be exported out of OpenLM system. EasyAdmin provides a unique and easy to use tool that allows the user to define the exact information needed. The user can filter the query by: server name, vendor name, features, users, groups, projects, time and even working days.

After defining the query the information will be displayed in EasyAdmin, using the export button located below the grid the information can be exported to a CSV file that can be easily imported into the spreadsheet software.

The user can also save the filter created for future use by using the “Funnel” icon.

The reports generated this way are available for any of the supported license managers like: FLEXnet, FLEXlm, IBM LUM, Sentinel RMS, SafeNet HASP, RLM and more.

Generating a Unique Daily Users Report

The unique daily user report allow companies to know who is consuming the network licenses every day. In order to create this example we have used Autocad network licenses (from Autodesk).

The usage information is exported in CSV format from the EasyAdmin->License Activity TAB.

The action is demonstrated in OpenLM Version 1.7 and Microsoft Excel Version 2010.

1. Using  ‘Easy Admin’ interface: Click Start -> Reports -> License Activity.
The filter on the left can be used in order to create the query for the report. After creating the query and clicking the “Apply” button, click the “Export” button (The small icon with green arrow at the bottom of the grid).  Save the generated CSV file on the disk.

2. Open the CSV file using Microsoft Excel.

3. Make a copy of the “Start Time” column in order to remove the hour component from the field.

4. Select the new column, click on “Data-> Text To Columns”  on the menu of Microsoft Excel, a window will pop:

1. Select “Delimited”’ and click “Next”.

2. Choose the ‘Space’ box and click next

3. Select ‘Text’ and click Finish

5. Three new columns has been created as a result of the process we did (columns which detail the date, the time & the daily time zone – AM/PM ).

We only need the column with the date.

Delete the other two columns and change the name of the column (The dates column)  to ‘Date Usage’

 

6. Select the column ‘Date Usage’ and right click the mouse in order to select the ‘Format Cell’ option from the menu. A window will open –  select ‘Date’ from the ‘Category’ list and click ‘OK’

 

7. Select all columns (CTRL+A) , click on ‘Insert’ ( in  Microsoft Excel menu ) and  on PivotTable.

Select the ‘New Worksheet’ on the ‘Create PivotTable’ window that will pop up and click ‘OK’.

A new worksheet will be created.

 

8. On the right side of the screen you will see all your columns( under ‘PivotTable Field List’ )

Drag first the ‘Date Usage’ field  with the mouse to the ’Row Labels’ box and then drag the ‘User Name’ field  to the ‘Row Labels’ box.

 

The example report shows the unique users that consumed licenses for each day. In the example report some days lists one user, for example 03/04/2011. On the 14/03/2011 we had two unique users.

Generating a Group Usage Report for Projects

The following report lists the total number of license usage hours each group investing for each project. Such a report can be useful for billing purposes or in order to support managerial decisions.

OpenLM provides two built in reports: Project usage report and Group usage report. this custom reports integrates the two reports together.

1. Perform steps 1-7 (listed above in the previous report).

2. On the right side of the screen you will see all your columns’ names ( under ‘PivotTable Field List’ ). Drag the ‘Project’ field to the ’Row Labels’ box and then drag the  ‘Group’ field  to the same box as shown in the following image.

3. Drag the ‘Count Of Usage Time’ field into the ‘Values’ box. The result will be generated automatically:

We can see that the GISteam group used 31 hours of Autocad network licensed software for the “City Plan” project and the “GISSpecial” only used 1 hour for the “Environment” project.

 

Generating a Feature (licensed software) Usage Report for Projects

The following report lists the products (licensed software, features in FLEXlm) used on each project. Such a report can be useful for billing purposes or in order to support managerial decisions.

1.Perform steps 1-7 (listed above).

2. On the right side of the screen you will see all your columns’ names ( under the ‘PivotTable Field List’ ),drag  the ‘project’ field  to the ’Row Labels’ box and then drag the ‘Product’ field to the same box as shown in the following image.

In this example we have used information from an ESRI ArcGIS license manager. In the report we can see the list of features used for the “City Plan” project. We can se the use of base licenses such as ArcView and ArcInfo or extensions such as 3DAnalyst network license.

Generating a Feature Usage Chart

The following chart shows the total number of users that used specific license (feature).

1. Perform steps 1-6 (listed above).

2. Select all columns (CTRL+A) , click on ‘Insert’ (Microsoft Excel menu) and choose the ‘PivotChart’ option from the ‘PivotTable’ menu as shown in the following image.

3. Select ‘New Worksheet’ on the ‘Create PivotTable with PivotChart ’ window that will pop and click ‘OK’. A new work sheet will be created.

4.  On the right side of the screen you will see all your columns (under the ‘PivotTable Field List’). Drag the ‘Product’ field to the ‘Legend Fields’ box and then drag the ‘User Name’ field to the ‘Values’ box.
This  automatically will generate a chart of the number of users that used each license, As shown in the following image.

Summary

This article explains how to generate custom reports and charts by using OpenLM export functionality and a spreadsheet software. OpenLM system allows the user to generate a query and to export the information to a CSV file that can be further processed by the spreadsheet software.
The article demonstrated the creation of sevelral reports such as: Unique Daily Users Report, Group Usage Report for Projects, Feature (licensed software) Usage Report for Projects and Feature Usage Chart.

 

Problem/Error with AutoCAD network license management: “A valid license could not be obtained by the network license manager”

Details:

You can face above problem frequently on AutoCAD 2007 based products when you are working in an organization where:

  • Concurrent licensing scheme is implemented through server/client networking mode.
  • Network bandwidth is low.
  • Network latency is high or connected through VPN.

All of the products based on AutoCAD 2007 contain licensing enhancements which tend to increase network latency and bandwidth utilization of the network. Therefore, you can face this problem while trying to claim the license of the program from the License Manager Server. Earlier versions of AutoCAD products i.e. older than 2007 release were not observing this problem. In this problem, first you are presented with a FLEXlm license finder dialogue box during license obtaining process followed by a message stating:

“A valid license could not be obtained by the network license manager.

Error [1.5. -15]”

In some other products you can receive a bit different message as given below:

“A valid license could not be obtained by the network license manager.

Error [1.5. -18]”

Reasons for Error:

A network throughput or data rate of the link is the main reason for this error especially in case of heavy applications like AutoCAD 2007. Reasons can be summarized as below:

  • Low Bandwidth of the connection i.e. Dial-up connection or low speed ISDN/DSL connection.
  • High Network Latency i.e. VPN
  • Response waiting time of the application/program

One or more of the above reasons can be the root cause of this problem. This problem has recommended solutions which given below.

Solutions:

  • Recommended solution for this problem is either increase in the bandwidth of the connection or decrease in the network latency or enhancement in both parameters.
  • By modification of the response waiting time counter/value which is used as the last resort for the solution of this problem. This is a stepwise procedure to modify the response waiting time counter. Here is the stepwise procedure for the same:
  1. Right click My Computer and choose properties.
  2. On system property dialogue box choose advanced tab.
  3. Click on the environment Variables
  4. On environment variable dialogue box choose system variables field and hit the new button
  5. A new system variable dialogue box with two fields appears; put “FLEXLM_TIMEOUT” in variable name and put 1000000 in variable value field.
  6. Click OK on all three dialogue boxes to close them
  7. Launch the AutoCAD application

 

 

 

 

 

 

 

 

If the problem persists, increase the variable value in multiples of 1000000 micro seconds and reach to the value which gives you satisfactory communication results.