Date: 2004-03-04T10:29:10
Editor: 151.200.234.250 <>
Wiki: Apache James Wiki
Page: James/Embedded
URL: http://wiki.apache.org/james/James/Embedded
no comment
Change Log:
------------------------------------------------------------------------------
@@ -2,7 +2,11 @@
This page describes what you need to do in order to get James to run inside
the JBoss application server. Unfortunately this is a pretty ugly process,
there are two reasons for this. Firstly the JMXLauncher files have not been
tagged with the Phoenix release tags so you need to get the trunk revisions
from the CVS repository. Secondly James does not work with the trunk revision
of Phoenix because of changes to the lifecycle methods in the underlying Avalon
framework and components. The latest revision of Phoenix that James will work
with is version 4.0.3.
----- Get and Build Phoenix
+'''NOTE: There are two ways to do it: using the source and building it, or
just using binaries with the .jar attached to this page. See the binary way
below.'''
+
+== Source Way ==
+
+=== Get and Build Phoenix ===
* Checkout Phoenix version 4.0.3 into a clean directory, the CVS tag for
this is Phoenix_4_0_3 and I'll refer to this directory as <phoenix_4_0_3>.
@@ -10,6 +14,9 @@
* Copy the following files from <phoenix_head> to <phoenix_4_0_3>
+{{{
avalon-phoenix/src/java/org/apache/avalon/phoenix/components/manager/AbstractJMXManager.java
}}}
+{{{
avalon-phoenix/src/java/org/apache/avalon/phoenix/components/manager/AbstractSystemManager.java
}}}
+''3/4/2004--added the above two files. Apparently CVS is diverging more and
more''
{{{
avalon-phoenix/src/java/org/apache/avalon/phoenix/components/manager/HostedSystemManager.java
}}}
{{{
avalon-phoenix/src/java/org/apache/avalon/phoenix/launcher/FreeNEasyPolicy.java
}}}
{{{
avalon-phoenix/src/java/org/apache/avalon/phoenix/launcher/JMXLauncher.java }}}
@@ -22,7 +29,7 @@
* Build <phoenix_4_0_3>
----- Install Phoenix in JBoss
+=== Install Phoenix in JBoss ===
* Copy phoenix distribution to Jboss directory:
@@ -48,5 +55,29 @@
* Run JBoss
+== Binary Way ==
+
+I did this with JBoss 3.2.3, James 2.1.3 and Phoenix CVS sources for
`JMXLauncher.jar` as of 3/4/2004. Note that `JMXLauncher.jar` is put in two
places because it contains both `JMXLauncher` and the `HostedSystemManager` in
one jar--technically, they are conceptually different and could be separated,
but one jar made it easier.
+
+ * Download James binary distribution and install it in %JAMES_HOME% (ie.
wherever you like). If you use james-2.1.3 and put it in %JBOSS_HOME%, the
attached phoenix-service.xml should work as is.
+
+ * Download attachment:JMXLauncher.jar and install it in the james phoenix
launcher directory:
+
+{{{ copy attachment:JMXLauncher.jar %JAMES_HOME%/bin/lib }}}
+ * Copy phoenix-loader.jar, attachment:phoenix-service.xml, and
attachment:JMXLauncher.jar to Jboss deployment dir (using Jboss 'default'
server as example):
+{{{ copy %JAMES_HOME%\bin\phoenix-loader.jar
%JBOSS_HOME%\server\default\deploy }}}[[BR]]
+{{{ copy phoenix-service.xml %JBOSS_HOME%\server\default\deploy }}}[[BR]]
+{{{ copy JMXLauncher.jar %JBOSS_HOME%/server/default/deploy }}}
+
+ * Edit the phoenix kernel configuration file,
%JBOSS_HOME%\phoenix\conf\kernel.xml, to use the hosted JMX system manager:
+
+{{{
+<component role="org.apache.avalon.phoenix.interfaces.SystemManager"
+
class="org.apache.avalon.phoenix.components.manager.HostedSystemManager"
+ logger="manager">
+</component>
+}}}
+
+ * Run JBoss
