Dynamic stores are created programmatically on the fly when:
An external system creates a store dynamically in BigMemory. These stores are also known as dynamic external stores because the external system is also the system the stores data in the store.
Note
: Access to dynamic external stores requires BigMemory be installed as a server or server array. MashZone NextGen must also have access to the BigMemory license.
To connect to dynamic external stores, a MashZone NextGen administrator must define connection configuration. See Add an External Dynamic In-Memory Store Connection (page 453) for more information. The Terracotta Management Console (TMC) must also be running to successfully connect to a dynamic external in-memory store.
RAQL uses the connection configuration to retrieve configuration for the store from the Terracotta Management Console (TMC) that manages the BigMemory host for this store. This includes search attribute information that is required to allow RAQL to work with the columns in this dataset.
One common example is the use of a dynamic external store to allow MashZone NextGen to work with datasets from distributed stores in the Apama MemoryStore.
With dynamic stores that hold external data, the external system must set a name for the cache manager and define search attributes programmatically when the external system creates the store, using the BigMemory API. See BigMemory documentation for more information and examples.
Configuration defined in MashZone NextGen for the dynamic store allows RAQL to retrieve this configuration information.