How do I configure the mscm_logging.properties file?

The mscm_logging.properties file controls how the mscm_server.log is written. They can be configured by entering the following commands:

  • log4j.rootLogger=DEBUG, ROOT - Changes the type of logging. The options are INFO, ERROR and DEBUG.

  • log4j.appender.ROOT.MaxFileSize=2000KB - Increases or decreases the size of the logs . Typically you will want to increase the size of the file if the mode is set to DEBUG, as the logs roll over quickly at the default 2000KB size.

  • log4j.appender.ROOT.MaxBackupIndex=100 - Defines how many logs are to be created. The default is 100 logs.

Note: 

Debugging specific class files is another method to control how the mscm_server.log is written. After you determine which class files that are to be output as DEBUG lines, set the rootLogger=INFO and add the class file to the bottom of the mscm_logging.properties. Then, add a prefix of "log4j.logger." to the front of the string and "=DEBUG" to the end. This creates a much more manageable log file that debugs only the class files that you have specified.

There are two methods of applying changes made to logging in the mscm_logging.properties file:

  • Update the mscm_logging.properties file in <MSCM>/config and run the log4jgraft script from the same directory to apply the changes. The log4jgraft pushes the changes out to the <WAS_HOME>/profiles/<profilename>/properties directory

  • Update the mscm_logging.properties directly in the WebSphere path <WAS_HOME>/profiles/<profilename>/properties. This method only requires that you save the file for the changes to be applied to the mscm_server.log.