More support for:
AIX, Linux, Windows, z/OS
17 June 2018
Collecting data for WebSphere issues
Merative ™ Social Program Management is now Cúram™ by Merative
Collecting data for Cúram™ by Merative WebSphere Issues
Question & Answer
What data is required when handling Performance and Configuration of Java issues on Websphere with Cúram? The information that you gather is also known as MustGather information.
The WebSphere logs of interest include:
The default location for JVM logs, FFDC logs, and Verbose GC logs, when configured, is the logs folder of the WebSphere profiles, for example:C:/IBM/WebSphere/AppServer/profiles/<profile_name>/logs.
Each server within the logs folder has a sub folder and the FFDC logs are stored in the logs\ffdc folder for the profile. So a copy of this folder, preferably in compressed format, is the easiest, most reliable way of gathering WebSphere logs since the JVM logs might be in multiple files. However, configuration options per server within WebSphere are available to adjust the JVM log location, size, and management strategy.
Your gathering of WebSphere logs needs to take into account any customisation. Depending on the nature of the issue, the logs for each profile including the deployment manager might be necessary.
To Configure JVM Verbose Garbage Collection
Due to its low overhead and value in identifying performance issues with the JVM, it is recommended that Verbose GC is always enabled and monitored in production environments.
In the WebSphere administrative console for each relevant server designated by <server_name>:
Processing Verbose GC Data
To process the verbose GC logs locally, use the IBM Monitoring and Diagnostics Tools for Java - Garbage.