Methods to configure the POM database

Last Updated : Sep 01, 2021 |

You can install the POM server and the POM database in more than one way. POM supports Oracle, Microsoft SQL Server, and PostgreSQL databases. The following table lists some configurations that you can set up the configuration according to your database requirements.

Configuration

Database

Considerations

The POM schema is installed on an external database, which is configured as Avaya Experience Portal's external reporting database.

PostgreSQL, Oracle, and Microsoft SQL Server

  • You must manually take the backup of the POM database.

  • Cross filtering of Avaya Experience Portal custom reports and POM reports is possible.

POM schema is installed on external Oracle database, and the Avaya Experience Portal external reporting database is configured on some other database.

Oracle

  • You must manually take the backup of the databases.

  • Cross filtering of Avaya Experience Portal custom reports and POM reports is not possible.

POM schema is installed on external Microsoft SQL Server database, and the Avaya Experience Portal external reporting database is configured on some other database.

Microsoft SQL Server

  • You must manually take the backup of the databases.

  • Cross filtering of Avaya Experience Portal custom reports and POM reports is not possible.

Report creation

Using cross filtering, you can generate the following reports:

  • A POM custom report and then use the report as a filter in the Avaya Experience Portal standard reports.

  • An Avaya Experience Portal custom report and then use the report as a filter in the POM Campaign Detail Report.

For example, you can generate a custom POM Campaign Detail report and then use the report as a filter in the Avaya Experience Portal call detail report. This report helps you get campaign-specific call details. For example, you can generate a custom Avaya Experience Portal call detail report with First Prompt Latency set. Apply this as a filter in POM Campaign Detail Report to get all call records having the specified latency.

Note:
If multiple Avaya Experience Portal systems share a common reporting database, then:

  • If you install a POM system on a single Avaya Experience Portal system, you can create the POM schema with the common reporting database. In this case, cross filtering of Avaya Experience Portal custom reports and POM reports is possible.

  • If you install a POM system on multiple Avaya Experience Portal systems, you cannot create the POM schema with the common reporting database. You must create the POM schema for each POM system linked with every Avaya Experience Portal system in a separate database. In this case, cross filtering of Avaya Experience Portal custom reports and POM reports is not possible.