Choosing BPMN or BPEL to model your processes from Redstack

• Write top level (i.e. true ‘business’ processes) in BPMN,
• Do not perform any kind of system interaction in these processes – don’t use adapters, call web services, etc.,
• Use activities or embedded sub-processes with boundary events and event sub-processes to handle all business faults that may occur,
• Make sure to have a ‘catch all’ event sub-process to handle any failures that are not specifically handled,
• Theoretically there should never be a system fault in these BPMN processes,
• Whenever there is a need to do some actual work, delegate this to BPEL, i.e. use a service activity with implementation type ‘service call’ to have BPEL go do the work,
• Make the BPEL processes atomic, so that they can easily be retried, rolled back, etc.,
• Use the fault management framework to control the handling of faults in the BPEL processes, and
• Keep BPEL ‘worker’ processes in separate composites from BPMN ‘business’ processes.

For Complete Article please visit http://redstack.wordpress.com/2012/02/13/choosing-bpmn-or-bpel-to-model-your-processes/