15 (1-Sep-08)
The release provides support for Windows Server 2012 and Windows 8.1 on the licence server. It
also provides a Support Bundle which will help the end user to gather relevant information in the
event of a licensing error occurring so that AVEVA can provide an improved support response.
This version will install over the top of a working AVEVA Licensing System 1.3, 1.2, 1.0, or 1.1.1.
Your existing license file and logs will be preserved when upgrading. You will however have to
obtain a new version 2 licence to continue working. Your existing licence (version 1) will not work
with ALS 2.0.
Please do not attempt to run this product on the same server as AVEVA Flexman 5.2,
running an older cadcentre.exe daemon, or any earlier releases of AVEVA Licensing (RMS
For further information please contact your local AVEVA support office, which can be found at
http://www.aveva.com/products/support/support.html
File: d30381
Last saved: 16-Sep-2015 Copyright 2015 AVEVA Solutions Limited Page 1 of 13
Product Release Letter
License Server). Before installing it, stop and remove them you can save any old license
files for emergency rollback recovery.
This version of AVEVA licensing WILL work alongside any other RMS servers for example
AVEVA laser modeller; it WILL also work alongside any other software FlexLM servers.
It is NOT POSSIBLE to combine another RMS products license keys with this RMS server.
It is NOT POSSIBLE to combine another Flex products license keys with this Flex server.
Minimum Supported 32bit O/S Version Windows Vista Enterprise and Business Editions
Maximum Supported 32bit O/S Version Windows 8.1 Professional and Enterprise Editions
Maximum Supported 64bit O/S Version Windows Server 2012 R2,
Windows 8.1 Professional and Enterprise Editions
Please note that recommended/supported hardware and software configurations are constantly subject to review, so
please consult the AVEVA support web pages for the latest recommendations.
ALS 2.0 requires Microsoft .NET 3.5. This is not installed by default on Windows 8.1 or Windows
2012 R2. It must be manually installed on these operating systems prior to installing the Aveva
Licensing System.
Installation on Windows 8.1: run the dotNetFx35setup in the ALS20\DotNetFX32SP1 folder of the
release package.
Installation on Windows 2012 R2: enable the .NET 3.5 Framework as a server feature. From the
Server Manager Dashboard, click on Add roles and features. Navigate the Wizard to Features
and select .NET Framework 3.5 (includes .NET 2.0 and 3.0):
Alternatively, it can be downloaded from the AVEVA Support site: download the ServerInfo2.zip
file, extract the program and .bat file from the .zip file, and run it on your server.
echoid will create a file (AVEVA-Server-computername-info.txt) with your machines locking data
for your license server. Please attach that file into the license request email.
Sentinel RMS Development Kit 8.6.1.0021 Host Locking Code Information Utility
Copyright (C) 2012 SafeNet, Inc.
IP address : 10.0.150.17
Disk ID : 0x884BA25A
Host name : UKCAMDxxxx
Ethernet address[1] : 18-A9-05-C2-37-21
Hard Disk Serial[1] : 9VMC5AEK
CPU Info String : GenuineIntel Intel(R) Xeon(R) CPU W3520 @ 2.67GHz 6 10 5
UUID : BD5E286E-30D0-11DF-BBDA-05C2372118A9
By return you will be sent a license file configured for your system for your applications. Please
save this file in C:\AVEVA\download\myARMSlicense.xml
See screenshot.
Note This Console will control AVEVA RMS, AVEVA Flex, and AVEVA RULES license systems.
If you are installing a redundant license file you will be prompted to enter the hostname
and IP addresses of the license server systems in the redundant array:
Enter the hostnames and IP addresses of the systems in your redundant server array (the
IP addresses will be filled in for you but should be double-checked as some hosts can
have multiple IP addresses). Click Continue when you have entered all the hostnames and
IP addresses and the installation process will continue as for non-redundant server
installation.
If the license locking criteria is OK and the licenses have been extracted, you must now start the
install of the license files. You will get a checking panel as below. Answering [Yes] will start
install.
Note :- The check and install of the license file will be written to a Console.log file stored in the
default folder C:\AVEVA\AVEVA Licensing System\.
If one part of the license system is not running, check inside the server log file for any reasons
why it has not started. Note that the RULES server is normally DOWN if there are no licensing
features that require it. If you want you can just start individually that part of the server by starting
the relevant License Services created by the install. See the AVEVA License System Overview,
further down this document.
This procedure should not take more than 10 minutes. You will need a new ALS 2.0 license file.
1. Before installing ALS 2.0 save the last license.xml file you had previously installed as a
precaution.
2. If you need to preserve records of your previous license usage, back up copies of your
usage log files and the usagelog.xml file in the RMS subdirectory of your installation.
3. Your existing license file and logs will be preserved when upgrading.
4. Close the Aveva License System Console.
5. Start the ALS 2.0 Installer (run setup.exe).
6. Follow the procedure on How To Install A License File earlier in this document.
7. This procedure finishes with starting the license server.
8. Your clients will not have to change anything to be able to access this upgraded server.
IMPORTANT: These license services must have Status Started for ALL AVEVA products to
work.
When you install a license .xml file, it is split out into three separate parts.:
This product mapping file lists which features are present/required for each product. This
information is used in the View Entitlement window that can be accessed via the AVEVA License
System Console.
Introduction
The RULES system provides support for a new AVEVA licensing model called Named User
Licensing. The Named User Model (NUM) differs from the floating license model currently used
by AVEVA in three major aspects:
In effect, this is a form of reserved user licensing, hence the acronym: RULES Reserved User
Licensing Enforcement System. The RULES system is only available with the AVEVA Insight
product at the moment and so users of other products are not affected by the RULES system and
can ignore any RULES-related issues.
The RULES system introduces the following new components to the ALS:
A new ALS Console application: support for starting and stopping the RULES server has
been added to the core functions, as well as the ability to view the RULES server log file.
The operation of RULES is fully automatic and no configuration is required by the user. RULES
obtains its operating parameters directly from the RMS license system and so there are no
additional duties for an administrator other than opening a port for the RULES server on the
system firewall.
The RULES server uses its own port to communicate with RULES applications (e.g. AVEVA
Insight). The port number is derived from the RMS server port number and cannot be explicitly
set, thus: the RULES server will use the next highest port after the RMS server port (as defined by
the LSPORT_AVEVA environment variable). For example, if the RMS server is configured to use
port 4545, then the RULES server will automatically use port 4546.
RULES clients will automatically determine the RULES server port number by using the same
calculation as the RULES server i.e. they will use the configured RMS server port number plus 1.
For example, if a client is configured with a server setting of 123@myServer, then the RULES
client will attempt to communicate with a RULES server on port 124 on server myServer.
For example, in ALS client configuration tool you just need to mention the RMS server port (by
default 4545) and license server name 4545@servername. The RULES client will then
automatically talk to the RULES server on port 4546.
For more information please refer to the manuals installed with this release.
Development Testing
Developers have carried out unit testing of each enhancement and/or fix in the development
environment to verify that any new functionalities have been correctly implemented and identified
defects have been corrected.
Regression tests have been run in the development environment to verify that enhancements
and/or fixes have not adversely affected the integrity of the product.
System Testing
Independent system testing has been carried out on the product, as released, to verify that it
installs correctly in all supported configurations and that product functionality operates as
intended, subject to a known exceptions listed below.
Acceptance Testing
This document has been prepared before Acceptance Testing. This product release will be
subjected to an acceptance test by AVEVAs Group Solutions Centre.
Any exceptions found during Acceptance Testing or after release, or any other updates, will be
reported in the Product Release Latest Update Note on AVEVA's support web site, see below.
http://downloads.aveva.com/30381/w30381.pdf .