Author: buildbot
Date: Mon Dec 31 15:49:22 2012
New Revision: 844420
Log:
Staging update by buildbot for ode
Modified:
websites/staging/ode/trunk/content/ (props changed)
websites/staging/ode/trunk/content/direct-process-to-process-communication.html
websites/staging/ode/trunk/content/endpoint-references.html
websites/staging/ode/trunk/content/extensions/wsdl-11-extensions-for-rest.html
websites/staging/ode/trunk/content/instance-data-cleanup.html
websites/staging/ode/trunk/content/ode-jbi-and-axis2-properties-overview.html
websites/staging/ode/trunk/content/sitemap.html
websites/staging/ode/trunk/content/wsdl-11-http-binding-support.html
Propchange: websites/staging/ode/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec 31 15:49:22 2012
@@ -1 +1 @@
-1427155
+1427156
Modified:
websites/staging/ode/trunk/content/direct-process-to-process-communication.html
==============================================================================
---
websites/staging/ode/trunk/content/direct-process-to-process-communication.html
(original)
+++
websites/staging/ode/trunk/content/direct-process-to-process-communication.html
Mon Dec 31 15:49:22 2012
@@ -28,7 +28,7 @@
<li class="">
<a href="/getting-ode.html">Getting ODE</a>
</li>
- <li class=" dropdown">
+ <li class="active dropdown">
<a href="/user-guide.html" class="dropdown-toggle"
data-toggle="dropdown" data-target="#">Documentation<b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="/userguide/">User Guide</a></li>
@@ -83,7 +83,8 @@
<div class="row">
<div class="span12">
- <p>ODE automatically optimizes all process-to-process communication
such that all message exchanges happen directly inside the engine and do not go
through the integration layer (e.g. Axis2, JBI, ...).</p>
+ <h1 id="p2p-communication">P2P Communication</h1>
+<p>ODE automatically optimizes all process-to-process (P2P) communication such
that all message exchanges happen directly inside the engine and do not go
through the integration layer (e.g. Axis2, JBI, ...).</p>
</div>
</div>
Modified: websites/staging/ode/trunk/content/endpoint-references.html
==============================================================================
--- websites/staging/ode/trunk/content/endpoint-references.html (original)
+++ websites/staging/ode/trunk/content/endpoint-references.html Mon Dec 31
15:49:22 2012
@@ -28,7 +28,7 @@
<li class="">
<a href="/getting-ode.html">Getting ODE</a>
</li>
- <li class=" dropdown">
+ <li class="active dropdown">
<a href="/user-guide.html" class="dropdown-toggle"
data-toggle="dropdown" data-target="#">Documentation<b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="/userguide/">User Guide</a></li>
@@ -84,19 +84,19 @@
<div class="row">
<div class="span12">
<p><a name="EndpointReferences-Introduction"></a></p>
-<h3 id="introduction">Introduction</h3>
+<h2 id="introduction">Introduction</h2>
<p>An endpoint reference holds information to call a service. The simplest
endpoint reference is usually an URL but it can also be much more complex such
as holding a message id, a reply-to address or custom properties.</p>
<p>In BPEL, endpoint references (aka EPRs) are modeled as partner link roles.
When defining a partner link, two roles maybe defined, <code>myRole</code> and
<code>partnerRole</code>:</p>
-<div class="codehilite"><pre><span class="o"><</span><span
class="n">partnerLink</span> <span class="n">name</span><span
class="o">=</span><span class="s">"responderPartnerLink"</span> <span
class="n">partnerLinkType</span><span class="o">=</span><span
class="s">"test:ResponderPartnerLinkType"</span>
- <span class="n">myRole</span><span class="o">=</span><span
class="s">"main"</span> <span class="n">partnerRole</span><span
class="o">=</span><span class="s">"responder"</span> <span
class="n">initializePartnerRole</span><span class="o">=</span><span
class="s">"yes"</span><span class="o">/></span>
+<div class="codehilite"><pre><span class="nt"><partnerLink</span> <span
class="na">name=</span><span class="s">"responderPartnerLink"</span>
<span class="na">partnerLinkType=</span><span
class="s">"test:ResponderPartnerLinkType"</span>
+ <span class="na">myRole=</span><span
class="s">"main"</span> <span class="na">partnerRole=</span><span
class="s">"responder"</span> <span
class="na">initializePartnerRole=</span><span
class="s">"yes"</span><span class="nt">/></span>
</pre></div>
<p>Both <code>partnerRole</code> and <code>myRole</code> represent EPRs. So
when assigning partner link roles or invoking partners, you are using EPRs
behind the scene.</p>
<p><a name="EndpointReferences-ODEandEndpointReferences"></a></p>
-<h3 id="ode-and-endpoint-references">ODE and Endpoint References</h3>
+<h2 id="ode-and-endpoint-references">ODE and Endpoint References</h2>
<p><a name="EndpointReferences-TypesofEPRs"></a></p>
-<h4 id="types-of-eprs">Types of EPRs</h4>
+<h3 id="types-of-eprs">Types of EPRs</h3>
<p>The ODE runtime supports 4 types of EPRs:</p>
<ul>
<li>A simple URL or a URL in the location attribute of the binding. See <a
href="http://www.w3.org/TR/wsdl#_soap:address";>soap:address</a> and <a
href="http://www.w3.org/TR/wsdl#_http:address";>http:address</a> WSDL 1.1
binding.</li>
@@ -191,7 +191,7 @@
<p>Normally BPEL requires wrapping EPRs with inside a <code>service-ref</code>
element, however ODE relaxes this requirement for ease of use and increased
interoperability with existing services. If the <code>service-ref</code>
element is absent, the EPR is automatically wrapped inside one on the fly.
Moreover, ODE automatically detects the different EPR types when assigning to a
partner link role. If you need to use WS-Addressing sessions (@see appropriate
page), then you will have to use <code>wsa:EndpointReference</code> EPRs.</p>
<p>You can just as well assign EPRs to/from variables to pass them around and
enable more dynamic communication patterns.</p>
<p><a name="EndpointReferences-PassingEndpointReferences"></a></p>
-<h3 id="passing-endpoint-references">Passing Endpoint References</h3>
+<h2 id="passing-endpoint-references">Passing Endpoint References</h2>
<p>To pass endpoint references around and manipulate them, you usually need to
assigne them to variables. The EPR can then be sent in a message and reassigned
to another partner link. This lets you model complex scenarii where you don't
know the address of your partner beforehand or where you select one partner
among many others.</p>
<p>The type of the variable that will hold your EPR defines the type of the
EPR that it will contain. For example if you define a message in your WSDL
document that looks like this:</p>
<div class="codehilite"><pre><span class="nt"><wsdl:message</span> <span
class="na">name=</span><span class="s">"EndpointMessage"</span><span
class="nt">></span>
Modified:
websites/staging/ode/trunk/content/extensions/wsdl-11-extensions-for-rest.html
==============================================================================
---
websites/staging/ode/trunk/content/extensions/wsdl-11-extensions-for-rest.html
(original)
+++
websites/staging/ode/trunk/content/extensions/wsdl-11-extensions-for-rest.html
Mon Dec 31 15:49:22 2012
@@ -28,7 +28,7 @@
<li class="">
<a href="/getting-ode.html">Getting ODE</a>
</li>
- <li class=" dropdown">
+ <li class="active dropdown">
<a href="/user-guide.html" class="dropdown-toggle"
data-toggle="dropdown" data-target="#">Documentation<b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="/userguide/">User Guide</a></li>
Modified: websites/staging/ode/trunk/content/instance-data-cleanup.html
==============================================================================
--- websites/staging/ode/trunk/content/instance-data-cleanup.html (original)
+++ websites/staging/ode/trunk/content/instance-data-cleanup.html Mon Dec 31
15:49:22 2012
@@ -28,7 +28,7 @@
<li class="">
<a href="/getting-ode.html">Getting ODE</a>
</li>
- <li class=" dropdown">
+ <li class="active dropdown">
<a href="/user-guide.html" class="dropdown-toggle"
data-toggle="dropdown" data-target="#">Documentation<b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="/userguide/">User Guide</a></li>
@@ -90,9 +90,11 @@
<h2 id="levels-of-cleanup">Levels of cleanup</h2>
<p><a name="InstanceDataCleanup-Cleanuponcompletion"></a></p>
<h3 id="cleanup-on-completion">Cleanup on completion</h3>
-<p>{panel}
-This feature is only available in ODE 1.3 or later
-{panel}</p>
+<div class="alert alert-info">
+ <h4 class="alert-heading">ODE Version</h4>
+ This feature is only available in ODE 1.3 or later
+</div>
+
<p>The easiest approach to get started is simply to wait until the instance
execution is finished and then cleanup everything that's related to it. That
would include the instance state with its variables, scopes and correlation,
but also all the messages it has received and sent. Execution events should
also be disposed of. So this description defines 5 different categories:
instance, messages and events. We should be able to turn on and off each level
separately.</p>
<ul>
<li>instance: ODE_PROCESS_INSTANCE, EXECUTION_STATE</li>
@@ -101,40 +103,40 @@ This feature is only available in ODE 1.
<li>correlations: ODE_CORRELATION_SET, ODE_CORSET_PROP</li>
<li>events: ODE_EVENTS</li>
</ul>
-<p><a name="InstanceDataCleanup-dtd"></a></p>
-<h4 id="dtd">dtd</h4>
-<div class="codehilite"><pre> <span class="nt"><xs:element</span> <span
class="na">name=</span><span class="s">"cleanup"</span> <span
class="na">minOccurs=</span><span class="s">"0"</span> <span
class="na">maxOccurs=</span><span class="s">"3"</span> <span
class="na">type=</span><span class="s">"dd:tCleanup"</span> <span
class="nt">/></span>
-
- <span class="nt"><xs:complexType</span> <span
class="na">name=</span><span class="s">"tCleanup"</span><span
class="nt">></span>
- <span class="nt"><xs:sequence></span>
- <span class="nt"><xs:element</span> <span
class="na">name=</span><span class="s">"category"</span> <span
class="na">default=</span><span class="s">"all"</span> <span
class="na">minOccurs=</span><span class="s">"0"</span> <span
class="na">maxOccurs=</span><span class="s">"unbounded"</span><span
class="nt">></span>
- <span class="nt"><xs:simpleType></span>
- <span class="nt"><xs:restriction</span> <span
class="na">base=</span><span class="s">"xs:string"</span><span
class="nt">></span>
- <span class="nt"><xs:enumeration</span> <span
class="na">value=</span><span class="s">"instance"</span> <span
class="nt">/></span>
- <span class="nt"><xs:enumeration</span> <span
class="na">value=</span><span class="s">"variables"</span> <span
class="nt">/></span>
- <span class="nt"><xs:enumeration</span> <span
class="na">value=</span><span class="s">"messages"</span> <span
class="nt">/></span>
- <span class="nt"><xs:enumeration</span> <span
class="na">value=</span><span class="s">"correlations"</span> <span
class="nt">/></span>
- <span class="nt"><xs:enumeration</span> <span
class="na">value=</span><span class="s">"events"</span> <span
class="nt">/></span>
- <span class="nt"><xs:enumeration</span> <span
class="na">value=</span><span class="s">"all"</span> <span
class="nt">/></span>
- <span class="nt"></xs:restriction></span>
- <span class="nt"></xs:simpleType></span>
- <span class="nt"></xs:element></span>
- <span class="nt"></xs:sequence></span>
- <span class="nt"><xs:attribute</span> <span
class="na">name=</span><span class="s">"on"</span> <span
class="na">use=</span><span class="s">"required"</span><span
class="nt">></span>
+<div class="caption">DTD</div>
+
+<div class="codehilite"><pre><span class="nt"><xs:element</span> <span
class="na">name=</span><span class="s">"cleanup"</span> <span
class="na">minOccurs=</span><span class="s">"0"</span> <span
class="na">maxOccurs=</span><span class="s">"3"</span> <span
class="na">type=</span><span class="s">"dd:tCleanup"</span> <span
class="nt">/></span>
+
+<span class="nt"><xs:complexType</span> <span class="na">name=</span><span
class="s">"tCleanup"</span><span class="nt">></span>
+ <span class="nt"><xs:sequence></span>
+ <span class="nt"><xs:element</span> <span
class="na">name=</span><span class="s">"category"</span> <span
class="na">default=</span><span class="s">"all"</span> <span
class="na">minOccurs=</span><span class="s">"0"</span> <span
class="na">maxOccurs=</span><span class="s">"unbounded"</span><span
class="nt">></span>
<span class="nt"><xs:simpleType></span>
<span class="nt"><xs:restriction</span> <span
class="na">base=</span><span class="s">"xs:string"</span><span
class="nt">></span>
- <span class="nt"><xs:enumeration</span> <span
class="na">value=</span><span class="s">"success"</span> <span
class="nt">/></span>
- <span class="nt"><xs:enumeration</span> <span
class="na">value=</span><span class="s">"failure"</span> <span
class="nt">/></span>
- <span class="nt"><xs:enumeration</span> <span
class="na">value=</span><span class="s">"always"</span> <span
class="nt">/></span>
+ <span class="nt"><xs:enumeration</span> <span
class="na">value=</span><span class="s">"instance"</span> <span
class="nt">/></span>
+ <span class="nt"><xs:enumeration</span> <span
class="na">value=</span><span class="s">"variables"</span> <span
class="nt">/></span>
+ <span class="nt"><xs:enumeration</span> <span
class="na">value=</span><span class="s">"messages"</span> <span
class="nt">/></span>
+ <span class="nt"><xs:enumeration</span> <span
class="na">value=</span><span class="s">"correlations"</span> <span
class="nt">/></span>
+ <span class="nt"><xs:enumeration</span> <span
class="na">value=</span><span class="s">"events"</span> <span
class="nt">/></span>
+ <span class="nt"><xs:enumeration</span> <span
class="na">value=</span><span class="s">"all"</span> <span
class="nt">/></span>
<span class="nt"></xs:restriction></span>
<span class="nt"></xs:simpleType></span>
- <span class="nt"></xs:attribute></span>
- <span class="nt"></xs:complexType></span>
+ <span class="nt"></xs:element></span>
+ <span class="nt"></xs:sequence></span>
+ <span class="nt"><xs:attribute</span> <span
class="na">name=</span><span class="s">"on"</span> <span
class="na">use=</span><span class="s">"required"</span><span
class="nt">></span>
+ <span class="nt"><xs:simpleType></span>
+ <span class="nt"><xs:restriction</span> <span
class="na">base=</span><span class="s">"xs:string"</span><span
class="nt">></span>
+ <span class="nt"><xs:enumeration</span> <span
class="na">value=</span><span class="s">"success"</span> <span
class="nt">/></span>
+ <span class="nt"><xs:enumeration</span> <span
class="na">value=</span><span class="s">"failure"</span> <span
class="nt">/></span>
+ <span class="nt"><xs:enumeration</span> <span
class="na">value=</span><span class="s">"always"</span> <span
class="nt">/></span>
+ <span class="nt"></xs:restriction></span>
+ <span class="nt"></xs:simpleType></span>
+ <span class="nt"></xs:attribute></span>
+<span class="nt"></xs:complexType></span>
</pre></div>
<p><a name="InstanceDataCleanup-examples"></a></p>
-<h4 id="examples">examples</h4>
+<h2 id="examples">Examples</h2>
<ol>
<li>
<p>no instance data cleanup</p>
@@ -220,7 +222,7 @@ This feature is only available in ODE 1.
</li>
</ol>
<p><a name="InstanceDataCleanup-FutureDevelopments"></a></p>
-<h3 id="future-developments">Future Developments</h3>
+<h2 id="future-developments">Future Developments</h2>
<p>WS-BPEL makes heavy use of scopes, those could be another hook in the
execution lifecycle for the cleanup to take place. So instead of waiting until
the instance is finished and clean up the whole state, we could proceed by
smaller increments and delete the state scope by scope. For short running
processes (say less than a few days) the advantages of this approach are
minimal but for long running processes (say months), there's potentially a lot
of unused state that's just sitting there and will never be used anymore.</p>
<p><a name="InstanceDataCleanup-Finalnotes"></a></p>
<h2 id="final-notes">Final notes</h2>
Modified:
websites/staging/ode/trunk/content/ode-jbi-and-axis2-properties-overview.html
==============================================================================
---
websites/staging/ode/trunk/content/ode-jbi-and-axis2-properties-overview.html
(original)
+++
websites/staging/ode/trunk/content/ode-jbi-and-axis2-properties-overview.html
Mon Dec 31 15:49:22 2012
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<html>
<head>
- <title>Apache ODE – ODE Jbi and Axis2 properties overview</title>
+ <title>Apache ODE – ODE JBI and Axis2 properties overview</title>
<meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
<meta property="og:image" content="http://ode.apache.org/img/ode-logo.png";
/>
@@ -28,7 +28,7 @@
<li class="">
<a href="/getting-ode.html">Getting ODE</a>
</li>
- <li class=" dropdown">
+ <li class="active dropdown">
<a href="/user-guide.html" class="dropdown-toggle"
data-toggle="dropdown" data-target="#">Documentation<b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="/userguide/">User Guide</a></li>
@@ -72,7 +72,7 @@
<header class="jumbotron subhead" id="overview">
<div class="container">
- <h1>ODE Jbi and Axis2 properties overview</h1>
+ <h1>ODE JBI and Axis2 properties overview</h1>
</div>
</header>
@@ -89,96 +89,96 @@
<p><a name="ODEJbiandAxis2propertiesoverview-Commonproperties"></a></p>
<h2 id="common-properties">Common properties</h2>
<p>Here, ode-jbi prefix is used. However for axis2, you need to replace it
into ode-axis2. </p>
-<div class="codehilite"><pre><span class="c1"># Database Mode
("INTERNAL", "EXTERNAL", "EMBEDDED")</span>
-<span class="c1"># What kind of database should ODE use?</span>
-<span class="c1"># * "EMBEDDED" - ODE will create its own embbeded
database (Derby)</span>
-<span class="c1"># and connection pool (Minerva).</span>
-<span class="c1"># * "EXTERNAL" - ODE will use an app-server
provided database and pool.</span>
-<span class="c1"># The "ode-jbi.db.ext.dataSource"
property will need to</span>
-<span class="c1"># be set.</span>
-<span class="c1"># * "INTERNAL" - ODE will create its own
connection pool for a user-</span>
-<span class="c1"># specified JDBC URL and driver.</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="n">mode</span><span class="o">=</span><span
class="n">EMBEDDED</span>
-
-<span class="c1"># External Database [JNDI Name]</span>
-<span class="c1"># JNDI Name of the DataSource for the ODE database. This is
only</span>
-<span class="c1"># used if the "ode-jbi.db.mode" property is set to
"EXTERNAL"</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="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="c1"># Embedded Database Name [String]</span>
-<span class="c1"># Name of the embedded Derby database. This is only used if
the</span>
-<span class="c1"># "ode-jbi.db.mode" property is set to
"EMBEDDED".</span>
-<span class="c1">#ode-jbi.db.emb.name=hibdb</span>
-<span class="c1">#ode-jbi.db.emb.name=jpadb</span>
-
-<span class="c1"># Internal Database Configuration using Tranql Vendor
packages</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>
-
-<span class="c1"># Internal Database Configuration using generic
JDBCDriverMCF</span>
-<span
class="c1">#ode-jbi.db.int.jdbcurl=jdbc:mysql://localhost/ode?user=sa</span>
-<span class="c1">#ode-jbi.db.int.driver=com.mysql.jdbc.Driver</span>
-
-<span class="c1"># DAO Connection Factory class.</span>
-<span class="c1"># uncomment the following for hibernate.</span>
-<span
class="c1">#ode-jbi.dao.factory=org.apache.ode.daohib.bpel.BpelDAOConnectionFactoryImpl</span>
-
-<span class="c1"># BPEL Event Listener</span>
-<span class="c1"># Uncomment the following for a debug output of BPEL
navigation events.</span>
-<span
class="c1">#ode-jbi.event.listeners=org.apache.ode.bpel.common.evt.DebugBpelEventListener</span>
-<span class="c1">#debugeventlistener.dumpToStdOut=on/off</span>
+<div class="codehilite"><pre><span class="c"># Database Mode
("INTERNAL", "EXTERNAL", "EMBEDDED")</span>
+<span class="c"># What kind of database should ODE use?</span>
+<span class="c"># * "EMBEDDED" - ODE will create its own embbeded
database (Derby)</span>
+<span class="c"># and connection pool (Minerva).</span>
+<span class="c"># * "EXTERNAL" - ODE will use an app-server
provided database and pool.</span>
+<span class="c"># The "ode-jbi.db.ext.dataSource"
property will need to</span>
+<span class="c"># be set.</span>
+<span class="c"># * "INTERNAL" - ODE will create its own
connection pool for a user-</span>
+<span class="c"># specified JDBC URL and driver.</span>
+<span class="na">ode-jbi.db.mode</span><span class="o">=</span><span
class="s">EMBEDDED</span>
+
+<span class="c"># External Database [JNDI Name]</span>
+<span class="c"># JNDI Name of the DataSource for the ODE database. This is
only</span>
+<span class="c"># used if the "ode-jbi.db.mode" property is set to
"EXTERNAL"</span>
+<span class="na">ode-jbi.db.ext.dataSource</span><span class="o">=</span><span
class="s">java:comp/env/jdbc/ode</span>
+
+<span class="c"># Embedded Database Name [String]</span>
+<span class="c"># Name of the embedded Derby database. This is only used if
the</span>
+<span class="c"># "ode-jbi.db.mode" property is set to
"EMBEDDED".</span>
+<span class="c">#ode-jbi.db.emb.name=hibdb</span>
+<span class="c">#ode-jbi.db.emb.name=jpadb</span>
+
+<span class="c"># Internal Database Configuration using Tranql Vendor
packages</span>
+<span class="c">#For MySQL</span>
+<span class="c">#ode-jbi.db.int.mcf=org.tranql.connector.mysql.XAMCF</span>
+<span class="c">#ode-jbi.db.int.mcf.databaseName=ODE</span>
+<span class="c">#ode-jbi.db.int.mcf.userName=root</span>
+<span class="c">#ode-jbi.db.int.mcf.password=root</span>
+<span class="c">#ode-jbi.db.int.mcf.serverName=localhost</span>
+
+<span class="c">#For Postgres</span>
+<span
class="c">#ode-jbi.db.int.mcf=org.tranql.connector.postgresql.PGXAMCF</span>
+<span class="c">#ode-jbi.db.int.mcf.databaseName=ODE</span>
+<span class="c">#ode-jbi.db.int.mcf.userName=postgres</span>
+<span class="c">#ode-jbi.db.int.mcf.password=postgres</span>
+<span class="c">#ode-jbi.db.int.mcf.serverName=localhost</span>
+
+<span class="c">#For SQLServer</span>
+<span class="c">#ode-jbi.db.int.mcf=org.tranql.connector.sqlserver.XAMCF</span>
+<span class="c">#ode-jbi.db.int.mcf.databaseName=ODE</span>
+<span class="c">#ode-jbi.db.int.mcf.userName=sa</span>
+<span class="c">#ode-jbi.db.int.mcf.password=sa</span>
+<span class="c">#ode-jbi.db.int.mcf.portNumber=1433</span>
+<span class="c">#ode-jbi.db.int.mcf.serverName=localhost</span>
+
+<span class="c">#For Oracle</span>
+<span class="na">ode-jbi.db.int.mcf</span><span class="o">=</span><span
class="s">org.tranql.connector.oracle.LocalMCF</span>
+<span class="na">ode-jbi.db.int.mcf.databaseName</span><span
class="o">=</span><span class="s">XE</span>
+<span class="na">ode-jbi.db.int.mcf.userName</span><span
class="o">=</span><span class="s">ODE</span>
+<span class="na">ode-jbi.db.int.mcf.password</span><span
class="o">=</span><span class="s">ode</span>
+<span class="na">ode-jbi.db.int.mcf.portNumber</span><span
class="o">=</span><span class="s">1521</span>
+<span class="na">ode-jbi.db.int.mcf.serverName</span><span
class="o">=</span><span class="s">localhost</span>
+<span class="na">ode-jbi.db.int.mcf.driverType</span><span
class="o">=</span><span class="s">thin</span>
+
+<span class="c"># Internal Database Configuration using generic
JDBCDriverMCF</span>
+<span
class="c">#ode-jbi.db.int.jdbcurl=jdbc:mysql://localhost/ode?user=sa</span>
+<span class="c">#ode-jbi.db.int.driver=com.mysql.jdbc.Driver</span>
+
+<span class="c"># DAO Connection Factory class.</span>
+<span class="c"># uncomment the following for hibernate.</span>
+<span
class="c">#ode-jbi.dao.factory=org.apache.ode.daohib.bpel.BpelDAOConnectionFactoryImpl</span>
+
+<span class="c"># BPEL Event Listener</span>
+<span class="c"># Uncomment the following for a debug output of BPEL
navigation events.</span>
+<span
class="c">#ode-jbi.event.listeners=org.apache.ode.bpel.common.evt.DebugBpelEventListener</span>
+<span class="c">#debugeventlistener.dumpToStdOut=on/off</span>
-<span class="c1">#Executor pool size</span>
-<span class="n">ode</span><span class="o">-</span><span
class="n">jbi</span><span class="o">.</span><span class="n">threads</span><span
class="o">.</span><span class="n">pool</span><span class="o">.</span><span
class="n">size</span><span class="o">=</span><span class="mi">100</span>
+<span class="c">#Executor pool size</span>
+<span class="na">ode-jbi.threads.pool.size</span><span class="o">=</span><span
class="s">100</span>
</pre></div>
<p><a name="ODEJbiandAxis2propertiesoverview-ode-axis2.properties"></a></p>
<h2 id="ode-axis2properties">ode-axis2.properties</h2>
<p>To configure those properties, please put ode-axis2.properties file in
webapps/ode/WEB-INF/conf directory. </p>
-<div class="codehilite"><pre><span class="c1"># HTTP connection pool used to
invoke external services</span>
-<span class="n">ode</span><span class="o">-</span><span
class="n">axis2</span><span class="o">.</span><span class="n">http</span><span
class="o">.</span><span class="n">connection</span><span
class="o">-</span><span class="n">manager</span><span class="o">.</span><span
class="n">max</span><span class="o">-</span><span class="n">per</span><span
class="o">-</span><span class="n">host</span><span class="o">=</span><span
class="mi">100</span>
-<span class="n">ode</span><span class="o">-</span><span
class="n">axis2</span><span class="o">.</span><span class="n">http</span><span
class="o">.</span><span class="n">connection</span><span
class="o">-</span><span class="n">manager</span><span class="o">.</span><span
class="n">max</span><span class="o">-</span><span class="n">total</span><span
class="o">=</span><span class="mi">100</span>
-
-<span class="c1"># Process dehydration</span>
-<span class="n">ode</span><span class="o">-</span><span
class="n">axis2</span><span class="o">.</span><span
class="n">process</span><span class="o">.</span><span
class="n">dehydration</span><span class="o">=</span><span class="n">true</span>
-
-<span class="c1"># Transaction factory</span>
-<span
class="c1">#ode-axis2.tx.factory.class=org.apache.ode.axis2.util.GeronimoFactory</span>
-<span
class="c1">#ode-axis2.tx.factory.class=org.apache.ode.axis2.util.JBossFactory</span>
-<span
class="c1">#ode-axis2.tx.factory.class=org.apache.ode.axis2.util.TomcatFactory</span>
-
-<span class="c1"># Used to redirect traffic to localhost instead of routing
again via load balancer in clustered environment</span>
-<span class="n">ode</span><span class="o">-</span><span
class="n">axis2</span><span class="o">.</span><span
class="n">cluster</span><span class="o">.</span><span
class="n">localRoute</span><span class="o">.</span><span
class="n">targets</span><span class="o">=</span><span
class="n">http:</span><span class="sr">//m</span><span
class="n">yloadbalancer</span><span class="o">.</span><span
class="n">com:8080</span><span class="sr">/ode/</span><span
class="n">processes</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">cluster</span><span class="o">.</span><span
class="n">localRoute</span><span class="o">.</span><span
class="n">base</span><span class="o">=</span><span class="n">http:</span><span
class="sr">//</span><span class="n">localhost:8888</span><span
class="sr">/ode/</span><span class="n">processes</span><span class="o">/</span>
+<div class="codehilite"><pre><span class="c"># HTTP connection pool used to
invoke external services</span>
+<span class="na">ode-axis2.http.connection-manager.max-per-host</span><span
class="o">=</span><span class="s">100</span>
+<span class="na">ode-axis2.http.connection-manager.max-total</span><span
class="o">=</span><span class="s">100</span>
+
+<span class="c"># Process dehydration</span>
+<span class="na">ode-axis2.process.dehydration</span><span
class="o">=</span><span class="s">true</span>
+
+<span class="c"># Transaction factory</span>
+<span
class="c">#ode-axis2.tx.factory.class=org.apache.ode.axis2.util.GeronimoFactory</span>
+<span
class="c">#ode-axis2.tx.factory.class=org.apache.ode.axis2.util.JBossFactory</span>
+<span
class="c">#ode-axis2.tx.factory.class=org.apache.ode.axis2.util.TomcatFactory</span>
+
+<span class="c"># Used to redirect traffic to localhost instead of routing
again via load balancer in clustered environment</span>
+<span class="na">ode-axis2.cluster.localRoute.targets</span><span
class="o">=</span><span
class="s">http://myloadbalancer.com:8080/ode/processes/</span>
+<span class="na">ode-axis2.cluster.localRoute.base</span><span
class="o">=</span><span class="s">http://localhost:8888/ode/processes/</span>
</pre></div>
@@ -186,26 +186,26 @@
<h2 id="ode-jbiproperties">ode-jbi.properties</h2>
<p>For JBI distribution, those properties are zipped into Service Assembly.
For SMX4 OSGi bundle distribution, those are in
SMX4/etc/org.apache.ode.jbi.cfg file. </p>
-<div class="codehilite"><pre><span class="c1"># Process Identifier Namespace
[QNAME]</span>
-<span class="c1"># Namespace for processes created using the JBI
integration.</span>
-<span class="c1"># This will be the namespace of the process identifiers
(PIDs)</span>
-<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="c1"># Allow Incomplete Deployment
("true","false")</span>
-<span class="c1"># Should incomplete deployments be allowed? An incomplete
deployment</span>
-<span class="c1"># arises when a service unit contains multiple processes and
not all</span>
-<span class="c1"># of the processes can be deployed. If incomplete deployments
are</span>
-<span class="c1"># allowed (true), the service unit will report success if any
of the</span>
-<span class="c1"># processes can be deployed. If not allowed (false), a
failure in</span>
-<span class="c1"># one process will prevent all processes from being
deployed.</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="c1"># Class name of the message mapper that should be used to
convert message</span>
-<span class="c1"># between ODE / NMS.</span>
-<span class="c1"># org.apache.ode.jbi.msgmap.JbiWsdl11WrapperMapper - use JBI
WSDL 1.1 "wrapped"</span>
-<span class="c1"># org.apache.ode.jbi.msgmap.ServiceMixMapper</span>
-<span class="c1"># org.apache.ode.jbi.msgmap.DocLitMapper</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>
+<div class="codehilite"><pre><span class="c"># Process Identifier Namespace
[QNAME]</span>
+<span class="c"># Namespace for processes created using the JBI
integration.</span>
+<span class="c"># This will be the namespace of the process identifiers
(PIDs)</span>
+<span class="na">ode-jbi.pidNamespace</span><span class="o">=</span><span
class="s">urn:ode-jbi</span>
+
+<span class="c"># Allow Incomplete Deployment
("true","false")</span>
+<span class="c"># Should incomplete deployments be allowed? An incomplete
deployment</span>
+<span class="c"># arises when a service unit contains multiple processes and
not all</span>
+<span class="c"># of the processes can be deployed. If incomplete deployments
are</span>
+<span class="c"># allowed (true), the service unit will report success if any
of the</span>
+<span class="c"># processes can be deployed. If not allowed (false), a failure
in</span>
+<span class="c"># one process will prevent all processes from being
deployed.</span>
+<span class="na">ode-jbi.allowIncompleteDeployment</span><span
class="o">=</span><span class="s">false</span>
+
+<span class="c"># Class name of the message mapper that should be used to
convert message</span>
+<span class="c"># between ODE / NMS.</span>
+<span class="c"># org.apache.ode.jbi.msgmap.JbiWsdl11WrapperMapper - use JBI
WSDL 1.1 "wrapped"</span>
+<span class="c"># org.apache.ode.jbi.msgmap.ServiceMixMapper</span>
+<span class="c"># org.apache.ode.jbi.msgmap.DocLitMapper</span>
+<span class="na">ode-jbi.messageMapper</span><span class="o">=</span><span
class="s">org.apache.ode.jbi.msgmap.ServiceMixMapper</span>
</pre></div>
</div>
</div>
Modified: websites/staging/ode/trunk/content/sitemap.html
==============================================================================
--- websites/staging/ode/trunk/content/sitemap.html (original)
+++ websites/staging/ode/trunk/content/sitemap.html Mon Dec 31 15:49:22 2012
@@ -124,7 +124,7 @@
<li><a href="/management-api.html">Management API</a></li>
<li><a href="/message-exchange.html">message exchange</a></li>
<li><a href="/ode-execution-events.html">ODE Execution Events</a></li>
-<li><a href="/ode-jbi-and-axis2-properties-overview.html">ODE Jbi and Axis2
properties overview</a></li>
+<li><a href="/ode-jbi-and-axis2-properties-overview.html">ODE JBI and Axis2
properties overview</a></li>
<li><a href="/ode-schema.html">ODE Schema</a></li>
<li><a href="/pick.html">pick</a></li>
<li><a href="/process-versioning.html">Process Versioning</a></li>
Modified: websites/staging/ode/trunk/content/wsdl-11-http-binding-support.html
==============================================================================
--- websites/staging/ode/trunk/content/wsdl-11-http-binding-support.html
(original)
+++ websites/staging/ode/trunk/content/wsdl-11-http-binding-support.html Mon
Dec 31 15:49:22 2012
@@ -28,7 +28,7 @@
<li class="">
<a href="/getting-ode.html">Getting ODE</a>
</li>
- <li class=" dropdown">
+ <li class="active dropdown">
<a href="/user-guide.html" class="dropdown-toggle"
data-toggle="dropdown" data-target="#">Documentation<b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="/userguide/">User Guide</a></li>
@@ -83,7 +83,8 @@
<div class="row">
<div class="span12">
- <p>Since version <a href="getting-ode.html">1.2</a>, ODE supports <a
href="http://www.w3.org/TR/wsdl#_http";>HTTP Binding</a>. ODE is almost fully
compliant with the WSDL 1.1 spec. The few limitations are related to MIME
types.
+ <h2 id="http-binding">HTTP Binding</h2>
+<p>Since version <a href="getting-ode.html">1.2</a>, ODE supports <a
href="http://www.w3.org/TR/wsdl#_http";>HTTP Binding</a>. ODE is almost fully
compliant with the WSDL 1.1 spec. The few limitations are related to MIME
types.
Actually only the following <a
href="http://www.iana.org/assignments/media-types/";>MIME types</a> are
supported:
1. Media types that represent <a
href="http://www.rfc-editor.org/rfc/rfc3023.txt";>XML MIME entities</a>.
Basically any types matching <code>"text/xml"</code>,
<code>"application/xml"</code> and <code>"\*+xml"</code>.
1. Non-XML types will be processed as Text, thus Text Media Types comes de
facto but they may have a very limited set of usages.</p>
![http://ode.apache.org/img/ode-logo.png"](http://ode.apache.org/img/ode-logo.png"){kind=link}