Abstract: An order processing system can include an order processing container, a factory registry, a relationship registry, and synchronization function component. The order processing system can handle orders, which are build plans including a set of tasks. The tasks can specify programmatic actions which may include creation, deletion, and modification of resources and resource topologies. The order processing container can be central engine that programmatically drives order processing actions. The factory registry can support a creation and deletion of resource instances in a resource topology defined by at least one order. The relationship registry can maintain relationships among resources. The synchronization function component can permit transparent usage of shared resources in accordance with shared usage resource topology parameters specified within processed orders.

Abstract: The present invention replaces the prior art Systems Management Flow execution environments with a new Order Processing Environment. The Order Processing Environment consists of an Order Processing Container (“Container” in short), a Relationship Registry, and a Factory Registry. The Factory Registry supports creation of new resource instances. The Relationship Registry stores relationships between resources. The Container gets as input an Order and a start point address for the first resource. The Order is a document (e.g., XML) which includes a number of Tasks for each involved resource without arranging those tasks in a sequence. This differentiates Orders from workflow descriptions used by standard workflow engines. Each Task includes at least all input parameters for executing the Task. The sequence of the Task execution is derived by the Container by using the Relationship Registry which reflects all current Resource Topologies.

Abstract: Orders are processed within an Order Processing Environment which includes an Order Processing Container, Relationship Registry, and Factory Registry. The Order Processing Environment is extended by a Reference Resolvement Function Component. The RRFC provides the basic functionality for resolving References defined in the Order Document at runtime and make the referenced data available as a usual input parameter for the resources involved in the Order Processing. Each Task in the Order may contain Resource Property References and Resource Property Relationship References which are pointers to properties of resources. These references are resolved by the RRFC during the Order Processing before the Order Document is delegated from one resource to the next. When resolving a Reference, the value of the referenced Resource Property is determined and the Reference is replaced by this value so that it can be used by the resource having it defined in its Task section as a usual input parameter.

Abstract: The present invention provides a method and system for automated handling of resolvable and non-resolvable errors in the execution of system management flows by enhancing Workflow Engines (30) by an Error Handling component (40) and by adding a supportive Error Handling Layer (60, 90, 100) to invoked system management tasks which serves as the counterpart to the Workflow Engine's Error Handling component (see FIG. 2). The additional functionality of the task-provided Error Handling Layer (90, 70, 100) is accessible for the Workflow Engine via extended web services interfaces (91, 71, 101). The Workflow Engine's Error Handling component (40) and the task-provided Error Handling Layer allow for the definition of a standard protocol between the Workflow Engine and invoked tasks (31) for automated error handling.

Abstract: An order processing system including an order processing container, a factory registry, a relationship registry, and synchronization function component. The order processing system can handle orders, which are build plans including a set of tasks. The tasks can specify programmatic actions which may include creation, deletion, and modification of resources and resource topologies. The order processing container can be central engine that programmatically drives order processing actions. The factory registry can support a creation and deletion of resource instances in a resource topology defined by at least one order. The relationship registry can maintain relationships among resources. The synchronization function component can permit transparent usage of shared resources in accordance with shared usage resource topology parameters specified within processed orders.

Abstract: The present invention replaces the prior art Systems Management Flow execution environments with a new Order Processing Environment. The Order Processing Environment consists of an Order Processing Container (“Container” in short), a Relationship Registry, and a Factory Registry. The Factory Registry supports creation of new resource instances. The Relationship Registry stores relationships between resources. The Container gets as input an Order and a start point address for the first resource. The Order is a document (e.g., XML) which includes a number of Tasks for each involved resource without arranging those tasks in a sequence. This differentiates Orders from workflow descriptions used by standard workflow engines. Each Task includes at least all input parameters for executing the Task. The sequence of the Task execution is derived by the Container by using the Relationship Registry which reflects all current Resource Topologies.

Abstract: Orders are processed within an Order Processing Environment which includes an Order Processing Container, Relationship Registry, and Factory Registry. The Order Processing Environment is extended by a Reference Resolvement Function Component. The RRFC provides the basic functionality for resolving References defined in the Order Document at runtime and make the referenced data available as a usual input parameter for the resources involved in the Order Processing. Each Task in the Order may contain Resource Property References and Resource Property Relationship References which are pointers to properties of resources. These references are resolved by the RRFC during the Order Processing before the Order Document is delegated from one resource to the next. When resolving a Reference, the value of the referenced Resource Property is determined and the Reference is replaced by this value so that it can be used by the resource having it defined in its Task section as a usual input parameter.

Abstract: The present invention provides a method and system for automated handling of resolvable and non-resolvable errors in the execution of system management flows by enhancing Workflow Engines (30) by an Error Handling component (40) and by adding a supportive Error Handling Layer (60,90,100) to invoked system management tasks which serves as the counterpart to the Workflow Engine's Error Handling component (see FIG. 2). The additional functionality of the task-provided Error Handling Layer (90, 70, 100) is accessible for the Workflow Engine via extended web services interfaces (91, 71, 101). The Workflow Engine's Error Handling component (40) and the task-provided Error Handling Layer allow for the definition of a standard protocol between the Workflow Engine and invoked tasks (31) for automated error handling.