|
Complete these tasks before you install the Avaya Experience Portal software on a single server.
| Step | Description | Notes |
|
|---|---|---|---|
| 1 | Make sure that the hard drive is partitioned properly in order to create sufficient space for Experience Portal installation. | For more information, see Partition requirements for hard drive in Administering Avaya Experience Portal. | |
| 2 | Make sure that you have access to the Avaya Experience Portal site-specific licensing information from Avaya. | See the License Requirements topic in Upgrading to Avaya Experience Portal. | |
| 3 |
Verify that you can access the planned Experience Portal server
using at least one of the following methods:
|
||
| 4 | Disable any firewall or anti-virus software on the target systems. | ||
| 5 |
Set default umask to 027 in the
/etc/profile and
/etc/bashrc scripts.
After setting the umask to 027 in these files, you need to log on again for the setting to take effect. Use the umask command to verify that the umask default is 027. |
||
| 6 | Check to see if there are any Experience Portal patches available on http://support.avaya.com. If there are patches available, download those patches before you begin the installation. | ||
| 7 | Verify that all servers are running the correct version of Avaya Enterprise Linux or Red Hat Enterprise Linux. | See Verifying the Linux version number. | |
| 8 | Verify that the planned Experience Portal server can communicate with the application server, speech servers, and the PBX. | See Verifying communication between the Experience Portal server and the external systems. | |
| 9 | For Red Hat Enterprise Linux installations, ensure that you configure a yum respository containing all the required Experience Portal packages. Otherwise the prerequisite installation for the Experience Portal server may fail. | ||
| 10 | Make sure that none of the mount points are stale or hung. | See Checking for stale or hung mount points. |