Context Store expiration feature.

Context Store AEP connector.

Context Store API.

Context Store Geo Redundancy.

Context Store server.

Context Store users.

The type of Context Store DataGrid.

For Avaya Oceana®, select STANDARD.

The comma-separated values of memoryCapacityPerContainer, maximumMemoryCapacity for ContextStore ManagerSpace DataGrid.

For example, 128m,256m.

The system interprets the numeric-only values as Mb. To specify the values in Gb, you must add the letter g after the number. For example, 1g.

The comma-separated values of memoryCapacityPerContainer, maximumMemoryCapacity for ContextStoreSpace DataGrid.

For example, 512m,10240m.

The system interprets the numeric-only values as Mb. To specify the values in Gb, you must add the letter g after the number. For example, 2g.

The type of deployment.

The options are:

• Standalone

• Oceana

• Elite

Specifies if communications between the Context Store and the EDM must use a secure connection.

The default value is true.

The attribute to ensure that any potentially personally identifiable, such as, the data field and the collected digits within Avaya Oceana®, are not replicated to External Data Mart.

You must enable this attribute if any Personally Identifying Information is written into the data field, or entered into the collected digits, to comply with Data Privacy Laws.

For Avaya Oceana®, the default value is true.

Specifies the period of time for which closed contacts are retained in the EDM.

The value range is 0-3650.

Setting this attribute to 0 keeps the closed contacts permanently. However, it is not recommended because of performance implications.

The default value is 30.

The hour of the day at which EDM maintenance runs.

The value range is 0-23. The default value is 2 (02:00).

The amount of context data to store for retry if disconnected from External Data Mart (EDM). The system discards the oldest data when this size limit is reached.

The attribute that enables or disables the persistence of Context data to EDM.

For Avaya Oceana®, select true.

Specifies how the Context Store data is stored in the EDM. For Avaya Oceana®, select Journey.

The type of the EDM database.

For Avaya Oceana®, select Microsoft SQL Server.

The attribute that enables or disables the provisioning of Context data to EDM.

For Avaya Oceana®, keep the default value false.

The TLS version for the connection to the EDM database.

The host name of the EDM database.

The port number of the EDM database.

The name of the EDM database.

The user name of the EDM database.

The password of the EDM database.

The memory required to deploy EDM Mirror Service.

For example, 1.

The system interprets the numeric-only value as GB. To specify the value in MB, you must add the letter m after the number. For example, 128m.

The attribute that determines whether to deny or accept a service when two nodes in a cluster are unavailable. If this attribute is disabled, the last remaining node continues to attempt service requests.

The permissible values are:

• true: If two nodes in a cluster are unavailable, the third node also denies service.

• false: Even if two nodes in a cluster are unavailable, the third node attempts to serve incoming requests.

The default value for this attribute is false.

The limit of event entries in the audit trail of context objects.

For Avaya Oceana®, enter the value as 1.

The default lease time, in seconds, for which context data remains in the in-memory data cache. Context Store automatically removes a context if the context remains in Context Store for the lease period without any change.

The default value for this attribute is 7200. You can specify any value between 1 to 86400 to configure this attribute.

For values specific to your deployment type, see Avaya Context Store Snap-in Release Notes.

The maximum lease time, in seconds, for the context data. The system logs warnings for leases longer than this value.

If the average lease time for the cluster exceeds this value, Context Store raises an error event. If a context is created or updated with a lease time that exceeds this value, Context Store logs only a warning.

The default value for this attribute is 14400. You can specify any value between 1 to 86400 to configure this attribute.

You can update this attribute dynamically.

High threshold on Context Store instance requests per second. This value must be greater than the related Minima. For a Context Store instance, if the number of requests per second exceeds this value, the instance rejects the further requests and raises an event.

The default value for this attribute is 65. You can specify any value between 1 to 650 to configure this attribute.

You can update this attribute dynamically.

For values specific to your deployment type, see Avaya Context Store Snap-in Release Notes.

Avaya Oceana® supports a maximum of 10000 active emails when you set the value of this field to 350. If you upgrade the ContextStoreManager SVAR, you must note down this value before the upgrade and set the same value after the upgrade.

Low threshold on Context Store instance requests per second. This value must be lesser than the related Maxima. For a Context Store instance, if the number of requests per second exceeds this value, the instance raises an event, without rejecting any further requests.

The default value for this attribute is 55. You can specify any value between 1 to 650 to configure this attribute.

You can update this attribute dynamically.

For values specific to your deployment type, see Avaya Context Store Snap-in Release Notes.

Avaya Oceana® supports a maximum of 10000 active emails when you set the value of this field to 330. If you upgrade the ContextStoreManager SVAR, you must note down this value before the upgrade and set the same value after the upgrade.

Threshold for maximum tolerated Context Store request error rate in percentage.

The default value for this attribute is 20. You can specify any value between 1 to 100 to configure this attribute.

You can update this attribute dynamically.

Threshold for maximum tolerated Context Store request latency in milliseconds. When the average latency exceeds the specified value, Context Store raises an event.

The default value for this attribute is 250. You can specify any value between 1 to 5000 to configure this attribute.

You can update this attribute dynamically.

High threshold on Context Store service requests per second. This value must be greater than the related Minima. For a Context Store cluster, if the number of service requests per second exceeds this value, Context Store rejects the further service requests and raises an event.

The default value for this attribute is 105. You can specify any value between 1 to 1240 to configure this attribute.

You can update this attribute dynamically.

For values specific to your deployment type, see Avaya Context Store Snap-in Release Notes.

Avaya Oceana® supports a maximum of 10000 active emails when you set the value of this field to 1240. If you upgrade the ContextStoreManager SVAR, you must note down this value before the upgrade and set the same value after the upgrade.

Low threshold on Context Store service requests per second. This value must be lesser than the related Maxima. For a Context Store cluster, if the number of service requests per second exceeds this value, Context Store raises and alarm, without rejecting the further service requests.

The default value for this attribute is 85. You can specify any value between 1 to 1240 to configure this attribute.

You can update this attribute dynamically.

For values specific to your deployment type, see Avaya Context Store Snap-in Release Notes.

Avaya Oceana® supports a maximum of 10000 active emails when you set the value of this field to 1200. If you upgrade the ContextStoreManager SVAR, you must note down this value before the upgrade and set the same value after the upgrade.

Context Store expiration feature.

Memory required for Geo-Redundancy Gateway Service deployment.

The system interprets a numeric value only as gigabytes. You can specify megabytes with an m or mb after the number. For example, 2m.

For values specific to your deployment type, see the Certified Deployments section in Avaya Context Store Snap-in Release Notes.

The default value is 1.

Certificate name of the geo redundancy keystore.

Password of the geo redundancy keystore.

Name of the target cluster on the geo redundant site

Setting this to 'true' enables clients to subscribe for personalized events from Context Store.

The supplier Id that Avaya provides.

The default value is 10000000.

This value indicates that centralized logging is needed by the snap-in. Enables centralized logging after the snap-in is installed.