In a typical AE Services configuration, a standard license file is installed on each AE Services server. The licenses in the license file are acquired through a local WebLM server running on the AE Services server. However, the following configurations are also possible:
Multiple AE Services may be configured to acquire their feature licenses from a single WebLM server where a standard license file is installed. In this configuration, feature licenses can pool from one AE Services server to another as needed.
With enterprise-wide licensing, an enterprise license file is installed on a master WebLM server. Feature licenses can be allocated from the enterprise license file to multiple AE Services servers. The local WebLM server acquires the feature licenses from the AE Services servers. If any of the feature licenses from the enterprise license are not allocated to the individual AE Services servers, these licenses can also pool among the AE Services servers.
Note:
If network delay is high in AE Services and WebLM server, then the use of pooled licensing for AE Services is not recommended.
If you are using pooled licenses, adjust your WebLM configuration accordingly.
When AE Services is configured for enterprise-wide licensing, the license cannot be removed until the local WebLM entries are removed. For more information, see the Enterprise Licensing topic in the Administering standalone Avaya WebLM guide.
When AE Services is upgraded to Release 8.1.2.1 and later, the Host ID utilized by the embedded Avaya WebLM server will change. The original license will not be valid since it is based on a different Host ID and the system will enter into a 30 day license error grace period. Hence, a new license must be created based on the new Host ID. For obtaining a new license, refer Upgrading Avaya Aura® Application Enablement Services guide. For more information on this issue, see PSN020518u on Avaya support site at https://support.avaya.com.
You cannot use a Virtual IP address with enterprise-wide licensing in Geo-Redundant High Availability (GRHA). You must configure the primary AE Services IP address on the WebLM server for enterprise license to work correctly.
If a standby or secondary AE Services server becomes the primary server, you must update the AE Services IP address on the WebLM server manually before the license grace period of 30 days expires.
In GRHA using Virtual IP, if AE Services is upgraded to Release 8.1.3 and later, the Host ID utilized by the embedded WebLM server will change. Hence, a new license must be created based on the new Host ID. For obtaining a new license, refer Upgrading Avaya Aura® Application Enablement Services guide. For more information on this issue, see PSN020518u on Avaya support site at https://support.avaya.com.
A separate license is not required to use WTI. The WTI service consumes TSAPI and DMCC licenses in AE Services 10.1.2 and later.
If the TSAPI service enters an error mode due to a change in the value notes received in the WebLM license file, the TSAPI service displays a VALUE_NOTES_CHANGED error cause. To return the TSAPI service to normal mode, you must restart the aesvcs service.
Standby AE Services must point to Active AE Services when local WebLM is configured.
