From riftsaw-commits at lists.jboss.org Mon Jul 5 09:58:56 2010 Content-Type: multipart/mixed; boundary="===============3499544345076372172==" MIME-Version: 1.0 From: riftsaw-commits at lists.jboss.org To: riftsaw-commits at lists.jboss.org Subject: [riftsaw-commits] riftsaw SVN: r834 - branches/RiftSaw-2.1.x/distribution/src/main/release/db and 6 other directories. Date: Mon, 05 Jul 2010 09:58:56 -0400 Message-ID: <201007051358.o65DwuQc009465@svn01.web.mwc.hst.phx2.redhat.com> --===============3499544345076372172== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: objectiser Date: 2010-07-05 09:58:55 -0400 (Mon, 05 Jul 2010) New Revision: 834 Added: branches/RiftSaw-2.1.x/docs/docbook/userguide/src/main/images/ActivateRe= tire.png trunk/docs/docbook/userguide/src/main/images/ActivateRetire.png Modified: branches/RiftSaw-2.1.x/distribution/src/main/release/db/bpel.properties branches/RiftSaw-2.1.x/docs/docbook/userguide/src/main/module/admin.xml branches/RiftSaw-2.1.x/pom.xml trunk/distribution/src/main/release/db/bpel.properties trunk/docs/docbook/userguide/src/main/module/admin.xml trunk/pom.xml Log: RIFTSAW-241 - added documentation on activate/retire and the stable interfa= ce property. Modified: branches/RiftSaw-2.1.x/distribution/src/main/release/db/bpel.prop= erties =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 --- branches/RiftSaw-2.1.x/distribution/src/main/release/db/bpel.properties= 2010-07-05 09:40:40 UTC (rev 833) +++ branches/RiftSaw-2.1.x/distribution/src/main/release/db/bpel.properties= 2010-07-05 13:58:55 UTC (rev 834) @@ -90,6 +90,7 @@ bpel.db.mode=3DEXTERNAL db.emb.create=3Dfalse bpel.db.ext.dataSource=3Djava:BPELDB + # if set to true will self-register BPEL endpoints upon deployment to a UD= DI. # this uses the juddi-client-3.0.x and the uddi client config can be set i= n the uddi.xml # file @@ -131,6 +132,3 @@ jta.UserTransaction=3DUserTransaction = ode.persistence=3Dhibernate - -ode.process.checkguid=3Dfalse -ode.process.store=3Dorg.apache.ode.store.JBossProcessStoreImpl Added: branches/RiftSaw-2.1.x/docs/docbook/userguide/src/main/images/Activa= teRetire.png =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 (Binary files differ) Property changes on: branches/RiftSaw-2.1.x/docs/docbook/userguide/src/main= /images/ActivateRetire.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Modified: branches/RiftSaw-2.1.x/docs/docbook/userguide/src/main/module/adm= in.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 --- branches/RiftSaw-2.1.x/docs/docbook/userguide/src/main/module/admin.xml= 2010-07-05 09:40:40 UTC (rev 833) +++ branches/RiftSaw-2.1.x/docs/docbook/userguide/src/main/module/admin.xml= 2010-07-05 13:58:55 UTC (rev 834) @@ -14,7 +14,7 @@ =
- BPM Console + BPEL Console =
Overview @@ -116,7 +116,100 @@ = =
+ = +
+ Retiring and Reactivating Process Definitions + = + + When a process definition is initially deployed (i.e. the first versio= n of the process), + it automatically becomes the active process definition. If that BPEL p= rocess definition + is subsequently change and redeployed, then the previous version is retired, + and the new version becomes the active version. + + = + + The only difference between an active and retired + process definition is that a retired process defi= nition can no longer + create new process instances. However if there are current process ins= tances associated + with the retired process definition version, then= these will continue + to execute. + + = + + On some occasions, the administrator may wish to change which version = of a process definition + is considered the active version. Or they may sim= ply want to + retire the currently active process definition, s= o that no more + process instances can be created, only allowing the already running pr= ocess instances to + continue until completed. + + = + + To change the status of a process definition, the administrator should= select the + Runtime tab from the lefthand panel, and then sel= ect the + Deployments option. This will show the process de= finitions, their + versions and their current status (active or retired). + + = + + + = + + + To change a particular version from retired to active, + simply select the retired version and press the <= emphasis>Activate + button in the bottom right. + + = + + To retire a currently active process definition, simply select the par= ticular version and + then press the Retire button in the bottom right. + + = +
=
= +
+ BPEL Properties + = + + When RiftSaw has been installed within the JBossAS environment, t= here is a property file + located at ${JBossAS}/server/default/deploy/riftsaw.sar= /bpel.properties. + + = + + This property file contains a number of properties that are speci= fic to ODE, and if interested + in these properties, then you should refer to the ODE documentati= on. Only one point to note, + the name of the property in this file maybe prefixed with bpel., however + in the ODE documentation the prefix would be ode.. + + = + + This section will present the properties that are specific to Rif= tSaw. + + = + + RiftSaw specific properties + + + + + + + + + + + + +
bpel.uddi.*These properties relate to the UDDI support, which is discuss= ed in a subsequent chapter.
bpel.jaxws.client.initializer.implThis property is automatically set upon installation, based o= n the JAXWS stack being used. + This value should not be changed.
bpel.ws.stableInterface (default false)This property determines whether the Web Service interface, a= ssociated with a BPEL process, + will be updated when a new version of the BPEL process is deploye= d. The benefit of setting this + to false is that changes to the WSDL will be= made active with the BPEL + process. However the issue is that during the transition between = the interfaces, the web service + will momentarily be unavailble - which may cause heavily used ser= vices to reject requests. By + setting this value to true, then the web ser= vice will remain available + while the BPEL process is updated, however any changes in the WSD= L will not be made available.
+
+ = Modified: branches/RiftSaw-2.1.x/pom.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 --- branches/RiftSaw-2.1.x/pom.xml 2010-07-05 09:40:40 UTC (rev 833) +++ branches/RiftSaw-2.1.x/pom.xml 2010-07-05 13:58:55 UTC (rev 834) @@ -74,7 +74,7 @@ 2.1.0-SNAPSHOT 2.1.0-SNAPSHOT - 2.1 + 2.1.1-SNAPSHOT 1.1.1 3.8.1 5.1.0.GA @@ -97,24 +97,24 @@ org.jboss.bpm gwt-console-rpc = - ${bpm.console.version} + ${bpel.console.version} org.jboss.bpm gwt-console-server-integration = - ${bpm.console.version} + ${bpel.console.version} org.jboss.bpm gwt-console-server - ${bpm.console.version} + ${bpel.console.version} riftsaw war org.jboss.bpm gwt-console - ${bpm.console.version} + ${bpel.console.version} riftsaw war Modified: trunk/distribution/src/main/release/db/bpel.properties =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/distribution/src/main/release/db/bpel.properties 2010-07-05 09:40= :40 UTC (rev 833) +++ trunk/distribution/src/main/release/db/bpel.properties 2010-07-05 13:58= :55 UTC (rev 834) @@ -90,6 +90,7 @@ bpel.db.mode=3DEXTERNAL db.emb.create=3Dfalse bpel.db.ext.dataSource=3Djava:BPELDB + # if set to true will self-register BPEL endpoints upon deployment to a UD= DI. # this uses the juddi-client-3.0.x and the uddi client config can be set i= n the uddi.xml # file @@ -131,6 +132,3 @@ jta.UserTransaction=3DUserTransaction = ode.persistence=3Dhibernate - -ode.process.checkguid=3Dfalse -ode.process.store=3Dorg.apache.ode.store.JBossProcessStoreImpl Added: trunk/docs/docbook/userguide/src/main/images/ActivateRetire.png =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 (Binary files differ) Property changes on: trunk/docs/docbook/userguide/src/main/images/ActivateR= etire.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Modified: trunk/docs/docbook/userguide/src/main/module/admin.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/admin.xml 2010-07-05 09:40= :40 UTC (rev 833) +++ trunk/docs/docbook/userguide/src/main/module/admin.xml 2010-07-05 13:58= :55 UTC (rev 834) @@ -14,7 +14,7 @@ =
- BPM Console + BPEL Console =
Overview @@ -116,7 +116,100 @@ = =
+ = +
+ Retiring and Reactivating Process Definitions + = + + When a process definition is initially deployed (i.e. the first versio= n of the process), + it automatically becomes the active process definition. If that BPEL p= rocess definition + is subsequently change and redeployed, then the previous version is retired, + and the new version becomes the active version. + + = + + The only difference between an active and retired + process definition is that a retired process defi= nition can no longer + create new process instances. However if there are current process ins= tances associated + with the retired process definition version, then= these will continue + to execute. + + = + + On some occasions, the administrator may wish to change which version = of a process definition + is considered the active version. Or they may sim= ply want to + retire the currently active process definition, s= o that no more + process instances can be created, only allowing the already running pr= ocess instances to + continue until completed. + + = + + To change the status of a process definition, the administrator should= select the + Runtime tab from the lefthand panel, and then sel= ect the + Deployments option. This will show the process de= finitions, their + versions and their current status (active or retired). + + = + + + = + + + To change a particular version from retired to active, + simply select the retired version and press the <= emphasis>Activate + button in the bottom right. + + = + + To retire a currently active process definition, simply select the par= ticular version and + then press the Retire button in the bottom right. + + = +
=
= +
+ BPEL Properties + = + + When RiftSaw has been installed within the JBossAS environment, t= here is a property file + located at ${JBossAS}/server/default/deploy/riftsaw.sar= /bpel.properties. + + = + + This property file contains a number of properties that are speci= fic to ODE, and if interested + in these properties, then you should refer to the ODE documentati= on. Only one point to note, + the name of the property in this file maybe prefixed with bpel., however + in the ODE documentation the prefix would be ode.. + + = + + This section will present the properties that are specific to Rif= tSaw. + + = + + RiftSaw specific properties + + + + + + + + + + + + +
bpel.uddi.*These properties relate to the UDDI support, which is discuss= ed in a subsequent chapter.
bpel.jaxws.client.initializer.implThis property is automatically set upon installation, based o= n the JAXWS stack being used. + This value should not be changed.
bpel.ws.stableInterface (default false)This property determines whether the Web Service interface, a= ssociated with a BPEL process, + will be updated when a new version of the BPEL process is deploye= d. The benefit of setting this + to false is that changes to the WSDL will be= made active with the BPEL + process. However the issue is that during the transition between = the interfaces, the web service + will momentarily be unavailble - which may cause heavily used ser= vices to reject requests. By + setting this value to true, then the web ser= vice will remain available + while the BPEL process is updated, however any changes in the WSD= L will not be made available.
+
+ = Modified: trunk/pom.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/pom.xml 2010-07-05 09:40:40 UTC (rev 833) +++ trunk/pom.xml 2010-07-05 13:58:55 UTC (rev 834) @@ -74,7 +74,7 @@ 2.2.0-SNAPSHOT 2.2.0-SNAPSHOT - 2.1.1-SNAPSHOT + 2.1.1-SNAPSHOT> 1.1.1 3.8.1 5.1.0.GA @@ -97,24 +97,24 @@ org.jboss.bpm gwt-console-rpc = - ${bpm.console.version} + ${bpel.console.version} org.jboss.bpm gwt-console-server-integration = - ${bpm.console.version} + ${bpel.console.version} org.jboss.bpm gwt-console-server - ${bpm.console.version} + ${bpel.console.version} riftsaw war org.jboss.bpm gwt-console - ${bpm.console.version} + ${bpel.console.version} riftsaw war --===============3499544345076372172==--