Abstract: There is disclosed a method and system for executing commands. The method comprises configuring an input event topic subscriber and a command orchestrator process. The input event topic subscriber is invoked. The input event topic subscriber receives an event. The event comprises an event context and associated data. The event is transformed into a command. The command orchestrator is invoked. The command is input to the command orchestrator. The command orchestrator adds contextual information to the command. The command orchestrator schedules execution of the command. The execution of the command is tracked. A returned data object corresponding to the command is received and output.

Abstract: There is disclosed a method and system for executing commands. The method comprises configuring an input event topic subscriber and a command orchestrator process. The input event topic subscriber is invoked. The input event topic subscriber receives an event. The event comprises an event context and associated data. The event is transformed into a command. The command orchestrator is invoked. The command is input to the command orchestrator. The command orchestrator adds contextual information to the command. The command orchestrator schedules execution of the command. The execution of the command is tracked. A returned data object corresponding to the command is received and output.

Abstract: There is disclosed a method and system for operating a workflow. The method comprises receiving, via a workflow editor interface, a user selection of a first artificial intelligence (AI) agent and a second AI agent. A selection of a data source to input to the first AI agent is received. A selection of data to input to the second AI agent is received. The data to input to the second AI agent comprises data output by the first AI agent. A selection of training data for the first AI agent and the second AI agent is received. The first AI agent and the second AI agent are trained using the training data. The first AI agent and the second AI agent are activated. A dashboard interface indicating performance of the first AI agent and the second AI agent is displayed.

Abstract: There is disclosed a method and system for operating an event-driven architecture. The event-driven architecture comprises a first machine-learning (ML) agent operating a first service and a second ML agent operating a second service. The first ML agent comprises a first model and first model metadata. The second ML agent comprises a second model and second model metadata. The method comprises generating, by the first ML agent, an event associated with event metadata. The event comprises results generated by the first model. The event metadata comprises an event identifier (ID). The first ML agent publishes the event in a virtualized dedicated space. The second ML agent determines whether the event is to be processed by the second ML agent. If a determination is made that the message is to be processed by the second ML agent, the second ML agent processes the event to generate an output.

Abstract: Systems and methods for managing multiple robotic agents in an enterprise. The robotic agents share their inputs and outputs with a data coordinator module. The coordinator module, through that data, learns the enterprise's goals and values and learns to optimize robotic agents on both a per section and on a per agent basis. The data is useful for training future versions of the coordinator module as well for training machine learning modules that aim to further the enterprise's goals.

Abstract: Systems and methods for managing and enhancing the performance of a number of robotic agents. An orchestrator module receives work output from a number of robotic agents and determines whether efficiencies can be obtained by rescheduling tasks and/or steps executed by the various robotic agents. As well, the orchestrator learns the various actions and values used by the agents and can check for anomalous actions and/or values. A workstation operated by a human can also send its work output to the orchestrator and this output, along with the steps performed by the human, can be analyzed to determine if the task executed can be done by a robotic agent.

Abstract: The invention relates to a method for request processing. The method includes receiving an asynchronous request for a shared context from a first client, where a second client is subscribed to the shared context. The method further includes receiving a modification of the shared context from the second client and, determining, in response to receiving the modification, that the modification matches a criteria specified in a first request filter, where the first request filter is one of a number of request filters associated with the shared context. The method further includes obtaining the first request filter and after determining that a first condition specified in the first request filter is satisfied, initiating the transmission of the modification to the first client, where the modification is displayed at the first client.

Abstract: The present invention is directed to a method, a computer readable medium and a and a system of managing consumption of computing environment resources by multiple applications that features limiting resource consumption based upon examination of the total real-time resources of a computing environment being consumed rather than by the total resources available. The method includes observing communication between computing resources and multiple applications to obtain a real usage profile (RUP), for one of the multiple applications. A request to consume resources of the computing environment is received for one of the multiple applications. It is determined whether the whether granting access in response to the request violates a desired usage profile (DUP) based upon real usage profile. The computer-readable medium includes computer instructions to facilitate carrying-out of the functions of the claimed method by a general computing system.

Abstract: The invention relates to a method for request processing. The method includes receiving an asynchronous request for a shared context from a first client, where a second client is subscribed to the shared context. The method further includes receiving a modification of the shared context from the second client and, determining, in response to receiving the modification, that the modification matches a criteria specified in a first request filter, where the first request filter is one of a number of request filters associated with the shared context. The method further includes obtaining the first request filter and after determining that a first condition specified in the first request filter is satisfied, initiating the transmission of the modification to the first client, where the modification is displayed at the first client.

Abstract: A method for managing an application server that is configured to execute a plurality of test applications is provided. The method includes the operations of (a) processing a first one of the plurality of test applications, (b) determining if the first application fails to be processed to completion, (c) recording an exception identifying an explanation for the failure if the first test application fails to be processed to completion, (d) refreshing the application server, (e) executing a next one of the plurality of test applications, and (f) repeating operations (a) through (e) if there are remaining ones of the plurality of test applications that still need to be processed.

Abstract: A method for analyzing a test coverage of a software application specification by a test suite is provided. The method includes reading an assertion document for a specification. The assertion document has a corresponding tagged assertion for each assertion in the specification. Each tagged assertion is defined in a markup language. The method also includes reading a static file for defining tests of the test suite. The static file is defined in the markup language. The test suite is divided into tests and each test is divided into test cases. The static file is configured to include an entry for each test case and each entry is configured to include tagged assertions tested by the test case. Also included in the method is correlating each of the tagged assertions in the assertion document with the test cases in the static file so as to determine test coverage of the specification.

Abstract: A method for maintaining standardized test results is provided. The method includes executing a test suite that includes embedded reporter codes and generating uniform test results using the embedded reporter codes. The embedded reporter codes are configured to include data as to anticipated test results and rationale supporting the anticipated test results. The method also includes storing the uniform test results so as to allow viewing of the uniform test results.

Abstract: A system for generating profiled test execution data using a plurality of test suite output files is provided. The system includes a plurality of test suites and a report tool engine. The plurality of test suites is executed creating a plurality of respective test suite output files. The report tool engine is configured to automatically transform each of the plurality of test suite output files to a standardized test execution results file. Each standardized test execution results file has an identical file format. The report tool engine is further configured to profile each of the standardized test execution results file in accordance with a user profile setting, generating a profiled data file.

Abstract: A method for updating Enterprise JavaBeans (EJB) classes is provided. Each EJB class is managed by an application server which maintains a database of active EJB classes. The method includes defining an update plug for an existing EJB class and assigning the update plug to the existing EJB. The method also includes compiling the existing EJB class using the update plug to generate a dependent EJB class. The dependent EJB class uses an adapter and a contract to gain access to methods of the dependent EJB class. Each method of the dependent EJB class is associated with an algorithm that defines a locking timestamp.

Abstract: A system for generating profiled test execution data using a plurality of test suite output files is provided. The system includes a plurality of test suites and a report tool engine. The plurality of test suites is executed creating a plurality of respective test suite output files. The report tool engine is configured to automatically transform each of the plurality of test suite output files to a standardized test execution results file. Each standardized test execution results file has an identical file format. The report tool engine is further configured to profile each of the standardized test execution results file in accordance with a user profile setting, generating a profiled data file.

Abstract: A method for maintaining standardized test results is provided. The method includes executing a test suite that includes embedded reporter codes and generating uniform test results using the embedded reporter codes. The embedded reporter codes are configured to include data as to anticipated test results and rationale supporting the anticipated test results. The method also includes storing the uniform test results so as to allow viewing of the uniform test results.

Abstract: A method for generating accurate test execution results in accordance with a release structure is provided. The method includes receiving the test execution results and inspecting the test execution results to create validated test execution results. The method also includes rejecting the validated test execution results back to an original owner to enable re-validation while the validated test execution results fail to satisfy a particular criteria. The method also includes releasing the validated test execution results to the next level in the release structure if the validated test execution results are acceptable and while a next level in the release structure exists. Also included in the method is rejecting the validated test execution results to the original owner if the validated test execution results are unacceptable. The method further includes posting the validated test execution results that were determined to be acceptable.

Abstract: A method for analyzing a test coverage of a software application specification by a test suite is provided. The method includes reading an assertion document for a specification. The assertion document has a corresponding tagged assertion for each assertion in the specification. Each tagged assertion is defined in a markup language. The method also includes reading a static file for defining tests of the test suite. The static file is defined in the markup language. The test suite is divided into tests and each test is divided into test cases. The static file is configured to include an entry for each test case and each entry is configured to include tagged assertions tested by the test case. Also included in the method is correlating each of the tagged assertions in the assertion document with the test cases in the static file so as to determine test coverage of the specification.

Abstract: A method for managing an application server that is configured to execute a plurality of test applications is provided. The method includes the operations of (a) processing a first one of the plurality of test applications, (b) determining if the first application fails to be processed to completion, (c) recording an exception identifying an explanation for the failure if the first test application fails to be processed to completion, (d) refreshing the application server, (e) executing a next one of the plurality of test applications, and (f) repeating operations (a) through (e) if there are remaining ones of the plurality of test applications that still need to be processed.

Abstract: A method for updating Enterprise JavaBeans (EJB) classes is provided. Each EJB class is managed by an application server which maintains a database of active EJB classes. The method includes defining an update plug for an existing EJB class and assigning the update plug to the existing EJB. The method also includes compiling the existing EJB class using the update plug to generate a dependent EJB class. The dependent EJB class uses an adapter and a contract to gain access to methods of the dependent EJB class. Each method of the dependent EJB class is associated with an algorithm that defines a locking timestamp.