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: The idea of the present invention is to provide a challenge-response mechanism to acquire work scope split range information from the application's Work Scope Split component of the over-utilized resource. By using the work scope split range information, the provisioning system is able to add a new resource, install a new application for that new resource, configure the new and the over-utilized resource's application, and reconfigure the load-balancer in accordance with the work scope split range information. The present invention adds scalability to complex and stateful application programs and allows dynamic provisioning of resources for these application programs.

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: A method and system for automated error handling in system management flows by enhancing workflow engines by an error handling component and by adding a supportive error handling layer to invoked system management tasks which serves as the counterpart to the workflow engine's error handling component. The additional functionality of the task-provided error handling layer is accessible for the workflow engine via extended Web services interfaces. The workflow engine's error handling component and the task-provided error handling layer allow for the definition of a standard protocol between the workflow engine and invoked tasks for automated error handling. Furthermore, an interface and method of communication between the enhanced workflow engine and an external error resolving device (such as an expert system) is defined with the purpose of using the external error resolving device for automatic error recovery.

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: A method and system for automated error handling in system management flows by enhancing workflow engines by an error handling component and by adding a supportive error handling layer to invoked system management tasks which serves m the counterpart to the workflow engine's error handling component. The additional functionality of the task-provided, error handling layer is accessible for the workflow engine via extended Web services interfaces. The workflow engine's error handling component and the task-provided error handling layer allow for the definition of a standard protocol between the workflow engine and invoked tasks for automated error handling. Furthermore, an interface and method of communication between the enhanced workflow engine and an external error resolving device (such as an expert system) is defined with the purpose of using the external error resolving device for automatic error recovery.

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: The idea of the present invention is to provide a challenge-response mechanism to acquire work scope split range information from the application's Work Scope Split component of the over-utilized resource. By using the work scope split range information, the provisioning system is able to add a new resource, install a new application for that new resource, configure the new and the over-utilized resource's application, and reconfigure the load-balancer in accordance with the work scope split range information. The present invention adds scalability to complex and stateful application programs and allows dynamic provisioning of resources for these application programs.

Abstract: The idea of the present invention is to provide a challenge-response mechanism to acquire work scope split range information from the application's Work Scope Split component of the over-utilized resource. By using the work scope split range information, the provisioning system is able to add a new resource, install a new application for that new resource, configure the new and the over-utilized resource's application, and reconfigure the load-balancer in accordance with the work scope split range information. The present invention adds scalability to complex and stateful application programs and allows dynamic provisioning of resources for these application programs.

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: The invention relates to a method and a scheduling system for scheduling a job, the job having at least one job requirement and being indicative of a scheduling policy of at least first and second scheduling policies, the method comprising the steps of: (a) performing a query in order to identify data processing resources matching the at least one job requirement and obtaining input data for the selected scheduling policy; and (b) selecting one of the matching resources by means of the selected scheduling policy on the basis of the input data.

Abstract: The idea of the present invention is to provide a challenge-response mechanism to acquire work scope split range information from the application's Work Scope Split component of the over-utilized resource. By using the work scope split range information, the provisioning system is able to add a new resource, install a new application for that new resource, configure the new and the over-utilized resource's application, and reconfigure the load-balancer in accordance with the work scope split range information. The present invention adds scalability to complex and stateful application programs and allows dynamic provisioning of resources for these application programs.