Enabling and configuring application server logging

Enabling diagnostic logging for the MDM operational server is accomplished by using WebSphere® Application Server Administration Console.

1. Open the WebSphere Application Server Administration Console.
2. Expand Troubleshooting and select Logs and trace. After Logs and trace is selected, the list of servers is presented.
3. Select the server where the operational server is deployed. The Logs and trace screen for the server is displayed.
4. Select Diagnostic Trace from the General Properties links. The Diagnostic Trace service panel is displayed and contains two tabs: Configuration and Runtime.
5. Select the Runtime tab for changes to take effect immediately. Changes on the Configuration tab take effect only when the server is restarted.
6. Note the Trace Output settings for File. Make sure the Maximum File Size and Maximum Number of Historical Files are large enough to capture the information you want to collect. Depending on the logging settings and the period of time to be traced, you can increase the values.
7. Click the Change log detail levels link under Additional Properties. The Change log detail levels screen is displayed.
8. Expand the Components and Groups item under Change log detail levels. You can browse a hierarchy of known loggers.
9. Find the component that you want to enable detailed logging for in the hierarchy. Use the table that follows to determine which logging level to use with each component based on your needs.
10. Set the logging levels. The text box shows your updated selection.
11. Click Apply.

    Table 1. Configuration components for the WebSphere Application Server

    Component	Description
    com.dwl.*	This component is one of four root components that in aggregate cover the largest portion of the operational server. You can indicate a specific component in lieu of the asterisk (*) to narrow the focus to a particular feature.
    com.ibm.mdm.*	This component is one of four root components that in aggregate cover the largest portion of the operational server. You can indicate a specific component in lieu of the asterisk (*) to narrow the focus to a particular feature.
    com.initiate.*	This component is one of four root components that in aggregate cover the largest portion of the operational server. You can indicate a specific component in lieu of the asterisk (*) to narrow the focus to a particular feature.
    com.initiatesystems.*	This component is one of four root components that in aggregate cover the largest portion of the operational server. You can indicate a specific component in lieu of the asterisk (*) to narrow the focus to a particular feature.
    Special components
    com.ibm.mdm.mds.log.NativeLog	Set to FINE to enable debug information or FINEST for trace information.
    com.ibm.mdm.mds.log.AlgorithmLog	Set to ALL to enable detailed Algorithm logging.
    com.ibm.mdm.mds.log.AuditLog	Set to ALL to enable audit logging.
    javax.sql.*	Set to ALL to enable database SQL logging.
    com.ibm.mdm.mds.log.PerformanceLog	Set to ALL to enable performance logging.
    com.ibm.mdm.mds.log.TimerLog	Set to ALL to enable timer logging.