From riftsaw-commits at lists.jboss.org Tue Mar 2 01:34:23 2010 Content-Type: multipart/mixed; boundary="===============5866197387254476453==" MIME-Version: 1.0 From: riftsaw-commits at lists.jboss.org To: riftsaw-commits at lists.jboss.org Subject: [riftsaw-commits] riftsaw SVN: r531 - in trunk/docs/docbook/userguide/src/main: module and 1 other directory. Date: Tue, 02 Mar 2010 01:34:22 -0500 Message-ID: <201003020634.o226YMPv022600@svn01.web.mwc.hst.phx2.redhat.com> --===============5866197387254476453== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: kurtstam Date: 2010-03-02 01:34:22 -0500 (Tue, 02 Mar 2010) New Revision: 531 Added: trunk/docs/docbook/userguide/src/main/module/uddi.xml Modified: trunk/docs/docbook/userguide/src/main/master.xml Log: RIFTSAW-151 adding UDDI integration documentation. Modified: trunk/docs/docbook/userguide/src/main/master.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 --- trunk/docs/docbook/userguide/src/main/master.xml 2010-03-02 06:25:04 UT= C (rev 530) +++ trunk/docs/docbook/userguide/src/main/master.xml 2010-03-02 06:34:22 UT= C (rev 531) @@ -14,5 +14,6 @@ + Added: trunk/docs/docbook/userguide/src/main/module/uddi.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 --- trunk/docs/docbook/userguide/src/main/module/uddi.xml = (rev 0) +++ trunk/docs/docbook/userguide/src/main/module/uddi.xml 2010-03-02 06:34:= 22 UTC (rev 531) @@ -0,0 +1,163 @@ + + + + UDDI Integration = + = +
+ Overview + + + The integration of a UDDI client into the RiftSaw runtime codebas= e allows for the auto-registration + of BPEL services to an UDDI registry upon deployment of the servi= ce. The registration + process uses the jUDDI-3 client libraries which are capable of co= mmunicating to any + UDDI v3 complaint registry. = + + = + Upon deployment both the Service and its BindingTemplate (E= ndPoint information) are registered, upon undeployment + the BindingTemplate is removed. + + = +
+ = +
+ UDDI config properties + + + By default RiftSaw uses the jUDDI client libraries of JBossESB/SOA-P, a= nd the client + configuration is found in the deploy/jbossesb.saw/esb.juddi.client.xml.= Both the + name of the ClerkManager and the Clerk itself are specified in the + bpel.properties file. + + = + + The UDDI properties in the bpel.properties file are: + + = + + + + bpel.uddi.registration + + + boolean + + + If set to 'false', the UDDI integration is turned off. The RiftS= aw installation process + sets this value to 'true' only if the jbossesb-registry.sar is d= etected containing a jUDDI v3 + registry. In all other case it is defaulted to false. + + + + + bpel.uddi.client.impl + + + String + + + Name of the a class that implements the org.jboss.soa.bpel.runti= me.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 vers= ion of JBossESB will use jUDDI-3.0.1 or higher and + for those it is set to org.jboss.soa.bpel.uddi.UDDIRegistrationI= mpl. + + + + + bpel.uddi.clerk.config + + + String + + + Defines the path to the bpel.uddi.client.xml config file. This c= an 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. + + + + + bpel.uddi.clerk.manager + + + String + + + 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-mana= ger', 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. + + + + + bpel.uddi.clerk + + + String + + + Defines the Clerk name that will be used. This value should corr= espond to the name of the clerk + in the esb.juddi.client.xml. By default this is set to 'BPEL_cle= rk'. + + + +
+ = +
+ Default configurations + When RiftSaw is deployed to a JBossAS-5.1.0, jUDDI v3 is no= t installed, and therefor + the UDDI integration is turned off (bpel.uddi.registration=3Dfals= e). + = + When RiftSaw is deployed to JBossAS-5.1.0 + JBossESB-4.7, t= he UDDI integration is + turned on. By default we use the jUDDI client library which ships= with the JBossESB, which + is configured in the jbossesb.sar/esb.uddi.client.xml, with manag= er name 'test-manager'. The bpel.uddi.client.impl is set = + to org.jboss.soa.bpel.uddi300.UDDI300RegistrationImpl. + + = + When RiftSaw is deployed to SOA-P-5.0.0 (or JBossESB > 4.7)= UDDI integration is + turned on and the bpel.uddi.client.impl is set to org.jboss.soa.b= pel.uddi.UDDIRegistrationImpl. + Again the jbossesb.sar/esb.uddi.client.xml is used, with manager = name 'esb.registry'. + +
+ = +
+ Other UDDI v3 Registries + = + Other UDDI v3 complaint registries can be used, however the= UDDIv3 spec only requires + communication using the UDDI WebServices. To set up SOAP based co= mmunication specify the JAXWS-Transport. + At this point it makes sense to no longer use the the esb.uddi.cl= ient.xml, but rather use your + own bpel.uddi.client.xml. For more details please see the jUDDI v= 3 documentain. + +
+ = +
+ UDDI Registry Entities and UDDI Seed Data + = + In the esb.uddi.client.xml a few properties are defined tha= t are used by the Clerk at = + registration time. These settings of these values can be customiz= ed, however they must + correspond to the UDDI seed data specified for the jbossesb publi= sher, in the = + jbossesb-registry.sar/juddi_custom_install_data. So you will need= to change it there as well. + + = + The clerk is configured to use the jbossesb publisher and t= he keyDomain + is set to "esb.jboss.org". + + = + The businessKey is set to "redhat-jbos= s". + = + The serviceDescription is set to "B= PEL Service deployed by Riftsaw". + = + The bindingDescription is set to "B= PEL Endpoint deployed by Riftsaw". + = + Note that in soa-p-5 the jbossesb-registry.sar/esb.uddi.xml= contains a property = + juddi.seed.always which is set to "true". Th= is means that that it + is always trying to load the root seed data on startup of the ser= ver. It is recommended + to turn this value to "false" once you are content with the UDDI = Seed Data. = + + = +
+ = + --===============5866197387254476453==--