Miscellaneous Snippet Topics
The Requires Own option on a BPEL activity is used to prevent a retry of the previous activities in case of an error.
When a business process calls a one-way service asynchronously, a failed event is generated in case of a runtime exception in the called component.
To restrict who can start a business process when using the BusinessFlowManager API to start the process, add a human task assigned to the designated group of potential starters on the Authorization tab of the respective receive activity.
In a long-running BPEL, you will uncheck the Enable persistence and queries of business relevant data flag on an Invoke activity to improve performance by avoiding activity-related data from being persisted to the database.
A notification event handler plugin within a human task is executed during an escalation.
In a long-running process when you need more than one person involved from a human task perspective, you can use ad-hoc follow-on tasks.
XPath to access an HTTP SOAP header in a mediation flow/headers/SOAPHeader.
When the call out Response node's fail terminal is not wired and an unmodeled fault is received, a mediation runtime exception will occur.
To interact with third-party messaging middleware use the "Generic JMS" binding.
Typically, you would choose to implement a JCA adapter rather than a Web Service (to an enterprise application) when the end application does not support transactions but a composite application requires assured delivery on all calls to the application.
Use a receive choice with a timeout element when a long-running business process needs further input from the client for a specified time, and if that time has passed without further user input, default processing should start.
