AltairLicensing InstallationGuide91

Altair License Management System Version 9.
Installation Guide version 9.1
Altair Engineering Contact Information

Web site FTP site www.altair.com Address: ftp.altair.com or ftp2.altair.com or http://ftp.altair.com/ftp Login: ftp Password: <your e-mail address>
Location
North America China France Germany India
Telephone
248.614.2425 86.21.5393.0011 33.1.4133.0992 49.7031.6208.22 91.80.66294500 1800.425.0234 (toll free) 39.800.905.595 81.3.5396.1341 81.3.5396.2881 82.31.716.4321 46.46.286.2052 44.1926.468.600 55.11.4223.5733 64.9.413.7981 64.9.413.7981
e-mail
HyperWorks hwsupport@altair.com support@altair.com.cn francesupport@altair.com hwsupport@altair.de support@india.altair.com
Italy Japan Korea Scandinavia United Kingdom Brazil Australia New Zealand
support@altairengineering.it
support@altairjp.co.jp support@altair.co.kr support@altair.se support@uk.altair.com support@altair.com.br anzsupport@altair.com anzsupport@altair.com
The following countries have distributors for Altair Engineering: Mexico, Romania, Russia, South Korea, Singapore, Spain, and Taiwan and Turkey. See www.altairhyperworks.com for complete contact information. 2008 Altair Engineering, Inc. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated to another language without the written permission of Altair Engineering, Inc. To obtain this permission, write to the attention Altair Engineering legal department at: 1820 E. Big Beaver, Troy, Michigan, USA, or call +1-248-614-2400. Altair HyperWorks 9.0 Application Installation Guide
Trademark and Registered Trademark Acknowledgments
Listed below are Altair HyperWorks applications. Copyright Altair Engineering Inc., All Rights Reserved for:
HyperMesh 1990-2008; HyperView 1999-2008; OptiStruct 1996-2008; RADIOSS 1999-2008; HyperCrash 2001-2008; HyperStudy 1999-2008; HyperStudyDSS 2002-2008; HyperGraph 1995-2008; HyperGraph 3D 2005-2008; MotionView 1993-2008; MotionSolve 2002-2008; TextView 1996-2008; MediaView 1999-2008; HyperForm 1998-2008; HyperXtrude 1999-2008; HyperView Player 2001-2008; Process Manager 2003-2008; Data Manager 2005-2008; Assembler 2005-2008; FEModel 2004-2008; Batch Mesher 2003-2008; Assembler 2005-2008; Templex 1990-2008; Manufacturing Solutions 20052008 All other trademarks and registered trademarks are the property of their respective owners. Portions of the FLEXnet documentation in this installation manual are reproduced with permission of Macrovision Corporation.
ii
Altair License Management System 9.1 Installation Guide 9.1

Proprietary Information of Altair Engineering
Table of Contents
Overview..............................................................................................................1
Introduction ............................................................................................................................. 1 About Altair License Management System .......................................................................... 1 Conventions Used in this Guide............................................................................................ 2
Altair License Management System Release Notes Version 9.1 ...................3

Enhancement...................................................................................................................... 3 Resolved Issues ................................................................................................................. 4 Known Limitations .............................................................................................................. 4 New Features ..................................................................................................................... 7 Resolved Issues ................................................................................................................. 9 Known Limitations .............................................................................................................. 9
Chapter 1: Altair License Management System ............................................13

1.1 Introduction..................................................................................................................... 13 1.2 Altair License Manager .................................................................................................. 14 1.3 Usage Monitoring Tool................................................................................................... 16 1.4 Usage Reporting Tool .................................................................................................... 17 1.5 Altair Application Server................................................................................................ 17 1.6 Tracking Features and Report Log File........................................................................ 18 1.7 alus.conf File ............................................................................................................... 20 1.8 System Limitation........................................................................................................... 20
Chapter 2: Preparing to Install Altair License Management System...........22

2.1 Installation Media ............................................................................................................ 23 2.2 Compatibility ................................................................................................................... 24

Proprietary Information of Altair Engineering.
2.3 Selecting License Server Nodes ................................................................................... 24 2.4 System Requirement...................................................................................................... 26
Chapter 3: Installing Altair License Management System on Linux/UNIX ..27

3.1 Install License Manager and Usage Report System on the Same Server ................ 27 3.2 Install License Manager and Usage Report System on Different Machines ............ 31 3.3 Manually Set up License Manager and Usage Report System .................................. 34 3.4 Connect to Altair Licensing Server .............................................................................. 35
Chapter 4: Installing Altair License Management System on Windows .....39

4.1 Install License Manager and Usage Report System on the Same License Server.. 39 4.2 Install License Manager and Usage Report System on Different Machines ............ 50 4.3 Connect Altair Applications to the License Manager ................................................. 51
Chapter 5: Operations and Maintenance .......................................................55

5.1 Setting up Redundant License Servers ....................................................................... 55 5.2 FLEXnet Publisher (Also known as FLEXlm) ............................................................ 58 5.3 Multiple FLEXnet Publisher Processes........................................................................ 64 5.4 Bringing Down a FLEXnet Publisher Process............................................................. 64 5.5 Setting up Server for Automatic Start of the License Manager upon Reboot (Optional) 65 5.6 How to Borrow Licenses................................................................................................ 66 5.7 Environment Variables................................................................................................... 69 5.8 Troubleshooting and Maintenance ............................................................................... 70
Chapter 6: Altair GridWorks Licensing .........................................................75

6.1 GridWorks Unit Licensing ............................................................................................. 75 6.2 GridWorks Units Used by Application ......................................................................... 76 6.3 GridWorks Leveling and Licensing Pools ................................................................... 78 6.4 Global Licensing............................................................................................................. 78
ii

Appendix A: Glossary .....................................................................................82 Appendix B: Installation Structure .................................................................85 Appendix C: License File Format ...................................................................87
Fields You Can Modify.......................................................................................................... 88 Create a USE_SERVER license file........................................................................................ 90
Appendix D: FLEXlm Error Messages.............................................................93 Appendix E: Example of alus.conf file .......................................................97

Example alus.conf file on Windows ................................................................................ 97 Example alus.conf file on Windows .................................................................................... 98
Appendix F: FLEXlm Administration Utilities.............................................101 Appendix G: Option File Keywords..............................................................111 Appendix H: Managing Licenses from Multiple Vendors ...........................118 Appendix I: Uninstallation Process..............................................................120 Appendix J: Instructions for Sending Reports Manually ............................121
Altair License Management System 9.1 Installation Guide 9.1 iii

iv

Overview
Introduction
This guide covers the concept of Altair GridWorks Units system, the installation and general operations of Altair License Management System on Windows, Linux, and UNIX platforms. It contains: Altair License Management System Release Notes Version 9.0 Chapter 1: Altair License Management System Chapter 2: Preparing to install Altair License Management System Chapter 3: Installing Altair License Management System on UNIX and LINUX Chapter 4: Installing Altair License Management System on Windows Chapter 5: Operation and Maintenance Chapter 6: Altair GridWorks licensing Appendices Chapter 1 provides fundamental knowledge about Altair License Management System and its main components. Chapter 2 lists the general installation procedures for required items, hardware and operating system consideration, and the list packages for each platform. Chapters 3 and 4 provide detailed instructions for installing the Altair License Management System on UNIX/Linux and on Windows. Chapter 5 documents information about operating and maintaining the license system including the license management and usage report. Chapter 6 provides the concepts of Altair GridWorks licensing system. Appendices provide additional information about licensing tools, license files, the license manager, usage tracking, and keyword options.
About Altair License Management System

Altair License Management System provides a common unit-based licensing model (GridWorks) for all Altair software - CAE, on-demand Computing, and Business Intelligence. This new system has been designed to enable HyperWorks Partner Products (selected third party products) to be licensed via GridWorks Units. The Altair License Management system comprises of two main parts: the license manager and the usage report system. The license manager is based on FLEXnet Publisher V10.8 (Also known as FLEXlm). The usage report system extracts the application usage data from license server and records the data to a log file located on the customers system. As part of the license agreement that

Overview enables partner software to be used, product usage must be sent to Altair.
Two types of licenses, GridWorks license and Feature license, have been applied to Altair products: GridWorks license: In this scheme, customers are given a fixed number of licenses for the GridWorks features. This is commonly referred to as GridWorks Units (GWUs). A GridWorks enabled Altair product, such as HyperWorks, can be launched as long as the associated tracking feature for this product is included in the license file and there are sufficient GWUs to grant the license check out. Feature licenses: Feature licenses allow a specific Altair application to run. A single license for the given feature name is checked out when feature based licenses are used. Feature licenses can be node-locked to a single machine, or a network floating license that is available to many machines on the network.
Conventions Used in this Guide

This guide uses the following conventions: Bold Italic All words from the user interface, including options, menus, buttons, and dialog box names. Example: On the Welcome screen, click Next. Courier The path of a program or folder; a Web address; a file name or component; text that the user is expected to enter. Example: The default path is C:\Altair\licensing9.0. Italic For emphasis or for introducing a new term; for names of topics (headings) within this guide. Example: See Minimum Requirements for more details. Warnings and notes pertaining to the installation appear in boxes as in the following. Important notes appear in these boxes. These messages are informational.
Warnings appear in these boxes. Their content is designed to prevent serious installation problems.
Questions regarding the software and license installation may be directed to Altair Support. See the back of the title page for further contact information.

Altair License Management System Release Notes Version 9.1

Altair license system version 9.1, an update release of the license version 9.0, provides the following enhancements and corrections.
Enhancement
License usage tracking Add the following three environment variables to capture the debug output from UMT: ALM_LOG_ENABLED=1, ALM_LOG_FACILITY=syslog, or stderr ALM_LOG_LEVEL=(error|debug|info) UMT/URT can handle multiple licensing ID UMT will report the license ID from the GridWorks FEATURE. If the GridWorks FEATURE is not present, it will take the license ID from the GridWorks INCREMENT feature line. If both a GridWorks FEATURE or INCREMENT do not exist, the first license ID in the file will be reported. UMT will report all the license IDs found in the license file that the UMT is monitoring on. In the usage log file, any license ID found in the license file except the one listed in the License ID will be recorded in the Additional Ids line. The prerequisite of .NET Framework on Windows is removed. When LM_LICENSE_FILE environment variables points to two set of license servers, for example 7788@server1:7788@server2, the UMT will move on to monitor server 2 when server1 is down.
License Manager

Altair License Management System Release Notes: 9.1
Resolved Issues
License usage tracking The issue that ALM_ERROR_TRACKING must be present in the registry for the UMT to start is corrected. Correct the error of UMT version number. The URT setup on Windows XP will be updated correctly in the alus.conf file, The missing "/" in the ALUS_UNDELIVERABLE_DB_FILE_PATH is corrected. The issue of URT/UMT error with the undeliverable.properties file not having proper permissions is corrected. The issue regarding Sun Solaris Buffer IO causing duplication information in the usage log file is corrected. License package Remove the obsolete TTF license file from license package
Known Limitations
Installation URT tries to use wrong izip executable on SLES9/10 PPC 64. The works is to remove the ./alus/utils/bin/LINUX directory and symlink it to the ppc64_se9 directory before starting the license daemon. URT tries to use wrong izip executables on SUN Solaris X86_64. The work around is to remove the ./alus/utils/bin/SOLARIS directory and symlink it to the x64_sun10 directory before starting the license daemon. On SGI IRIX platform, the JRE does not work properly with SSL and DNS lookups. The workaround is using the HTTP to send the data. FLEXnet 10.8 does not support Windows Vista 32- or 64bit platform. To make it work, replace the lmutil, lmgrd and lmtools executables from FLEXNet 11.4. There is a known issue with the license reporting tool when running on RHEL5 and Itanium processors. This issue causes the reporting tool to send data constantly instead of once a month. If you are installing on RHEL5 and Itanium please contact Altair local support for an update to fix this issue. The License Manager vendor daemon (altair_lm) may fail to start on Solaris and HPUX machines, due to insufficient file descriptors. Increasing the hard limit and soft limit of the maximum number of file descriptors available for the license manager (lmgrd) process to 1024 helps resolve this issue.
License Manager
License usage tracking
Vendor daemon

Altair License Management System Release Notes: 9.1 Multiple license pools There is a limitation on HyperWorks leveling when working with multiple license pools. This limitation occurs due to the following FLEXlm characteristics: o Each license pool functions independently of other license pools and cannot communicate with any other license pool. o The application tries all license servers in the order in which they are listed in the ALTAIR_LM_LICENSE_FILE or LM_LICENSE_FILE environment variables. The first available license server that can grant licenses is used for checkout. o A license pool is a collection of licenses that could consist of a single license server or a cluster of redundant servers. Within a single license pool, you can launch multiple HyperWorks applications on the same host and with the same display with the number of licenses consumed being equal to the number required by the application with the highest draw of licenses. If launching new HyperWorks applications by the same user/host/display causes licenses to be drawn from a license pool other than the one checked out earlier (perhaps because the first license pool has run out of licenses), additional HyperWorks units are checked out from the second license pool, thus stacking the licenses. For a three-server redundancy licensing setting, it is recommended to have all three servers physically located close to each other, and on the same subnet. Placing three servers in different geographical locations is not recommended by FLEXNet. When working with three server license pool configurations, licenses may be leveled on UNIX (in most cases) by setting the HW_POOL_SECURITY environment variable to 1. lmborrow option The lmborrow option used to borrow mobile licenses only works for products that do not stack licenses. A borrowed license listed in the LMTOOLS is not automatically updated when the license expired. Manually checking the feature back in is required.
LMTools
On Windows, the GUI for lmtools ignores the following environment variables when launching lmgrd. ALTAIR_NOLOG ALTAIR_LOGFILE ALTAIR_LOG_INTERVAL As a workaround, start lmgrd from the command line.

Altair License Management System Release Notes: 9.1 Altair License 9.0 Release Notes
Starting in HyperWorks 9.0 release, most of Altair products, including HyperWorks 9.0 applications and the PBS/GridWorks products, will be licensed under a single license system called Altair License Management System. Two main changes are made to this new system: a switch has been made from HyperWorks licenses (HyperWorks Units, or HWU) to GridWorks licenses (GridWorks Units, or GWU), and the system now has the capability to report license usage information. GridWorks Units work very much like HyperWorks Units with one main difference: one HyperWorks Unit is equivalent to 100 GridWorks Units. This change allows for the pricing of less expensive Altair products within the same unit-based licensing system. The Altair License Management system has been designed to enable HyperWorks Partner Products (selected third party products) to be licensed via GridWorks Units. As part of the license agreement that enables partner software to be used, product usage must be sent to Altair. The Altair GridWorks license package contains both the FLEXnet license manager and usage reporting tools.

New Features
GridWorks licensing The Altair licensing system now uses GridWorks Units (GWU). o o o A new feature, GridWorks, has been added for license units. 100 GridWorks units is equivalent to 1 HyperWorks unit. A new set of global license features has been added: GlobalGridWorksAM, GlobalGridWorksEU and GlobalGridWorksAP.
HyperWorks 9.0 application will recognize the GridWorks units and not the HyperWorks units.
License usage tracking
The licensing usage monitor and reporting tools (UMT and URT) is included in the 9.0 License Manager package. UMT and URT record the usage of each feature (in GWU.unit minutes) and will send the report back to Altair on a monthly basis. The usage log files that are generated are in plain text. Licensing features for HyperWorks Partner Software are implemented in the Altair license Management system. This allows partner software to check out GridWorks units.
Partner software

Altair License Management System Release Notes: 9.1 License files
The tracking features listed in the license file are now required to launch an Altair product that draw GridWorks units. Without the tracking feature, the associate Altair product will fail to invoke. New license features for HyperWorks 9.0 applications: o GridWorks o GlobalGridWorksAM o GlobalGridWorksEU o GlobalGridWorksAP o HyperGraphTrans o RadiossA o RadiossB o RadiossCheck o OptiStructCheck o ADM_NAMED o ADM_WEB_ENTRY o ADM_CONCURRENT
License Manager
License manager uses FLEXnet Publisher v10.8. License Manager has its own package and not bundled within the HyperWorks application packages. License Manager supports the platforms supported by most of Altair products recognize the GridWorks licenses, including HyperWorks.

Altair License Management System Release Notes: 9.1 Leveling/Stacking of batch applications
HyperWorks Solvers (OptiStruct, RADIOSS, and MotionSolve) that run under the same UHD (user, host, and display) will level or stack under the new licensing mechanism described below: o At the first invocation of a batch application, GridWorks Units will level against the existing HyperWorks applications. o Similarly, at the first invocation of a different batch application, the GridWorks Units still level. o The GridWorks Units stack when you invoke two or more instances of the same batch application. o When the leveled run finishes, the next invocation levels again.
Leveling and stacking are not restricted by the number of machine cores. The GridWorks Units required for each RADIOSS instance changes and is dependent on the number of machine cores.
Resolved Issues
License Manager License Manager on a Linux 64-bit machine is more robust and stable. License Manager no longer restarts when an application is invoked. License Manager now works properly with a combined license (multiple flex license file combined). altair_lm no longer fails to start on SLES 10.0 platform if the working directory of lmgrd is not writable. In this case, logging will be disabled.
Known Limitations
License Manager FLEXnet 10.8 does not support Windows Vista 32- or 64-bit platform. To make it work, replace the lmutil, lmgrd and lmtools executables from FLEXNet 11.4. The License Manager vendor daemon (altair_lm) may fail to start on Solaris and HPUX machines, due to insufficient file descriptors. Increasing the hard limit and soft limit of the maximum number of file descriptors available for the license manager (lmgrd) process to 1024 helps resolve this issue.
Vendor daemon

Altair License Management System Release Notes: 9.1 Multiple license pools There is a limitation on HyperWorks leveling when working with multiple license pools. This limitation occurs due to the following FLEXlm characteristics: o Each license pool functions independently of other license pools and cannot communicate with any other license pool. o The application tries all license servers in the order in which they are listed in the ALTAIR_LM_LICENSE_FILE or LM_LICENSE_FILE environment variables. The first available license server that can grant licenses is used for checkout. o A license pool is a collection of licenses that could consist of a single license server or a cluster of redundant servers. Within a single license pool, you can launch multiple HyperWorks applications on the same host and with the same display with the number of licenses consumed being equal to the number required by the application with the highest draw of licenses. If launching new HyperWorks applications by the same user/host/display causes licenses to be drawn from a license pool other than the one checked out earlier (perhaps because the first license pool has run out of licenses), additional HyperWorks units are checked out from the second license pool, thus stacking the licenses. For a three-server redundancy licensing setting, it is recommended to have all three servers physically located close to each other, and on the same subnet. Placing three servers in different geographical locations is not recommended by FLEXNet. When working with three server license pool configurations, licenses may be leveled on UNIX (in most cases) by setting the HW_POOL_SECURITY environment variable to 1. lmborrow option
The lmborrow option used to borrow mobile licenses only works for products that do not stack licenses. A borrowed license listed in the LMTOOLS is not automatically updated when the license expired. Manually checking the feature back in is required.
LMTools
On Windows, the GUI for lmtools ignores the following environment variables when launching lmgrd. ALTAIR_NOLOG ALTAIR_LOGFILE ALTAIR_LOG_INTERVAL As a workaround, start lmgrd from the command line.
10

Altair License Management System 9.1 Installation Guide 9.1 11

Chapter 1: Altair License Management System
This chapter introduces the Altair license management system, the key components of this system, and the mechanism of how Altair licensing works.
1.1 Introduction
Altair License Management System provides a common unit-based licensing model (GridWorks) for all Altair software - CAE, on-demand Computing, and Business Intelligence. This system comprises of two major parts: the license manager and the usage report system. The license manager is based on FLEXnet Publisher V10.8 (Also known as FLEXlm) is a set of licensing libraries provided by Macrovision Corporation. It consists of the following two schemes for license checkouts: GridWorks license: In this scheme, customers are given a fixed number of licenses for the GridWorks features. This is commonly referred to as GridWorks Units (GWUs). A GridWorks enabled Altair product, such as HyperWorks, can be launched as long as the associate tracking feature for this product is included in the license file and there are sufficient GWUs to grant the license check out. Feature licenses: Feature licenses allow a specific Altair application to run. A single license for the given feature name is checked out when feature based licenses are used. Feature licenses can be node-locked to a local machine, or a server type (floating) that is available to many machines on the network. The usage report system contains the usage monitoring tool (UMT), the usage report tool (URT) and the Altair application server (AAS). The report system extracts the application usage data from the license server and records the data to the log file(s) located on the customers system. Your company signed a new license agreement and agreed to provide certain software usage data to Altair. You may install the Altair License Management System with this usage report tools so that this monthly reporting is automated - a 'push' from you, the customer, to Altair. Or you may choose a 'man-in-the-loop' option whereby someone within your company will be responsible for reviewing the monthly report and then submitting it to Altair. The key components of an Altair license management system are: the Altair License Sever (ALS), the Usage Monitoring Tool (UMT), the Usage Reporting Tool (URT), and the Altair Application Sever (AAS).

13
Chapter 1: Altair License Management System ALS: UMT: Altair License Server, the FLEXlm license server distributed by Altair. Usage Monitoring Tool, the mechanism that will query the server and log license usage. Usage Reporting Tool, the mechanism that will send the logs back to Altair. Altair Application Server, references the application server that is deployed to accept usage logs from the customers.
URT: AAS:
Based upon Altairs partner program, a number of independent software vendors (ISVs) can provide their software to you via Altairs patented license management system. Customers who install these license enabled applications can launch these products by drawing the GridWorks units from the Altair license pool if sufficient GridWorks Units are available.
1.2 Altair License Manager

Altair license manager uses FLEXnet Publisher v10.8 libraries. There are four main components of FLEXnet. License manager daemon (lmgrd) Vendor daemon (altair_lm) License file (altair_lic.dat) Application program (e.g., HyperWorks, PBS professional, HiQube, etc.) A brief discussion of each follows.
14

1.2a
License Manager Daemon (lmgrd)
The license manager daemon, lmgrd, is one of the two components (the other being the vendor daemon described below), which comprise the license server. lmgrd runs in the background and handles the initial contact with an Altair application and passes the connection to the vendor daemon, altair_lm. lmgrd also starts and maintains the vendor daemon, altair_lm. FLEXnet Publisher permits the application to use multiple license servers for redundancy on different machines. This allows some, or all, of the licenses to be available even if one or more server nodes fail.
1.2b
Vendor Daemon (altair_lm)
Each vendor who has a FLEXnet licensed product on the network has one background process on the machine where the license manager daemon (lmgrd) is running, called the vendor daemon. For Altair products, the vendor daemon is the altair_lm process. altair_lm is started automatically by the FLEXlm license manager, lmgrd, and keeps track of how many licenses are checked out, and who has them. If the altair_lm/lmgrd daemons terminate for any reason, all users of HyperWorks will be disconnected from the license server. Users will automatically regain their licenses, and not notice any difference, if the application can establish the connection with the altair_lm within fifteen to twenty minutes. If the connection cannot be established within the timeout period, the applications will prompt users to save their work and quit. Altair products (for example, HyperWorks programs) communicate with the altair_lm daemon through TCP/IP sockets. The client node (where the application runs) and the license server (the lmgrd daemon and altair_lm daemon processes) can run on separate nodes on your network. Also, the traffic between the altair_lm and the license manager daemon is machine-independent, allowing for heterogeneous networks. This means the license server and the workstation that is running the application can be different hardware platforms or different operating systems.
1.2c
License File (altair_lic.dat)
A text file, called the license file, stores the licensing data. It contains information about the server nodes and vendor daemons. The general name Altair products used for this license file is altair_lic.dat. The default location of the license file is: UNIX Windows [User-defined installation directory]/altair/security/altair_lic.dat [User-defined drive]:altair\licensing9.0\security\altair_lic.dat
End users can also set the environment variable, ALTAIR_LM_LICENSE_FILE, to point to the license server serving Altair licenses. See Chapter 5, Section 7: Environment Variables for more information. If you need details on managing licenses from multiple vendors using FLEXnet Publisher, refer to the Appendix H. The license files can contain node locked or floating network licenses. Altair License Management System 9.1 Installation Guide 9.1 15
Chapter 1: Altair License Management System The network license is available to many machines on a network. It is usually called the server license which requires an active FLEXlm license manager process. The GridWorks licensing only works as a network floating license. In order for the applications to draw units from the GridWorks licensing pool, the GridWorks license file must contain the tracking features for the application. A node locked license is locked to an individual machine. There is no need to run the license manager for this type of license. Altair GridWorks feature does not work as a node locked license. The detail description of an Altair license file format can be found in Appendix C: License File Format.
1.3 Usage Monitoring Tool

The main function of the Usage Monitoring Tool (UMT) is to communicate with the Altair license manager, query the number of the GridWorks units and tracking features that are checked out from this server, and write the information to a log file periodically. The UMT performs the following logging tasks periodically: Once per minute, it queries the number of the Altair GridWorks Units and the tracking license features that are checked out from that license pool. Once per hour (and whenever the UMT is shut down), it totals the number of license times minutes for each feature and write the totals to a file. Once per day, it writes the log file to disk and opens another file. Once per month, it launches the Usage Report Tools (URT) to transmit the files to Altair. The report transmitted at a random time during the first week of each month to reduce server load.
The UMT runs separately from the FLEXlm license manager (two different executables). It can be started automatically at the same time as the license manager, or can be set up later. It is recommended to run the UMT and License manager on the same machine. However, you can set them on separate machines as long as proper environment variables are set. UMT Limitations The UMT relies on a system init script to start. If this fails, the UMT will not run and no data will be logged. If there is a problem with UMT operation, there is no means for Altair or the customer to learn of the breakdown until the next data report is missed. This could lead to the loss of a month or more of data. Altair License Server will continue to work even if the UMT is turned off or not functioning properly. If an application starts and ends between two successive samples, no time will be recorded for that application.
16

1.4 Usage Reporting Tool

The Usage Report Tool (URT) is a tool that is launched by the Usage Monitoring Tools (UMT) once per month. When it is initiated, it will read the log files recorded by the UMT, validate them, and transmit the data. In order to transmit valid files from the customer site to the Altair site, the URT needs to be configured by customers to be able to contact Altair through their firewall. Both UMT and URT are installed on the customers intranet. File transferring functions in a one-way direction, from the customers intranet to Altair application server. The report log file contains digital signatures. Any altered log file is considered as an invalid log file which will not be transmitted. If the connection does not go through, the URT will try again up to seven times before moving the files to a undeliverable directory. If you decide to disable the automatic reporting system (URT), you must send the usage log files to Altair manually per the Altair license agreement.
1.5 Altair Application Server

The Altair Application Server is a server located at Altair site. It provides a service that allows the URT, residing on each customers intranet, to connect and transfer log files.

1.6 Tracking Features and Report Log File

1.6a Tracking features
An Altair product or an ISV partner software will run only if an associated tracking feature is present in the license file for that product. These tracking features will also be used for usage logging. These applications will each check out GridWorks, Global GridWorks (AM, EU or AP), and tracking licenses. The same quantity of tracking licenses as GridWorks licenses will be checked out by each application. GridWorks and Global GridWorks licenses may level or stack, depending on the application. For example, HyperMesh levels and Data Manager stacks. However the tracking licenses will always stack, meaning that each instance of each application will increment the total number of tracking licenses. Example 1: If a single instance of HyperMesh is running, it will draw the following number of licenses - 2100 GWU - 2100 Global GWU(AM) - 2100 HyperMesh tracking Example 2: If one user launches two copies each of HyperMesh, HyperGraph, and MotionView on the same machine and the same display (same UHD), the server will draw the following number of licenses - 2100 GridWorks - 2100 Global GridWorks (AM) - 2100*2 = 4200 HM3D tracking - 600*2 = 1200 HG tracking - 2100*2 = 4200 MV tracking For some applications, the usage of specific user profiles (LsDynaUP, AbaqusUP, NastranUP, etc.) is tracked in the log file. These user profile tracking features do not draw any GWUs or GlobalGWUs. Applications that use user profile tracking features will check out one user profile tracking license, leveled, for each instance of the application that is using a particular user profile.
1.6b Report log files

The first few lines listed in the report log file give you useful information such as the license ID of the license file where the GridWorks units are pulled from, the server, the list of the tracking features the license file contains, etc. Every license file issued by Altair License Manager System 9.0 will contains a 34-character license ID that is unique to each license file. Every sample time, the number of the licenses checked out by an individual feature is multiplied by the number of the minutes between samples (one minute). For each feature, this number is summed at each sample time, and is written and reset each time a record is written (one record per hour). In each <data> row, it lists the values of the date/time, the feature:number_used and a signature. The feature:number_used lists the name of the tracking feature and the total number of license*time used during this record period.
18

1.6c Location of report log files

Once the UMT is launched, it starts querying the number of the GridWorks Units and tracking features that are checked out from the license server, and writing the information to a log file every hour. Depending on the time and in which phase of the usage reporting process, the log file can be located in one of the following folders: processing, pending, scratch, sent, invalid or undeliverable When UMT is started and the first data is ready to be written to the disk, a log file is created with a file name of umt_log_<year><month><data><time> to collect the data. This first log file resides in the processing folder until it is one day old, and then it is moved to the pending folder. A new log file will be created again in the processing folder with new time stamp to collect the data from the second day. The same process continues until the first week of the month when UMT launches the URT and to transmit the data to Altair application server. To avoid the heavy traffic of transmitting the data, the hand shake time is chosen randomly within the first week of each month. When URT starts, it will first validate the data in the pending folder and then move those files deemed invalid to the invalid folder and the valid log files to the scratch folder, and then compress them into one zip file before sending them to the application server. The zipped file remains in the sent folder after one copy of the zip file is transmitted to Altair. If the URT fails to send the zip file after trying seven times (within 75 minutes), the zip file will be placed in the undeliverable folder. The next month, the URT will take the zip files from both the undeliverable and the pending folders and send them to the Altair applications server. It is recommended to monitor the invalid and undeliverable folders periodically. Contact Altair support if the problem sending the log file occurs and persists. By default, these folders are located in the following directory. You can change them through the configuration file, alus.conf. An example of how to set the locations of these folders can be found in the Appendix B:Example of alus.conf File.

Chapter 1: Altair License Management System <installation directory>\security\urt_dist\alus\data\
1.7 alus.conf File

The alus.conf is a configuration file that stores the values of the variables for the usage report systems (UMT and URT). The values of some variables, like proxy settings, are blank and set by the user during the install time. Some of the values, like the data folders described in the previous section, are given by default once the user has chosen the installation directory. If the values set during the install time are no longer valid, you can modify them in the alus.conf file before activating the UMT/URT processes. If the UMT is running already, you can terminate the process, modify the alus.conf file, then restart the process. The example alus.conf files for Windows and UNIX are listed in the Appendix E: Example of alus.conf File.
1.8 System Limitation

The usage report system is designed to report the usage of the GridWorks Units. Some limitations apply to this version of Altair License Management System: Node_locked standalone licenses are not tracked. The system does not track which version of Altair application is being run. The UMT queries the usage data from the license server every minute. For a three-server redundancy setting, when the master goes down and the second server becomes the master, the UMT may not be able to query the data from the new master until a new log file is generated, typically the next day.. Altair License Management System 9.1 Installation Guide 9.1
20

Chapter 2: Preparing to Install Altair License Management System

This chapter summarizes the items and procedures needed to install and successfully run Altair License Management System on Linux, UNIX, or Windows platforms. It includes a list of required items, access to the license package, hardware and operating system considerations, system requirements, and the compatibility of a license server running on HyperWorks Units and GridWorks Units.
The general procedures of installing and activating the license management system are: Determine the server(s) for license manager and the usage report system. Verify there is no license manager from previous version (i.e., HyperWorks license manager) running on the servers. Download the proper package(s). Install License Management System on the designated machine(s) and, if required, install the hardware key (dongle) on the appropriate machine(s). Activate the license manager and the usage report system. Point an existing Altair product to the activated license system via the environment variable.
What you need: An access to the Altair Web site Altair License Management System CD, or images downloaded from the Altair Web site. CD drive License file (generally received via e-mail) A hostid for UNIX installations Either an Ethernet (MAC) address or a hardware key (dongle) provided by Altair Engineering, Inc. for Windows installations
22
HyperWorks 9.1 Installation Guide

2.1 Installation Media

The Altair License Management System 9.0 software is available for downloading by registered customers from the Altair Web site through the Altair Client Center (http://www.altairhyperworks.com/clientcenter). The images on the Altair web site are one tar file per platform. Download the images for the platforms from which you expect the license manager and usage report system to be launched. If you plan to run the license manager and the usage report system on different server, download the proper packages for both servers. Consult the following list to download the right package for your system.
Package Name altair_flexlm-9.1.amd64_s8 .tar
Platform Details Linux-AMD64 SUSE Enterprise Server8 or later, RHEL3.0 or later 64 bits
altair_flexlm-9.1.hp700_u11.tar
HPUX PARISC HPUX 11.11 32 bits
altair_flexlm-9.1.i86_r9 .tar
Linux-x86 RH 9.0 or higher 32 bits (glibc >= 2.3)
altair_flexlm-9.1.it32_hp11.tar
HPUX-Itanium 11.23 32 bits
altair_flexlm-9.1.it64_re3.tar
Linux-Itanium RHEL 3.0 IA 64 bits
altair_flexlm-9.1.ppc64_se9 .tar
Linux-PPC64 SUSE Enterprise Server 9 or later PowerPC 64 bits
altair_flexlm-9.1.ppc_u4.tar
AIX 5.1or higher Power PC 32 bits
altair_flexlm-9.1.sgi32_u6.tar
SGI IRIX 6.5 32 bits

altair_flexlm-9.10.sun4_u7.tar
SUN Solaris Sparc 2.7 to 2.10 32 bits
altair_flexlm-9.1.sun64_u5.tar
SUN Solaris Sparc 2.7 to 2.10 64 bits
altair_flexlm-9.1.x64_sun10.tar
SUN Solaris 10 AMD 64 bits
licensing9.1_win32.exe
Windows XP
licensing9.1_win64.exe
Windows XP 64
2.2 Compatibility
In general, you cannot run two versions of Altair license managers on the same server because they use the same vendor daemon (altair_lm). Before you install the license package, make sure there is no license manager daemon (lmgrd) and Altair vendor daemon (altair_lm) running on this machine. Remove the license registration key and the environment variables (ALTAIR_LM_LICENSE_FILE and LM_LICENSE_FILE) if the license manager is running on a Windows operating system.
2.3 Selecting License Server Nodes
The license files are of two types: Network Node locked License available to many machines on a network. This is usually called the server license. It requires an active FLEXlm license manager process. License is locked to an individual machine. There is no need to run the license manager for this type of license.
24

Chapter 2: Preparing to Install Altair License Management System The following section helps you decide which machines to use for license servers.
Resources Used By License Servers

When you select a server machine, you may need to take into account the system limits on these resources. For small numbers of licenses, most of these system limits are not a problem on any workstation.
Sockets
Each licensed application connected to a license server uses one or more sockets (two sockets are used if SAMsuite tracking is enabled in the license file). The number of sockets available to the license server is defined by the per-process system limit for file descriptors. The total number of sockets used by the license server is slightly larger than the total number needed by the licensed applications, which are served by it. If the number of sockets that are required by the license server on a single machine becomes excessive, then it is probably good to split the license file into more than one file, onto different servers, to lighten networking traffic. The client applications can then check out licenses from multiple servers using a license-file list via the ALTAIR_LM_LICENSE_FILE environment variable.
CPU Time
For small numbers of clients, the license servers use very little CPU time. The servers might have only a few seconds of CPU time after many days. For a large number of clients, or for high checkout/checkin activity levels, the amount of CPU time consumed by the server may start to become significant, although even in this case, CPU usage is normally not high. In this case, you may need to ensure that the server machine you select has enough CPU cycles to spare.
Disk Space
The license package requires about 100 MB disc space to install. The log files created by the usage report system resides in the same directory as the Altair usage report tools installed. There is at least one log file created per day. It is recommended to have 50 MB of available disk space for this monthly log files. The log files once sent to Altair will still remain on the UMT/URT server located on your site. You can either move these log files and maintain them on another machine, or reserve enough disk space on the usage report server.
Memory
The license manager daemons use little memory. The lmgrd daemon uses approximately 2 MB and the vendor daemons use approximately 2 MB each, although memory usage increases in the vendor daemon with the size of the license file, the size of the options file, and the number of concurrent users. The usage report tool, URT, requires roughly 20 MB.
Network Bandwidth
FLEXlm sends relatively small amounts of data across the network. Each transaction, such as a checkout or checkin, is typically satisfied with less than 1KB of data transferred. This means that FLEXlm licensing can be effectively run over slow networks (such as dial-up SLIP lines) for a small number of clients. For a large number of FLEXlm applications (hundreds), the network bandwidth may start to become significant. In this case, run the client application and license server on the same local area network, which may require splitting licenses between two files for two servers.

Chapter 2: Preparing to Install Altair License Management System Users can use a license file list in the ALTAIR_LM_LICENSE_FILE environment variable to have effective access to both servers.
Remote Mounted Disks

Macrovision recommends that you do not use remote mounted disks when you run the license server. In other words, lmgrd, altair_lm, the license file, the debug log file and the report log files should be on local mounted disks. If any of these files are on a remote mounted disk, you double the points of failure, which could lead to temporary loss of licensing service
Redundant License Servers

If you want to use redundant servers, select stable systems as server machines. In other words, do not pick systems that are frequently rebooted or shut down. FLEXlm supports redundancy via a license-file list in the ALTAIR_LM_LICENSE_FILE environment variable, or via a set of three redundant license server configurations. Redundant licenses are covered in Chapter 5, Section 1, Set up Redundant License Servers.
2.4 System Requirement

In addition to selecting a proper machine as a server, it is important to have a stable and robust network system that allows client machines to communicate with the server efficiently. The Altair License Management System requires about 100 MB disc space to install. You also need enough disk space to store the usage data. It is recommended to have 50 MB of available disk space for the monthly log files. The log files created by the usage report system reside in the same directory as the Altair usage report tools were installed. The log files after sent to Altair will not be removed from the UMT/URT server located on your site. You can either move these log files and maintain them on another database, or reserve enough disk space on the usage report server. There is a dependency between Microsoft .NET Framework and Altair License Management System. If a Windows XP or Windows XP64 machine is chosen to be the server where the usage report system is running, it is necessary to install the .NET Framework version 2.0SP1 before installing Altair License Management System. This dependency will be removed with Altair license management system 9.1 release.
26

Chapter 3: Installing Altair License Management System on Linux/UNIX
If you will be installing on a Windows machine, see the software installation instructions in Chapter 4. You need super user permissions to install this software. Check with your systems administrator for your installation requirements.
This guide provides the major steps required to install and activate the license manager 9.0 and the usage report system on Linux and UNIX. For server licenses, install the Altair License Management System package on the license server machine(s). On the application servers, install the required applications. Set each client's environment variable to point to the license server(s).
3.1 Install License Manager and Usage Report System on the Same Server
Make Sure there are no earlier versions of HyperWorks license server running on this machine. Solaris 10 AMD Systems must link the x64_sun10 directory to SOLARIS. Use the following commands.
cd <altair_home>/security/urt_dist/alus/utils/izip/bin rm rf SOLARIS ln s x64_sun10 SOLARIS

27
Chapter 3: Installing Altair License Management System on UNIX/Linux
Consult the table listed in Chapter 1 to download the package (in tar format) that is appropriate for the machine that is served as license server. You can download the package from the Altair Web site (www.altair.com), or from the CD media sent by Altair.
3.1.a Install software

1. Download the proper package(s). 2. Mount the CD-ROM drive containing the licensing manager CD to a directory on your machine (for example, /CDROM ) if the tar images are sent to you through the CD media. 3. Log in as root on the machine where the license package will be installed You need to log in as root to set up the license init scripts to automatically launch the daemons at boot time. 4. Place the downloaded package in a directory where you have permission to extract the files. Use the tar xvf command to extract files from the package. For example, tar xvf altair_flexlm-9.0.i86_r9.tar The licsetup.sh file that is used to launch the installation procedure is located in the directory where the packaged is extracted. 5. Change to the directory where licsetup.sh resides and run the command ./licsetup.sh to start the installation process. 6. Answer the questions and designate the location where you want to install the licensing package. If you provide a non existing directory, the script will try to create it. The script creates a sub-directory, altair/, where the License Manager and the report tools software reside. This directory needs to be writable by the user who will be running the daemons. The script extracts the required files from the different packages and installs them in the altair/security/ and altair/scripts/ directory. The installer installs Altair License manager, the usage monitoring package, the usage reporting package, and the Java runtime package. 7. Configure the usage monitoring/report server and provide the proxy configuration data: protocol, IP address, Port number, username and password. You have option to choose HTTPS or HTTP. If you do not have the data to configure the proxy, you can skip this step and later manually modify the altair/security/urt_dist/alus/alus.conf. Alternatively, if you have no proxy, you can choose to set up the proxy and leave all the fields (aside from HTTPS or HTTP) blank. You have now completed the software installation.
28

3.1.b Install and modify the license file

Server licenses require an active FLEXnet Publisher (FLEXlm) license manager process. Node-locked licenses do not. If you need to manage license servers from multiple FLEXlm vendors, refer to Appendix H.
FLEXnet Publisher is case- and space-sensitive. The license in the altair_lic.dat file must look exactly as it does in the e-mail message you receive. Save the .dat file as a text file, making sure the extension remains .dat.
You will need a GridWorks license supplied by Altair Engineering, Inc. to complete the activation process. If you do not have a license, contact your account manager at Altair Engineering, Inc. or your local Altair support office for assistance. With your request, provide the lmhostid value of your license server. 1. To obtain the host ID for the machine that hosts the license server, on the machine where the license package was installed, run the following command to get the host ID <Install_location>/altair/scripts/lmhostid 2. Verify the first word in the GridWorks license file for a server or network license is SERVER. Save the license file in the installation directory: <install_location>/altair/security/altair_lic.dat>. 3. All server licenses need correct hostname on the SERVER line(s). Open the license file, altair_lic.dat, in a text editor. Replace the hostname on the SERVER line(s) with the hostname/IP address of the license server machine(s), and save the file.
4. Replace hostname with the license server machine name or IP address For single servers, there would be only one SERVER line with hostname and port number. SERVER hostname 807d5133 7788 Port Number
For three-server redundancy servers, there are three SERVER lines. SERVER hostname 807d5133 7788 SERVER hostname 807d4132 7788 SERVER hostname 807d7138 7788 When finished, your server lines will be similar to the following example: SERVER licsera 807d5133 7788 SERVER licserb 807d4132 7788 SERVER licserc 807d7138 7788 5. Modify the port number if necessary If the port number 7788 (appearing on the SERVER line(s) in your Altair license) is used for any Port Number

Chapter 3: Installing Altair License Management System on UNIX/Linux other non-Altair application, change 7788 to another unique number on all SERVER lines. Refer to Appendix H for additional information on managing multiple license servers from different vendors. 6. Copy the modified license to all other license servers If this is a three-server redundant installation, copy the modified license to the <install_location>/security/altair_lic.dat file for the remaining license servers in the installation.
FLEXlm is case- and space-sensitive; the copied license must look exactly like the license on the server. Before starting the license daemons, remove the ./alus/utils/bin/SOLARIS directory and symlink it to the x64_sun10 directory. Before starting the license daemons, remove the ./alus/utils/bin/LINUX directory and symlink it to the ppc64_se9 directory. Solaris 10 uses a services system to run lmgrd, altair_lm, and the umt. When installing the boot scripts, after reboot in order to shut them down you will need to use this system. Killing the processes or using the altairlm.init.sh script will not work, as the services system will restart them immediately. Refer to the man pages for svcs and svcadm for information on this system.
3.1.c Start the license daemons

The preferred method of starting the license system is using the altairlm.init.sh script located in the <Install_location>/altair/security directory. This script sets the necessary environment variables (ALUS_HOME, ALUS_CONF_FILE, the default location of the license file, and the default license log file location) for the license system to run, and starts the lmgrd and altair_lm daemons, and the Usage Report/Monitoring tools. 1. On the UNIX command prompt, change to the <Install_location>/altair/security/ directory. 2. Execute the following command: ./altairlm.init.sh start You have now completed the activation of the license system.
3.1.d Set up Start up script (Optional)

This section is only needed if you start Section 3.1.a as non-root. You must have super user privileges to install the license startup script. Without the root privilege, the flexlm daemon will not start at boot time, which is a helpful function in managing the license server. 1. Remain logged in as root. 2. Run <Install_location>/altair/security/install_altairlm.sh You should see a message similar to the following (installation location may vary by system).
30

Chapter 3: Installing Altair License Management System on UNIX/Linux <Install_location>/altair/security/altairlm.init.sh has been install into /etc/init.dat/altairlmgrd The Altair license Manager Daemon has been installed. Now you have completed the license installation on the server. The following processes should be running on this server: lmgrd altair_lm umt
3.1.e Launch Altair applications from the client machines

Altair HyperWorks 9.0, PBS Professional 9.0, and most of Altair products that are released after 2008 will recognize the GridWorks licensing system. You can launch these products by pointing to a valid 9.0 GridWorks license server through the environment variable, ALTAIR_LM_LICENSE_FILE. Perform the following steps to set up the environment variables on the client machines where the applications are installed, and launch the software. 1. Install Altair products such as HyperWorks or PBS Professional on a client machine. 2. On the client machine, set the environment variable ALTAIR_LM_LICENSE_FILE to <port>@<host>, where port is the port number where the license server is running and host is the hostname/IP address of the license server. 3. If there are multiple license servers, the value of the above environment variables should be set to port1@host1:port2@host2:port3@host3 where port1, port2 and port3 are the port numbers where the license servers are running. The host1, host2 and host3 are the hostnames/IP addresses of the independent license servers that are running under different license files. 4. Launch the application. You can launch an Altair application by selecting the appropriate programs from the <install_location>/ directory. For example, run <install_location>/altair/scripts/hm to start HyperMesh.
3.2 Install License Manager and Usage Report System on Different Machines
By default the Altair License Manager Daemon and the UMT (Usage Monitoring Tools) are started (or stopped) on the same machine. However, you have choice to set them up on different machines by setting the proper values for the corresponding environment variables before starting the licensing system. Perform the following steps to set up this configuration.

3.2.a Prepare the packages

1. Following the same steps described in Section 2.1a, download the proper package for the host that you have chosen to be your license server as well as for the host of UMT/URT tools. 2. On the license server machine, follow the same procedure to extract the files from the package that is for this host machine. 3. On the machine that will run UMT/URT, follow the same procedure to extract the files from the package that is for this machine.
3.2.b Install and activate License Manager

1. Follow Section 3.1a Steps 1-6. 2. Answer no to the question about setting up the proxy. 3. Open the altair/security/altairlm.init.sh file and change the value of the following variables to: ALTAIR_LM=1 ALTAIR_UMT=0 You have now completed the installation and are ready to activate the license servers. 4. Follow the directions described in Section 3.1b-d to complete the activation process. 5. You should see that both lmgrd and altair_lm daemon are running on your machine.
3.2.c Install and activate usage report/monitoring tools

1. Log in as root on the machine where the usage tools will be running 2. Follow Section 3.1a Steps 1-6. 3. Configure the usage monitoring/report server and provide the proxy configuration data: protocol, IP address, Port number, username and password. You have the option to choose HTTPS or HTTP. If you do not have the data to configure the proxy, you can skip this step and manually modify the script altair/security/urt_dist/alus/alus.conf at a later time. Alternatively, if you have no proxy, you can choose to set up the proxy and leave all the fields (except HTTPS or HTTP) blank. 4. Open the altair/security/altairlm.init.sh file and change the value of the following environment variables to: ALTAIR_LM=0
32

Chapter 3: Installing Altair License Management System on UNIX/Linux ALTAIR_UMT=1 You have now completed the installation and are ready to activate the license servers. 5. Follow Section 3.1b-d to complete the activation process. 6. You should see the umt process running on this machine. 7. Reference Section 3.1e for launching Altair applications from a client machine.

3.3 Manually Set up License Manager and Usage Report System

3.3.a Launch the daemons manually
1. Follow the installation procedure described in Section 3.1a-b. 2. The script to invoke Flex license daemon, lmgrd, is located at <Install_location>/altair/scripts/lmgrd 3. It is recommended, although not required, that you run lmgrd as a non-root user. If you choose to use a non-root user, make sure that the user has write access to the current working directory, as the log files and usage data will be written in that area. 4. At the UNIX command prompt, type the following command to go the right directory: cd <Install_location>/altair/security Then run the following command ../scripts/lmgrd -c <Install_location>/altair/security/altair_lic.dat 5. The environment variables, ALTAIR_LM_LICENSE_FILE, ALUS_HOME and ALUS_CONF_FILE must be set in order for the monitoring utility to function. Depending on your shell, use either the 'export' or 'setenv' command to achieve this. 6. Run the following command to set the environment variables: export ALTAIR_LM_LICENSE_FILE=<path to the new license file> or export ALTAIR_LM_LICENSE_FILE=port@host (use real host name and port) export ALUS_HOME=<Install_location>/altair/security/urt_dist/alus/ export ALUS_CONF_FILE=<Install_location>/altair/security/urt_dist/alus/alus.c onf 7. Run the following command to launch the UMT from the security directory: ./bin/<platform>/umt_dist/umt &
34

3.4 Connect to Altair Licensing Server

Most Altair products can recognize GridWorks licensing system. Once connecting to a valid GridWorks license server(s), these products can draw the GridWorks Units and launch successfully. In general, there are three ways to connect Altair products to an existing 9.0 license server and draw the GridWorks Units. On either the machine with local software installation or on the server of the software server installation, use one of the following ways to connect the application clients to the Altair license manager. Method 1: Modify the ALTAIR_LM_LICENSE_FILE environment variable on each client to look for the license on the license server. Any time the license changes, only the license file on the license server(s) will need to be updated. Method 2: Create a USE_SERVER license file and copy it to all clients. Any time the license changes, only the license file on the license server(s) will need to be updated. Method 3: Copy the license file to each client. Copy the license from the license server into the security directory on each client machine. With this method, you will need to do this step every time the license changes. Each Altair Product may have its preference of how to connect to the server. Follow the proper method recommended by the individual product to set up the connection.
3.4.a Set up the environment variable

Set the ALTAIR_LM_LICENSE_FILE environment variable to point to the Altair license server(s) using port@host format. Any time the license changes, only the license server(s) will need to be updated. This is the recommended method for server licenses.
FLEXlm is space- and case-sensitive, so make sure when the license file is copied it looks exactly like the version on the license server.
Method 1: Set up the environment variable,ALTAIR_LM_LICENSE_FILE This method sets the environment variable ALTAIR_LM_LICENSE_FILE, using the port@hostname syntax. Follow the following steps: On each UNIX client machine, issue the following command:
setenv ALTAIR_LM_LICENSE_FILE port@hostname1,port@hostname2,port@hostname3
where port is the port number. The port number in this command matches with the port number in the SERVER line in the license file on the license server. host1, host2, and host3 are the host names can be the names or the IP address of the servers. If you have only one server, use this command: setenv ALTAIR_LM_LICENSE_FILE port@hostname

Chapter 3: Installing Altair License Management System on UNIX/Linux For example: In the C shell: setenv ALTAIR_LM_LICENSE_FILE 7788@host1 In Bourne shell(and its derivatives): Export ALTAIR_LM_LICENSE_FILE=7788@host1 Export ALTAIR_LM_LICENSE_FILE Or, using the IP address on the C shell: setenv ALTAIR_LM_LICENSE_FILE 7788@101.953.23.58
3.4.b Create a USE_SERVER license file and copy it to all clients.

Using this method, any time the license changes, only the license on the license server(s) will need to be updated. On the application server or the local machine where software is installed, copy the altair_lic.dat file from the license server to the <install_location>/altair/security directory. Delete the content of the license except the server line(s). Add the USE_SERVER line to the end of the server line(s). For example: SERVER licsera 807d8553 7788 SERVER licserb 807d2314 7788 SERVER licserc 807d4598 7788 USE_SERVER
3.4.c Use the Altair license file

With this method, you will need to update the license file every time the license file in the server is changed. Copy the altair_lic.dat file from the license server to the <install_location>/altair/security directory on all UNIX clients. For Windows clients the location is <install_location>\security\altair_lic.dat.
3.4.d Connect to multiple license pools

The best way to connect multiple license pools is by setting the environment variable ALTAIR_LM_LICENSE_FILE, to point to all the servers of two license pools using port@host syntax. For example if the user would like to connect to two single-server license pools, on each UNIX client machine, issue the following command:
setenv ALTAIR_LM_LICENSE_FILE port@host1:port@host2
36

Chapter 3: Installing Altair License Management System on UNIX/Linux If the user would like to connect to two three-server license pools, on each UNIX client machine, issue the following command:
setenv ALTAIR_LM_LICENSE_FILE port@host1,port@host2,port@host3:port@host4,port@host5,port@host6
where host1,2,3 are three redundant servers of the first license pool and host4,5,6 are three redundant servers of the second license pool. On UNIX/Linux, use : to separate two license pools (or quorums).

Chapter 4: Installing Altair License Management System on Windows
If you will be installing on a UNIX or Linux machine, see the software installation instructions in Chapter 3. You need Administrator permissions to install this software on Windows.
This guide provides the major steps requires to install and run Altair License Manager 9.0 as well as the Usage Monitoring Tool (UMT) and Usage Reporting Tool(URT). For server licenses, install the License Manager package on the license server machine(s). For application servers, install the required applications. Set each client's environment variable to point to the server.
4.1 Install License Manager and Usage Report System on the Same License Server
Make Sure there is no earlier versions of HyperWorks license server running on this machine.
Consult the table listed in Chapter 2 to download the package (in tar format) that is appropriate for the machine that served as license server. You can download the package from the Altair Web site (www.altair.com), or from the CD media sent by Altair.

39
4.1.a Install software

1. Download the proper package on the machine where the license package will be installed if you do not use Altair license CD. Place it in a directory where you have permission to extract the files. 2. You need to be a member of the administrator group to install this package. 3. Navigate to the CD-ROM drive that contains the CD media sent by Altair, or the directory where the downloaded image is stored. 4. Double click on the licensing9.1_win32.exe or licensing9.1_win64.exe package to start the installation procedures:
5. Press next at the welcome screen. 6. Select the location you would like Altair Licensing installed to. The default is set to C:\Altair\licensing9.1\
40

7. Press next. 8. Allow Altair licensing related files to be installed and completed.
9. The Installer will now quit, and you must set up the license server. Make sure to note the name of the license server Windows Service.
4.1.b Install and modify the GridWorks license file

You will need a GridWorks license supplied by Altair Engineering, Inc. to complete the activation process. If you do not have a license, contact your account manager at Altair Engineering, Inc. or your local Altair support office for assistance. With your request, provide the lmhostid value of your

Chapter 4: Installing Altair License Management System on Windows license server. 1. To obtain the disk serial number for the machine that hosts the license server, on the machine where the license package has installed, launch Start Menu/Altair Licensing 9.1 /FLEXlm Utilities
2. In the Utility windows, click the System Settings tab and note the value listed next to Disk Volume Serial Number. 3. Verify the first word in the received GridWorks license file for a server or network license is SERVER. Save the license file in the installation directory: <install_location>/security/altair_lic.dat>. 4. All server licenses need the correct hostname on the SERVER line(s). Open the license file, altair_lic.dat, in a text editor. Replace the hostname on the SERVER line(s) with the hostname/IP address of the license server machine(s), and save the file.
5. Replace hostname with the license server machine name or IP address For single servers, there would be only one SERVER line with hostname and port number. SERVER hostname 807d5133 7788 Port Number
For three-server redundancy servers, there are three SERVER lines. SERVER hostname 807d5133 7788 SERVER hostname 807d4132 7788 SERVER hostname 807d7138 7788 When finished, your server lines will be similar to the following example: SERVER licsera 807d5133 7788 SERVER licserb 807d4132 7788 SERVER licserc 807d7138 7788 6. Modify the port number if necessary If the port number 7788 (appearing on the SERVER line(s) in your Altair license) is used for any other non-Altair application, change 7788 to another unique number on all SERVER lines. Refer to Appendix H for additional information on managing multiple license servers from different vendors. 7. Copy the modified license to all other license servers If this is a three-server redundant installation, copy the modified license to the <install_location>/security/altair_lic.dat file for the remaining license servers in the installation. Port Number
!
42
FLEXlm is case- and space-sensitive; the copied license must look exactly like the license on the server.

4.1.c Install a Dongle

Dongles are the hardware devices act as a unique hardware ID for FLEXlm. Dongles are installed on workstations and license servers. If the license file is set up through a dongle, follow the following steps to install dongles and set up license: If your installation is using Ethernet (MAC) addresses, skip this section. Two procedures are necessary to make the dongle active. Install the dongle on the appropriate machine. Install the FLEXid Driver. 1. Attach the dongle (hardware key) to the printer or USB port, based on the type of dongle. If a printer cable is plugged into the computer, install the hardware key between the computer and the printer cable. 2. Log onto the local machine or license server as Administrator. 3. Using Windows Explorer, go to the <install_location>\security\bin\win32 folder. 4. Double-click FLEXidInstaller.exe to install the driver. 5. Follow the instructions in the installer. Note: Note: Note While Rainbow Sentinel dongles are no longer available, they are still supported. Dongles are not supported on Windows XP64-bit and Linux. The 7-series of dongles are not supported by FLEXlm.
4.1.d Start the license daemons

1. Start the FLEXlm Utilities windows as described in Section 4.1.b, Step 1. 2. Click the Config Services tab.
Verify that all path names are correct.

Chapter 4: Installing Altair License Management System on Windows If needed, use the respective Browse buttons to specify the path names. The path names should be similar to the following: Path to the lmgrd.exe file: <install_location>\security\bin\win32\lmgrd.exe Path to the license file: <Install_location>\security\altair_lic.dat Path to the debug log file: <install_location>\security\bin\win32\lmgrd_debug.log 3. Click the options Use Services and Start Server at Power Up (appears when Use Services option is checked). 4. Click Save Service. 5. If prompted Would you like to save the settings fro the service: FlexLm Service 1 Click Yes. 6. Go to the Start/Stop/Reread tab. 7. Click Start Server.
Window XP Service Pack 2 Users Servers that run on Windows XP, Service Pack 2 with a built-in firewall will encounter an error when you attempt to start the license server. The vendor daemon will attempt to start, and then quit in a few seconds. Due to the built-in firewall, the status displayed in the lmgrd debug log is 28. To work around this error, perform the following procedure: 1. Select two static TCP ports (one for the SERVER line and one for the VENDOR/DAEMON line). 2. Specify the two port numbers in the license file. For example, if ports 31000 and 31005 are selected, then the license file will read as follows: SERVER xp_sp2 hostid 31000 VENDOR altair_lm "c:\Altair\license9.0\security\bin\win32\altair_lm.exe" port=31005 FEATURE ...... FEATURE ...... 3. Manually configure the Windows firewall to add TCP port exceptions for the selected ports.
Refer to Microsoft documentation for additional information on how to add port exceptions for built-in firewalls. See http://support.microsoft.com/default.aspx?kbid=875357#7.
4.1.e Verify the FLEXnet license manager is active:

1. On a license server, execute: <install_location>\security\bin\win32\lmtools.exe 2. Click the Service/License File tab. 3. Click the Configuration using Services option. 4. Click the Server Status tab.
44

5. Click Perform Status Inquiry. If the service started correctly, a status message is displayed. Review each license server as well as the vendor daemon to show a status of UP. If the daemons are not running, see Chapter 5, Section 2, FLEXnet.
4.1.f Configure the usage report system

1. From the Start Menu, run Altair Licensing 9.1 > Setup URT.
2. You will be asked if the license server is currently running on the machine.

3. Click the radio button for Yes, and press Next. You will be presented with a screen requiring the name of the license service. Enter it here.
4. You will be asked if you would like to establish communications. Answer Now to this question if you want to setup proxy information for the UMT. If you answer Later you will need to setup the UMT on another server or manually edit the configuration file later and installation will now finish.
46

5. You are now asked if you would like to use HTTP or HTTPS to connect to the internet. Choose HTTPS if you would like communication to be encrypted, or HTTP if you prefer information to be clear text.
6. Next you will be asked if you want to setup a proxy, if you select No then no proxy will be setup. If you select Yes you will be prompted for the various values necessary to utilize the proxy setup at your site.

7. The next page will ask you for your proxy host and port values. A default port of 80 is entered for you, this is the most common value and you will only need to change it if your proxy uses a different port
8. The next step will ask you for proxy authentication
48

9. Enter a username and password for your proxy if authentication is required.
10. Now the installation is completed.

4.2 Install License Manager and Usage Report System on Different Machines
By default the Altair License Manager Daemon and the UMT (Usage Monitoring Tools) are started (or stopped) on the same machine. You can also set them up on different machines following these steps:
Make Sure there is no earlier version of HyperWorks license server running on this machine.
Consult the table listed in Chapter 1 to download the package that is appropriate for the machine that served as the usage tracking tools. You can download the package from the Altair Web site (www.altair.com), or from the CD media sent by Altair. On the machine where the usage report tool will be running, 1. Follow the steps outlined in Chapter 4 Section 1.a to finish the software installation. 2. Follow the steps in Chapter 4 Section 1.f to set up and activate the usage report tools.
50

Chapter 4: Installing Altair License Management System on Windows 3. Follow Chapter 4 Section 1.f Step 2; click no since the license server is not on this machine. 4. Now you are finishing setting the UMT machine. 5. On the Altair License Manager server machine, go to the Service control panel (Start >> Control Panel >> Administrative Tools >> Services). Select the service named Altair UMT and then right-click and select Properties from the context menu. Then change the startup type from Automatic to Manual. You may stop the service now if it is already running.
4.3 Connect Altair Applications to the License Manager

Most Altair products can recognize GridWorks licensing system. Once connecting to a valid GridWorks license server(s), these products can draw the GridWorks Units and be launched successfully. In general, there are three ways to connect Altair products to an existing 9.0 license server and draw the GridWorks Units. On either the machine with local software installation or on the server of the software server installation, use one of the following ways to connect the application clients to the Altair license manager. Method 1: Modify the ALTAIR_LM_LICENSE_FILE environment variable on each client to look for the license on the license server. Any time the license changes, only the license file on the license server(s) will need to be updated. Method 2: Create a USE_SERVER license file and copy it to all clients. Any time the license changes, only the license file on the license server(s) will need to be updated. Method 3: Copy the license file to each client. Copy the license from the license server into the security directory on each client machine. With this method, you will need to do this step every time the license changes. Each Altair Product may have its preference of how to connecting to the server. Follow the proper method recommended by the individual product to set up the connection.
4.3.a Set up the environment variable

This method sets the ALTAIR_LM_LICENSE_FILE environment variable to point to the Altair license server(s) using port@host format. Any time the license changes, only the license server(s) will need to be updated. This is the recommended method for server licenses. Follow the instructions for your operating system. Windows XP 1. Right-click Start and choose Explore. 2. Right-click My Computer. 3. Select Properties. 4. Select the Advanced tab. 5. Click Environment variables. Altair License Management System 9.1 Installation Guide 9.1 51
Chapter 4: Installing Altair License Management System on Windows 6. Under User Variables:, select ALTAIR_LM_LICENSE_FILE. 7. For Value: enter the port@host settings from the SERVER lines in this format: port@host1 where port is the port number from the server line and host is the machine name or IP address of each server. The example of a completed entry for Value: for a single server license pool is 7788@host1 The example of a completed entry for Value: for a three-server licensing pool is 7788@host1,7788@host2,7788@host3 If pointing to two independent license pool, use ; to separate the values of these two license pools. For example, the completed entry for Value: for two single-server licensing pools is 7788@host1:7788@host2 The completed entry for Value: for two three-server licensing pools is 7788@host1,7788@host2,7788@host3;7788@host4,7788@host5,7788@host6
FLEXlm is space- and case-sensitive, so make sure when the license file is copied it looks exactly like the version on the license server.
On Windows, use ; to separate two license quorums (or pools).
This method also applies to a local installation with standalone node-locked type licensing if the license file is stored on this machine but not in the <install_location>\security\ directory.
4.3.b Create a USE_SERVER license file and copy it to all clients

A USE_SERVER line in the license file directs the application to contact the license server to obtain licenses. Using this method, any time the license changes, only the license on the license server(s) will need to be updated. This modified license file will work even when the client machine has a different platform than the server.
1. Copy the license from the license server into one clients file: <install_location>\security\altair_lic.dat 2. Keep all of the SERVER lines and remove all of the other lines. 3. Add this line to the end of the file: USE_SERVER Your completed license file will be similar to the following example for single-server installations. SERVER licsera 807d4212 7788 USE_SERVER Your completed license file will be similar to this example for three-server installations:
52

Chapter 4: Installing Altair License Management System on Windows SERVER licsera 807d4212 7788 SERVER licserb 807d6497 7788 SERVER licserc 807d3261 7788 USE_SERVER 4. Save the file. 5. Copy the edited file onto all remaining clients in their license file: <install_location>\security\altair_lic.dat.
4.3.c Use Altair license file

With this method, you will need to update the license file every time the license file in the server is changed. For all clients, copy the license from the license server to the clients file <install_location>\security\altair_lic.dat. FLEXlm is space- and case-sensitive, so make sure when it is copied it looks exactly like the version on the license server. This method also applies to a local installation with standalone node locked type licensing.
Windows, use ; to separate two license pools (or quorums).
4.3.d Set up node-locked licensing for local installation

Some Altair products accept standalone node locked licenses. If you have received a standalone node locked license for a local machine, you need to install the software on the machine where the host ID is specified in the license file. No license modifications need to be done in this case. If the license is set through a dongle, consult Chapter 4.1.c for dongle installation. Use either Section 4.3.a or Section4.3.c to set up license for this type setting.

Chapter 5: Operations and Maintenance

This chapter covers information you may find helpful in keeping the license system functioning normally. It contains information on setting up three-server redundancy, FLEXlm sdministration tools, borrowing license, general troubleshooting, and maintenance sections.
5.1 Setting up Redundant License Servers

5.1.a Introduction
A redundant server setup helps ensure the availability of some or all of your licenses in the event of a system crash of one or more of the license server machines. With some additional administration, you can ensure your licenses are available even if one server crashes. With FLEXnet Publisher, you can set up one of two types of redundant server configurations to operate as a single logical license server: 1) license server list; or 2) three-server configuration. A license server list is a collection of license files, or port@host settings, pointing to license managers serving Altair licenses. Each server listed is one of a group of license servers serving a subset of the total GridWorks licenses. You can set ALTAIR_LM_LICENSE_FILE environment variable to a license file list, where each license file/port@host refers to one of the license servers. The application then tries each server in the list, in order, until it succeeds or gets to the end of the list. If one of the servers goes down, the number of licenses assigned to that server becomes unavailable. The license files/port@hosts listed in the license server list are separated using ; on Windows and ':' on UNIX. With three-server redundancy, if any two of the three license servers are up and running (two out of three license servers is referred to as a quorum), the system is functional and serves its total complement of licenses. If more than one server goes down, no licenses will be available. Threeserver redundant servers need to have excellent communication on a reliable network, need to be physically close to each other, and need to be located on the same subnet. This form of redundancy requires that the servers exchange heartbeats periodically, and poor communication can cause poor performance. You should never configure redundant servers with slow communication or dial-up links. Three-server redundancy does not provide load balancing. Use ALTAIR_LM_LICENSE_FILE list instead for this type of redundancy. This is because with three-server redundancy, only one of the three servers is master, capable of issuing licenses. Since all clients must contact the master, all clients must have reliable networking to a single node.

55
Chapter 5: Operations and Maintenance When is three-server redundancy recommended? It is recommended when there is a license administrator monitoring the license servers. This is because for the three-server redundancy to function, at least two servers need to be up at any given time (known as the quorum). When is three-server redundancy discouraged? When there is less system administration available to monitor license servers. When the system should be more lenient if the quorum is lost. When load-balancing is needed for FLEXlm-licensed applications located far apart (London and Tokyo, for example).You can make servers available locally, with remote servers available as backup. The list of servers need not be limited to three. When the software relies on a single host. In this case, there is a single point of failure, and redundant FLEXlm servers only complicate administration and do not add any redundancy to the overall system. Is it OK to NFS-mount license files when using redundant servers?
We do not recommend running the license manager or accessing the license file from an NFS mounted directory in any situation.
5.1b Setting up a License Server List

As an alternate to three-server redundancy, you can create a license server list using the ALTAIR_LM_LICENSE_FILE environment variable. Split the number of GridWorks Units into smaller pieces and obtain a license for each server. These licenses can then be installed on multiple independent machines. In the event one server goes down, licenses remain available from the remaining servers. The process of installing the license remains the same. In addition, you need to set the ALTAIR_LM_LICENSE_FILE environment variable to a list of servers. The servers can be located far from each other. This is a method you can use to load-balance your system, or to provide a more robust system. The license files/port@hosts listed in the license server list are separated using ';' on Windows and ':' on UNIX. When is it recommended to use an lm-license-file list for redundancy rather than three-server redundant servers? When less system administration is available to monitor license servers. When load balancing is needed for clients located far apart, e.g., London and Tokyo. You can make servers available locally, with remote servers available as backup. License-file list allows applications to be checked out even if more than one of the license server nodes goes down. It is not limited to three servers (any number works). For wide-area networks, local servers can be specified first, with remote servers available as backup. Clients do not require reliable networking to a single node with a license file list, so this is recommended where networking itself requires redundancy.
Example: Suppose a customer wants 20 licenses for feature f1. The license distributor can ship two license
56

Chapter 5: Operations and Maintenance files for 10 licenses each of f1, each with one SERVER line, for two different hostids. For example: License File 1: SERVER node1 12345678 2837 DAEMON demo /usr/local/flexlm/demo FEATURE f1... License File 2: SERVER node2 87654321 2837 DAEMON demo /usr/local/flexlm/demo FEATURE f1... On UNIX the user sets ALTAIR_LM_LICENSE_FILE to file1:file2 (or 2837@node1:2837@node2). When a checkout for f1 is attempted, it first attempts a checkout from node1. If this fails for any reason, a checkout is attempted from node2. For Windows: Use a semi-colon (;) to separate license paths.
5.1c Setting up Three-server Redundancy

To set up three-server redundancy, you must provide the hostid for each of the three servers to Altair Engineering to obtain a license file with three SERVER lines. Each license server requires lmgrd, the vendor daemon program, and the GridWorks license file to be on the local file system. Follow the software installation instructions appropriate to your operating system; then start lmgrd on each license server. Quorums and three-server redundant servers With three-server redundancy, no licenses are available until there is a quorum of servers. A quorum of servers is defined as a strict majority of the servers listed in the license file. In a three-server configuration, a quorum is two. As soon as two of the three servers are running and communicating with each other, all of the licenses are available. lmgrd is started on all three servers. One of the servers starts out as the master server and serves licenses. If the master goes down, another server takes over as master. Redundant servers require a quorum of two servers to be up, or no licenses are served. Start the servers in any order that is convenient. There is no time limit. The first server started of the first two listed in the license file becomes the master.

5.2 FLEXnet Publisher (Also known as FLEXlm)

This section examines the general structure of FLEXnet Publisher administrator tools, license manager options files, and multiple license manager processes from Macrovision.
5.2a License Administration Tools

FLEXlm provides license administration tools that help manage the licensing activities on the network. These include the main daemon program, lmgrd, and lmutil, the main FLEXnet Publisher license management utility. HyperWorks UNIX installations include scripts to execute lmgrd and several commands within lmutil. Altair scripts use the same names as the FLEXnet Publisher utilities.
lmutil
lmutil is the main FLEXnet Publisher license management utility. The commands under lmutil for which Altair Engineering provided scripts are lmborrow,lmdiag, lmhostid, lmnewlog, lmpath, lmremove, lmreread, lmstat, lmswitch, lmswitchr, and lmstat. The Altair scripts use the same name as the lmutil command. For UNIX installations, the scripts for these commands are located in the <install_location>/altair/scripts directory. For Windows installations, execute lmtools.exe located in the <install_location>\security folder. The following table lists the various utilities and their functions. For the complete command syntax for these utilities, see Appendix G. Utility lmborrow Description lmborrow supports borrowing of server licenses. It must be run on the client machine where licenses are borrowed. It is used to perform the following: Initiate borrowing by setting the borrow period. Clearing the borrow period. Determining the borrow status. Returning a borrowed license early.
lmdiag
Allows you to diagnose problems when you cannot check out a license.
lmhostid
Reports the hostid of a system. The output of this command looks as follows: lmutil - Copyright (c) 1989-2003 by Macrovision Corporation. All rights reserved. The FLEXlm host ID of this machine is "8044316e"
58

Chapter 5: Operations and Maintenance Utility lmnewlog Description Switches the report log file by moving the existing report log information to a new file, then starts a new report log with the original report log file name. If you rotate report logs with lmnewlog instead of lmswitchr, you do not have to change the file name in the REPORTLOG line of the Altair license manager's options file. Allows direct control over FLEXnet license path settings. It is used to add to override, or to get the current license path settings. Allows you to remove a single user's license for a specified feature. If the application is active, it rechecks out the license shortly after it is freed by lmremove. Causes the license manager to reread the license file and start any new vendor daemons that are added. In addition, all currently running vendor daemons are signaled to reread the license file and their end-user options files for changes in feature licensing information or option settings. Helps you monitor the status of all network licensing activities, including: Daemons that are running License files Users of individual features Users of features served by a specific vendor daemon Switches the debug log file written by altair_lm by closing the existing debug log and starting a new debug log with a new file name. It also starts a new debug log file written by altair_lm if one does not already exist. Switches the report log file written by closing the existing report log and starting a new report log with a new file name. It also starts a new report log file if one does not already exist. Reports the FLEXnet version of a library or binary file.
lmpath
lmremove
lmreread
lmstat
lmswitch
lmswitchr
lmver
5.2b FLEXnet Publisher Options File

The options file allows the license administrator to control various operating parameters of FLEXnet. Users can be identified by their user name, host name, display, or IP address. Specifically, the license administrator can: Allow the use of features Deny the use of features Reserve licenses Control the amount of information logged about license usage Enable a report log file

Chapter 5: Operations and Maintenance Options files allow you, as the license administrator, to be as secure or open with licenses as you like.
Creating an options file

Use any text editor and the appropriate options (see the following List of options) to create the options file. Each line of the file controls one option and is limited to 2048 characters. The \ character is a continuation character in options file lines. You can include comments in your options file by starting each comment line with the pound sign #. Everything in an options file is case sensitive. Be sure that user names and feature names, for example, are entered correctly. See Appendix G for the syntax for each option.
Using the options file

You can locate the options file anywhere; however, it is recommended to place the options file in the same directory as the license file. You then have two choices to make it active. Add the path to the options file in the license file as the fourth field on the DAEMON line. For example: VENDOR altair_lm /altair70/altair/security/bin/HPUX \ /altair70/altair/security/altair_lm.opt Enables the vendor daemon, altair_lm, to look at the specified options file. Name the file altair_lm.opt, place it in the same directory as the license used by lmgrd, and it will automatically be used at server startup.
List of options
Following is the list of available options. See Appendix G for the syntax for the option you wish to use. Option Keyword BORROW_LOWWATER DEBUGLOG EXCLUDE EXCLUDE_BORROW EXCLUDEALL FQDN matching GROUP Description Sets the number of BORROW licenses that cannot not be borrowed. Specifies a location for the debug log output from altair_lm. Denies access to feature for a user or pre-defined group of users. Denies a user the ability to borrow licenses. Denies access to all features for a user or pre-defined group of users. Sets the level of host name matching. Defines a group of users for use in INCLUDE, INCLUDEALL, EXCLUDE, EXCLUDEALL, and RESERVE option lines.
60

Chapter 5: Operations and Maintenance GROUPCASEINSENSITIVE The values are OFF or ON. If set to ON, user names and host names specified with the options file GROUP and HOST_GROUP keywords, respectively, are treated as case insensitive. GROUPCASEINSENSITIVE is OFF by default; user names and host names are treated as case sensitive. Defines a group of hosts for use in INCLUDE, INCLUDEALL, EXCLUDE, EXCLUDEALL, and RESERVE option lines. Multiple HOST_GROUP lines add all of the specified hosts into the group. Allows a user or a pre-defined group of users to access a feature. Allows a user to borrow licenses. Allows a user or a pre-defined group of users, etc., to access all features served by altair_lm. Anyone not in an INCLUDEALL statement is not allowed to use these features. Limits usage of a particular feature for a group or user. Changes the maximum borrow period for a specified feature. Limits OVERDRAFT license below the OVERDRAFT allowed by the license file. Suppresses logging selected type of event in the debug log file. Specifis the report log file for altair_lm, which is used by SAMreport. It is recommended preceding the report_log_path with a + character to append logging entries, otherwise the file is overwritten each time altair_lm is started. On Windows, path names, which include spaces, have to be enclosed in double quotes. SAMreport, a separate product available from Macrovision, is used to process FLEXlm report log files. SAMreport processes only report log files, not debug log files. Reserves licenses for a specific user. Any licenses reserved for a user are dedicated to that user. Even when that user is not actively using the license, it is unavailable to other users. However, a RESERVEd license does not cause usage to be reported by SAMreport if the license is not actually in use.
HOST_GROUP
INCLUDE INCLUDE_BORROW INCLUDEALL
MAX MAX_BORROW_HOURS MAX_OVERDRAFT NOLOG REPORTLOG
RESERVE
How the vendor daemon uses the options file

When altair_lm (the vendor daemon) is started by lmgrd, it reads its options file. There can only be one options file per vendor daemon and each vendor daemon needs its own options file. For changes in an options file to take effect, the vendor daemon must reread its options file. lmreread causes the vendor daemon to re-read its options file.
Rules of precedence in options files

Before you can use options to utilize licenses effectively you must understand the options file

Chapter 5: Operations and Maintenance precedence. INCLUDE and EXCLUDE statements can be combined in the same options file and control access to the same features. When doing so, keep the following in mind: 1. If there is only an EXCLUDE list, everyone who is not on the list will be allowed to use the feature. 2. If there is only an INCLUDE list, only those users on the list will be allowed to use the feature. 3. If neither list exists, everyone is allowed to use the feature. 4. The EXCLUDE list is checked before the INCLUDE list; someone who is on both lists will not be allowed to use the feature. Once you create an INCLUDE or EXCLUDE list, everyone else is implicitly outside the group. This feature allows you, as an administrator, the ability to control licenses without having to explicitly list each user that you wish to allow or deny access to. In other words, there are two approaches; you can either: Give most users access and list only the exceptions Or Severely limit access and list only the those users that have access privileges
Options file examples

The following information gives some examples of options files intended to illustrate ways to effectively control access to your licenses. Simple options file example RESERVE 1 compile USER robert RESERVE 3 compile HOST mainline EXCLUDE compile USER lori NOLOG QUEUED This options file would: Reserve one license for the feature compile for the user robert. Reserve three licenses for the feature compile for anyone on the system with the host name mainline. Prevent the user lori from using the compile feature on any node on the network. Cause QUEUED messages to be omitted from the debug log file. The sum total of the licenses reserved must be less than or equal to the number of licenses specified in the FEATURE line. In the example shown, there must be a minimum of four licenses on the compile FEATURE line. If fewer licenses are available, only the first set of reservations (up to the license limit) is used. If this data were in file /a/b/sampled/licenses/sampled.opt, then you would modify the license file DAEMON line as follows: DAEMON sampled /etc/sampled /a/b/sampled/licenses/sampled.opt
Limiting access for multiple users

Each INCLUDE, INCLUDEALL, EXCLUDE, EXCLUDEALL, MAX, and RESERVE line must have a single user name (or group) listed. To affect more than one user name, create a GROUP. For example, to exclude bob, howard, and james from using the feature called toothbrush, create the following options file: EXCLUDE toothbrush USER bob EXCLUDE toothbrush USER howard EXCLUDE toothbrush USER james However, there is an easier way. Create a GROUP and exclude the list of users from using the feature. Like the previous example, the following options file would exclude bob, howard, and 62 Altair License Management System 9.1 Installation Guide 9.1
Chapter 5: Operations and Maintenance james from using the feature called toothbrush: # First define the group "Hackers" GROUP Hackers bob howard james # Then exclude the group EXCLUDE toothbrush GROUP Hackers Now when you want to allow or deny access to any feature to that group, you have an alias list to make it simple. You can use HOST_GROUP to allow, deny, or reserve licenses for multiple hosts. For example, to exclude all users logged in on the hosts fred and barney from using a feature called f1, add these lines to your options file: HOST_GROUP writers fred barney EXCLUDE f1 HOST_GROUP writers Note See Appendix G, GROUP, and HOST_GROUP, for more information about defining groups.
EXCLUDE example
#First Define the group "painters" GROUP painters picasso mondrian klee EXCLUDE spell GROUP painters EXCLUDE spell USER bob EXCLUDE spell INTERNET 123.123.123.* This options file would: Prevent the users picasso, mondrian, and klee from using the feature spell on any machine on the network. Prevent the user bob from using the feature spell on any machine on the network. Prevent any user logged into a host with an IP address in the range 123.123.123.0 through 123.123.123.255 from using the feature spell. Allow any other user, as long as they are not on the excluded IP addresses, and they are not a member of the painters GROUP, and they are not bob, to use feature spell (by implication). Note that bob could have been added to the group painters. However, painters might be used for some other purpose in the future so the license administrator chose to handle bob as a special case here. In this case, the two EXCLUDE statements concatenate to create a list of four users. INCLUDE example INCLUDE paint USER picasso INCLUDE paint USER mondrian INCLUDE paint HOST bigbrush This options file would: Allow the user picasso to use the feature paint on any machine on the network. Allow the user mondrian to use the feature paint on any machine on the network. Allow any user, as long as they are on the host bigbrush, to use feature paint. Deny access to the feature paint to anyone except picasso, mondrian, or anyone from the host bigbrush (by implication).

5.3 Multiple FLEXnet Publisher Processes

When more than one FLEXnet Publisher process runs on the same server: 1. It may be necessary to change the port number on the SERVER line as only one process can bind to a given port. See Appendix C, SERVER line section for the location of the port number. 2. If the server is a Windows server, then also set a new Service Name on the Configure Services tab accessible from lmtools.exe. See Chapter 3, Installing HyperWorks on Windows. 3. If you need more information on managing licenses from multiple vendors using FLEXnet, refer to Appendix H.
5.4 Bringing Down a FLEXnet Publisher Process

5.4a On UNIX
1. Go to the license server machine. 2. At the UNIX prompt, enter the following: ps -ef |grep lmgrd The "|" is the pipe sign. The lmgrd process id is returned. 3. Terminate the lmgrd process by typing the following at the UNIX command prompt: kill <lmgrd process id> 4. At the UNIX prompt, enter the following: ps -ef |grep altair_lm. This returns the altair_lm process. 5. Terminate the altair_lm process by entering the following at the UNIX command prompt: kill <altair_lm process id>
5.4b
On Windows
1. Execute <install_location>/security/lmtools.exe. 2. Click the Service/License File tab. 3. Click the Configuration using Services option to activate it. 4. Click the Start/Stop/Reread tab. 5. Click Stop Server. 6. Click File. 7. Click Exit to close LMTOOLS.
64

5.5 Setting up Server for Automatic Start of the License Manager upon Reboot (Optional)
If you want the license manager process to come up automatically on reboot and you did not install as root (super user), follow the instructions specific to the operating system you are using. For UNIX: Run the script <install_location>/altair/security/install_altairlm (written to disk during the license server installation). You must run this script as root on the machine where the license manager process will run.
If using Solaris/HP-UX Itanium machines, please take note of the following:

Vendor daemon not starting (on Solaris only) The default Solaris TCP port delay may cause problems when restarting an Altair license server. If you have a problem restarting license servers on Solaris, a root user can reset the port delay to 2.4 seconds (2400 milliseconds). As part of the installation script, Altair asks if you wish to reset the port delay in the license manager auto startup script to 2.4sec. However, if you do not wish to use Altair's auto startup script for the license manager, we recommend this be done in a boot script since the port delay is reset every time the machine reboots. For example: Solaris 2.8+: /usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 2400 Vendor daemon that dies after startup on HP-UX/HP-UX Itanium and Solaris The license manager cannot handle any more concurrent clients due to a lack of file descriptors. You will receive the following types of messages in the lmgrd debug log: (altair_lm) This server can handle no more concurrent clients (altair_lm) since it is out of file descriptors. or (altair_lm) Vendor daemon can't talk to lmgrd (Cannot read data from license server (-16,287:22"Invalid argument")) (lmgrd) Vendor daemon died with status 50 To solve this problem, increase the number of file descriptors available for Altair lmgrd process by setting the file descriptors to 1024. For example: Starting lmgrd from a /bin/sh script Change the script to look like: #!/bin/sh ulimit -H -n 1024 lmgrd [...] where [...] is the lmgrd arguments.

Chapter 5: Operations and Maintenance For Windows: 1. Log onto the machine as Administrator. 2. Execute <install_location>/security/lmtools.exe. 3. Click the Service/License File tab. 4. Click the Configuration using Services option. 5. Click the Configure Services tab. 6. Select the service name for the HyperWorks FLEXnet license service. 7. Click the options Use Services and Start Server at Power Up to activate them. 8. Click File. 9. Click Exit. A message is displayed stating "Would you like to save the settings for the service: <Service Name>". 10. Click Yes. LMTOOLS closes.
5.6 How to Borrow Licenses

Starting with HyperWorks 8.0, server licenses can be borrowed by laptops that are intermittently connected to the network. When the licenses are borrowed, the client machine can be disconnected from the network, and will be able to run the applications, for as long as the borrowed license is valid. When the licenses are borrowed from the license server, the licenses remain checked out until the borrowed period expires.
5.6a Prerequisites to licensing borrowing

1. The license server (lmgrd/altair_lm) should have a minimum FLEXnet version of 10.8. You can determine the version of lmgrd/altair_lm by running the license manager utility lmver 2. All of the feature lines in the server license should have the keyword BORROW, as in the example below.
66

Chapter 5: Operations and Maintenance 3. The applications for which licenses are being borrowed should be HyperWorks 8.0 and above only. 4. Licenses can only be borrowed for applications that do not stack licenses. 5. HyperWorks 8.0 applications need to be installed on machines that will borrow licenses.
5.6b Procedure for borrowing licenses:

1. Licenses are borrowed by setting the LM_BORROW environment variable. Use one of the following ways to set LM_BORROW on a client machine that needs to borrow licenses: a. Use the lmtools utility on WINDOWS : Click the Borrowing tab in lmtools.exe Enter the date/time period for the borrowed license. Set Borrow Expiration.
b. Use the command line utility lmutil lmborrow: Type lmutil lmborrow altair_lm <end date> <end time>
c. Set LM_BORROW environment directly use the following syntax: <today>:altair_lm:enddate[:time] where today: Todays date is in the format dd-mm-yyyy. Any checkouts done on this date create local borrow information. If a check out is done on a date other than this date, no borrowing information is created. Date the borrowed license is to be returned in dd-mm-yyyy format. Optional time is specified in 24-hour format (hh:mm) in the FLEX enabled applications local time. If time is unspecified, the checkout lasts until the end of
enddate: time

Chapter 5: Operations and Maintenance the given date. For example: set LM_BORROW=11-aug-2006:altair_lm_13-aug-2006:13:00 The above sets the licenses to be borrowed on 11-aug-2006. The borrowed licenses will be returned to the central license server on 13-aug-2006 at 1 PM. 2. Running the application: Run all the applications that the licenses need to be borrowed for. For example, if licenses for HyperMesh and MotionView need to be borrowed, open the applications HyperMesh and MotionView. Note: in the above example, even though 21 licenses will be borrowed from the license server, HyperGraph cannot be run on the client with a borrowed license, as the application was not explicitly borrowed. 3. Clear the borrow period: Once all the licenses have been borrowed prevent licenses for any additional features from being borrowed by running lmborrow clear. This clears the LM_BORROW setting in the registry (Windows) or $HOME/.flexlmborrow (UNIX). Lmborrow clear does not clear the local information about licenses that are already borrowed.
5.6c Checking the borrow status:

To display information about borrowed features, issue the following command from <installed location>/security/bin/<platform> on the client machine from which the licenses are borrowed. lmutil lmborrow status The client machine does not have to be connected to the network to determine the status.
5.6d Returning a borrowed license early:

To return a borrowed license before the borrow period expires, first reconnect the borrowing system back to the network and then, from the same machine that initialed the borrowing, issue the command: Lmutil lmborrow return [-c licnese_file_list] feature. For example, to return a HyperMesh license early, the following will need to be done: Lmutil lmborrow return c 7788@server1 feature HyperWorks Lmutil lmborrow return c 7788@server1 feature GlobalLicAM Lmutil lmborrow return c 7788@server1 feature HM3D
68

5.7 Environment Variables

The following environment variables can be set on UNIX and Windows to control certain features within FLEXlm. Variable ALM_ERROR_TRACKING Description This environment variable is useful for debugging license checkout failures. When set to an integer greater than 0, all debug messages from the security library will be printed to stdout. This variable only needs to be set on client machines. When set to an integer greater than 0, this environment variable represents the number of days the license expiration warning will be displayed, before the license expires. This variable only needs to be set on client machines When set to an integer greater than 0, the license expiration warning will NOT be displayed. Warning displays within 30 days of license expiring. This variable only needs to be set on client machines Sets the path to the license file. Multiple license files can be combined using ':' to separate the files on UNIX and ';' on Windows. Macrovision provides this environment variable. This variable only needs to be set on client machines The fully qualified name of the Altair log file. This needs to be set on the license server(s), before starting the license server machine(s). By default, the log file will be called altairhw_<date/time>.csv and will be created in the same directory as the license server. Sets the time interval in minutes when the usage log will be updated by the license server. By default, the time interval is set to 60 minutes. The minimum time interval is 15 minutes and the maximum time interval is 30 days. This environment variable needs to be set on the license server machine(s), before starting the license server(s). When set, all logging will be disabled. This needs to be set on the license server machine(s), before starting the license server(s). When set to an integer between 1 and 3, this provides diagnostic information when a checkout fails. On UNIX, the diagnostic message is sent to stderr. On Windows, the diagnostic message is in a file flex<pid>.log in the current working directory. When set, this environment variable provides debug information about all environment variables that are set by scripts that launch this application. This environment variable also turns on ALM_ERROR_TRACKING. This variable only needs to be set on client machines.
ALM_EXPIRE_DAY_WARNING
ALM_NO_EXPIRE_WARNING
ALTAIR_LM_LICENSE_FILE
ALTAIR_LOGFILE
ALTAIR_LOGINTERVAL
ALTAIR_NOLOG
FLEXLM_DIAGNOSTICS
HW_DEBUG_INFO (UNIX only)

Chapter 5: Operations and Maintenance Variable HW_POOL_SECURITY (UNIX only) LM_BORROW LM_LICENSE_FILE Description When set, this environment variable levels HyperWorks units across three-server license pools. Used for initiating license borrowing and setting the borrow period. Sets the path to the license file. Multiple license files can be combined using ':' on UNIX and ';' on Windows. This variable can be set on client and server machines. All applications will first use the license files/servers set by ALTAIR_LM_LICENSE_FILE before attempting checkouts on license files/servers set by LM_LICENSE_FILE. Used in the SAMreport for usage logging. The value set should be 30 characters or less. Used to set the highest file descriptor value, above which the license server will not access. Improves FLEXnet license server system performance when processing license requests. Set to 1 to enable performance enhancements. Use with caution: when enabled, it may cause an increase in network traffic.
LM_PROJECT LM_SERVER_HIGHEST_FD TCP_NODELAY
Registry Setting (Windows only) On Windows, the FLEXlm registry is at HKEY_LOCAL_MACHINE->Software->FLEXllm License Manager ->ALTAIR_LM_LICENSE_FILE
5.8 Troubleshooting and Maintenance

This section presents solutions to some installation problems you may experience. If your concerns are not covered in this section, contact Altair Support.
Troubleshooting
a. Why does the vendor daemon altair_lm die soon after the FLEXnet license server is started on UNIX?
This may be due to a port number already in use or an existing lockaltair_lm file. Sometimes when the lmgrd goes down or is killed the port status remains active or in use because the operating system does not release the port in a timely manner. If the port number is already in use, then either wait for the port to free or go to the installation instructions, license file section for instructions to change the port number in the SERVER line of the
70

Chapter 5: Operations and Maintenance license file to eliminate conflicts. This lockaltair_lm lock file exists when the vendor daemon is running. The file is removed when the vendor daemon is shut down. Sometimes, if the daemon is shut down by a fatal error, the lockaltair_lm file still exists. This file cannot exist before the daemon is restarted. Remove the lockaltair_lm file and restart FLEXnet as follows: 1. Go to the license server machine. 2. At the UNIX prompt, enter the following: ps -ef|grep lmgrd The "|" is the pipe sign. The lmgrd process is returned. 3. Kill all Altair HyperWorks lmgrd processes by typing the following at the UNIX command prompt: kill <lmgrd process ids> 4. At the UNIX prompt, enter the following: ps -ef |grep altair_lm. The altair_lm process is returned. 5. Kill all Altair HyperWorks altair_lm processes by entering the following at the UNIX command prompt: kill <altair_lm process ids> 6. Look for a lockaltair_lm file in the following directories: /tmp/ /etc/ /var/ /usr/ /tmp/usr 7. Delete the lockaltair_lm file. 8. Restart FLEXnet. See the instructions in Chapter 2.
b. HyperWorks and the license seem to be installed correctly, but the lmgrd script does not start the FLEXnet license server. What else can I do to try to start FLEXnet?
Try starting the FLEXnet license server manually. Prior to this, kill any existing HyperWorks lmgrd or altair_lm processes. See Bringing down a FLEXnetservice in Chapter 4, Section 5. Also, make sure that a lockaltair_lm file does not exist. See the previous section.
c. What if I do not have a license file?

If you do not have a license file, you will need to contact your local Altair support office and supply the hostid for any server machines in the installation and/or any local/stand-alone machines. To obtain the machines hostid, enter the following command at the UNIX prompt: <install_location>/altair/scripts/lmhostid When you receive the license file via e-mail, continue the license activation process.

d. Do I need a new license file if I have installed HyperWorks in the past?

You do need a new license file if the HyperWorks application release you are installing is a major release. See Chapter 4, Section 1 for more information.
Maintenance
a. License File Maintenance
Whenever a major release of HyperWorks software occurs, a new license file needs to be obtained from Altair Engineering. Major releases follow the format #.0 where # represents the version number. For example: 8.0 is a major release. Periodically, Altair will release what is called a service pack. These releases are upgrades of the software and, in general, do not require a new license file. In general, the license is backward compatible in that the license for the newest version of HyperWorks will run the previous versions applications. The license for the previous version of HyperWorks applications is incompatible with the newest version of HyperWorks applications. If you install the newest version of the server license, you will also need to install the latest version of the FLEXlm license manager.
b. Replacing existing server license with a new one

When replacing an existing server license with a new one, the FLEXlm license server process does not need to be shut down. UNIX 1. Go to the license server machine. 2. Replace the existing license in the altair_lic.dat file with the new one. The altair_lic.dat file is located in the <install_location>/altair/security directory. 3. Edit the new altair_lic.dat file by replacing hostname in the SERVER line with the server machine's IP address. For redundant server licenses, do this for each SERVER line in the license file. 4. Enter the following at the UNIX command prompt: <install_location>/altair/scripts/lmreread The license daemon rereads the license file altair_lic.dat. If the reread is successful, the message "lmreread successful" is returned in the UNIX window. 5. If the altair_lic.dat file resides on client machines, replace it with the updated altair_lic.dat file that is on the license server machine. Windows 1. Go to the license server machine. 2. Replace the existing license in the altair_lic.dat file with the new one. The altair_lic.dat file is located in the <install_location>/security directory. FLEXlm is case and space sensitive. The license in the altair_lic.dat file should look exactly as it does in the e-mail message.
72

Chapter 5: Operations and Maintenance 3. Edit the new altair_lic.dat file by replacing hostname in the SERVER line with the server machine's IP address. For redundant server licenses, do this for each SERVER line in the license file. 4. Execute <install_location>/security/lmtools.exe or select Start Menu/Programs/Altair Licensing 9.0/FLEXlm Utilities.
5. In the LMTOOLS dialog, click the Start/Stop/Reread tab. 6. Click the Reread License File button. 7. The license daemon rereads the license file altair_lic.dat. If the reread is successful, a message at the bottom of the dialog box states "Reread Server License File Completed." If the reread is unsuccessful, shut down the server(s) and restart them. If the restart fails, call Altair Support with the error message. 8. Click File. 9. Click Exit to close LMTOOLS. If the altair_lic.dat file resides on client machines, replace it with the server machine's updated altair_lic.dat file.
c. Determine who is using an Altair application at a given time

On UNIX To determine who is using HyperWorks applications at a given time, type the following at the UNIX command prompt: <install_location>/altair/scripts/lmstat -A On Windows To determine who is using HyperWorks applications at a given time: 1. Execute <install_location>/security/lmtools.exe. 2. Click the Service/License File tab. 3. Click the Configuration using Services option to make it active. 4. Click the Server Status tab. 5. Click Perform Status Enquiry. 6. Use the scroll bar to view the information in the window. Active users are reported just below the "Users of <application name>" line. 7. Click File and then click Exit to close LMTOOLS.

Chapter 6: Altair GridWorks Licensing

Altair License Management System uses two types of licensing GridWorks Unit license and Feature licenses. GridWorks Units licenses allow any of the GridWorks enabled applications to run, so long as there are sufficient GridWorks licenses available. Feature licensing allows a particular Altair application to run, as long as the feature is available in the license file. A more complete description of each licensing type follows. For details on the format of the license file see Appendix C, License File Format. This chapter explains how GridWorks Unit licensing works, including the units drawn by applications, the concept of leveling and stacking, and the global licensing.
6.1 GridWorks Unit Licensing

Starting in 9.0, Altair licensing system used by most of Altair products has been switched from using HyperWorks units to a new licensing system called GridWorks Units (GWU). GridWorks Units work very much the same as HyperWorks units with the one main difference being that one HyperWorks Unit is equivalent to 100 GridWorks Units. The splitting of HyperWorks units into GridWorks units allows for the pricing of less expensive Altair products within the same unit-based licensing system. The GridWorks licensing system has been designed to allow HyperWorks Partner Products (selected third party products) to be licensed via GridWorks units. As part of the license agreements to enable partner software, product usage data needs to be sent to Altair. The Altair GridWorks license package is separate from the HyperWorks application package and contains both the FLEXnet license manager and usage report tools.
GridWorks Units licensing has these characteristics. Uses a server license The licensing client and server require at least one of the following global license features pertinent to its time zone. GlobalGridWorksAM allows license usage in the American Global Zone (AM). GlobalGridWorksEU allows license usage in the European Global Zone (EU). GlobalGridWorksAP allows license usage in the Asia Pacific Global Zone (AP). Specifies the number of GridWorks units purchased. Allows simultaneous sessions of an application for the same display, host, and user with a single license for most applications. Serves multiple Altair Products as long as there are sufficient units available in the license pool. Depending on the products, the GridWorks units are leveled, rather than stacked, for the

75
Chapter 6: Altair GridWorks Licensing same user, host, display combination. The quantity of GridWorks units a customer purchases forms the units pool. The license server keeps tracking the total quantity of units the customer purchased and how many of those units are currently being used by each user. When a user requests the initial application, the required units for that application are pulled from this pool. When too few units remain, additional start requests are denied. Units used follow one of two concepts-leveling or stacking. When an application levels units, a single user/host/display (UHD) combination can open multiple sessions of the same application, and applications without consuming any extra licenses, as long as the number of licenses required is less than or equal to what has already been checked out by this user/host/display. So, for example, if HyperMesh is launched by a specific user/host/display combination, the same user/host/display can run the applications like HyperView, MotionView, HyperGraph, HyperGraph 3D, and any other HyperWorks applications that uses 2100 GridWorks units or fewer. No additional licenses are pulled in this case. If the same user/host/display now launched HyperStudy, an additional 1700 units will be taken from the license pool instead of 3800 units, as 2100 units have already been checked out. Most HyperWorks applications level units. Some HyperWorks applications stack licenses, rather than level them. When an application stacks units, the full amount of units will be checked out from the license pool. Additional licenses are needed in order to run concurrent sessions of the application. So, for example, if a user/host/display launches HyperMesh and one session DataManager, 2500 (2100+400) units will be used.
6.2 GridWorks Units Used by Application

This table shows the number of GridWorks units each application draws. For a particular display/host/user, most applications level units. This means with the same user/host/display combinations you can launch multiple sessions of the same application, and other applications that use the same number or fewer licenses as the application first checked out. For those applications that are stacked, if units are available, permission to launch is granted.
Feature Batch Mesher Data Manager DistributedLoadMapper HyperCrash FEModel HarnessLinkBuilder HarnessLinkConnCatalog HarnessLinkDatabase HarnessLinkViewer 76
Units 2100 400 100 2100 2100 6000 2100 2100 2500
Notes Stacked always Stacked always

HarnessLinkWebEntry HyperForm3D HyperGraph HyperGraph3D HyperMesh3D HyperStudy HyperStudyDSS HyperView HyperViewPlayer HyperXtrudeFEA HyperXtrudePre MediaView MotionSolve* MotionView OptiStruct* OptiStructAdvA** OptiStructFEA* OptiStructMulti ** ProcessManagerApp ProcessStudio
200 2100 600 2100 2100 3800 3800 2100 100 5000 1000 600 3800 2100 5000 3800 2500 6000 1000 5000 The unit count for RADIOSS depends on the number of CPUs used for a job. The unit count for RADIOSS depends on the number of CPUs used for a job. UNIX only
RadiossA
2500***
RadiossA Templex Text PBS Professional
3800*** 600 600 3
3 GWUs per requested/running CPU
* Using HyperWorks Solver licensing stacking rules. ** OptiStructMulti feature is checked out when an "optimization" model is submitted with nproc=x or cpu=x;
x>1. This feature follows both the rules of stacking and the rules for multiple processors. OptiStructMulti


license feature will be checked out on systems where: a) the executable is multi-processor enabled; and b) it gives reasonable performance improvement when running in multi-processor mode.
*** The number of GridWorks Units required to run a RADIOSS job is dependent on the machine CPU
numbers the RADIOSS job uses.
6.3 GridWorks Leveling and Licensing Pools

6.3.a Using License Pools
A license pool is a collection of licenses. A single license pool can be constructed for use with either a redundant server license (three servers) or single-server license. You can create multiple license pools by dividing your total licenses into two or more groups. For example: If you had a total of 6300 GridWorks Units, you could create two license pools, one with 3500 licenses and the other with 2800 licenses. Multiple license pools provide the ability to load balance the GridWorks Units, allow some units to be available if a license server(s) fail, and obtain licenses from another license resource when the primary one reaches its maximum limit. To use multiple license pool, set the environment variable ALTAIR_LM_LICENSE_FILE to point to the license servers. The different license files/port@host settings in a license pool should be separated using ';' on Windows and ':' on UNIX. Licenses can be leveled in most cases on UNIX clients using three-server redundant licenses if the environment variable HW_POOL_SECURITY is set.
6.3.b How leveling works with multiple license pools

Since each license pool functions independently of any other license pool, a license pool cannot communicate with any other license pool (this limitation is due to the inherent functionality of FLEXlm). This means, while leveling occurs in a single license pool for the same user, host, and display, leveling is not possible between multiple license pools. Instead, license usage is stacked. For example: User1 checks out HyperMesh from the first license pool. This draws 2100 GridWorks Units (GWU). Later, User1, on the same host and display, wishes to run OptiStruct concurrently with HyperMesh. Since OptiStruct uses 5000 GWUs, the first license pool needs 2900 additional GWUs to be available to launch OptiStruct (leveling). However, if the first license pool has only ten licenses available, User1s request would be directed to the second license pool. Because the two license pools operate independently, User1 would need 5000 GWUs from the second license pool to launch OptiStruct and User1 would be using 7100 total GWUs (stacked).
6.4 Global Licensing

In HyperWorks 9.0, the global license scheme is defined based on the following global zones. The client and server will require the global license feature pertinent to its time zone. The definition of the three global zones and the mechanism of global license is described, following:
78

6.4.a Global Zones Definition:

1. American Global Zone (AM): This global zone covers from Hawaii to Iceland, including North and South America. GMT-12 < Local time < GMT 2. European Global Zone (EU): This global zone covers Europe, the Middle East and Africa. GMT <= Local time < GMT + 4 3. Asia Pacific Global Zone (AP): This global zone covers Asia Pacific (India, China) and Australia. GMT +4 <= Local time <= GMT + 12
6.4.b Global License Features and License Scheme:

The existing GlobalLicAM, GlobalLicEU, and GlobalLicAP that used in HyperWorks 8.0 are replaced replaced by the following features. All applications, including the license server, will check out the feature that is pertinent to the global zone where application is running. 1. GlobalGridWorksAM: Allows license usage in the American Global Zone (AM). 2. GlobalGridWorksEU: Allows license usage in the European Global Zone (EU). 3. GlobalGridWorksAP: Allows license usage in the Asia Pacific Global Zone (AP). With the new global license scheme, every application, including the license server, will need the global license feature specific to its time zone. A company can designate one or more servers to be Global license servers, servicing requests from clients in global zones that are different from its own. Depending on the global license features available, the license server may be able to service clients in different global zones.

6.4.c Example of license file with Global License Features:
6.4.d Examples for the new global license scheme

1. Server and client spanning a single global zone
Server Location
Client Location
Features in License File
Global Zone AM Hawaii - Iceland
Global Zone AMHawaii - Iceland
GlobalGridWorksAM
Global Zone EU Europe Africa
GlobalGridWoksEU
Global Zone AP Asia - Australia
GlobalGridWorksAP
2. Server and client spanning two global zones
80

Server Location
Client Location
GlobalGridWorksAM GlobalGridWorksEU
GlobalGridWorksEU GlobalGridWroksAP
GlobalGridWorksAM GlobalGridWorksAP
3. Server and client spanning three global zones
Server Location
Client Location
Global Zone AM Global Zone AM
GlobalGridWorksAM GlobalGridWorksEU
Hawaii - Iceland GlobalGridWorksAP

Appendix A: Glossary
Term AAS ALS Client Daemon
Definition Altair Application Server, references the application server that is deployed to accept usage logs from the customers. Altair License Server, the FLEXlm license server distributed by Altair. An application program requesting or receiving a license. A background process that usually performs some function such as license verification or document printing. On Windows they are known as Services. A piece of hardware that looks like a printer plug with pins on one side and holes on the other or a USB plug. It is mounted on the printer port (or USB port) and used as part of the licensing activity on Windows. It accepts standard printer plugs so it may be daisychained with other locks and printer cables. Also known as a hardware key. A license to operate a specific product or products. Available as a node-locked or server license. The ID of a hardware key. See section 3.2 for instructions to obtain this value which is required for Windows licenses. Software from Macrovision that manages licensing. For Altair software products, like HyperWorks, it uses the license to authorize the use of applications. New version of software from Macrovision that manages licensing. For Altair software products such as HyperWorks, it uses the license to authorize the use of applications. A license for concurrent (network) users. Allows users to share licenses across a network. The new license system that replaces HyperWorks Units license. It works very similar to the HyperWorks Units system. Depending upon the number of purchased units (licenses), one or more applications in the suite may be activated simultaneously by one or more users. The license file contains a SERVER line, DAEMON line, and one or more FEATURE lines in the license designating Altair applications. One HyperWorks Unit is equivalent to 100 GridWorks Units
Dongle
Feature license Flexid FLEXlm
FLEXnet
Floating license GridWorks Units license
82

Appendix A: Glossary Term Hardware key Definition A piece of hardware that looks like a printer plug with pins on one side and holes on the other. It is mounted on the printer port and used as part of the licensing activity on Windows. It accepts standard printer plugs so it may be daisy-chained with other locks and printer cables. Also known as a dongle. Depending upon the number of purchased units (licenses), one or more applications in the suite may be activated simultaneously by one or more users. The license file contains a SERVER line, DAEMON line, and one or more FEATURE lines in the license designating HyperWorks applications. HyperWorks Units license system is used in HyperWorks 8.0 and older version. See Hardware key. Allows a user to launch from the same host and display multiple GridWorks applications and consume only the number of units (licenses) required by the application with the highest draw. For example, a user can run HyperMesh at 2100 GridWorks units and as many other applications requiring 2100 or fewer units as desired without additional units being charged. The authorization to use Altair products such as HyperWorks and PBS Professional. Two types of licenses are available with Altair products, server and node locked (for single machines only). See each license type for more information. A file distributed with the software that enables/restricts usage of specified products. Contains encrypted code using the hostid, Ethernet (MAC) address, or flexid to identify the users machine as authorized to access applications in HyperWorks. See license file. An application that uses the daemons lmgrd and vendor to handle license verification. A physical device on which the license server manager is installed. Multiple servers across a wide network with the capability of granting licenses. See section 4.10 Server configurations for more details. The license manager daemon that directs license requests to the specific vendor daemon. The name of the system that has FLEXlm installed on it. See section 2.2 for instructions on obtaining this value which is required for UNIX license. A version of HyperWorks with a number format of #.0 where # represents the version (8.0, for example). A new license is required for a major release. The license that applies to one machine only. Depending upon the type of license purchased, there may be one to many FEATURE lines in the license. At least three servers configured to serve HyperWorks software and/or licenses. Two configurations are possible: three-server or license server list.
HyperWorks Units license
Key Leveling
License
License file
License key License manager License server License server list lmgrd lmhostid
Major release
Node-locked license
Redundant server

Appendix A: Glossary Term Server license Server node Services Definition A license allowing multiple users to be served permissions to access HyperWorks applications. The first word in the license is SERVER. Computer system running the license server software. In Windows, Daemons are referred to as Services. A background process that usually performs some function such as license verification or document printing. In certain situations, HyperWorks Units from one product are combined with the units from another product. For example: HyperWeb requires 2 units stacked. If a user ran HyperMesh (21 units) concurrently with HyperWeb from the same host and display, the user would consume 23 units. Using three servers on the same sub-net to authorize licenses. Usage Monitoring Tool, the mechanism that will query the server and log license usage. Usage Reporting Tool, the mechanism that will send the logs back to Altair. Daemon/service/server that dispenses licenses.
Stacked
Three-server redundancy UMT URT Vendor daemon
84

Appendix B: Installation Structure

Below is the installation structure of Altair License Management System on Windows. The usage data are located in the security\urt_dist\alus\data\ directory by default.

85
Appendix C: License File Format

This appendix describes the differences between node-locked and server license files, the general format of each line that may appear in the license file, and modifiable fields. The license files are of two types: Network Node_locked License available to many machines on a network. This is usually called the server license. It requires an active FLEXlm license manager process. License is locked to an individual machine. There is no need to run the license manager for this type of license.
Look at the first line in your license file. If the first word is SERVER, the license is a server license; if the first three lines have SERVER as their first word, then it is a redundant server license. If the first word is FEATURE, it is a node-locked license (typically used for a stand-alone machine).
Node-locked License Example

The following example is a portion of a node-locked license with the major fields labeled. A node-locked license contains only FEATURE lines that allow the associate Altair applications to invoke. For a node-locked license, the hostid field appears in the FEATURE line instead of the SERVER line.

87
Server License Example

A GridWorks Unit license contains at least a server line, a VENDOR line, a FEATURE line contains GridWorks feature, a Geographic Feature (for example, the GlobalGridWorksAM), and the tracking feature lines for Altair applications. The following example shows the first few lines of a single server license with the major fields labeled. In a server license file, several fields can be modified. See the discussion below titled Fields you can modify.
Fields You Can Modify

On the SERVER line(s): Host name on the SERVER line(s). TCP/IP port numbers on the SERVER line(s). On the DAEMON line: Paths on the DAEMON/VENDOR line(s) (optional). Optional TCL/IP port numbers on VENDOR/DAEMON line(s) for firewall support. FEATURE and INCREMENT lines cannot be modified. Nothing else in the license file is modifiable, and should be entered exactly as supplied by Altair Engineering. All data in the license file is case and space sensitive, unless otherwise indicated. The following sections give more information about the lines in a license file and the modifiable fields.
88

SERVER Line
The SERVER line specifies the node name and hostid of the license server, and the TCP port number of the license manager daemon, lmgrd. You do not have the option of deleting a SERVER line from a license file since its hostid is used to create the encrypted license key on all FEATURE and INCREMENT lines. The following example shows the format of a SERVER line:
node name
Also known as the hostname. This field can be edited by the license administrator. It should be the string returned by the UNIX hostname or uname -n commands, or an IP address in the format of ###.###.###.###. IP address is recommended for sites where NIS or DNS have trouble resolving a host name or if a server has multiple network interfaces, thus having multiple host names. On UNIX, the string returned by the lmhostid command. For Windows, it is the FLEXid number on the hardware key (dongle) or the Ethernet (MAC) address. See the installation chapters on your specific platform for instructions to obtain this value. The customer cannot modify this field. TCP port number used by the FLEXlm license server process. Only one license server process can run on a port at one time. Modify this number only when your site has multiple license processes. If modified, we recommend the new number be greater than the original number. By default, the port number in license files issued by Altair Engineering is 7788.
hostid
port-number
VENDOR Line
The DAEMON line specifies the vendor daemon name and the optional path names for the vendor daemon executable and the options file. The format of the DAEMON line is shown in the example below with optional items appearing in brackets.
vendor daemon name daemon_path
The name of the vendor daemon used to serve some FEATURE(s) in the file. Not modifiable by the customer. The path name to the executable for this daemon. The UNIX default path name is <install_location>/altair/security/<FLEXlm version>/bin/<platform>/altair_lm. The Windows default path name is <drive>:\<install_location>\security\altair_lm.exe. You are free to install the daemon anywhere. However, if it resides in the default installation directory, you are not required to specify its path name on the DAEMON line.

Appendix C: License File Format options_file_path The fully qualified path name of the end-user specified options file for this daemon. An options file is not required. If a daemon_path is not specified and an options_file_path is needed, precede the options_file_path with the key word options=. See the options file (Appendix G) for more detail. This is the vendor daemon port. If a client is connecting to lmgrd/altair_lm through a firewall, a port number must be specified. By default, if the <port> number is not specified, it is chosen by the operating system at run time. If a <port> is specified, there may be a delay restarting altair_lm until all of the clients have closed their connection with altair_lm.
firewall_port
These three variables must to be added after the altair_lm in the following order: Vendor daemon path, option file path, firewall Port. If you only want to specify one or two paths, additional option= or port= needs to be added in front of the path. For example, VENDOR altair_lm options=C:\options\altair_lm.opt port=8800 VENDOR altair_lm options=C:\options\altair_lm.opt VENDOR altair_lm port=8800 An option file will be taken into account automatically without adding it to the license file if it is named altair_lm.opt and placed in the same directory as the Altair license file.
Tracking Feature Line

The Altair 9.0 license file for GridWorks license must contains the application tracking feature in order to launch the associate applications. For example, in order to run Altair RADIOSS, a GWRadiossA tracking feature must be listed in the license file as shown below:
Create a USE_SERVER license file

For a server license, you can simplify the license file located on the client machine by creating a USE_SERVER license file. The USE_SERVER line directs the application to use licenses on the license server. This modified license file will work even when the client machine has a different platform than
90

Appendix C: License File Format the server. 6. Copy the license file from the license server to a client machines file: <install_location>/altair/security/altair_lic.dat 7. Keep all SERVER lines and remove the remaining lines in the license file. 8. Append the line USE_SERVER and save the modified license file. Your edited license file will be similar to this example for single server license installations: SERVER 101.953.23.67 807d4688 7788 USE_SERVER Your edited license file will be similar to this example for three-server license installations: SERVER 101.953.23.23 807d6754 7788 SERVER 101.953.23.85 807d3574 7788 SERVER 101.953.23.98 807d9214 7788 USE_SERVER 9. Copy this modified file to all remaining client machines file: For UNIX: <install_location>/altair/security/altair_lic.dat For Windows: <install_location>\security\altair_lic.dat

Appendix D: FLEXlm Error Messages

This table contains a list of FLEXlm error codes (negative) and ALM_ERROR_CODES (positive) with an explanation for the code. Error code -1 Description/cause/workaround Cannot find license file. There is nothing specified in environment variable LM_LICENSE_FILE/ALTAIR_LM_LICENSE_FILE or the file specified in LM_LICENSE_FILE/ALTAIR_LM_LICENSE_FILE. Invalid license file syntax. This usually happens when the license file is empty. No server for this feature. The vendor daemon name specified in the FEATURE line does not match the vendor daemon name. All licenses are in use. The feature cannot be found in the license file. The SERVER line does not specify a TCP/IP port number, and the TCP license service does not exist in /etc/services. Cannot connect to the license server, as there is no socket connection. Invalid license key. This usually happens when a license file has been altered or corrupted. Invalid host. The hostid specified in the license file does not match the node on which the software is running. Feature has expired. Invalid license file syntax. Cannot connect to the license server. Invalid data returned from the license server. Invalid license file syntax. No SERVER license in the license file. Cannot connect to license server. The SERVER host name cannot be found in the network database. The lookup for the host name on the SERVER line in the license file failed. This often happens when NIS or DNS or the hosts file is incorrect. Workaround: Use IP address (123.456.789.123. for example) instead of host name. Cannot connect to the license server. The server has not yet been started or the wrong port@host or license file is being used, or the port or host name in the license file has been changed. Cannot connect to the license server. Cannot read data from license server.
-2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 -14
-15
-16

93
Appendix D: FLEXlm Error Message Error code -17 -18 Description/cause/workaround Cannot connect to the license server. Cannot write data to license server. License server does not support this feature. The feature has expired (on the server), or has not yet started, or the version is greater than the highest supported version. If the -license file has multiple lines with the same feature name, make sure that the line with the highest version number comes first in the license file. System error. Error in select system call. License file does not support this version. Cannot connect to the license server. License server is temporarily busy (new server connecting). altair_lm is in the process of establishing a quorum condition. New requests from clients are deferred during this period. This request should be retried. License server does not support this version of this feature. Request for more licenses than this feature supports. Cannot find Ethernet device. The license file cannot be read (errno == EPERM or EACCES). The feature is not enabled yet in the license file. No such attribute. Cannot communicate with the license server. Clock difference is too large between the client and the server. Cannot communicate with the license server. This is an internal license server error. The user/host/display has been excluded from this feature by an end user's vendor daemon options file. The user/host/display has NOT been included in this feature by an end user's vendor daemon options file. System error. Cannot locate dynamic memory. Feature was never checked out. Invalid parameter System error. Clock setting check not available in daemon. Cannot connect to the license server. altair_lm did not respond within timeout interval. System error. socket() call failed. This can occur when the UNIX OS runs out of system resources. The setsockopt() call has failed. This is likely due to an OS error. Cannot communicate with the license server due to poor networking communications. Server message checksum failure.
-19 -21 -23
-25 -26 -29 -30 -31 -32 -33 -34 -36 -38 -39 -40 -41 -42 -47 -52 -57 -58 -59 -60
94

Appendix D: FLEXlm Error Message Error code -61 Description/cause/workaround Cannot read license file data from server. This occurs when the license file, via LM_LICENSE_FILE is defined incorrectly. This only occurs in lmutil when LM_LICENSE_FILE is set to port@host or @host. System error. Network software (TCP/IP) not available. Some systems may have this problem, but the error will not be reported as LM_NONETWORK -system calls will simply fail. You are not a license administrator. Various functions, such as lc_remove() and lc_shutdown(), require the user to be a license administrator, depending on how lmgrd was started. lmremove request before the minimum lmremove interval (120 seconds). Invalid TZ environment variable. Attempt to read beyond end of license file path. An error occurred with the list of license files. Internal FLEXlm error - please report to Macrovision software. Invalid license file syntax. License server needs to be updated. FLEXlm version of the client is newer than the license server. USER_BASED license has no specified users -- see server log. When a feature has the USER_BASED attribute, this error occurs when there is no INCLUDE line in the end-user options file for this feature, or the number or users included exceeds the number authorized. License server does not support this request. The license server (lmgrd, altair_lm) has an older FLEXlm version than the client. The license server needs to be updated. Checkout exceeds MAX specified in the options file. System error. System clock has been set back. Invalid license file syntax: Future license file format or misspelling in license file. Checkout failure due to two possible causes: 1) The feature is removed during lmreread, but the client is reading an old copy of the license file, which still has removed feature. 2) The hostid on the SERVER line is for a different host, so all features in this license file were removed. Cannot connect to the license server specified in the license file. Network connect to this_host failed. Change this_host on the SERVER line in the license file to the actual host name. Cannot connect to the license server. The entire server system is down or not responding on this node. See the system administrator about starting the server or make sure that you are referring to the correct host in ALTAIR_LM_LICENSE_FILE and LM_LICENSE_FILE. Cannot connect to the license server. altair_lm is down, but lmgrd is up. Check lmgrd log file or try lmreread.
-62
-63
-64 -71 -74 -76 -77 -83 -84
-85
-87 -88 -90 -92
-95
-96
-97

Appendix D: FLEXlm Error Message Error code -101 -103 Description/cause/workaround All licenses are reserved for others. Reservations are made in the options file. The server must be restarted for option file changes to take place. Terminal server remote client not allowed. A server license is needed to run applications on Windows terminal server remote client machines. Contact Altair support to get a server license. License server out of network connections. altair_lm cannot handle any more users. See the debug log for more details. Dongle is not attached or cannot read dongle. Either the hardware dongle is unattached or the necessary software driver for this dongle type is missing. Dongle drivers are available at www.Macrovision.com or at <install_location>\security\flexid.exe. Missing dongle driver. In order to read the dongle hostid, the correct driver must be installed. These drivers are available at www.Macrovision.com or at <install_location>\security\flexid.exe. lmreread must be run on license server node. This module has been disabled from running. This product has been disabled in the license file. Unable to retrieve Global License information. Unable to communicate with the vendor daemon (altair_lm). Check the version of lmgrd/altair_lm. They may need to be updated to the same HyperWorks version as the client application. The feature 'PartialGlobalLicense' is needed in the license file to run this application. There is a four-to-eight hour time difference between the client and the license server. Contact Altair support or your account manager to request a new license with this feature. The feature 'FullGlobalLicense' is needed in the license file to run this application. There is an eight hour or more time difference between the client and the license server. Contact Altair support or your account manager to request a new license with this feature. The license server needs to be updated. The client has a newer FLEXlm/HyperWorks version than the license server. Unable to retrieve Global License information. There was an error retrieving the time zone information from the client or the server. Make sure that the client has the same FLEXlm/HyperWorks version as the license server. Contact Altair support. Invalid license file. The feature has an incorrect format in the license file.
-106 -110
-112
-119 1 2 3
6 7
96

Appendix E: Example of alus.conf file
Example alus.conf file on Windows

Below is an example alus.conf file, with comments for UNIX/Linux. The comments are led by the # signs. Example
# The variables below are for both the UMT and URT. They point to the directories that the usage data, # logs, etc. are stored in. The place-holder "$MY_DIRECTORY" reflects the directory that the package # has been installed to. This is set by the install script. (Note: This is not the internal variable # used by the script itself. ALUS_LOGGER_DIRECTORY=$MY_DIRECTORY/altair/security/urt_dist/alus/logs ALUS_PENDING_DIRECTORY=$MY_DIRECTORY/altair/security/urt_dist/alus/data/pending ALUS_SENT_DIRECTORY=$MY_DIRECTORYa/ltair/security/urt_dist/alus/data/sent ALUS_INVALID_DIRECTORY=$MY_DIRECTORY/altair/security/urt_dist/alus/data/invalid ALUS_UNDELIVERABLE_DIRECTORY=$MY_DIRECTORY/altair/security/urt_dist/alus/data/undeliverable ALUS_PROCESSING_DIRECTORY=$MY_DIRECTORY/altair/security/urt_dist/alus/data/processing ALUS_SCRATCH_DIRECTORY=$MY_DIRECTORY/altair/security/urt_dist/alus/data/scratch ALUS_UNDELIVERABLE_COUNT=7 ALUS_UNDELIVERABLE_DB_FILE_PATH=$MY_DIRECTORY/altair/security/urt_dist/alus/data/undeliverable.pr operties # These are the URLs that point to the Usage Data server. You do not need to edit the URL, just set # MY_HTTP to either http or https. Remember that your proxy and this must both be either http or https ALUS_ALAS_URL=MY_HTTP://urtserv01.altair.com ALUS_WSDL_URL=MY_HTTP://urtserv01.altair.com/GWUsageBeanService/GWUsageBean ALUS_URT_LOCATION=$MY_DIRECTORY/altair/security/urt_dist/alus/bin/urt.sh
## Configuration of proxy should be either HTTPS(SSL) or HTTP. Cannot have both set. ## user and password should not be set if they are not required by your proxy server #ALUS_HTTP_PROXYHOST=0.0.0.0 #ALUS_HTTP_PROXYPORT=80 #ALUS_HTTP_PROXY_USER=username

97

#ALUS_HTTP_PROXY_PASSWORD=password ## HTTPS(SSL) Proxy setup ## user and password should not be set if they are not required by your proxy server ALUS_HTTPS_PROXYHOST=news ALUS_HTTPS_PROXYPORT=80 ALUS_HTTPS_PROXY_USER= ALUS_HTTPS_PROXY_PASSWORD=
Example alus.conf file on Windows

Below is an example alus.conf file, with comments. The comments are led by the # sign. Example:
# The variables below are for both the UMT and URT. They point to the directories that the usage data, # logs, etc. are stored in. The place-holder "$MY_DIRECTORY" reflects the directory that the package # has been installed to. This is set by the install script. (Note: This is not the internal variable # used by the script itself. ALUS_LOGGER_DIRECTORY=C:\Altair\licensing9.0\security\urt_dist\alus\logs ALUS_PENDING_DIRECTORY=C:\Altair\licensing9.0\\security\urt_dist\alus\data\pending ALUS_SENT_DIRECTORY=C:\Altair\licensing9.0\\security\urt_dist\alus\data\sent ALUS_INVALID_DIRECTORY=C:\Altair\licensing9.0\security\urt_dist\alus\data\invalid ALUS_UNDELIVERABLE_DIRECTORY=C:\Altair\licensing9.0\security\urt_dist\alus\data\undeliverable ALUS_PROCESSING_DIRECTORY=C:\Altair\licensing9.0\security\urt_dist\alus\data\processing ALUS_SCRATCH_DIRECTORY=C:\Altair\licensing9.0\security\urt_dist\alus\data\scratch ALUS_UNDELIVERABLE_COUNT=7 ALUS_UNDELIVERABLE_DB_FILE_PATH=C:\Altair\licensing9.0\/altair/security/urt_dist/alus/data/undeliverable. properties # These are the URLs that point to the Usage Data server. You do not need to edit the URL, just set # MY_HTTP to either http or https. Remember that your proxy and this must both be either http or https ALUS_ALAS_URL=MY_HTTP://urtserv01.altair.com ALUS_WSDL_URL=MY_HTTP://urtserv01.altair.com/GWUsageBeanService/GWUsageBean ALUS_URT_LOCATION=$MY_DIRECTORY/altair/security/urt_dist/alus/bin/urt.sh
## Configuration of proxy should be either HTTPS(SSL) or HTTP. Cannot have both set. ## user and password should not be set if they are not required by your proxy server #ALUS_HTTP_PROXYHOST=0.0.0.0 #ALUS_HTTP_PROXYPORT=80 #ALUS_HTTP_PROXY_USER=username
98


#ALUS_HTTP_PROXY_PASSWORD=password ## HTTPS(SSL) Proxy setup ## user and password should not be set if they are not required by your proxy server ALUS_HTTPS_PROXYHOST=news ALUS_HTTPS_PROXYPORT=80 ALUS_HTTPS_PROXY_USER= ALUS_HTTPS_PROXY_PASSWORD=

Appendix F: FLEXlm Administration Utilities

This section describes the command syntax for the various FLEXlm license utilities to help the license administrator manage the licensing activities on the network. These utilities are presented in alphabetical order.
lmdiag
lmdiag allows you to diagnose problems when you cannot check out a license. Usage is: lmdiag [-c license_file_list] [-n] [feature[:keyword=value]] where: -c license_file_list -n Diagnose the specified file(s). Run in non-interactive mode; lmdiag will not prompt for any input in this mode. In this mode, extended connection diagnostics are not available. Diagnose this feature only. Keyword can be one of the following: VERSION, HOSTID, EXPDATE, KEY, VENDOR_STRING, ISSUER. If a license file contains multiple lines for a particular feature, you can select a particular line for lmdiag to report on.
feature keyword=value

101
Appendix F: FLEXlm Administration Utility Example: lmdiag f1:HOSTID=12345678 Attempts a checkout on the line with the hostid 12345678. Notes If no feature is specified, lmdiag will operate on all features in the license file(s) in your list. lmdiag will first print information about the license, then attempt to check out each license. If the checkout succeeds, lmdiag will indicate this. If the checkout fails, lmdiag will give you the reason for the failure. If the checkout fails because lmdiag cannot connect to the license server, then you have the option of running extended connection diagnostics. These extended diagnostics attempt to connect to each port on the license server node, and can detect if the port number in the license file is incorrect. lmdiag will indicate each port number that is listening, and if it is an lmgrd process, lmdiag will indicate this as well. If lmdiag finds the vendor daemon for the feature being tested, then it will indicate the correct port number for the license file to correct the problem.
lmgrd
lmgrd is the main daemon program for FLEXlm. When you invoke lmgrd, it looks for a license file containing information about vendors and features. On UNIX systems, it is strongly recommended that lmgrd be run as a non-privileged user (not root). Usage is: lmgrd [-c license_file_list] [-l [+]debug_log_path] [-2 -p] [-local] [-nfs_log] [-x lmdown] [-x lmremove] [-z ] [-v] where: c license_file_list l [+]debug_log_path Use the specified license file(s). Write debugging information to file debug_log_path. This option uses the letter l, not the numeral 1. Prepending debug_log_path with the + character appends logging entries. Restricts usage of lmdown, lmreread, and lmremove to a FLEXlm administrator who is by default root. If there a UNIX group called lmadmin, then use is restricted to only members of that group. If root is not a member of this group, then root does not have permission to use any of the above utilities. If 2-p is used when starting lmgrd, no user on Windows can shut down the license server with lmdown. Restricts the lmdown command to be run only from the same machine where lmgrd is running. It is not recommended to write a debug log to an NFS-mounted or Windows network-mounted disk since this can significantly slow the license server. If you choose to write to a mounted disk and the speed of the license server is too slow, you can use this flag to cache debug info before it is written out (when approximately 1kb of data is reached) thereby improving license server performance.
2 -p
-local nfs log
102

Appendix F: FLEXlm Administration Utility x lmdown Disable the lmdown command (no user can run lmdown). If lmdown is disabled, you will need to stop lmgrd via kill pid (UNIX) or stop the lmgrd and vendor daemon processes through the Windows Task Manager or Windows service. On UNIX, be sure the kill command does not have a 9 argument. Disable the lmremove command (no user can run lmremove). Run in foreground. The default behavior is to run in the background. If -l debug_log_path is present, then no windows are used, but if no -l argument specified, separate windows are used for lmgrd and each vendor daemon. Prints lmgrd version number and copyright and exits.
x lmremove -z
-v
lmhostid
The lmhostid utility reports the hostid of any machine whose platform is supported by FLEXlm. The default hostid type is displayed for a platform, unless an optional hostid type is specified and supported by that platform. Usage is: lmhostid [-n] [type] where type is one of: [-internet] (Optional on all platforms) [-vsn] [-flexid] -n -internet -vsn -flexid No header is printed, only the hostid is printed. IP address in ###.###.###.### format. Volume Serial Number of the Windows C:\ drive. Macrovision dongle-based hostid. (Windows)
The output of this command looks as follows: lmhostid - Copyright (c) 1989, 2002 Macrovision Software, Inc. The FLEXlm hostid of this machine is "69021c89"
lmnewlog
The lmnewlog utility switches the report log file by moving the existing report log information to a new file, then starting a new report log with the original report log file name. If you rotate report logs with lmnewlog instead of lmswitchr, you will not have to change the file name in the REPORTLOG line of the vendors options file.

Appendix F: FLEXlm Administration Utility Usage is: lmnewlog [-c license_file_list] feature renamed_report_log or: lmnewlog [-c license_file_list] vendor renamed_report_log where: -c license_file_list feature vendor renamed_report_log Use the specified license file(s). Any feature in this license file. Vendor daemon in this license file. New file path where existing report log information is to be moved.
lmpath
The lmpath utility allows direct control over FLEXlm license path settings. It can be used to add to, override, or get the current license path settings. Usage is: lmpath {-add | -override} {vendor | all} license_file_list where: -add Prepends license_file_list to the current license-file list or creates the license-file list, if it doesnt exist, initializing it to license_file_list. Duplicates are discarded. Overrides the existing license-file list with license_file_list. If license_file_list is the null string, "", the specified list is deleted. Deletes the value of LM_LICENSE_FILE. Deletes the value of ALTAIR_LM_LICENSE_FILE A vendor daemon name. Affects the value of ALTAIR_LM_LICENSE_FILE. Refers to all vendor daemons. Affects the value of LM_LICENSE_FILE. A colon-separated list on UNIX and a semi-colonseparated list on Windows. If license_file_list is the null string, "", then the specified entry is deleted.
-override
lmpath -override all "" lmpath -override vendor "" vendor all license_file_list
Note:
lmpath works by setting the FLEXlm registry entry on Windows or $HOME
To display the current license path settings, use: lmpath -status
104

Appendix F: FLEXlm Administration Utility The following is displayed: lmpath - Copyright (C) 1989-2001 Macrovision Software, Inc. Known Vendors: _____________ demo: ./counted.lic:./uncounted.lic _____________ Other Vendors: ______________ /usr/local/flexlm/licenses/license.lic where the path is set to a directory, all of the *.lic files are listed separately.
lmremove
lmremove is needed only when a client node crashes, because that is the only condition where a license is not automatically freed immediately (licenses will be freed within twenty minutes automatically). The lmremove utility allows you to remove a single users license for a specified feature. If the application is active, it will re-checkout the license shortly after it is freed by lmremove. Usage is: lmremove [-c license_file_list] feature user user_host display or lmremove [-c license_file_list] -h feature server_host port handle where: -c license_file_list feature user user_host display server_host port handle Specify license file(s). Name of the feature checked out by the user. Name of the user whose license you are removing, as reported by lmstat -a. Name of the host the user is logged into, as reported by lmstat -a. Name of the display where the user is working, as reported by lmstat -a. Name of the host on which the license server is running. Port number where the license server is running, as reported by lmstat -a. License handle, as reported by lmstat -a.
The user, user_host, display, server_host, port, and handle information must be obtained from the output of lmstat -a. lmremove removes all instances of user on user_host and display from usage of feature. If the optional -c license_file_list is specified, the indicated file(s) is used as the license file. You should protect the execution of lmremove, because removing a users license can be disruptive. See the -x or -2 -p options in lmgrd for details about securing access to lmremove. The -h variation uses the server_host, port, and license handle, as reported by lmstat -a. Consider this example lmstat -a output: joe nirvana /dev/ttyp5 (v1.000) (cloud9/7654 102), start Fri 10/29 18:40 In this example, the user is joe, the user host is nirvana, the display is /dev/typp5, the server host is cloud9, the port is 7654, and the license handle is 102.

Appendix F: FLEXlm Administration Utility To remove this license, issue one of the following commands: lmremove f1 joe nirvana /dev/ttyp5 or lmremove -h f1 cloud9 7654 102 When removing by handle, if licenses are grouped as duplicates, all duplicate licenses will also be removed. If license lingering is set and lmremove is used to reclaim the license, lmremove will start, but not override, the licenses linger time.
lmreread
The lmreread utility causes the license daemon to reread the license file and start any new vendor daemons that have been added. In addition, all running daemons are signaled to reread the license file and their end-user options files for changes in feature licensing information or option settings. If report logging is enabled, any report log data still in the vendor daemons internal data buffer is flushed. A vendor daemon rereads the path to its option file and rereads its options file as a result of lmreread. lmreread also allows server machine host names to be reread, but still cannot be used to change server port numbers. If the optional vendor daemon name is specified, only the named daemon rereads the license file and its end-user options file (in this case, lmgrd does not reread the license file). Usage is: lmreread [-c license_file_list] [-vendor vendor] [-all] where: -c license_file_list -vendor vendor -all Use the specified license file(s). Only this one vendor daemon should reread the license file. lmgrd will restart the vendor daemon if necessary. If more than one lmgrd is specified, instructs all lmgrds to reread.
You may want to protect the execution of lmreread. See the -2 -p and -x options in lmgrd for details about securing access to lmreread. To stop and restart a single vendor daemon, use lmdown -vendor vendor, then use lmreread -vendor vendor, which restarts the vendor daemon. Note: If you use the -c license_file_list option, the license file(s) specified will be read by lmreread, not by lmgrd; lmgrd rereads the file it read originally.
106

Appendix F: FLEXlm Administration Utility
lmstat
Note: lmstat -a is a potentially expensive command. With many active users, this can generate a lot of network activity, and therefore should not be used too often.
The lmstat utility helps you monitor the status of all network licensing activities, including: Daemons that are running Users of individual features Users of features served by a specific vendor daemon BORROW licenses borrowed lmstat prints information that it receives from the license server, therefore it will not return any information about users of node-locked uncounted or DEMO licenses, unless the servers license file includes the node-locked licenses and the client is not reading the license file (via port@host or USE_SERVER). Queued users and licenses shared due to duplicate grouping are also not returned by lmstat. Usage is: lmstat [-a] [-A] [-c license_file_list] [-f [feature]] [-S [vendor]] where: -a -A -c -f [feature] -S [vendor] Display all information about. List all active licenses. Use the specified license_file_list license file(s). List users of feature. List all users of vendors features.
lmremove requires the output of lmstat -a. The output of lmstat -a looks similar to: License server status: 27000@myhost1 License file(s) on myhost1: install_dir/altair/security/counted.lic myhost1: license server UP v10.1 Vendor daemon status (on myhost1): demo: UP v10.1 Feature usage info: Users of f1: (Total of 200 licenses issued; Total of 1 license in use) "f1" v1.0, vendor: demo floating license daniel myhost2 19.16.18.26 (v1.0) (myhost1/27000 102), start Wed 9/13 17:37 where: daniel myhost2 19.16.18.26 v1.0 myhost1 user user_host display version server_host User name. Host where user is running. Display where user is running. Version of feature. Host where license server is running.

Appendix F: FLEXlm Administration Utility
27000 102 start Wed 9/13 17:37
port handle checkout_time
Port on server_host where license server is running. License handle. Time that this license was checked out.
lmswitch
The lmswitch utility switches the debug log file written by a particular vendor daemon by closing the existing debug log for that vendor daemon and starting a new debug log for that vendor daemon with a new file name. It will also start a new debug log file written by that vendor daemon if one does not already exist. Usage is: lmswitch [-c license_file_list] vendor new_debug_log where: -c license_file_list vendor new_debug_log Use the specified license file(s). Vendor daemon in this license file. Path to new debug log file.
Debug log output from lmgrd and all vendor daemons started by that lmgrd are written into the same debug file by default. lmswitch allows companies to keep separate log files for different vendors and control the size of their debug log file. If debug log output is not already directed to a separate file for this vendor daemon, lmswitch tells the vendor daemon to start writing its debug log output to a file, new_debug_log. If this vendor daemon is already writing to its own debug log, lmswitch tells the vendor daemon to close its current debug log file and start writing its debug log output to new_debug_log. The effect of lmswitch continues only until the vendor daemon is shut down or its options file is reread via lmreread. When the vendor daemon is restarted or its options file is reread, it will look for a DEBUGLOG line in the options file to determine whether or not to write its debug log output into its own file and, if so, what file to write.
lmswitchr
The lmswitchr utility switches the report log file by closing the existing report log and starting a new report log with a new file name. It will also start a new report log file if one does not already exist. Usage is: lmswitchr [-c license_file_list] feature new_report_log or with vendor daemon: lmswitchr [-c license_file_list] vendor new_report_log
108

Appendix F: FLEXlm Administration Utility where: -c license_file_list feature vendor new_report_log Use the specified license file(s). Any feature in this license file. Vendor daemon in this license file. Path to new report log file.
If report logging is not enabled for the vendor daemon, lmswitchr tells it to start writing its report log output to new_report_log. If report logging is already enabled for the vendor daemon, lmswitchr tells the vendor daemon to close its report log file and start writing its new report log output to new_report_log. The effect of lmswitchr continues only until the vendor daemon is shut down or its options file is reread via lmreread. When the vendor daemon is restarted or its options file is reread, it will look for a REPORTLOG line in the options file to determine whether or not to write report log output to a file and, if so, what file to write. See Also lmnewlog
lmver
The lmver utility reports the FLEXlm version of a library or binary file. Usage is: lmver filename where filename is the name of an executable file built with FLEXlm. For example if you have an application called spell, type: lmver spell Alternatively, on UNIX systems, you can use the following commands to get the FLEXlm version of a binary: strings filename | grep Copy

Appendix G: Option File Keywords

This appendix covers type specification and the syntax each option requires. The options are listed alphabetically.
Type Specification
The following option keywords restrict who may use licenses or where licenses may be used: EXCLUDE, EXCLUDEALL, INCLUDE, INCLUDEALL, MAX, and RESERVE. These options take a TYPE argument specifying whether the restriction is based on USER, HOST, DISPLAY, or INTERNET: USERUNIX user name of the user executing the program. HOSTmachine where the application is executing. Anywhere a host name can be used in an options file, an IP-address of the format #.#.#.# can be used instead. The IP-addresses can contain wildcards. DISPLAYdisplay where the application is displayed. On UNIX, DISPLAY is /dev/ttyxx (which is always /dev/tty when an application is run in the background) or the X-Display name. On Windows, it is the system name or, in the case of a terminal server environment, the terminal server client name. INTERNETIP address of the machine where the application is executing (wildcards can be used in the IP address). The types listed above take a single member. For example: EXCLUDE coolsoft USER joe To specify a list of users or hosts, first define the list using the GROUP or HOST_GROUP option lines, then use the GROUP or HOST_GROUP type to specify the group name. For example: GROUP stars joe barbara susan EXCLUDE coolsoft GROUP stars
Alphabetical List of Options

BORROW_LOWWATER
BORROW_LOWWATER feature[:keyword=value] n
feature keyword=value n
Name of the feature being affected. Feature name modifier to denote a group of licenses. Number of licenses that can not be borrowed via licensing borrowing. HyperWorks 9.1 Installation Guide
111
Appendix G: Option File Keywords Example: If there are total 10 license for feature f1 and borrow is enabled in this application, the following line in the option file allows only 7 licenses to be borrowed: BORROW_LOWWATER f1 3
DEBUGLOG
DEBUGLOG [+]debug_log_path Specifies a location for the debug log output from the vendor daemon associated with this options file, debug_log_path should be the full path of the debug log. Preceding the debug_log_path with a + character appends logging entries; otherwise the file will be overwritten each time the daemon is started. Note that this affects output from only the vendor daemon associated with this options file. The debug log output of lmgrd and any other vendor daemons in the same license file is not captured in this file. See also lmswitch in Appendix F.
EXCLUDE
EXCLUDE feature[:keyword=value] type {name | group_name} Omits a user or pre-defined group of users, etc., from the list of who is allowed to use the feature. EXCLUDE overrides INCLUDE. feature keyword=value type Name of the feature being affected. Feature name modifier to denote a license pool. One of USER, HOST, DISPLAY, INTERNET, GROUP, or HOST_GROUP. See the above section, Type Specification, for details. Name of an item of type to reserve licenses for. Name of the group to exclude.
name group_name
Example: To exclude the user hank from the list of users able to use feature f1: EXCLUDE f1 USER hank
EXCLUDE_BORROW
EXCLUDE_BORROW feature[:keyword=value] type {name | group_name} Excludes a user or pre-defined group of users, etc., from the list of who is allowed to borrow licenses for this BORROW feature. EXCLUDE_BORROW supersedes INCLUDE_BORROW; conflicts between the EXCLUDE_BORROW list and the INCLUDE_BORROW list are resolved by the EXCLUDE_BORROW taking precedence. feature keyword=value type Name of the feature being affected. Feature name modifier to denote a group of licenses. One of USER, HOST, DISPLAY, INTERNET, GROUP, or HOST_GROUP. See the previous section, Type Specification, for details. Name of an item of type for which license borrowing is excluded.
name
112

Appendix G: Option File Keywords
group_name
Name of the group to exclude from borrowing.
Example: To exclude the user fred from the list of users able to borrow feature f1: EXCLUDE_BORROW f1 USER fred
EXCLUDEALL
EXCLUDEALL type {name | group_name} Omits a user or pre-defined group of users, etc., from the list of who is allowed to use all features served by this vendor daemon. type name group_name One of USER, HOST, DISPLAY, INTERNET, GROUP, or HOST_GROUP. See the previous section, Type Specification, for details. Name of an item of type to reserve licenses for. Name of the group to exclude.
Example: To exclude any user on the machine chaos from using all features served by this vendor daemon: EXCLUDEALL HOST chaos
FQDN_MATCHING
FQDN_MATCHING exact | lenient Sets the level to which host names used in HOST type-specifiers must match the host name sent by the FLEXanbled application. The application is configured to send either its host name or its fully qualified domain name (FQDN) to the vendor daemon for validation with HOST typespecifiers. Check with your vendor to determine fully quality domain name support. exact lenient The host name in the HOST type specifier must match in content and format to that sent by the application. This is the default setting. The host name sent by the application needs match to the extent supplied in the HOST type specifier or by the application, whichever is less restrictive.
Only the list FQDN_MATCHING keyword in the options file has effect; all others are ignored.
GROUP
GROUP group_name user_list Defines a group of users for use in INCLUDE, INCLUDEALL, EXCLUDE, EXCLUDEALL, and RESERVE option lines. group_name user_list Name of the group being defined. List of user names in that group.
Example: To define the group Hackers consisting of bob, howard, and james: GROUP Hackers bob howard james Multiple GROUP lines for the same group name will add all the specified users into the group.

Appendix G: Option File Keywords Note USER_GROUP is an alias for GROUP.
GROUPCASEINSENSITIVE
GROUPCASEINSENSITIVE OFF|ON_ If set to ON, user names and host names specified with the options file GROUP and HOST_GROUP keywords, respectively, are treated as case insensitive. By default, GROUPCASEINSENSITIVE is OFF; user names and host names are treated as case sensitive.
HOST_GROUP
HOST_GROUP group_name host_list Defines a group of hosts for use in INCLUDE, INCLUDEALL, EXCLUDE, EXCLUDEALL, and RESERVE option lines. Multiple HOST_GROUP lines will add all the specified hosts into the group. group_name host_list Name of the group being defined. List of host names in that group.
To define the host group Pacific consisting of tokyo, seattle, and auckland: HOST_GROUP Pacific tokyo seattle auckland Anywhere a host name can be used in an options file, an IP-address can be used instead.
INCLUDE
INCLUDE feature[:keyword=value] type {name | group_name} Adds a user or pre-defined group of users, etc., in the list of who is allowed to use licenses for this feature. Anyone not in an INCLUDE statement will not be allowed to use that feature. EXCLUDE overrides INCLUDE. feature keyword=value type name group_name Name of the feature being affected. Feature name modifier to denote a license pool. A license pool is a collection of licenses. One of USER, HOST, DISPLAY, INTERNET, GROUP, or HOST_GROUP. Name of an item of type to reserve licenses for. Name of the group to include.
To include user bob in the list of users able to use feature f1: INCLUDE f1 USER bob Note: INCLUDE is required for USER_BASED or HOST_BASED features. The system administrator specifies which users are allowed to use the product, via INCLUDE, and the license limits the number of users that can be INCLUDEd.
INCLUDE_BORROW
INCLUDE_BORROW feature[:keyword=value] type {name | group_name} Includes a user or predefined group of users, etc., from the list of who is allowed to borrow the BORROW feature. Anyone not in an INCLUDE_BORROW statement is not allowed to borrow licenses. EXCLUDE_BORROW supersedes INCLUDE_BORROW; conflicts between the
114

Appendix G: Option File Keywords EXCLUDE_BORROW list and the INCLUDE_BORROW list are resolved by the EXCLUDE_BORROW taking precedence. feature keyword=value type Name of the feature being affected. Feature name modifier to denote a group of licenses. One of USER, HOST, DISPLAY, INTERNET, GROUP, or HOST_GROUP. See the previous section, Type Specification, for details. Name of an item of type for which license borrowing is included. Name of the group for which license borrowing is included.
name group_name
Example: To include user tom in the list of users able to borrow feature f1: INCLUDE_BORROW f1 USER tom
INCLUDEALL
INCLUDEALL type {name | group_name} Includes a user or predefined group of users, etc. in the list of who is allowed to use all features served by this vendor daemon. Anyone not in an INCLUDEALL statement will not be allowed to use these features. type name group_name One of USER, HOST, DISPLAY, INTERNET, GROUP, or HOST_GROUP. See the section, Type Specification, for details. Name of an item of type to reserve licenses for. Name of the group to include.
Example: To allow the user jane to use all features served by this vendor daemon: INCLUDEALL USER jane
MAX
MAX num_lic feature[:keyword=value] type {name | group_name} Limits usage for a group or user. num_lic feature keyword=value type name group_name Usage limit for this user or group. Feature this limit applies to. Feature name modifier to denote a license pool. A license pool is a collection of licenses. One of USER, HOST, DISPLAY, INTERNET, GROUP, or HOST_GROUP. Name of an item of type to reserve licenses for. Name of the group to limit.
Note:
User-based options will not work when licenses are stacked. Stacking occurs

Appendix G: Option File Keywords when OptiStruct and HyperOpt are run on a machine with more than two processors, or while using the application mode of Process Manager, or using HyperWeb.
MAX_BORROW_HOURS
MAX_BORROW_HOURS feature[:keyword=value] num_hours Changes the maximum period a license can be borrowed from that specified in the license certificate for feature. The new period must be less than that in the license certificate. If multiple MAX_BORROW_HOURS keywords appear in the options file, only the last one is applied to feature.
feature keyword=value num_hours
Feature this borrow period applied to. The license certificate for feature must have BORROW enabled. Feature name modifier to denote a group of licenses. A license pool is a collection of licenses. Number of hours in the new borrow period. This value must be less than that specified in the license certificate for feature (the default, if not specified, is 168 hours).
MAX_OVERDRAFT
MAX_OVERDRAFT feature[:keyword=value] num_lic Limits OVERDRAFT license usage below the OVERDRAFT allowed by the license file. feature keyword=value num_lic Feature this limit applies to. Feature name modifier to denote a license pool. A license pool is a collection of licenses. Usage limit for this user or group.
NOLOG
NOLOG { IN | OUT | DENIED | QUEUED } Suppresses logging the selected type of event in the debug log file. To turn off logging of checkins: NOLOG IN To turn off logging of checkouts and queued requests two separate NOLOG lines are required: NOLOG DENIED NOLOG QUEUED Note: License administrators might use this option to reduce the size of the debug log file. See Appendix F, lmswitch.
REPORTLOG
REPORTLOG [+]report_log_path REPORTLOG specifies the report log file for this vendor daemon. It is recommended preceding the report_log_path with a + character to append logging entries, otherwise the file will be 116 Altair License Management System 9.1 Installation Guide 9.1
Appendix G: Option File Keywords overwritten each time the daemon is started. Note: SAMreport, a separate product available from Macrovision, is used to process FLEXlm report log files. SAMreport can process only report log files, not debug log files.
RESERVE
RESERVE num_lic feature[:keyword=value] type{name | group_name} Reserves licenses for a specific user. num_lic feature keyword=value type name group_name Number of license to reserve for this user or group. Feature this reservation applies to. Feature name modifier to denote a license pool. A license pool is a collection of licenses. One of USER, HOST, DISPLAY, INTERNET, GROUP, or HOST_GROUP. Name of an item of type to reserve licenses for. Name of group to reserve licenses for.
Example: to reserve one license of feature f1 for user mel: RESERVE 1 f1 USER mel If you want to reserve a license for each of several users or groups, you must use a separate RESERVE line for each user or group. Note: Any licenses reserved for a user are dedicated to that user. Even when that user is not actively using the license it will be unavailable to other users. However, a RESERVEd license will not cause an overdraft to be reported by SAMreport if the license is not actually in use.

Appendix H: Managing Licenses from Multiple Vendors

When you are running FLEXlm licensed products from multiple vendors, you may need to take steps to prevent licensing conflicts during installation. There are several strategies to accomplish this, which are discussed below. These strategies are ordered from most to least independence among vendors.
Multiple Machines
In this scenario, each distinct vendor daemon and its associated license file(s) is located on a separate server machine. Each machine serves licenses for its vendor daemon and runs its own local copy of lmgrd. Advantages Machines are maintained separately. If one machine goes down, the other machines continue to serve licenses for their vendors. Each server has its own debug log. License load is distributed. Disadvantages Administrative overhead is the highest. Starting the license server Invoke the license manager daemon using on each machine: lmgrd -c server_machine_n_license_list
One Machine with Multiple License Servers

In this scenario, each lmgrd process serves licenses for its vendor daemon, using a separate license file(s). Licenses for all vendors are contained in one machine. For this scenario, the following needs to be taken in consideration: The TCP/IP port number specified on the SERVER line of the license files must be different for each license server. Use a standard text editor to change the TCP/IP port number in each of the license files so that they are unique. You can use an explicit path to lmgrd to make sure that the license manager is compatible with the license file being used. Only the CPU, memory and networking of the machine, limits the number of license servers.
118

Appendix H: Managing Licenses from Multiple Vendors Advantages License servers are maintained separately. If one server goes down, the other servers continue to serve licenses for their vendors. Each server has its own debug log. Disadvantages Administrative overhead is high. If the machine goes down, all licensing is disabled. Licensing load is concentrated to one machine. Starting the license server Invoke each license server: For server 1: lmgrd -c vendor_ABC_license_file For server 2: lmgrd -c vendor_DEF_license_file For server 3: lmgrd -c vendor_XYZ_license_file
One Machine with One License Server and Multiple License Files
In this scenario, one lmgrd runs on the server machine and serves one or more vendor daemons, each with one or more license files. The license files are usually in the same directory. Advantage Reduced administrative overhead. Disadvantages One lmgrd serves all vendor daemons. If lmgrd goes down, all licensing is disabled. If the machine goes down, all licensing is disabled. Maximizes license load to one machine and one lmgrd process. The lmgrd process might run out of file descriptors. Output from all vendor daemons goes into one common debug log, unless separate debug logs are specified with DEBUGLOG in each vendor's options file. Having one common debug log makes it harder to debug a single vendor daemon's problems. Starting the license server Invoke the license manager daemon once on the server machine: lmgrd -c license_file_list

Appendix I: Uninstallation Process
Appendix I: Uninstallation Process

Uninstalling from Windows 1. Stop the processes running from Altair License Managemet system ( Flexlm and UMT). Back up the existing Altair license file if you need to use it later. 2. Open the Windows Control Panel then select the add/remove control panel icon. 3. Locate and highlight the Altair Licensing 9.1 Package and then click the remove button. 4. A prompt should pop up indicating Do you want to completely remove the selected application and all of its features? 5. Click Yes to start the un-installation process. At the end of the process, the Installation Wizard pops up indicating that the uninstall was complete. 6. Click Finish to complete the process.
Uninistalling from UNIX/Linux

1. Stop the license manager system and UMT (lmgrd, altair_lm, and umt processes). 2. The init script files, (altairlmgrd, S90altairlmgrd, K10altairlmgrd) must be deleted. Remove the init script files from the /etc/rc.d/init.d, /etc/rc5.d, and /etc/rc0.d. 3. On the UNIX command prompt, use the following command to remove the installed directory. /bin/rm rf <install_dir>
120

Appendix J: Instructions for Sending Reports Manually

These instructions are meant for customers that want to implement a manual or man-in-the-loop method of delivering Gridworks license usage. There are two implementations that are available. Method 1 uses Altairs communication software but allows the customer to manually start the sending process. Method 2 is a completely manual process. It would be advantageous to have some background on how the current system works. There are three main processes that are involved. The actual Flexlm license system daemons/services (lmgrd and altair_lm), the Altair Usage Monitoring Tool (UMT) and the Altair Usage Reporting Tool (URT). Lmgrd and altair_lm are the services that actually provide the licenses for software. The UMT is installed and monitors the Flexlm system by polling it every 1 minute to gather usage information. That information is written to a log every hour. The log is rotated every day and the daily logs are stored. Once a month the UMT kicks-off the URT during a random minute in the first week of the month. The URT then looks in the log storage directory, zips up all daily log files there and transmits them to Altairs server via HTTP or HTTPS. Depending on success or failure, a copy of the zip file is moved to a different directory location and the storage area is cleared to accept the next months worth of logs. No other information than what is contained in the ASCII readable log files is gathered by the UMT or URT for transmission. The URT does a validation handshake with the server when sending by checking the License ID contained in the file against a valid License ID file on the server. The directory structure is as follows for Windows (similar for UNIX/Linux):

121
Appendix J: Instructions for Sending Reports Manually The current, open UMT log file is in the directory processing, closed, finished logs are stored in pending, and successfully sent zip files are kept in sent. The directory bin contains the file that is used to start the URT (urt.bat or urt.sh). All log files are plain text and digitally signed to prevent tampering. The current URT utilizes a Java program (bin/altairURT.jar) to send the data from the host to Altair. The configuration file for the program is alus.conf. This is where things like proxy settings and HTTP vs. HTTPS are configured. In the end the UMT simply executes the file bin/urt.bat (or urt.sh) once a month. This is a simple script that launches the URT. This is the easiest way of knowing that information is getting sent to the correct location during the correct time period. Realizing that not every customer wants a completely automated system, Altair is providing the following two methods to place a man-in-the-loop Method one (1) only takes the automated sending out of the loop, and allows the customer to kick-off the URT by hand. It still utilizes the totally automated system for collecting, zipping, communicating and moving the logs. Method two (2) is completely manual, requiring some work on the administrators part to gather logs (etc.) and deliver them manually via email to Altair.
METHOD 1: Manual usage of existing URT software

All that is required to implement this method is to copy/backup the urt.sh or urt.bat file to another name, such as urt_original.bat or urt_original.sh and then change the original file to be empty So on linux/Unix you could: cp urt.sh urt_original.sh for Windows: copy urt.bat urt_original.bat Then, edit the urt.bat or urt.sh and remove all lines, leaving the file completely empty. This way when the UMT starts the URT nothing will happen and the UMT will continue on normally When you are ready to send your data go to the bin directory and use the urt_original script. All that has to be done is to type ./urt_original.sh or urt_original.bat. This will process all the logs and send the data. During this, you will see verbose output of what is happening. If you want to examine all the logs before they are sent, they are sitting in the pending directory.
METHOD 2: Completely manual processing and emailing of data

This method is a completely manual method of collecting the log files and sending them to Altair for processing. The administrator will be required to inspect the log files as desired, zip them up using the supplied program, send a copy to Altair and then archive the zip file if desired. It is assumed that if this
122

Appendix J: Instructions for Sending Reports Manually method is used that the administrator has basic knowledge of the computing platform and the directions given can be carried out on the specific platform that the software is installed on. The zip utility included with the Altair license package is required to be used for processing. It is located in the urt_dist/alus/utils/izip/bin/PLATFORM directory where PLATFORM represents the platform you are running on (AIX, LINUX, WIN32). In that directory you will find the executables for zip and unzip. First, follow the steps in Method 1 to move the urt.bat or urt.sh file aside and have an empty script in its place. Change directory to the urt_dist/alus/data/pending directory and inspect the log files that are present there, if desired. When you are ready to package them up, use the following command: urt_dist/alus/utils/izip/bin/PLATFORM/izip YYYYMMDD.zip *.dat (YYYY is the current year, MM is the current 2-digit month and DD is the current date. Please use two digits for MM and DD, e.g., January 4th, 2008 is 20080104) Once this is finished, place a copy of the zip file in the sent directory and delete *.dat from the pending directory. Send the file YYYYMMDD.zip to Altair as an attachment to usagereporting@altair.com. Please contact your Altair support organization if you have any questions.

123
124


AltairLicensing InstallationGuide91

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

AltairLicensing InstallationGuide91

Încărcat de

Drepturi de autor:

Formate disponibile

Altair License Management System Version 9.

Installation Guide version 9.1

Altair Engineering Contact Information

Trademark and Registered Trademark Acknowledgments

Altair License Management System 9.1 Installation Guide 9.1

Altair License Management System Release Notes Version 9.1 ...................3

Chapter 1: Altair License Management System ............................................13

Chapter 2: Preparing to Install Altair License Management System...........22

Altair License Management System 9.1 Installation Guide 9.1

2.3 Selecting License Server Nodes ................................................................................... 24 2.4 System Requirement...................................................................................................... 26

Chapter 3: Installing Altair License Management System on Linux/UNIX ..27

Chapter 4: Installing Altair License Management System on Windows .....39

Chapter 5: Operations and Maintenance .......................................................55

Chapter 6: Altair GridWorks Licensing .........................................................75

Altair License Management System 9.1 Installation Guide 9.1

Appendix D: FLEXlm Error Messages.............................................................93 Appendix E: Example of alus.conf file .......................................................97

Altair License Management System 9.1 Installation Guide 9.1 iii

Altair License Management System 9.1 Installation Guide 9.1

About Altair License Management System

Altair License Management System 9.0 Installation Guide 9.0

Conventions Used in this Guide

Altair License Management System 9.1 Installation Guide 9.1

Altair License Management System Release Notes Version 9.1

Altair License Management System 9.1 Installation Guide 9.1

Altair License Management System Release Notes: 9.1

License usage tracking

Altair License Management System 9.1 Installation Guide 9.1

Altair License Management System 9.1 Installation Guide 9.1

Altair License Management System 9.1 Installation Guide 9.1

Altair License Management System Release Notes: 9.1

License usage tracking

Altair License Management System 9.1 Installation Guide 9.1

Altair License Management System Release Notes: 9.1 License files

Altair License Management System 9.1 Installation Guide 9.1

Altair License Management System 9.1 Installation Guide 9.1

Altair License Management System 9.1 Installation Guide 9.1

Altair License Management System Release Notes: 9.1

Altair License Management System 9.1 Installation Guide 9.1 11

Chapter 1: Altair License Management System

Altair License Management System 9.1 Installation Guide 9.1

1.2 Altair License Manager

Altair License Management System 9.1 Installation Guide 9.1

Chapter 1: Altair License Management System

License Manager Daemon (lmgrd)

Vendor Daemon (altair_lm)

License File (altair_lic.dat)

1.3 Usage Monitoring Tool

Altair License Management System 9.1 Installation Guide 9.1

Chapter 1: Altair License Management System

1.4 Usage Reporting Tool

1.5 Altair Application Server

Altair License Management System 9.1 Installation Guide 9.1 17

Chapter 1: Altair License Management System

1.6 Tracking Features and Report Log File

1.6b Report log files

Altair License Management System 9.1 Installation Guide 9.1

Chapter 1: Altair License Management System

1.6c Location of report log files

Altair License Management System 9.1 Installation Guide 9.1 19

Chapter 1: Altair License Management System <installation directory>\security\urt_dist\alus\data\

1.7 alus.conf File

1.8 System Limitation