Author: mriou
Date: Tue May 1 14:43:21 2007
New Revision: 534249
URL: http://svn.apache.org/viewvc?view=rev&rev=534249
Log:
Instructions for JBI deployment
Modified:
incubator/ode/trunk/BUILDING
incubator/ode/trunk/RELEASE_NOTES
Modified: incubator/ode/trunk/BUILDING
URL:
http://svn.apache.org/viewvc/incubator/ode/trunk/BUILDING?view=diff&rev=534249&r1=534248&r2=534249
==============================================================================
--- incubator/ode/trunk/BUILDING (original)
+++ incubator/ode/trunk/BUILDING Tue May 1 14:43:21 2007
@@ -49,15 +49,15 @@
It just works! For more information about buildr see
http://buildr.rubyforge.org/.
-Running in Tomcat
------------------
+Running in Tomcat (WAR deployment)
+----------------------------------
-You should find the full distribution in the distro-axis/target directory.
Unzip it somewhere on your disk, everything needed is inside.
+You should find the full distribution in the distro-axis2/target directory.
Unzip it somewhere on your disk, everything needed is inside.
-Get the WAR file in the distribution root directory, rename it to *ode.war*
and copy this file to Tomcat's webapp directory. You should get a blank page
under http://localhost:8080/ode. The Ode WAR includes its own embedded database
(Derby - http://db.apache.org/derby) so you don't have to worry about
configuring any external database for now.
+Get the WAR file in the distribution root directory (should be named
apache-ode-war-x.x.zip), rename it to *ode.war* and copy this file to Tomcat's
webapp directory. You should get a blank page under http://localhost:8080/ode.
The Ode WAR includes its own embedded database (Derby -
http://db.apache.org/derby) so you don't have to worry about configuring any
external database for now.
-Testing
--------
+Testing a Tomcat Deployment
+---------------------------
Copy the content of examples directory in the distribution (the 3
sub-directories) to _tomcat/webapps/ode/WEB-INF/processes_, this will
automatically deploy the 3 example processes. Use the sendsoap command located
in the distribution _bin_ directory to send test messages. The messages to run
each of the 3 examples are provided in their respective directory
(testRequest.soap). For each example type:
@@ -69,4 +69,24 @@
The URLs should be updated according to the address defined in the WSDL file
for the process service.
-If you want to use an IDE to explore the PXE sources or debug PXE executables,
Eclipse .project and .classpath files are present in all the modules; simply
choose File|Import from the Eclipse menu, and select the root ODE directory.
You may also use Maven to generate project files for other IDEs. See the Maven
documentation for details.
\ No newline at end of file
+If you want to use an IDE to explore the PXE sources or debug PXE executables,
Eclipse .project and .classpath files are present in all the modules; simply
choose File|Import from the Eclipse menu, and select the root ODE directory.
You may also use Maven to generate project files for other IDEs. See the Maven
documentation for details.
+
+Running in ServiceMix (JBI deployment)
+--------------------------------------
+
+You should find the full distribution in the distro-jbi/target directory.
Unzip it somewhere on your disk, everything needed is inside.
+
+Get the zip containing ODE's service engine in the distribution root directory
(should be named apache-ode-jbi-x.x.zip) and copy it in the install directory
of ServiceMix 3.1. Most process deployments will also require HTTP binding so
you should also copy the servicemix-shared and servicemix-http zip files from
its components directory to its install directory. Start ServiceMix by going
into its root directory and type:
+
+bin/servicemix
+
+The server should start properly.
+
+Testing a ServiceMix Deployment
+-------------------------------
+
+JBI examples come with ant scripts to build the service assemblies and test
them. It's just a 3 step process:
+
+1. Go to the example directory and run ant (no need to specify a task, the
default one will work).
+2. Copy the zip service assembly created in the build subdirectory to the
deploy directory of ServiceMix.
+3. Run 'ant test' from the example directory.
\ No newline at end of file
Modified: incubator/ode/trunk/RELEASE_NOTES
URL:
http://svn.apache.org/viewvc/incubator/ode/trunk/RELEASE_NOTES?view=diff&rev=534249&r1=534248&r2=534249
==============================================================================
--- incubator/ode/trunk/RELEASE_NOTES (original)
+++ incubator/ode/trunk/RELEASE_NOTES Tue May 1 14:43:21 2007
@@ -9,7 +9,10 @@
build. So these first release notes are going to be closer to a
features list.
-Apache ODE 1.0 requires Java 1.5.x.
+Apache ODE 1.0 requires Java 1.5.x. The WAR distribution can run in
+most J2EE servlet container. The JBI distribution should be able to
+run in any JBI container but has only been tested with ServiceMix
+3.1 so far.
Apache ODE is a WS-BPEL compliant web services orchestration engine.
It organizes web services calls following a process description
