Combining the design rules and patterns from Chapter 3, Building the Core – Enterprise Business Flows, Chapter 4, From Traditional Integration to Composition – Enterprise Business Services, and Chapter 5, Maintaining the Core – the Service Repository, and from this one, we can assume the following:
The Service Repository with all the service metadata elements is properly maintained. We have clear associations between services, endpoints, and Audit messages under the roof of processes. Simply put, every process has a distinct service invocations footprint. Technically, it can be presented as a master
tModelfor a task-orchestrated service if we look at the UDDI analogy.
The preceding assumption is too bold. In dynamic compositions, the sequence of service invocations and even the number of invocations (that is, footprint) can be different for the same abstractly defined process. The key here is to watch out for the services with specific service roles, sometimes...