From overlord-commits at lists.jboss.org Tue Dec 16 12:17:57 2008
Content-Type: multipart/mixed; boundary="===============2408110207430012641=="
MIME-Version: 1.0
From: overlord-commits at lists.jboss.org
To: overlord-commits at lists.jboss.org
Subject: [overlord-commits] Overlord SVN: r448 -
 cdl/trunk/docs/docbook/userguide/src/main/module.
Date: Tue, 16 Dec 2008 12:17:56 -0500
Message-ID: <E1LCdYS-0001QS-QX@committer01.frg.pub.inap.atl.jboss.com>

--===============2408110207430012641==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Author: objectiser
Date: 2008-12-16 12:17:56 -0500 (Tue, 16 Dec 2008)
New Revision: 448

Modified:
   cdl/trunk/docs/docbook/userguide/src/main/module/conversation-validation=
-with-cdl.xml
Log:
Updated user guide to include 'record only' service validator configuration.

Modified: cdl/trunk/docs/docbook/userguide/src/main/module/conversation-val=
idation-with-cdl.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- cdl/trunk/docs/docbook/userguide/src/main/module/conversation-validatio=
n-with-cdl.xml	2008-11-18 14:09:08 UTC (rev 447)
+++ cdl/trunk/docs/docbook/userguide/src/main/module/conversation-validatio=
n-with-cdl.xml	2008-12-16 17:17:56 UTC (rev 448)
@@ -4,9 +4,7 @@
 <chapter id=3D"conversationvalidationwithcdl">
 	<title>Conversation Validation with CDL</title>
 	<section>
-      	<title>Conversation Validation</title>
-		<section>
-			<title>Overview</title>
+      	<title>Overview</title>
 			<para>
 			Conversation validation is a form of runtime governance concerned with =
the dynamic behaviour of a system.
 		</para>
@@ -16,8 +14,7 @@
 		<para>
 This section introduces the choreography description language (CDL) define=
d by W3C, and the <emphasis>pi4soa</emphasis> open source project which pro=
vides an editor for creating choreography descriptions, as well as utilizin=
g these descriptions for runtime validation and execution purposes.
 =

-			</para>
-		</section>
+		</para>
 =

 	</section>
 =

@@ -205,7 +202,7 @@
 =

 		<para>
 		When the dialog box is displayed, either enter the path to the <filename=
>validator-config.xml</filename>
-		in the text field, or use the <emphasis>Browse</emphasis> button to loca=
te the file3
+		in the text field, or use the <emphasis>Browse</emphasis> button to loca=
te the file.
 		</para>
 =

 		<imageobject>
@@ -285,4 +282,66 @@
 If any <emphasis>out of sequence</emphasis> or other error situations aris=
e, these are displayed in red.
 		</para>
 	</section>
+
+	<section>
+		<title>Configuration for Conversation Recording</title>
+
+		<para>
+		As well as validating the interactions between a set of
+		services, against a pre-defined choreography description,
+		it is also possible to use the <emphasis>Service Validators</emphasis>
+		in a non-validating record mode.
+		</para>
+
+		<para>
+		This will be useful in situations where a choreography
+		description does not currently exist, and we wish to
+		use the stream of business events being sent and received
+		by each identified service (or participant type) to
+		gain an understanding of the current business process.
+		</para>
+
+		<para>
+		An example of this type of configuration, associated
+		with the TrailBlazer example, is:
+		</para>
+			<informalexample>
+  				<programlisting role=3D"XML" ><![CDATA[
+	<validator active=3D"true" >
+		<service participantType=3D"LoanBrokerParticipant" validate=3D"false" >
+			<output epr=3D"jms:queue/esb-tb-creditAgencyQueue" />
+			<input epr=3D"jms:queue/esb-tb-creditAgencyQueue_reply" />
+			<output epr=3D"jms:queue/esb-tb-jmsBankRequestQueue" />
+			<output epr=3D"jms:queue/esb-tb-fileBankRequestQueue" />
+			<input epr=3D"jms:queue/esb-tb-jmsBankResponseQueue" />
+			<output epr=3D"jms:queue/esb-tb-customerNotifier" />
+			<input epr=3D"jms:queue/esb-tb-fileBankResponseQueue" />
+		</service>
+		<service participantType=3D"CreditAgencyParticipant" validate=3D"false" >
+			<input epr=3D"jms:queue/esb-tb-creditAgencyQueue" />
+			<output epr=3D"jms:queue/esb-tb-creditAgencyQueue_reply" />
+		</service>
+		<service participantType=3D"BankParticipant" validate=3D"false" >
+			<input epr=3D"jms:queue/esb-tb-jmsBankRequestQueue" />
+			<input epr=3D"jms:queue/esb-tb-fileBankRequestQueue" />
+			<output epr=3D"jms:queue/esb-tb-jmsBankResponseQueue" />
+			<output epr=3D"jms:queue/esb-tb-fileBankResponseQueue" />
+		</service>
+		<service participantType=3D"NotifierParticipant" validate=3D"false" >
+			<input epr=3D"jms:queue/esb-tb-customerNotifier" />
+		</service>
+	</validator>
+ 				 ]]></programlisting>
+			</informalexample>
+
+		<para>
+		To define a <emphasis>Service Validator</emphasis> in record
+		only mode, the <emphasis>cdmFilePath</emphasis> attribute
+		is not specified (because no choreography description exists
+		to be validated against), and the optional <emphasis>validate</emphasis>
+		attribute should be set to <emphasis role=3D"bold">false</emphasis> (by =
default
+		this attribute is <emphasis role=3D"bold">true</emphasis>).
+		</para>
+	</section>
+
 </chapter>


--===============2408110207430012641==--