Abstract: A computer-readable medium, computer-implemented method, and system are provided. In one embodiment, a business process is created, and a cost of change value for the business process is defined. An executable process that is generated from the business process is executed, and a change request is received. It is determined whether the cost of change value is greater than a threshold value, and, when the cost of change value is not greater than the threshold value, the change request is initiated.

Abstract: A distributed order orchestration system is provided that includes an event manager configured to generate and publish a set of events based on a process state and metadata stored in a database. A set of subscribers can consume the set of events, and each subscriber can execute a task based on the consumed event.

Abstract: Particular embodiments generally relate to the orchestration of an order fulfillment business process using effectivity dates and versioning. In one embodiment, a plurality of services in the order fulfillment business process are provided. A definition of a business process including one or more services is received from an interface. The one or more services may be defined in steps to be performed in the order fulfillment business process. An effectivity date associated with the definition is also received from the interface. For example, the effectivity date may be associated with the business process or individual steps in the business process and may specify a period of time during which the process or step can be used. The effectivity dates and versioning may then be enforced at run-time.

Abstract: Particular embodiments provide a method for orchestrating an order fulfillment business process that includes a sub-process. In one embodiment, abstraction of business processes from an underlying information technology (IT) infrastructure is provided. An orchestration process can be designed using sub-processes such that the sub-process is assembled at run-time into an executable process. The sub-process may be defined in an interface as a single step. A plurality of services as then assembled as steps in the executable process at run-time.

Abstract: A distributed order orchestration system for orchestrating a business process of an order fulfillment system receives from an interface a definition of the business process and generates metadata from the definition. The system then generates an abstract syntax tree from the metadata. The tree includes a plurality of nodes and one or more of the nodes correspond to a predefined template. The system then generates executable orchestration code based on the abstract syntax tree and the predefined template.

Abstract: Techniques for dynamic service invocation and dynamic service adaptation in the context of a service oriented application. In one set of embodiments, a plurality of mediator services are introduced between the application and a plurality of actual services accessed by the application. The plurality of mediator services are configured to expose a common, abstract operation. At application runtime, the application determines, via a rules engine, a selection of a mediator service, and invokes the abstract operation by sending an invocation message to the selected mediator service. The selected mediator service transforms (i.e., adapts) the message into a format appropriate for invoking an actual operation exposed by an actual service associated with the selected mediator service. The selected mediator service then invokes the actual operation by sending the transformed message to the actual service.

Abstract: A distributed order orchestration system is provided that includes an event manager configured to generate and publish a set of events based on a process state and metadata stored in a database. A set of subscribers can consume the set of events, and each subscriber can execute a task based on the consumed event.

Abstract: A computer-readable medium, computer-implemented method, and system are provided. In one embodiment, a business process is created, and a cost of change value for the business process is defined. An executable process that is generated from the business process is executed, and a change request is received. It is determined whether the cost of change value is greater than a threshold value, and, when the cost of change value is not greater than the threshold value, the change request is initiated.

Abstract: A computer-readable medium, computer-implemented method, and system are provided. In one embodiment, a task layer service pattern is created, and a task layer service is created from the task layer service pattern. The task layer service is assigned to a step of an executable process, and the step of the executable process is executed. The task layer service is executed in order to invoke a fulfillment service.

Abstract: A computer-readable medium, computer-implemented method, and system are provided. In one embodiment, an original executable process is executed in a regular mode. When a change request is received, the original executable process is stopped, and a new executable process is created. The new executable process is then executed in a change mode.

Abstract: A distributed order orchestration system for orchestrating a business process of an order fulfillment system receives from an interface a definition of the business process and generates metadata from the definition. The system then generates an abstract syntax tree from the metadata. The tree includes a plurality of nodes and one or more of the nodes correspond to a predefined template. The system then generates executable orchestration code based on the abstract syntax tree and the predefined template.

Abstract: In one embodiment, abstraction of business processes from an underlying information technology (IT) infrastructure is provided. An orchestration process can be designed using encapsulated service invocations. A plurality of services may be provided that are configured to provide services in the order fulfillment business process. An interface may be used by a user to provide a definition of a business process. The business process may identify one or more services that define steps to be performed in the order fulfillment process. This definition may include metadata that can be stored in a runtime table. During runtime, the metadata may be read from the table and used by the run-time engine to perform an executable process. The one or more services may be dynamically invoked during orchestration of the executable process, which coordinates performance of the services.

Abstract: Particular embodiments provide a method for orchestrating an order fulfillment business process that includes a sub-process. In one embodiment, abstraction of business processes from an underlying information technology (IT) infrastructure is provided. An orchestration process can be designed using sub-processes such that the sub-process is assembled at run-time into an executable process. The sub-process may be defined in an interface as a single step. A plurality of services as then assembled as steps in the executable process at run-time.

Abstract: Particular embodiments generally relate to the orchestration of an order fulfillment business process using effectivity dates and versioning. In one embodiment, a plurality of services in the order fulfillment business process are provided. A definition of a business process including one or more services is received from an interface. The one or more services may be defined in steps to be performed in the order fulfillment business process. An effectivity date associated with the definition is also received from the interface. For example, the effectivity date may be associated with the business process or individual steps in the business process and may specify a period of time during which the process or step can be used. The effectivity dates and versioning may then be enforced at run-time.

Abstract: Techniques for dynamic service invocation and dynamic service adaptation in the context of a service oriented application. In one set of embodiments, a plurality of mediator services are introduced between the application and a plurality of actual services accessed by the application. The plurality of mediator services are configured to expose a common, abstract operation. At application runtime, the application determines, via a rules engine, a selection of a mediator service, and invokes the abstract operation by sending an invocation message to the selected mediator service. The selected mediator service transforms (i.e., adapts) the message into a format appropriate for invoking an actual operation exposed by an actual service associated with the selected mediator service. The selected mediator service then invokes the actual operation by sending the transformed message to the actual service.