Integrate Software AG Products Using Digital Event Services 10.4 | Integrate Software AG Products Using Digital Event Services | MashZone NextGen Help | Appendix | Administration | MashZone NextGen Server Configuration | BigMemory for Caching, Connections and MashZone NextGen Analytics
 
BigMemory for Caching, Connections and MashZone NextGen Analytics
 
Caching for the MashZone NextGen Server
Configure BigMemory Servers for MashZone NextGen Caching and In-Memory Stores
Declare BigMemory Stores for MashZone NextGen Analytics
Manage Dynamic BigMemory Stores for MashZone NextGen Analytics
Configuring Mashable/Mashup Response Caching
By default MashZone NextGen uses local memory for caching and the MashZone NextGen Analytics In-Memory Stores that MashZone NextGen Analytics creates. This uses BigMemory as a local client that is installed with MashZone NextGen and requires only your MashZone NextGen license. In specific cases, you must also install BigMemory Servers on one or more additional hosts and configure MashZone NextGen and the Integrated MashZone Server to work with them. MashZone NextGen requires BigMemory Servers with a BigMemory license to support:
*Significant, extensible amounts of memory, most commonly for very large datasets used with MashZone NextGen Analytics.
BigMemory Servers can be deployed in clusters, also known as Terracotta Server Arrays, that can easily be extended for scalable memory requirements.
*Access to off-heap memory.
BigMemory Servers also can manage memory outside of heap both for better scalability and performance improvements.
*Access to In-Memory Stores created and populated dynamically by external systems.
BigMemory manages the In-Memory Stores created dynamically by other systems and makes connection information available to MashZone NextGen through the Terracotta Management Console (TMC) to allow MashZone NextGen to work with this data. Apama, for example, dynamically creates distributed stores for the Apama MemoryStore which MashZone NextGen can connect to and query.
*Distributed caching when MashZone NextGen is deployed in clusters.
With clusters, some of the interal MashZone NextGen caches must be distributed and managed by BigMemory Servers.
*MashZone feeds that use BigMemory connections as a data source.
See Configure BigMemory Servers for MashZone NextGen Caching and In-Memory Stores for instructions on configuring MashZone NextGen to work with BigMemory Servers.
See Working with MashZone NextGen Analytics In-Memory Stores for an overview and links to additional information on MashZone NextGen Analytics In-Memory Stores.
You also need to provide configuration and connection information for In-Memory Stores that are created by other systems or stores created by MashZone NextGen Analytics that need different settings than the defaults. For more information on these tasks, see:
*Declare BigMemory Stores for MashZone NextGen Analytics
*Manage Dynamic BigMemory Stores for MashZone NextGen Analytics.
See Caching for the MashZone NextGen Server for an overview of MashZone NextGen caching. For caching configuration, see Distributed Caching for MashZone NextGen Clusters.

Copyright © 2019 | 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