IBM MobileFirst™ Platform Foundation reports errors, warnings, and informational messages into a log file. The underlying logging mechanism varies by application server.
IBM MobileFirst Platform Server (MobileFirst Server for short) uses the standard java.util.logging package. By default, all MobileFirst logging goes to the application server log files. You can control MobileFirst Server logging by using the standard tools that are available in each application server. For example, if you want to activate trace logging in WebSphere® Application Server Liberty, add a trace element to the server.xml file. To activate trace logging in WebSphere Application Server, use the logging screen in the console and enable trace for MobileFirst logs.
MobileFirst logs all begin with com.ibm.mfp.
Application Center logs begin with com.ibm.puremeap.
Application server | Location of documentation |
---|---|
Apache Tomcat | http://tomcat.apache.org/tomcat-7.0-doc/logging.html#Using_java.util.logging_(default) |
WebSphere Application Server Version 8.5 full profile | http://ibm.biz/knowctr#SSEQTP_8.5.5/com.ibm.websphere.base.doc/ae/ttrb_trcover.html |
WebSphere Application Server Version 8.5 Liberty profile | http://ibm.biz/knowctr#SSEQTP_8.5.5/com.ibm.websphere.wlp.doc/ae/rwlp_logging.html?cp=SSEQTP_8.5.5%2F1-16-0-0 |
MobileFirst Server uses the java.util.logging API. The logging levels map to the following levels:
For Apache Tomcat, you can use IBM® Operations Analytics - Log Analysis or other industry standard log file monitoring tools to monitor logs and highlight errors and warnings.
For WebSphere Application Server, use the log viewing facilities that are described in IBM Knowledge Center. The URLs are listed in the table in the MobileFirst Server section of this page.
When the audit log is enabled, you can download it from MobileFirst Operations Console by clicking the Audit log link in the footer of the page.