Hi Roberto,
The scenarios just highlight the most interesting aspects of a domain (in this case BAM), where different usage types in SAP NetWeaver combine to compose a new solution.
Milestone monitoring is important because you are listening out for silences among all the noise. In other words you'll publish an event when something does <b>not</b> happen or when aggregated events reach a particular threshold (e.g. 5 cancelled orders of a recently launched product in a day).
In fact you can define the BPEL listening process not just to publish an event but to invoke any service that you choose, such as to send an alert, generate a task for someone to work on or even invoke an automatic repair action.
Best regards,
Alan Rickayzen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.