-
1. Re: IronJacamar RHQ plugin
jesper.pedersen Jan 4, 2011 9:37 AM (in response to yang.yong)1) we can NOT saw any setter methods in those classes, so how to change the configuration?
Take a look at AbstractFungalRADeployer::registerManagementView(). This is the method that converts the management model to JMX MBeans for the standalone distribution. And look at the usage of that method.
You need to make a method like that for RHQ setup in the deployers for AS 7 (org.jboss.as.connector.deployers). However, the RHQ method should use the management model directly, like:
JOPR -> RHQ -> IronJacamar Management Model -> Resource Adapter -> * JOPR -> RHQ -> IronJacamar Management API -> Metrics / Statistics
We have enough for the first part - the second part we need to create.
2) class ManagementRepository is a singleton class, we can access it directly in embedded environment, but will ManagementRepository/Connector/ConnectionFactory/AdminObject be registered to org.jboss.deployers.spi.management.ManagementView? so them can be accessed by ManagementView like hornetq plugin.
Yes, all deployments in the IronJacamar container should be registered with the ManagementRepository singleton. The IronJacamar management model is independant of the technology used, like JMX or RHQ.
However, there is no o.j.d.s.m.ManagementView in AS 7 - at least not yet. Maybe Emanuel or Heiko can comment on that.
If IronJacamar has embedded in current AS7 release? if not, how can we test IronJacamar plugin?
IronJacamar is included in AS 7.0.0.Alpha1 - however, RHQ isn't integrated yet - Heiko is working on that. There are two options:
- Create the RHQ plugin in the AS 7 distribution (org.jboss.as.connector.rhq) and work together with Heiko on the integration of platform itself
- Add support for RHQ in the IronJacamar standalone distribution incl. web ui - and create a new module (rhq) with the code
I think 1) would be the easiest for now.
-
2. Re: IronJacamar RHQ plugin
jesper.pedersen Jan 4, 2011 9:45 AM (in response to jesper.pedersen)See the email thread: http://lists.jboss.org/pipermail/jboss-as7-dev/2010-December/000150.html
-
-
4. IronJacamar RHQ plugin
gaol Jan 17, 2011 7:47 AM (in response to jesper.pedersen)Hi, Jepser:
Thanks for the information.
Some questions:
Yes, all deployments in the IronJacamar container should be registered with the ManagementRepository singleton. The IronJacamar management model is independant of the technology used, like JMX or RHQ.
1. The method of ManagementRepository.getInstance() is not declared as static, it should be, right?
2. Has the ManagementRepository been used already to register deployments when deploying some resources?
3. RHQ is Server/Agent architecture, which means it is possible that the agent plugin will work in another JVM than the jca container one. Shall the IronJacamar RHQ plugin work only in the embedded jopr environment which does not require remote access or work in the RHQ HA environment also which will require remote access to the jca deployments?
-
5. IronJacamar RHQ plugin
gaol Jan 17, 2011 8:07 AM (in response to jesper.pedersen)Add support for RHQ in the IronJacamar standalone distribution incl. web ui - and create a new module (rhq) with the code
Since RHQ plugin execution requires the RHQ plugin container, the support for RHQ in IronJacamar sjc can be done by deploying the embedded jopr(admin-console.war) in the IronJacamar sjc jetty. Yang Yong and I spent some days working on deploying the admin-console.war to jetty, but failed. The embedded jopr(admin-console.war) should be made more independent to be able to be deployed to any web container easily.
-
6. Re: IronJacamar RHQ plugin
jesper.pedersen Jan 17, 2011 2:43 PM (in response to gaol)1. The method of ManagementRepository.getInstance() is not declared as static, it should be, right?
Ok, that class was wrong - see JBJCA-492 - the first couple of fixes have been committed.
There is one ManagementRepository per JCA container, so the class isn't static but must be injected into the code that needs it - or there must be a service that keeps a reference to it. Same idea as the MetadataRepository class.
2. Has the ManagementRepository been used already to register deployments when deploying some resources?
That part was missing for the standalone/embedded. It has been fixed as part of JBJCA-492.
3. RHQ is Server/Agent architecture, which means it is possible that the agent plugin will work in another JVM than the jca container one. Shall the IronJacamar RHQ plugin work only in the embedded jopr environment which does not require remote access or work in the RHQ HA environment also which will require remote access to the jca deployments?
Lets start with EMBJOPR and go from there.
-
7. Re: IronJacamar RHQ plugin
jesper.pedersen Jan 17, 2011 2:45 PM (in response to gaol)Agreed. You can raise that issue with the JOPR team.
There will be a RHQ platform in AS 7, so it is probably the easiest to deploy the plugin to that environment first. But I'll take a look at deployment of the console in standalone - maybe we will have some additional information after the console meeting this week.