Before starting a POM installation, here's a list of items to consider:
EPM Web Console
-
Hostname or IP Address
-
Admin credentials
-
Ddadmin creds for internal app server
-
Outbound routing for PSTN calls
EPM Host Access (ssh)
-
Cust credentials
-
Root credentials (or cust is in sudoers file)
-
Software available in cust home directory
DB Server
-
External DB required for production setup
-
POM database (dev 1G, grow by 10%, prod, must be sized)
- Set READ_COMMITTED_SNAPSHOT = true
mssql: ALTER DATABASE SET READ_COMMITTED_SNAPSHOT ON -
POM operations database (dev 1G, grow by 10%, prod, must be sized)
- Set READ_COMMITTED_SNAPSHOT = false
mssql: ALTER DATABASE SET READ_COMMITTED_SNAPSHOT OFF -
Database owner credentials for creating tables in both databases
- Service account that DOESN'T EXPIRE (we don’t want the system to stop working 30 days after we are complete).
DBA Notes – MSSQL
-
Set tempdb to auto grow.
-
Ensure the disk has enough free space.
-
Set tempdb initial size reasonably. It is recommended that it should be 1/3 of DB size. Eg. In our lab, we kept DB size is 86 GB, so TempDB size should be 30 GB.
-
If possible, put tempdb on its separate disk.
-
Set the recovery model of tempdb to SIMPLE. This model automatically reclaims log space.
Application Server
-
Required for production setup.
-
Admin credentials
-
Either Windows, RHEL or CentOS
POM Installation
-
For the POM install, anything important to offer as an option?
- Default install location (uses ~ 500M, will generate plenty of logs)
-
DB Installation
-
Geo Redundancy - this can be enabled afterwards.
-
Encrypted DB Connection?
-
Avaya Environment
-
CC Elite
-
Most Common, predictive dialer features, if ever needed
-
Monitoring skills requires RT Sockets licensing and configuration (outside of scope)
-
-
Oceana
- "next-generation" customer engagement solution
-
AACC
- Avaya Blue, older, unlikely
-
None
- Perhaps an option, it doesn't hurt to install CC Elite and leave it unconfigured.
-
-