Before you configure Experience Portal, ensure that Avaya provides the following site-specific
items:
Product ID:
The unique product ID for your site. The numeric identifier that Avaya
must provide when the EPM software is installed.
The Experience Portal license file: The file that determines the various licensed
features and the capacity available to Experience Portal. For example, the license determines maximum number of
telephony ports available to Experience Portal. The file also determines whether the speech applications
in the system can use ASR or TTS resources, whether the system can
process Email, HTML and SMS messages. You must install the license
file on the Avaya WebLM server.
 | Note: |
|
Before you upgrade the Experience Portal system to a newer version, ensure that you have the license
file with required version as per the compatibility matrix below.
If you upgrade an Experience Portal system to a newer version and the license version being
used is older, the system provides a grace period of 30 days. During
the grace period, you must upgrade the license as per the compatibility
matrix below; otherwise the system will no longer be functional once
the license grace period ends. Experience Portal 8.1.2 includes WebLM Server 8.1 which mandates EULA
acceptance for all installed licenses. Prior releases of
Experience Portal included older versions of WebLM Server which did not have
support for EULA acceptance. As a result, after upgrade, WebLM
Server 8.1 will not load any licenses which were installed prior
to upgrade and Experience Portal will go into 30 day grace period till the licenses are
manually re-installed or updated.
Installed licenses: All licenses that were installed on the
WebLM Server which is co-resident with Primary EPM need to be re-installed.
| Note: | |
The license files can be found on the Primary EPM under
$WEBLMSERVER_HOME/webapps/WebLM/licenses folder.
|
Allocated licenses: All licenses that were allocated to the
WebLM Server which is co-resident with Primary EPM need to be re-allocated.
To re-allocate the licenses, use one of the below options:
Wait for the Enterprise or Master WebLM to push the new allocation
licenses as per the periodic license allocation schedule which happens
on a weekly interval. Change the periodic license allocation schedule on the Enterprise
or Master WebLM for the Local WebLM, to the next closest hour. The
Master WebLM then pushes the new allocation licenses to the Local
WebLM as per the new schedule. Once the re-allocation occurs, you
can update the periodic license allocation schedule as needed. Delete the Local WebLM entry from the Enterprise or Master
WebLM, add the Local WebLM again and push the required allocations.
The compatible versions of Experience Portal and WebLM licenses are:
|
Voice Portal/Experience Portal Version
|
License Version
|
|
Avaya Experience Portal 6.0.x
|
6
|
|
Avaya Experience Portal 7.x
|
7
|
|
Avaya Experience Portal 8.x
|
8
|
|
If Avaya Services
maintains the Experience Portal system, the Avaya Services representative must get the
following:
The Avaya Service
Account authentication file that you can use to create Avaya Service
accounts after you install the Experience Portal software.
The Listed Directory
Number (LDN) in the Avaya Services database for each EPM and MPP server, and each speech server.
