Not logged in | Login
Shutdown Procedure For BPELSE
Follow the steps outlined below to shutdown BPEL-SE for maintenence or upgrade
Your upgrade is complete.
FAQs Q. I have a BPEL process that has a receive-reply pair. What happens to the active process instances for which the responses have not been received yet and the HTTP BC endpoint is suspended? A. The suspend functionality only suspends the incoming messages. The responses will be sent to the client by the HTTP BC whenever the BPEL process instance executes the reply activity.
Q. I have a BPEL process: Receive-Invoke-Reply. If I suspend the endpoint for Receive, does it affect the Invoke which consumes a web service via HTTP BC. A. No, the Invoke is not affected
Q. Does the HTTP BC suspend functionality correspond to any of the JBI lifecycle actions for the Service Unit. A. No, the HTTP BC suspend functionality is a custom functionality and has nothing to do with the JBI specification.
Q. What if the business process has a wait activity, how would these instances be handled. A. If the business process has a wait, then after the endpoint is suspended, the user must wait for all the process instances to complete before he/she shuts down the BPEL-SE.
Q. What if the business process is waiting for a correlated receive. A. The user can suspend the endpoint which initiates the business process, then wait for all the correlated messages (related to another endpoint) to arrive. Once this is done and the instances are completed, the user can shutdown the BPEL-SE.