Contents
Introduction
This document contains Experience Portal 7.0 product information that is not included in the product documentation. This document highlights known issues about the Experience Portal product along with workarounds that are available.
Note: Before continuing, check the Avaya support Web site at http://support.avaya.com for an updated version of this document.
Product Information
The Experience Portal Documentation Library contains some information in hypertext markup language (HTML) and some information in portable document format (PDF). The HTML information is available on the Experience Portal software DVD. The PDF information is available from the Avaya support Web site at http://support.avaya.com.
See the document Avaya Aura® Experience Portal Documentation Roadmap at http://downloads.avaya.com/css/P8/documents/100176099 for a description of the various documents related to Experience Portal that are available.
To access the Experience Portal Documentation Library, place the Experience Portal DVD into a Windows system and use Internet Explorer to view the file \Documentation\VoicePortalDocLibrary\_StartHere.html.
Note: License agreements for each of the third-party components that ship with Experience Portal can be found in the Experience Portal DVD directory \Licenses.
Installation Notes
Important: Before installing or upgrading Experience Portal, please review the Known Issues section in this document for issues that are not addressed in the product documentation. Several of the issues listed there are related to installation.
For detailed installation procedures for non-OVA based systems, see either Implementing Avaya Aura Experience Portal on multiple servers or Implementing Avaya Aura Experience Portal on a single server, whichever is appropriate for your installation. These guides also contain important installation worksheets that should be filled out before starting the Experience Portal installation.
Important: Before starting an upgrade, you should back up your existing Voice Portal or Experience Portal database. In many cases, the upgrade procedure requires you to take a backup in order to preserve your existing data. Additionally, if the upgrade fails for any reason, you will need this backup to restore your system to its prior state.
For detailed upgrade procedures for non-OVA based systems, see Upgrading to Avaya Aura Experience Portal 7.0.
For instructions on how to deploy Experience Portal from OVA files in a VMware environment, see Deploying Avaya Aura Experience Portal in an Avaya Customer Experience Virtualized Environment.
Note: Deploying Avaya Aura Experience Portal in an Avaya Customer Experience Virtualized Environment contains procedures for both new deployments and upgrades of existing deployments.
Known Issues
Experience Portal 6.0.x includes two instances of the Application Interface web service, which allows web service clients to launch applications on Experience Portal and generate outcalls. One instance of the Application Interface web service uses Apache Axis and the other instance uses Apache Axis2.
Experience Portal 7.0 supports only the instance of the Application Interface web service that uses Apache Axis2. This instance is accessed via the URL http://<EPM_Server>/axis2/services/VPAppIntfService.
Note: The <EPM_Server> above is the host name or IP address of a Primary EPM or Auxiliary EPM server.
Applications that use the Axis based instance of the Application Interface web service should be modified to use the Axis2 based instance before the system is upgraded to Experience Portal 7.0.
Experience Portal 6.0.x includes two instances of the Application Logging web service, which allows web service clients to log information that will be displayed on Experience Portal Application Detail reports. One instance of the Application Logging web service uses Apache Axis and the other instance uses Apache Axis2.
Experience Portal 7.0 supports only the instance of the Application Logging web service that uses Apache Axis2. This instance is accessed via the URL http://<EPM_Server>/axis2/services/VPAppLogService.
Note: The <EPM_Server> above is the host name or IP address of a Primary EPM or Auxiliary EPM server.
Applications that use the Axis based instance of the Application Logging web service should be modified to use the Axis2 based instance before the system is upgraded to Experience Portal 7.0.
Experience Portal 7.0 requires newer versions of speech software than previous versions of Experience Portal require. As a result, you may need to upgrade your speech servers before upgrading to Experience Portal 7.0.
See the document Avaya Aura® Experience Portal Overview and Specification at http://downloads.avaya.com/css/P8/documents/100176098 for details on which versions of Loquendo and Nuance speech software are supported by Experience Portal 7.0.
N/A
N/A
The Primary EPM periodically collects report data related to email and SMS processing from each Auxiliary EPM. If an Auxiliary EPM server is re-imaged, then the Primary EPM will stop collecting report data from it.
To work around this issue, reset the report data position on the Primary EPM server whenever you re-image an Auxiliary EPM server. Follow whichever procedure below is appropriate for your system.
To reset the report data position on systems that use only the internal Experience Portal database:
| cd $AVAYA_HOME/Support/VP-Tools |
| ./ResetEmailSMSLocalDB <Auxiliary_EPM_Name> |
Where:
To reset the report data position on systems that use an external database:
| cd $AVAYA_HOME/Support/VP-Tools |
| ./ResetEmailSMSExtDB "<Database_URL>" <JDBC_Driver> <Database_User_Name> <Experience_Portal_Name> <Auxiliary_EPM_Name> |
Where:
Important: Put quotation marks around the URL.
A component of the Primary EPM periodically collects report data that is generated by the email and SMS processing components that also run on the Primary EPM. If the Primary EPM server is re-imaged and the system is configured to use an external database, then the Primary EPM will stop sending email and SMS report data from the Primary EPM server to the external database.
To work around this issue, reset the report data position on the Primary EPM server whenever you re-image a Primary EPM server that is configured to use an external database.
To reset the report data position:
| cd $AVAYA_HOME/Support/VP-Tools |
| ./ResetEmailSMSExtDB "<Database_URL>" <JDBC_Driver> <Database_User_Name> <Experience_Portal_Name> <Primary_EPM_Name> |
Where:
Important: Put quotation marks around the URL.
The Change MPP Server page of the EPM Web interface contains a field labeled Maximum Simultaneous Calls. Whenever you change the value configured for Maximum Simultaneous Calls for an MPP you should restart that MPP in order to force the new value to be used.
In order for Experience Portal to establish a TLS connection to a Session Manager server, you must install the security certificate from Experience Portal on Session Manager.
If your Session Manager is version 6.x, refer to your Session Manager product documentation for instructions on how to install a security certificate on Session Manager. The relevant information can be found in the document Administering Avaya Aura® Session Manager in Chapter 3: Managing Security.
If your Session Manager is version 5.x, please contact Avaya technical support for help with installing the Experience Portal security certificate on Session Manager.
In order for Experience Portal to establish a TLS connection to a Session Manager server, you must install the security certificate from Session Manager on Experience Portal. The correct URL to obtain the security certificate from Session Manager is:
https://<Session_Manager_SM-100>:5061
Note: The <Session_Manager_SM-100> above is the host name or IP address of the SM-100 asset within your Session Manager server. Depending on your Session Manager configuration, the SM-100 asset may be either hardware or software.
Note: Refer to the appropriate interoperability guide that came with your Loquendo software for instructions on configuring your Loquendo speech servers and configuring Experience Portal to work with them. With Loquendo MRCP Server 7.2 software the appropriate document is called Avaya Interoperability Guide. With Loquendo Speech Suite 7.0 software the appropriate document is called Avaya Voice Portal Interoperability HowTo.
Experience Portal communicates with speech servers using either Media Resource Control Protocol version one (MRCPv1) or Media Resource Control Protocol version two (MRCPv2). You must configure Experience Portal to use MRCPv1 when communicating with Loquendo speech servers.
Experience Portal systems that use Loquendo speech servers are limited to a maximum of 100 ports of ASR and 100 ports of TTS.
More Information
Online: