Main.Documentation
E2EMngmt-Jasmine
en
0
Main.Documentation.E2EMngmt
xwiki:XWiki.donsez
xwiki:XWiki.calmant
xwiki:XWiki.calmant
1280321001000
1283551886000
1283551886000
1.8
Aspire :: End-to-end management :: Jasmine
1 Aspire :: End-to-end management :: Jasmine
----
#toc("" "" "true")
----
This section describes the usage of OW2 Jasmine to manage autonomically the components of the Aspire middleware.
1.1 Context
[OW2 Jasmine>http://jasmine.ow2.org] enables the autonomic management of distributed infrastructure of machines executed the Aspire components (ALE, BEG, EPCIS, ...).
OW2 Jasmine elements are:
* [MBeanCmd>http://jasmine.ow2.org/doc/docbkx/mbeancmd-user-guide/2.2.1-SNAPSHOT/html/mbeancmd_guide.html]
** [command stat>http://jasmine.ow2.org/doc/docbkx/mbeancmd-user-guide/2.2.1-SNAPSHOT/html/mbeancmd_guide.html#mbeancmd.stat]
* [Drools rules for notification>http://jasmine.ow2.org/doc/docbkx/jasmine-monitoring-user-guide/1.2.3-SNAPSHOT/html/jasmine-monitoring_guide.html#monitoring.notification]
1.1 Usecases
1.1.1 Static topology
1.1.1.1 Bootstrap
* µJOnAS : provides utility MBeans (send a file to the server, ...)
* Jasmine Agent
1.1.1.1 Artifact repository
1.1.1.1 Configuration repository
In order to ease the deployment and to have a homogeneous platform, all configuration files (ECSpec, LRSpec, ...) may be available on a specific repository, common for all servers.
1.1.1 Machine wakeup
The code from the [GreenIT demo>http://ecom.ow2.org/xwiki/bin/view/Main/engreenit] for machines wake up is based on the WakeOnLAN standard.
This standard can't cross routers, and may have to be used in internal networks.
Also, the ALE server may be automatically started when the system is up (Unix daemon, Windows service...), or started via a JASMINe Agent.
1.1.1 Initial provisioning
Different ways has been discussed for the initial provisioning :
* via [deployment plans>http://jonas.ow2.org/JONAS_5_1_0/doc/doc-en/html/deployment-plans_guide.html]
* by sending bundles JAR files to the server (via its sendFile() capable MBean), then load it with a FileInstall bundle, or via the AdminMBean
* by using PaxRunner or Tomcat
1.1.1 Provisioning update
* There is no information about updating a deployment plan.
* Sending an updated file, and use it with FileInstall or AdminMBean may not be difficult
1.1.1 Configuration provisioning and recovery
When the µJOnAS is started, it provides some utility MBeans.
One of them allows to send a binary file to the server (via a bytes array).
This way, when JASMINe is able to recognize that a new server is up, a drools rule can provide base ECSpec and LRSpecs XML files.
1.1.1 Metrics collection and alarms
All data may be collected throught JMX MBeans.
Some metrics are purely informative (uptime...), but other ones may be used in order to control the server state (number of generated reports, event cycles...).
By using the '-rate' option of the JASMINe *stat* command and a threshold, a drools rule is able to test the ale server activity, and notify the administrator, via JASMINe notifications, if the server runs to slow or to fast.
1.1 Hints
1.1.1 Server start-up
The server may be started by using an agent able to launch Pax Runner with a specified configuration file provided through an MBean method call.
1.1.1 Server configuration
By using MBeanCmd, JASMINe events can be used to detect new servers, and send them their specific configuration via MBeans.
A sample rule has been developed to demonstrate this mechanism :
* JASMINe polls periodically an ALE server MBean attribute : the uptime
* When the server is down, no event are triggered
* When the server is up, a rule handles the event, and sends a server-specific configuration (Logical readers, ECSpecs, subscriptions) via ALE server MBeans.
*TODO* attach the demonstration files
1.1.1 Access MBeans through the network
MBeans can be accessed directly on a local machine, but a little trick allows a remote access : in the ALE server command line, the JMX remote options must be defined.
Example :
{code}
$ java \
-Dcom.sun.management.jmxremote.port=8088 # Listening port
-Dcom.sun.management.jmxremote.authenticate=false # no authentication
-Dcom.sun.management.jmxremote.ssl=false # No SSL connexion
-Dfelix.config.properties=file:felix/config.ini
-jar bundles/org.apache.felix.main_2.0.2.jar
{code}
This way, the ALE server can be accessed by MBeanCmd in JASMINe, by using the corresponding JNDI target address :
{code}
service:jmx:rmi://ale_server_address/jndi/rmi://ale_server_address:1111/jmxrmi
{code}
1.1.1 MBean value polling with MBeanCmd
MBeanCmd and its command stat allows to retrieve periodically informations about the current server state.
Each time a requested attribute has been read, a JasmineEventEB event is raised, and can be handled in a Drool script.
Example : Retrieve the server uptime everey 5 seconds
{code}
$ stat \
-p 5 # Poll delay
-name "org.ow2.aspirerfid:type=aleserver,name=server" # Source MBean
-a Uptime # MBean attribute to read
-target service:jmx:rmi://localhost/jndi/rmi://localhost:1111/jmxrmi
-jasmine vm://MBeanCmd_dispatcher # Event handler (JASMINe)
{code}
1.1 Links
<h2 class="heading-1"><span id="HAspire3A3AEndtoendmanagement3A3AJasmine">Aspire :: End-to-end management :: Jasmine</span></h2>
<hr class="line"/>
<ul>
<li><a href="#HContext">1 Context</a>
<li><a href="#HUsecases">2 Usecases</a>
<ul>
<li><a href="#HStatictopology">2.1 Static topology</a>
<ul>
<li><a href="#HBootstrap">2.1.1 Bootstrap</a>
<li><a href="#HArtifactrepository">2.1.2 Artifact repository</a>
<li><a href="#HConfigurationrepository">2.1.3 Configuration repository</a>
</ul>
<li><a href="#HMachinewakeup">2.2 Machine wakeup</a>
<li><a href="#HInitialprovisioning">2.3 Initial provisioning</a>
<li><a href="#HProvisioningupdate">2.4 Provisioning update</a>
<li><a href="#HConfigurationprovisioningandrecovery">2.5 Configuration provisioning and recovery</a>
<li><a href="#HMetricscollectionandalarms">2.6 Metrics collection and alarms</a>
</ul>
<li><a href="#HHints">3 Hints</a>
<ul>
<li><a href="#HServerstartup">3.1 Server start-up</a>
<li><a href="#HServerconfiguration">3.2 Server configuration</a>
<li><a href="#HAccessMBeansthroughthenetwork">3.3 Access MBeans through the network</a>
<li><a href="#HMBeanvaluepollingwithMBeanCmd">3.4 MBean value polling with MBeanCmd</a>
</ul>
<li><a href="#HLinks">4 Links</a>
</ul> <hr class="line"/><p class="paragraph"/>This section describes the usage of OW2 Jasmine to manage autonomically the components of the Aspire middleware.
<h3 class="heading-1-1"><span id="HContext">Context</span></h3>
<span class="wikiexternallink"><a href="http://jasmine.ow2.org">OW2 Jasmine</a></span> enables the autonomic management of distributed infrastructure of machines executed the Aspire components (ALE, BEG, EPCIS, ...).<p class="paragraph"/>OW2 Jasmine elements are:
<ul class="star">
<li><span class="wikiexternallink"><a href="http://jasmine.ow2.org/doc/docbkx/mbeancmd-user-guide/2.2.1-SNAPSHOT/html/mbeancmd_guide.html">MBeanCmd</a></span><ul class="star">
<li><span class="wikiexternallink"><a href="http://jasmine.ow2.org/doc/docbkx/mbeancmd-user-guide/2.2.1-SNAPSHOT/html/mbeancmd_guide.html#mbeancmd.stat">command stat</a></span></li>
</ul>
</li>
<li><span class="wikiexternallink"><a href="http://jasmine.ow2.org/doc/docbkx/jasmine-monitoring-user-guide/1.2.3-SNAPSHOT/html/jasmine-monitoring_guide.html#monitoring.notification">Drools rules for notification</a></span></li>
</ul><h3 class="heading-1-1"><span id="HUsecases">Usecases</span></h3>
<h4 class="heading-1-1-1"><span id="HStatictopology">Static topology</span></h4>
<h5 class="heading-1-1-1-1"><span id="HBootstrap">Bootstrap</span></h5>
<ul class="star">
<li>µJOnAS : provides utility MBeans (send a file to the server, ...)</li>
<li>Jasmine Agent</li>
</ul><h5 class="heading-1-1-1-1"><span id="HArtifactrepository">Artifact repository</span></h5>
<h5 class="heading-1-1-1-1"><span id="HConfigurationrepository">Configuration repository</span></h5><p class="paragraph"/>In order to ease the deployment and to have a homogeneous platform, all configuration files (ECSpec, LRSpec, ...) may be available on a specific repository, common for all servers.
<h4 class="heading-1-1-1"><span id="HMachinewakeup">Machine wakeup</span></h4><p class="paragraph"/>The code from the <span class="wikiexternallink"><a href="http://ecom.ow2.org/xwiki/bin/view/Main/engreenit">GreenIT demo</a></span> for machines wake up is based on the WakeOnLAN standard.<p class="paragraph"/>This standard can't cross routers, and may have to be used in internal networks.<p class="paragraph"/>Also, the ALE server may be automatically started when the system is up (Unix daemon, Windows service...), or started via a JASMINe Agent.
<h4 class="heading-1-1-1"><span id="HInitialprovisioning">Initial provisioning</span></h4><p class="paragraph"/>Different ways has been discussed for the initial provisioning :
<ul class="star">
<li>via <span class="wikiexternallink"><a href="http://jonas.ow2.org/JONAS_5_1_0/doc/doc-en/html/deployment-plans_guide.html">deployment plans</a></span></li>
<li>by sending bundles JAR files to the server (via its sendFile() capable MBean), then load it with a FileInstall bundle, or via the AdminMBean</li>
<li>by using PaxRunner or Tomcat</li>
</ul><h4 class="heading-1-1-1"><span id="HProvisioningupdate">Provisioning update</span></h4>
<ul class="star">
<li>There is no information about updating a deployment plan.</li>
<li>Sending an updated file, and use it with FileInstall or AdminMBean may not be difficult</li>
</ul><h4 class="heading-1-1-1"><span id="HConfigurationprovisioningandrecovery">Configuration provisioning and recovery</span></h4><p class="paragraph"/>When the µJOnAS is started, it provides some utility MBeans.
One of them allows to send a binary file to the server (via a bytes array).<p class="paragraph"/>This way, when JASMINe is able to recognize that a new server is up, a drools rule can provide base ECSpec and LRSpecs XML files.
<h4 class="heading-1-1-1"><span id="HMetricscollectionandalarms">Metrics collection and alarms</span></h4><p class="paragraph"/>All data may be collected throught JMX MBeans.<p class="paragraph"/>Some metrics are purely informative (uptime...), but other ones may be used in order to control the server state (number of generated reports, event cycles...).<p class="paragraph"/>By using the '-rate' option of the JASMINe <strong class="strong">stat</strong> command and a threshold, a drools rule is able to test the ale server activity, and notify the administrator, via JASMINe notifications, if the server runs to slow or to fast.
<h3 class="heading-1-1"><span id="HHints">Hints</span></h3>
<h4 class="heading-1-1-1"><span id="HServerstartup">Server start-up</span></h4><p class="paragraph"/>The server may be started by using an agent able to launch Pax Runner with a specified configuration file provided through an MBean method call.
<h4 class="heading-1-1-1"><span id="HServerconfiguration">Server configuration</span></h4><p class="paragraph"/>By using MBeanCmd, JASMINe events can be used to detect new servers, and send them their specific configuration via MBeans.<p class="paragraph"/>A sample rule has been developed to demonstrate this mechanism :
<ul class="star">
<li>JASMINe polls periodically an ALE server MBean attribute : the uptime</li>
<li>When the server is down, no event are triggered</li>
<li>When the server is up, a rule handles the event, and sends a server-specific configuration (Logical readers, ECSpecs, subscriptions) via ALE server MBeans.</li>
</ul><strong class="strong">TODO</strong> attach the demonstration files
<h4 class="heading-1-1-1"><span id="HAccessMBeansthroughthenetwork">Access MBeans through the network</span></h4><p class="paragraph"/>MBeans can be accessed directly on a local machine, but a little trick allows a remote access : in the ALE server command line, the JMX remote options must be defined.<p class="paragraph"/>Example :
<div class="code"><pre>$ java
-Dcom.sun.management.jmxremote.port=8088 # Listening port
-Dcom.sun.management.jmxremote.authenticate=<span class="java-keyword">false</span> # no authentication
-Dcom.sun.management.jmxremote.ssl=<span class="java-keyword">false</span> # No SSL connexion
-Dfelix.config.properties=file:felix/config.ini
-jar bundles/org.apache.felix.main_2.0.2.jar</pre></div><p class="paragraph"/>This way, the ALE server can be accessed by MBeanCmd in JASMINe, by using the corresponding JNDI target address :<p class="paragraph"/><div class="code"><pre>service:jmx:rmi://ale_server_address/jndi/rmi://ale_server_address:1111/jmxrmi</pre></div>
<h4 class="heading-1-1-1"><span id="HMBeanvaluepollingwithMBeanCmd">MBean value polling with MBeanCmd</span></h4><p class="paragraph"/>MBeanCmd and its command stat allows to retrieve periodically informations about the current server state.<p class="paragraph"/>Each time a requested attribute has been read, a JasmineEventEB event is raised, and can be handled in a Drool script.<p class="paragraph"/>Example : Retrieve the server uptime everey 5 seconds<p class="paragraph"/><div class="code"><pre>$ stat
-p 5 # Poll delay
-name <span class="java-quote">"org.ow2.aspirerfid:type=aleserver,name=server"</span> # Source MBean
-a Uptime # MBean attribute to read
-target service:jmx:rmi://localhost/jndi/rmi://localhost:1111/jmxrmi
-jasmine vm://MBeanCmd_dispatcher # Event handler (JASMINe)</pre></div>
<h3 class="heading-1-1"><span id="HLinks">Links</span></h3><p class="paragraph"/><p class="paragraph"/>