Using the ContextStoreQuery service, you can retrieve customer data stored in an External Data Mart (EDM) database. For detailed information about EDM, see Avaya Context Store Snap-in Reference.
License Features
Name
Description
FEAT_CS_EXPIRATION
Context Store expiration feature.
VALUE_CS_AEP_CONNECTOR
Context Store AEP connector.
VALUE_CS_API
Context Store API
VALUE_CS_GEO_REDUNDANT_1
Context Store Geo Redundancy
VALUE_CS_SERVER
Context Store server
VALUE_CS_USERS
Context Store users
External Data Mart Configuration
Name
Description
Secure Connections to EDM
Specifies if communications between the Context Store and the EDM must use a secure connection.
The default value is true.
Note:
For unsecured connections from Avaya Oceana® to EDM, you must set the value to false. Unsecured EDM connections are for laboratory use only. They are not intended for Avaya Oceana® instances that confirm to security policies.
EDM: Database type
The type of the EDM database.
For Avaya Oceana®, select Microsoft SQL Server.
EDM: TLS version
The TLS version for the connection to the EDM database.
EDM: Database host
The host name of the EDM database.
EDM: Database port
The port number of the EDM database.
EDM: Database name
The name of the EDM database.
EDM: Database username
The user name of the EDM database.
EDM: Database password
The password of the EDM database.
EDM: Maximum Database Query Results
The maximum number of results that a ContextStoreQuery REST APIs return. If a query returns more than this maximum, then only the newest results is returned.
The valid range is 50 - 5000.
The default limit is set to 1000.
GDPR Redact Configuration
Name
Description
Thread pool size for tasks to delete contexts
The maximum number of threads per cluster node to handle submitted tasks. The range is between 1 and 8. The default value is 4.
A snap-in restart is not required to take effect.
Supplier
Name
Description
Supplier Id
The supplier ID that Avaya provides.
Advanced Configuration
Name
Description
Enable Centralized Logging
This value indicates that centralized logging is needed by the snap-in. Enables centralized logging after the snap-in is installed.
