How to use Dynamic Endpoint Selection (DES) or Late Binding in a BPM integration project

In many cases a customer will want to avoid hard coding specific endpoints URLs within their Advanced Integration Services (AIS) on BPM.  This is often because each environment (Dev, Staging, SIT, ProductionA etc) might require different setup.  Sometimes this is also because late binding can mean that rules can be applied based on time of day, content or context of message or other criteria.  In earlier versions of IBM middleware such as WebSphere Dynamic Process Edition (WDPE AKA "Fabric") this was achieved through the use of Policy along with Assertions.  This approach was not maintained within the later BPM product set, but an alternative is to use the embedded ILOG jRules engine (JRE) to externalized the business logic so that late binding can be performed in a similar way.  Thus by using this design pattern, it is possible to log into the rules portal at run time, and change the SCA binding address, (or other content/context information used in the business rule), to allow rules based dynamic endpoint selection (late binding)

The following deck provides details of how this is achieved.

https://ibm.box.com/s/nepps8t5el301xuvmkc4cywmsebp46sp