Parameters Only Found in maconfig.conf

Certain parameters are not exposed to the web interface. In some cases, the defaults are expected to provide the best scenario; in others there are practical limitations to exposing the parameter (for example, changing web server port).

  • Windows service configurations: a collection related to how the service behaves in Windows. Among these are heap size parameters (wrapper.java.initmemory, wrapper.java.maxmemory) and Java class path (wrapper.java.classpath.x).

  • Wrapper Logging Properties: a collection related to logging behavior:

    • wrapper.console.loglevel

      Log level to use for console output. Valid log levels include: NONE for no output, FATAL to only show fatal error messages, ERROR to show all error messages, STATUS to show all state changes, INFO shows all JVM output and informative messages, and DEBUG shows detailed debug information. The default value is INFO.

    • wrapper.logfile

      Log file to which all output to the console will be logged. If the logfile is not specified, then file logging will be written to a file called "wrapper.log" in a log directory in the installation directory. Providing a blank value will cause file logging to be disabled.

    • wrapper.logfile.format

      Format to use for logging to the log file. Logging was intentionally kept simple. The format consists of the tokens 'L' for log level, 'P' for prefix, 'D' for thread, 'T' for time, 'Z' for millisecond time, and 'M' for message. If the format contains these values then it will be included in the format. The order of the tokens does not affect the way the log appears, but the 'M' token should usually be placed last as it is the only column without a uniform width. If the property is missing or commented out, then the default value 'LPTM' will be used. Setting the property to a blank value will cause file logging to be disabled.

    • wrapper.logfile.loglevel

      Log level to use for logging to the log file. Valid log levels include: NONE for no output, FATAL to only show fatal error messages, ERROR to show all error messages, STATUS to show all state changes, INFO shows all JVM output and informative messages, and DEBUG shows detailed debug information. The default value is INFO.

    • wrapper.logfile.maxsize

      The wrapper.log file can be set to roll when the file reaches a specified size. The default value of 0 will disable log file rolling. To roll the file, specify a maximum file size in bytes. The size can be abbreviated with the suffixes 'k' for kilobytes, or 'm' for megabytes. For example, '10m' sets the log file to be rolled when it reaches a size of 10 megabytes.

    • wrapper.logfile.maxfiles

      When log file rolling is enabled, old log files will be renamed by appending an integer to the end of the file. Larger indices are older log files. The maximum number of rolled log files can be set using this property. The default value, 0, implies no limit on the number of files. If this number is reduced from say 10 to 5, the extra 5 files will not be deleted, new log files will only be rolled within the first 5 indices.

    • wrapper.syslog.loglevel

      Log level to use for logging to the Event Log on Windows systems, or the syslog on unix systems. Valid log levels include: NONE for no log output, FATAL to only log fatal error messages, ERROR to log all error messages, STATUS to log all state changes, INFO logs all JVM output and informative messages, and DEBUG logs detailed debug information. The default value is NONE. Be careful setting log which are too low. DEBUG for example will very quickly fill up your syslog or event log.

  • Wrapper NT Service Properties: These properties may not be modified while FileCatalyst Central is installed as a service. Please uninstall the service before modifying, and then reinstall the service once complete.

    • wrapper.netservice.name

      Name of the NT service when installed.

      WARNING: Never change the value of this property while an application is installed as a service. Doing so will make it impossible to uninstall the service. Always remove an existing service before changing the name. The service with the new name can then safely be reinstalled.

    • wrapper.ntservice.displayname

      Display name of the NT service when installed.

    • wrapper.ntservice.starttype

      Mode in which the service is installed. AUTO_START starts the service automatically when the system is rebooted. Or DEMAND_START which requires that the service me started manually.

    • wrapper.ntservice.interactive

      Setting the interactive property to true will make it possible for the service to display a GUI and have access to the desktop when run as a service. The default is false, or a non-interactive service.