JRun SDK Guide
JRun Services

Loading MBeans through MLETs

JRun uses Java Management Extensions (JMX) to drive its service-based architecture. Additionally, JRun lets you use MLETs (abbreviation for management applets) to dynamically load JMX MBeans across a network using a remote URL. You define MLETs to JRun in the SERVER-INF/jrun.mlets file, which contain one or more MLET tags that define JMX MBeans, their locations, and attributes.

When the JRun server starts, it loads the JMX MBean. While MBeans loaded through MLETs are not JRun services, you can access the MBeans through a JMX management tool, such as the JMX HTML Adapter, which is defined through the HTMLAgent service in the jrun.xml file.

The following example shows an MLET tag in the jrun.mlets file:

...

<!--
��������This file is used to add third-party JMX MBeans
        to the JRun server. If you have an existing JMX
        library or component that you wish to load into
        JRun, add your existing MLET entries to this file.

        Your MBeans can be loaded across the network; if
        this is the desired behavior, be sure to include
        the CODEBASE attribute in your MLet entry.

        Your MBeans will be loaded and added to the JRun
        MBeanServer immediately after all JRun services
        are loaded, initialized, and started.
-->

<!-- Example MLet -->
<MLET
  CODE="jrun.samples.services.SampleMletService" 
  ARCHIVE="jrunsamples.jar"
  CODEBASE="./lib/"
  NAME=":mbean=SampleMletService"
>
    <attribute name="string">Hello World</attribute>
    <attribute name="woStringValue">foobar</attribute>
</MLET>

For more information on the JMX HTMLAgent service, see JRun Administrator's Guide. For more information on JMX, see the Sun website.

Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/jrun/4/JRun_SDK_Guide/creatingservices6.htm

Add Comment