|
On a Primary EPM server, the Experience Portal database might increase to a large size. The report data that is generated by Experience Portal causes the database to increase by approximately 4GB for every one million calls processed. If the applications use the Experience Portal application logging feature, the database grows at a faster rate.
By default, the Experience Portal database is saved in the directory /var/lib/pgsql/data. In the software-only offer for Experience Portal, when you install RHEL on the EPM server, ensure that the disk partitions provide adequate space for the Experience Portal database. The default partitioning provided by RHEL is adequate for most Experience Portal installations as the Experience Portal database is in a partition that spans most of the hard disk.
On an MPP server, the MPP logs directory might increase to a large size, especially if the applications use the VoiceXML <log> tag or CCXML <log> tag to generate application log data.
By default, the MPP logs are saved in the directory /opt/Avaya/ExperiencePortal/MPP/logs. In the software-only offer for Experience Portal, when you install RHEL on the MPP server, ensure that the disk partitions provide adequate space for the MPP logs. The default partitioning provided by RHEL is adequate for most Experience Portal installations as the MPP logs are in a partition that spans most of the hard disk.
In the partitioning provided by Avaya Enterprise Linux, the MPP logs are saved in a relatively smaller disk partition. If you encounter space related issues, move the MPP logs to a different location. For more information on moving the MPP logs to a different location, see Administering Avaya Experience Portal.