MashZone NextGen 10.2 | Appendix | Legacy Presto components | MashZone NextGen Analytics | Working with MashZone NextGen Analytics In-Memory Stores | Store Data in MashZone NextGen Analytics In-Memory Stores | Manage Memory for Dynamic In-Memory Stores
 
Manage Memory for Dynamic In-Memory Stores
When you store a dataset in an In-Memory Store for the first time with a <storeto> statement, MashZone NextGen Analytics creates the In-Memory Store in either local memory or in memory managed by a BigMemory server or server array.
If the store is a declared store, the configuration added to MashZone NextGen when the store was declared defines where the store may be kept in memory.
For dynamic stores, the In-Memory Store store is created in local memory by default. You can configure the store to allow a BigMemory server to keep the store in memory in the BigMemory server or server array using:
*useTSA = "true" on the <storeto> statement in the mashup that creates this In-Memory Store. For example:
...
<storeto useTSA="true" cache='myEvents' key='#unique' variable='theseEvents' />
...
*Configuration in the dynamiccache.xml file in the webapps-home/mashzone/WEB-INF/classes folder. You can use this configuration file to define properties for all In-Memory Stores created dynamically by MashZone NextGen.
Include the connection information to the BigMemory Server that manages memory for In-Memory Stores. For example:
<ehcache name="dynamiccache" overflowToOffHeap="true"
maxBytesLocalHeap="1G">
<terracottaConfig url="localhost:9510" /></ehcache>

Copyright © 2013-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release