Using the JMX Server process with ITCAM DC and how to temporarily stop it.

Body

When you install the Data Collector (DC) v7.2 IF12 with the WAS YN agent v7.2 IF5 or higher, you will see an "extra" JMXServer process running on your server, in addition to the regular DC.  This JMXServer process is used to gather PMI data that's obtained from the monitored WebSphere server.  The JMXServer process will act as a JMX client to transfer data from WebSphere to the YN agent.  This JMXServer process is related to the DC-less feature that was introduced in the WAS YN agent v7.2 IF5 on-wards.

Although its harmless if you have the JMXServer running (it doesn't consume much CPU), there may be cases where you may wish to stop it temporarily or permanently.  For example, there may be conflicts if you are using an LDAP server on the same network, and your authentication credentials may conflict with the authentication credentials in the connection.properties file in the runtime/* folder of the DC.  Or, you just don't want the "extra" process around if you are already using a full-fledged DC. 

There are several ways to do this:

• simply use a "exit 0" inside the JMXServer.sh script, somewhere right at the top of the file (make backup of file first.) In this case, the script will simply exit out early in the process and not do anything.
• another option would be to simply rename the file ../config/gdc_install_history.txt itself, and that will stop the JMXServer process from running/spawning.  (Note: do this only if you have a regular full-fledged DC.)

Good luck. 

Noel Lewis

ITCAM / APM / ICAM L2 Support team

Subscribe and follow us for all the latest information directly on your social feeds: