Hi Subbu, I have recently commited some changes to the JMX facility that upgrades it to use the latest MX4J release. Unfortunately, I still haven't got around to writing any end user documentation on it.
Here are some steps that should get you up and running, and likely the beginnings of the JMX facility user documentation ;-). I'll start right from scratch as I'm not sure if you are looking at the subversion version or not: -= Checkin out the source, building, and setting up Merlin =- First, check out the latest source: $ svn co http://svn.apache.org/repos/asf/avalon/trunk avalon $ cd avalon Now, initialize the magic buildsystem (this only has to be done once): $ ant setup Now, build the various components of merlin and it's facilities: $ ant This build will have created a Merlin distribution, you can unzip it to install it. This is also a one time step. Note that the zip resides in your local magic repository, a .magic directory in your user home directory. On unix, check your $HOME directory, in Windows, check C:\Documents and Settings\<your user name> for that directory. unzip the zip file to the location you want to install merlin, and set the environment variables MERLIN_HOME (pointing to the merlin directory you just unzipped) and add $MERLIN_HOME/bin to your path. The full path to the zip file is $HOME/.magic/main/avalon/merlin/dist/avalon-merlin-cli-SNAPSHOT.zip. -= Launching the JMX Facility example =- Now that it's all built and you have merlin installed, you can play with the JMX facility: $ cd planet/facilities/jmx The following command will run the test block, which establishes the JMX facility, and a single test component that exposes a management API: $ merlin -repository $HOME/.magic/main test/target/deliverables/blocks/avalon-jmx-test.block You should see a couple info messages printed on the console indicating the facility has started, and started HTTP and RMI adaptors to the MBean server. You can now access the JMX console at http://127.0.0.1:8082. If you click on the MBean: Merlin:container=jmx,name=test,topic=JMXTestComponentMBean it will bring up the management interface of the test component. Management interfaces for a component are currently only determined by inspecting the component's implemented interfaces for interfaces with names ending with "MBean". For each "MBean" interface found, an MBean is created and registered with the MBeanServer by the JMX facility. An example of this is the JMXTestComponent located in the test directory. I hope this helps, and I hope to have some more formalized documentation as well as some facility enhancements available in the near future. Let me know if you run into any problems. Regards, -Cameron On Wed, 2004-09-08 at 14:32, S V Subramonian wrote: > Hi Peter, > > I would appreciate if you can let me know the JMX > facility that you got. Also please send me if there is > any to do list document or guide for incorporating JMX > in Merlin. > > regards, > Subbu > --- [EMAIL PROTECTED] wrote: > > > Hi Subbu, > > we have the JMX facility running here, so I could > > take a look at the demo > > next week if no one else has time. > > > > /peter > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > __________________________________ > Do you Yahoo!? > Read only the mail you want - Yahoo! Mail SpamGuard. > http://promotions.yahoo.com/new_mail > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
