With most BPEL processes, partner links are static in that they reference a single instance of web service specified by the developer at design time (though typically configured at deployment).
In the majority of cases, this approach is fine. However, in this recipe we will consider a scenario in which a standard service contract might be implemented by multiple providers, the selection of which we want to dynamically configure at runtime.
An example of this, is the order aggregation process of our online bookstore, where at the point of placing an order with the publisher, we will need to invoke the appropriate service in order to route our book order to the correct publisher.
For this scenario, the BPEL ...