Abstract: Described herein are systems and methods for implementing a task assignment protocol. In one or more embodiments, a task management system receives task data and resource data. Responsive to the receipt, the task management system receives input for selection of a resource. A candidate subset of tasks that match the properties of the resource is then identified. Upon receipt of selection of the candidate task, a task icon updates. The task icon may update to reflect the resource identifier associated the assigned resource. Additionally, or alternatively, a resource icon is updated to reflect the availability of the resource. The protocol repeats until one or more resources are allocated to the tasks. A resource chart additionally displays to aid in evaluation of resource availability.

Abstract: Described herein are systems and methods for implementing a task assignment protocol. In one or more embodiments, a task management system receives task data and resource data. Responsive to the receipt, the task management system receives input for selection of a resource. A candidate subset of tasks that match the properties of the resource is then identified. Upon receipt of selection of the candidate task, a task icon updates. The task icon may update to reflect the resource identifier associated the assigned resource. Additionally, or alternatively, a resource icon is updated to reflect the availability of the resource. The protocol repeats until one or more resources are allocated to the tasks. A resource chart additionally displays to aid in evaluation of resource availability.

Abstract: Described herein are systems and methods for implementing a task assignment protocol. In one or more embodiments, a task management system receives task data and resource data. Responsive to the receipt, the task management system receives input for selection of a resource. A candidate subset of tasks that match the properties of the resource is then identified. Upon receipt of selection of the candidate task, a task icon updates. The task icon may update to reflect the resource identifier associated the assigned resource. Additionally, or alternatively, a resource icon is updated to reflect the availability of the resource. The protocol repeats until one or more resources are allocated to the tasks. A resource chart additionally displays to aid in evaluation of resource availability.

Abstract: Described herein are systems and methods for implementing a task assignment protocol. In one or more embodiments, a task management system receives task data and resource data. Responsive to the receipt, the task management system receives input for selection of a resource. A candidate subset of tasks that match the properties of the resource is then identified. Upon receipt of selection of the candidate task, a task icon updates. The task icon may update to reflect the resource identifier associated the assigned resource. Additionally, or alternatively, a resource icon is updated to reflect the availability of the resource. The protocol repeats until one or more resources are allocated to the tasks. A resource chart additionally displays to aid in evaluation of resource availability.

Abstract: A method of recovering batch-based processes may include providing an interface for receiving processes recoverability information. The recoverability information may include (i) information describing a mutual exclusivity of data affected by a process, (ii) information describing sub-processes associated with the process, and/or (iii) information describing scope cleanup procedures associated with the process. The method may also include receiving the recoverability information through the interface, and receiving an indication that the process experienced an error while being executed on a client system. The method may additionally include providing the process recoverability information to make a recoverability determination for the process.

Abstract: A method of recovering batch-based processes may include providing an interface for receiving processes recoverability information. The recoverability information may include (i) information describing a mutual exclusivity of data affected by a process, (ii) information describing sub-processes associated with the process, and/or (iii) information describing scope cleanup procedures associated with the process. The method may also include receiving the recoverability information through the interface, and receiving an indication that the process experienced an error while being executed on a client system. The method may additionally include providing the process recoverability information to make a recoverability determination for the process.

Abstract: Embodiments of the invention provide systems and methods for recovering a failed data summarization. According to one embodiment, recovering a failed instance can comprise processing existing summarization instances identified as instances for which a new data summarization instance needs to wait. Upon a completion or a timeout of each of the instances identified as instances for which the new data summarization instance needs to wait, an exclusive lock can be acquired on a table storing scope information for the plurality of data summarization instances. One or more existing data summarization instances that match the new data summarization instance or that have an overlapping scope with the new data summarization instance can be processed, remaining tasks to be performed by the new data summarization instance can be defined, the exclusive lock can be released, and the remaining tasks to be performed by the new data summarization instance can be performed.

Abstract: Embodiments of the invention provide systems and methods for providing summarizations of data and transactions based on the status of the summarization and the data and transactions being summarized. According to one embodiment, a method for providing summarizations of data and transactions related to one or more applications can comprise initiating a first summarization of the data and transactions related to the one or more applications. The first summarization can be paused in response to a request to evaluate the data and transactions being summarized. Data and transactions available for summarization can be evaluated in response to and based on the request. The first summarization can be resumed upon a completion or a timeout of the evaluating of the data and transactions being summarized.

Abstract: Extraction methods can interact on a common data source using identifiers that correspond to events or other actions. These identifiers can be updated, whenever appropriate, once the corresponding data has been summarized, in order to provide for multiple extraction methods to operate only on the data of interest, and obtain a lock only on the data within the scope of extraction. High water marks, such as identifiers in the sequent, can be used to further designate which data has previously been extracted. Similarly, summarization methods can interact by utilizing corresponding persistent tables in the flows for the methods, but utilizing separate intermediate tables to allow for data transformations and application of various business rules and tuning techniques. The ability to switch between different methods can accommodate business, performance, or other such needs, and can provide for the dynamic extraction and summarization of different volumes of data.

Abstract: Embodiments of the invention provide systems and methods for recovering a failed data summarization. According to one embodiment, recovering a failed instance can comprise processing existing summarization instances identified as instances for which a new data summarization instance needs to wait. Upon a completion or a timeout of each of the instances identified as instances for which the new data summarization instance needs to wait, an exclusive lock can be acquired on a table storing scope information for the plurality of data summarization instances. One or more existing data summarization instances that match the new data summarization instance or that have an overlapping scope with the new data summarization instance can be processed, remaining tasks to be performed by the new data summarization instance can be defined, the exclusive lock can be released, and the remaining tasks to be performed by the new data summarization instance can be performed.

Abstract: Embodiments of the invention provide systems and methods for providing summarizations of data and transactions based on the status of the summarization and the data and transactions being summarized. According to one embodiment, a method for providing summarizations of data and transactions related to one or more applications can comprise initiating a first summarization of the data and transactions related to the one or more applications. The first summarization can be paused in response to a request to evaluate the data and transactions being summarized. Data and transactions available for summarization can be evaluated in response to and based on the request. The first summarization can be resumed upon a completion or a timeout of the evaluating of the data and transactions being summarized.

Abstract: A method of summarizing data includes providing a multi-method summarization program including instructions for summarizing data for a transaction processing system. At least one functional aspect of the transaction processing system for which a summarization of a subset of the data is desired is determined. The functional subset to a user as a light summarization program is exposed. The dependencies of the functional subset can be enforced at runtime allowing packaging flexibility. A method for efficient parallel processing involving not necessarily filled requests for help.

Abstract: A method for consuming data includes determining a scope of summarization for a data set in response to receiving a request from a summarization program, obtaining a lock on the data within the scope of summarization and consuming the data from the summarization program within the scope of data summarization. The summarization program includes methods configured to obtain concurrent locks on different portions of the data set. The consumption of the data may be governed by specific rules.

Abstract: Summarization methods can interact on a common data source using identifiers that correspond to events or other actions. These identifiers can be updated, whenever appropriate, once the corresponding data has been summarized, in order to provide for multiple extraction methods to operate only on the data of interest, and obtain a lock only on the data within the scope of extraction. High water marks, such as identifiers in the sequent, can be used to further designate which data has previously been extracted. Similarly, summarization methods can interact by utilizing corresponding persistent tables in the flows for the methods, but utilizing separate intermediate tables to allow for data transformations and application of various business rules and tuning techniques. The ability to switch between different methods can accommodate business, performance, or other such needs, and can provide for the dynamic extraction and summarization of different volumes of data.

Abstract: A method of summarizing data includes providing a multi-method summarization program including instructions for summarizing data for a transaction processing system. At least one functional aspect of the transaction processing system for which a summarization of a subset of the data is desired is determined. The functional subset to a user as a light summarization program is exposed. The dependencies of the functional subset can be enforced at runtime allowing packaging flexibility. A method for efficient parallel processing involving not necessarily filled requests for help.

Abstract: A method for consuming data includes determining a scope of summarization for a data set in response to receiving a request from a summarization program, obtaining a lock on the data within the scope of summarization and consuming the data from the summarization program within the scope of data summarization. The summarization program includes methods configured to obtain concurrent locks on different portions of the data set. The consumption of the data may be governed by specific rules.

Abstract: Extraction methods can interact on a common data source using identifiers that correspond to events or other actions. These identifiers can be updated, whenever appropriate, once the corresponding data has been summarized, in order to provide for multiple extraction methods to operate only on the data of interest, and obtain a lock only on the data within the scope of extraction. High water marks, such as identifiers in the sequent, can be used to further designate which data has previously been extracted. Similarly, summarization methods can interact by utilizing corresponding persistent tables in the flows for the methods, but utilizing separate intermediate tables to allow for data transformations and application of various business rules and tuning techniques. The ability to switch between different methods can accommodate business, performance, or other such needs, and can provide for the dynamic extraction and summarization of different volumes of data.

Abstract: Summarization methods can interact on a common data source using identifiers that correspond to events or other actions. These identifiers can be updated, whenever appropriate, once the corresponding data has been summarized, in order to provide for multiple extraction methods to operate only on the data of interest, and obtain a lock only on the data within the scope of extraction. High water marks, such as identifiers in the sequent, can be used to further designate which data has previously been extracted. Similarly, summarization methods can interact by utilizing corresponding persistent tables in the flows for the methods, but utilizing separate intermediate tables to allow for data transformations and application of various business rules and tuning techniques. The ability to switch between different methods can accommodate business, performance, or other such needs, and can provide for the dynamic extraction and summarization of different volumes of data.