MashZone NextGen File-Based Configuration and Extensions

Most file-based configuration or extensions involve information that MashZone NextGen needs to connect to the MashZone NextGen Repository or extensions that must be added to the application server’s classpath. In clustered environments, you can share extensions and some of this file-based configuration using an external configuration folder. See MashZone NextGen Configuration Files That Can Be External and MashZone NextGen Extensions for details on resources that can be shared across a cluster.

File

Description and Configuration

Default Location

dynamiccache.xml

Default configuration information for dynamic In-Memory Stores created by MashZone NextGen Analytics.

MashZoneNG-install/apache-tomcat/presto/WEB-INF/classes

ehcache.xml

Configuration information for MashZone NextGen caches. This also contains configuration for MashZone NextGen Analytics In-Memory Stores from version 3.6.

presto.config

Miscellaneous MashZone NextGen properties, including the path to the deployed web app home folder.

rdsJdbc.properties

Connection information for the MetaData and User section of the MashZone NextGen Repository.

Note:

Although MashZone NextGen uses JNDI to connect to the MashZone NextGen Repository, JDBC connection properties are also used in some specific cases.

See Move the MashZone NextGen repository to a robust database solution for details.

The Terracotta BigMemory license file

The license file for BigMemory, used for MashZone NextGen caches and MashZone NextGen Analytics In-Memory Stores, is a separate license file from the MashZone NextGen license. You can keep the BigMemory license in an external folder shared across the cluster.

See Configure BigMemory Servers for MashZone NextGen Caching and In-Memory Stores for required configuration steps to enable a shared license.

userRespositoryLdap.properties

Connection information for your LDAP Directory. See Integrate Your LDAP Directory with MashZone NextGen for details.

For clustered environments, you must copy these configuration files to each cluster member. In most cases, you change configuration once, when you first deploy a MashZone NextGen Server in the cluster. Any subsequent changes to this configuration for one cluster member, however, must be copied to all other cluster members manually, using a scheduled job or using another replication scheme.

File	Description and Configuration
applicationContext-commonServices.xml	You edit configuration in this file if you choose to use distributed response caching for MashZone NextGen. See Configure BigMemory Servers for MashZone NextGen Caching and In-Memory Stores for more information. You may need to update this configuration, as needed, to add additional distributed cache nodes to tune performance.
applicationContext-security.xml	You edit this file initially to enable either SSO authentication or X509 certificate authentication for MashZone NextGen. See Authentication with Single Sign-On Solutions or Authentication with Digital Certificates/SSL for more information.
applicationContext-security-x509.xml	You edit this file initially to enable X509 certificate authentication for MashZone NextGen. See Authentication with Digital Certificates/SSL for more information.
applicationContext-scheduler.xml	You edit this file when you move the MashZone NextGen Repository from the default Derby database to a robust solution. See Move the MashZone NextGen repository to a robust database solution for more information.
log4j.properties	This file is updated automatically when you change logging configuration in the Admin Console. See Configure Logging for the MashZone NextGen Server for details. When you change logging for MashZone NextGen Servers in a cluster, only the specific MashZone NextGen Server that the Admin Console is connected to is affected. To change logging for the entire cluster, you must update this file and copy it to each cluster member.
userRepositoryApplicationContext.xml	You edit these files when you configure MashZone NextGen to use your LDAP Directory as the user repository. See Integrate Your LDAP Directory with MashZone NextGen for details.
userRepositoryApplicationContext-ldap.xml

File	Default Location
Scripts or classes called in mashups in EMML using the <script> statement. This includes: JavaScript files Any Java class that is not in java.lang Groovy scripts See Adding User-Defined Scripting Code to Mashups for details.	MashZoneNG-install/apache-tomcat/presto/WEB-INF/classes or MashZoneNG-install/apache-tomcat/presto/WEB-INF/lib (for JARs)
XSLT stylesheets called in mashups in EMML using the <xslt> statement. See <xslt> for details.
Custom XPath function classes used in mashups in EMML. See Defining Custom XPath Functions for details.
Local copies of WSDL files used for WSDL web services.
Custom security profile classes used with mashables. See Configure Secure Connections for Mashables for details.
Custom certificate validation classes for certificate authentication. See Configure Additional Certificate Validation for details.
Custom filter classes for single sign-on authentication. See Implementing a Custom SSO Filter for details.
Classes and third-party libraries for a user-defined function library to use with RAQL. See Create and Add User-Defined Functions for RAQL Queries for more information.