You can configure MashZone NextGen to work with one or an array of BigMemory Max Servers to provide additional memory, provide reliability and support specific other features. See BigMemory Max for Caching, Connections and In-Memory Stores for more information on features that require BigMemory Max servers.
Procedure
If MashZone NextGen is deployed in a cluster, you must copy this file to every cluster member.
wrapper.java.additional.<n+1>=Dcom.tc.productkey.path=MashZoneNG-install/apache-tomcat/conf/terracotta.key
Where n is the number of last additional Java parameter.
If MashZone NextGen is deployed in a cluster, you must update the server configuration files for every cluster member.
<!-- <terracottaConfig url="localhost:9510" /> -->
Remove the comment markers and change the url attribute to the host (or IP address) and port for the BigMemory Max server(s) you installed. For example:
<terracottaConfig url="tcHost1:9510" />
There are several ways to identify one or more BigMemory Max servers for MashZone NextGen. See BigMemory Max documentation for more information.
SEARCH_RESULTS_CACHE = one part of the MashZone NextGen Artifact cache.
SERVICES_BY_ID_CACHE = = one part of the MashZone NextGen Artifact cache.
SERVICE_RESPONSE_CACHE = the MashZone NextGen Response cache for dashboards and data feeds. This is optional. Update this cache only if you want it to be distributed.
This <terracotta> element allows the In-Memory Store and MashZone NextGen caches to use heap and off-heap memory in both the local host and BigMemory Max hosts. This combined memory is managed by BigMemory Max.
For more information on the <terracotta> element, see Distributed Configuration topics in BigMemory Max documentation.
For clusters where this configuration file is not stored in a shared external folder, copy this file to the same location for each MashZone NextGen cluster member.