2.1. Pre-requisites

2.2. JADE control through JMX

This package acts as a communication bridge between jadeboot and the JOnAS. Executing ant inside the folder where jade-jmx.zip was unzipped will start the package:

$ ant Buildfile: build.xml

jade-jmx:
[java] service:jmx:rmi:///jndi/rmi://127.0.1.1:9098/server
[java] RMI registry ready.

The RMI registry is started on the port 9098 by default.

This package can be executed in any node of the cluster. Its location is a decision of the cluster administrator. It's not mandatory to run it on a specific node.

[Note]Note

The package's location have to be specified in the UI config files, otherwise the UI will ask for it.

2.3. JADE Boot

The next step is to run the jade boot.

The JadeBoot can be configured through 2 properties files :

jadeboot.registry.host=localhost
jadeboot.registry.port=1238

jadeboot.discovery.host=localhost
jadeboot.discovery.port=9998

jadeboot.urls.deployable.file=file:./examples/j2ee/;file:./examples/j2ee/org.ow2.jasmine.jade.resource.j2ee-2.0.0.jar

jadeboot.jndi.port=1239
			
jonathan.connectionfactory.host=localhost

#http.proxyHost =
#http.proxyPort =
#http.proxyAuth = login:password
			

[Note]Note

It's recommended to write a completely qualified hostname (host.domain) or IP for *.host properties, instead of localhost.

To start the JADE boot from <jade-boot-home>/ :

$ sh jadeboot.sh

Welcome to Felix.
=================

JadeBoot starting ...
Fractal registry is started on port <jasmine-control-node-port>
[NodeDiscovery service] listen on port 9998
[NodeLauncher] Node "<jasmine-control-node-address>_0" registered
[Joram server] started
[NodeDiscovery service] started
[JNDI] connected to fr.dyade.aaa.jndi2.client.NamingContextFactory on <jasmine-control-node-address>:1239
[Allocator] started
[Deployer] started
[Registry cleaner] started
JadeBoot started
		

<jasmine-control-node-address> is the name of the machine and <jasmine-controle-node-port> is the port number where the Fractal registry will listen.

The next step is to run the jade nodes on every host part of the managed cluster.

2.4. JADE Node

All the nodes that will be monitored and managed need a JADE node package.

The JadeNode can be configured through 2 properties files :

jadeboot.registry.host=localhost
jadeboot.registry.port=1238

jadeboot.discovery.host=localhost
jadeboot.discovery.port=9998
			

To start the JADE node from <jade-node-home>/:

$ sh jadenode.sh

Welcome to Felix.
=================

JadeNode starting ...
Fractal Registry: <jasmine-control-node-address>:1238
[NodeLauncher] Node "<jasmine-monitored-node-address>_<node_id>" registered
[Heartbeat] started
JadeNode started
		

If the connection is successful, this message will be displayed in the jadeboot node console:

[Allocator] receive newNode jmsMessage : <jasmine-monitored-node-address>_<node-id>
		

2.4.1. User permissions & Apache

The administrator has to take care of the permissions of the user that is running the jadenode, because JADE may need to deploy Apache HTTPd and start it, the user will need some grants to launch it on a restricted port (<1024).

A simple solution is to give to the JADE user some admin rights. But a better solution is to use sudo for executing apachectl (the script that launches Apache HTTPd).

To do that it's necessary to edit /etc/sudoers file using the visudo command (we'll need root access) and add this line:

# User privilege specification <user-for-jadenode>
<jasmine-host-name> = (root)
NOPASSWD:<path-to-the-deployed-apachectl>
			
[Note]Note

This solution is just necessary if we need an Apache HTTPd server to listen at port 80 (or <1024). Otherwise the user will not need administrator rights and this part can be skipped.

Copyright © 2006-2007 JASMINe / ObjectWeb consortium
Creative Commons License
This work is licensed under a Creative Commons Attribution-Share Alike 3.0 License.

http://jasmine.objectweb.org