Configure BigMemory Max Servers for MashZone NextGen Caching

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

  1. Copy your license for BigMemory Max to MashZone NextGen and update MashZone NextGen startup scripts:
    1. Copy the license file terracotta.key to the MashZoneNG-install/apache-tomcat/conf folder.

      If MashZone NextGen is deployed in a cluster, you must copy this file to every cluster member.

    2. Add the following Java system property to the MashZone NextGen server configuration file <MashZone NextGen installation>/apache-tomcat/conf/wrapper.conf:

      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.

  2. Edit the ehcache.xml file for MashZone NextGen in a text editor of your choice.
  3. Find the line in ehcache.xml with <terracottaConfig> that is commented out like this:

    <!-- <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.

  4. Find the line in ehcache.xml with <terracotta> that is commented out and uncomment this line for each of the following named <cache> elements:

    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.

  5. Save these changes to ehcache.xml.

    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.

  6. Start BigMemory Max Server(s).
  7. If needed, adjust memory configuration for the local MashZone NextGen host. See Memory Configuration for the MashZone NextGen Server for instructions.
  8. Restart MashZone NextGen. See Start and Stop the MashZone NextGen Server for instructions.