Sap Ag

Sap Se

Alistair P Barros

Alexander Grosskopf

Anis Charfi

Ingo Weber

Matthias Allgaier

Michael Stollberg

Benjamin Schmeling

Torben Schreiter

Markus Heller

Uwe Kylau

A broker consumer gateway may interface with a service consumer of a computing device consuming at least one service of at least one service provider, including receiving requests for forms, providing the forms, and receiving submitted forms. A service delivery manager may deliver the at least one service. The service delivery manager may include a consumer session manager that creates at least one consumer session to execute at least a portion of the at least one service, a consumer instance manager that creates at least one instance of the at least one service, and a service coordinator configured to coordinate the delivery of the at least one service, based on a coordination model characterizing the at least one service in which the forms are associated with service states of the at least one service and in which transitions between the service states are executed based on the submitted forms.

Service delivery management for brokered service delivery

A buffer may be configured to store a plurality of items, and to be accessed by one or more activities of an instance of a process model. A scheduler may be configured to schedule execution of each of a plurality of activities of the process model, and to determine an activation of an activity of the plurality of activities. The scheduler may include an activity manager configured to access an activity profile of the activity upon the determining of the activation, the activity profile including buffer access characteristics according to which the activity is designed to access the buffer. A process execution unit may be configured to execute the activity and may include a buffer access manager configured to access the buffer according to the buffer access characteristics of the activity profile, and to thereby facilitate an exchange of at least one item between the buffer and the activity.

Streaming operations for workflow process models using multiple views on a same buffer

Implementations include receiving service information regarding one or more services provided by one or more service providers, the services being executed by one or more service computing devices, storing the service information on a computer-readable storage device that is in communication with the one or more broker computing devices, receiving user input at the one or more broker computing devices, the user input being transmitted to the one or more broker computing devices from one or more consumer computing devices over a service channel that corresponds to a service being accessed by a service consumer, transmitting the user input to the one or more service computing devices, receiving service output from the one or more service computing devices, the service output generated based on processing of the user input using the service, and transmitting the service output to the one or more consumer computing devices over the service channel.

Service delivery framework

Implementations of the present disclosure include methods for provisioning services in a business network. In some implementations, methods include receiving data corresponding to a first service, receiving data corresponding to a second service, processing the data corresponding to the first service and the data corresponding to the second service using a computer-executable tool selected from a plurality of computer-executable tools to enable provisioning of a service using the business network, and the processing being performed in a situational modeling layer of a service provisioning framework, generating a kernel model corresponding to the service, the generating being performed in a kernel modeling layer of the service provisioning framework, and storing the kernel model in computer-readable memory.

Framework for diversified provisioning of services into business networks

A selected activity of a service process model displayed in a process view of a graphical user interface may be determined. The service process model may represent a software service to be provided from a service provider to a consumer by way of a service broker. At least one service delivery entity associated with the service broker and providing service delivery functionality to be included in a brokered service process model may be determined, the service delivery entity including a state machine comprising states and transitions between the states. Configuration options may be provided in a configuration view of the graphical user interface. The configuration options may include goal states of the states to be reached as part of the brokered service process model and in association with the selected activity. A selected goal state of the goal states may be determined. The brokered service process model may be provided within a brokered service process view of the graphical user interface. The brokered service process model may include at least one entity activity configured to cause the selected goal state to be reached in association with the selected activity.

Brokered service delivery

Implementations are described for exception handling for collaborating process models. Once an error or other exception is determined during execution of a process model, a collaborating process model is determined to be notified. The collaborating process model and the process model may be executing in a collaborating orchestration engine and in an orchestration engine, respectively. Thus, the collaborating process model may be notified of the exception. Then, the execution of the collaborating process model within the collaborating orchestration engine may be at least partly suspended, and execution of the process model and the collaborating process model may later be resumed once the exception has been resolved.

Exception handling for collaborating process models

Activations of a plurality of incoming branches may be detected at a synchronization point having a plurality of outgoing branches. A first synchronization may be executed after a first number of activations is detected, and at least one of a plurality of outgoing branches from the synchronization point may be activated, based on the first synchronization. A second synchronization may be executed after a second number of activations is detected, and at least a second one of the plurality of outgoing branches from the synchronization point may be activated, based on the second synchronization.

Process model control flow with multiple synchronizations

A first instance and a second instance of an activity of a process model may be executed, the first instance, the second instance, and the activity being associated with activity state data describing one or more states thereof. A co-process associated with the first instance, the second instance, and the activity may be spawned, and the co-process may be executed based on the activity state data.

Multiple instance management for workflow process models

Various implementations are disclosed for routing messages according to a routing order, where sequences (e.g., sub-sections or subsets) of the routing order are progressively and/or iteratively resolved during a run-time of the message routing operation(s). The resolution of a sequence may involve determining identity information of recipients that were previously only described within the sequence in relation to one another, in relation to the group, or in relation to a type of routing order. Further, the resolution(s) of the sequences may depend at least in part on responses received from recipients of the message during execution of earlier (resolved) sequences of the message routing operations. In this way, message routing may occur dynamically, so that, for example, new recipients may be added, or a (new) message order may otherwise be realized or implemented, during the run-time of the routing operation.

Dynamic message routing

Various implementations are disclosed for designing a process model that includes a task, the task associated with a potential suspension, e.g., in response to an error or other exception. At least one suspension task may be provided in parallel with the task to form a parallel combination thereof within the process model. A first control task, e.g., an AND split task, may be provided prior to the parallel combination, and a second control task, e.g., a synchronize/merge task, may be provided subsequent to the parallel combination, the first control task and the second control task configured to activate and join, respectively, the task and the at least one suspension task during execution of the process model.

Growing community of inventors

Camira, Australia

Alistair P Barros