productEvent.xml. Reports the name of products that caused events reports in the logs.productEvent.xml. Reports the name of products that caused events reports in the logs.loggerEvent.xml. Reports the names of components that caused the event reports in the logs.logLevel.xml. Reports a summary of all available events found in the logs.messageBased.xml. Reports a summary of the issues with common message texts found in the logs.componentEvent.xml. Reports the Java artifacts such as jars, portlets, or web applications that caused the events found in the log.On Windows: loganalyzer.bat logFile [options]On UNIX./loganalyzer logFile[options]Arguments and Options | Description |
logfile | Specifies the full directory path and name of the log file to analyze, or specifies a directory that contains the errors.log file. When you provide a directory without specifying a filename, the loganalyzer command searches for a log file by checking the subdirectories for file names matching the following: errors.logerrors.xmlerrorsThe loganalyzer command scans the first file matching the file name criteria for warn, error, and fatal events that are generated by My webMethods Server. |
{-f | --from-date} | Specifies the date from which to start analyzing the selected log file. Use yyyy.MM.dd HH:mm:ss format for the date or use days (d) or hours (h), for example, 2d or 3h. This captures information from the logs that occurred within the specified time period (or, for example, the logs that have been modified in the last 3 hours). The default value is 1970.01.01 02:00:00. |
{-t | --to-date} | Specifies the date to stop analyzing the selected log file. Use yyyy.MM.dd HH:mm:ss format for the date or use days (d) or hours (h), for example, 2d or 3h. This captures information from the logs that occurred prior to the specified date (or, for example, logs that have been modified up until 3 hours ago). The default value is 1970.01.01 02:00:00. |
{-i |--similarity} | Specifies a percentage for the similarity level by which log messages are considered equal or dissimilar. |
{-j | --javaArtifactMapping} | Specifies the full path to the directory of the javaArtifactMapping.xml file. If you do not specify a location for the javaArtifactMapping.xml file, the loganalyzer searches for the file in the following locations: When you provide only a directory location for the logfile argument, the loganalyzer searches for the javaArtifactMapping.xml file in the specified directory.When you provide a directory location and file name for the logfile argument, the loganalyzer searches for the javaArtifactMapping.xml file by traversing the directories to find the logfile and then does the same search to find the javaArtifactMapping.xml file. For example, if the logFile is in C:\Directory1\Directory2\Directory3\errors.log, then the expected location and name of the JavaArtifactMapping.xml is C:\Directory1\Directory2\config\javaArtifactMapping.xml file. |
{-s | --server} | Specifies a server available on the local system. When you do not specify a server instance, the loganalyzer uses the default My webMethods Server instance. |
{-a | --action} | Specifies the information type to analyze. The default value is frequency. The valid values for this option are as follows: all captures information about all messages.frequency captures information about messages by the frequency of their appearance.severity captures information about messages according to their severity.Note: You can specify the {-e |--severity} option to narrow the results in the frequency report to include only the results that have a severity level you specify. component captures information about environment-related messages.product captures information about Java-related messageslogger captures information about database-related messages. |
{-e |--severity} | Reports on the severity level that you supply. You can only use this option when also using the action option with the frequency value. The default value is INFO. Specify one of the following severity levels: DEBUGERRORFATALINFOWARN |
{-x | --xml} | Displays XML output in the console window. |
{-o | --output} | Saves the XML output to a file on the file system and does not display it in the console window. Valid only with the {-x | --xml} option. |
{-h | --help} | Displays command help text about the command, the available options and arguments, and default values. |
The loganalyzer command detects changes resulting from installing a single fix of the product because the version numbers of the internal JAR files and the product components might differ.If you specify that you want the loganalyzer command to provide component-oriented output that displays the components that cause the events in the log, loganalyzer also lists fixes, if any, that are applied to the components.Before running the loganalyzer command, you might want to update the javaArtifactMapping.xml file if you have installed and deployed any custom components on My webMethods Server. To update the javaArtifactMapping.xml file, see Updating the Java Artifact Mapping
File.After running the loganalyzer command and determining the product and component raising errors, you might want to narrow your results. You can exclude classes of that component and product from the logging information and the displayed statistics. The next time you run loganalyzer, the result shows other components and products from the stack trace that are possible candidates responsible for the error. Use the excludedMappingClasses.xml file to list class names to exclude from the query of components and products that cause errors.The loganalyzer command uses the errors.log which is a log4j-produced result. For more information, see Log4j.Windows example:UNIX example:The following example shows a loganalyzer command that uses the default {-a | --action} argument frequency to capture log information by the frequency of appearance. In this case, this creates a frequency report from a log4j XML file produced by the dbintegritycheck command. The example command also includes the --severity ERROR option to narrow the results so that the frequency report includes only items with severity level ERROR: