Ensure that you create the database tables before enabling the External Data Mart provisioning feature. For more information about creating database tables, see Creating database tables for External Data Mart .
About this task
You cannot enable the EDM provisioning feature at runtime. Restart the cluster to redeploy the data grid with the updated configuration.
Note:
EDM: Enable Provisioning from database is an optional attribute. Provisioning is a separate, optional EDM feature than EDM Persistence (which is used for Customer Journey).Enabling Data Mart Provisioning is not supported with an Oceana Deployment.
Procedure
On the System Manager web console, click Elements > Avaya Breeze > Configuration > Attributes.
Click Service Clusters tab.
Select the Service Cluster.
From the Service drop-down menu, select ContextStoreManager.
Enter true in the EDM: Enable Provisioning from database field.
Configure the other EDM attributes. All attributes related to External Data Mart configuration are prefixed with EDM:.
Configure the ContextStoreManager service data grid:
Set the applicable values for DataGrid Settings, EDM: Mirror Service redo log size, and Mirror Service container size for the deployment size.
For more information see the Certified Deployments section in Avaya Context Store Snap-in Release Notes for applicable values.
Click Commit.
If necessary, restart all the Avaya Breeze® platform servers in the Context Store cluster.
Note:
Cluster restart is required if the DataGrid type has changed. All other geo-redundancy-related configuration is dynamic and can be updated by disabling, updating, and re-enabling the feature.
Next Steps
Confirm that the provisioning was successful by using ContextStoreRest to retrieve a context object from the data-grid, that existed in the CS_PROVISION table in the database.
