Instance Configuration

The instance configuration supports four different configuration types:

The following table gives an overview of the supported configuration types, their location and which configuration aspects they cover.

Configuration type

Configuration instance

Location

Covered aspects

General Properties

MashZone NextGenMashZone NextGen properties

<TOMCAT_ROOT>/webapps/

WEB-INF/mashzone.properties

  • Initial resource folder
  • Import/Export folder
  • JDBC drivers folder
  • Feed calculation settings
  • Feed related and general cache settings
  • Event Service endpoit URL
  • PPM connection timeout

General Properties

Presto Config

<TOMCAT_ROOT>/webapps/

WEB-INF/classes/presto.config

  • UI mode "MashZone" or "Classic"
  • SAML2 configuration
  • JWT configuration
  • Landing page welcome text
  • Parts of the SSL configuration (selfsigned, anyhosts)
  • Parameters to control DAO/DB code generation
  • Database DAO service registration options

Memory

-

<TOMCAT_ROOT>/conf/

wrapper.conf

<TOMCAT_ROOT>/conf/

custom_wrapper.conf

  • JVM initial heap size
  • JVM maximum heap size

Jaca Service Wrapper

-

<TOMCAT_ROOT>/conf/

wrapper.conf

<TOMCAT_ROOT>/conf/

custom_wrapper.conf

  • Java home and Java command locations
  • Java Main class to be used
  • Java classpath
  • Wrapper log settings
  • Wrapper Display Name
  • Windows service settings
  • Wrapper files locations
  • ...and some more settings of lower importance

Java System Properties

-

<TOMCAT_ROOT>/conf/

wrapper.conf

<TOMCAT_ROOT>/conf/

custom_wrapper.conf

  • Tomcat location settings
  • File encoding
  • Some RAQL settings
  • Presto classic resource folder
  • Terracotta license key and config timeout
  • Derby locks settings
  • Some file locations concerning event services
  • Optional: Remote JMX settings
  • Optional: Remote debugging settings

<TOMCAT_ROOT> usually is <INSTALL_ROOT>/MashZoneNG/apache-tomcat.

The latter three configuration types are handled by the Tanuki Service Wrapper. It supports a "cascaded" configuration. That means, that only the default configuration is contained in file wrapper.conf. Parameters that were added or manipulated are stored in file custom_wrapper.conf which is included by wrapper.conf. If parameters are contained in both files, the ones in custom_wrapper.conf overwrite the original values in wrapper.conf.

Note: Some important configuration aspects of MashZone NextGen are currently not supported by Command Central. They can be configured by using the MashZone NextGen user interface or by editing specific configuration files. Detailed information on how to configure MashZone NextGen can be found in MashZone NextGen Server Configuration.