Production System logs information during its operation. By default, the log file is saved in the current user's log directory (on Windows, this is C:\Users\<user>\AppData\Roaming\STR\SuperSERVER SA\logs).
You can configure the settings for logging by modifying log4j.sa2ps.properties, which is located in the SuperSERVER program data directory (by default, C:\ProgramData\STR\SuperSERVER SA).
Logging is provided by the Apache component Log4j, which has six levels of logging. These levels are (listed in order, from most verbose to least verbose):
|Most verbose. All possible messages are written to the logs.|
|Logs everything except |
|This is the default setting. Recommended for production use. Logs |
|Logs only |
|Logs only |
|Least verbose. Only |
Increase or Decrease the Amount of Information Logged
By default, Production System is configured to log at the
INFO level. This means that all
FATAL messages are logged.
You can change this by editing the following line:
For example, to change to the
DEBUG level, you could change this to:
This will configure Production System to log
DEBUG messages, in addition to
Change the Log File Location
By default the Production System log file is written to the current user's log directory. You can change the location of the log output by removing the comment from the start of the following line and setting the value to the location you want to generate the log file:
You can either use a relative path or an absolute path. For example:
The following setting configures the log file location to be a directory called logs within the current directory (this is relative to the current directory from which you ran Production System).BASH
The following setting configures an absolute file path for the log file.BASH
Other SuperSTAR components have their own individual logging settings. For more information, see:
In addition, SuperSTAR has an optional Audit Logging component that can be used to track user activity.
For more information about Log4j, refer to the Apache documentation: http://logging.apache.org/log4j/1.2/manual.html.