The PowerConnect application is able to extract data from over two thousand JMX Beans in the SAP system. These JMX Beans can be leveraged for SAP performance use cases.
Potential Use Cases
This event could be used in the following scenarios:
Count of heap memory dumps over time
Visualize system CPU architecture and Java version
Alert on garbage collection
PowerConnect Administrative Console Configuration
Important: None of the configurations below requires a restart of the PowerConnect agent.
There are two methods that can be used to configure the list of enabled JMX Beans in the PowerConnect Java application. Both methods are documented below:
Configuring via User Interface
Log into the PowerConnect administrative console via the following URL (http://<serverhost>:<port>/webdynpro/resources/com.powerconnect5/spcj_wd/SapPowerConnectJava#). Then click on the JMX tab.
The list of available JMX Beans is displayed on the top half of the screen, and the bottom half of the screen shows the list of JMX Beans enabled.
To enable a new JMX Bean, click on the JMX Bean of interest, and then add it to the list below using the arrow button.
The JMX Beans will then be added to the list of Enabled JMX beans below.
Then Save using the button at the bottom of the screen.
To disable a JMX Bean click on the respective line in the “Enabled JMX Beans” section and move it to the top. Save the configuration afterwards.
Configuring Using XML File
The enabled JMX Beans can also be exported and imported using an XML configuration file. The schema of the XML file is very simple – as an example:
You can edit this file to include the JMX Beans that you would like to see in Splunk. To access the list of available JMX Beans and XML configuration, please log into the PowerConnect administrative console via the following URL (http://<serverhost>:<port>/webdynpro/resources/com.powerconnect5/spcj_wd/SapPowerConnectJava#). Then click on the JMX tab.
The list of available JMX Beans is displayed on the top half of the screen, and the bottom half of the screen shows the list of JMX Beans enabled. To export the JMX config click on the JMX Export button on the bottom of the screen.
Once the XML file has been exported, modify as desired. Once the XML file has been edited as desired, you can import the configuration by selecting the file using the “Choose file” button, find the XML file on your computer/server, and then select the Import button. Save.
You will see a Popup Window display the message “Successfully imported JMX Configuration” and the Enabled JMX Beans table should be automatically updated to reflect the newly applied configuration.
JMX Bean Reference
Here are some useful MBeans with their fields and associated descriptions:
System cpu architecture
Number of cpu cores
Free physical RAM on the host system
Used virtual memory
Free swap space
Maximum number of file descriptors available
Operating System name
Used file descriptors
Cpu load of the Java process
Cpu time of the Java proces
Cpu load of the host system
Cpu load average of the host system
Total physical RAM available on the host system
Operating System version
Memory Pool Name
Memory pool initial size
Memory pool commit size
Memory pool used size
Memory pool maximum size
Type of memory that the pool uses e.g. HEAP or NON_HEAP
The accumulated time the Java process has spent doing JIT compilation (milliseconds)
Type of Garbage Collector configured e.g. Concurrent Mark Sweep
Number of times the Garbage Collector has run since the Java process was started
The accumulated time the Garbage Collector has run
Number of threads used to run the Garbage Collector
How long the last Garbage Collector run took
Milliseconds since Java process was launched
Milliseconds since Java process was launched
Information about the committed, initial, max and used memory before the Garbage Collection event
Information about the committed, initial, max and used memory after the Garbage Collection event
Process ID of the Java Process
Boot Classpath of the Java process
Classpath of the Java process
Array of arguments with which the Java process was started
Time in Epoch format the Java process was started
The number of milliseconds the Java process has been running
Array of system properties with which the Java process was started
Number of daemon threads running
Number of threads running currently
Maximum number of threads running since the Java Process was started
Total number of threads started since the Java Process was started
Please note the fields displayed will vary depending on which Java MBean is selected. The event will look like this in Splunk: