*
*Home|Chinese|Japanese*About ARM|Forums|Events|News|Employment|Contact Us|Investors*
dotted rule
*ARM - the architecture for the digital worldARM - the architecture for the digital world
search
*
*
***
*MARKETS:PRODUCTS & SOLUTIONS:CONNECTED COMMUNITY:TECHNICAL SUPPORT:DOCUMENTATION*
*
technical support
*
*
****
*.Technical Support
*
*
*>>Home Page*
*
*.Obtaining Support*
*
*.FAQs*
*
**Development Tool FAQs*
**IP FAQs*
**Embedded Software FAQs*
**Artisan Physical IP FAQs (Login Required)*
*
*.Downloads*
*
*.Documentation*
*
*.Training*
*
*.Where To Buy*
*
*.Keil MCU Tools*
*
*.What's New*
*
*.ARM Newsgroups*
*
*.Active Assist On-site Services*
*
*
*
technical support FAQsask ARM*
*

Technical Support Search
*     (Advanced Search)
  FAQs   Documentation   Downloads   Forums

*

 
downarrowUpdating an ADS License Server to license RVDS features
Applies to: RealView Developer Suite (RVDS) 2.0, RealView Developer Suite (RVDS) 2.1, RealView Developer Suite (RVDS) 2.2, RealView Development Suite (RVDS) 3.0, RealView Development Suite (RVDS) 3.1, RealView Development Suite (RVDS) 3.1 Professional, Tool Licensing (License Management)

If you upgrade from ADS to RVDS then following receipt of RVDS upgrade, you must apply to ARM for a new RVDS license file.

Following receipt of an RVDS license file there are now two possibilities:

1 - The License Server details have changed from the previous installation.

If this is the case then you should proceed as for a new license server installation. NOTE: Existing clients wishing to use this new License Server must also be updated to locate the new server.

The simplest scheme is to create or update the existing licensing environment variable ARMLMD_LICENSE_FILE using the port@servername scheme. for example 8224@My_Licence_Server

2 - The License Server details are unchanged from the previous installation.

In this case the License Server software must be updated to license the new RVDS components and the license file must be updated. If this is not done then the new license file will fail, typically with the error message "Invalid license key(inconsistent authentication code)".

Upgrading the License Server

The License Server license file "license.dat", must either be replaced by the new version supplied by ARM, or combined with the existing license file. If the license file is combined with the new license file, then the license server will support the previous tools in addition to the new RVDS components. The FAQ entry: How do I merge my license files?  discusses how to combine license files.

For the License Server to grant RVDS licenses, the License Server daemons must be updated to the version 9.0 builds or later, this means that lmgrd and armlmd daemons on the license server must be replaced by new versions from the RVDS CD. We also recommend that lmutil is also updated.

New versions of the FLEXnet/FLEXlm components for the supported license server platforms are supplied on the RVDS installation CD, e.g., at the following location Utilities\FLEXlm\9.0\release

The version of a FLEXlm component can be identified in two ways ( in the examples below the version number associated with armlmd is examined).

>lmutil lmver armlmd
lmutil - Copyright (c) 1989-2003 by Macrovision Corporation. All rights reserved
FLEXlm v9.0.0 (lmgr.lib), Copyright (c) 1988-2003 by Macrovision Corporation. All
rights reserved.
>armlmd -vsn
16:01:24 (armlmd) FLEXlm version 9.0
16:01:24 (armlmd) Vendor daemons must be run by lmgrd

Summary
The License Server software must be upgraded along with the new Server License file. Either remove the existing License Server software and perform a new installation, or incrementally replace the old components.

NOTE: The existing license server process must of course be stopped when these changes are made and then restarted.



Related:






back to top

*
**
*4 dots*Other ARM Websites
*
shadow *LEGAL STATEMENTshadow