Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Licensing System

Configuration and installation of the Three Redundant Server License Files

Configuration and installation of the Three Redundant Server License Files

  • Last UpdatedApr 10, 2025
  • 3 minute read
  1. Install the ALS on all License Server pool machines.

  2. Generate a locking information file on all machines.

    By default, a file named AVEVA-Server-HOSTNAME-info.txt is generated when the AVEVA License System Console is opened for the first time. The generated file is located in the ALS installation folder. For example, C:\Program Files (x86)\AVEVA\AVEVA Licensing System\RMS\Tools.

    To launch the AVEVA License System Console, select Start > AVEVA > AVEVA License System Console.

    Alternatively, if the file is not available, you can generate the ALS locking server criteria file manually.

    Launch the command prompt as an administrator.

    Use the command prompt to navigate to the ALS installation location. For example, C:\Program Files (x86)\AVEVA\AVEVA Licensing System\RMS\Tools.

    Enter the following command to generate a file named AVEVA-Server-HOSTNAME-info.txt:

    AVEVA-Locking.bat

  3. Send all locking information files to the AVEVA license administrator and specify which machines are to be the primary (leader), secondary, and tertiary license servers in the License Server pool.

  4. Save the license file, received from the license administrator, on the primary (leader) server machine.

  5. Launch the AVEVA License System Console to install the license file on the primary (leader) server.

  6. Click the Manage Licenses tab.

  7. Click Browse and select the license file.

  8. Click Install License File, the following message is displayed.

    Steps 4 & 5 of the warning suggest that you copy the Product Mapping File (ProductMappingFile.xml) and the Reserved User List file (POM.xml) to the other License Servers.

    • An identical Reserved User List file must be used on each License Server in the License Server pool.

    • Subsequent changes made to the Reserved User List file, on any of the License Servers, must be manually copied to all License Servers in the License Server pool.

    • The Reserved User List file of all License Servers in the License Server pool must not be different at any time. This may result in the three redundant server setup behaving abnormally.

  9. Click Continue

  10. Enter system server host names and IP addresses (the IP addresses are populated automatically but should be double-checked as some hosts can have multiple IP addresses).

    Note:
    Server details should be entered in the same order as you request the license file (refer to step 3. for further information).

  11. Click Continue.

  12. On the Install AVEVA License File window, click Start License File Installation.

  13. Click Yes in the confirmation window.

    The license file installation success/failure status is displayed in the Install AVEVA License File window.

    Note:
    The checks and installation details of the license file are written to a Console.log file and stored in the default folder (C:\Program Files (x86)\AVEVA\AVEVA Licensing System). If there is a failure in the license file installation, send the Console.log file to the AVEVA license administrator or the AVEVA support engineer.

  14. Once you have successfully completed the license installation procedure on the primary server, the following files are created in your AVEVA licensing installation (by default C:\Program Files (x86)\AVEVA\AVEVA Licensing System).

    C:\Program Files (x86)\AVEVA\AVEVA Licensing System\RMS\lservrlf_AVEVA.

  15. Copy these files to the same directories on your secondary and tertiary servers.

  16. Once you have copied the license files, restart your license services by using the Stop Licensing System/Start Licensing System buttons provided in the ALS Console.

    Important:
    You must ONLY perform the license installation procedure (from steps 5. to 13.) on the PRIMARY server, and copy the generated files onto the secondary and tertiary servers as described. If you perform the license installation procedure on the secondary or tertiary servers, the licensing system will fail to function correctly.

TitleResults for “How to create a CRG?”Also Available in