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 Administration | Deploying MashZone NextGen Instances, Clusters or Artifacts | Setting Up an External MashZone NextGen Configuration Folder | MashZone NextGen File-Based Configuration and Extensions
 
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.
Some file-based configuration, however, must reside in the web application for each MashZone NextGen Server. In clusters, this configuration must be replicated in each cluster member. See MashZone NextGen Configuration Files That Must Be Internal for details.
MashZone NextGen Configuration Files That Can Be External
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/mashzone/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.
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.
MashZone NextGen Configuration Files That Must Be Internal
The file-based configuration that must remain in each MashZone NextGen Server web application resides in the web-apps-home/mashzone/WEB-INF/classes folder.
For upgrades to new MashZone NextGen versions, you can generally copy these configuration files from your existing MashZone NextGen version to the new version. Review the MashZone NextGen Release Notes for changes or new features that may require updates to configuration.
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
MashZone NextGen Extensions
Some extensions, such as macros, are registered and reside in the MashZone NextGen Repository. Any of the following file-based extensions can reside in an external folder:
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
MashZoneNG-install/apache-tomcat/mashzone/WEB-INF/classes
or
MashZoneNG-install/apache-tomcat/mashzone/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.

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