Professional Documents
Culture Documents
Disclaimer
1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free from
viruses.
1.2 AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar losses; loss of
anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of data or information; any
special, indirect, consequential or pure economic loss, costs, damages, charges or expenses which may be
suffered by the user, including any loss suffered by the user resulting from the inaccuracy or invalidity of any data
created by the AVEVA software, irrespective of whether such losses are suffered directly or indirectly, or arise in
contract, tort (including negligence) or otherwise.
1.3 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with the
performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year in which the user's
claim is brought.
1.4 Clauses 1.1 to 1.3 shall apply to the fullest extent permissible at law.
1.5 In the event of any conflict between the above clauses and the analogous clauses in the software licence under
which the AVEVA software was purchased, the clauses in the software licence shall take precedence.
Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every part of it
(including source code, object code, any data contained in it, the manual and any other documentation supplied
with it) belongs to, or is validly licensed by, AVEVA Solutions Limited or its subsidiaries.
All rights are reserved to AVEVA Solutions Limited and its subsidiaries. The information contained in this document
is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without
the prior written permission of AVEVA Solutions Limited. Where such permission is granted, it expressly requires
that this copyright notice, and the above disclaimer, is prominently displayed at the beginning of every copy that is
made.
The manual and associated documentation may not be adapted, reproduced, or copied, in any material or
electronic form, without the prior written permission of AVEVA Solutions Limited. The user may not reverse
engineer, decompile, copy, or adapt the software. Neither the whole, nor part of the software described in this
publication may be incorporated into any third-party software, product, machine, or system without the prior written
permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictly
prohibited, and may give rise to civil liabilities and criminal prosecution.
The AVEVA software described in this guide is to be installed and operated strictly in accordance with the terms
and conditions of the respective software licences, and in accordance with the relevant User Documentation.
Unauthorised or unlicensed use of the software is strictly prohibited.
Copyright 1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved. AVEVA shall not
be liable for any breach or infringement of a third party's intellectual property rights where such breach results from
a user's modification of the AVEVA software or associated documentation.
AVEVA Solutions Limited, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom.
Trademark
AVEVA and Tribon are registered trademarks of AVEVA Solutions Limited or its subsidiaries. Unauthorised use of
the AVEVA or Tribon trademarks is strictly forbidden.
AVEVA product/software names are trademarks or registered trademarks of AVEVA Solutions Limited or its
subsidiaries, registered in the UK, Europe and other countries (worldwide).
The copyright, trademark rights, or other intellectual property rights in any other product or software, its name or
logo belongs to its respective owner.
Copyright 2012, SafeNet, Inc. All rights reserved. SafeNet® and Sentinel® are registered trademarks of SafeNet,
Inc. All other product names referenced herein are trademarks or registered trademarks of their respective
manufacturers.
AVEVA Licensing System
Revision Sheet
Contents Page
1 Introduction
The AVEVA Licensing System (ALS) uses Dual License Server technology (DLS) that
consists of two individual license servers based on different proprietary technologies:
1. A Rights Management System (RMS) license server provided by SafeNet that serves
licenses for newer products (e.g. E3D).
2. A Flex license server provided by Flexera that serves licenses to older products (e.g.
PDMS).
The RMS and Flex license servers work in a cooperative manner that effectively allows the
delivery of licenses from a single "pool" of licenses. This means that different applications
that are licensed with the different technologies are able to share those license features.
This is of particular benefit when customers use different versions of the same application,
some of which are licensed with RMS, and some that are licensed with Flex.
This benefits customers by allowing them to license their products without having to
purchase duplicate sets of licenses for each license server.
The following diagram shows a typical ALS configuration using the default license server
ports:
RMS License File: Contains the licenses that can be served by the RMS License
Server.
Usage Log: A log file written by the RMS License Server that contains
details of license check-out and check-in operations
performed by RMS-enabled applications.
Flex License File: Contains the licenses that can be served by the Flex License
Server.
Debug Log: A log file written by the Flex License Server that contains
details of license check-out and check-in operations
performed by Flex-enabled applications.
The user will also notice that there are two ports configured in the ALS: one port is used by
the RMS License Server and one by the Flex License Server. The use of two ports is
required because it is not possible for the two license servers to share the same port.
Log Files
The contents of the RMS Usage Log file and the Flex Debug Log file do reflect the
operations of the RMS and Flex clients.
Important: The DLS functionality means that the RMS Usage Log also contains the details
of the Flex licensing operations.
Note: The ALS has been specifically designed so that existing FlexMan clients do not need
to be reconfigured if the ALS Server is installed using the detail port settings.
The AVEVA Licensing Client Configuration Tool is used to configure a workstation so that
licensed applications can locate up to three license servers where they can obtain the
licenses required to function.
The Client Configuration Tool also allows configuration of a network timeout setting that can
be used to tune performance on networks that offer intermittent connectivity to a license
server. For example, a license server is located on a remote site.
The Client Configuration Tool will usually only need to be used once when installing the first
AVEVA application, however it may be necessary to run it again if the license server
configuration changes.
The tool allows the configuration of the license server and timeout for the currently logged in
Windows user (via the User Environment settings) or for all users on the workstation (via the
System Environment settings).
The FlexManConfig button will launch the FlexManConfig client configuration tool so that
the workstation can be configured so applications licensed with FlexMan can be used.
If the user is unfamiliar with the AVEVA Licensing System (ALS) refer to Introduction as it
provides an explanation of the ALS and how it works.
The ALS consists of two separate license servers that run cooperatively. Due to the
complexity of configuring the two separate license servers so that they can operate together
a dedicated utility has been provided called the ALS Console.
The ALS Console is an easy-to-use GUI that can be used to perform tasks such as license
file installation and stopping and starting the license system.
While it is possible to manually configure the ALS by directly editing configuration files
AVEVA strongly recommends that only the ALS Console is used to administer the ALS.
AVEVA recommends that the default ports are used if possible. If the user does not want to
use the default ports then they can be changed as follows:
RMS Server: a new port number can be entered via the "Edit Configuration" dialog
accessible via the Query/Configure tab.
Flex Server: a new port can be specified by editing the last field on "SERVER" line
in the Flex license file. An editor (notepad) can be started by clicking
View License File on the Licenses tab).
If AVEVA applications have previously been installed it is highly recommended that the user
uses the same port numbers configured in the workstations that run the AVEVA
applications. To find out these port numbers implement the following:
• For workstations running AVEVA applications that are licensed with the ALS run the
ALSconfig.exe tool.
• For workstations running older applications that are licensed with the FlexMan
licensing system run the FlexManConfig.exe tool.
When the license server port numbers have been set, the workstations that run the
applications need to be configured so that they can locate the license servers. To do this run
either ALSconfig.exe or FlexManConfig.exe depending on whether the applications are
licensed with ALS or FlexMan.
Important: If the workstations are already configured with settings for a FlexMan license
server the user can avoid the need to reconfigure the workstations if they do the
following:
1. Install the ALS on the same host as the old FlexMan server (which must be
uninstalled first).
2. Use the default RMS port number 4545.
New applications that are licensed with ALS RMS will automatically use the older FlexMan
settings if no ALS settings are configured. In these circumstances applications will attempt
to communicate with an ALS RMS server on port 4545 on the same host as the configured
FlexMan server host. For example, if the user has an existing FlexMan server on a host
called "myhost" and the workstations are configured with the FlexMan setting
"744@myhost" the user can install the ALS server on myhost, set the RMS server port to
4545 and then install the ALS-enabled applications on the workstations without the need to
reconfigure them.
4 Console Tool
The Console Tool consists of three tabs, each tab presents a different area of functionality:
• Query/Configure: query the server status, view log files, edit license server
configuration.
• Start/Stop: start and stop the license servers.
• Licenses: install license files and product entitlement, view individual license files.
4.1 Query/Configure
The Query/Configure tab displays the following window:
Note: The status boxes are not updated dynamically and so users should update the status
by clicking Query Server when appropriate.
View Log
1. Use the radio buttons to select the license server log file required to view, then click
View Server Log: a new window is displayed listing the contents of the license server
log file.
2. If RMS is selected then an additional window before the log file is displayed that allows
the user to choose whether to view the default anonymised log or view a de-
anonymised log file that displays the proper user, host, and display names.
• Server and License File Location: displays the path of the RMS license server and
license file. This setting cannot be changed.
• License Server Port: allows the RMS server port to edited.
• Log File: Allows the usage log file name and directory to be configured. Note that the
usage log file name cannot contain three or more continuous underscores.
3. If Flex is selected in the radio button the Flex configuration file
(%AVEVA_LICENSING%\FlexMan\cadcentre.opt) will be opened in Notepad. The user
can then edit the file and save it as appropriate.
Note: No validation will be done on the kind of changes done by the user on the Flex
configuration file.
Note: The changes in the RMS log file configuration would only be visible once the system
is rebooted.
4.2 Start/Stop
The Start/Stop tab allows the user to start or stop the license servers. The window below
the button shows the results of the commands that are used to start or stop the servers so
that any errors can be seen.
4.3 Licenses
The Licenses tab displays the following window:
Install License
1. Use Browse to locate the license file.
2. Click Install New License File(s) (a warning prompt is displayed that installing a
license file requires the license servers to be stopped and given the opportunity to back
out).
3. If the user clicks Yes to install the license file the following sequence of events will
occur:
• Backups of existing license files will be created.
Note: Old license files cannot be reused.
• The license servers are restarted and a message is displayed to the user.
Entitlement/Revoke
Clicking View Entitlement/Revoke will open a new window that allows the user to view the
licenses and products that they have licenses for. The window shows the amount of licenses
available in the form of a chronological graph to make it easy to visualize the licenses, below
is an example:
Operations
1. The tool will refer the product mapping file at the following location:
%AVEVA_LICENSING%\ProductMaps
2. The list of products in the product mapping file will be listed on the left screen in a tree
format.
3. On expanding the node for a particular product, all features belonging to that product
will be listed down.
4. Further on expanding each feature, the list of licenses in that feature will be listed
down. For example in the above screenshot, the following are the products and
features read from the product mapping file:
Product Features
5. Continuing with the above example, Feature1 has two licenses (Lic0 and Lic1). When a
specific feature is selected, the entitlements for that feature will be displayed on the
right side of the dialog.
6. The date range on X axis will include all licenses for that feature (From earliest start
date to latest end date).
7. Horizontal bars are specific to each license.
8. Vertical bars are indicating the total entitlements for all licenses (of that feature) at a
particular date.
Revoking Entitlements
Operations
Revoke process will consist of following steps:
1. Select one of the following options available in the View entitlement Screen:
The user will need to check all three check boxes to proceed.
4. If the user chooses Re-host Some, following dialog will be prompted:
The user will need to check the two check boxes to proceed.
5. Once the user has confirmed and clicked Next, End User Tool will perform revocation
of all licenses.
On successfully revoking the licenses, one of the following two message boxes will be
displayed by the tool.
6. The options disabled earlier can be enabled again by clicking on any product or feature
on the left side of the screen.
7. Also on successful revocation, End User Tool will save the binary data of Revocation
Certificate and that of the Permission Ticket in form of an XML file.
8. End User Tool will prompt the user to send this file back to AVEVA so that AVEVA can
have a proof that the licenses were indeed revoked.
Note:
• The tool will revoke all the licenses from the machine irrespective of the option user
chooses in Step 2. The only difference will be the in Message Box the tool prompts.
• The value for Deferred Revocation Days is read from the Private Vendor Info of AVEVA
"Meta Data License" which should be available on the license server. In case it is not
present or the value of Deferred Revocation Days defined in the license is not valid
(outside 1-30), a default value of 14 days is used.