Change the message IDs used in log files

 

+

Search Tips   |   Advanced Search

 

Overview

You can change the default format for message IDs in server logs by setting the system property...

com.ibm.websphere.logging.messageId.version

In new releases of WAS, logging files will be formatted according to a standardized system. However, the default runtime behavior is still configured to use the older format. In new releases of WAS the message IDs written to log files will be changed to ensure they do not conflict with other IBM products. The default runtime behavior is still configured to use the older message IDs, deprecated in V6.1.

The following is a sample of an entry in a trace.log file using a default message ID. Note that the message ID is PMON0001A

[1/26/05 10:17:12:529 EST] 0000000a PMIImpl       A   PMON0001A: PMI is enabled

A sample of the same entry using a new message ID follows. Note that the message ID is CWPMI0001A. All new WAS message IDs begin with 'CW'.

[1/26/05 10:17:12:529 EST] 0000000a PMIImpl       A   CWPMI0001A: PMI is enabled.

If you are using a logging tool that uses the new standardized format, you might want to change the default configuration settings to format the logging output appropriately. You will need to change the configuration for each JVM in the cell if you want the output formatting to be the same across appservers.

 

Procedure

To configure message logging to be compliant with the new standard, use wsadmin to execute...

 set jvmEntry [$AdminConfig list JavaVirtualMachine]

$AdminConfig create Property $jvmEntry 
{
    {
        name com.ibm.websphere.logging.messageId.version
    } 
    {
        value 6
    } 
    {
        required false
    }
}

Do this for each JVM in the cell for consistent output formatting.

Restart the appserver for the changes to take effect.

 

Results

---

Convert log files to use IBM unique Message IDs
convertlog command
MessageConverter class