ABSTRACT
In a process-driven service-oriented architecture, the basic idea to connect the process and services worlds is that activities in the processes invoke services. Services must be invoked from a process flow, and the business scenario requires a synchronous communication between the process and the service. That is, the process depends on the functional interface of the service and needs to react on the possible results of the service. The fire-and-forget service activity solution separates the request from the execution of the service. Services must be invoked from a process flow, and the business scenario requires picking up multiple service results while other process steps need to be executed in the meantime. Business processes are executed on a process engine, and the business scenarios of the processes require communicating process states to other partners. Business processes are modeled with subprocesses and are executed on a process engine.
