Integration Server 10.3 | Integration Server Administrator's Guide | Diagnosing the Integration Server | Using the Diagnostic Utility
 
Using the Diagnostic Utility
 
Diagnostic Utility Performance
Running the Diagnostic Utility from Integration Server Administrator
Running the Diagnostic Utility Service
You use the diagnostic utility to collect configuration, operation, and logging data from the Integration Server. You can also use the diagnostic utility to view the list of fixes applied to the installed packages and Integration Server. The diagnostic utility is an Integration Server service called wm.server.admin:getDiagnosticData. It is accessible only by members of the Administrators group. Although you run the utility via the diagnostic port to troubleshoot, it can also be used with any HTTP or HTTPS port to collect diagnostic data periodically. You can access the service through the Get Diagnostics button in Integration Server Administrator.
The diagnostic utility creates a temporary diagnostics_hostname_port_yyyyMMddHHmmss.zip file in the Integration Server_directory \instances\instance_name\logs directory and writes to the .zip file as it collects information. It also contains a config\PackagesAndUpdates.txt file, which lists the packages and package updates for the Integration Server.
If there are problems creating the .zip file, such as insufficient space in the file system, it will return a text file. In the text file, the configuration and operation data are separated into distinct sections for easier reading. Unlike the .zip file, the text file does not contain logging data.
The .zip file contains a file in the config directory called PackagesAndUpdates.txt. This file lists the packages and package updates for the Integration Server.