Managing message events is particularly important when the business process is waiting for callbacks from PARTNER Web services. ACTIVITY, LETS you wait for only a single (exactly specified) message on a port type. Often, however, it is more useful to wait for more than one message, of which only one will occur.

Alarm events are useful when you want the process to wait for a callback for a CERTAIN period of time, such as 15 minutes. If no callback is received, the process flow continues as designed. This APPROACH is particularly useful in loosely coupled service-oriented architectures, where you cannot rely on Web services being available all the time. This way, the process flow can proceed even if one of the bookstores does not return an offer.

Managing message events is particularly important when the business process is waiting for callbacks from partner Web services. activity, lets you wait for only a single (exactly specified) message on a port type. Often, however, it is more useful to wait for more than one message, of which only one will occur.

Alarm events are useful when you want the process to wait for a callback for a certain period of time, such as 15 minutes. If no callback is received, the process flow continues as designed. This approach is particularly useful in loosely coupled service-oriented architectures, where you cannot rely on Web services being available all the time. This way, the process flow can proceed even if one of the bookstores does not return an offer.