Pinned topicConfiguring Hyperic HQ 4.6.6 with stand alone WXS8.5

‏2012-10-23T20:30:54Z
|Tags:

Answered question
This question has been answered.

Unanswered question
This question has not been answered yet.

Hi,

Having some problem trying configure hyperic with WXS stand alone environment. I am able to install both server and agents(one on each JVM for containers). I have followed the same steps mentioned in the infocenter here with some changes as applied to hyperic latest version(directory structure).

23-10-2012 15:07:41,283 CDT ERROR Thread-6NullScan@88 AutoScan failed for WebSphere eXtreme Scale 7.1
org.hyperic.hq.product.PluginException: java.lang.NullPointerException
at org.hyperic.hq.plugin.extremescale.XSServerDetector.getServerResources(XSServerDetector.java:151)
at org.hyperic.hq.autoinventory.scanimpl.NullScan.scan(NullScan.java:81)
at org.hyperic.hq.autoinventory.Scanner.start(Scanner.java:198)
at org.hyperic.hq.autoinventory.ScanManager.mainRunLoop(ScanManager.java:141)
at org.hyperic.hq.autoinventory.ScanManager.access$000(ScanManager.java:41)
at org.hyperic.hq.autoinventory.ScanManager$1.run(ScanManager.java:107)
Caused by: java.lang.NullPointerException
at org.hyperic.hq.plugin.extremescale.XSServerDetector$ObjectGridServer.validateServer(XSServerDetector.java:417)
at org.hyperic.hq.plugin.extremescale.XSServerDetector.detectObjectGridServers(XSServerDetector.java:86)
at org.hyperic.hq.plugin.extremescale.XSServerDetector.getServerResources(XSServerDetector.java:107)
... 5 more
Did anybody run through such problem before?

Re: Configuring Hyperic HQ 4.6.6 with stand alone WXS8.5

‏2012-10-23T20:47:55Z

This is the accepted answer.
This is the accepted answer.

The WXS Hyperic plug-in uses the hyperic AutoServerDetector, which looks for the catalog server by looking at the the command line arguments. It's looking for the following:
com.ibm.ws.objectgrid.server.impl.InitializationService <servername> -catalogServiceEndPoints <endpoints> -jmxServicePort <portnumber>

You need to use the startOgServer script with the -jmxServicePort argument. If you start the catalog server using any other method, it won't be able to automatically detect it.

Re: Configuring Hyperic HQ 4.6.6 with stand alone WXS8.5

The WXS Hyperic plug-in uses the hyperic AutoServerDetector, which looks for the catalog server by looking at the the command line arguments. It's looking for the following:
com.ibm.ws.objectgrid.server.impl.InitializationService <servername> -catalogServiceEndPoints <endpoints> -jmxServicePort <portnumber>

You need to use the startOgServer script with the -jmxServicePort argument. If you start the catalog server using any other method, it won't be able to automatically detect it.

Thanks for the quick reply Cris. I am using server.properties file to push all the necessary arguments and provide this properties file's reference while running the start command for catalog as well as container servers.

Is there a way I can still use hyperic to pull out the useful matrix. I guess this is the recommended way as per IBM documentations to start the server.

Re: Configuring Hyperic HQ 4.6.6 with stand alone WXS8.5

Thanks for the quick reply Cris. I am using server.properties file to push all the necessary arguments and provide this properties file's reference while running the start command for catalog as well as container servers.

Is there a way I can still use hyperic to pull out the useful matrix. I guess this is the recommended way as per IBM documentations to start the server.

The Hyperic plug-in is pretty small and simple, and was written to support startOgServer. It wouldn't take much for you to roll your own since it simply talks to our statistics MBeans via JMX. Hyperic has evolved quite a bit since this plug-in was written and there are probably better ways of detecting the catalog service now.

If you can, I'd suggest looking at ITM and ITCAM, which provide better integration options.

Re: Configuring Hyperic HQ 4.6.6 with stand alone WXS8.5

The WXS Hyperic plug-in uses the hyperic AutoServerDetector, which looks for the catalog server by looking at the the command line arguments. It's looking for the following:
com.ibm.ws.objectgrid.server.impl.InitializationService <servername> -catalogServiceEndPoints <endpoints> -jmxServicePort <portnumber>

You need to use the startOgServer script with the -jmxServicePort argument. If you start the catalog server using any other method, it won't be able to automatically detect it.

Thanks Chris. It did work now. Can you point me out in the direction where I need to modify the plugin to run it with only serverprops option and not jmxserviceport and catalogserviceEndpoints options?

It would also be good if you have some pointers on how to customize the existing plugin and related stuff.