Abstract: 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.

Abstract: 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.

Abstract: Implementations of the present disclosure include methods for lifecycle management of services provisioned in a business network that include actions of defining a service package associated with a service, the service package being a logical representation of the service and including a plurality of artifacts, storing the service package in computer-readable memory, defining a service lifecycle model associated with the service, the service lifecycle model including a plurality of states, storing the service lifecycle model in the computer-readable memory, determining that the service is in a first state, determining that a first set of provisioning activities has occurred, in response to determining that the first set of provisioning activities has occurred, transitioning the service lifecycle model from the first state to a second state, and updating the service lifecycle model in the computer readable memory.

Abstract: 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.

Abstract: 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.

Abstract: Various implementations are disclosed for enabling transactions in which a reply constraint(s) is defined between a minimum and maximum number of a defined group of recipients that are requested to respond to a sender within a defined time limit. Further, a determination of whether the reply constraint is satisfied is made during a first phase of a two-phase transaction, in which the first phase represents an abbreviated version of the desired transaction, and is used to ensure fulfillment of the reply constraint before the fill transaction is allowed to proceed. In this way, flexibility may be obtained in executing an atomic multicast transaction, while a determination of a likely success of the transaction (as well as the resulting execution of the transaction) may be performed quickly, reliably, and efficiently.

Abstract: 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.