Making BPEL Processes Dynamic
In most basic process designs, partner links are static; they refer to a single external process selected by the developer at design time. This approach is appropriate for highly targeted or constrained systems. However, in larger systems business processes are more complex. They interact with multiple external services and define multiple partner links, and some of these partner links might not be known at design time. As a result, all potential callouts and logic for deciding which partner links to use must be built inside the business process itself - unnecessarily complicating that process. Fortunately, the BPEL language supports the concept of dynamic binding of partner links. Dynamic binding allows the developer to add new services through configuration or run-time inputs.