[jboss-svn-commits] JBL Code SVN: r34734 - labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Sun Aug 15 19:45:00 EDT 2010
Author: dlesage
Date: 2010-08-15 19:45:00 -0400 (Sun, 15 Aug 2010)
New Revision: 34734
Removed:
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Performance_Tuning.xml
Modified:
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Configuring_Examples.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Content_Based_Routing_Using_Drools.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Content_Based_Routing_Using_Smooks.xml
Log:
JBESB 3460
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Configuring_Examples.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Configuring_Examples.xml 2010-08-15 23:37:23 UTC (rev 34733)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Configuring_Examples.xml 2010-08-15 23:45:00 UTC (rev 34734)
@@ -12,23 +12,23 @@
</title>
<para>
- Study the examples in this section to learn about different registry
- configuration options.
+ Read this section to learn the
+ different ways in which the jUDDI registry can be configured.
</para>
<section>
<title>
- Embedding Components
+ Embedding
</title>
<para>
- All of those server components, (including the Enterprise
- Service Bus and Web Service) that have a relationship of
- any kind with the <systemitem>registry</systemitem> can
- share the latter between themselves. Indeed, multiple
- instances of the <application>JBoss Enterprise SOA
- Platform</application> can use the same
- <systemitem>registry</systemitem> via a shared database.
+ By embedding the registry, one allows server
+ components to share it.
+ In
+ fact, even multiple instances of the JBoss
+ Enterprise SOA Platform can share the same
+ registry.
+ Here is an illustration of the concept:
</para>
<figure>
@@ -40,65 +40,82 @@
</mediaobject>
</figure>
- <para>
- Properties example:
- </para>
-
+ <procedure>
+ <title>Embedding the jUDDI Registry</title>
+ <step>
+ <para>To embed the jUDDI Registry, set these properties</para>
<programlisting language="XML" role="XML"><xi:include href="extras/configuring_examples/embeddedjuddi.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
+ </step>
+ </procedure>
+
</section>
<section>
<title>
- Remote Method Invocation Using the jbossesb.sar File
+ Remote Method Invocation via the jbossesb.sar File
</title>
<para>
- This is a straightfoward process. Simply deploy a version of the
- jUDDI Registry that brings up a Remote Method Invocation
- service. (The JBoss Enterprise Service Bus deploys the Remote
- Method Invocation service by default: it starts the registry
+ The second configuration method is that of using Remote Method
+ Invocation. This is a straightfoward process. Here
+ is an illustration of the concept:
+ </para>
+
+ <figure>
+ <title>Remote Method Invocation</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/configuring_examples/chart17.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <procedure>
+ <title>Configuring the jUDDI Registry to Use Remote Method Invocation via the jbossesb.sar File</title>
+ <step>
+ <para>Simply deploy a version of
+ the jUDDI registry that brings up a Remote Method
+ Invocation service. (The JBoss Enterprise Service
+ Bus deploys the Remote Method Invocation service
+ by default: it starts the registry
within the <filename>jbossesb.sar</filename> archive. This same
- archive also registers an RMI service.)
- </para>
-
-<figure>
- <title>Remote Method Invocation</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/configuring_examples/chart17.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>
- Here are the properties:
- </para>
-
-<programlisting language="XML" role="XML"><xi:include href="extras/configuring_examples/reg1.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
-
- <para>
- The <filename>juddi.war</filename> is configured to bring up a
- RMI Service, this being triggered by the following setting in
- the <filename>web.xml</filename> file:
- </para>
+ archive also registers an RMI service.)</para>
+ <para>
+ These are the properties to set:
+ </para>
+
+ <programlisting language="XML" role="XML"><xi:include href="extras/configuring_examples/reg1.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
+ <para>
+ The <filename>juddi.war</filename> is configured to bring up a
+ RMI Service, this being triggered by the following setting in
+ the <filename>web.xml</filename> file:
+ </para>
-<programlisting language="XML" role="XML"><xi:include href="extras/configuring_examples/reg2.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
-
- <para>
- Include the following JNDI settings in
- <filename>juddi.properties</filename>:
- </para>
+ <programlisting language="XML" role="XML"><xi:include href="extras/configuring_examples/reg2.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
-<programlisting language="Java" role="JAVA"><xi:include href="extras/configuring_examples/reg3.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
-
- <important>
- <para>
- Remember to include <filename>scout-client.jar</filename> in the
- RMI client's class-path.
- </para>
- </important>
+
+ </step>
+
+
+<step>
+
+ <para>
+ Include the following JNDI settings in
+ <filename>juddi.properties</filename>:
+ </para>
+
+ <programlisting language="Java" role="JAVA"><xi:include href="extras/configuring_examples/reg3.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
+ <important>
+ <para>
+ Remember to include <filename>scout-client.jar</filename> in the
+ RMI client's class-path.
+ </para>
+ </important>
+
+</step>
+ </procedure>
</section>
@@ -111,9 +128,9 @@
<para>
If, for some reason, one does not to deploy the
- <filename>juddi.war</filename>, simply configure one of the
+ juddi.war, it is possible to simply configure one of the
Enterprise Service components running in the same Java Virtual
- Machine as <application>jUDDI</application> to register the RMI
+ Machine as the jUDDI registry to register the RMI
service:
</para>
@@ -126,44 +143,47 @@
</mediaobject>
</figure>
- <para>
- For Application One, local settings are needed:
- </para>
-
+
+ <procedure>
+ <title>Configuring RMI Using One's Own JNDI Registration</title>
+ <step>
+ <para> For Application One, configure these local
+ settings:</para>
<programlisting language="XML" role="XML"><xi:include parse="text" href="extras/configuring_examples/registry_config_example_2.xmlt" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
-
-
- <para>
- Application Two requires the Remote Method Invocation
- settings:
- </para>
-
- <programlisting language="XML" role="XML"><xi:include href="extras/configuring_examples/webxml.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
-
-
- <para>
- Point the hostnames of the
- <classname>queryManagerURI</classname> and
- <classname>lifeCycleManagerURI</classname> classes to
- the host on which jUDDI is running (this is also where
- Application One is running.) Obviously, Application One
- needs to have access to a naming service. To register
- it, undertake the following process:
- </para>
-
-
- <programlisting language="Java" role="JAVA"><xi:include href="extras/configuring_examples/properties.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
-
- <para>
- For example, make sure to include the following JNDI settings in the file
- <filename>jbossesb-registry.sar/esb.juddi.xml</filename>:
- </para>
-
+
+ </step>
+<step>
+ <para> For Application Two, configure the Remote Method
+ Invocation
+ settings:</para>
+ <programlisting language="XML" role="XML"><xi:include href="extras/configuring_examples/webxml.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
+</step>
+<step>
+ <para>
+ Point the hostnames of the
+ <classname>queryManagerURI</classname> and
+ <classname>lifeCycleManagerURI</classname> classes to
+ the host on which the jUDDI registry is running (this is also where
+ Application One is running.) Obviously, Application One
+ needs to have access to a naming service.
+ </para>
+</step>
+<step>
+<para>
+To register
+ the application, use these settings:
+ </para>
+
+ <programlisting language="Java"><xi:include href="extras/configuring_examples/properties.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
+</step>
+ </procedure>
<important>
<para>
- Always include the <filename>scout-client.jar</filename> file in the classpath of the RMI clients.
+ Always include the
+ <filename>scout-client.jar</filename> file in the
+ RMI client's class-path.
</para>
</important>
@@ -173,46 +193,48 @@
<title>
SOAP
- </title>
+ </title>
<para>
- Read this section to learn how to configure
- <application>Apache Scout</application> to use SOAP to
- communicate with <application>jUDDI</application>.
+ The next method uses
+ SOAP (via Apache Scout) to
+ communicate with the jUDDI
+ registry.
</para>
-
- <para>
- Firstly, deploy the <filename>juddi.war</filename> and
- configure the data-source.
- </para>
- <important>
- <para>
- It is best to also shut down the
- RMI service by "commenting out"
- <filename>web.xml</filename>'s
- <systemitem>RegisterServicesWithJNDI</systemitem> servlet.
- </para>
- </important>
-
- <figure><title>SOAP-based Communications</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/configuring_examples/chart18.png"/>
- </imageobject>
- </mediaobject>
+ <figure><title>SOAP-based Communications</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/configuring_examples/chart18.png"/>
+ </imageobject>
+ </mediaobject>
</figure>
- <para>
- Properties example:
- </para>
-
+ <procedure>
+ <title>Configuring Apache Scout to Use SOAP</title>
+ <step>
+ <para> Deploy the <filename>juddi.war</filename> and
+ configure the data-source. </para>
+ <important>
+ <para>
+ It is best to also shut down the
+ RMI service by "commenting out"
+ <filename>web.xml</filename>'s
+ <systemitem>RegisterServicesWithJNDI</systemitem> servlet.
+ </para>
+ </important>
+<para>
+Here are sample properties:
+</para>
- <programlisting language="XML" role="XML"><xi:include href="extras/configuring_examples/sampleproperties.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
+<programlisting language="XML" role="XML"><xi:include href="extras/configuring_examples/sampleproperties.xmlt" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include></programlisting>
-
+ </step>
+
+ </procedure>
+
</section>
</section>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Content_Based_Routing_Using_Drools.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Content_Based_Routing_Using_Drools.xml 2010-08-15 23:37:23 UTC (rev 34733)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Content_Based_Routing_Using_Drools.xml 2010-08-15 23:45:00 UTC (rev 34734)
@@ -150,18 +150,24 @@
</title>
<para>
- A rule set can be created using the JBoss
- Developer Studio which includes a plug-in for Drools.
- Below is a screen shot of the plug-in. For a detailed
- discussion on rule creation and the Drools language itself
- please see the Drools documention. To turn a regular ruleSet
- into a Countent Based Routing RuleSet you must be evaluating an
- EsbMessage and the rule match should result in a List of
- Strings containing the service destination names. To do this
- you need to make sure you remember two things:
+ Create a rule-set by using the <application>JBoss
+ Developer Studio</application> which includes a plug-in for
+ <application>JBoss Rules</application>. <xref
+ linkend="screenshot"/> shows a screen-shot of this plug-in. For
+ a detailed analysis of the subjects of rule creation and the
+ <application>JBoss Rules</application> language itself, please
+ see the <application>JBoss Rules</application> documentation.
</para>
+
+ <para>
+ To turn a regular rule-set into one that can be used for
+ content-based routing, one must evaluate an
+ ESB message and ensure that the rule match
+ results in a list of strings containing the service destination
+ names. Bear two things in mind whilst doing this:
+ </para>
-<itemizedlist>
+ <itemizedlist>
<listitem>
<para>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Content_Based_Routing_Using_Smooks.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Content_Based_Routing_Using_Smooks.xml 2010-08-15 23:37:23 UTC (rev 34733)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Content_Based_Routing_Using_Smooks.xml 2010-08-15 23:45:00 UTC (rev 34734)
@@ -14,16 +14,20 @@
</title>
<para>
- Use the SmooksAction to split huge messages into
- fragments and perform content-based routing upon these.
+ To split huge messages
+ into more manageable
+ fragments and perform content-based routing
+ upon these, use the SmooksAction.
</para>
<para>
For example, one might have a huge order message with
- thousands/millions of order items per message. In order
- to split the order up by order item and route each order item
- split fragment to one or more destinations based on the
- fragment content. This example can be illustrated as follows:
+ thousands of order items per message. One
+ could
+ split the order up by item and route each
+ split fragment to one or more destinations
+based on the
+ fragment's content. This example can be illustrated as follows:
</para>
Deleted: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Performance_Tuning.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Performance_Tuning.xml 2010-08-15 23:37:23 UTC (rev 34733)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/Performance_Tuning.xml 2010-08-15 23:45:00 UTC (rev 34734)
@@ -1,18 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-<!ENTITY % BOOK_ENTITIES SYSTEM "Services_Guide.ent">
-%BOOK_ENTITIES;
-]>
-
-<chapter id="chap_PerformanceTuning">
- <title>
- Performance Tuning
- </title>
-
-
- <para>
- Please refer to the JBossESB wiki for information on Performance Tuning: <ulink
- url="http://community.jboss.org/wiki/JBossESBPerformanceTuning"
- />.
- </para>
-</chapter>
More information about the jboss-svn-commits
mailing list