[riftsaw-commits] riftsaw SVN: r875 - trunk/docs/docbook/userguide/src/main/module and 1 other directory.

Author: objectiser Date: 2010-07-15 07:56:27 -0400 (Thu, 15 Jul 2010) New Revision: 875 Modified: branches/RiftSaw-2.1.x/docs/docbook/userguide/src/main/module/uddi.xml trunk/docs/docbook/userguide/src/main/module/uddi.xml Log: Remove references to ESB4.7 from UDDI documentation. Modified: branches/RiftSaw-2.1.x/docs/docbook/userguide/src/main/module/uddi.xml =================================================================== --- branches/RiftSaw-2.1.x/docs/docbook/userguide/src/main/module/uddi.xml 2010-07-15 04:22:37 UTC (rev 874) +++ branches/RiftSaw-2.1.x/docs/docbook/userguide/src/main/module/uddi.xml 2010-07-15 11:56:27 UTC (rev 875) @@ -27,7 +27,7 @@ <para> By default RiftSaw uses the jUDDI client libraries of JBossESB/SOA-P, and the client - configuration is found in the deploy/jbossesb.saw/esb.juddi.client.xml. Both the + configuration is found in the deploy/jbossesb.sar/esb.juddi.client.xml. Both the name of the ClerkManager and the Clerk itself are specified in the <emphasis>bpel.properties</emphasis> file. </para> @@ -68,31 +68,26 @@ <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. + Name of the class that implements the <emphasis>org.jboss.soa.bpel.runtime.engine.ode.UDDIRegistration</emphasis> interface. </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. + Defines the path to the <filename>bpel.uddi.client.xml</filename> config file. This can be left commented out if + you want to use the <filename>jbossesb.sar/esb.uddi.client.xml</filename>. However in that case a + <filename>bpel.uddi.clerk.manager</filename> 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. + Defines the ClerkManager name that will be used if the <emphasis>bpel.uddi.clerk.config</emphasis> 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. + in the <filename>esb.juddi.client.xml</filename>. Note that if the <emphasis>bpel.uddi.clerk.config</emphasis> is defined, the + setting of the <emphasis>bpel.uddi.clerk.manager</emphasis> is ignored. </entry> </row> <row> @@ -100,7 +95,7 @@ <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'. + in the <filename>esb.juddi.client.xml</filename>. By default this is set to 'BPEL_clerk'. </entry> </row> <row> @@ -122,20 +117,13 @@ <section> <title>Default configurations</title> - <para>When RiftSaw is deployed to a JBossAS-5.1.0, jUDDI v3 is not installed, and therefore + <para>When RiftSaw is deployed to JBossAS-5.1.0, jUDDI v3 is not installed, and therefore the UDDI integration is turned off (bpel.uddi.registration=false).</para> - <para>When RiftSaw is deployed to JBossAS-5.1.0 + JBossESB-4.7, the UDDI integration is - turned on. By default we use the jUDDI client library which ships with the JBossESB, which - is configured in the <filename>jbossesb.sar/esb.uddi.client.xml</filename>, - with manager name 'test-manager'. The <emphasis>bpel.uddi.client.impl</emphasis> is set - to <emphasis>org.jboss.soa.bpel.uddi300.UDDI300RegistrationImpl</emphasis>. - </para> - - <para>When RiftSaw is deployed to SOA-P-5.0.0 (or JBossESB > 4.7) UDDI integration is + <para>When RiftSaw is deployed to SOA-P-5.0.0 (or JBossESB 4.8 or higher) UDDI integration is turned on and the <emphasis>bpel.uddi.client.impl</emphasis> is set to <emphasis>org.jboss.soa.bpel.uddi.UDDIRegistrationImpl</emphasis>. - Again the <filename>jbossesb.sar/esb.uddi.client.xml</filename> is used, with manager name 'esb.registry'. + The <filename>jbossesb.sar/esb.uddi.client.xml</filename> is used, with manager name 'esb.registry'. </para> </section> @@ -174,12 +162,6 @@ to turn this value to "false" once you are content with the UDDI Seed Data. </para> - - <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.</para></warning> - </section> </chapter> Modified: trunk/docs/docbook/userguide/src/main/module/uddi.xml =================================================================== --- trunk/docs/docbook/userguide/src/main/module/uddi.xml 2010-07-15 04:22:37 UTC (rev 874) +++ trunk/docs/docbook/userguide/src/main/module/uddi.xml 2010-07-15 11:56:27 UTC (rev 875) @@ -27,7 +27,7 @@ <para> By default RiftSaw uses the jUDDI client libraries of JBossESB/SOA-P, and the client - configuration is found in the deploy/jbossesb.saw/esb.juddi.client.xml. Both the + configuration is found in the deploy/jbossesb.sar/esb.juddi.client.xml. Both the name of the ClerkManager and the Clerk itself are specified in the <emphasis>bpel.properties</emphasis> file. </para> @@ -68,31 +68,26 @@ <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. + Name of the class that implements the <emphasis>org.jboss.soa.bpel.runtime.engine.ode.UDDIRegistration</emphasis> interface. </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. + Defines the path to the <filename>bpel.uddi.client.xml</filename> config file. This can be left commented out if + you want to use the <filename>jbossesb.sar/esb.uddi.client.xml</filename>. However in that case a + <filename>bpel.uddi.clerk.manager</filename> 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. + Defines the ClerkManager name that will be used if the <emphasis>bpel.uddi.clerk.config</emphasis> 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. + in the <filename>esb.juddi.client.xml</filename>. Note that if the <emphasis>bpel.uddi.clerk.config</emphasis> is defined, the + setting of the <emphasis>bpel.uddi.clerk.manager</emphasis> is ignored. </entry> </row> <row> @@ -100,7 +95,7 @@ <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'. + in the <filename>esb.juddi.client.xml</filename>. By default this is set to 'BPEL_clerk'. </entry> </row> <row> @@ -122,20 +117,13 @@ <section> <title>Default configurations</title> - <para>When RiftSaw is deployed to a JBossAS-5.1.0, jUDDI v3 is not installed, and therefore + <para>When RiftSaw is deployed to JBossAS-5.1.0, jUDDI v3 is not installed, and therefore the UDDI integration is turned off (bpel.uddi.registration=false).</para> - <para>When RiftSaw is deployed to JBossAS-5.1.0 + JBossESB-4.7, the UDDI integration is - turned on. By default we use the jUDDI client library which ships with the JBossESB, which - is configured in the <filename>jbossesb.sar/esb.uddi.client.xml</filename>, - with manager name 'test-manager'. The <emphasis>bpel.uddi.client.impl</emphasis> is set - to <emphasis>org.jboss.soa.bpel.uddi300.UDDI300RegistrationImpl</emphasis>. - </para> - - <para>When RiftSaw is deployed to SOA-P-5.0.0 (or JBossESB > 4.7) UDDI integration is + <para>When RiftSaw is deployed to SOA-P-5.0.0 (or JBossESB 4.8 or higher) UDDI integration is turned on and the <emphasis>bpel.uddi.client.impl</emphasis> is set to <emphasis>org.jboss.soa.bpel.uddi.UDDIRegistrationImpl</emphasis>. - Again the <filename>jbossesb.sar/esb.uddi.client.xml</filename> is used, with manager name 'esb.registry'. + The <filename>jbossesb.sar/esb.uddi.client.xml</filename> is used, with manager name 'esb.registry'. </para> </section> @@ -174,12 +162,6 @@ to turn this value to "false" once you are content with the UDDI Seed Data. </para> - - <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.</para></warning> - </section> </chapter>