Author: buildbot
Date: Mon Dec 10 21:36:05 2012
New Revision: 841544
Log:
Staging update by buildbot for ode
Modified:
websites/staging/ode/trunk/content/ (props changed)
websites/staging/ode/trunk/content/jbi-deployment.html
websites/staging/ode/trunk/content/smx4-osgi-deployment.html
websites/staging/ode/trunk/content/user-guide.html
websites/staging/ode/trunk/content/war-deployment.html
Propchange: websites/staging/ode/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec 10 21:36:05 2012
@@ -1 +1 @@
-1419786
+1419798
Modified: websites/staging/ode/trunk/content/jbi-deployment.html
==============================================================================
--- websites/staging/ode/trunk/content/jbi-deployment.html (original)
+++ websites/staging/ode/trunk/content/jbi-deployment.html Mon Dec 10 21:36:05
2012
@@ -81,21 +81,22 @@
<div class="row">
<div class="span12">
- <p>Here's a quick overview to deploy PXE/ODE on a JBI container
(e.g. <a href="http://servicemix.apache.org";>ServiceMix</a>)</p>
+ <h2 id="overview">Overview</h2>
+<p>Here's a quick overview to deploy PXE/ODE on a JBI container (e.g. <a
href="http://servicemix.apache.org";>ServiceMix</a>)</p>
<p><a name="JBIDeployment-1)DownloadtheJBIdistribution"></a></p>
-<h4 id="1-download-the-jbi-distribution">1) Download the JBI distribution</h4>
+<h2 id="1-download-the-jbi-distribution">1) Download the JBI distribution</h2>
<p>Check our <a href="getting-ode.html">download page</a> and get the latest
JBI-based distribution. Unzip it in a directory of your choice. We'll now refer
to this directory as ODE_HOME.</p>
<p><a name="JBIDeployment-2)InstallonJBIcontainer"></a></p>
-<h4 id="2-install-on-jbi-container">2) Install on JBI container</h4>
+<h2 id="2-install-on-jbi-container">2) Install on JBI container</h2>
<p>For example, with ServiceMix you can use file-system deployment:</p>
-<div class="codehilite"><pre><span class="p">(</span><span
class="n">from</span> <span class="n">ode</span><span class="o">/</span><span
class="n">jbi</span> <span class="n">directory</span><span class="p">)</span>
-<span class="n">cp</span> <span class="n">ODE_HOME</span><span
class="sr">/ode-jbi-1.1.zip SERVICEMIX_DIR/i</span><span class="n">nstall</span>
+<div class="codehilite"><pre>(from ode/jbi directory)
+cp ODE_HOME/ode-jbi-1.1.zip SERVICEMIX_DIR/install
</pre></div>
<p>The above will result in ODE being installed with the default settings. You
may wish to first modify the <code>ode-jbi.properties</code> file found in the
root of the installer ZIP.</p>
<p><a name="JBIDeployment-3)DeployingProcesses"></a></p>
-<h4 id="3-deploying-processes">3) Deploying Processes</h4>
+<h3 id="3-deploying-processes">3) Deploying Processes</h3>
<p>We are assuming that the reader is familiar with JBI deployment concepts.
Deploying a process consists of the following steps:</p>
<ol>
<li>Create a temporary <em>service unit</em> directory for the BPEL
processes</li>
@@ -110,7 +111,7 @@
<li>Copy the service assembly archive into the appropriate <em>deploy</em>
directory</li>
</ol>
<p><a name="JBIDeployment-Examples"></a></p>
-<h4 id="examples">Examples</h4>
+<h2 id="examples">Examples</h2>
<p>Some JBI examples are available under the <em>examples</em> directory of
the ODE distro:</p>
<ul>
<li>HelloWorld2</li>
@@ -119,34 +120,34 @@
</ul>
<p>Extract the distro-jbi-2.0-SNAPSHOT.zip created in the build instructions
above.</p>
<p>To compile the examples, you may wish to define the ODE_HOME environment
variable. The build script does a good job of figuring this out without
ODE_HOME set, however.</p>
-<div class="codehilite"><pre><span class="c1"># On Linux/Unix</span>
-<span class="n">export</span> <span class="n">ODE_HOME</span><span
class="o">=</span><span class="sr">/path/</span><span class="n">to</span><span
class="sr">/ode/</span><span class="n">distribution</span>
+<div class="codehilite"><pre># On Linux/Unix
+export ODE_HOME=/path/to/ode/distribution
-<span class="c1"># On Windows</span>
-<span class="n">set</span> <span class="n">ODE_HOME</span><span
class="o">=</span><span class="n">C:</span><span class="o">\</span><span
class="n">Path</span><span class="o">\</span><span class="n">To</span><span
class="o">\</span><span class="n">ODE</span><span class="o">\</span><span
class="n">Distribution</span>
+# On Windows
+set ODE_HOME=C:\Path\To\ODE\Distribution
</pre></div>
<p>and run Ant in the example's directory:</p>
-<div class="codehilite"><pre><span class="n">cd</span> <span
class="nv">%ODE_HOME%</span><span class="err">/</span><span
class="nv">examples</span><span class="o">/</span><span
class="n">PingPong</span>
-<span class="n">ant</span>
+<div class="codehilite"><pre>cd %ODE_HOME%/examples/PingPong
+ant
</pre></div>
<p>This will create a JBI service assembly in the "build" subdirectory. With
ServiceMix you can simply copy it to the file-system hot deployment
directory:</p>
-<div class="codehilite"><pre><span class="p">(</span><span
class="n">from</span> <span class="n">PingPong</span> <span
class="n">directory</span><span class="p">)</span>
-<span class="n">cp</span> <span class="n">build</span><span
class="sr">/PingPing-sa.zip SERVICEMIX_DIR/</span><span class="n">deploy</span>
+<div class="codehilite"><pre>(from PingPong directory)
+cp build/PingPing-sa.zip SERVICEMIX_DIR/deploy
</pre></div>
<p>Finally, you can test the example by typing:</p>
-<div class="codehilite"><pre><span class="p">(</span><span
class="n">from</span> <span class="n">PingPong</span> <span
class="n">directory</span><span class="p">)</span>
-<span class="n">ant</span> <span class="n">test</span>
+<div class="codehilite"><pre>(from PingPong directory)
+ant test
</pre></div>
<p><a name="JBIDeployment-JBIEndpoints"></a></p>
-<h3 id="jbi-endpoints">JBI Endpoints</h3>
+<h2 id="jbi-endpoints">JBI Endpoints</h2>
<p>ODE now relies strictly on abstract web service definitions (i.e., without
binding/service/port definitions), meaning that you only need abstract WSDLs
when compiling processes. Since JBI uses normalized messages (in theory, at
least), there is no need to define bindings for the BPEL service engine.</p>
<p>In deploy.xml, you simply define the JBI internal endpoints invoked or
provided by your partnerLinks,</p>
<div class="codehilite"><pre><span class="cp"><?xml version="1.0"
encoding="UTF-8"?></span>
@@ -171,13 +172,13 @@
<p>One may use JBI binding components to make services externally available
and therefore providing concrete bindings to those binding components. An
example of exposing process services via SOAP/HTTP can be found in the PingPong
<a
href="http://svn.apache.org/repos/asf/ode/branches/APACHE_ODE_1.X/distro/src/examples-jbi/PingPong/ping-http/";>ping-http
service unit</a>.</p>
<p><a name="JBIDeployment-Database"></a></p>
-<h3 id="database">Database</h3>
+<h2 id="database">Database</h2>
<p>The generated installer will use an internally-managed embedded Derby
database. No configuration is required. To use an external database one needs
to modify <code>ode-jbi.properties</code> found in the component installer
zip.</p>
<p><a name="JBIDeployment-CompatibilityCaveat"></a></p>
-<h3 id="compatibility-caveat">Compatibility Caveat</h3>
+<h2 id="compatibility-caveat">Compatibility Caveat</h2>
<p>Many binding components are not very good about delivering messages in the
correct format for WSDL11 services.</p>
<p><a name="JBIDeployment-KnownIssueswithServiceMix"></a></p>
-<h4 id="known-issues-with-servicemix">Known Issues with ServiceMix</h4>
+<h3 id="known-issues-with-servicemix">Known Issues with ServiceMix</h3>
<p>ServiceMix' so-called <em>lightweight components</em> make it difficult to
properly expose process services since they do not fully implement the JBI
contract and do not allow the process engine to enquire about its external
endpoints.
* SoapHelper needs to properly resolve the WSDL operation name (patch
available)
<a
href="https://issues.apache.org/activemq/browse/SM-488";>https://issues.apache.org/activemq/browse/SM-488</a></p>
Modified: websites/staging/ode/trunk/content/smx4-osgi-deployment.html
==============================================================================
--- websites/staging/ode/trunk/content/smx4-osgi-deployment.html (original)
+++ websites/staging/ode/trunk/content/smx4-osgi-deployment.html Mon Dec 10
21:36:05 2012
@@ -82,56 +82,56 @@
<div class="row">
<div class="span12">
<p><a
name="SMX4OSGiDeployment-DeployApacheODEOSGibundleandexampleprocess(PingPong)"></a></p>
-<h3 id="deploy-apache-ode-osgi-bundle-and-example-process-ping-pong">Deploy
Apache ODE OSGi bundle and example process (Ping Pong)</h3>
+<h2 id="deploy-apache-ode-osgi-bundle-and-example-process-ping-pong">Deploy
Apache ODE OSGi bundle and example process (Ping Pong)</h2>
<p>Enter smx4 console and run following commands:</p>
-<div class="codehilite"><pre><span class="err">features:addUrl</span> <span
class="err">mvn:org.apache.ode/ode-jbi-karaf/1.3.5-SNAPSHOT/xml/features</span>
-<span class="err">features:install</span> <span class="err">ode</span>
-<span class="err">features:install</span> <span
class="err">examples-ode-ping-pong</span>
+<div class="codehilite"><pre>features:addUrl
mvn:org.apache.ode/ode-jbi-karaf/1.3.5-SNAPSHOT/xml/features
+features:install ode
+features:install examples-ode-ping-pong
</pre></div>
<p>This will install ODE with default settings (OpenJPA DAO, embedded Derby
database)</p>
<p><a name="SMX4OSGiDeployment-Configuringdatabase"></a></p>
-<h3 id="configuring-database">Configuring database</h3>
-<p>Create SMX4/etc/org.apache.ode.jbi.cfg file with following contents:</p>
-<div class="codehilite"><pre><span class="n">ode</span><span
class="o">-</span><span class="n">jbi</span><span class="o">.</span><span
class="n">pidNamespace</span><span class="o">=</span><span
class="n">urn:ode</span><span class="o">-</span><span class="n">jbi</span>
-<span class="n">ode</span><span class="o">-</span><span
class="n">jbi</span><span class="o">.</span><span
class="n">allowIncompleteDeployment</span><span class="o">=</span><span
class="n">false</span>
-<span class="n">ode</span><span class="o">-</span><span
class="n">jbi</span><span class="o">.</span><span
class="n">messageMapper</span><span class="o">=</span><span
class="n">org</span><span class="o">.</span><span class="n">apache</span><span
class="o">.</span><span class="n">ode</span><span class="o">.</span><span
class="n">jbi</span><span class="o">.</span><span class="n">msgmap</span><span
class="o">.</span><span class="n">ServiceMixMapper</span>
-<span class="n">ode</span><span class="o">-</span><span
class="n">jbi</span><span class="o">.</span><span class="n">event</span><span
class="o">.</span><span class="n">listeners</span><span class="o">=</span><span
class="n">org</span><span class="o">.</span><span class="n">apache</span><span
class="o">.</span><span class="n">ode</span><span class="o">.</span><span
class="n">bpel</span><span class="o">.</span><span class="n">common</span><span
class="o">.</span><span class="n">evt</span><span class="o">.</span><span
class="n">DebugBpelEventListener</span>
-
-<span class="c1">#For MySQL</span>
-<span class="c1">#ode-jbi.db.int.mcf=org.tranql.connector.mysql.XAMCF</span>
-<span class="c1">#ode-jbi.db.int.mcf.databaseName=ODE</span>
-<span class="c1">#ode-jbi.db.int.mcf.userName=root</span>
-<span class="c1">#ode-jbi.db.int.mcf.password=root</span>
-<span class="c1">#ode-jbi.db.int.mcf.serverName=localhost</span>
-
-<span class="c1">#For Postgres</span>
-<span
class="c1">#ode-jbi.db.int.mcf=org.tranql.connector.postgresql.PGXAMCF</span>
-<span class="c1">#ode-jbi.db.int.mcf.databaseName=ODE</span>
-<span class="c1">#ode-jbi.db.int.mcf.userName=postgres</span>
-<span class="c1">#ode-jbi.db.int.mcf.password=postgres</span>
-<span class="c1">#ode-jbi.db.int.mcf.serverName=localhost</span>
-
-<span class="c1">#For SQLServer</span>
-<span
class="c1">#ode-jbi.db.int.mcf=org.tranql.connector.sqlserver.XAMCF</span>
-<span class="c1">#ode-jbi.db.int.mcf.databaseName=ODE</span>
-<span class="c1">#ode-jbi.db.int.mcf.userName=sa</span>
-<span class="c1">#ode-jbi.db.int.mcf.password=sa</span>
-<span class="c1">#ode-jbi.db.int.mcf.portNumber=1433</span>
-<span class="c1">#ode-jbi.db.int.mcf.serverName=localhost</span>
-
-<span class="c1">#For Oracle</span>
-<span class="n">ode</span><span class="o">-</span><span
class="n">jbi</span><span class="o">.</span><span class="n">db</span><span
class="o">.</span><span class="nb">int</span><span class="o">.</span><span
class="n">mcf</span><span class="o">=</span><span class="n">org</span><span
class="o">.</span><span class="n">tranql</span><span class="o">.</span><span
class="n">connector</span><span class="o">.</span><span
class="n">oracle</span><span class="o">.</span><span class="n">LocalMCF</span>
-<span class="n">ode</span><span class="o">-</span><span
class="n">jbi</span><span class="o">.</span><span class="n">db</span><span
class="o">.</span><span class="nb">int</span><span class="o">.</span><span
class="n">mcf</span><span class="o">.</span><span
class="n">databaseName</span><span class="o">=</span><span class="n">XE</span>
-<span class="n">ode</span><span class="o">-</span><span
class="n">jbi</span><span class="o">.</span><span class="n">db</span><span
class="o">.</span><span class="nb">int</span><span class="o">.</span><span
class="n">mcf</span><span class="o">.</span><span
class="n">userName</span><span class="o">=</span><span class="n">ODE</span>
-<span class="n">ode</span><span class="o">-</span><span
class="n">jbi</span><span class="o">.</span><span class="n">db</span><span
class="o">.</span><span class="nb">int</span><span class="o">.</span><span
class="n">mcf</span><span class="o">.</span><span
class="n">password</span><span class="o">=</span><span class="n">ode</span>
-<span class="n">ode</span><span class="o">-</span><span
class="n">jbi</span><span class="o">.</span><span class="n">db</span><span
class="o">.</span><span class="nb">int</span><span class="o">.</span><span
class="n">mcf</span><span class="o">.</span><span
class="n">portNumber</span><span class="o">=</span><span class="mi">1521</span>
-<span class="n">ode</span><span class="o">-</span><span
class="n">jbi</span><span class="o">.</span><span class="n">db</span><span
class="o">.</span><span class="nb">int</span><span class="o">.</span><span
class="n">mcf</span><span class="o">.</span><span
class="n">serverName</span><span class="o">=</span><span
class="n">localhost</span>
-<span class="n">ode</span><span class="o">-</span><span
class="n">jbi</span><span class="o">.</span><span class="n">db</span><span
class="o">.</span><span class="nb">int</span><span class="o">.</span><span
class="n">mcf</span><span class="o">.</span><span
class="n">driverType</span><span class="o">=</span><span class="n">thin</span>
+<h2 id="configuring-database">Configuring database</h2>
+<p>Create <code>SMX4/etc/org.apache.ode.jbi.cfg</code> file with following
contents:</p>
+<div class="codehilite"><pre>ode-jbi.pidNamespace=urn:ode-jbi
+ode-jbi.allowIncompleteDeployment=false
+ode-jbi.messageMapper=org.apache.ode.jbi.msgmap.ServiceMixMapper
+ode-jbi.event.listeners=org.apache.ode.bpel.common.evt.DebugBpelEventListener
+
+#For MySQL
+#ode-jbi.db.int.mcf=org.tranql.connector.mysql.XAMCF
+#ode-jbi.db.int.mcf.databaseName=ODE
+#ode-jbi.db.int.mcf.userName=root
+#ode-jbi.db.int.mcf.password=root
+#ode-jbi.db.int.mcf.serverName=localhost
+
+#For Postgres
+#ode-jbi.db.int.mcf=org.tranql.connector.postgresql.PGXAMCF
+#ode-jbi.db.int.mcf.databaseName=ODE
+#ode-jbi.db.int.mcf.userName=postgres
+#ode-jbi.db.int.mcf.password=postgres
+#ode-jbi.db.int.mcf.serverName=localhost
+
+#For SQLServer
+#ode-jbi.db.int.mcf=org.tranql.connector.sqlserver.XAMCF
+#ode-jbi.db.int.mcf.databaseName=ODE
+#ode-jbi.db.int.mcf.userName=sa
+#ode-jbi.db.int.mcf.password=sa
+#ode-jbi.db.int.mcf.portNumber=1433
+#ode-jbi.db.int.mcf.serverName=localhost
+
+#For Oracle
+ode-jbi.db.int.mcf=org.tranql.connector.oracle.LocalMCF
+ode-jbi.db.int.mcf.databaseName=XE
+ode-jbi.db.int.mcf.userName=ODE
+ode-jbi.db.int.mcf.password=ode
+ode-jbi.db.int.mcf.portNumber=1521
+ode-jbi.db.int.mcf.serverName=localhost
+ode-jbi.db.int.mcf.driverType=thin
-<span class="c1"># Uncomment the following to enable hibernate (this is
recommended for production use):</span>
-<span
class="c1">#ode-jbi.dao.factory=org.apache.ode.daohib.bpel.BpelDAOConnectionFactoryImpl</span>
+# Uncomment the following to enable hibernate (this is recommended for
production use):
+#ode-jbi.dao.factory=org.apache.ode.daohib.bpel.BpelDAOConnectionFactoryImpl
</pre></div>
@@ -142,19 +142,19 @@ So you need to run following command fro
</pre></div>
-<p>Please note that etc/org.apache.ode.jbi.cfg must be set to the same
database (in this case oracle) to load required dependencies properly. </p>
+<p>Please note that <code>etc/org.apache.ode.jbi.cfg</code> must be set to the
same database (in this case oracle) to load required dependencies properly.</p>
<p><a name="SMX4OSGiDeployment-Tips"></a></p>
-<h3 id="tips">Tips</h3>
+<h2 id="tips">Tips</h2>
<p><a name="SMX4OSGiDeployment-HowtomakePMAPIwork?"></a></p>
-<h4 id="how-to-make-pmapi-work">How to make PMAPI work?</h4>
+<h3 id="how-to-make-pmapi-work">How to make PMAPI work?</h3>
<p>You can grab pmapi SA from here <a
href="http://markmail.org/message/ghigpzcpt2j3qnoo";>http://markmail.org/message/ghigpzcpt2j3qnoo</a>.
-Then edit SMX4 etc/config.properties and change from:</p>
-<div class="codehilite"><pre><span class="n">org</span><span
class="o">.</span><span class="n">osgi</span><span class="o">.</span><span
class="n">framework</span><span class="o">.</span><span
class="n">bootdelegation</span><span class="o">=</span><span
class="n">sun</span><span class="o">.*</span><span class="p">,</span><span
class="n">com</span><span class="o">.</span><span class="n">sun</span><span
class="o">*</span><span class="p">,</span><span class="n">javax</span><span
class="o">.</span><span class="n">transaction</span><span
class="p">,</span><span class="n">javax</span><span class="o">.</span><span
class="n">transaction</span><span class="o">.*</span>
+Then edit SMX4 <code>etc/config.properties</code> and change from:</p>
+<div
class="codehilite"><pre>org.osgi.framework.bootdelegation=sun.*,com.sun*,javax.transaction,javax.transaction.*
</pre></div>
<p>to:</p>
-<div class="codehilite"><pre><span class="n">org</span><span
class="o">.</span><span class="n">osgi</span><span class="o">.</span><span
class="n">framework</span><span class="o">.</span><span
class="n">bootdelegation</span><span class="o">=</span><span
class="n">sun</span><span class="o">.*</span><span class="p">,</span><span
class="n">com</span><span class="o">.</span><span class="n">sun</span><span
class="o">*</span><span class="p">,</span><span class="n">javax</span><span
class="o">.</span><span class="n">transaction</span><span
class="p">,</span><span class="n">javax</span><span class="o">.</span><span
class="n">transaction</span><span class="o">.*</span><span
class="p">,</span><span class="n">javax</span><span class="o">.</span><span
class="n">xml</span><span class="o">.</span><span class="n">stream</span><span
class="p">,</span><span class="n">javax</span><span class="o">.</span><span
class="n">xml</span><span class="o">.</span><span class="n">stream</span><span
class=
"o">.*</span>
+<div
class="codehilite"><pre>org.osgi.framework.bootdelegation=sun.*,com.sun*,javax.transaction,javax.transaction.*,javax.xml.stream,javax.xml.stream.*
</pre></div>
</div>
</div>
Modified: websites/staging/ode/trunk/content/user-guide.html
==============================================================================
--- websites/staging/ode/trunk/content/user-guide.html (original)
+++ websites/staging/ode/trunk/content/user-guide.html Mon Dec 10 21:36:05 2012
@@ -83,7 +83,7 @@
<div class="span12">
<p><a name="UserGuide-GettingStarted"></a></p>
<h2 id="getting-started">Getting Started</h2>
-<p>First of all, getting familiar with the <a href="ws-bpel-2.0.html">WS-BPEL
2.0</a> standard is a very good idea. To use ODE, you will need to write
processes using the BPEL language. There are several examples in our <a
href="getting-ode.html">distributions</a> that you can use to get started, but
a decent understanding of the spec is assumed.</p>
+<p>First of all, getting familiar with the <a href="ws-bpel-20.html">WS-BPEL
2.0</a> standard is a very good idea. To use ODE, you will need to write
processes using the BPEL language. There are several examples in our <a
href="getting-ode.html">distributions</a> that you can use to get started, but
a decent understanding of the spec is assumed.</p>
<p>Then, you can optionally check out <a href="ode-schema.html">ODE Schema</a>
page in order to install schema for your database. Please note that schemas
from distribution sometimes contain errors, because of poor quality of ORM
schema generators.</p>
<p>ODE can be deployed in three different environments:</p>
<ul>
Modified: websites/staging/ode/trunk/content/war-deployment.html
==============================================================================
--- websites/staging/ode/trunk/content/war-deployment.html (original)
+++ websites/staging/ode/trunk/content/war-deployment.html Mon Dec 10 21:36:05
2012
@@ -82,25 +82,26 @@
<div class="row">
<div class="span12">
<p><a name="WARDeployment-DeployingtheWAR"></a></p>
-<h4 id="deploying-the-war">Deploying the WAR</h4>
+<h2 id="deploying-the-war">Deploying the WAR</h2>
<p>Unzip the <a href="getting-ode.html">distribution</a> somewhere on your
disk, everything needed is inside.</p>
-<p>Get the WAR file in the distribution root directory, rename it to
<em>ode.war</em> and copy this file to <a
href="http://tomcat.apache.org";>Tomcat</a>'s webapp directory. Start Tomcat and
ODE should be up and running. You should get the
[Axis2|http://ws.apache.org/axis2] welcome 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.</p>
+<p>Get the WAR file in the distribution root directory, rename it to
<em>ode.war</em> and copy this file to <a
href="http://tomcat.apache.org";>Tomcat</a>'s webapp directory. Start Tomcat and
ODE should be up and running. You should get the <a
href="http://ws.apache.org/axis2";>Axis2</a> welcome page under <a
href="http://localhost:8080/ode";>http://localhost:8080/ode</a>. The ODE WAR
includes its own embedded database (<a
href="http://db.apache.org/derby";>Derby</a>) so you don't have to worry about
configuring any external database for now.</p>
<p><a name="WARDeployment-Examples"></a></p>
-<h4 id="examples">Examples</h4>
+<h3 id="examples">Examples</h3>
<p>Copy the content of the <em>examples</em> directory in the distribution
(the 3 sub-directories) to <em>tomcat/webapps/ode/WEB-INF/processes</em>, this
will automatically deploy the 3 example processes. Use the sendsoap command
located in the distribution <em>bin</em> 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 something like:</p>
-<div class="codehilite"><pre><span class="n">bin</span><span
class="sr">/sendsoap http://localhost:8080/o</span><span
class="n">de</span><span class="sr">/processes/</span><span
class="n">helloWorld</span> <span class="n">examples</span><span
class="sr">/HelloWorld2/</span><span class="n">testRequest</span><span
class="o">.</span><span class="n">soap</span>
+<div class="codehilite"><pre>bin/sendsoap
http://localhost:8080/ode/processes/helloWorld
examples/HelloWorld2/testRequest.soap
</pre></div>
<p>The <em>sendsoap</em> executable can be found in the distribution
<em>bin</em> directory. The urls should be updated according to the address
defined in the WSDL file for the process service.</p>
<p><a name="WARDeployment-ConfiguringODEinTomcatwithaMySQLdatabase"></a></p>
-<h4 id="configuring-ode-in-tomcat-with-a-mysql-database">Configuring ODE in
Tomcat with a MySQL database</h4>
+<h3 id="configuring-ode-in-tomcat-with-a-mysql-database">Configuring ODE in
Tomcat with a MySQL database</h3>
<p>The ODE war should have been copied to the <em>webapps</em> directory of
Tomcat and the server should have been started at least once before following
these instructions. This ensures that the webapp is properly exploded.</p>
<ol>
<li>Drop the MySQL JDBC driver (<a
href="http://dev.mysql.com/downloads/#connector-j";>MySQL Connector/J</a>) in
the <em>common/lib</em> directory of Tomcat.</li>
<li>
<p>Add the following stanza to <em>conf/server.xml</em> inside the <Host>
element:</p>
-<p><Context path="/ode" docBase="ode" debug="5" reloadable="true"
crossContext="true">
+<p>:::xml
+ <Context path="/ode" docBase="ode" debug="5" reloadable="true"
crossContext="true">
<Resource name="jdbc/ODEDB" auth="Container" type="javax.sql.DataSource"
maxActive="100" maxIdle="30" maxWait="10000"
username="root" password="" driverClassName="com.mysql.jdbc.Driver"
@@ -109,27 +110,29 @@
</li>
<li>
<p>Make sure that MySQL is started and the <a
href="^ode_openjpa_mysql-1.3.2.sql.html">ODE schema</a> has been loaded in a
<em>ode</em> database.</p>
-<p>$ mysql -u root
+<p>:::text
+$ mysql -u root
mysql> create database ode;
mysql> exit
$ mysql -u root ode < ode_openjpa_mysql-1.3.2.sql</p>
</li>
<li>
<p>Add a file named <em>ode-axis2.properties</em> under
<em>webapps/ode/WEB-INF/conf</em> with the following content:</p>
-<p>ode-axis2.db.mode=EXTERNAL
- ode-axis2.db.ext.dataSource=java:comp/env/jdbc/ODEDB</p>
+<p>:::text
+ode-axis2.db.mode=EXTERNAL
+ode-axis2.db.ext.dataSource=java:comp/env/jdbc/ODEDB</p>
</li>
</ol>
<p>You're done!</p>
<p><a
name="WARDeployment-ConfiguringODEinJBosswithJNDIEXTERNALdatasource"></a></p>
-<h4 id="configuring-ode-in-jboss-with-jndi-external-datasource">Configuring
ODE in JBoss with JNDI EXTERNAL datasource</h4>
+<h2 id="configuring-ode-in-jboss-with-jndi-external-datasource">Configuring
ODE in JBoss with JNDI EXTERNAL datasource</h2>
<p>Create ode/WEB-INF/conf/ode-axis2.properties with following content:</p>
-<div class="codehilite"><pre><span class="c1">#Uncomment for using dao
hibernate</span>
-<span
class="c1">#ode-axis2.dao.factory=org.apache.ode.daohib.bpel.BpelDAOConnectionFactoryImpl</span>
-<span class="n">ode</span><span class="o">-</span><span
class="n">axis2</span><span class="o">.</span><span class="n">db</span><span
class="o">.</span><span class="n">mode</span><span class="o">=</span><span
class="n">EXTERNAL</span>
-<span class="n">ode</span><span class="o">-</span><span
class="n">axis2</span><span class="o">.</span><span class="n">db</span><span
class="o">.</span><span class="n">ext</span><span class="o">.</span><span
class="n">dataSource</span><span class="o">=</span><span
class="n">java:comp</span><span class="sr">/env/</span><span
class="n">jdbc</span><span class="o">/</span><span class="n">ode</span>
-<span class="n">ode</span><span class="o">-</span><span
class="n">axis2</span><span class="o">.</span><span class="n">event</span><span
class="o">.</span><span class="n">listeners</span><span class="o">=</span><span
class="n">org</span><span class="o">.</span><span class="n">apache</span><span
class="o">.</span><span class="n">ode</span><span class="o">.</span><span
class="n">bpel</span><span class="o">.</span><span class="n">common</span><span
class="o">.</span><span class="n">evt</span><span class="o">.</span><span
class="n">DebugBpelEventListener</span>
-<span class="n">ode</span><span class="o">-</span><span
class="n">axis2</span><span class="o">.</span><span class="n">tx</span><span
class="o">.</span><span class="n">factory</span><span class="o">.</span><span
class="n">class</span><span class="o">=</span><span class="n">org</span><span
class="o">.</span><span class="n">apache</span><span class="o">.</span><span
class="n">ode</span><span class="o">.</span><span class="n">axis2</span><span
class="o">.</span><span class="n">util</span><span class="o">.</span><span
class="n">JBossFactory</span>
+<div class="codehilite"><pre>#Uncomment for using dao hibernate
+#ode-axis2.dao.factory=org.apache.ode.daohib.bpel.BpelDAOConnectionFactoryImpl
+ode-axis2.db.mode=EXTERNAL
+ode-axis2.db.ext.dataSource=java:comp/env/jdbc/ode
+ode-axis2.event.listeners=org.apache.ode.bpel.common.evt.DebugBpelEventListener
+ode-axis2.tx.factory.class=org.apache.ode.axis2.util.JBossFactory
</pre></div>
</div>
</div>
