Designing BPEL processes to reduce persistence
Every step in a BPEL process adds an overhead. In this recipe we'll suggest some design options to consider when deciding how to construct your processes.
Getting ready
You will need an understanding of SOA Suite programming concepts.
How to do it...
The following steps cover some of the techniques for reducing process persistence:
If you have lots of variable assignment steps, consider a call out to a Business Rules component to check and set multiple values in response to the user input.
If complex logic is required, consider embedding a call to a Java class in the composite if this can reduce the number of steps.
How it works...
By default, the BPEL composite design will consist of adding steps to a process until the business logic can be satisfied. This can make it easy to end up with monolithic processes that have too many steps. For example, processes which make decisions and then fork on the results, require an increasing number of steps to deal...