QA4/1, QA7/2 & QA11/3 - DNote v4.

15 (1-Sep-08)

Product Release Letter

AVEVA Licensing System 1.3
Full Release 30377
Windows Server 2008, 2003; Windows7, Vista, XP
This letter introduces and describes this release, which is supported on the indicated platform(s).

This Release Contains

A release of AVEVA Licensing System 1.3 that consists of the new RULES server (please see
page11 for more information on the RULES server), new ALS console, and updated documents.

This version of AVEVA Licensing is designed to replace the AVEVA Flexman 5.2 license server so
that there are minimal changes for clients using any AVEVA product secure with RMS alongside
earlier AVEVA products secure with Flexlm.
Or
This version will Install over the top of a working AVEVA Licensing System 1.2, 1.0, or 1.1.1. Your
existing license file and logs will be preserved when upgrading. You will however be able to re-
install your last license (.xml) file once this release has been installed if you choose to.

The components installable from this release are as follows:

Version
Component Name
Number
lservnt.exe (RMS License Server) 8.5.3.1605
Wlmadmin.exe (RMS Administration Tool) 8.5.3.0035
cadcentre.exe (Flex License Server) 6.2.1.0
lmgrd.exe (Flex License Server) 11.8.0.0
ALSConsole.exe 1.4.0.0
AVEVALogAgent.exe (Usage Log Transfer) 4.2.9.0
AVEVA_RULES_Server.exe (RULES License Server) 1.0.2

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
License Server). Before installing it, stop and remove them – you can save any old license
files for emergency rollback recovery.

For further information please contact your local AVEVA support office, which can be found at
http://www.aveva.com/products/support/support.html

This document has been prepared and approved by the following:

Job Title Name
Product Manager Ian Steele,James Bidewell
VP product Support and Training. Martin Bain

File: d30377.doc
Last saved: 8-Jan-2015  Copyright 2015 AVEVA Solutions Limited Page 1 of 12
 Product Release Letter
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 for
example TribonLS 4.1.

This version of AVEVA Licensing supports installation of redundant server licenses.

It is NOT POSSIBLE to combine another RMS product’s license keys with this RMS server.
It is NOT POSSIBLE to combine another Flex product’s license keys with this Flex
server.Prerequisite for this release – operating system:

Minimum Supported 32bit O/S Version Windows XP SP3, Windows Server 2003
Windows Vista Enterprise and Business Editions
Maximum Supported 32bit O/S Version Windows Server 2008 SP2
Windows 7 Professional and Enterprise Editions
Maximum Supported 64bit O/S Version Windows Server 2008 R2 SP1
Windows 7 SP1 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.

To Install product release:

The Licensing System is simply installed using the setup.exe file. Once installed, full details of
configuration are given in the AVEVA Licensing System User Guide, which can be found using
Start > All Programs > AVEVA > Licensing System. The summary on next pages may be
helpful.

d30377.doc 8-Jan-2015  Copyright 2015 AVEVA Solutions Limited Page 2 of 12

 Product Release Letter

How To Obtain A License File (locking Criteria)

To ensure you have correct license server locking criteria, run the echoid application via the
AVEVA-locking.bat file found in the \RMS\Tools\ folder installed with this release.

Alternatively, it can be downloaded from the AVEVA Support site: download the ServerInfo.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 machine’s locking data
for your license server. Please attach that file into the license request email.

The text below is an example output from an AVEVA-Server-info.txt file :-

Sentinel RMS Development Kit 8.5.3.0020 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

Locking Code 1 [1] : 381E-*17K YRQD S5MZ 78EC

---------------------------------------------------------------------
Ethernet address[1] : 18-A9-05-C2-37-21
Hard Disk Serial[2] : 9VMC5A07

Locking Code 1 [2] : 381E-*195 M6LA JKJG 7RDN

---------------------------------------------------------------------

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

DO NOT EDIT THIS FILE PRIOR TO INSTALLING.

d30377.doc 8-Jan-2015  Copyright 2015 AVEVA Solutions Limited Page 3 of 12

 Product Release Letter
How To Install A License File

Run the AVEVA License System Console, this is found under :-

START>All Programs> AVEVA>Licensing System>
AVEVA License System Console

See screen shot.

Note – This Console will control AVEVA RMS, AVEVA Flex, and AVEVA RULES license systems.

First click on the Licenses Tab.

d30377.doc 8-Jan-2015  Copyright 2015 AVEVA Solutions Limited Page 4 of 12

 Product Release Letter
To install your license file, on the Licenses tab, Browse to your saved license.xml file.
This will first check the license file contents.

Note: If you are installing a redundant server:-

If you are installaing a redundant license file you will be prompted to enter the hostname
and IP addresses of the license server systems in the redundant array:

d30377.doc 8-Jan-2015  Copyright 2015 AVEVA Solutions Limited Page 5 of 12

 Product Release Letter

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 :- As shown above 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\ folder.

d30377.doc 8-Jan-2015  Copyright 2015 AVEVA Solutions Limited Page 6 of 12

 Product Release Letter
License Installed OK.

Starting And Stopping The RMS License Server

To check server is running go back to Query/Configure tab and action [Query Servers] button.

If one part of the license system is not running, check inside the server log file for any reasons
why it has not started. If you want you can just start individually that part of the server by starting
the License services created by the install. See Services created in AVEVA License System
Overview, further down this document

d30377.doc 8-Jan-2015  Copyright 2015 AVEVA Solutions Limited Page 7 of 12

 Product Release Letter
To enable a client product to see the ARMS server:
Run the ALSClientConfigTool.exe and configure either the individual users or machines
To the license server , the default ALS servers port is 4545.

For your clients change this example of the

Hostname (ukcamd3903) to your license
server Host Name that was in the :-
AVEVA-Server-info.txt file.

d30377.doc 8-Jan-2015  Copyright 2015 AVEVA Solutions Limited Page 8 of 12

 Product Release Letter
Installing ALS 1.3 over a working ALS 1.2, ALS 1.0 or ALS1.1.1 Server.

This whole procedure should not take more than 10 minutes.

1. Before installing ALS 1.3 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 1.3 Installer (run setup.exe)
6. Once the install has finished start the new Aveva License System Console V1.4.0.0 and
click on ‘Start Licensing System’ to start the servers
7. Then follow the procedure on how to install a license file if you want to install new license
file. (page 3 in this document)
8. Your clients will not have to change anything to be able to access this upgraded server.

AVEVA License System Overview.

The AVEVA license System Console stops and starts three License manager services that are
defined during the install. These can be manually stopped and restarted via Services.

Sentinel RMS License Manager _AVEVA

AVEVA DLS Flex Server

d30377.doc 8-Jan-2015  Copyright 2015 AVEVA Solutions Limited Page 9 of 12

 Product Release Letter

AVEVA RULES Server

When you install a license .xml file, it is split out into three separate parts.
The two main parts are the RMS license server file :-
AVEVA\AVEVA Licensing System\RMS\lservrc
and the Flex license server file :-
AVEVA\AVEVA Licensing System\Flex\licenses.lic

The third part is a product mapping file that details 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.

IMPORTANT: License services must be in the “Started” state for ALL AVEVA products to work.

d30377.doc 8-Jan-2015  Copyright 2015 AVEVA Solutions Limited Page 10 of 12

 Product Release Letter
RULES Server

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:

1. Licenses are restricted to a specific number of named users.

2. Licenses are locked to a specific user for 30 days from “first use”.
3. Locked licenses can be used by a user on a limited number of devices.

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 server, AVEVA_RULES_Server.exe. This server must be running in order for

RULES-enabled applications to function.

 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.

 A new directory, %AVEVA_LICENSING%\RULES, that contains applications and files that

support the RULES functionality.

RULES System and Port Configuration

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 Client Configuration

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.
Example: In ALS client configuration tool just need to mention the RMS server port (by default
4545) and license server name 4545@servername. RULES client will automatically talks to
RULES server on port 4546.

d30377.doc 8-Jan-2015  Copyright 2015 AVEVA Solutions Limited Page 11 of 12

 Product Release Letter

AVEVA products secured via FlexLm.

When an older AVEVA product which is secured via Flexlm runs it talks to the Cadcentre.exe
daemon via the default TCP port no 744 (which can be changed via the SERVER line in the
licenses.lic file) The Cadcentre.exe daemon in turn asks the Flex lmgrd.exe if it has a license key
to run. As this is a dual license system, the Cadcentre.exe then asks the RMS server via the
default UDP port No. 4545 if it also has the same key. Only if both systems have the same keys
will it return the OK to the product to run. The UDP 4545 port can be changed for RMS via the
AVEVA License System Console.

AVEVA products secured via AVEVA Licensing System (RMS)

AVEVA Everything3D™ 1.1 is one of the first AVEVA products to be secured via RMS.
When this runs it talks directly to the RMS server via the UDP port no 4545.
It does not rely on Flex at all.
So eventually as AVEVA’s products are migrated over to use the RMS system, it will be possible
to turn off the Flex part of the AVEVA Licensing System.

For more information please refer to the manuals installed with this release.

PRODUCT QUALITY STATEMENT

The development, maintenance and testing of AVEVA Solutions’ software products is carried out
in accordance with the company’s KEYSTONE lifecycle processes and this document includes a
summary of the testing carried out on this release and a list of significant defects known to exist at
the time of 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 AVEVA’s Group Solutions Centre.

Any exceptions found during Acceptance Testing or after release will be reported in the Product
Release Latest Update Note on AVEVA's support web site
http://downloads.aveva.com/30377/w30377.pdf .

Exceptions – Significant Defects And Recommended Workarounds

For the latest list of exceptions and other updates, please see the Product Release Latest Update
Note on AVEVA's support web site http://downloads.aveva.com/30377/w30377.pdf .

d30377.doc 8-Jan-2015  Copyright 2015 AVEVA Solutions Limited Page 12 of 12