BMC Remedy ITSM - Mobility server is unable to generate logs

If the BMC Remedy ITSM - Mobility server is not generating logs, perform the following steps:

1. Verify that the logging path from the logs4j-config.xml file in the <MobilityServerDir>\MobilityServer\WEB-INF\classes directory is correct.

2. Edit the all appenders in the logs4j-config.xml file with your log file destination.
    Following is an example of an appender. Update the following value with the correct path:
   <param value="D:/Program Files/Apache Software Foundation/Tomcat 7.0/logs/mobility-stdout.log"/> 

   
   <appender name="stdout">
       <param value="D:/Program Files/Apache Software Foundation/Tomcat 7.0/logs/mobility-stdout.log"/>
       <param value="8MB"/>
       <param value="5"/>
       <layout>
         <param name="ConversionPattern"
           value="%d{ISO8601}{GMT} +0000 %-5p [%X{flexClient}%X{userLoginId}%c{1}] - %m%n"/>
       </layout>
     </appender>
   
3. Verify that the log level is set correctly in the Cluster tab in the Admin Console. The log level determines the amount of logs to be generated. Error level means that only errors will be entered in the log file.