Data Storage Settings page field descriptions

Last Updated : Jun 05, 2026 |

Use this page to configure the data storage settings for report data and conversations:

  • Report Database

  • Avaya Breeze® platform

  • Conversations

Report Database

Field or Button

Description

Location radio buttons

The options are:

  • Local: The database resides on the local EPM server machine.

  • External: The database resides on a different server. This option is generally used when you have several Experience Portal systems that share an external database.

Note:

If you select External, the rest of the fields in this section become available. Contact your database administrator if you do not know the information to complete these fields.

URL

The fully-qualified path to the external database.

A common URL format for Oracle connections is: jdbc:oracle:thin:@OracleServerName:1521:DBName

A format for PDB (portable db) connections is: jdbc:oracle:thin:@ServerName:1521/pdbName

A format for CDB (container db) connections is: jdbc:oracle:thin:@ServerName:1521/cdbName

A common URL format for Postgres is: jdbc:postgresql://PostgresServerName:5432/DBName

A common URL format for Microsoft SQL connections is: jdbc:sqlserver://SQLServerName:1433;databaseName=DBName

A common URL format for MySQL connections is: jdbc:mysql://ServerName:3306/DBName

A common URL format for MariaDB connections is: jdbc:mariadb://ServerName:3306/DBName

JDBC Driver

The name of the Java class that implements the JDBC API to the external database. Experience Portal makes JDBC calls through this class when communicating with the external database. Experience Portal installs drivers for Oracle, Postgres and Microsoft SQL Server.

For Oracle, the name is oracle.jdbc.driver.OracleDriver.

For Postgres, the name is org.postgresql.Driver.

For Microsoft SQL Server, the name is com.microsoft.sqlserver.jdbc.SQLServerDriver.

For both MySQL and MariaDB, the name is org.mariadb.jdbc.Driver.

User Name

The user name for the external database.

Note:

For Oracle, the user name must be assigned CREATE TABLE, CREATE SESSION and CREATE SEQUENCE privileges for the database.

For Microsoft SQL Server, the user name must be assigned SELECT, INSERT, UPDATE and DELETE privileges on all tables in the database.

For Postgres, the user name must be assigned CONNECT, TEMPORARY ON DATABASE, SELECT, INSERT, UPDATE and DELETE privileges on all tables in the database.

For both MySQL and MariaDB, the database user name for Experience Portal must be assigned SELECT, INSERT, UPDATE, DELETE privileges on all tables in the database. The CREATE TEMPORARY TABLE permission is also required. When creating the database, set a collation type of utf8_unicode_ci.

Password

The password for the external database.
Note:

The Oracle Advanced Security Option is available only if you set the external database to Oracle.

Field

Description

Encryption Type

Encryption algorithms transform data into a form that cannot be deciphered easily.

Select an encryption type to protect sensitive information sent between the EPM and external database.

The options are:

  • None

  • AES128

  • AES192

  • AES256

  • RC4_40

  • RC4_56

  • RC4_128

  • RC4_256

  • DES40C

  • DES56C

  • 3DES112

  • 3DES168

Note:

If you select None, Avaya Experience Portal sets the encryption level to rejected. For any other value, Avaya Experience Portal sets the encryption level to required.

Checksum Type

Data integrity algorithms can protect against certain network-based attacks by generating cryptographically secure message digests which are included in data packets sent between the EPM and external database.

Select a checksum type you want to use.

The options are:

  • None

  • MD5

  • SHA1

Note:

If you select None, Avaya Experience Portal sets the checksum level to rejected. For any other value, Avaya Experience Portal sets the checksum level to required.
Note:

You might need to increase Session Timeout from the Home > User Management > Login Options page for very large databases where on-demand reports might take more than 10 minutes. Scheduled reports are not subject to this timeout.

Avaya Breeze® platform

Field

Description

Platform Host Address

SIP Entity IP address of Avaya Breeze® platform.

Context Store Address

Cluster IP address of the context store on Avaya Breeze® platform.

Client Timeout

Maximum number of seconds that the Orchestration Designer application should wait for the platform or the context store to respond back to its request. Enter a number between 15 and 300. The default is 60.
Note:

When you select the context store, the application server requires proper certificates setup for mutual authentication.

Conversations

Field or Button

Description

Local EPM (SMS channel only)

A database on EPM that is processing the application that creates the conversation.

Use this option for a valid SMS application. If a non-SMS application attempts to create a conversation, the operation fails. This configuration provides backward compatibility with Experience Portal 7.0.

Primary EPM (All channels)

A database on the Primary EPM server.

Use this option for systems that do not contain any Auxiliary EPM servers. This option does not support high availability and the conversation data is unavailable for applications when the Primary EPM server is down.

Context Store (All channels)

The Context Store of Avaya Breeze® platform.

Use this option to provide configuration information to Orchestration Designer. Orchestration Designer is the application that reads/writes the conversation data whereas Experience Portal provides the configuration information to Orchestration Designer. This option supports high availability, which is optional, and is robust only if you have setup Context Store in cluster mode.

  • Host Address: Cluster IP address of the Context Store associated with Avaya Breeze® platform.

  • Client Timeout: Maximum number of seconds that the Orchestration Designer application should wait for the platform or the context store to respond back to its request. Enter a number between 15 and 300. The default is 60.

    Note:

    The Context Store option supports Orchestration Designer 7.1 or later. Orchestration Designer 7.0.1 SMS applications will use Local EPM for conversations even if you select the Conversation Store as Context Store.

Existing conversations can be lost when you switch from the conversation store location.