External Data Mart provisioning

Last Updated : Feb 23, 2023 |
Prolog information
Metadata
Keywords:
With the EDM provisioning feature, you can replicate contexts to an external database and use the replicated contexts to redeploy a pre-populated CS data grid. To facilitate such provisioning, you must create contexts with the "persistTo":"CS_PROVISION" flag set.
Context Store stores the contexts that contain the provisioning flag into the provisioning table of the external data mart. When you reboot Context Store, the contexts stored in the CS_PROVISION table are returned into the data grid from the external data mart.
An operation on a context in the data grid updates the provisioning table in the external data mart with the latest version of the context.

Provisioned context data

When you reboot Context Store, the data grid is empty. If the EDM: Enable Provisioning from database field is set to true in the ContextStoreManager attributes, Context Store queries the CS_PROVISION table in the EDM database for context entries. Then the system performs a pump-up of the provisioned data to populate the data grid
Context Store supports retrieving 10 contexts from the external data mart per second.
This feature is designed for automatically provisioning vital operational information into the data-grid. It does not pump up all general context data from external sources.
If a configured external data mart is unavailable or the operation times out, Context Store attempts the operation a fixed number of times. The multiple attempts are to ensure that potential networking difficulties are addressed. For more information about enabling the EDM provisioning feature in Context Store, see the Enabling External Data Mart topic. For more information about EDM provisioning, see Avaya Context Store Snap-in Developer Guide.