Monthly Archives: June 2011

Agent Installation Guide

Posted on by

OpenLM Agent Installation Guide

OpenLM Agent is the end-user tool of OpenLM System. The purpose of the agent is to allow OpenLM to interact with the end user in order to provide better license availability.
System administrators can have full control over the functionality that is available to the end user.

OpenLM Agent is a “lightweight” software that appears as a blue icon located on the end users “Windows Notification Area”. The system provides the following services:

  • Allowing the user to query license availability, license users and full users details.
  • Allowing the user to receive license availability notifications.
  • Allowing the user to report active project.
  • Allowing the administrator to release a license or close an application that is not in use.

Installation and configuration

Download the latest version of the Agent from our downloads area. The installation is a normal “Next-Next” installation, we will only explain the unusual parts.

Extension installation

“OpenLM Extensions” allows OpenLM to provide dedicated services to specific software systems. The extensions enable the “Save Project” functionality in case of a need to close the software remotely.

OpenLM extension licensing usage depends on another license from OpenLM.

“OpenLM Agent Installer” will suggest to install an extension if a supported system is installed on the local machine. Version 1.6 supports extensions for ESRI Desktop ArcGIS and Autodesk software. Selecting one of the available options will install the extension onto the software.

(The example above shows that extensions are available for ArcGIS network licenses and Autocad network licenses (from Autodesk).

When the installation finishes the “Agent Configuration Window” pops up:

OpenLM Server Settings:

OpenLM Server – OpenLM Server name. Note that it does not have to be the license manager server name, it may be, if OpenLM is installed on the same machine as the license manager.
Port – OpenLM Server port (by default 7012).

After setting server name and port, click “Check connectivity to OpenLM Server”.
If everything is configured properly, the system will show the following message:

Advanced:

Logger Configuration File – Sets the location of the “Agent Log File”.
Logging Level –  Sets the Agents logging level after the installation.
Box 1-  “Skip Double Instances Alert”.

This option enable or blocks warning alerts when trying to open two agent session simultaneously. This option is ON by default.

Box 2-  “Shut Agent When Products Are Inactive”.

This option is useful when installing OpenLM Agent on a  terminal server (Citrix for example). This option is OFF by default

Box 3- “Use Local Computer’s Proxy Settings”

This setting may solve possible problems when working with a proxy server. This option is OFF by default

 

 

Guide to update Autodesk Network License Manager IPv6 for 64-bit Windows OS

Posted on by

Requirements: There are certain pre-requisites or requirements which must be fulfilled before upgrading the Autodesk Network License Manager to IPv6 version support.

  • You must have Autodesk Network License Manger already installed on your server before applying IPv6 support update.
  • So, make it sure that installed software is working good otherwise install a new one by referring Network Licensing Guide which is available in Help System.
  • The server must be stopped before carrying out software update or any other administratively critical maintenance activity on Network License Manger server; server should be restarted after the successful completion of activity.
  • You must be logged into the system with administrator rights for stopping, updating and restarting the services on the server.

Limitations: Though this update is very excellent tool but it has following limitations which should be considered while deciding or working with Autodesk Network License Manger.

  • It supports the operating system with 64-bit configuration; supported Operating systems are Microsoft® Windows® Server 2008 and 2008 R2 64-bit, Windows Vista® 64-bit and Windows7 64-bit.
  • This supports either a mixed environment of IPv4/IPv6 or IPv6-only.
  • This implementation does not support IPv4 –only environment.

Updating procedure: You must make it sure that all the requirements are fulfilled for upgrade activity. Now follow the step by step task given below for updating the Autodesk Network License Manger for IPv6 support.

  • Download NLM_IPv6Support_Win64.exe file and save on the desk top of the server.
  • One the desktop of the server, right click on LMTOOLS.exe and choose Run as Administrator; the LMTOOLS program will start.
  • On LMTOOLS select ‘start/stop/reread’ tab and choose stop server and wait for 15 seconds, then close the LMTOOLS program. Your server has stopped now.
  • The default location of Autodesk Network License Manager is C:\Program Files\Autodesk Network License Manager; you have to locate lmtools.exe, lmutil.exe, lmgrd.exe, and adskflex.exe files to take the backup of Autodesk Network License Manager Files.
  • After taking the backup of above mentioned files, double click the downloaded file NLM_IPv6Support_Win64.exe placed on the desktop of the server.
  • The NLM_IPv6Support_Win64.exe file will be extracted automatically on ‘C:\install\Autodesk\NLMIPv6Support_Win64’ location; extracted updated files are lmtools.exe, lmtools.exe, lmutil.exe, lmgrd.exe, and adskflex.exe.
  • Copy all above mentioned updated files and paste them into existing Autodesk Network License Manager Folder whose default location is C:\Program Files\Autodesk Network License Manager\.
  • System will prompt for replacing the existing file; click yes to confirm.
  • Right click again on LMTOOLS.exe available at desktop and choose run as Administrator.
  • On LMTOOLS program click Start/Stop/Reread tab and choose start server tab; this will restart your server with updated support to IPv6 on 64-bit windows operating systems.
  • Close the LMTOOLS program and you are done now.

Based on information from Autodesk website Published date: 2011-Mar-22 ID: DL10976858

How to set a test OpenLM Version 1.7 installation

Posted on by

General

This guide describes the process of checking OpenLM Version 1.7 with your existing database in test environment.
The process consists of several steps:

  1. Set testing environment
  2. Install OpenLM Server on test environment
  3. Migrate Your DB on test environment
  4. Run OpenLM 1.7 and start checking

Set testing environment

In order to set testing environment, select a workstation or a server that is not the same machine that has OpenLM production installed.
Testing machine can be any workstation with Windows XP or higher or a server running Window 2003 R2 server or higher.

Before  installing, be sure to have a backup of the production database file – OPENLM_DB.GDB, which is typically located under “C:\Program Files\OpenLM\OpenLM Server\db”. After copying, rename the file extension to FDB so it will be called “OPENLM_DB.FDB”. We are changing the DB file extension in order to improve the performance.

If you use external database (Oracle or SQL Server) with your OpenLM system, create a copy of your production schema/database for testing upgrade process.

Install OpenLM Server on test environment

Download OpenLM Server Version 1.7 here and install it on test machine. During the installation OpenLM installer will open the configuration form, don’t configure it, leave everything as is and click close. We will get the configuration automatically after upgrading the existing DB.

After installation, stop OpenLM Server windows service and replace the default database with the copy you made earlier. The database is typically located in the following folder: “C:\Program Files\OpenLM\OpenLM Server\db”.

Don’t restart OpenLM Server windows service and move on to the next step.

Migrate Your DB on test environment

Run “Start” → “OpenLM” → “Server” → “Upgrade Database from Earlier Versions”
Upgrade process should take several seconds to several minutes depending on the size of your database.

If you are using OpenLM with an external database, download the appropriate database upgrade script from OpenLM Downloads area and upgrade the test schema/database.
Before restarting OpenLM Server windows service, be sure to configure OpenLM Server (using “OpenLM DB Configuration”) to reference the test schema/database.

Run OpenLM 1.7 and start checking

Now start OpenLM Server windows service.

Using OpenLM EasyAdmin and OpenLM Server configuration form the upgraded system should show the exact configuration as your production system.

Supplement: Version 1.7 highlights

License server configuration – OpenLM 1.7 supports the concept of a virtual license server and by that provides better support to FLEXlm triad configuration and allows OpenLM users to set a name to each license server. This functionality is very important for organization that has many ports on the same license server.
Active Directory integration – We have improved the grouping by allowing REGEX filtering to the “By Attribute” grouping capability.
Desktop like interface – There are no tabs anymore. Every OpenLM tool is a Window on a desktop.
EasyAdmin Filtering – A better collapsible filters.
Localization – OpenLM EasyAdmin and OpenLM Agent now supports localization.
Improved Charting – Charting is better, try to interact with it.
New Agent – A modern interface was applied to the Agent. Try the support for additional languages.

Please test common actions that you usually use and send us your feedback.

 

Application Note 1025: OpenLM Database Configuration Form

Posted on by

OpenLM software supports the use of leading database systems as its storage base. The OpenLM Server is configured by default to use the FireBird embedded DB. It could also be configured to use MS SQL Server or Oracle databases which are very popular in organizations.
In this guide we will explain the different options available in the OpenLM Database Configuration
(Start -> Programs -> OpenLM -> Server -> OpenLM Database configuration).


Firebird Embedded Database

This is the default option. OpenLM is using an embedded FireBird database.
The DB file is stored under the server installation folder.


Using the form, the user can set the location of the database by moving the DB file and changing the defined path. The form also enables the user to change the “user/password” according to what is defined in the database itself.

Firebird external DB configuration

OpenLM can be configured to use Firebird Server database (not embedded). The use of Firebird as an external DB allows the company to get a much better performance and the ability to access the information while OpenLM Server is using it.
The use of Firebird Server requires the installation and configuration of Firebird server. On the OpenLM external DB configuration form, we need to uncheck the “Embedded” option and apply.

Oracle external DB configuration

The use of the Oracledatabase usually requires the services of an Oracle DBA to create a dedicated OpenLM schema in Oracle. The Oracle DBA uses the DDL (Database Definition Language) scripts provided by OpenLM.After generating the schema and the creation of the dedicated user for OpenLM with access to this schema, the information can by typed into OpenLM Database Configuration form.

 

DataSource = Schema (Collection of database objects) the instance name
User ID = The user name of OpenLM Server.
Password = The OpenLM user password.

Notes:
1. The OpenLM Server version 1.7x uses MS-ADO drivers to connect to Oracle. This requires the installation of the Oracle Client version 8.1.7 or above on the OpenLM server machine.
2. Both Oracle DB versions 10i & 11g have been tested, and are supported.
3. Only in version 11g,  the statement : “set define off” must be added at the top of the oracle DDL script provided by OpenLM.

SQLServer

The Microsoft SQL Server is very popular in organizations and can be easily configured to work with OpenLM.

The SQL Server DBA needs to use OpenLM DDL (Database Definition Language) scripts in order to create a dedicated OpenLM DB in SQL.

Using the MS SQL Server, OpenLM supports two authentication methods, that could be set according to the requirement of the organization:

  • SQL Server Authentication.
  • Windows Authentication.

Windows Authentication

The user name is defined in the OpenLM Server Service. This user should have the needed permissions on the OpenLM database, i.e. (Read / Write / Delete) privileges need to to be granted to the local user.

DataSource – SQL Server name.
Initial Catalog –  The name of the OpenLM Database (Usually OpenLM is a good option).

SQL Server Authentication

Server – The SQL Server name.
Initial Catalog –  The name of the OpenLM Database (Usually OpenLM is a good option).
User ID – The user with (Read / Write / Delete) privileges on the OpenLM database.
Password – The OpenLM User password as defined in MS SQL Server.