Enable the Java virtual machine profiler data

Use the Java virtual machine profiler to enable the collection of information.

Overview

Use the Java Virtual Machine Tool Interface (JVMTI) to collect data about garbage collection and thread states from the JVM that runs the application server. When JVMTI is enabled, a collection of JVMTI-specific statistics can be enabled through the predefined All statistic set or through the use of a Custom statistic set.

To enable JVMTI data reporting for each individual application server:

Procedure

1. Open the administrative console.

2. Click Servers > Application Servers in the administrative console navigation tree.

3. Click the application server for the JVM profiler that needs enabling.

4. Click Java and Process Management under Server Infrastructure.

5. Click Process Definition.

6. Click Java virtual machine under Additional properties.

7. Type -agentlib:QWASJVMTI in the Generic JVM arguments field.

   Note: If the deprecated JVMPI profiler is used in WebSphere Application Server V6.1, type -XrunQWASJVMPI in the Generic JVM arguments field. For more information, refer to Java virtual machine profiling.

8. Click Apply or OK.

9. Click Save.

10. Click Servers > Application Servers in the administrative console navigation tree.

11. Click the application server for the JVM profiler that needs enabling.

12. Click the Configuration tab. When in the Configuration tab, settings apply when the server is restarted. When in the Runtime Tab, settings apply immediately. Performance Monitoring Infrastructure (PMI) can be enabled only in the Configuration tab.

13. Click Performance Monitoring Infrastructure under Performance.

14. Select the Enable Performance Monitoring Infrastructure (PMI) check box.

15. Click Custom and select JVM Runtime on the left-side tree.

16. Click a JVM profiler group under JVM Runtime and enable or disable the statistic on the right-side table. Go back to the main PMI configuration page, by clicking PMI.

17. Click Apply or OK.

18. Click Save.

19. Start the application server, or restart the application server if it is currently running.

20. Refresh the Tivoli Performance Viewer if you are using it. The changes you make will not take effect until you restart the application server.

Related tasks