Abstract: A mainframe workflow method manages workflow tasks in a mainframe workflow management system. The method includes selecting, by a user terminal, a target mainframe computing system from a plurality of target mainframe computing systems for execution of a mainframe workflow process having a plurality of workflow tasks, and transmitting the plurality of workflow tasks to the selected target mainframe computing system over a communication network. The method also includes storing the plurality of workflow tasks, in a workflow file repository at the target mainframe computing system, and checking the plurality of workflow tasks for inter-task dependencies.

Abstract: Systems and methods for application performance management across one or more networks are disclosed. A system includes a plurality of geographically distributed computing devices executing one or more applications. A plurality of collectors are distributed across the one or more networks, each collector being positioned proximate a respective computing device. The collectors may sample, by each of the plurality of collectors, a plurality of trace events received from the applications executing on the computing devices proximate the collector. The collectors may retain in memory sampled trace events that meet a configurable attribute. The collectors may use probabilistic sets and tail-based sampling to determine root events and policies for identifying relevant traces. Benefits can be achieved in bandwidth savings, network cost and cyber security.

Abstract: Systems and methods for application performance management across one or more networks are disclosed. A system includes a plurality of geographically distributed computing devices executing one or more applications. A plurality of collectors are distributed across the one or more networks, each collector being positioned proximate a respective computing device. The collectors may sample, by each of the plurality of collectors, a plurality of trace events received from the applications executing on the computing devices proximate the collector. The collectors may retain in memory sampled trace events that meet a configurable attribute. The collectors may use probabilistic sets and tail-based sampling to determine root events and policies for identifying relevant traces. Benefits can be achieved in bandwidth savings, network cost and cyber security.

Abstract: Method and apparatus for navigating along a vessel network of a body. An imaging catheter has an elongated body with opposing ends and a central lumen extending therethrough. A plurality of forward-facing imaging sensors are disposed at at least a first end, and a push wire is affixed to the second end. The central lumen is sized to allow passage of a deployable structure, such as a stent or an inflatable balloon, through the imaging catheter along a guide wire to a target location. The imaging catheter is configured for advancement and retraction to successively image the target location, the structure in the undeployed state, and the structure in the deployed state. Intravascular ultrasound (IVUS) or other types of image data can be captured. An external imaging system can additionally be used to provide top-down, 2D and/or 3D imaging of the catheter and structure at the target location.

Abstract: Systems and methods for application performance management across one or more networks are disclosed. A system includes a plurality of geographically distributed computing devices executing one or more applications. A plurality of collectors are distributed across the one or more networks, each collector being positioned proximate a respective computing device. The collectors may sample, by each of the plurality of collectors, a plurality of trace events received from the applications executing on the computing devices proximate the collector. The collectors may retain in memory sampled trace events that meet a configurable attribute. The collectors may use probabilistic sets and tail-based sampling to determine root events and policies for identifying relevant traces. Benefits can be achieved in bandwidth savings, network cost and cyber security.

Abstract: A mainframe workflow method manages workflow tasks in a mainframe workflow management system. The method includes selecting, by a user terminal, a target mainframe computing system from a plurality of target mainframe computing systems for execution of a mainframe workflow process having a plurality of workflow tasks, and transmitting the plurality of workflow tasks to the selected target mainframe computing system over a communication network. The method also includes storing the plurality of workflow tasks, in a workflow file repository at the target mainframe computing system, and checking the plurality of workflow tasks for inter-task dependencies.

Abstract: A mainframe workflow creation method creates and manages managing workflow tasks in a mainframe workflow management system. The method includes activating a workflow creation engine in the mainframe workflow management system by a user of a computing device using a web dashboard, communicating with the mainframe workflow management system over a communication network, and creating workflow tasks corresponding to a mainframe workflow. The method also includes associating the workflow tasks with a mainframe workflow process, and selecting a target mainframe computing system from a plurality of target mainframe computing systems for execution of the mainframe workflow process. The method further includes transmitting the mainframe workflow process to the selected target mainframe computing system over the communication network, and executing the mainframe workflow process, including plurality of workflow tasks, by the selected target mainframe computing system.

Abstract: A mainframe workflow creation method creates and manages managing workflow tasks in a mainframe workflow management system. The method includes activating a workflow creation engine in the mainframe workflow management system by a user of a computing device using a web dashboard, communicating with the mainframe workflow management system over a communication network, and creating workflow tasks corresponding to a mainframe workflow. The method also includes associating the workflow tasks with a mainframe workflow process, and selecting a target mainframe computing system from a plurality of target mainframe computing systems for execution of the mainframe workflow process. The method further includes transmitting the mainframe workflow process to the selected target mainframe computing system over the communication network, and executing the mainframe workflow process, including plurality of workflow tasks, by the selected target mainframe computing system.

Abstract: Embodiments of the present invention are directed to a computer implemented web based unified workflow management system and method for reducing complexity and building repeatable mainframe workflows by creating and managing workflow tasks associated with at least one mainframe workflow. The system and method provide a workflow creation engine for creating at least one mainframe workflow task associated with the at least one mainframe workflow, the at least one mainframe workflow task including an execution target destination, a mainframe process, and a success criteria. The system and method further provide a web dashboard that displays the details and results of the mainframe workflow tasks associated with a mainframe workflow, and allows a user to monitor and control the mainframe workflow, and its associated tasks. The system and method further comprise a workflow task dependency manager for creating global task dependencies between tasks associated with the at least one mainframe workflow.

Abstract: An approach is provided that receives a set of tracking data from a monitored activity. The set of tracking data includes name-value pairs. The received set name-value pairs are compared with context masks. Each context mask include one or more name-filter pairs. One of the sets of context masks is selected in response to determining that the incoming name-value pairs matches the mask name-filter pairs of the selected context mask. Name-value pairs are selected based upon the selected context mask. The selected name-value pairs are then stored in an aggregate data store. If the received set of tracking data fails to match at least one of the name-filter pairs then the received set of tracking data is disregarded and none of the name-value pairs are stored in the aggregate data store.

Abstract: In a variable torque rate test joint, screw-threaded first and second elements are rotated relative to one another by a tool under test. At least one spring beam is cantilevered over a pivot point to exert an axial force between the first and second elements and the torque rate of the test joint can be varied by moving the pivot point to change the axial force. The first element may be a shaft that is fixed during testing and the second element is a nut rotatably mounted on the shaft, whereby the element rotated by the tool has a minimal moment of inertia. Whichever of the first and second elements is held stationary during the test may be mounted in a hub that is locked during the test but can be rotated at the end of the test to reset the test joint. Measurements may be made of the torque and the rotation angle to derive an actual torque rate of the joint, which allows correction of errors by moving the pivot point.

Abstract: An API can be extended to automatically correlate events based on context. Started events for each context (e.g. threads of execution) are maintained on independent stacks. When an instrumented application starts a new transaction, the API generates a started event. A transaction correlation unit within the API can determine if the new transaction started during a previous transaction. If there is a previous started event on the stack, the new transaction started during the previous transaction. The transaction correlation unit can insert an outbound indicator into the new started event to associate the new transaction and the previous transaction. Then, the new started event can be pushed on the stack.

Abstract: In a variable torque rate test joint, screw-threaded first and second elements are rotated relative to one another by a tool under test. At least one spring beam is cantilevered over a pivot point to exert an axial force between the first and second elements and the torque rate of the test joint can be varied by moving the pivot point to change the axial force. The first element may be a shaft that is fixed during testing and the second element is a nut rotatably mounted on the shaft, whereby the element rotated by the tool has a minimal moment of inertia. Whichever of the first and second elements is held stationary during the test may be mounted in a hub that is locked during the test but can be rotated at the end of the test to reset the test joint. Measurements may be made of the torque and the rotation angle to derive an actual torque rate of the joint, which allows correction of errors by moving the pivot point.

Abstract: An approach is provided that receives a set of tracking data from a monitored activity. The set of tracking data includes name-value pairs. The received set name-value pairs are compared with context masks. Each context mask include one or more name-filter pairs. One of the sets of context masks is selected in response to determining that the incoming name-value pairs matches the mask name-filter pairs of the selected context mask. Name-value pairs are selected based upon the selected context mask. The selected name-value pairs are then stored in an aggregate data store. If the received set of tracking data fails to match at least one of the name-filter pairs then the received set of tracking data is disregarded and none of the name-value pairs are stored in the aggregate data store.

Abstract: A computer implemented method, apparatus, and computer usable program code for the distributed monitoring of a SOAP service is provided. A test configuration file specifying a test input is distributed from a central reporting location to at least one remote data processing system that has access to a SOAP service to be tested. The test configuration file is created without accessing the SOAP service to be tested. Furthermore, the user that created the test configuration file is not allowed access to the SOAP service to be tested.

Abstract: An API can be extended to automatically correlate events based on context. Started events for each context (e.g. threads of execution) are maintained on independent stacks. When an instrumented application starts a new transaction, the API generates a started event. A transaction correlation unit within the API can determine if the new transaction started during a previous transaction. If there is a previous started event on the stack, the new transaction started during the previous transaction. The transaction correlation unit can insert an outbound indicator into the new started event to associate the new transaction and the previous transaction. Then, the new started event can be pushed on the stack.

Abstract: A computer implemented method, apparatus, and computer usable program code for the distributed monitoring of a SOAP service is provided. A test configuration file specifying a test input is distributed from a central reporting location to at least one remote data processing system that has access to a SOAP service to be tested. The test configuration file is created without accessing the SOAP service to be tested. Furthermore, the user that created the test configuration file is not allowed access to the SOAP service to be tested.

Abstract: A method of forming a liposomal pharmaceutical composition containing the compound: from a feedstock solution of the compound, comprises the steps of assaying a permeate wash for HSPC and cholesterol; processing the permeate wash to form a concentrated solution of the compound if the assay result is lower or equal to a predetermined value; and adding the concentrated solution to the feedstock solution.