When I try to start the 4.0.3 agent on our linux Websphere 6.1 server it fails to start. I can start the agent and see it from the server if I point it to a different jvm, but then the websphere monitoring piece doesn't work.
Any details on the correct configuration of the agent with Websphere 6.1 would be greatly appreciated.
Checked all that but as I am running against a WAS that is Windows based the /opt doesn't work. Moreover, there is a problem with setting the HQ_JAVA_HOME variable in that environment. That's needed to get the correct IBM Java, but it does not really work and I have my doubts about the remaining parts of the installation, even though the windows agent manages to connect.
Plugin error: plugin class not found: com.ibm.websphere.management.exception.connectorexception (invalid classpath or corrupt plugin.jar)
It doesn't at this point, tell me what the path was that it tried. The plugin is apparently in the pdk/plugins directory where it is expected to be.
Sorry you had trouble BJ. Just to confirm, setting HQ_JAVA_HOME on Windows should solve the problem. I'll update the config instructions to include instructions for how to do this on Windows. Hope things are going better for you now.
That's OK.. it worked the way I did it and I expect trouble with IBM cause there's multiple Java installations there and you have to use the one that WAS uses. I expect LESS trouble on the AIX boxes because they have a clearer definition of which Java to use and fewer java's. The next problem from that is that the path to the IBM plugins directory isn't correct. This causes exceptions... working out what jars are required with a home-rolled ws-admin client per IBM's instructions. I do want it, but I have found yet another possible method of getting at it.
IBM is starting to offer a servlet to install on WAS that provides perf. data. I suggested something like it over a year ago... somebody must have listened... just a little http servlet. I am not privy to details yet but I ought to be able to script a lynx connection from anywhere and filter the results. How that'd fit into Hyperic I am not sure... have to look at the other customizations.
One other note... if you have installed security on your WAS and most people will do that eventually, you have to enable security for your perf monitoring. Using a borrowed WAS I didn't know about it when I started.
I expect to have this sorted in another day or so.
Then I have to sort HermesJMS to actually manipulate the internal JMS queues.
OK... as nearly as I can make out, the entry for "was.install.root" in the console page is having trouble with the spaces in the directory path that Windows provides. I am sure there is a special place in hell reserved for the people who thought up the Microsoft brainstorm of putting spaces in the filenames.
If I could force it into the agent configuration that'd be good. I am looking at how to provide the jar it needs but with the security required as well I may be stymied until I work out where this path is for real.
In Windows you need to set the HQ_JAVA_HOME environment BEFORE you hit the hq-agent.bat install step Setting it before you start the agent is nice but doesn't get the windows clean. AFAIK, there is still trouble. I don't know because I finally adopted belt & suspenders approach and copied the entire contents of the websphere plugins directory into my lib directory. added the runtime/cllient jar (not the thinclient) and the bootstrap.jar and with the PMI enabled and security disabled on websphere it connects and offers up stats on the JDBC and the rest.... 28 of about 280 enabled metrics for the Websphere server are available.
Connecting to the MBean server is however, still giving trouble.
After all, it is IBM Java... not Sun. Not threaded either.