This article describes how to configure basic logging using the .props file regardless of whether it is for a main server or slave server. For further assistance, contact email@example.com.
- A server installation directory containing all required files to run the server
- A .props file located in the same directory as the server files
Configuring the Logging
- Name the prop file based on what server it is going to log. Examples:
- Main server: swServer.log
- Slave server: swSlaveServer.log
- Open the .props file in a text editor.
- Select which type of logging - INFO or DEBUG - to set for Log4d.rootCategory= and make one of them active.
- The INFO level designates informational messages that highlight the progress of the application at coarse-grained level. (default)
- The DEBUG Level designates fine-grained informational events that are most useful to debug an application.
Note: When DEBUG level is used, be aware that the size of the file can become quite large.
- Define the file path and name of the log file on the log4d.appender.Fil1.fileName= line.
- Set whether or not the log file should be cleared (=false) after restart of the server application or if logging should append on the log4d.appender.Fil1.append= line. The default of append is recommended.
- Save your changes.
Example of INFO-level logging for swSlaveServer
Starting the Logging
Logging will start once you start/restart the server application.
Note: If a server application GUI is open while you complete the configuration, it must be first closed and then reopened prior to the start/restart for the logging to begin successfully.