OpenLM Maintenance Release Version: OpenLM Server 2.0.0.37

OpenLM Server version 2.0.0.37

OpenLM Server version 2.0.0.37 is a maintenance release to OpenLM version 2.0. It contains some bug fixes to problems found in previous versions and enhancements. We recommend all users of previous OpenLM Server 2.0 versions to upgrade to this latest version.

Note that this version does not update the database, only software. If your current version is 2.0.0.28 or higher, no database upgrade is needed. This is mainly important for users that has an external database.

What’s new in OpenLM Server 2.0.0.37 (October Nov. 24th, 2014)

Fixed Issues:

  • 2525: License Usage Report: No scrollbar in IE11
  • 2528: OpenLM Admin showing negative numbers for RMS licenses
  • 2529: Options file management ruins usage report.
  • 2490: OpenLM does not release package license
  • 2527: Groups: Manually adding users to groups deletes them from OpenLM_Everyone
  • 2524: License Usage Report: export of table causes error
  • 2519: EasyAdmin – Roles – Agent_query_role is not working as expected
  • 2523: License Usage – Table – Unable to download results
  • 2516:Take Cancel button from Process Features
  • 2489 EasyAdmin – Cleanup Manager – History does delete only part of  history

 

  1. Before upgrading please make sure your system is compliant with the OpenLM System requirements.
  2. If the OpenLM server (of any version) has been already installed on the machine for a period longer than the Evaluation period, A license file will be required . Please make sure you have one before proceeding with the upgrade process.

In order to obtain a valid OpenLM license file, please contact OpenLM support, and provide your MAC address and Hostname (case sensitive).

Upgrading the OpenLM Server (Internal Firebird Database)

In order to upgrade to version 2.0.0.37:

  1. Download the OpenLM Server installation file from the ‘Downloads’ section in the OpenLM site.
  2. Stop the OpenLM Server service
  3. Backup your DB file (Typically located in: C:\Program Files (x86)\OpenLM\OpenLM Server\db)
  4. Make sure ALL windows are closed; especially the services window.
  5. For OpenLM versions 1.8, Install the new version on top of the existing one.
  6. If prompted to do so, contact OpenLM to obtain an up-to-date license file. Please provide your MAC address and Hostname (case sensitive) for that. Copy this file to the “C:\Program Files (x86)\OpenLM\OpenLM Server\License”  folder, and restart the OpenLM Server service.

Upgrading the OpenLM Server (External MS-SQL Database)

If your current version is 2.0.0.27 or lower in order to upgrade to version 2.0.0.37, please contact OpenLM support at support@openlm.com

 

 

Please follow and like us:

OpenLM Maintenance Release Version: OpenLM Server 2.0.0.26

OpenLM Server version 2.0.0.26 is an official maintenance release to OpenLM version 2.0. It contains some bug fixes to problems found in previous versions and enhancements. We recommend that all users of previous OpenLM Server 2.0 versions would upgrade to this latest version.

Note that this version does not include changes in database structure, i.e. upgrading of version 2.0.0.18 or higher does not require running database upgrade scripts for external databases.

What’s new in OpenLM Server 2.0.0.26 (September 16, 2014)
Fixed Issues:

  • 2257: [OpenLM Server] Modification  to LUM commands execution (Add /k)
  • 2256: [OpenLM Server] Do not split feature usage for multiple sessions
  • 2221: [OpenLM Server] Logs uploader information does not reach the OpenLM Server

Prerequisites
1. Before upgrading please make sure your system is compliant with the OpenLM System requirements.
2. If the OpenLM server (of any version) has been already installed on the machine for a period longer than the Evaluation period, A license file will be required . Please make sure you have one before proceeding with the upgrade process.
In order to obtain a valid OpenLM license file, please contact OpenLM support, and provide your MAC address and Hostname (case sensitive).

Upgrading the OpenLM Server (Enbedded Firebird Database)
In order to upgrade to version 2.0.0.26:

1. Download the OpenLM Server installation file from the ‘Downloads’ section in the OpenLM site.
2. Stop the OpenLM Server service
3. Backup your DB file (Typically located in: C:\Program Files (x86)\OpenLM\OpenLM Server\db)
4. Make sure ALL windows are closed; especially the services window.
5. Install the new version on top of the existing one.
6. If prompted to do so, contact OpenLM to obtain an up-to-date license file. Please provide your MAC address and Hostname (case sensitive) for that. Copy this file to the
C:\Program Files (x86)\OpenLM\OpenLM Server\License   folder, and restart the OpenLM Server service.

Upgrading the OpenLM Server (External MS-SQL Database)

In order to upgrade to version 2.0.0.26, please contact OpenLM support at support@openlm.com

 

Please follow and like us:

FLEXlm Timeout Settings

What is FLEXlm?

FLEXlm is a license manager that manages software used by multiple end users on different computers. Notably, it allows companies to take advantage of floating licenses. A system employing floating licenses has a license pool on a host server from which end users check out licenses. When a user finishes using a software license, it is checked back into the pool, now available for another user to check out.

Further information on FLEXlm

What is FLEXlm license timeout?

FLEXlm license timeout is a feature that releases inactive licenses back to the license pool. Licensed software is determined to be inactive when a machine is completely idle, meaning no mouse clicks, keystrokes, modal dialog boxes are occurring. Its timeout settings determines how long such a period continues before licenses are freed up.

How to set FLEXlm timeout

License timeout settings can be configured for some or all the features, and are configured in the FLEXlm option file.

Further information on option files

Individual license key timeout is set by entering the variable “timeout” followed by the timeout period (in seconds).

Example: Setting AutoCAD to be timed out in 108000 seconds (3 hours)

 timeout AutoCAD 108000

License timeout for all license keys in the system is set by the variable “timeoutall,” followed by the timeout period.

Example: Setting all licenses to be timed out after 30 minutes of inactivity

timeoutall 1800

Limitations on license timeout settings

It is important to note that software vendors often impose limitations on the timeout period for their products; specifically, the minimum amount of time of inactivity after which licenses can be freed up. For example, whereas Autodesk licenses can be released after 15 minutes of inactivity, MathWorks licenses can only be released after 4 hours.

Autodesk 900 sec (15 minutes)

MathWorks 14,400 seconds (4 hours)

IBM 7200 seconds (2 hours)

Application

Customizing FLEXlm timeout settings is simple way to improve the efficiency of your company’s licenses, ensuring that end users aren’t slowed down by waiting for inactive, locked-up licenses.

 

Please follow and like us:

Application Note 1030: OpenLM license usage monitoring according to projects – v1.8.

General

OpenLM is able to record information about the usage of various licenses and allocate them to different company projects. This ability facilitates license allocation according to organizational projects, and can also serve as a mean to effectively charge-back license usage expenses according to these projects.

This ability complements OpenLM’s license monitoring capabilities; integrating license usage optimization with Active directory synchronization, Project assignment, and monitoring a variety of  license managers such as FlexLM (Flexnet), Sentinel HASP, Sentinel RMS, RLM, DSLS, LM-X, IBM LUM, and MathLM.

Scope

The Project license usage recording capability is available for OpenLM from version 1.6 onwards. In the 1.8 version, some modifications have been made:

  • The configuration of Project monitoring was shifted from the OpenLM Server configuration tool to the EasyAdmin web application.

  • Administrative capabilities have been added, such as Enabling / Disabling a project, assigning it a priority and expected duration, and marking the project’s completeness percentage.

  • Projects can now be assigned to user groups (not just to individual users), and

  • Projects can be introduced by end-users via the OpenLM Agent module.

This Application Note describes the feature as implemented in the 1.8 version.

Project usage reporting

The Project usage reporting is available on the EasyAdmin web interface. Click OpenLM Start → Resports → Project usage in order to see the report. Set the filtering options on the left-hand side of the screen, and click the ‘Apply’ button in order to run the usage query. It is also possible to view the report in a chart format, or extract the information to a CSV file (green arrow icon at the bottom) and manipulate it on a spreadsheet software.

However, before having any information to report – it is necessary to set up the projects. Please follow the section below in order to do so.

Projects Settings

The “Projects Settings” screen defines the policy of the Project usage monitoring capability. In order to open it, click the OpenLM ‘Start’ button → ‘Administration’ → ‘Projects’ icon.

Notes:

1. Projects’ information logging requires the installation of the OpenLM Agent (Either Active Agent or Utilizer Agent) on the end-users’ workstations.

2. When the OpenLM server is configured to employ user permissions, access to this window requires administrative privileges.

The ‘Projects’ window appears:

Note:

The project configuration window was moved in OpenLM version 1.8 to EasyAdmin (under the Administration menu. Following is an account of its different configuration objects:

Log Projects Information

Check the Log projects information checkbox to start recording license usage information according to projects’ allocation.

Minimal Usage Duration for Project

This setting defines the shortest duration for logging purposes. Shorter periods would be merged together to form significant usage periods. For example, if the minimal duration is set to 5 minutes, and a user has opened the application for only 3 minutes, this usage period will not be accumulated to the current session, but rather merged with the following session.

Agent’s Behavior Settings

These settings define what the end-users will see on their workstations if they work on more than one project for their organization. If the workers are only allocated to one project in EasyAdmin then OpenLM will log their license usage without the need to take any action when the software is started. If the users work on more than one project then a dialog box will appear on their screen prompting them to select the current project.

Hide projects option from menu

Deny users the ability to determine the name of the project on which they’re working.

Projects window fades away after

OpenLM enables users to ignore the project dialog box by having it fade away after a predefined number of seconds. The Projects window fades away after setting defines the number of seconds after which it becomes invisible.

Allow creation of projects in Agent

This option has been introduced in the OpenLM 1.8 version.

The OpenLM project management module facilitates project creation via the OpenLM Agent. Check this box to enable this option, thus adding the “Create New Project” menu item in the OpenLM Agent interface (see image below).

When an end-user selects this option, the “Create new Project” window opens. The user then could create new projects and associate themselves to them.

Modification of these projects will be possible in EasyAdmin only. The origin of creation of the project will be apparent in the EasyAdmin Projects list window.

Show unassigned projects

By default, users can only see projects they are assigned to in the Agent → Set Active Project menu option. Checking this box will produce a list that contains all enabled projects in the system and the user will be able to select any project from this list. This option has been introduced in the OpenLM 1.8 version.

Support Environment Variable

The LM_PROJECT env. variable support is a backward-compatibility option, that supports this variable for registering projects. The variable is defined separately for each workstation, so there is no option of overriding its value between users.

The environment variable option is disabled by default. It is recommended to use the OpenLM supplied solution, unless backward support of the environment variable option is required.

The “Add unknown project” option presents an administrative filter for project names that are unknown to the OpenLM server:

  • Checked: The unknown project will be set and added to the list of projects.

  • Unchecked (default): The unknown project will not be set.

Selecting the active project

When logging of project information is enabled (see above), work hours need to be assigned to a specific project. When there is only one project – that project will automatically be assigned all the working hours. When there are more than one project – it is up to the end users to report on what project they are currently working.

1. One option for the end user to set the Active project is to right-click the Agent icon, and select the “Set Active Project” option.

2. Another option for setting the Active project is by a pop-up window. The appearance of this pop-up is configurable by options in the ‘Projects’ window, which was mentioned above.

Display at license retrieval

The default option is to prompt the worker to select the project when retrieving a license. This is a very useful way to ensure accurate logging of the project information, therefore the recommended setting is to leave the checkbox turned on.

Display periodically every

Users may start to work on one project, and then switch to a different one, without changing the Active Project setting. If this checkbox is ticked, a dialog box will pop up in a predefined time interval, according to the number of minutes set by the user.

Project creation in EasyAdmin

In the previous section, we have seen the mathod for creating project via the Agent. Projects can also be created via the EasyAdmin “Add project” window.  

In the “Project details” tab, the Administrator can set up the following characteristics:

  • Project name

  • Start and End time for the project

  • Number of working hours allocated to this project

  • The project’s priority, and

  • The project’s completeness percentage.

Users and user groups may be assigned to the project upon its creation, via the ‘Users’ and ‘Groups’ tabs. After configuring these items, click the ‘Save’ button.

Editing existing projects

The new project would be apparent in the Projects list window. In order to access this window, Click the EasyAdmin Start button → Users and Permissions → Project List.

This window presents options to create new projects, as well as to delete or edit existing ones. It is split to two panes:

  • The left pane serves as a filter for projects to be shown on the list on the right pane.

    • The Priority drop-down list presents Low / Medium / High priority levels.

    • “Created in” marks whether the project was created by the Agent or via the EasyAdmin window: Admin / Agent

  • The right pane consists of a list of the existing projects, and an action bar at the top.  Click the top bar icons to add a new project, delete a selected project, Edit a selected project’s properties, Enable or Disable a selected project.

Attaching users and user groups to the project

After creating a project, it is time to bind users or user groups to the different projects, according to organizational preferences. In order to do so, select the target project, and select the Users or Groups tab in the ‘Add project’ window. Then select the User or Group that would be attached to the project, and click the ‘Add’ button.

Appendix A: Projects information logging in v1.7

This application note relates to the OpenLM 1.8 version. As stated in the scope of this document, most Projects information logging capabilities are already existent in the 1.7 version. The main change of interface is due to the shift of the configuration from the OpenLM Server configuration tool to the EasyAdmin web application. Below is a screenshot of the 1.7 Projects setting tab on the OpenLM Server configuration tool for comparison.

Please follow and like us:

Application Note 1029: LDAP (Active Directory) Synchronization

General

The OpenLM Server is capable of synchronizing users and groups with an organization’s LDAP to combine license management, license statistics, and report extraction with other company information. LDAP synchronization provides automatic maintenance of Users’ and Groups’ data.

LDAP Synchronization holds many advantages, for different levels of decision makers in the organization. On an administrative and managerial standpoint, it can be applied for enforcing license usage permissions, implementing usage chargeback (usage billing), analysis of usage trends etc. Administrators may gain in automating FlexLM Option file management, thus streamlining FlexLM reporting. From the end-user point of view, this information may be applied to easily locate other users holding a required license.

The Groups synchronization functionality is part of the Users and Groups extension, and requires additional licensing.

Additional information

Please refer to the video tutorial section on the OpenLM site, for a demonstration of Active Directory synchronization.

Users and groups presentation

The Users and User groups which exist in the OpenLM Database are apparent in the EasyAdmin web application, in the Users and Groups windows respectively. Initially, upon installation of the OpenLM server, the Users and Groups windows are only populated by the logged user (e.g. ‘Orik’ – that’s me), the default ‘generaluser’ user, and the “OpenLM Users” default group.

The Active directory tab – Interfacing the LDAP

This tab is the OpenLM Server’s interface to LDAP (Active directory) synchronization. The 1st thing to do is to connect to the LDAP Database. Type in the LDAP server details:

  • Domain name: the IP Address of the server which is your organization’s domain controller (e.g: 102.101.100.106)

  • Username (e.g: administrator)

  • Password, and

  • LDAP server type: (e.g. “Active Directory”)

Click the ‘Check’ button, and receive an authentication status notification, as depicted below:

 

Organizations may have multiple domain controllers (for example, if different departments or subsidiary companies have their own servers for user authentication). In order to add a second server, select the row where the asterisk is shown above, and type in the data for the second server. In order to apply another synchronization rule to the same LDAP server, click the “Duplicate” button under the list of domain controllers.

Synchronizing Users

It is important to note that synchronizing to the LDAP is a tricky business. You may end up having taken in more users than you intended, and deleting users from the database is difficult. It is highly recommended to experiment on a separate database, NOT on the production database.

In order to synchronize user information:

  • Check the “Synchronize users” check-box. Other fields on the “Active directory” tab are activated.

  • Click the ‘Select’ button. The active directory browser opens.

  • Select a synchronization start node.In this example, We’ve selected an Organizational Unit (OU): OU_Test. Click ‘OK’ and the node path appears in the “Synchronization Start Node” text box. The LDAP would be synchronized from this node down.

 

  • Set the “Sync time interval” value. The value in this example states that the user details would be updated every 12 hours.
  • It is highly recommended to Check the “Sync only active users of licenses” in order to avoid adding users that do not actively use the application. New active users would be added to the list of users as they check out a license, and their LDAP details would be synchronized when the “Sync time interval” elapses.
  • Set the “Sync username attribute”.

    • “sAMAccountName” is good for Pre Windows server 2000 Active directory versions.

    • “userPrincipalName” is good for Post Windows server 2000 Active directory versions.

    • “cn”  should be used for any LDAP configuration other than “Active Directory”, i.e. “Novelle Directory” or “Apache DS” .

      The value of the selected field (sAMAccountName or userPrincipalName or cn) within the Active Directory would be applied as the user name recognized by OpenLM.

Synchronization of Groups

Check the “Synchronize groups” checkbox to enable a variety of options for associating users with groups in the OpenLM database, according to the data structure on the LDAP.

AD Groups:

This option goes through the list of users that populate the nodes beneath the selected node. The “AD Groups” selection should be used carefully, because it may introduce a large amount of undesired groups. This is because users who are members of groups within the selected node may also be members of groups from beyond that node, resulting in additional introduction of these external groups.

Attribute:

OpenLM groups may be created according to specific attributes their members may have. In order to do that, select the “Attribute” radio button, and pick up a suitable attribute from the adjacent drop-down list of attributes. Examples for attributes are: “Division”, “Employee ID”, “Initials” or “Cost center”. Type in a Regex expression that would articulate the required attribute.

Fixed:

This option enables the administrator to associate a particular group name to all users of a specific node within the AD tree. The ‘Fixed’ name typed in the textbox is the group name of the users that would consequently be synchronized in this method.

OUs (organizational units):

This option is in use by organizations that have an organizational hierarchy represented in the LDAP; for example departments nested inside divisions. By selecting the OU synchronization method:

  • Users would be introduced into groups in the OpenLM database. These groups would be named after the LDAP OUs under which the users have been created.

  • If the “Add full hierarchy” checkbox is ticked, the entire OU hierarchy tree descending from the start node would be introduced as groups in the OpenLM database. OUs in which no users have been defined in the LDAP, would be presented in OpenLM as empty groups.

  • If the “Add full hierarchy” checkbox is not ticked, OpenLM would flatly create groups named after the LDAP OUs, and populate these groups by the users which have been defined under these OUs. No empty groups would be created.

Case study

In order to demonstrate the different group synchronization methods, I have created the following OU structure, and enabled all users. Note that Users U_A1 & U_AB2 are members of more than one group:

Case 1: Synchronize users only

Procedure: OU_AB was selected as the start node.

Outcome: All Users were synchronized. No Groups or OUs synchronized.

Case 2: Synchronize AD Groups (1)

Procedure: OU_AB was selected as the start node.

Outcome: All groups and users beneath OU_AB were synchronized. The Hierarchical tree was not preserved.

Case 3: Synchronize AD Groups (2)

Procedure: OU_B was selected as the start node.

Outcome:

  • Users B1 & AB2 have been synchronized.
  • Group B1 was synchronized.
  • Group A1 was synchronized, with only user AB2.

Case 4: Synchronize AD Groups (3)

Procedure: OU_A was selected as the start node.

Outcome: Mirror image of the previous case:

  • Users A1, A2, A3 & AB2 were synchronized.
  • Groups  A1, A2, A3 & B1 were synchronized. Group B1 only contains user AB2.

Case 5: Fixed

Procedure: Start node = OU_A. The “Fixed” name was named “The_A_Team”.

Outcome: All of OU_A’s users were gathered in “The_A_Team” group.

Case 6: Attribute

Reminder: Users A1 & B1 are the only users to have been defined owning “division” attributes with the value “my_division” (See LDAP diagram).

Procedure: OU_AB was selected as the start node. The “Attribute” synchronization method was chosen. The ‘division’ attribute with the value “my_division” was configured in the Active directory configuration form.

Outcome: All Users in OU_AB were synchronized. Users A1 & B1 were gathered in the “my_division” group.

Case 7: OU

Procedure: OU_AB was selected as the start node. “Add Full Hierarchy” was not checked.

Reminder: Users  AB1 & B1 were created under the OU_AB Operational Unit. All other users, i.e. A1, A2, A3, AB2 were created under OU_A.

Outcome: All users under OU_AB were synchronized. OpenLM has flatly created groups named OU_AB, and OU_A. Each of these two groups contain the users which have been created under the respective LDAP’s OUs:

  • Group “OU_AB” contains the users AB1 & B1 (see image below).
  • Group “OU_A” contains all other users, i.e. A1, A2, A3, AB2.

Case 8: OU (2)

Procedure: OU_AB was selected as the start node. “Add Full Hierarchy” was checked.

Outcome: This time the OU hierarchy was preserved, so OU_A and OU_B appear under OU_AB. The users are again grouped according to the position in which they were created:

  • Group “OU_AB” contains the users AB1 & B1.
  • Group “OU_A” contains all other users, i.e. A1, A2, A3, AB2 (see image below).
  • Group “OU_B” is empty.

Please follow and like us:

OpenLM Maintenance Release Version 1.7.2.5

Version 1.7.2.5

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

Upgrading

In order to upgrade to version 1.7.2.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.
  4. Install the new version on top of the existing one.

What’s new in version 1.7.2.5 ?

OpenLM Server:

  1. French version labels in EasyAdmin and OpenLM server corrected.
  2. Fix LM-X reading: Fix LMX multi-session reporting issue (Bug #415).
  3. Fix DSLS reading for SQLServer DB
  4. Add first name, last name to active products export (Bug #404)
  5. Correct OpenLM LightTPD path variable (Bug #396)

OpenLM Agent:

  1. Active Agent 1.7.1.1: Install extensions for every Autocad component on a workstation.
  2. Agent 1.7.1.2: Add updated French resources.
Please follow and like us:

Trouble Shoot Form: EasyAdmin Item 001 (Unable to connect to EasyAdmin)

Title Unable to connect to EasyAdmin
Category EasyAdmin web application
Date Oct 11, 2011
Handled by
Relevant Links
Applies to license managers FLEXlm, FLEXnet, IBM LUM, HASP, RLM, Sentinel RMS
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Symptoms Customer could not connect to EasyAdmin.
Observed during investigation
Trouble shoot process Check web server service running,
Check OpenLM server service running.
Solution Found (Found/Pending/Known Issue)
Other steps for troubleshooting

Symptom

The customer complained that he “Couldn’t connect to the EasyAdmin”. Attempting to open the EasyAdmin web application resulted in the following message box appearing on his screen:

In a similar case, the customer got a different notification:

 Troubleshoot process

This kind of issues is related to services that have stopped and are not currently active. The 1st thing to try is restarting the respective process.

1. Navigate to the windows services: Click Start → Control Panel → System and Security → Administrative Tools → Services. The “Services” window appears.

2. In the first case (“Couldn’t connect to host” message box), it may be an issue of the OpenLM Server service.

2a. Select that OpenLM Server service in the “Services” window.

2b. Right click the OpenLM Server service, and set it to restart – see image below.

2c. Restart the EasyAdmin web application.

3. If the 2nd type message box (“Please Check your Internet connection”) appeared, it may be an issue of the web server service. Restart your web server service (e.g.: LightTPD).

Other steps for troubleshooting:

If restarting the services does not work – here are some other things you may try:

  • Run the EasyAdmin application from the same computer as the OpenLM Server.

  • Make sure that any security components (Firewall) are not blocking communication to the EasyAdmin web application.

  • Temporarily stop the OpenLM Server and OpenLM Broker services. Open the task manager’s processes window. Make sure the computer is not held-up by any other process.

  • Still in the task manager’s processes window, look for the LightTpd process. If there are multiple processes with that name – kill them, and restart the LightTpd service on the services window.

  • Make sure the default HTTP listener port (7019) is kept open. Try a different port (e.g. 7020) on the lighttpd-inc.conf configuration file(C:\Program Files\OpenLM\OpenLM Server\WebServer) . Then restart LightTPD service.

  • Try connecting the proxy to the test page; Select the test page from the ‘Start’ menu (see below). Click the ‘Check’ button. An indication similar to that of the 2nd image below should appear.

  • Try a different web browser.

  • Try erasing the Proxy server logs. These are found in the following positions:

Win 7: C:\ProgramData\OpenLM

XP, Win 2003: C:\Documents and Settings\All Users\Application\OpenLM

Please follow and like us:

Application Note 1015a: The OpenLM EasyAdmin Mobile application

The OpenLM EasyAdmin Mobile application enables system administrators to keep track of the license management systems, while being out of office. This document describes the essentials of the OpenLM EasyAdmin for mobile application; installing the application, and running it on a Mobile set.

Background

The ever increasing obligation of system administrators to support their users’ issues in real time has produced the need to perform license management operations upon request. OpenLM has come up with a solution to this requirement: An “Out of the office”, slick, mobile application that extracts the bulk license management information, and enables system administrators to resolve user issues even when networking is inaccessible to them.

Supported Devices

The EasyAdmin Mobile application is developed according to web development standards, e.g.: HTML5 and CSS3. It is supported by most popular mobile operating systems like iOS, Google Android, and BlackBerry OS.

User experience

The user experience is of a sliding window menu, spanning over 4 separate pages. Navigating among these pages is easy and intuitive, and the information contained on them is adequate for system administrators to perform troubleshooting in the field.

Users can also test the application using a Google Chrome web browser. It is designed to have the same look and feel as the authentic mobile application. In fact, the screenshots contained in this article have been cropped using this browser.

Network considerations

Using the OpenLM Mobile application requires a network connection between the Mobile application and the Internet server that serves the application. It also requires connection to the OpenLM Server UI port. Observe the image below for clarification.

 

This image depicts two scenarios:

  1. Intranet: Mobile devices inside the company connect to the Local Area Network. Access to the web server serving OpenLM is direct. After loading the application to the mobile device, the requests for information are handled by the OpenLM Server.

  2. Internet: Mobile devices access the application from the Internet. The company needs to open ports for loading the application and for communicating with the OpenLM Server.

 

The image demonstrates a system with two servers. In many cases, the OpenLM Server and the web server (http server) run on the same machine.

 

Application Pages

Important note:

The EasyAdmin Touch Application is available for installation on all Mobile operating systems. However, as a PC browser application for debugging, this application currently supports Chrome browser v. 8.0 upwards only. This is at the time of writing this revision (Rev 1.0).

 

The information presented in the EasyAdmin mobile application is presented on four separate pages. These pages appear on the bottom panel, and are named: License Servers, Active Products, Alerts and Settings.

The “License Servers” and “Active products” Pages

List of license servers: The License servers page is the Mobile application’s landing page. It presents the license servers in rapport of which the OpenLM server works (image below). These License servers are named as they were in the configuration tool (Bottom image).

Server specific licensed features: Click on a license server name (or its blue circled arrow), e.g.: lm10. The Licenses list page for that license server appears.

 

This page depicts the current License usage for each licensed feature on the selected License server. Click on a used license, e.g.: Viewer. The Active Products page appears.

This page presents the user and workstation who is currently holding the license for the selected feature. In the case depicted below, the user name is Orik, he is using efrat-laptop Workstation, and the start time of his usage is also presented.

The Active Products page may also be directly accessed by clicking the “Active Products” star icon on the bottom task bar. In this case, the Feature and Server columns are added in order to avoid ambiguity. See the image below for clarification.

 

On either one of the “Active Products” windows, click on the User of interest. The user’s details (Full name, email, phone etc) appears.

The Alerts page

Click the ‘i’ icon on the bottom panel. The Alerts page appears.

This page presents predefined system alerts to the administrator. Please refer to the “Application note 1013: OpenLM Alerts” document for further clarification.

The Settings page

This page contains timezone and time format settings.

Installing the OpenLM Mobile EasyAdmin application

1. Install the application on the HTTP Server

There are two possible HTTP server configurations, requiring a slightly different process:

1a. Using the built-in HTTP server – LightTPD

  • Download and install the latest OpenLM server version from OpenLMs site. The Mobile application would be set in the directory: C:\Program Files\OpenLM\OpenLM Server\WebApps.

  • The default application name is “EasyAdmin_touch”. This name can be changed by altering the “EasyAdmin_touch” folder name.

1b. Using standard HTTP servers

Installing the OpenLM EasyAdmin mobile application on a standard HTTP server, like Apache or IIS, is a simple task for any system administrator. Changing the application name is done by applying a different name in the “Application Name” text box.

2. Open the EasyAdmin mobile application

Open the web browser on your mobile device and navigate your mobile device browser to the application URL:

http://<CompanyDomainName.com> / <MobileApplicationDirectory>/

where CompanyDomainName and MobileApplicationDirectory are the Company’s Internet domain name, and the Directory path of the Mobile application respectively, e.g.: http://localhost:7019/EasyAdmin_touch/

In order to view the EasyAdmin Mobile application on a PC it is best to run it using the Google Chrome browser.

Revision

1.0: Feb 05, 2012 Orik.

 

Please follow and like us:

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

Scope

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

The “Active Products” window

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

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

User Idle

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


Removing licenses

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

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

Closing applications

In order to actively close an application on the workstation,  an administrator should highlight the relevant row, and click the Close Application icon (See image below).

This operation will retrieve the license back to the license pool, save the open project,  and the application itself will be shut down.
There are some constraints that are specific to this feature:

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


Common Constraints

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

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

Revision 1.1: Orik, Apr 15 2012


Please follow and like us:

OpenLM Maintenance Release Version 1.7.1.6

OpenLM Maintenance Release Version 1.7.1.6

Version 1.7.1.6

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

Upgrading

In order to upgrade to version 1.7.1.6:

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

What’s new in version 1.7.1.6?

OpenLM Server:

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

OpenLM Broker (version 1.7.1.7):

  1. Add pane to installation , explaining about the configuration tool, to prevent confusion.
  2. Fix some type in configuration tool.
  3. Fix automatic detection of ports on windows 64bit. read the Wow6432Node registry key.
  4. Improved Option file reading. See item #2 in the OpenLM server section, above.
Please follow and like us: