Installing a license file

Last Updated : May 24, 2024 |

About this task

You can install a license file on the WebLM server. Use the Uninstall functionality to remove the license file from the WebLM server.

Licenses installed for WebLM Release 7.1 and later must support a SHA256 digital signature and 14–character host ID.

There is a limit of 50 licenses per WebLM server.

Note:

If you have a mix of Communication Manager Release 6.3.x, 7.x, 8.x, and 10.1.x software with Communication Manager 6.3.x, 7.x, 8.x, and 10.1.x license files, use the Communication Manager 10.1.x license file for all the Communication Manager Release software.

For more information, see Uninstalling the Communication Manager 6.3.x, 7.x, and 8.x license file and installing the Communication Manager 10.1.x license file.

Before you begin

  • Get the license file from the Avaya Product Licensing and Delivery System (PLDS) website at https://plds.avaya.com.

  • Log on to the WebLM web console with administrator privilege credentials.

  • For the standard license file, remove the older license file before you install the new file.

    Note:

    WebLM displays an error message if an older license file is still available.

    For a centralized license file, the system automatically overwrites the older license file during installation.

For information about the license file installation errors while installing the license file, see Administering standalone Avaya WebLM.

Procedure

  1. In the navigation pane, click Install license.
  2. On the Install license page, click Browse and select the license file.
  3. Read the terms and conditions, and click Accept the License Terms & Conditions.
  4. Click Install.

    WebLM displays a message on the successful installation of the license file. The installation of the license file might fail for reasons such as the following:

    • The digital signature on the license file is invalid. If you get such an error, request PLDS to redeliver the license file.

    • The current capacity use exceeds the capacity in the installed license.

    • An acquired license does not cover a licensed feature or product.

    • An over-installation of licenses. In this scenario, free the already acquired licenses and retry installing the new license file. You could also try uninstalling the existing installed license file and installing a new license file.

Related information
Scenario 01