This topic describes where to find log messages and trace information for Everyplace Mobile Portal extensions, Multi-Channel Server, and Image Conversion Service.
When the Everyplace Mobile Portal components are installed with WebSphere Portal, the log messages and trace information appear in the WebSphere Portal log files. When Multi-Channel Server is installed with a messaging Web application or Image Conversion Service is installed, the log and trace information appear in the SystemOut.log log file for the application server to which these components are mapped.
Log location | Description |
---|---|
wp_root/log/ConfigTrace.log | Contains installation messages and errors. See the Installing topics in this information center for details on when you should examine this log file. |
wp_root/log/SystemOut.log | Contains startup messages and system output messages |
wp_root/log/SystemErr.log | Contains errors from uncaught exceptions and system error messages |
wp_root/log/wps_date_time.log | Contains WebSphere® Portal Server, Multi-Channel Server, and Mobile Portal extension log messages and trace information. Also contains the Everyplace Mobile Portal build information. date_time is the date and time the file was created. |
The following table lists the Everyplace Mobile Portal trace strings that can be specified in the wp_root/shared/app/config/log.properties file or by using the Enable Tracing portlet ( ).
If you are uncertain which components to enable tracing for, enable the top-level trace strings for both WebSphere Everyplace Mobile Portal Enable extensions (com.ibm.mwp.*=all=enabled) and the Multi-Channel Server (com.volantis.*=all=enabled).
Component | Description | Trace String |
---|---|---|
WebSphere Everyplace Mobile Portal Enable extensions | Traces all WebSphere Everyplace Mobile Portal Enable extension classes. | com.ibm.mwp.*=all=enabled |
Manage Mobile Pages Portlet | Traces the Manage Mobile Pages portlet. | com.ibm.mwp.portlets.mobilepages.*=all=enabled |
Extended Properties Portlet | Traces the Extended Properties portlet. | com.ibm.mwp.portlets.extattr.*=all=enabled |
Preload Notice Portlet | Traces the Preload Notice portlet. | com.ibm.mwp.portlets.preloadNotice.*=all=enabled |
Utility classes | Traces common utility/helper classes. | com.ibm.mwp.util.*=all=enabled |
Metadata classes | Traces classes associated with retrieving meta-data. | com.ibm.mwp.metadata.*=all=enabled |
Rules for metadata | Traces classes used for rules resolution. | com.ibm.mwp.metadata.rule.*=all=enabled |
Aggregator helper classes | Traces helper classes used by the XDIME aggregator. | com.ibm.mwp.util.aggregation.*=all=enabled |
XDIME tag library | Trace all tags in the XDIME tag library. | com.ibm.mwp.tags.xdime.*=all=enabled |
Preload notice datastore classes | Traces the preload notice datastore classes. | com.ibm.mwp.db.user.*=all=enabled |
Multi-Channel Server | Traces all Multi-Channel Server classes | com.volantis.*=all=enabled |
Multi-Channel Server Servlet Filter | Traces XDIME markup created by the XDIME aggregator and XDIME portlets. | com.volantis.mcs.servlet.XDIMERequestProcessor=all=enabled |
Virtual portal |
Enables tracing for the Login portlet and vpMapper functionality. The Login portlet trace information includes WebSphere Portal Login portlet information. Trace information uses the CWMPA message ID prefix. |
com.ibm.mwp.portlets.login.*=all=enabled com.ibm.mwp.tags.xdime.*=all=enabled |
Log location | Description |
---|---|
was_root/profiles/profile_name/logs/application-server-name/SystemOut.log where application-server-name is the name of the application server to which the messaging Web application or Image Conversion Service is mapped. | Contains startup messages and system out messages. |
was_root/logs/application-server-name/SystemErr.log where application-server-name is the name of the application server to which the messaging Web application or Image Conversion Service is mapped. | Contains errors from uncaught exceptions and system error messages. |
The trace and log messages for Multi-Channel Server and Image Conversion Service are logged only to these files. This is true even if you enable diagnostic tracing to a trace file (for example, trace.log) from the WebSphere Application Server Administrative Console.
For more information on using the Administrative Console to enable diagnostic tracing, see the WebSphere Application Server information center.
Message type | Description |
---|---|
debug | Enables tracing information and informational, warning, error, and fatal logging messages. |
info | Enables informational, warning, error, and fatal logging messages. |
warn | Enables warning, error, and fatal logging messages. |
error | Enables error and fatal logging messages. |
fatal | Enables severe error logging messages. |
Error and fatal log messages are enabled by default and are logged to wp_root/log/wps*date_time.log files when Multi-Channel Server is installed with WebSphere Portal. When Multi-Channel Server is installed with a messaging Web application or when Image Conversion Service is installed, the error and fatal log messages will be logged to was_root/profiles/profile_name/logs/application-server-name/SystemOut.log where application-server-name is the name of the application server to which the messaging Web application or Image Conversion Service is mapped.
For Multi-Channel Server (MCS), you can enable other logging levels and enable tracing tracing either by modifying the MCS logging configuration file or by using the MCS manager.
You
Edit the log.properties file through the WebSphere Application Server Integrated Solutions Console or by using a text editor. When editing the file, specify a trace string for the MCS component (for example, com.volantis.*=all=enabled).