Author: buildbot
Date: Mon Dec 31 15:26:02 2012
New Revision: 844415
Log:
Staging update by buildbot for ode
Modified:
websites/staging/ode/trunk/content/ (props changed)
websites/staging/ode/trunk/content/bpel-management-api-specification.html
websites/staging/ode/trunk/content/creating-a-process.html
websites/staging/ode/trunk/content/jbi-deployment.html
websites/staging/ode/trunk/content/management-api.html
websites/staging/ode/trunk/content/process-versioning.html
websites/staging/ode/trunk/content/sitemap.html
websites/staging/ode/trunk/content/smx4-osgi-deployment.html
websites/staging/ode/trunk/content/upgrading-ode.html
websites/staging/ode/trunk/content/war-deployment.html
Propchange: websites/staging/ode/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Dec 31 15:26:02 2012
@@ -1 +1 @@
-1427093
+1427148
Modified:
websites/staging/ode/trunk/content/bpel-management-api-specification.html
==============================================================================
--- websites/staging/ode/trunk/content/bpel-management-api-specification.html
(original)
+++ websites/staging/ode/trunk/content/bpel-management-api-specification.html
Mon Dec 31 15:26:02 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/creating-a-process.html
==============================================================================
--- websites/staging/ode/trunk/content/creating-a-process.html (original)
+++ websites/staging/ode/trunk/content/creating-a-process.html Mon Dec 31
15:26:02 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,11 +83,13 @@
<div class="row">
<div class="span12">
- <div class="toc">
+ <h2 id="overview">Overview</h2>
+<div class="toc">
<ul>
+<li><a href="#overview">Overview</a></li>
<li><a href="#deploying-a-process-in-ode">Deploying a Process in ODE</a></li>
<li><a href="#deployment-descriptor">Deployment Descriptor</a></li>
-<li><a href="#formal-definition">Formal definition</a><ul>
+<li><a href="#formal-definition">Formal definition</a></li>
<li><a href="#examples">Examples</a></li>
<li><a href="#additional-settings">Additional settings</a><ul>
<li><a href="#in-memory-execution">In memory execution</a></li>
@@ -95,32 +97,30 @@
</ul>
</li>
</ul>
-</li>
-</ul>
</div>
<p><a name="CreatingaProcess-DeployingaProcessinOde"></a></p>
-<h3 id="deploying-a-process-in-ode">Deploying a Process in ODE</h3>
+<h2 id="deploying-a-process-in-ode">Deploying a Process in ODE</h2>
<p>Each deployment is a directory with all relevant deployment artifacts. At
the minimum it will contain the deployment descriptor, one or more process
definitions (BPEL or .cbp), WSDL and XSDs (excluding those compiled into the
.cbp). It may also contain other files, such as SVGs or XSLs. The deployment
descriptor is a file named deploy.xml (see the next paragraoh for its
description).</p>
<p>During deployment, the process engine loads all documents from the
deployment descriptor. Loading documents allow it to reference processes,
service and schema definitions using fully qualified names, and import based on
namespaces instead of locations.</p>
-<p>To deploy in ODE, just copy the whole directory containing your artifacts
(the directory itself, not only its content) in the path
%DEPLOYMENT_ROOT%/WEB-INF/processes (in Tomcat it would be
%TOMCAT_HOME%/webapps/ode/WEB-INF/processes).</p>
+<p>To deploy in ODE, just copy the whole directory containing your artifacts
(the directory itself, not only its content) in the path
<code>%DEPLOYMENT_ROOT%/WEB-INF/processes</code> (in Tomcat it would be
<code>%TOMCAT_HOME%/webapps/ode/WEB-INF/processes</code>).</p>
<p><a name="CreatingaProcess-DeploymentDescriptor"></a></p>
-<h3 id="deployment-descriptor">Deployment Descriptor</h3>
+<h2 id="deployment-descriptor">Deployment Descriptor</h2>
<p>To deploy your process in ODE you will need to create a simple deployment
descriptor with basic information. The deploy.xml file configures one or
several processes to use specific services. For each process, deploy.xml must
supply binding information for partner links to concrete WSDL services. Every
partner link used with a <receive> activity must be matched with a <provide>
element, and every partnerLink used in an <invoke> activity must be matched
with an <invoke> element in <em>deploy.xml</em> (unless that partnerLink has
initializePartnerRole="false").</p>
<p><a name="CreatingaProcess-Formaldefinition"></a></p>
-<h3 id="formal-definition">Formal definition</h3>
+<h2 id="formal-definition">Formal definition</h2>
<p>The XML schema describing ODE's deployment descriptor is available <a
href="http://svn.apache.org/viewvc/ode/trunk/bpel-schemas/src/main/xsd/dd.xsd?view=markup";>here</a>.
The root element, deploy, contains a list of all deployed processes from the
deployment directory:</p>
<div class="codehilite"><pre><span class="nt"><deploy></span>
- <span class="nt"><process</span> <span class="err">...</span><span
class="nt">></span>*
- { other elements }
- <span class="nt"></process></span>
+ <span class="nt"><process</span> <span class="err">...</span><span
class="nt">></span>*
+ { other elements }
+ <span class="nt"></process></span>
<span class="nt"></deploy></span>
</pre></div>
<p>Each process is identified by its qualified name and specifies bindings for
provided and invoked services:</p>
<div class="codehilite"><pre><span class="nt"><process</span> <span
class="na">name =</span> <span class="s">QName</span> <span
class="na">fileName =</span> <span class="s">String?</span> <span
class="na">bpel11wsdlFileName =</span> <span class="s">String?</span> <span
class="nt">></span>
- (<span class="nt"><provide></span> | <span
class="nt"><invoke></span>)*
- { other elements }
+ (<span class="nt"><provide></span> | <span
class="nt"><invoke></span>)*
+ { other elements }
<span class="nt"></process></span>
</pre></div>
@@ -128,7 +128,7 @@
<p>Each process element must provide a <code>name</code> attribute with the
qualified name of the process. Optionally, a <code>fileName</code> attribute
can be used to specify the location of the BPEL process definition (the .bpel
file). The <code>fileName</code> attribute does not need to be provided unless
non-standard compilation options are used or the
<code>bpel11wsdlFileName</code> attribute is used to specify a WSDL document
for a BPEL 1.1 process. </p>
<p>Each <code><process></code> element must enumerate the services
provided by the process and bind each service to an endpoint. This is done
through <code><provide></code> elements which associates
<code>partnerLink</code>s with <code>endpoint</code>s:</p>
<div class="codehilite"><pre><span class="nt"><provide</span> <span
class="na">partnerLink=</span><span class="s">NCName</span><span
class="nt">></span>
- <span class="nt"><service</span> <span class="na">name =</span> <span
class="s">QName</span> <span class="na">port =</span> <span
class="s">NCName?</span><span class="nt">></span>
+ <span class="nt"><service</span> <span class="na">name =</span> <span
class="s">QName</span> <span class="na">port =</span> <span
class="s">NCName?</span><span class="nt">></span>
<span class="nt"></provide></span>
</pre></div>
@@ -136,7 +136,7 @@
<p>Note, that only one partnerLink can be bound to any specified endpoint.</p>
<p>The port attribute can be used to select a particular endpoint from the
service definition.</p>
<p><a name="CreatingaProcess-Examples"></a></p>
-<h4 id="examples">Examples</h4>
+<h2 id="examples">Examples</h2>
<p>A very simple process that would only be invoked would use a deploy.xml
very similar to:</p>
<div class="codehilite"><pre><span class="nt"><deploy</span> <span
class="na">xmlns=</span><span
class="s">"http://www.apache.org/ode/schemas/dd/2007/03"</span>
<span class="na">xmlns:pns=</span><span
class="s">"http://ode/bpel/unit-test"</span> <span
class="na">xmlns:wns=</span><span
class="s">"http://ode/bpel/unit-test.wsdl"</span><span
class="nt">></span>
@@ -167,7 +167,7 @@
<span class="nt"></invoke></span>
<span class="nt"></process></span>
<span class="nt"><process</span> <span class="na">name=</span><span
class="s">"resp:MagicSessionResponder"</span><span
class="nt">></span>
- <span
class="nt"><type></span>resp:MagicSessionResponder<span
class="nt"></type></span>
+ <span class="nt"><type></span>resp:MagicSessionResponder<span
class="nt"></type></span>
<span class="nt"><provide</span> <span
class="na">partnerLink=</span><span
class="s">"mainPartnerLink"</span><span class="nt">></span>
<span class="nt"><service</span> <span
class="na">name=</span><span
class="s">"mws:MSResponderService"</span> <span
class="na">port=</span><span class="s">"MSResponderPort"</span><span
class="nt">/></span>
<span class="nt"></provide></span>
@@ -181,9 +181,9 @@
<p>See the complete example <a
href="https://svn.apache.org/repos/asf/ode/trunk/distro-axis2/src/examples/MagicSession/";>here</a>.</p>
<p><a name="CreatingaProcess-Additionalsettings"></a></p>
-<h4 id="additional-settings">Additional settings</h4>
+<h2 id="additional-settings">Additional settings</h2>
<p><a name="CreatingaProcess-Inmemoryexecution"></a></p>
-<h5 id="in-memory-execution">In memory execution</h5>
+<h3 id="in-memory-execution">In memory execution</h3>
<p>For performance purposes, you can define a process as being executed only
in-memory. This greatly reduces the amount of generated queries and puts far
less load on your database. Both persistent and non-persistent processes can
cohabit in ODE.</p>
<p>To declare a process as in-memory just add an in-memory element in your
deploy.xml:</p>
<div class="codehilite"><pre><span class="nt"><process</span> <span
class="na">name=</span><span class="s">"pns:HelloWorld2"</span><span
class="nt">></span>
@@ -197,13 +197,13 @@
<p>Be aware that in-memory executions introduces many restrictions on your
process and what it can do. The instances of these processes can't be queried
by using the <a href="management-api.html">Management API</a>. The process
definition can only include one single receive activity (the one that will
trigger the instance creation).</p>
<p><a name="CreatingaProcess-User-definedprocessproperties"></a></p>
-<h5 id="user-defined-process-properties">User-defined process properties</h5>
+<h3 id="user-defined-process-properties">User-defined process properties</h3>
<p>User-defined process properties provide means to configure process models
and their instances. They are either statically declared and set in the
deployment descriptor <code>deploy.xml</code> or can be set using the process
management API. All instances of a process model share the same set of process
properties. If a process property changes, it changes for all instances.</p>
<p>A process property is identified by a QName and can carry a string as
value. To set a process property statically in the deployment descriptor, add
the following snippet to your <code>deploy.xml</code>:</p>
<div class="codehilite"><pre><span class="nt"><process</span> <span
class="na">name=</span><span class="s">"pns:HelloWorld2"</span><span
class="nt">></span>
- ...
- <span class="nt"><property</span> <span
class="na">xmlns:loan=</span><span class="s">"urn:example"</span>
<span class="na">name=</span><span
class="s">"loan:loanThreshold"</span><span
class="nt">></span>4711<span class="nt"></property></span>
- ...
+ ...
+ <span class="nt"><property</span> <span
class="na">xmlns:loan=</span><span class="s">"urn:example"</span>
<span class="na">name=</span><span
class="s">"loan:loanThreshold"</span><span
class="nt">></span>4711<span class="nt"></property></span>
+ ...
<span class="nt"></process></span>
</pre></div>
@@ -216,10 +216,10 @@
<p>To read process properties in a BPEL process, you can use the non-standard
XPath extension <code>bpws:process-property(propertyName)</code>, e.g. in a
transition condition or in an assign activity:</p>
<div class="codehilite"><pre>...
<span class="nt"><assign></span>
- <span class="nt"><copy></span>
- <span class="nt"><from</span> <span class="na">xmlns:loan=</span><span
class="s">"urn:example"</span><span
class="nt">></span>bpws:process-property(loan:loanThreshold)<span
class="nt"></from></span>
- <span class="nt"><to></span><span class="p">$</span><span
class="nv">threshold</span><span class="nt"></to></span>
- <span class="nt"></copy></span>
+ <span class="nt"><copy></span>
+ <span class="nt"><from</span> <span
class="na">xmlns:loan=</span><span
class="s">"urn:example"</span><span
class="nt">></span>bpws:process-property(loan:loanThreshold)<span
class="nt"></from></span>
+ <span class="nt"><to></span><span class="p">$</span><span
class="nv">threshold</span><span class="nt"></to></span>
+ <span class="nt"></copy></span>
<span class="nt"></assign></span>
...
</pre></div>
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 31 15:26:02
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,7 +84,7 @@
<div class="row">
<div class="span12">
<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>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>
<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>
Modified: websites/staging/ode/trunk/content/management-api.html
==============================================================================
--- websites/staging/ode/trunk/content/management-api.html (original)
+++ websites/staging/ode/trunk/content/management-api.html Mon Dec 31 15:26:02
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/process-versioning.html
==============================================================================
--- websites/staging/ode/trunk/content/process-versioning.html (original)
+++ websites/staging/ode/trunk/content/process-versioning.html Mon Dec 31
15:26:02 2012
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<html>
<head>
- <title>Apache ODE – Process Versioning *
[Introduction](#ProcessVersioning-Introduction) * [How Versioning
Works](#ProcessVersioning-HowVersioningWorks) * [Process Versioning in
ODE](#ProcessVersioning-ProcessVersioninginOde) * [Remote Deployment vs.
Hand-Made
Deployment](#ProcessVersioning-RemoteDeploymentvs.Hand-MadeDeployment)</title>
+ <title>Apache ODE – Process Versioning</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>Process Versioning *
[Introduction](#ProcessVersioning-Introduction) * [How Versioning
Works](#ProcessVersioning-HowVersioningWorks) * [Process Versioning in
ODE](#ProcessVersioning-ProcessVersioninginOde) * [Remote Deployment vs.
Hand-Made
Deployment](#ProcessVersioning-RemoteDeploymentvs.Hand-MadeDeployment)</h1>
+ <h1>Process Versioning</h1>
</div>
</header>
@@ -84,7 +84,19 @@
<div class="row">
<div class="span12">
<p><a name="ProcessVersioning-Introduction"></a></p>
-<h3 id="introduction">Introduction</h3>
+<h2 id="introduction">Introduction</h2>
+<div class="toc">
+<ul>
+<li><a href="#introduction">Introduction</a><ul>
+<li><a href="#how-versioning-works">How Versioning Works</a><ul>
+<li><a href="#process-versioning-in-ode">Process Versioning in ODE</a></li>
+<li><a href="#remote-deployment-vs-hand-made-deployment">Remote Deployment vs.
Hand-Made Deployment</a></li>
+</ul>
+</li>
+</ul>
+</li>
+</ul>
+</div>
<p>Before starting on what process versioning exactly does, let's see what the
world (or at least ODE) would be without versioning. It will be much more
easier for you to understand the solution after fully seeing the problem.</p>
<p>So you're starting using ODE and you've just designed you first business
process. It's all nice and dandy and works perfectly. It works so well that you
let your users start using it. It's not really production but you know, release
early, release often, so let's see what users think of it. After a couple of
days you realize that a couple of steps are missing, you add them in your
process and once again, it executes smoothly. So let's see what our users think
of the improvement! Next thing you know, your phone starts ringing and the user
on the other side is most likely pretty upset. What happened?</p>
<p>So when you start using a process, executions for it are created, running
processes if you like (also called process instances). Depending on the type of
your business these could take a variable amount of time to execute but they're
usually not instantaneous. So you have all these running processes sometimes
doing things, sometimes just waiting there and all of a sudden, a brand new
process definition replaces the original one all these executions have been
using so far. What is a process engine to do with all these executions? Well,
the most logic thing on earth: just nuke them all.</p>
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:26:02 2012
@@ -127,7 +127,7 @@
<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
href="#ProcessVersioning-Introduction">Introduction</a> * <a
href="#ProcessVersioning-HowVersioningWorks">How Versioning Works</a> * <a
href="#ProcessVersioning-ProcessVersioninginOde">Process Versioning in ODE</a>
* <a href="#ProcessVersioning-RemoteDeploymentvs.Hand-MadeDeployment">Remote
Deployment vs. Hand-Made Deployment</a></a></li>
+<li><a href="/process-versioning.html">Process Versioning</a></li>
<li><a href="/receive.html">receive</a></li>
<li><a href="/required-third-party-libraries.html">Required Third-Party
Libraries</a></li>
<li><a href="/resource-services.html">Resources & Services</a></li>
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 31
15:26:02 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>
@@ -96,44 +96,44 @@ features:install examples-ode-ping-pong
<p><a name="SMX4OSGiDeployment-Configuringdatabase"></a></p>
<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
+<div class="codehilite"><pre><span class="na">ode-jbi.pidNamespace</span><span
class="o">=</span><span class="s">urn:ode-jbi</span>
+<span class="na">ode-jbi.allowIncompleteDeployment</span><span
class="o">=</span><span class="s">false</span>
+<span class="na">ode-jbi.messageMapper</span><span class="o">=</span><span
class="s">org.apache.ode.jbi.msgmap.ServiceMixMapper</span>
+<span class="na">ode-jbi.event.listeners</span><span class="o">=</span><span
class="s">org.apache.ode.bpel.common.evt.DebugBpelEventListener</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>
-# Uncomment the following to enable hibernate (this is recommended for
production use):
-#ode-jbi.dao.factory=org.apache.ode.daohib.bpel.BpelDAOConnectionFactoryImpl
+<span class="c"># Uncomment the following to enable hibernate (this is
recommended for production use):</span>
+<span
class="c">#ode-jbi.dao.factory=org.apache.ode.daohib.bpel.BpelDAOConnectionFactoryImpl</span>
</pre></div>
@@ -151,12 +151,12 @@ So you need to run following command fro
<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 <code>etc/config.properties</code> and change from:</p>
-<div
class="codehilite"><pre>org.osgi.framework.bootdelegation=sun.*,com.sun*,javax.transaction,javax.transaction.*
+<div class="codehilite"><pre><span
class="na">org.osgi.framework.bootdelegation</span><span
class="o">=</span><span
class="s">sun.*,com.sun*,javax.transaction,javax.transaction.*</span>
</pre></div>
<p>to:</p>
-<div
class="codehilite"><pre>org.osgi.framework.bootdelegation=sun.*,com.sun*,javax.transaction,javax.transaction.*,javax.xml.stream,javax.xml.stream.*
+<div class="codehilite"><pre><span
class="na">org.osgi.framework.bootdelegation</span><span
class="o">=</span><span
class="s">sun.*,com.sun*,javax.transaction,javax.transaction.*,javax.xml.stream,javax.xml.stream.*</span>
</pre></div>
</div>
</div>
Modified: websites/staging/ode/trunk/content/upgrading-ode.html
==============================================================================
--- websites/staging/ode/trunk/content/upgrading-ode.html (original)
+++ websites/staging/ode/trunk/content/upgrading-ode.html Mon Dec 31 15:26:02
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">
- <div class="alert alert-note"><h4 class="alert-heading">You shall
backup</h4></div>
+ <h2 id="overview">Overview</h2>
+<div class="alert alert-note"><h4 class="alert-heading">You shall
backup</h4></div>
<p>ODE upgrade procedures usually consist in:</p>
<ul>
@@ -95,7 +96,7 @@
<li>copying all the previous configuration and deployed processes (with the
corresponding markers).</li>
</ul>
<h2 id="from-133-to-134">From 1.3.3 to 1.3.4</h2>
-<p>First, apply SQLs to denormalize LARGE_DATA table from here:
[https://issues.apache.org/jira/browse/ODE-694]</p>
+<p>First, apply SQLs to denormalize LARGE_DATA table from <a
href="https://issues.apache.org/jira/browse/ODE-694";>here</a></p>
<p>Then, please apply following updates:</p>
<div class="codehilite"><pre><span class="k">alter</span> <span
class="k">table</span> <span class="n">BPEL_XML_DATA</span> <span
class="k">add</span> <span class="n">SIMPLE_VALUE</span> <span
class="n">varchar2</span><span class="p">(</span><span
class="mi">255</span><span class="p">);</span>
@@ -119,7 +120,7 @@
<h2 id="from-132-to-133">From 1.3.2 to 1.3.3</h2>
<p>None</p>
<h2 id="from-12-to-132">From 1.2 to 1.3.2</h2>
-<p>If you're currently using ODE <em>1.2</em> and are upgrading to 1.3.2,
please run the following queries.</p>
+<p>If you're currently using ODE 1.2 and are upgrading to 1.3.2, please run
the following queries.</p>
<h3 id="for-openjpa-database-schema">For OpenJPA database schema</h3>
<div class="codehilite"><pre><span class="k">create</span> <span
class="k">table</span> <span class="n">ODE_SCHEMA_VERSION</span> <span
class="p">(</span><span class="k">VERSION</span> <span
class="nb">integer</span><span class="p">);</span>
<span class="k">insert</span> <span class="k">into</span> <span
class="n">ODE_SCHEMA_VERSION</span> <span class="k">values</span> <span
class="p">(</span><span class="mi">5</span><span class="p">);</span>
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 31 15:26:02
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,7 +90,7 @@
<p><a name="WARDeployment-Examples"></a></p>
<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>bin/sendsoap
http://localhost:8080/ode/processes/helloWorld
examples/HelloWorld2/testRequest.soap
+<div class="codehilite"><pre>$ bin/sendsoap
http://localhost:8080/ode/processes/helloWorld
examples/HelloWorld2/testRequest.soap
</pre></div>
@@ -124,8 +124,8 @@ $ mysql -u root ode < ode_openjpa_mys
</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>
-<div class="codehilite"><pre>ode-axis2.db.mode=EXTERNAL
-ode-axis2.db.ext.dataSource=java:comp/env/jdbc/ODEDB
+<div class="codehilite"><pre><span class="na">ode-axis2.db.mode</span><span
class="o">=</span><span class="s">EXTERNAL</span>
+<span class="na">ode-axis2.db.ext.dataSource</span><span
class="o">=</span><span class="s">java:comp/env/jdbc/ODEDB</span>
</pre></div>
@@ -133,14 +133,14 @@ ode-axis2.db.ext.dataSource=java:comp/en
</ol>
<p>You're done!</p>
<p><a
name="WARDeployment-ConfiguringODEinJBosswithJNDIEXTERNALdatasource"></a></p>
-<h2 id="configuring-ode-in-jboss-with-jndi-external-datasource">Configuring
ODE in JBoss with JNDI EXTERNAL datasource</h2>
+<h2 id="configuring-ode-in-jboss-with-external-jndi-datasource">Configuring
ODE in JBoss with external JNDI datasource</h2>
<p>Create ode/WEB-INF/conf/ode-axis2.properties with following content:</p>
-<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
+<div class="codehilite"><pre><span class="c">#Uncomment for using dao
hibernate</span>
+<span
class="c">#ode-axis2.dao.factory=org.apache.ode.daohib.bpel.BpelDAOConnectionFactoryImpl</span>
+<span class="na">ode-axis2.db.mode</span><span class="o">=</span><span
class="s">EXTERNAL</span>
+<span class="na">ode-axis2.db.ext.dataSource</span><span
class="o">=</span><span class="s">java:comp/env/jdbc/ode</span>
+<span class="na">ode-axis2.event.listeners</span><span class="o">=</span><span
class="s">org.apache.ode.bpel.common.evt.DebugBpelEventListener</span>
+<span class="na">ode-axis2.tx.factory.class</span><span
class="o">=</span><span class="s">org.apache.ode.axis2.util.JBossFactory</span>
</pre></div>
</div>
</div>
![http://ode.apache.org/img/ode-logo.png"](http://ode.apache.org/img/ode-logo.png"){kind=link}