Author: kurtstam
Date: 2010-03-22 17:42:53 -0400 (Mon, 22 Mar 2010)
New Revision: 585
Modified:
trunk/docs/docbook/userguide/src/main/module/uddi.xml
Log:
RIFTSAW-158, Deploytime lookup of partnerChannel WSDL Endpoints. Updating Documentation.
Modified: trunk/docs/docbook/userguide/src/main/module/uddi.xml
===================================================================
--- trunk/docs/docbook/userguide/src/main/module/uddi.xml 2010-03-22 21:41:15 UTC (rev
584)
+++ trunk/docs/docbook/userguide/src/main/module/uddi.xml 2010-03-22 21:42:53 UTC (rev
585)
@@ -14,8 +14,10 @@
UDDI v3 complaint registry.
</para>
- <para>Upon deployment both the Service and its BindingTemplate (EndPoint
information) are registered, upon undeployment
- the BindingTemplate is removed.
+ <para>Upon deployment both the Service and its BindingTemplate (EndPoint
information) are registered, and a
+ partnerLinkChannel is created for each partnerLink. UDDI lookup will obtain the
WSDL Endpoint from the
+ UDDI and access this URL to obtain the WSDL straight from the Service. Upon
undeployment the
+ BindingTemplate is removed from the UDDI Registry.
</para>
</section>
@@ -30,80 +32,92 @@
<emphasis>bpel.properties</emphasis> file.
</para>
- <para>
- The UDDI properties in the bpel.properties file are:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- bpel.uddi.registration
- </para>
- <para>
- boolean
- </para>
- <para>
- If set to 'false', the UDDI integration is turned off. The RiftSaw
installation process
- sets this value to 'true' only if the jbossesb-registry.sar is detected
containing a jUDDI v3
- registry. In all other case it is defaulted to false.
- </para>
- </listitem>
- <listitem>
- <para>
- bpel.uddi.client.impl
- </para>
- <para>
- String
- </para>
- <para>
- Name of the a class that implements the
org.jboss.soa.bpel.runtime.engine.ode.UDDIRegistration interface.
- The RiftSaw installation process set this value to
org.jboss.soa.bpel.uddi300.UDDI300RegistrationImpl
- if JBossESB-4.7 is detected. JBossESB-4.7 uses
- the jUDDI-3.0.0 client libary, while SOA-P-5.0.0 and future version of JBossESB
will use jUDDI-3.0.1 or higher and
- for those it is set to org.jboss.soa.bpel.uddi.UDDIRegistrationImpl.
- </para>
- </listitem>
- <listitem>
- <para>
- bpel.uddi.clerk.config
- </para>
- <para>
- String
- </para>
- <para>
- Defines the path to the bpel.uddi.client.xml config file. This can be left
commented out if
- you want to use the jbossesb.sar/esb.uddi.client.xml. However in that case a
bpel.uddi.clerk.manager
- needs to be defined.
- </para>
- </listitem>
- <listitem>
- <para>
- bpel.uddi.clerk.manager
- </para>
- <para>
- String
- </para>
- <para>
- Defines the ClerkManager name that will be used if the bpel.uddi.clerk.config
is left commented out.
- This value should correspond to the name of the manager
- in the esb.juddi.client.xml. For JBossESB-4.7 this is 'test-manager',
while for SOA-P-5.0.0
- and newer version of JBossESB it is 'esb-registry'. Note that if the
bpel.uddi.clerk.manager is defined, the
- setting of the bpel.uddi.clerk.manager is ignored.
- </para>
- </listitem>
- <listitem>
- <para>
- bpel.uddi.clerk
- </para>
- <para>
- String
- </para>
- <para>
- Defines the Clerk name that will be used. This value should correspond to the
name of the clerk
- in the esb.juddi.client.xml. By default this is set to 'BPEL_clerk'.
- </para>
- </listitem>
- </itemizedlist>
+ <table>
+ <title>The UDDI related properties in the bpel.properties</title>
+ <tgroup cols="3" >
+ <colspec colnum="1" colname="col1" />
+ <colspec colnum="2" colname="col2" />
+ <colspec colnum="3" colname="col3" />
+ <thead>
+ <row>
+ <entry>attribute</entry><entry>type
(default)</entry><entry>description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>bpel.uddi.registration</entry>
+ <entry>boolean (true)</entry>
+ <entry>
+ If set to 'false', the UDDI integration is turned off. The RiftSaw
installation process
+ sets this value to 'true' only if the jbossesb-registry.sar is
detected containing a jUDDI v3
+ registry. In all other case it is defaulted to false.
+ </entry>
+ </row>
+ <row>
+ <entry>bpel.webservice.secure</entry>
+ <entry>boolean (false)</entry>
+ <entry>
+ The UDDI Registration process registers an WSDL AccessPoint in the
BindingTemplate for the
+ BPEL Service it is registering. The BPEL server exposes the service WSDL
Endpoint on the
+ WS stack (Currently we support JBossWS and CXF), if your WS stack is
configured to a use
+ a secure (https) protocol, then you need to switch this setting to
'true'. Note that this
+ setting is used during the registration process only.
+ </entry>
+ </row>
+ <row>
+ <entry>bpel.uddi.client.impl</entry>
+ <entry>String
(org.jboss.soa.bpel.uddi.UDDIRegistrationImpl)</entry>
+ <entry>
+ Name of the a class that implements the
org.jboss.soa.bpel.runtime.engine.ode.UDDIRegistration interface.
+ The RiftSaw installation process set this value to
org.jboss.soa.bpel.uddi300.UDDI300RegistrationImpl
+ if JBossESB-4.7 is detected. JBossESB-4.7 uses
+ the jUDDI-3.0.0 client libary, while SOA-P-5.0.0 and future version of
JBossESB will use jUDDI-3.0.1 or higher and
+ for those it is set to org.jboss.soa.bpel.uddi.UDDIRegistrationImpl.
+ </entry>
+ </row>
+ <row>
+ <entry>bpel.uddi.clerk.config</entry>
+ <entry>String (not used by default)</entry>
+ <entry>
+ Defines the path to the bpel.uddi.client.xml config file. This can be left
commented out if
+ you want to use the jbossesb.sar/esb.uddi.client.xml. However in that case a
bpel.uddi.clerk.manager
+ needs to be defined.
+ </entry>
+ </row>
+ <row>
+ <entry>bpel.uddi.clerk.manager</entry>
+ <entry>String (esb-registry)</entry>
+ <entry>
+ Defines the ClerkManager name that will be used if the bpel.uddi.clerk.config
is left commented out.
+ This value should correspond to the name of the manager
+ in the esb.juddi.client.xml. For JBossESB-4.7 this is 'test-manager',
while for SOA-P-5.0.0
+ and newer version of JBossESB it is 'esb-registry'. Note that if the
bpel.uddi.clerk.config is defined, the
+ setting of the bpel.uddi.clerk.manager is ignored.
+ </entry>
+ </row>
+ <row>
+ <entry>bpel.uddi.clerk</entry>
+ <entry>String (BPEL_clerk)</entry>
+ <entry>
+ Defines the Clerk name that will be used. This value should correspond to the
name of the clerk
+ in the esb.juddi.client.xml. By default this is set to 'BPEL_clerk'.
+ </entry>
+ </row>
+ <row>
+ <entry>bpel.uddi.lookup</entry>
+ <entry>boolean (true)</entry>
+ <entry>
+ If set to true, the creating process of the partner channel will do a lookup
by serviceName in the
+ UDDI, and a WSDL Endpoint is retrieved. This WSDL Endpoint is the then used to
obtain the WSDL. This
+ process makes it easier to move Endpoints around within your deployment,
without having to update
+ the partnerlink WSDL files in your bpel deployments. Note that an it is still
a requirement to
+ deploy the initial partnerlink WSDL file for each partnerLink.
+ </entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
</section>
<section>
@@ -158,10 +172,11 @@
to turn this value to "false" once you are content with the UDDI Seed
Data.
</para>
- <warning>When running on JBossESB-4.7, the root seed data will only be
installed if the UDDI tables are
+
+ <warning><para>When running on JBossESB-4.7, the root seed data will
only be installed if the UDDI tables are
still empty. This means that you need to make sure that the jUDDI Root Seed Data
install process
did not run before installing RiftSaw. In other words, do not start JBossESB-4.7
before installing
- RiftSaw.</warning>
+ RiftSaw.</para></warning>
</section>
Show replies by date