Author: jeff.yuchang Date: 2010-12-06 22:51:58 -0500 (Mon, 06 Dec 2010) New Revision: 1195 Modified: trunk/docs/docbook/userguide/src/main/en-US/module/admin.xml Log: *RiftSaw-321, document how to safely undeploy processes. Modified: trunk/docs/docbook/userguide/src/main/en-US/module/admin.xml =================================================================== --- trunk/docs/docbook/userguide/src/main/en-US/module/admin.xml 2010-12-07 03:50:39 UTC (rev 1194) +++ trunk/docs/docbook/userguide/src/main/en-US/module/admin.xml 2010-12-07 03:51:58 UTC (rev 1195) @@ -407,4 +407,24 @@ </section> + <section> + <title>How to safely undeploy processes</title> + + <para> + If an active process definition is undeployed, any active process instances will be terminated. + If this is not desired behaviour, then the administrator should first retire the process definition (version) using the BPEL console, + and then when all active process instances for the version have completed, it can be safely undeployed. + </para> + + <para> + So below is the recommended steps for safely undeploy processes. + <itemizedlist> + <listitem>Check if the processes have any active process instances.</listitem> + <listitem>If it has unfinished process instances, retire the process in BPEL Console first.</listitem> + <listitem>Undeploy the processes only if they don't have any active process instances.</listitem> + </itemizedlist> + </para> + + </section> + </chapter>