Hi!
Thanks for this plugin, it is really helpful to us, we are trying to use Jboss Operations Network to monitor WAS 8.5.5. The plugin works but there are some minor issues:
Autodiscovery: It seems we've run into the problem with too long java command lines, meaning the plugin is unable to detect running WAS instances, so they have to be added manually. It would be great if the plugin could use some other method to discover WAS servers apart from the cmdline.
SSL Trust:Is it really necessary to have 'strict' SSL trust in the client (agent)? For JBoss EAP for instance, the agent trusts any certificate when Jboss management is over SSL. I understand there might be limitations in the IBM API since the plugin uses IBM code I assume.
SSL Truststore location: The default location of the RHQ agent truststore is /conf/truststore.dat. This file is referenced in the default prefs.xml. If this was used then it would be a lot easier to add certificates that are needed. Of course, this file could have a password, so the plugin would need to support opening jks-files with passwords.
I solved the above with symlinking data/WebSphere/trust.jks to truststore.dat but it's not a very elegant solution.
I would love to help out any way I can with this, I have downloaded the code but I am not a Java developer and not very familiar with the RHQ APIs.
Hi! Thanks for this plugin, it is really helpful to us, we are trying to use Jboss Operations Network to monitor WAS 8.5.5. The plugin works but there are some minor issues:
Autodiscovery: It seems we've run into the problem with too long java command lines, meaning the plugin is unable to detect running WAS instances, so they have to be added manually. It would be great if the plugin could use some other method to discover WAS servers apart from the cmdline.
SSL Trust:Is it really necessary to have 'strict' SSL trust in the client (agent)? For JBoss EAP for instance, the agent trusts any certificate when Jboss management is over SSL. I understand there might be limitations in the IBM API since the plugin uses IBM code I assume.
SSL Truststore location: The default location of the RHQ agent truststore is/conf/truststore.dat. This file is referenced in the default prefs.xml. If this was used then it would be a lot easier to add certificates that are needed. Of course, this file could have a password, so the plugin would need to support opening jks-files with passwords.
I solved the above with symlinking data/WebSphere/trust.jks to truststore.dat but it's not a very elegant solution.
I would love to help out any way I can with this, I have downloaded the code but I am not a Java developer and not very familiar with the RHQ APIs.
regards, Stian Lund