Author: jeff.yuchang
Date: 2010-09-21 23:04:30 -0400 (Tue, 21 Sep 2010)
New Revision: 970
Added:
trunk/docs/docbook/userguide/src/main/images/riftsaw-cluster.jpg
trunk/docs/docbook/userguide/src/main/module/clustering.xml
Modified:
trunk/docs/docbook/gettingstartedguide/src/main/module/installation.xml
trunk/docs/docbook/userguide/src/main/master.xml
trunk/runtime/clustering/src/main/java/org/jboss/soa/bpel/clustering/ODEJobClusterListener.java
Log:
* Added clustering userguide, and a cross pointer at gettingstartedguide.
Modified: trunk/docs/docbook/gettingstartedguide/src/main/module/installation.xml
===================================================================
--- trunk/docs/docbook/gettingstartedguide/src/main/module/installation.xml 2010-09-22
01:18:43 UTC (rev 969)
+++ trunk/docs/docbook/gettingstartedguide/src/main/module/installation.xml 2010-09-22
03:04:30 UTC (rev 970)
@@ -83,6 +83,7 @@
<para>
Unpack the RiftSaw distribution into a location alongside the JBossAS installation.
</para>
+
<para>
<itemizedlist>
<listitem>
@@ -102,13 +103,22 @@
the list of options for update of the web service stack is discussed in the one
following it.
</para>
<note>
- <para>
- Please note that RiftSaw should not be deployed while JBoss AS is running.
- </para>
+ <para>
+ Please note that RiftSaw should not be deployed while JBoss AS is running.
+ </para>
</note>
</listitem>
</itemizedlist>
</para>
+
+ <para>
+ <tip>
+ The above installation steps are meant to be for riftsaw single server deployment,
if you want to deploy riftsaw that supports clustering, you either need to specify
+ the JBoss AS instance as 'all' config, or add
'-Dclustering.support=true' in the command line. For detail, please refer to
<filename>userGuide</filename>'s RiftSaw Clustering Support chapter.
+ </tip>
+ </note>
+ </para>
+
</listitem>
</orderedlist>
Added: trunk/docs/docbook/userguide/src/main/images/riftsaw-cluster.jpg
===================================================================
(Binary files differ)
Property changes on: trunk/docs/docbook/userguide/src/main/images/riftsaw-cluster.jpg
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Modified: trunk/docs/docbook/userguide/src/main/master.xml
===================================================================
--- trunk/docs/docbook/userguide/src/main/master.xml 2010-09-22 01:18:43 UTC (rev 969)
+++ trunk/docs/docbook/userguide/src/main/master.xml 2010-09-22 03:04:30 UTC (rev 970)
@@ -17,5 +17,6 @@
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
href="module/wsconfig.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
href="module/uddi.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
href="module/esb.xml"/>
+ <xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
href="module/clustering.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
href="module/db.xml"/>
</book>
Added: trunk/docs/docbook/userguide/src/main/module/clustering.xml
===================================================================
--- trunk/docs/docbook/userguide/src/main/module/clustering.xml
(rev 0)
+++ trunk/docs/docbook/userguide/src/main/module/clustering.xml 2010-09-22 03:04:30 UTC
(rev 970)
@@ -0,0 +1,52 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<chapter id="clustering">
+<title>RiftSaw Clustering Support</title>
+
+ <section>
+ <title> Overview </title>
+ <para>
+ In order to make riftsaw to be able to work in a clustering environment, it has to be
configured to a shared database for
+ all the nodes that among the clustering environment, because riftsaw persists all of
process states into database. For the frontend,
+ it needs a load balancer to dispatch the soap message into nodes properly.Below is the
picture of riftsaw server deployment architecture for clustering.
+ </para>
+
+ <imageobject>
+ <imagedata fileref="images/riftsaw-cluster.jpg"/>
+ </imageobject>
+ </section>
+
+ <section>
+ <title>Installation</title>
+
+ <para>
+ In the $riftsaw/install folder, if you set the <emphasis
>org_jboss_as_config=all</emphasis> in the
<filename>deployment.properties</filename>,
+ it will deployed riftsaw-clustering libraries and files into JBoss AS. If you want to
deploy the riftsaw clustering feature into other config, say like you copied 'all'
into 'node1',
+ you can run the following command, (which basically added
'-Dclustering.support=true').
+ </para>
+ <para>
+ <command>ant deploy -Dclustering.support=true</command>
+ </para>
+ </section>
+
+ <section>
+ <title>Deployment</title>
+
+ <para>
+ Deploying bpel artifact in clustering environment is different from deploying it into a
single server.
+ You have to copy your bpel artifact (say hello_world.jar) into
<filename>$JBossAS/server/$config (like all)/farm/</filename>,
+ any artifacts deployed in this folder will be copied into all nodes that in the
clustering environment.
+ </para>
+ </section>
+
+ <section>
+ <title>Bpel Process Service Invocation</title>
+
+ <para>
+ For the bpel service that you deployed in the clustering environment, if you want to
invoke that service, you should be specifying the <emphasis>load balancer's
url</emphasis>
+ instead of the soap address that you specified in the wsdl file.
+ </para>
+ </section>
+
+</chapter>
\ No newline at end of file
Modified:
trunk/runtime/clustering/src/main/java/org/jboss/soa/bpel/clustering/ODEJobClusterListener.java
===================================================================
---
trunk/runtime/clustering/src/main/java/org/jboss/soa/bpel/clustering/ODEJobClusterListener.java 2010-09-22
01:18:43 UTC (rev 969)
+++
trunk/runtime/clustering/src/main/java/org/jboss/soa/bpel/clustering/ODEJobClusterListener.java 2010-09-22
03:04:30 UTC (rev 970)
@@ -99,6 +99,7 @@
nodeLists.add(node);
}
((ClusterAware)scheduler).setNodeList(nodeLists);
+ logger.info("The available nodes now are " + nodeLists);
}
}