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