Author: buildbot
Date: Fri Jul 14 07:54:22 2017
New Revision: 1015453
Log:
Staging update by buildbot for ode
Modified:
websites/staging/ode/trunk/content/ (props changed)
websites/staging/ode/trunk/content/jbi-deployment.html
Propchange: websites/staging/ode/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jul 14 07:54:22 2017
@@ -1 +1 @@
-1801909
+1801911
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 Fri Jul 14 07:54:22
2017
@@ -97,13 +97,27 @@
<div class="row">
<div class="span12">
- <h2 id="overview">Overview</h2>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
+<hr />
+<p><strong>This feature is no more supported from ODE Release
1.3.7</strong></p>
+<hr />
+<h2 id="overview">Overview<a class="headerlink" href="#overview"
title="Permanent link">¶</a></h2>
<p>Here's a quick overview to deploy ODE on a JBI container (e.g. <a
href="http://servicemix.apache.org";>ServiceMix</a>)</p>
<p><a name="JBIDeployment-1)DownloadtheJBIdistribution"></a></p>
-<h2 id="1-download-the-jbi-distribution">1) Download the JBI distribution</h2>
+<h2 id="1-download-the-jbi-distribution">1) Download the JBI distribution<a
class="headerlink" href="#1-download-the-jbi-distribution" title="Permanent
link">¶</a></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>
-<h2 id="2-install-on-jbi-container">2) Install on JBI container</h2>
+<h2 id="2-install-on-jbi-container">2) Install on JBI container<a
class="headerlink" href="#2-install-on-jbi-container" title="Permanent
link">¶</a></h2>
<p>For example, with ServiceMix you can use file-system deployment:</p>
<div class="codehilite"><pre>(from ode/jbi directory)
cp ODE_HOME/ode-jbi-1.1.zip SERVICEMIX_DIR/install
@@ -112,7 +126,7 @@ cp ODE_HOME/ode-jbi-1.1.zip SERVICEMIX_D
<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>
-<h3 id="3-deploying-processes">3) Deploying Processes</h3>
+<h3 id="3-deploying-processes">3) Deploying Processes<a class="headerlink"
href="#3-deploying-processes" title="Permanent link">¶</a></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>
@@ -127,7 +141,7 @@ cp ODE_HOME/ode-jbi-1.1.zip SERVICEMIX_D
<li>Copy the service assembly archive into the appropriate <em>deploy</em>
directory</li>
</ol>
<p><a name="JBIDeployment-Examples"></a></p>
-<h2 id="examples">Examples</h2>
+<h2 id="examples">Examples<a class="headerlink" href="#examples"
title="Permanent link">¶</a></h2>
<p>Some JBI examples are available under the <em>examples</em> directory of
the ODE distro:</p>
<ul>
<li>HelloWorld2</li>
@@ -163,7 +177,7 @@ ant test
<p><a name="JBIDeployment-JBIEndpoints"></a></p>
-<h2 id="jbi-endpoints">JBI Endpoints</h2>
+<h2 id="jbi-endpoints">JBI Endpoints<a class="headerlink"
href="#jbi-endpoints" title="Permanent link">¶</a></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>
@@ -188,13 +202,13 @@ ant test
<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>
-<h2 id="database">Database</h2>
+<h2 id="database">Database<a class="headerlink" href="#database"
title="Permanent link">¶</a></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>
-<h2 id="compatibility-caveat">Compatibility Caveat</h2>
+<h2 id="compatibility-caveat">Compatibility Caveat<a class="headerlink"
href="#compatibility-caveat" title="Permanent link">¶</a></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>
-<h3 id="known-issues-with-servicemix">Known Issues with ServiceMix</h3>
+<h3 id="known-issues-with-servicemix">Known Issues with ServiceMix<a
class="headerlink" href="#known-issues-with-servicemix" title="Permanent
link">¶</a></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>
