Diagnostic Utility Performance
The diagnostic utility can execute slowly when logging large amounts of data from the Integration Server and, possibly, layered products. To increase performance, you can set limits to the amount of data the diagnostic tool returns by specifying a maxLogSize value or setting the watt.server.diagnostic.logperiod parameter.
The maxLogSize parameter of the wm.server.admin:getDiagnosticData service sets the size limit for log files written to the diagnostic_data.zip file. If a log file exceeds the specified maxLogSize, the diagnostic utility omits it from the .zip file but records it in a diagnosticwarning.txt file. This file lists all of the log files that exceed the maxLogSize value. It is located in the logs directory of the .zip file.
Note:
You can use the
maxLogSize input parameter only when running the diagnostic utility from a browser. You cannot limit the log size when you run the diagnostic utility from
Integration Server Administrator. For more information, see
Running the Diagnostic Utility
Service.
Use the
watt.server.diagnostic.logperiod parameter to specify the log period. By default, it is set to 6 hours. When this property is set to 0, the utility does not return any log files. It returns only the configuration and run-time data files. The logging information the utility returns depends on how you store the logs. If you save the logs to a database, the diagnostic utility will return the exact number of log entries that match the specified number of hours. If you save the logs to the file system, it will return not only the period within the specified number of hours but the entire log for that day. For instructions about how to set server configuration parameters, see
Working with Extended Configuration Settings.
The logging information the diagnostic utility returns also depends on whether logs from layered products are included in the .zip file. A layered product is any product that runs on top of Integration Server such as ActiveTransfer or Trading Networks Server. Layered products can include product-specific log files in the diagnostic utility by registering their product logs with the utility.
Use the watt.server.diagnostic.logFiles.maxMB parameter to specify the size limit for including audit log files in the diagnostic archive. While collecting each audit log file, Integration Server calculates the total size of the log files for the requested log period. If the total size of the log files for a particular audit log exceeds the value of watt.server.diagnostic.logFiles.maxMB for the log period, Integration Server does not include that audit log file in the diagnostic archive. The size limit applies to all log files included in the diagnostic archive, including log files produced by layered products.
Consider the examples below.
Example 1
watt.server.diagnostic.logFiles.maxMB is 250 and
watt.server.diagnostic.logperiod is 6.
There are two WMSESSION log files that cover the previous six hours.
The total size of the two WMSESSION log files is greater than 250 MB.
RESULT: No session audit log data will be included in the diagnostic data archive.
Example 2
watt.server.diagnostic.logFiles.maxMB is 300 and
watt.server.diagnostic.logperiod is 8
There is one WMSERVICE log file that covers the previous eight hours.
The size of the WMSERVICE log file is less than 300 MB.
RESULT: Service audit log data will be included in the diagnostic data archive.