0% found this document useful (0 votes)

260 views49 pages

Beta LM Tools v7.0 Setup Guide

This document provides a quick installation guide and overview for beta_lm_tools license management software. The guide outlines 8 key steps for downloading and installing beta_lm_tools, including deciding on a license server, downloading the software, unpacking it, generating a host key, obtaining a valid license file, and launching the license manager. Additional sections provide more detailed instructions on installation, configuration, usage and troubleshooting of beta_lm_tools and its various components.

Uploaded by

itzranjeeth

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

260 views49 pages

Beta LM Tools v7.0 Setup Guide

Uploaded by

itzranjeeth

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 49

SECTION 0. QUICK INSTALLATION GUIDE ................................................................................................... 2

0.1. QUICK INSTALLATION GUIDE................................................................................................................................ 2
0.2. UPDATING TO NEWER VERSION............................................................................................................................ 4
SECTION 1. INTRODUCTION TO BETA_LM_TOOLS ..................................................................................... 5
1.1. BASIC COMPONENTS .......................................................................................................................................... 5
1.2. OVERVIEW OF FEATURES ..................................................................................................................................... 5
1.3. HARDWARE REQUIREMENTS ................................................................................................................................ 6
SECTION 2. INSTALLING BETA_LM_TOOLS ................................................................................................ 7
2.1. OVERVIEW OF ACTIONS ....................................................................................................................................... 7
2.2. INSTALLATION PROCEDURE ................................................................................................................................. 7
2.2.1. Select a suitable license server scheme ............................................................................................. 7
2.2.2. Download beta_lm_tools ....................................................................................................................... 7
2.2.3. Verification of the download using Message Digest-5 (MD5) hash function .................................. 8
2.2.4. Unpack beta_lm_tools package ............................................................................................................ 9
2.2.5. Information required to build a valid license file .............................................................................. 10
2.2.6. Receive a valid license file .................................................................................................................. 11
2.2.7. Launching the beta_lm license manager ........................................................................................... 11
2.3. SUPPORTED BETA_LM FEATURES ...................................................................................................................... 14
2.4. MORE ON FEATURES, CREDITS AND PACKAGES ......................................................................................... 16
2.4.1. FEATUREs and their important keywords (WEIGHT, CREDIT and OPTIONS) ................................ 16
2.4.2. The pre-post PACKAGE ....................................................................................................................... 17
2.4.3. Examples .............................................................................................................................................. 19
2.5. BETA LICENSED APPLICATIONS: CREDITS/USER................................................................................................. 21
SECTION 3. OPTIONS AND USAGE OF LICENSE ADMINISTRATION TOOLS .........................................23
3.1. THE BETA_LM OPTIONS .................................................................................................................................... 23
3.1.1. Terminating beta_lm ............................................................................................................................ 24
3.2. THE BETA_LM STATISTICAL TOOLS .................................................................................................................... 24
3.2.1 The beta_lm_stat options ..................................................................................................................... 24
3.2.2. Monitoring license usage ..................................................................................................................... 28
3.3. THE BETA_LM_KILL_USER OPTIONS................................................................................................................... 29
3.4. THE BETA_LM_CONTROL OPTIONS .................................................................................................................... 29
SECTION 4. THE ADMINISTRATOR OPTIONS FILE ....................................................................................30
4.1. THE ADMINISTRATOR OPTIONS FILE................................................................................................................... 30
4.1.1. Idle User Timeout ................................................................................................................................. 30
4.1.2. Allow, deny or limit the access to specific features ......................................................................... 32
SECTION 5. THE LICENSE.DAT FILE .............................................................................................................34
5.1. THE LICENSE.DAT FILE ...................................................................................................................................... 34
5.2. ADDITIONAL SHORT TERM LICENSES & LICENSE EXTENSIONS .............................................................................. 36
SECTION 6. RUNNING A LICENSED APPLICATION ....................................................................................37
6.1. SEARCHING FOR A VALID LICENSE ..................................................................................................................... 37
6.1.1. Stand-alone server scheme ................................................................................................................. 38
6.1.2. Redundant server scheme ................................................................................................................... 39
6.2. RELEASING A LICENSE ...................................................................................................................................... 40
SECTION 7. BETA_LM ON THE GO ................................................................................................................41
7.0. INTRODUCTION TO BETA_LM ON THE GO .......................................................................................................... 41
7.0.1. What is beta_lm On The Go ................................................................................................................. 41
7.1. BASIC COMPONENTS & REQUIREMENTS ............................................................................................................ 41
7.1.1. What is a USB Ethernet/WiFi card ...................................................................................................... 41
7.1.2. Scheme & Hardware requirements .................................................................................................... 41
7.2. PROCEDURE & APPLICATION............................................................................................................................. 42
7.2.1. Overview of actions ............................................................................................................................. 42
7.2.2. Installation procedure .......................................................................................................................... 42
SECTION 8. TROUBLESHOOTING BETA_LM ...............................................................................................43
8.1. TROUBLESHOOTING BETA_LM ........................................................................................................................... 43
BETA LM Setup Guide

Section 0.
Quick Installation Guide
0.1. Quick installation guide
Users familiar with license management software can quickly browse through the following steps in
order to download & install beta_lm_tools. Numbers in the third column indicate the corresponding
paragraphs where detailed information on each specific step is given.

Action Paragraph
1. Decide on the machine that will be used as license server. If a server redundancy 1.2
scheme is to be used, decide on its type and on the machines that will be used as & 2.2.1
license servers.

2. Log on to BETA CAE Systems server and download beta_lm_tools for each machine 2.2.2
and platform that will be used as a server.

3. On each of these servers, unpack beta_lm_tools and execute the command: 2.2.4
& 2.2.5
beta_lm -host_key

Store the outcome of the above command, which consists of the beta_lm version,
the machine’s hostname, the machine's ethernet card MAC address and a string of
forty (40) characters, like:

BETA LM v7.0
BETA LM Host Name = Gauss
MAC = 00:0f:b0:43:34:9a
BETA LM Host Key = 200a025ec00b5f5e0f1b2e1b3d5e020bd04e5144

On WINDOWS systems only, the administrator has the option to extract the above
key based on another network interface, namely USB or WiFi. To produce such a key,
use the command:

beta_lm -host_key -ni [network interface, e.g. USB | WiFi]

4. Provide the above to BETA CAE Systems. Using these data, BETA CAE Systems will 2.2.6
generate the corresponding license file, usually called license.dat & 5.1

5. Copy the license.dat file on each server and install the beta_lm license daemon using 2.2.7
the commands:

Linux Systems:
beta_lm -f [full_path_to]license.dat -L
[full_path_to]license.log

BETA CAE Systems Page 2

BETA LM Setup Guide

Windows Systems:
beta_lm -install -f [full_path_to]license.dat -L
[full_path_to]license.log

Alternatively, the single name of the license (license.dat) and the license.log files
can be used, if navigated to the directory where the license file is located.
If the administrator used a USB or a WiFi network interface to extract the server
host key, then this interface should also be declared during installation:

beta_lm -install -ni [USB | WiFi] -f

[full_path_to]license.dat -L [full_path_to]license.log

Start the "BETA LM Service" from:

Control Panel > Administrative Tools > Services

6. Verify that beta_lm is up and running on each server, using the command: 2.2.7

beta_lm_stat -h server_name

The outcome of the above command will display the features available within the
license.dat file.
Note that in the "hardware failover" redundant server scheme, only the server that is
currently the "master" will respond.

7. Modify the BETA_LIC_SRV environment variable to match the server settings. 6.1.1
For example, in the three server "hardware failover" scheme, one can set a & 6.1.2
“permanent” environment variable with BETA_LIC_SRV as a name and
port@server1,port@server2,port@server3 as a value.

8. Launch a licensed application (e.g. ANSA, META) using the provided execution 6.1
scripts.

For troubleshooting actions please refer to section 8.

BETA CAE Systems Page 3

BETA LM Setup Guide

0.2. Updating to newer version

When updating to a newer version of beta_lm_tools and in case that the server machines have not
changed, one needs to follow the steps as described below.

Action Paragraph
1. Terminate the old version of beta_lm_tools. 3.1.1

2. Log on to BETA CAE Systems server and download beta_lm_tools for each machine 2.2.2
and platform that are used as a server.

3. On each of these servers, unpack beta_lm_tools and install the beta_lm license 2.2.4
daemon using the commands: & 2.2.7

Linux Systems:
beta_lm -f [full_path_to]license.dat -L
[full_path_to]license.log

Windows Systems:
beta_lm -install -f [full_path_to]license.dat -L
[full_path_to]license.log
and start the "BETA LM Service" from:
Control Panel > Administrative Tools > Services

beta_lm -install -ni [USB | WiFi] -f

[full_path_to]license.dat -L [full_path_to]license.log

4. Verify that beta_lm is up and running on each server, using the command: 2.2.7

beta_lm_stat -h server_name

When updating to a newer version of beta_lm_tools and in case that the server machines have changed
or they are Virtual Machines one should follow the steps as described in section 0.1.

BETA CAE Systems Page 4

BETA LM Setup Guide

Section 1.
Introduction to beta_lm_tools
1.1. Basic components
beta_lm_tools is the license manager package for use with all products licensed by BETA CAE
Systems and should be downloaded and installed on all machines that are designated as license
servers. The package contains the following:

 beta_lm: license daemon that handles the initial contact and communication with the
licensed application through a TCP/IP network protocol. The communication itself is
machine independent, so the licensed application and the license daemon can be running on
different platforms and different operating systems

 beta_lm_stat: a reporting tool that provides information on license usage

 beta_lm_kill_user: a tool to terminate process of specific users

 beta_lm_control: a tool to communicate with the license manager for various tasks

 an optional administration options file (usually called license.opt) that can be used by the
license administrator to control various operating parameters of beta_lm. All configurable
parameters that appear in the administration options file remain within the license rights
granted by BETA CAE Systems

 related documentation on the installation and maintenance of beta_lm_tools

Upon installation, the beta_lm license daemon searches for and reads the license file, usually called
license.dat. This is a standard ASCII file storing all licensing information necessary for the proper
and uninterrupted use of the licensed application. This information is related to the license servers
and the respective communication ports, the licensed software packages and features that the
customer can use etc. The license file is created by BETA CAE Systems in accordance to the
requirements set by the customer and is installed by the license administrator.

1.2. Overview of features

The main features of the beta_lm licensing system are the following:

 License server redundancy: two redundancy schemes are currently available - one for load
distribution using more than one servers and one for hardware failover protection

 Flexible short term licensing

 Group licensing: where a group of specific software products or software features can be
set to hold a specific amount of the total available licenses

 Shared licensing: multiple executions of the same application by the same user on the same
machine/console will occupy a single license

 Idle User timeout and Kill User functionality

BETA CAE Systems Page 5

BETA LM Setup Guide

 On-Line statistics and Logging

1.3. Hardware requirements

Minimum hardware requirements for the installation of beta_lm_tools package are given below:

MacOS 32bit OS Version 64bit OS Version

MacOS Darwin 8.7.3 or later

LINUX

AMD Athlon, glibc 2.2 AMD Athlon 64, glibc 2.3.2

INTEL Pentium IV, glibc 2.2 AMD Athlon 64FX, glibc 2.3.2
AMD Opteron, glibc 2.3.2
INTEL Xeon EM64T, glibc 2.3.2

WINDOWS

AMD Athlon, Win2K SP3, WinXP SP1 AMD Athlon, WinXP Pro x64, SP1
INTEL Pentium IV, Win2K SP3, WinXP SP1 INTEL Pentium IV, WinXP Pro x64, SP1
Windows Server 2003/2008 Windows Server 2003/2008

BETA CAE Systems Page 6

BETA LM Setup Guide

Section 2.
Installing beta_lm_tools
2.1. Overview of actions
The license administrator should take the following actions prior to installing the license
management package:

 Select a suitable license server scheme and decide on the platforms to be used as servers
 Download beta_lm_tools package for the above platforms
 Provide to BETA CAE Systems all information needed to generate a valid license file
 Receive a valid license file

Once the license file is received, then

 beta_lm license daemon must be launched on all license servers

Details on these actions are given below.

2.2. Installation procedure

2.2.1. Select a suitable license server scheme

The beta_lm license management system supports a stand-alone scheme and two server
redundancy schemes:

 Stand-alone Scheme: In this case beta_lm is installed in a single machine that is designated
by the customer as the license server. The server responds to all requests for license and
serves the total number of available licenses. The stand-alone scheme is considered the
default, unless a redundancy scheme is explicitly specified by the customer.

 Hardware Failover Scheme: This is a quorum scheme, i.e. a scheme of three license servers
where if any two of the three machines are up and running, the system is functional and
serves the total number of licenses. This scheme is commonly known as two-over-three
scheme and is designed to provide hardware failover protection.

 Multiple Servers Scheme: The total number of licenses can be distributed (equally or not) to
any number of machines that will be used as alternate license servers. Under this scheme,
each time a license is requested, the client will try to engage this license from the first server.
Upon denial, the client will automatically request license from the next available server and
so on, until it succeeds or reaches the end. This type of redundancy is best suited for
distributing license requests, but has the disadvantage that if one server becomes
unavailable, the corresponding licenses that this server distributes become unavailable as
well.

2.2.2. Download beta_lm_tools

In order to get the beta_lm_tools license management package follow these steps:

BETA CAE Systems Page 7

BETA LM Setup Guide

 Decide on the machine(s) that will be used as license server(s)

 Visit http://www.beta-cae.com and sign in to BETA CAE Systems secure site
 Enter the LICENSE MANAGER section, under the [Downloads] area, located on the left.
 Locate the latest version of BETA_LM_TOOLS package and switch into the respective folder
 Download the compressed files that represent the hardware platforms to be used as license
servers:
MacOS / LINUX Platforms WINDOWS Platforms
beta_lm_tools_[version]_[platform].tar.gz beta_lm_tools_[version]_[platform].zip

For example,

- to install beta_lm_tools v7.0 on a Linux 32bit machine, you need to download the
beta_lm_tools_v7.0_linux.tar.gz file

- to install it on a 64bit WinXP platform, you need to download the

beta_lm_tools_v7.0_win64.zip file

 Optionally, download the license administration options file, license.opt

2.2.3. Verification of the download using Message Digest-5 (MD5) hash function

A. MacOS / LINUX Platforms

On the download list of beta_lm_tools you will notice that each compressed file has a respective
md5sum file. This can be used to verify that the compressed file was downloaded correctly
using the standardized MD5 checksums.

For example, imagine that you need to verify the correctness of beta_lm_tools_v7.0_linux.tar.gz.
To do so, download the beta_lm_tools_v7.0_linux.tar.gz_md5sum file and place in the same
location as beta_lm_tools_v7.0_linux.tar.gz:

PlatformFiles
beta_lm_tools_v7.0_linux.tar.gz,
beta_lm_tools_v7.0_linux.tar.gz_md5sum

Then open a command shell, switch into this location where these files reside and type the
command:
md5sum -c beta_lm_tools_v7.0_linux.tar.gz_md5sum
If the outcome of the above command is OK, then the compressed file was downloaded
correctly; if not, you need to download it again.

B. WINDOWS Platforms
If the Windows version of the beta_lm_tools package is downloaded on a LINUX machine, then
its correctness can be verified as above, by downloading the respective md5sum file and using
the built-in md5sum command. For example:

PlatformFiles
beta_lm_tools_v7.0_win32.zip
beta_lm_tools_v7.0_win32.zip_md5sum

Then open a command shell, switch into the location where the above files reside and type the
command:
md5sum -c beta_lm_tools_v7.0_win32.zip_md5sum

BETA CAE Systems Page 8

BETA LM Setup Guide

If the outcome of the above command is OK, then the compressed file was downloaded
correctly; if not, you need to download it again.

However, if the Windows version of beta_lm_tools package is downloaded on a Windows

machine, then a third party tool should be used for the verification, since Windows may not have
a built-in md5sum utility. Please refer to http://en.wikipedia.org/wiki/Md5sum

2.2.4. Unpack beta_lm_tools package

A. MacOS / LINUX Platforms

 open a command shell and switch into the location where the beta_lm_tools package files
reside
 unpack the package:

tar -zxvf beta_lm_tools_v7.0_linux.tar.gz

 when unpacked, the following directory structure will be created:

directory structure notes

/beta_lm_tools  root-folder of
beta_lm_tools package
/linux  sub-folder indicating the
current platform
beta_lm
beta_lm_stat contents of beta_lm_tools
beta_lm_kill_user package
beta_lm_control

 Optionally, if you have downloaded the license administration options file license.opt,
copy this file to the location of the beta_lm_tools files, so the contents of the beta_lm_tools
package now become:

directory structure notes

/beta_lm_tools  root-folder of
beta_lm_tools package
/linux  sub-folder indicating the
current platform
beta_lm
beta_lm_stat
beta_lm_kill_user
contents of beta_lm_tools
beta_lm_control package
license.opt

B. WINDOWS Platforms
 Open a file explorer and double click on the beta_lm_tools compressed zip file. A currently
installed archive package (like WinZIP, WinRAR) or the Windows built-in tool will be launched
 Select a suitable location to unpack beta_lm_tools

NOTE: It is recommended to avoid paths with empty spaces, like ..\Program files\ etc. and prefer
an exemplary path, like e.g. C:\beta_lm\ etc

 when unpacked, the following directory structure will be created:

directory structure notes
\beta_lm_tools  root-folder of
beta_lm_tools
package

BETA CAE Systems Page 9

BETA LM Setup Guide

\win32  sub-folder indicating

the current platform
beta_lm.exe contents of
beta_lm_stat.exe
beta_lm_kill_user.exe beta_lm_tools
beta_lm_control.exe package

 Optionally, if you have downloaded the license administration options file license.opt, copy
this file to the location of the beta_lm_tools files. So, the contents of the beta_lm_tools
package now become:

directory structure notes

\beta_lm_tools  root-folder of
beta_lm_tools
package
\win32  sub-folder indicating
the current platform
beta_lm.exe
beta_lm_stat.exe contents of
beta_lm_kill_user.exe beta_lm_tools
beta_lm_control.exe package
license.opt

2.2.5. Information required to build a valid license file

In order to build a valid license for the selected license scheme, BETA CAE Systems requires three
pieces of information for all machines that will be used as license servers. This information, its
description as well as the respective command that should be used to obtain it is given in the table
below:

command
Item description
(all platforms)
name by which this machine is
1 hostname identified within the customer's
network beta_lm -host_key
2 MAC address media access control address
3 host key beta_lm alphanumeric string

Important in WINDOWS platforms only: By default, beta_lm targets the ethernet card in order to
generate the required host key. However, in Windows platforms only, the user can explicitly ask to
generate a host key based on an existing USB or WiFi installed network adapter. To do so, the -ni
(standing for network interface) flag should be used, followed by an argument pointing to the
desired network interface:

Item description command (WINDOWS only)

name by which this machine is
beta_lm -host_key -ni USB
1 hostname identified within the customer's
network or
2 MAC address media access control address beta_lm -host_key –ni WiFi

beta_lm alphanumeric string based

3a host key from USB beta_lm -host_key -ni USB
on a USB network interface
beta_lm alphanumeric string based on
3b host key from WiFi beta_lm -host_key –ni WiFi
a wireless interface

NOTE: In both LINUX and WINDOWS platforms, the required host key can also be generated based
on the machine’s Universally Unique Identified (UUID), by using the -ni flag, followed by the
argument UUID:

BETA CAE Systems Page 10

BETA LM Setup Guide

Item description Command

beta_lm alphanumeric string beta_lm -host_key -ni UUID
1 host key from UUID
based on the UUID

The process above should be followed on all machines that are designated as license servers. For
example, for a three server hardware failover scheme the customer should provide three sets of
information, one for each server:

server1 command response

1 hostname Gauss
2 MAC beta_lm -host_key 00-11-D8-AA-5C-3C
3 host key 200a025ec00b5f5e0f1b2e1b3d5e020bd04e5144
server2 command response
1 hostname Riemann
2 MAC beta_lm -host_key 00-11-D8-AA-5B-FD
3 host key 200a025ec00be1b3d5e020bd04e51445f5e0f1b2
server3 command response
1 hostname Hilbert
2 MAC beta_lm -host_key 00-14-22-DC-C6-EC
3 host key 200a025ab5f5e0f1b2e1bec003d5ebd04e510203

2.2.6. Receive a valid license file

Upon acceptance of the above information, BETA CAE Systems will proceed to the generation of a
valid license file, usually called license.dat. This file should be placed to all license server machines,
preferably at the same location where beta_lm_tools files reside. Thus, the contents of the
beta_lm_tools for a 32bit windows will become:

directory structure notes

\beta_lm_tools  root-folder of beta_lm_tools
package
\win32  sub-folder indicating the
current platform
beta_lm.exe
beta_lm_stat.exe
beta_lm_kill_user.exe contents of beta_lm_tools
beta_lm_control.exe package
license.opt
license.dat

Details on the contents of the license file are given in a dedicated paragraph later.

2.2.7. Launching the beta_lm license manager

The license manager is installed by the license administrator using the beta_lm command with the
appropriate options. When this command is invoked, beta_lm will look for a valid license file at the
location indicated by the administrator. The described process must be followed for all machines
that will be used as license servers.

A. MacOS / LINUX Platforms

 open a command prompt and switch into the folder containing the beta_lm_tools files,
for example:
cd ~/beta_lm_tools/linux_64

 issue the command:

BETA CAE Systems Page 11

BETA LM Setup Guide

beta_lm -f ~/beta_lm_tools/linux_64/license.dat -L
[full_path_to]license.log
NOTE: Alternatively and given that we have navigated to the directory where the license file is
located, the single name of the license.dat and license.log files can be used, instead of the
full file address.
The above command will launch the beta_lm license daemon, read the license file
(license.dat) and write any related messages into a log file (license.log).

 Verify that beta_lm is installed and that the total number of available licenses is correct
using the command:
beta_lm_stat -h server_name

the result should, for example, look like:

Trying 6007@server_name ....

Found License daemon on server_name

PACKAGE:FEATURE | MAX CREDIT | CREDIT USED | USED PERCENTAGE | USAGE

PRE_POST:ANSA | 5000 | 100 | 2(%) | 1
PRE_POST:ANSA_BATCH | 5000 | 0 | 0(%) | 0
second section
PRE_POST:META_POST | 5000 | 0 | 0(%) | 0
PRE_POST:ANSA_CATIA_V4 | 250 | 0 | 0(%) | 0
NEW_ANSA_CATIA_V5 | 250 | 0 | 0(%) | 0

PACKAGE USAGE REPORT

PACKAGE | MAX CREDIT | CREDIT USED | USED PERCENTAGE third section

PRE_POST | 5000 | 100 | 2(%)

At the first section, we get information on the active licensed packages along with the
duration and the corresponding credits of each package.

At the second section, we get information about the current usage of each feature,
i.e. of each licensed application that is currently running.

At the third section, the current usage per package is shown. The information is available
both as an absolute value of used credits, as well as a usage percentage, over the total
amount of credits available for this package.

B. WINDOWS Platforms

 open a command prompt and switch into the folder containing the beta_lm_tools files,
for example:
cd c:\beta_lm_tools\win32

 by default beta_lm considers that the host key used to produce the license.dat file is based
on the ethernet card of the server machine. In this default case, the beta_lm installation
command should be:

BETA CAE Systems Page 12

BETA LM Setup Guide

beta_lm -install -f C:\beta_lm_tools\win32\license.dat -L

[full_path_to]license.log

However, if a USB or WiFi network interface was used to build the host key, then the same
network interface must be declared at the installation command. For example, in the USB
case the installation command should be:

beta_lm -install -ni USB -f C:\beta_lm_tools\win32\license.dat -L

[full_path_to]license.log

NOTE: Alternatively and given that we have navigated to the directory where the license file is
located, the single name of the license.dat and license.log files can be used, instead of the
full file address.
The above command will install a SERVICE for the beta_lm license daemon.
At this stage, licenses are still not available for use, since the SERVICE is not yet "Started".

 Go to Start > Control Panel > Administrative Tools and double-click on Services.
This action will display a list with all services installed on the machine.

 Locate the BETA LM Service and verify that is has a Stopped status.

 Right-click on the BETA LM Service and ask to Start it. During initiation of the BETA LM
Service, the beta_lm license daemon is activated, it reads the license file (license.dat) and
writes any related messages into the log file (license.log).

 Right-click again on the BETA LM Service, go to Properties and, under the General tab.
If needed, change the Startup Type to Automatic. This will force the beta_lm license daemon
to automatically start after each reboot.

 Verify that beta_lm is properly installed and that the total number of available licenses is
correct using the command:
beta_lm_stat -h server_name

The result should, for example, look like:

Trying 6007@server_name ....

Found License daemon on server_name

PACKAGE:FEATURE | MAX CREDIT | CREDIT USED | USED PERCENTAGE | USAGE

PRE_POST:ANSA | 5000 | 100 | 2(%) | 1
PRE_POST:ANSA_BATCH | 5000 | 0 | 0(%) | 0
PRE_POST:META_POST | 5000 | 0 | 0(%) | 0 second section
PRE_POST:ANSA_CATIA_V4 | 250 | 0 | 0(%) | 0
NEW_ANSA_CATIA_V5 | 250 | 0 | 0(%) | 0

PACKAGE USAGE REPORT

third section
PACKAGE | MAX CREDIT | CREDIT USED | USED PERCENTAGE
PRE_POST | 5000 | 100 | 2(%)

At the first section, we get information on the active licensed packages along with the
duration and the corresponding credits of each package.

BETA CAE Systems Page 13

BETA LM Setup Guide

At the second section, we get information about the current usage of each feature, i.e. of
each licensed application that is currently running.

A note on launching the beta_lm license manager on Virtual Machines

Root privileges are required when running beta_lm on a Linux Virtual Machine. The only exception is
when the Virtual Machine is running on a Xen hypervisor. More details are available in the
Confluence KB article: License Manager for Virtual Machines

Troubleshooting actions for installation problems are given at the end of this document.

2.3. Supported beta_lm features

A short description of the available features of the beta_lm license management system is
summarized in the following table:

Available
Feature Description through

The total number of licenses can be distributed (equally or not)

Server to a number of machines that will be used as alternate license
Redundancy servers. Two redundancy schemes are available: a hardware license.dat
failover and a license distribution scheme through multiple
servers

Any number of additional short term licenses that will cover

Flexible Short peak workload will be provided upon request. These will be
license.dat
Term Licensing integrated into the existing licensing file and will expire on
prescribed dates.

Combinations of specific software products as well as software

features can be set to hold a specific amount of the total
Group Licensing license.dat
available credits, provided by the standard license system (e.g.
metapost, ansa-catia).

No extra licenses will be held for multiple software executions

Shared Licensing provided that these are requested from the same user and on license.dat
the same physical machine/console.

BETA CAE Systems Page 14

BETA LM Setup Guide

If a user remains idle within a specific time interval, then the

current session will be considered as disconnected and the
corresponding licenses will become available to other users.
licence.opt
Disconnect Idle Note that the idle session will not be lost, but any attempt to
and
Users resume working will subject to current license availability.
license.dat
If no licenses are available, a dialogue menu appears giving the
option to Retry to acquire license or to save the working session
and/or exit.

Specific filters can deny, limit or exclusively allow usage of licence.opt

Configure Feature particular features by particular users. Likewise, the idle user
usage and Idle user and
timeout can be configured to be applicable only to particular
timeout rules users or during specific timeframes within a day. beta_lm_control

The Administrator (with full administrative privileges) has the

"Kill" Selected Users option to terminate the processes of a specific user, or to beta_lm_kill
terminate processes on specific machines.

A general log-file records all activities related to license license.log

requests, denials due to saturation, license usage, application
Statistics & Logging versions, exit conditions, server changes etc.
Also, on-line statistics report the current licensing status. beta_lm_stat

BETA CAE Systems Page 15

BETA LM Setup Guide

2.4. More on FEATUREs, CREDITs and PACKAGEs

There are some important keywords used in every portion of the license file that control the way that
licenses are distributed among the licensed applications. These keywords are:

 FEATURE: It represents any application or procedure that is asking for a license.

For example, ANSA or META constitute FEATURES. In addition, procedures like running a
script (ANSA_BATCH), META_POST_BATCH post-processing, ANSA_CATIA_V4 translation
etc. are FEATURES as well. FEATURES can be stand-alone or can belong to a PACKAGE.

 PACKAGE: This defines a group of FEATURES, i.e. a group of licensed applications or

procedures (as defined above). FEATURES that belong to the same PACKAGE draw credits
from the pool of credits that is assigned to this PACKAGE.

 WEIGHT: It is the currency of the transaction between the license server and the licensed
FEATURE.

 CREDIT: It represents the total amount of credits that become available through the license
file, as well as the amount of credits necessary to launch a specific application or procedure.

2.4.1. FEATUREs and their important keywords (WEIGHT, CREDIT and OPTIONS)

The stand-alone applications that our licensing system, beta_lm, is called to manage are:

 ANSA
 META
 CAD Translators
 KOMVOS
 RETOMO
 NEERE
 …and others…

In addition to the above, there exist features (i.e. aspects of functionality or procedures) embedded
in these applications that are also licensed when used, for example:

 special “operation modes” of an application (e.g. running an automatic, unsupervised

instance of the application without any user interface, for example ANSA Batch Mesh, when
running through script)
 the conversion of a CAD-data file (e.g. conversion of a CATIA V4 or V5 file into ANSA format)
 a special reduced environment for the communication with a third-party tool (e.g. the TOSCA
optimizer)
 EPILYSIS solver (when called though ANSA)
 Machine Learning Environment (available through KOMVOS)
 …and others…

In our licensing system language, all above are called FEATURES:

 FEATURE=ANSA
 FEATURE=META_POST
 FEATURE=NEW_ANSA_CATIA_V5

BETA CAE Systems Page 16

BETA LM Setup Guide

 FEATURE=ANSA_BATCH
 FEATURE=ANSA_TOSCA
 FEATURE=TOMO
 ... … …

In essence, a FEATURE can represent either a stand-alone application or an aspect of its

functionality.
When an instance of a FEATURE is called to run it will need to engage a specific number of credits.
This number is determined by the keyword WEIGHT:

 FEATURE=ANSA, WEIGHT=100 (ANSA needs 100 credits to launch)

 FEATURE=META_POST, WEIGHT=33 (META needs 33 credits to launch)
 FEATURE=NEW_ANSA_CATIA_V5, WEIGHT=25 (a CATIA V5 to ANSA translation needs 25
credits)
 FEATURE=ANSA_TOSCA, WEIGHT=30 (the reduced ANSA-TOSCA Environment needs 30
credits to launch)
 FEATURE=TOMO, WEIGHT=100 (RETOMO needs 100 credits to launch)
 ... … …

As mentioned before, the CREDIT determines the maximum number of credits that a FEATURE is
allowed to engage:

 FEATURE=ANSA, WEIGHT=100, CREDIT=2300 (total ANSA credits cannot exceed 2300)

 FEATURE=META_POST, WEIGHT=33, CREDIT=100 (total META credits cannot exceed 100)
 FEATURE=TOMO, WEIGHT=100, CREDIT=100 (total RETOMO credits cannot exceed 100)
 ………

In other words, the CREDIT keyword assigns an individual pool of credits that can be used by this
FEATURE only.

Finally, the OPTIONS keyword determines whether a new instance of the FEATURE will engage
additional credits or not, if launched by the same user on the same machine. The ‘shared’ OPTIONS
implies that no extra credits whereas the ‘blank’ OPTIONS implies additional credits.

 FEATURE=ANSA, WEIGHT=100, … … …, OPTIONS=’shared’ (no extra credits for new ANSA

instances)
 FEATURE= NEW_ANSA_CATIA_V5,WEIGHT=25,… … …, OPTIONS=’ ‘ (a new CATIA V5
translation would need another 25 credits)

2.4.2. The pre-post PACKAGE

The PACKAGE is a collection of FEATURES. The most frequently used PACKAGE is the PRE_POST:

 PACKAGE=PRE_POST

Each PACKAGE contains a CREDIT keyword to designate a pool of credits that becomes available to
its members:

 PACKAGE=PRE_POST, CREDIT=2300

In essence, each FEATURE within a license file can exist either independently or as a member of a
PACKAGE:

BETA CAE Systems Page 17

BETA LM Setup Guide

 When a FEATURE is standing independently within a license file, then this FEATURE
occupies credits from its own, individual, pool of credits that is defined in the CREDIT= value
of the FEATURE
 When a FEATURE becomes a member of a PACKAGE, then the number of credits stated in
the CREDIT= value of the FEATURE represent the maximum number of credits that this
FEATURE is allowed to engage from the total number of credits that this PACKAGE can
deliver.

A license file may contain more than one PRE_POST PACKAGE, each distributing a different pool of
credits to its contents (FEATUREs):

PACKAGE=PRE_POST, CREDITS=2432
FEATURE=ANSA, PACKAGE=PRE_POST
FEATURE=ANSA_BATCH, PACKAGE=PRE_POST
FEATURE=ANSA_CATIA_V4, PACKAGE=PRE_POST
FEATURE=ANSA_TOSCA, PACKAGE=PRE_POST
FEATURE=ANSA_UG, PACKAGE=PRE_POST
FEATURE=META_POST, PACKAGE=PRE_POST
FEATURE=META_POST_BATCH, PACKAGE=PRE_POST
FEATURE=META_POST_OLD, PACKAGE=PRE_POST

Pool of 2432 credits,

serviced by
PACKAGE=PRE_POST.
These credits are accessible
only to the FEATUREs of
the PRE_POST Package
(see above)

BETA CAE Systems Page 18

BETA LM Setup Guide

2.4.3. Examples

Now, let’s try to interpret some sections of the license file in order to gain a better understanding of
these keywords, their interaction and how they control licensing:
21 SN=1,PACKAGE=PRE_POST,CREDIT=2432,ISU=10-oct-2014,EXP=31-jan-2015,SIGNATURE=1e\

 PACKAGE=PRE_POST: A package called PRE_POST is defined

 CREDIT=2342: This package can serve a total of 2432 credits to its FEATURES
(see below)
 The package was issued on 10-oct-2014 and will expire on 31-jan-2015
24 SN=1,FEATURE=ANSA,PACKAGE=PRE_POST,WEIGHT=100,CREDIT=2300,OPTIONS='shared',SIG\

 FEATURE=ANSA: A licensed application called ANSA is defined as a FEATURE

 PACKAGE=PRE_POST: This FEATURE (i.e. ANSA) belongs to a PACKAGE,
namely the PRE_POST package
 WEIGHT=100: The WEIGHT of ANSA is 100 credits; so when ANSA is called to
launch, the license server will have to engage 100 credits; these will have to be
deducted from the total of 2432 credits that the PRE_POST package can serve
(line 21)
 CREDIT=2300: There is an upper limit on the total number of credits that a
FEATURE can occupy within a PACKAGE. In this example, this limit for ANSA is
set by CREDIT=2300. So, although the PRE_POST package can serve a total of
2432 credits (as seen in line 21), ANSA can utilize only 2300 credits; in other
words, there can be no more than 23 individual ANSA instances running at the
same time. It will be seen later that the remainder 132 credits of the package
are utilized by META
 OPTIONS=’shared’: FEATURES having the ‘shared’ option will not engage
additional credits if launched by the same user on the same machine. We have
seen in this example that the first instance of ANSA will need 100 credits to
launch; but, since ANSA is ‘shared’, any additional instance launched by the
same user on the same machine will continue to use the same 100 credits
engaged by the first ANSA instance.
30 SN=1,FEATURE=ANSA_CATIA_V4,PACKAGE=PRE_POST,WEIGHT=25,CREDIT=2300,OPTIONS=' ',\

 FEATURE=ANSA_CATIA_V4: A licensed procedure, the conversion of CAT-

IA_V4 files into ANSA native format, is defined as a FEATURE
 PACKAGE=PRE_POST: This procedure belongs to the PRE_POST package; it
will therefore engage credits from the same pool of credits that is made avail-
able to all applications that belong to PRE_POST
 WEIGHT=25: When the CATIA_V4 to ANSA conversion procedure is launched, it
will ask for and engage 25 credits
 CREDIT=2300: The maximum number of the total PRE_POST credits that can
be engaged by this feature is limited to 2300
 OPTION=' 'Unlike ANSA in line 24, this feature is not ‘shared’. This effectively
means that each of the CATIA_V4 to ANSA instances will ask for and will have
to engage 25 credits (regardless if launched by the same user on the same
machine). In other words, 2 instances will need 50 credits, 3 will need 75 and
so on.

42 SN=1,FEATURE=META_POST,PACKAGE=PRE_POST,WEIGHT=33,CREDIT=2432,OPTIONS='shared'\

 In this line, an application called META is defined, that belongs to the

PRE_POST package. Its WEIGHT is 33 credits so, if called to launch, META will
ask for and engage 33 credits. It is also seen that META is ‘shared’, so addi-

BETA CAE Systems Page 19

BETA LM Setup Guide

tional instances by the same user on the same machine will still use the al-
ready engaged 33 credits
 What is important in line 42 is that the maximum number of credits that META
can use is 2432. This effectively means that (unlike the rest of the licensed
FEATURES), META can use all the credits that PRE_POST package can deliver.

52 SN=1,FEATURE=NEW_ANSA_CATIA_V5,WEIGHT=25,CREDIT=25,ISU=10-oct-2014,EXP=31-jan-\
53 2015,OPTIONS=' ',SIGNATURE=f7f5776ba498a9730fe1ddfdbde52acbde76432ec0ef5809147\

 This is an example of a stand-alone FEATURE. As such, the

NEW_ANSA_CATIA_V5 does not belong to any PACKAGE, it has its own validity
period (ISU and EXP) and it will use its own pool of credits (CREDITS=25). Each
instance of this feature will engage 25 credits (WEIGHT=25), so effectively
there can be only 1 instance running at any given time. Notice also that the
FEATURE is not ‘shared’, meaning that if additional instances were to be
launched, each would have to engage 25 credits.

118 SN=5,FEATURE=TOMO,WEIGHT=100,CREDIT=100,ISU=28-jan-2020,EXP=31-jan-2021,OPTION\
S='shared',SIGNATURE=fdbf1abf1313fa0cccfefd934b73b0aa08e4e16438d55a10d0dc38f74\

 This is an example of a stand-alone FEATURE, corresponding to an application

called RETOMO. As such, the TOMO does not belong to any PACKAGE, it has
its own validity period (ISU and EXP) and it will use its own pool of credits
(CREDITS =100). Each instance of this feature will engage 100 credits
(WEIGHT=100), so effectively there can be only 1 instance running at any given
time. Notice also that the TOMO FEATURE is ‘shared’, so additional instances
by the same user on the same machine will still use the already engaged 100
credits.

BETA CAE Systems Page 20

BETA LM Setup Guide

2.5. BETA Licensed applications: credits/user

BETA License Manager should be up and running prior to the installation of any BETA application.

 Pre-processing Software System ANSA, (100 credits/user)

 ANSA Batch Mode (100 credits/session)
 ANSA CAD-data Translation for CATIA V4 (25 credits/user)
 ANSA CAD-data Translation for UG/NX (25 credits/user)
 ANSA-TOSCA feature for optimization (30 credits/user)
 Post-processing Software System MΕΤΑ, (33 credits/user)
 MΕΤΑ Batch Mode (33 credits/session)

 ANSA CAD-data Translation for CATIA V5 (25 credits/user)

 ANSA CAD-data Translation for Pro Engineer (100 credits/user)
 ANSA CAD-data Translation for JT Open (25 credits/user)
 RETOMO (100 credits/user)
 SPDRM / Simulation Process, Data and Resources Management (follows separate licensing
scheme)

 EPILYSIS solver requires the corresponding license FEATURE (100 credits/user)

When EPILYSIS is called through ANSA, by selecting SOLVE IN ANSA, the ANSA session
freezes and EPILYSIS starts solving, switching the occupied credits from ANSA to EPILYSIS
FEATURE. When solving finishes, credits are switched back to ANSA.

If the option SOLVE OUT OF ANSA is selected, then ANSA remains active for the user to
continue working and EPILYSIS starts by occupying additional 100 credits from the EPILYSIS
FEATURE, (200 credits in total).

If the user needs to run EPILYSIS from ANSA and then load (automatically) the results in
META which is launched, 133 credits are in overall occupied.

Finally, when EPILYSIS solver is called independently, through a command prompt,

100 EPILYSIS FEATURE credits are used.

 KOMVOS does not require a specific license FEATURE.

KOMVOS occupies 100 credits, taken from the ANSA FEATURE. Namely, when ANSA and
KOMVOS are both up and running, 100 credits are in overall occupied. (100 credits/user)
 Machine Learning Environment, available through KOMVOS, requires the ML_SERVER license
FEATURE (100 credits/user).

 NEERE requires 3 specific license FEATURES:

NEERE_SERVER
NEERE_ROOM
NEERE_USER

BETA CAE Systems Page 21

BETA LM Setup Guide

The server requires 100 credits.

For every active room (i.e. at least one user is in the room) 10 credits are required.
For every user that is active in a room 1 credit is required.

BETA CAE Systems Page 22

BETA LM Setup Guide

Section 3.
Options and usage of
License Administration Tools
3.1. The beta_lm options
As discussed in earlier paragraphs the beta_lm command initiates the license daemon. The
corresponding command is:

beta_lm -f [full_path_to_the_license_file]*

NOTE: Alternatively, the single name of the license.dat and license.log files can be used, if navigated
to the directory where the license file is located.
Additional flags are:

-L [full_path_to_the_log_file]: write report log information to this file (recommended)

-h [hostname or ip_address] : specify the license server machine
-p [portnumber] : specify the communication port
-install : installation option (Windows only)
-debug : run in interactive mode for debugging (Windows only)
-remove : remove the beta_lm service (Windows only)
-host_key : generate a license key based on ethernet adapter
-ni [USB, WiFi] : generate a license key based on USB, WiFi
-noadmin : run beta_lm as a console app in case the user does not
have Administrator rights. In this case, the beta_lm
command should be:

beta_lm -noadmin -f C:\beta_lm_tools\win32\license.dat -L

[full_path_to]license.log

Then a licensed application can start using the flag:

-h port@server_name flag

NOTE: The Command Prompt needs to stay open (Windows only)

* In its simplest form, the "-f" for Linux and "-install -f" flags for Windows would suffice to initiate the
license daemon. However, it is strongly suggested that the "-L" flag followed by a log filename is also
used:
beta_lm -f [full_path_to]license.dat -L [full_path_to]license.log
beta_lm -install -f [full_path_to]license.dat -L
[full_path_to]license.log

In this way the license daemon is able to print in the license.log file useful messages concerning the
service installation, debugging or license monitoring.

BETA CAE Systems Page 23

BETA LM Setup Guide

3.1.1. Terminating beta_lm

A. LINUX Platforms
 open a command prompt and terminate beta_lm by issuing a "kill" command followed by any
signal - except "-9" - and the PID of the parent beta_lm process. It is recommended to use
the "-3" (QUIT) or "-15" (TERMINATE) signal for this action.
NOTE: Killing beta_lm using the "-9" signal will cause abnormal termination and the licensing
system will not function correctly, especially in cases where a server redundancy scheme is
used.

B. WINDOWS Platforms
 In order to terminate beta_lm in WINDOWS systems, the administrator should access the
"BETA LM Service" from Control Panel > Administrative Tools > Services and select to "stop"
the service.

3.2. The beta_lm statistical tools

Basically there are two statistical tools for the BETA License Manager service:

First, the beta_lm_stat report, which is used to provide information about the current licensing
status.
Second, the license.log file (optional), where the full license communication between the License
Manager and the client machines is recorded, along with several other useful information.

3.2.1 The beta_lm_stat options

The corresponding command is:

beta_lm_stat –options

with options:
-h [server hostname] : specify the server that information is required from
-a : request individual information about all users
-u [username] : request information about a specific user
-u [username@hostname] : to request information about a specific user, at a
specific host
-s : request extra information about shared sessions. Must
be combined with one of the -a,-u flags
-x : request extra information about active features
(application version, OS, GPU info etc). Must be
combined with one of the -a,-u flags

Depending on the used option, the following information is acquired:

(a) using the -h [server hostname] flag. For example, if we want to see the status of a
specific license server called server_name, we type:

beta_lm_stat -h server_name

and the result looks like:

Trying 6007@server_name

Found License daemon on server_name

BETA CAE Systems Page 24

BETA LM Setup Guide

PACKAGE:FEATURE | MAX CREDIT | CREDIT USED | USED PERCENTAGE | USAGE

PACKAGE USAGE REPORT

PACKAGE | MAX CREDIT | CREDIT USED | USED PERCENTAGE third section

PRE_POST | 5000 | 100 | 2(%)

- At the first section, we get information on the currently licensed packages along with the
duration and the corresponding credits of each package.

- At the second section, we get information about the current usage of each feature, i.e. of each
licensed application that is currently running.

-At the third section, the current usage per package is shown. The information is available both
as an absolute value of used credits, as well as a usage percentage, over the total amount of
credits available for each package.

NOTE: All the above sections are repeated when using the -a and -u flags.

(b) using the -a flag returns information about all active users. We type:

beta_lm_stat –a

and the result looks like:

Trying 6007@server_name ....

Found License daemon on server_name

Usage Report for users: all

PACKAGE:FEATURE | MAX CREDIT | CREDIT USED | USED PERCENTAGE | USAGE

PRE_POST:ANSA | 5000 | 400 | 8(%) | 4
PRE_POST:META_POST | 5000 | 0 | 0(%) | 0 second section
PRE_POST:ANSA_OLD | 5000 | 0 | 0(%) | 0 (as before)
PRE_POST:ANSA_CATIA_V4 | 250 | 0 | 0(%) | 0
ANSA_CATIA_V5 | 300 | 0 | 0(%) | 0

PACKAGE USAGE REPORT

third section
PACKAGE | MAX CREDIT | CREDIT USED | USED PERCENTAGE (as before)
PRE_POST | 5000 | 400 | 8(%)

NOTE: A zero PID indicates a shared process.

BETA CAE Systems Page 25
BETA LM Setup Guide

(c) using the -u [username] flag returns information about a specific user. For example, if we
type:
beta_lm_stat -u user2

we will get information about user2 on all machines:

Trying 6007@server_name ....

Found License daemon on server_name

Usage Report for users: user2

PACKAGE:FEATURE | MAX CREDIT | CREDIT USED | USED PERCENTAGE | USAGE

PRE_POST:ANSA | 5000 | 200 | 4(%) | 2
PRE_POST:META_POST | 5000 | 0 | 0(%) | 0
PRE_POST:ANSA_OLD | 5000 | 0 | 0(%) | 0
PRE_POST:ANSA_CATIA_V4 | 250 | 0 | 0(%) | 0
ANSA_CATIA_V5 | 300 | 0 | 0(%) | 0

PACKAGE USAGE REPORT

PACKAGE | MAX CREDIT | CREDIT USED | USED PERCENTAGE

PRE_POST | 5000 | 200 | 4(%)

(d) We can restrict information by indicating the hostname where a user is logged by typing:

beta_lm_stat -u user2@host1

and the result will be:

Trying 6007@server_name ....

Found License daemon on server1.localdomain

PACKAGE:FEATURE | MAX CREDIT | CREDIT USED | USED PERCENTAGE | USAGE

PRE_POST:ANSA | 5000 | 0 | 0(%) | 0
PRE_POST:META_POST | 5000 | 33 | 0(%) | 1
PRE_POST:ANSA_OLD | 5000 | 0 | 0(%) | 0
PRE_POST:ANSA_CATIA_V4 | 250 | 0 | 0(%) | 0
ANSA_CATIA_V5 | 300 | 0 | 0(%) | 0

PACKAGE USAGE REPORT

PACKAGE | MAX CREDIT | CREDIT USED | USED PERCENTAGE

PRE_POST | 5000 | 33 | 0(%)

(e) We can request more information by using the –x and/or –s options, combined with either
–a or –u:

beta_lm_stat -a –x

which will result in additional information in the Usage Report:

BETA CAE Systems Page 26
BETA LM Setup Guide

USER NAME@HOST | FEATURE | PID | START | VERSION | OS |

beta_lm_stat -a –s

which will result in detailed report for all active shared sessions of each user:
Trying 6007@server_name ....

Found License daemon on server_name

Usage Report for users: all

USER NAME@HOST | FEATURE | PID | START

PACKAGE:FEATURE | MAX CREDIT | CREDIT USED | USED PERCENTAGE | USAGE

PRE_POST:ANSA | 5000 | 200 | 4(%) | 2
PRE_POST:META_POST | 5000 | 0 | 0(%) | 0 second section
PRE_POST:ANSA_OLD | 5000 | 0 | 0(%) | 0 (as before)
PRE_POST:ANSA_CATIA_V4 | 250 | 0 | 0(%) | 0
ANSA_CATIA_V5 | 300 | 0 | 0(%) | 0

PACKAGE USAGE REPORT

third section
PACKAGE | MAX CREDIT | CREDIT USED | USED PERCENTAGE (as before)
PRE_POST | 5000 | 200 | 4(%)

The logged users section shows all the active shared sessions in detail. The initial session, that
engaged the license credits, is recorded with a line starting with (+) and holds a zero PID. All the rest
shared sessions are recorded with a line starting with ( | ). In this case, user 1 has launched 2
different ANSA instances, while user2 has launched 1 ANSA instance only. The total credits used are
shown on the rest of the sections, as normal.

BETA CAE Systems Page 27

BETA LM Setup Guide

3.2.2. Monitoring license usage

When the beta_lm license manager is installed using the "-L" flag, the license log file records all the
licensing communication information along with several other useful information. The content of
this log file looks like:
FEATURE USERNAME@HOST PID START
ANSA user1@host1(:0) 2467 Wed Mar 23 21:23:14 2020
ANSA_BATCH user2@host2(:0.0) 1554 Wed Mar 23 21:32:10 2020
META_POST user1@host1(:0) 0 Wed Mar 23 21:33:52 2020
---------- ---------- ---------- ----------

END EXIT_INFO OS Version

Wed Mar 23 21:24:47 2020 NORMAL_PROGRAM_EXIT Windows 21.0.0
Continuation
Wed Mar 23 21:38:02 2020 CLIENT_LOST Linux 20.1.2
of.log file
Wed Mar 23 21:40:24 2020 IDLE_USER_TIMEOUT Windows 21.0.0
---------- ---------- ---------- ----------

where:

FEATURE : corresponds to the running licensed application (e.g. ANSA)

USERNAME@HOST : indicates the user, machine and display console (linux) or session id
(windows) of the running application

PID : the corresponding Process ID (Zero PID indicates a shared feature)

START / END : starting and termination time of the application

EXIT_INFO : indicates the condition under which the application is stopped. Available
messages are:
NORMAL_PROGRAM_EXIT, CLIENT_LOST, IDLE_USER_TIMEOUT,
RELEASED_BY_USER, KILL_USER_BY_ADMIN, TIMED_CREDITS_CHARGED,
FEATURE_RELEASED, NOT ENOUGH PRE_POST CREDITS

OS : the operating system of the machine that the application is launched

Version : the version of the running application (available since ANSA/ META
version 20.1.2 and onwards)

The license.log file also records license request denials due to saturation (NOT ENOUGH PRE_POST
CREDITS). The users that have asked for a license and are currently in the queue are listed and shown
in the .log file. Extra information on the total (the sum of waiting time, so that all the clients in the
queue get a license) and average waiting time is also provided.

Additionally, a more advanced style of the license.log file can be provided. This recording mode is
invoked through the license.opt file (see next chapter ), using the keyword "LOG_STYLE=1".
More specifically, detailed license traffic information, per application session, is reported.
Every single license call, successful or not, is recorded, like shown next:

Mon May 18 14:25:08 2020(betalm) IN: "ANSA" "21.0.0" user@apollon(:0.0) [27349]

Mon May 18 14:26:38 2020(betalm) IN: "ANSA_BATCH" "21.0.0" user@apollon(:0.0) [27629]
Mon May 18 14:26:52 2020(betalm) OUT: "ANSA_BATCH" "21.0.0" user@apollon(:0.0) [27629] (FEATURE_RELEASED)
Mon May 18 14:26:52 2020(betalm) IN: "ANSA" "21.0.0" user@apollon(:0.0) [27629]
Mon May 18 14:27:02 2020(betalm) DENIED: "ANSA" "20.1.2" user2@host8 (:2) [7988]
(NOT ENOUGH CREDITS ( WAITING TIME FROM BETA_LM STARTUP: TOTAL=89702 sec , AVERAGE=150 sec ))
Mon May 18 14:27:03 2020(betalm) OUT:"ANSA" "21.0.0" user@apollon(:0.0) [27629] (NORMAL_PROGRAM_EXIT)
Mon May 18 14:27:13 2020(betalm) OUT:"ANSA" "21.0.0" user@apollon(:0.0) [27349] (NORMAL_PROGRAM_EXIT)

BETA CAE Systems Page 28

BETA LM Setup Guide

It is possible to reset the starting time from which statistics for the license.log are calculated,
without terminating the process (see section 3.4).
All information acquired either from the global log file or through the current licensing status is
suitable for input to standard spreadsheet tools (e.g. EXCEL, OpenOffice etc.) for further statistical
processing.

3.3. The beta_lm_kill_user options

This tool is used in order to terminate the processes of a specific user. The command is:

beta_lm_kill_user –options

with options:

-u [username@hostname] : kill all processes of a specific user at a specific host

-i [proc_id] : kill a specific process-id
-n [hostname] : kill all processes of a specific host

An example of killing a user could be:

beta_lm_kill_user -u user2@host1(:0)

which will kill all processes of user2 that run on host1 using the default display (:0).

NOTE: The beta_lm_kill_user command can be issued only from the user that initiated the
beta_lm daemon (i.e. the Administrator with full administrative privileges). On WINDOWS systems,
the Administrator should be logged in as Root (i.e. as Administrator with full administrative
privileges).

3.4. The beta_lm_control options

This tool is used to communicate with the license manager for various tasks. The appropriate syntax
to be used is:

beta_lm_control –options

with options:

-h [hostname] -reloadopt : define the server hostname and reload the

license.opt file without the need to restart the BETA
LM service
-h [hostname] -resetstats : define the server hostname and reset the time from
which statistics for the license.log are calculated

BETA CAE Systems Page 29

BETA LM Setup Guide

Section 4.
The Administrator Options File
4.1. The administrator options file
The administrator options file (license.opt) is a single text file that can be downloaded from BETA
CAE Systems secure site and used by the administrator in order to configure several parameters of
the licensing system. Its use is optional and it serves cases where the administrator wishes to
customize the behavior of the license service with regards to various features.
One or more valid parameters, as outlined in the next sections, can be used. The file should be
edited accordingly and saved in a specific directory, for example at the directory where the
license.dat is located. Additionally the license file (license.dat) should also be edited, using a reliable
editor, concerning the line starting with: OPTIONS=…. Enter there the full path of the license.opt file
and save.

For example:

################ START OF EDITABLE SECTION

# Replace FULL_PATH_TO in the next line with the full path of the directory
# where license.opt file resides.
OPTIONS=C:/beta-cae/beta_lm_tools_v7.0/win64/license.opt

The license.opt file is read upon the beta_lm service startup. However, it can also be reloaded,
without interrupting the service, using the command:
beta_lm_control -h [hostname] -reloadopt

4.1.1. Idle User Timeout

One of the configurable parameters in the options file is the maximum time (in minutes) that a user
may remain idle, before the corresponding reserved credits are released. In general, as Idle is
considered a user that has not taken any action in ANSA/META for longer than the time defined as
Idle User Timeout. When such a user will take action again, there are two cases:

- If there are available license credits, BETA License Manager will provide the needed credits and
the user will continue working, without any notification
- If there are no available license credits any more, the application will be interrupted, asking the
user to SAVE & Quit or to retry re-acquiring license

The respective syntax in the license.opt file is: IDLE_USER_TIMEOUT=

So if, for example, the administrator wishes license credits to be released after a user being idle for
30 minutes, the keyword that should be used in the options file is:
IDLE_USER_TIMEOUT=30
The minimum acceptable value is 10 minutes. If the IDLE_USER_TIMEOUT parameter is set below
the minimum value (except zero), it will be switched automatically to the minimum, i.e. 10 min. If the
parameter is missing or set to zero, then no limitations are applied.

NOTE: When the Idle User Time Out option is active, the respective notification appears in the
application’s terminal upon start-up. Older application versions report at starting that
IDLE_USER_ TIMEOUT less than 20min is not accepted. In those versions, the idle time setting
automatically switches to 20min, releasing credits after 20min, as expected.

BETA CAE Systems Page 30

BETA LM Setup Guide

Apart from setting the idle time limit, it is also possible to configure the applicability of this limit
per user, group of users, IP addresses or hostnames. The filtering options for configuring the idle
user timeout are applicable since versions 19.1.7, 20.0.4, 20.1.2 and 21.0.0 onwards. It is also
possible to configure the idle time limit to be enabled or disabled during specific timeframes within
the day (since version 21.0.0 onwards). The appropriate syntax and some examples of each filtering
option are provided in the tables below:

Syntax in .opt file Description

IDLE_DISABLE {FEATURE} The idle user timeout will be ignored for the
users=.../groups=..../hosts=.../ips=... defined feature, when launched by the
defined users, groups, hosts or IP addresses.

IDLE_ONLY {FEATURE} The idle user timeout will only be applied to

users=.../groups=..../hosts=.../ips=... the defined feature, when launched by the
defined users, groups, hosts or IP addresses.

IDLE_TIME_RANGE_DISABLE=... The idle user timeout will be ignored during

the defined time range.

IDLE_TIME_RANGE_ONLY=... The idle user timeout will only be applied

during the defined time range.

Example Description
IDLE_DISABLE ANSA users=demo,demo1 The feature ANSA will not be subject to the
idle user timeout for the listed users.

IDLE_DISABLE ANSA groups=group1,group2 The feature ANSA will not be subject to the
idle user timeout for users belonging to the
listed groups.

IDLE_DISABLE ANSA hosts=WIN100,LIN200 The feature ANSA will not be subject to the
idle user timeout when it is launched by the
listed hosts.

IDLE_DISABLE ANSA ips=192.168.2.1,192.168.2.3 The feature ANSA will not be subject to the
IDLE_DISABLE ANSA ips=192.168.2.1-192.168.2.6 idle user timeout when it is launched by the
listed IP addresses.
IDLE_DISABLE ANSA ips=192.168.2.0/8
NOTE: The syntax 192.168.2.0/8 means that
the last 8 bits of the defined IP address will
be ignored.

IDLE_ONLY ANSA users=demo,demo1 Only the feature ANSA will be subject to the
idle user timeout and only for the listed
users.

IDLE_ONLY ANSA groups=group1,group2 Only the feature ANSA will be subject to the
idle user timeout and only for users
belonging to the listed groups.

IDLE_ONLY ANSA hosts=WIN100,LIN200 Only the feature ANSA will be subject to the
idle user timeout and only when it is
launched by the listed hosts.

IDLE_ONLY ANSA ips=192.168.2.1,192.168.2.3 Only the feature ANSA will be subject to the
IDLE_ONLY ANSA ips=192.168.2.1-192.168.2.6 idle user timeout and only when it is

BETA CAE Systems Page 31

BETA LM Setup Guide

IDLE_ONLY ANSA ips=192.168.2.0/8 launched by the listed IP addresses.

NOTE: The syntax 192.168.2.0/8 means that
the last 8 bits of the defined IP address will
be ignored.

IDLE_TIME_RANGE_DISABLE=08:00-14:00 The idle user timeout will be disabled

between 08.00-14.00 hours.

IDLE_TIME_RANGE_ONLY=08:00-14:00 The idle user timeout will only be applicable

between 08.00-14.00 hours.

NOTE: All the filters above can be used with the syntax “=*” to include all users, groups, IPs,
hosts, respectively.

4.1.2. Allow, deny or limit the access to specific features

A series of options is offered in order to configure the usage of specific features according to the
user, group of users, IP addresses and hostnames. The access to particular features by particular
users may be denied, exclusively allowed or limited to a specific number. These filtering rules are
applicable from versions 19.1.7, 20.0.4, 20.1.2 and 21.0.0 onwards. The appropriate syntax and
some examples of each filtering option are provided in the tables below:

Syntax in .opt file Description

DENY {FEATURE} users=.../groups=..../hosts=.../ips=... The defined feature will not be available,
when launched by the defined users, groups,
hosts or IP addresses.

ALLOW_ONLY {FEATURE} Only the defined feature will be available and

users=.../groups=..../hosts=.../ips=... only when launched by the defined users,
groups, hosts or IP addresses.

LIMIT {FEATURE}: {LIMIT} The number of instances that the defined

users=.../groups=..../hosts=.../ips=... feature can be launched by the defined
users, groups, hosts or IP addresses is
limited to a specific number.

Example Description
DENY ANSA users=demo,demo1 The feature ANSA will not be available to the
listed users.

DENY ANSA groups=group1,group2 The feature ANSA will not be available to the
users belonging to the listed groups.

DENY ANSA hosts=WIN100,LIN200 The feature ANSA will not be available when
launched by the listed hosts.

DENY ANSA ips=192.168.2.1,192.168.2.3 The feature ANSA will not be available when
DENY ANSA ips=192.168.2.1-192.168.2.6 launched by the listed IP addresses.
DENY ANSA ips=192.168.2.0/8 NOTE: The syntax 192.168.2.0/8 means that
the last 8 bits of the defined IP address will
be ignored.

ALLOW_ONLY ANSA users=demo,demo1 Only the feature ANSA will be available for
launching and only by the listed users.

ALLOW_ONLY groups=group1,group2 Only the feature ANSA will be available for

launching and only by users belonging to the
listed groups.
BETA CAE Systems Page 32
BETA LM Setup Guide

ALLOW_ONLY ANSA hosts=WIN100,LIN200 Only the feature ANSA will be available for
launching and only when launched by the
listed hosts.

ALLOW_ONLY ANSA ips=192.168.2.1,192.168.2.3 Only the feature ANSA will be available for
ALLOW_ONLY ANSA ips=192.168.2.1-192.168.2.6 launching and only when launched by the
listed IP addresses.
ALLOW_ONLY ANSA ips=192.168.2.0/8
NOTE: The syntax 192.168.2.0/8 means that
the last 8 bits of the defined IP address will
be ignored.

LIMIT ANSA:1 users=demo,demo1 Only one instance of ANSA will be available

among the listed users. As long as one user
has launched ANSA, the other listed users
will be denied access.

LIMIT ANSA:2 groups=group_1,group_2 Only two instances of ANSA will be available

among users belonging to the listed groups.
The third attempt to launch the feature by
one of the users belonging to the listed
groups will lead to access denial.

LIMIT ANSA:1 hosts=WIN100,LIN200 Only one instance of ANSA will be available

among the listed hosts. The second attempt
to launch the feature by one of the listed
hosts will lead to access denial.

LIMIT ANSA:3 ips=192.168.2.1,192.168.2.3 Only three instances of ANSA will be

LIMIT ANSA:3 ips=192.168.2.1-192.168.2.6 available when launched by one of the listed
IP addresses. The fourth attempt to launch
LIMIT ANSA:3 ips=192.168.2.0/8
the feature by one of the listed IP addresses
will lead to access denial.
NOTE: The syntax 192.168.2.0/8 means that
the last 8 bits of the defined IP address will
be ignored.

NOTES:
a) All the filters above can be used with the syntax “=*” to include all users, groups, IPs, hosts,
respectively.

b) It is also possible to use negative values as limits for the allowed features. In such cases,
when a feature is subject to shared licensing, the total number of shared feature sessions is
limited. For instance, assuming ANSA has been granted shared licensing:
LIMIT ANSA:-2 users=demo1,demo2 means that if a user launches two instances of
ANSA in the same machine, the limit will have been reached hence no third ANSA will be al-
lowed to be launched, by anyone. This serves cases where limiting of hardware resources is
required. It is noted that although the two instances of the same feature by the same user in
the same machine will be counted as individual, the credits occupied will still be counted
once, as expected due to the shared licensing nature of the particular feature.

c) When a license is denied due to one of the above options, the following message
(or a similar one, based on the
application version), appears
in the terminal window:

BETA CAE Systems Page 33

BETA LM Setup Guide

Section 5.
The License.dat File
5.1. The license.dat file
The license file license.dat holds all information that is necessary for the proper and uninterrupted
use of the licensed application. This file is unique and is created for use with the customer's
designated license servers and respective license scheme. Moreover, since it is a file required by the
beta_lm to manage all licensed applications, it should be installed to every server that is running a
beta_lm daemon.

A typical license file contains:

1. An editable section for the optional administration options file (to be discussed later)
2. License server names and host-ids and corresponding communication ports
3. A not-editable section with the licensing specifications and any possible features of the
licensed applications (any unauthorized modifications of this section will result in license
termination)
and has the following structure:

Line Typical License File

1 #
2 # This file is a license file for use with beta_lm License Manager
3 # Run as Administrator : beta_lm -f full_path_to_this_file
4 #
5
6 ################ START OF EDITABLE SECTION
7
8 # Replace FULL_PATH_TO in the next line with the full path of the directory
9 # where license.opt file resides.
10 OPTIONS=FULL_PATH_TO
11
12 # Replace SERVER_NAME in the next line with the hostname of your server
13 SERVER=SERVER_NAME,PORT=6007
14
15 ################ END OF EDITABLE SECTION
16
17 SN=1,HOSTID=200a025ec00b5f5e0f1b2e1b3d5e020bd04e5144,ISU=08-jul-2003,EXP=25-s\
18 ep2004,OPTIONS='COMPANY="yourcompany_name",Tn=10,Tm=40,Ts=20,WCL=60,nodebug,\
19 ACD=10,ART=5,FRC=15,SSC=3,SIGNATURE=07ab9e1920137cb1f0137cb07ab9e19207ab9e192\
20 0137cb1f0137cb07ab9e192cb011d719207ab9e192019e1920137cb1f0137c9e1920137c07ab9\
21 e1920137cb1f0137cb07ab1f01e4432d2f3dd7c9e1920137cb1f0137c
22 SN=1,PACKAGE=PRE_POST,CREDIT=3000,SIGNATURE=9e1920137c07ab9e1920137cb1f0137c7\
23 cdb1f013719207ab9e192019e1920137cb1f0137c9e1920137c07ab9e1920137cb1f0137cb07a\
24 b1f0137c21e2d401cb9e1920137cb1f0137cb07a
25 SN=1,FEATURE=ANSA,PACKAGE=PRE_POST,WEIGHT=100,CREDIT=3000,ISU=08-jul-2003,EXP\
26 =25-sep-2004,OPTIONS='shared',SIGNATURE=90a137c07ab9e1920137cb1f0137cb07acdb1\
27 7137cb07aecd2d223419207ab9e192019e1920137cb1f0137c9e1920137c07ab9e1920137cb1f\
28 0137cb07ab1f0137
29 SN=1,FEATURE=ANSA_CATIA,PACKAGE=PRE_POST,WEIGHT=25,CREDIT=200,ISU=08-jul-20-0\
30 3,EXP=25-sep-2004,OPTIONS=' ',SIGNATURE=9e19d12037c07ab9e1920137cb1f0137cb07a\
31 1f013712da37c\aecd2211ceab9e12019e1920137cb1f0137c9e1920137c07ab9e1920137cb1f\
32 0137cb07ab1f0137c201cb
33 SN=1,FEATURE=META_POST,PACKAGE=PRE_POST,WEIGHT=33,CREDIT=300,ISU=08-jul-2003,\
34 EXP=25-sep-2004,OPTIONS=' ',SIGNATURE=9e19d201317c07ab9e1920137cb1f0137cb07ae\
35 b1f0137137cb07332c37137cb07332caecd223407ab9e1920137cb1f0137cb07aecdb1f013713\
36 7cb01f0137

- Lines 1-4 contain information about the license daemon installation.

BETA CAE Systems Page 34

BETA LM Setup Guide

- Lines 6-15 represent the editable section of the license file. In line 10 the administrator may
optionally provide the location of the "administration options file", which contains all
configurable parameters of the licensing system (see Section 4).

- Line 13 holds information about the license server machine and communication port, so the
administrator should fill in the corresponding values. Note that the default communication
port is 6007. Normally, a license file has one SERVER line. If more SERVER lines appear it
means that a license scheme with redundant servers is used.
- Whatever follows below line 15 belongs to the not-editable section and any modifications
will result in license termination. This not-editable section contains all licensing specifications
(such as software groups, total number of credits and duration of each group etc) and is
created by BETA CAE Systems based on a unique key that is supplied by the customer.

The licensing specifications are divided into sections which in turn are characterized by a
serial number, an identification, the duration and an encrypted digital signature key. A brief
description of the corresponding flags used in these sections is given below:

Flag Description
SN= This is the serial number of the current section of the license file.

HOSTID= This is the host-id of the License Server. It corresponds to the

server_name given in line 13. See next paragraph on how to obtain
a valid host-id.

ISU= & EXP= Line 17: Duration of the license file.

Lines 25, 29 and 33: Duration of the current section of the license
file. Can be different from the total duration that is set for the
license file but cannot exceed the duration set for the license file.

OPTIONS= Line 17: This is the company name for which the license file is
prepared for and installed.
Lines 26, 30 and 34: Additional options related to the current
'shared' section.
Note that in line 26, the 'shared' option specifies that the current
licensed application (ANSA) will reserve a single license if it is
requested by the same user for the same machine/console.

Tn= , Tm= , Ts= , Reserved Flags.

WCL= , ACD= ,
FRC= ,
SSC=

SIGNATURE= Encrypted digital key of the current section.

PACKAGE= This flag is used in order to define a licensed application “group”.

For example, in line 22 a group called “PRE_POST” is defined and
3000 credits are assigned to this group.

CREDIT= Total credits available for this section. If this section belongs to a
PACKAGE or FEATURE, then these are the total credits for this
package or feature.

FEATURE= A "feature" can be either a specific licensed application (like ANSA

in line 25), or a specific software-feature that consumes a different
number of credits (like the ANSA_CATIA translation in line 29).
Such FEATUREs can either belong to a software PACKAGE or can
be stand-alone.

BETA CAE Systems Page 35

BETA LM Setup Guide

WEIGHT= This is the "weight" of a FEATURE, i.e. the number of credits that
are reserved by one instance of the FEATURE. The weight of all
currently running FEATUREs cannot exceed the corresponding
number of CREDITS assigned to this FEATURE. For example, in line
29, it is apparent that up to a total of 8 ANSA_CATIA instances are
allowed to run, since the weight of each one is 25 and the total
credits are 200.

MAINTENANCE= This is the maintenance expiration date for either the PACKAGE or
the FEATURE. It is used only for licenses that do not include
unlimited maintenance or for perpetual licenses. The message:
FEATURE [Feature_Name] EXCEEDED MAINTANANCE PERIOD will
appear in the log file monitoring the license.

TZOFFSETMIN= This only appears when a license file is locked to machines that
TZOFFSETMAX= have a Time Zone which falls between the minimum and maximum
offset – TZOFFSETMIN and TZOFFSETMAX, respectively,
compared to the server. The message: FEATURE [Feature_Name]
EXCEEDED TIMEZONE RANGE will appear in the log file monitoring
the license.

5.2. Additional short term licenses & license extensions

When a license.dat file is created for the very first time by BETA CAE Systems, the serial numbers of
all packages / features are set to SN=1. If an additional short term license is requested by the
customer for one or more of packages / features, then BETA CAE Systems will issue a new license
file having a higher SN for the respective packages / features. In order beta_lm to realize such
changes, the administrator should:

 Stop the beta_lm service

 Replace the license.dat file with the updated one
 Restart the beta_lm service

BETA CAE Systems Page 36

BETA LM Setup Guide

Section 6.
Running a Licensed Application
6.1. Searching for a valid license
When the end-user launches an application, this client application will search on several locations to
find the license server name(s). On each server it will search for available floating licenses. The
locations are searched in a sequential order and are given below:

#Location Server name Notes

1.-h provided by user command argument
2.-f read from provided license.dat command argument
3.BETA_LIC_FILE read from provided license.dat environment variable
4.ANSA_HOME (or META_POST_HOME) read from provided license.dat environment variable
5.current directory read from provided license.dat -
6.BETA_LIC_SRV provided by user environment variable
7.ANSA_SRV provided by user environment variable
8.ansa_srv configured by the administrator DNS alias
9.localhost equals to localhost name -

!NOTE: If the search fails in all above locations, the application will not start. The license server
name(s) is indicated at the SERVER line of the license.dat file provided by BETA CAE Systems.

Locations 1, 6, 7 and 8 point directly to the provided server name, while locations 2, 3, 4 and 5 point
to the SERVER line of the license.dat file.

Location 1. The end-user has the option to declare a specific license server by its name or
IP-address, using the -h flag:

ansa -h port@server
or

ansa -h port@ip
When a redundancy scheme is used, the above command should be like:

ansa -h port@server1,port@server2,port@server3

Location 2. In addition, it is possible to run the application using the -f option to point to the
license.dat e.g.:

ansa -f [full_path_to]license.dat

Locations 3, 6, 7. BETA_LIC_FILE, BETA_LIC_SRV and ANSA_SRV are set as environment varia-

bles (see paragraph 6.1.1 and 6.1.2).

Location 4. ANSA_HOME (or META_POST_HOME) is a variable defined by the application and corre-
sponds to the pathname of the config folder inside the application’s installation directory. This op-
tion requires the license.dat file to be placed within this folder.

BETA CAE Systems Page 37

BETA LM Setup Guide

Location 5. This option requires the license.dat file to be placed within the current directory. The
current directory corresponds to a directory that can be defined in three ways:
 The directory where the application is invoked when called from a shell or command prompt.
 The “Start in” directory when the application is invoked through a Windows shortcut.
 The directory defined with the –changedir running argument.

Location 8. This option points to the server name set as ansa_srv in the DNS server.

Location 9. This option matches the server name with the localhost name.

NOTE: The –h option prevails over –f, when given together.

In its simplest form, a licensed application needs to know where in the network, does the
BETA_LIC_SRV environment variable points to. In turn, BETA_LIC_SRV should point to the server or
servers (single server or redundant servers), as these are listed in the corresponding license.dat
file. Related examples are given in the following paragraphs.

6.1.1. Stand-alone server scheme

In a stand-alone server scheme the SERVER=line of the license.dat file indicates the server and
port used by beta_lm to communicate with clients. For example:

SERVER=plank,PORT=6007

Consequently, the BETA_LIC_SRV environment variable should be set as:

LINUX systems:
setenv BETA_LIC_SRV 6007@plank
(in the .cshrc file for csh or tcsh Unix shell)
or
export BETA_LIC_SRV=6007@plank
(in the .bashrc file for bash Unix shell)

Command: echo $shell to get the shell type (e.g. /bin/tcsh)

WINDOWS systems:
Variable name: BETA_LIC_SRV
Variable value: 6007@plank
(under Control Panel> All Control Panel Items> System> Advanced system settings> Environment
variables> System variables> New)

The ANSA_SRV is defined in a similar manner by setting a variable with ANSA_SRV as name and
6007@plank as value.

Accordingly, the BETA_LIC_FILE is defined by setting a variable with BETA_LIC_FILE as name and
the [full_path_to]license.dat as value.

BETA CAE Systems Page 38

BETA LM Setup Guide

6.1.2. Redundant server scheme

As mentioned in paragraph 2.1.1, beta_lm supports two server redundancy schemes; one uses
multiple servers for license distribution and one is for hardware failover protection. The scheme
which is currently used is reflected in the license file (license.dat) delivered by BETA CAE Systems to
the customer. For example a hardware failover scheme would look like:

SERVER=gauss,PORT=6007
SERVER=hilbert,PORT=6007
SERVER=riemann,PORT=6007

In such cases, the licensed application needs to know all alternate servers that may provide the
requested license. Consequently, the BETA_LIC_SRV environment variable should be set as:

LINUX Systems:
setenv BETA_LIC_SRV 6007@gauss,6007@hilbet,6007@riemann
(in the .cshrc file for csh or tcsh Unix shell)
or
export BETA_LIC_SRV=6007@gauss,6007@hilbet,6007@riemann
(in the .bashrc file for bash Unix shell)

Command: echo $shell to get the shell type (e.g. /bin/tcsh)

WINDOWS Systems:
Variable name: BETA_LIC_SRV
Variable value: 6007@gauss,6007@hilbert,6007@riemann
(under Control Panel> All Control Panel Items> System> Advanced system settings> Environment
variables> System variables> New)

The ANSA_SRV is defined in a similar manner by setting a variable with ANSA_SRV as name and
6007@gauss,6007@hilbert,6007@riemann as value.

Accordingly, the BETA_LIC_FILE is defined by setting a variable with BETA_LIC_FILE as name and
the [full_path_to]license.dat as value.

NOTE: When defining more than one server, “blank spaces” should not exist in-between the server
names.

A note on the server searching order

When more than one servers are declared in the BETA_LIC_SRV variable, the client application will
request for a license by checking these servers in a specific search order: At first, the client will
check the first declared server and then will start checking backwards from the last server to the
second.

As an example consider a server scheme consisting of n servers. The respective BETA_LIC_SRV

declaration should be:

BETA CAE Systems Page 39

BETA LM Setup Guide

LINUX Systems:
setenv BETA_LIC_SRV server1,server2,....server(n-1),server(n)
(in the .cshrc file for csh or tcsh Unix shell)
or
export BETA_LIC_SRV=server1,server2,....server(n-1),server(n)
(in the .bashrc file for bash Unix shell)
Command: echo $shell to get the shell type (e.g. /bin/tcsh)

WINDOWS Systems:
Variable name: BETA_LIC_SRV
Variable value: server1,server2,....server(n-1),server(n)
(under Control Panel> All Control Panel Items> System> Advanced system settings> Environment
variables> System variables> New)

In such cases the client will check the servers in the following order:

1. server1 (first declared server)

2. server(n) (last declared server)
3. server(n-1) (second to the last server)
.....
n. server2 (second server)

A note on Licensed Applications running on Virtual Machines

The launching of any application licensed by BETA CAE Systems (e.g. ANSA or META) from within
any type of Virtual Machine may (depending on the application’s version) disable the “sharing” of
credits for this application. In other words, any instance of an application launched through a Virtual
Machine may not share the same license and will occupy the prescribed number of credits.

6.2. Releasing a license

Since ANSA/META version 21.0.0 onwards, the end-user has the option, to temporarily release the
reserved license without exiting the application. This functionality is accessible within ANSA or
META application via “File > Release License” option. When the license is released, a Confirmation
window appears.

By pressing the OK button, the application can search again for available licenses. With this option,
the end-user can practically bypass the Idle User Timeout setting.

BETA CAE Systems Page 40

BETA LM Setup Guide

Section 7.
beta_lm On The Go
7.0. Introduction to beta_lm On The Go

7.0.1. What is beta_lm On The Go

Problem: Need for an ANSA leasing for a small period of time (short-term), in order to use it on trips
on laptops.

From version 6.1 and on, beta_lm fully supports the usage of a USB Ethernet/WiFi card for the
license server.

For more detailed information regarding the USB Ethernet/WiFi card and the general beta_lm On The
Go features and functionalities, you may refer to the following section.

7.1. Basic Components & Requirements

7.1.1. What is a USB Ethernet/WiFi card

With USB Ethernet/WiFi card, we mean Wireless USB Adapter. Wireless USB is a short-range,
high-bandwidth wireless radio communication protocol. A Wireless USB adapter enables wireless
internet access to either a desktop or a notebook PC. The adapter simply plugs into the external USB
port of the PC. The antenna technology built into the adapter will give full mobility with the notebook,
or enable to place the desktop anywhere at home without the need to use unsightly Ethernet cables.
This device looks like a simple USB, but is a bit bigger, including Ethernet.

7.1.2. Scheme & Hardware requirements

Scheme requirements, as well as Hardware requirements for the beta_lm On The Go application are
given below:

beta_lm On The Go is supported ONLY for Single server scheme and ONLY on Windows platform.

Scheme Availability Platform Availability

Single server YES Windows YES

(32bit/64bit OS Version)

Redundant NO LINUX/MacOS NO
(32bit/64bit OS Version)

BETA CAE Systems Page 41

BETA LM Setup Guide

7.2. Procedure & Application

7.2.1. Overview of actions

When it’s time to get a general license from BETA CAE Systems, the customer can order x-1 license
for the main server and one license for a USB Ethernet /WiFi card that will be installed on another
server.
The client machines will look for licenses first in the main server and if there is saturation,
then they will look for the "USB" server.

In case someone needs to go on a trip with a laptop and needs to launch a Licensed Application
(ANSA/META), then they can take the USB adapter and connect it on the laptop. In this way they will
have an active license at the laptop that can be "returned" upon their return.

The advantage of this scheme is that there is one license that can be taken and used by any
computer
with no interaction from our side, and this license’s cost can be included on the total year budget.
Of course, the disadvantage is that when the USB is away, there is one less license available.

When the USB based license is docked back at the office:

Multiple Server scheme: e.g. server_1 and one USB license on server_2, then the client machines will
have BETA_LIC_SRV = server_1,server_2

NO Redundant Server scheme available.

7.2.2. Installation procedure

In order to receive a license file with the required information

 Select a USB Ethernet adapter and plug it on a Windows platform machine

 Download beta_lm_tools from BETA CAE Systems secure site
 Unpack beta_lm_tools package
 Fetch the information required to build a valid license file, via the command:

beta_lm –host_key –ni USB

The execution of this command will provide the three pieces of information that BETA CAE Systems
requires in order to build a valid license for the selected license scheme. This information, its
description as well as the respective command that should be used to obtain, is given in the table
below:

Item description command (WINDOWS only)

name by which this machine
1. hostname is identified within the
customer's network
media access control
2. MAC address beta_lm -host_key -ni USB
address
beta_lm alphanumeric string
3. host key from USB based on a USB network
interface

BETA CAE Systems Page 42

BETA LM Setup Guide

Section 8.
Troubleshooting beta_lm
8.1. Troubleshooting beta_lm
Troubleshooting actions for problems encountered during installation or operation of the beta_lm
license management tools are given in this paragraph. Since most of these problems are reported in
the "license log" file, it is recommended to use the -L flag during the installation of the beta_lm
license daemon (see paragraph 2.2.7).

The following table presents a list of common errors along with the corresponding description and
recovery action.

Error Message Error Description and Recovery Actions

platform: WINDOWS

description: The beta_lm service could not be started.

recovery: Open a command prompt, switch to the beta_lm_tools

folder and remove the current beta_lm service using the
"beta_lm -remove" command. Then, follow the steps below:

1- Make sure that the network interface is active, even

though there is no physical connection to any network.

2- Make sure that the server NAME specified in the

SERVER= line of the license.dat file is correct and it
corresponds to the machine that will be used as
license server. It might also be necessary to edit this
line and change from:

SERVER=hostname,PORT=6007 to
SERVER=hostname.localdomain,PORT=6007 or
ERROR 1067: The process terminated SERVER=localhost,PORT=6007 or
unexpectedly SERVER=IP_ADRESS,PORT=6007

3- Verify that beta_lm is installed on the same machine

that was declared to BETA CAE Systems as license
server; the HOSTID within license.dat should be
identical to the key reported by running the "beta_lm -
host_key" command

4- Make sure that the PORT number specified in the

SERVER= line of the license.dat file is not already used
by another application or is blocked by a firewall.

5- Make sure that there are no "blank spaces" in the full

path leading to the license.dat file. Replace the location
of the file to avoid blank spaces.

6- Make sure that all complete lines in the non-editable

section of the license.dat file are not wrapped and they
end with a back-slash "\".

BETA CAE Systems Page 43

BETA LM Setup Guide

7- In rare occasions, it might be necessary to login as

"Administrator" and not as a user with administrative
privileges.

8- Confirm that the date & time settings on the

workstation are correct.

Finally, reinstall beta_lm as described in paragraph 2.2.7.

If the problem persists, contact BETA CAE Systems for
assistance.

platform: WINDOWS

description: The beta_lm servive could not be started.

ERROR 1063: StartServiceCtrlDispatcher
failed
recovery: Use the full path of the license file during the
installation procedure.

platform: ALL

description: The machine where beta_lm is launched and will be

used as license server is different from the machine that is
declared as server within the license.dat file. As a result, the
ABORTING SERVER: COULD NOT INSTALL installation process is aborted.
SERVER
recovery: Verify that beta_lm is installed on the same machine
that was declared to BETA CAE Systems as license server; the
HOSTID within license.dat should be identical to the key
reported by running the "beta_lm -host_key" command.

platform: ALL

description: The license.dat file does not contain

SERVER UNDEFINED MODE comprehensive instructions to the server. beta_lm cannot serve
any licenses.

recovery: Contact BETA CAE Systems for assistance.

platform: ALL

SERVER APPLICATION ERROR description: beta_lm has encountered a serious system error.

recovery: Contact BETA CAE Systems for support.

platform: ALL
SERVER Invalid License File
description: The license.dat file has an invalid SERVER= line.

recovery: Contact BETA CAE Systems for assistance.

platform: ALL
Failed FILE address resolution description: beta_lm cannot resolve the server name or IP
address.
recovery: Verify that the SERVER= line of the license.dat file has

BETA CAE Systems Page 44

BETA LM Setup Guide

the correct server hostname. If the error persists, replace the

hostname with the corresponding IP-address or with "localhost".

To obtain the IP address, open a command prompt window and
use the “ping” command:
ping server_hostname.

Check also if the port is used by any other application.

platform: ALL
ERROR Option -L, file name TOO BIG
description: the file name specified for the log file is too big.

recovery: Specify a smaller file name for the log file.

platform: ALL
ERROR Options : check syntax
ERROR Option -c : REMOVE description: Invalid options were used during installation.
ERROR Option -F : REMOVE
recovery: Use valid options. Refer to paragraph 3.1.

platform: ALL

description: There is no license file specified or the path leading

ERROR License File not found to the license.dat file is wrong.
No License File found
recovery: Verify that the license.dat file exists and reinstall
beta_lm using the full path to the license.dat file. See paragraph
2.2.7 for details.

platform: ALL

description: There is no license file specified or the path leading

to the license.dat file is wrong, or the user has no “read”
ERROR License File could not be opened
privileges for the license file.
for read
recovery: Verify that the license.dat file exists, has the proper
privileges, and reinstall beta_lm using the full path to the
license.dat file. See paragraph 2.2.7 for details.

platform: ALL

description: The HOSTID string within the license.dat file does

not match the one created by the current beta_lm_tools version.
ERROR in License File: Could not locate
HOSTID match
recovery: Verify that the HOSTID string inside the license.dat file
is identical to the one produced by the currently installed version
of beta_lm_tools. If not, install the latest beta_lm_tools and
create a new host key.

platform: ALL

description: The specified license.dat file is invalid.

NOT A VALID LICENSE FILE FOUND
recovery: Verify that the HOSTID within license.dat is identical to
the key reported by running the "beta_lm -host_key" command.
Contact BETA CAE Systems for assistance.

BETA CAE Systems Page 45

BETA LM Setup Guide

platform: ALL

description: The alphanumeric strings at the SIGNATUE= lines

are not valid.
ERROR in License File : Signatures did not
verify recovery: Contact BETA CAE Systems for assistance.

platform: ALL

description: The alphanumeric strings at the SIGNATUE= lines

are not valid.
Signatures don't verify with hostid line
recovery: Follow the steps below:
Signatures don't verify with feature line
1- Make sure that all complete lines in the non-editable section
of the license.dat file are not wrapped and end with a back-slash
"\".
2- Verify that the HOSTID within license.dat is identical to the
key reported by running the "beta_lm -host_key" command.

platform: ALL
License Error at Line : #
description: There is an error in this particular line of the license.dat
file.

platform: ALL
Disabled # Credits of Package
description: These particular credits of the specific feature or
Disabled # Credits of Feature
package contained in the license.dat file are disabled (possibly the
feature or package has expired).

platform: ALL, in hardware failover redundancy scheme

Communication Failed description: The communicated server does not currently serve any
licenses, i.e. is a slave server. Please circle through the rest of the
redundant servers.

platform: ALL

description: In redundant server schemes, Slave servers lose contact

with the Master. Usually occurs after multiple continuous license
requests to the Master server.
Not a Master instance of License daemon
recovery: Follow the steps below:
1- Upgrade to beta_lm_v7.0
2- Circle through all servers via the 'beta_lm_stat' command, in order
to verify their status

platform: ALL

description: The license file lists servers by name. However, the

ERROR In License File: Address in file cannot system needs their IP-Addresses.
be resolved.
Check SERVER Lines for misspelled or recovery: Check whether you have DHCP (Dynamic Host
duplicated entries. Configuration Protocol) -i.e. Dynamic Address detection- on your
computer.
DHCP System has an automatic and dynamic allocation of IP-
Addresses and, therefore, it should find all.

BETA CAE Systems Page 46

BETA LM Setup Guide

platform: WINDOWS Vista

description: During installation of beta_lm license daemon on

Windows Vista, the specific Error Message appears.

recovery: Follow the steps below:

OpenSC manager failed
1- Just before beta_lm installation, go to 'User Accounts'
2- At the respective window go to 'Turn User Account ….. on/off'
3- At the new window notice the flag 'Use User Account Control' --->
this should be UNCHECKED !
4- Restart your PC, as the corresponding message prompts you, and
go ahead with the installation.

platform: ALL

description: During installation of beta_lm license daemon, the

specific Error Message appears.
Error 193:0xc1
recovery: Cross-check and confirm that the installation path of
beta_lm package, as well as the location of the respective license.dat
file, do not contain empty spaces like ..\Program files\ etc. It is
recommended to choose an exemplary path instead, like
C:\beta_lm\ etc.

BETA CAE Systems Page 47

Data Access Guide
No ratings yet
Data Access Guide
55 pages
HBM Prenscia
No ratings yet
HBM Prenscia
16 pages
Aveva Licensing System
100% (1)
Aveva Licensing System
66 pages
Root@localhost: #
80% (5)
Root@localhost: #
62 pages
Passwords and Hash Summ For Data Files
No ratings yet
Passwords and Hash Summ For Data Files
3 pages
BETA CAE License Manager
No ratings yet
BETA CAE License Manager
30 pages
Beta LM Tools v6.3 Setup Guide
0% (1)
Beta LM Tools v6.3 Setup Guide
26 pages
LAM Guide: Linux, Solaris, and Windows
No ratings yet
LAM Guide: Linux, Solaris, and Windows
50 pages
Installation Licensing
No ratings yet
Installation Licensing
21 pages
Siemens PLM Licensing User Guide: April 2018
No ratings yet
Siemens PLM Licensing User Guide: April 2018
34 pages
Licenciamento em Rede
No ratings yet
Licenciamento em Rede
66 pages
OpenLM Software Manual 1.5.5
No ratings yet
OpenLM Software Manual 1.5.5
92 pages
MGC Licen
No ratings yet
MGC Licen
104 pages
SLM 71 Sys
No ratings yet
SLM 71 Sys
136 pages
Gnucash Guide
No ratings yet
Gnucash Guide
233 pages
BPA v3.1
No ratings yet
BPA v3.1
24 pages
SPLMLicensing User Guide
No ratings yet
SPLMLicensing User Guide
33 pages
Autocad 2012 Licensing Guide
No ratings yet
Autocad 2012 Licensing Guide
68 pages
Schlumberger Licensing User Guide
No ratings yet
Schlumberger Licensing User Guide
28 pages
TEKnowlogy Solutions Basic LUM Installation
No ratings yet
TEKnowlogy Solutions Basic LUM Installation
3 pages
0 Instalacion de PDI
No ratings yet
0 Instalacion de PDI
42 pages
Schlumberger Licensing User Guide
No ratings yet
Schlumberger Licensing User Guide
32 pages
Intergraph Batch Services For Windows NT: Quick-Start Guide
No ratings yet
Intergraph Batch Services For Windows NT: Quick-Start Guide
39 pages
Batch
No ratings yet
Batch
39 pages
Autodesk Licensing Guide: Autocad 2013
No ratings yet
Autodesk Licensing Guide: Autocad 2013
68 pages
MGC Licen
No ratings yet
MGC Licen
95 pages
And The Status of Them
No ratings yet
And The Status of Them
4 pages
ILO Advanced Installation Instructions 5
No ratings yet
ILO Advanced Installation Instructions 5
1 page
Tecplot
No ratings yet
Tecplot
50 pages
Licensing Mentor Graphics Software: Software Version v2009 - 2 August 2009
No ratings yet
Licensing Mentor Graphics Software: Software Version v2009 - 2 August 2009
86 pages
FLT 7.0v2 UserGuide
No ratings yet
FLT 7.0v2 UserGuide
97 pages
User Guide
No ratings yet
User Guide
97 pages
BMC Remedy Action Request System 7.5.00 Configuration Guide
No ratings yet
BMC Remedy Action Request System 7.5.00 Configuration Guide
414 pages
Schlumberger Licensing User Guide
No ratings yet
Schlumberger Licensing User Guide
29 pages
OpenLM License Harvesting
No ratings yet
OpenLM License Harvesting
16 pages
Telelogic Licensing Guide 1.5 PDF
No ratings yet
Telelogic Licensing Guide 1.5 PDF
72 pages
02sflm6 Install Users
No ratings yet
02sflm6 Install Users
42 pages
Benchmark Factory User Guide - 830
No ratings yet
Benchmark Factory User Guide - 830
270 pages
Adsk Lic
No ratings yet
Adsk Lic
60 pages
Normal Skill Badges
No ratings yet
Normal Skill Badges
6 pages
User Guide Lumension Application Scanner 2-3-2
No ratings yet
User Guide Lumension Application Scanner 2-3-2
38 pages
Autocad - Guia de Licenciamiento
No ratings yet
Autocad - Guia de Licenciamiento
66 pages
Lum Codes
No ratings yet
Lum Codes
41 pages
Flexlm
No ratings yet
Flexlm
81 pages
BMC Blade Logic Client Automation Application Packager User Guide
100% (1)
BMC Blade Logic Client Automation Application Packager User Guide
454 pages
Flexman Installation and Configuration Guide
No ratings yet
Flexman Installation and Configuration Guide
38 pages
MetaQuery User Guide
No ratings yet
MetaQuery User Guide
15 pages
Flexman 5 - 2 Installation and Configuration Guide PDF
No ratings yet
Flexman 5 - 2 Installation and Configuration Guide PDF
38 pages
FlexLM Installation Guide
No ratings yet
FlexLM Installation Guide
6 pages
PowerCenter 9' Level 2 Developer Student Guide Lab
No ratings yet
PowerCenter 9' Level 2 Developer Student Guide Lab
84 pages
Xpress Install Guide
No ratings yet
Xpress Install Guide
44 pages
Licensing
No ratings yet
Licensing
148 pages
Flexman 4 - 1 Installation and Configuration Guide
No ratings yet
Flexman 4 - 1 Installation and Configuration Guide
32 pages
Certscare Cs0 003 Comptia Cybersecurity Analyst Cysa Exam Verified Questions Answers by Ortiz 15-04-2024 7qa
No ratings yet
Certscare Cs0 003 Comptia Cybersecurity Analyst Cysa Exam Verified Questions Answers by Ortiz 15-04-2024 7qa
13 pages
Survey Paper On Different Type of Hashing Algorithm
No ratings yet
Survey Paper On Different Type of Hashing Algorithm
5 pages
63 Certificate
No ratings yet
63 Certificate
2 pages
Experiment: 1 Euclidean and Extended Euclidean Algorithm
No ratings yet
Experiment: 1 Euclidean and Extended Euclidean Algorithm
23 pages
MD5 Experiment
No ratings yet
MD5 Experiment
6 pages
BSA 2023 Certificates
100% (1)
BSA 2023 Certificates
2 pages
Python Forensics Tutorial
100% (1)
Python Forensics Tutorial
51 pages
Cryptography Hash Functions
No ratings yet
Cryptography Hash Functions
5 pages
Digital Evidence Controls
No ratings yet
Digital Evidence Controls
25 pages
RG-NBS3100, NIS3100, NBS3200, NBS5000 Series Switches ReyeeOS 2.280 Release Notes
No ratings yet
RG-NBS3100, NIS3100, NBS3200, NBS5000 Series Switches ReyeeOS 2.280 Release Notes
18 pages
Introduction To Cyber Security Course Content
No ratings yet
Introduction To Cyber Security Course Content
6 pages
Validating The MD5 Checksum of A File
No ratings yet
Validating The MD5 Checksum of A File
4 pages
Lab 1
No ratings yet
Lab 1
10 pages
Unit Iii
No ratings yet
Unit Iii
90 pages
MD5 & Sha
No ratings yet
MD5 & Sha
9 pages
User's Manual: About the Usage of Open Source Software オープンソースソフトウエアの使用について
No ratings yet
User's Manual: About the Usage of Open Source Software オープンソースソフトウエアの使用について
2 pages
Duplicate Cleaner Log
No ratings yet
Duplicate Cleaner Log
6 pages
MD5 Hash
No ratings yet
MD5 Hash
34 pages
MISP Integration Documentation
No ratings yet
MISP Integration Documentation
9 pages
Wicked Cool Perl Scripts
No ratings yet
Wicked Cool Perl Scripts
336 pages
File Transfers
No ratings yet
File Transfers
56 pages
Web and Mobile Security Worksheet 2.1
No ratings yet
Web and Mobile Security Worksheet 2.1
7 pages
Unit 4
No ratings yet
Unit 4
74 pages
IS Lab Manual
No ratings yet
IS Lab Manual
29 pages
Financials, Transactions,: 1.1 Purpose of This Document
No ratings yet
Financials, Transactions,: 1.1 Purpose of This Document
41 pages
MISS-1103 System and Network Security - File-03 - Digital Signature & Cryptographic Hash Function - KMA
No ratings yet
MISS-1103 System and Network Security - File-03 - Digital Signature & Cryptographic Hash Function - KMA
37 pages

Beta LM Tools v7.0 Setup Guide

Uploaded by

Beta LM Tools v7.0 Setup Guide

Uploaded by

Table of Contents

SECTION 0. QUICK INSTALLATION GUIDE ................................................................................................... 2

beta_lm -host_key -ni [network interface, e.g. USB | WiFi]

BETA CAE Systems Page 2

beta_lm -install -ni [USB | WiFi] -f

Start the "BETA LM Service" from:

For troubleshooting actions please refer to section 8.

BETA CAE Systems Page 3

0.2. Updating to newer version

beta_lm -install -ni [USB | WiFi] -f

BETA CAE Systems Page 4

 beta_lm_stat: a reporting tool that provides information on license usage

 beta_lm_kill_user: a tool to terminate process of specific users

 related documentation on the installation and maintenance of beta_lm_tools

1.2. Overview of features

 Flexible short term licensing

 Idle User timeout and Kill User functionality

BETA CAE Systems Page 5

 On-Line statistics and Logging

1.3. Hardware requirements

MacOS 32bit OS Version 64bit OS Version

MacOS Darwin 8.7.3 or later

AMD Athlon, glibc 2.2 AMD Athlon 64, glibc 2.3.2

BETA CAE Systems Page 6

Once the license file is received, then

 beta_lm license daemon must be launched on all license servers

Details on these actions are given below.

2.2. Installation procedure

2.2.1. Select a suitable license server scheme

2.2.2. Download beta_lm_tools

BETA CAE Systems Page 7

 Decide on the machine(s) that will be used as license server(s)

- to install it on a 64bit WinXP platform, you need to download the

 Optionally, download the license administration options file, license.opt

A. MacOS / LINUX Platforms

BETA CAE Systems Page 8

However, if the Windows version of beta_lm_tools package is downloaded on a Windows

2.2.4. Unpack beta_lm_tools package

A. MacOS / LINUX Platforms

tar -zxvf beta_lm_tools_v7.0_linux.tar.gz

 when unpacked, the following directory structure will be created:

directory structure notes

directory structure notes

 when unpacked, the following directory structure will be created:

BETA CAE Systems Page 9

\win32  sub-folder indicating

directory structure notes

2.2.5. Information required to build a valid license file

Item description command (WINDOWS only)

beta_lm alphanumeric string based

BETA CAE Systems Page 10

Item description Command

server1 command response

2.2.6. Receive a valid license file

directory structure notes

2.2.7. Launching the beta_lm license manager

A. MacOS / LINUX Platforms

 issue the command:

BETA CAE Systems Page 11

the result should, for example, look like:

Trying 6007@server_name ....

Found License daemon on server_name

PACKAGE:FEATURE | MAX CREDIT | CREDIT USED | USED PERCENTAGE | USAGE

PACKAGE USAGE REPORT

PACKAGE | MAX CREDIT | CREDIT USED | USED PERCENTAGE third section

BETA CAE Systems Page 12

beta_lm -install -f C:\beta_lm_tools\win32\license.dat -L

beta_lm -install -ni USB -f C:\beta_lm_tools\win32\license.dat -L

The result should, for example, look like:

Found License daemon on server_name

PACKAGE:FEATURE | MAX CREDIT | CREDIT USED | USED PERCENTAGE | USAGE

PACKAGE USAGE REPORT

BETA CAE Systems Page 13

A note on launching the beta_lm license manager on Virtual Machines

2.3. Supported beta_lm features

The total number of licenses can be distributed (equally or not)