Patent application number | Description | Published |
20130111499 | APPLICATION ACCESS TO LDAP SERVICES THROUGH A GENERIC LDAP INTERFACE INTEGRATING A MESSAGE QUEUE | 05-02-2013 |
20130111500 | MESSAGE QUEUING APPLICATION ACCESS TO SPECIFIC API SERVICES THROUGH A GENERIC API INTERFACE INTERGRATING A MESSAGE QUEUE | 05-02-2013 |
20130179446 | Linking Single System Synchronous Inter-Domain Transaction Activity - An approach is provided to correlate transaction data occurring at two different domains running on a common operating system image without using static, or common, correlators. Request-type event records are collected at a first domain within the operating system image, with each of the request-type event records including execution identifiers and a unique token that indicates the order in which the corresponding request-type event occurred on the first domain. Similarly, response-type event records are collected at a second domain within the operating system image. The request-type event records are matched with the response-type event records based on the execution identifiers and an overall order that is indicated by unique tokens included in the records. The matching of request-type event records with response-type event records indicate a number of inter-domain transactions which are recorded in a correlation data store. | 07-11-2013 |
20130179448 | Linking Single System Synchronous Inter-Domain Transaction Activity - An approach is provided to correlate transaction data occurring at two different domains running on a common operating system image without using static, or common, correlators. Request-type event records are collected at a first domain within the operating system image, with each of the request-type event records including execution identifiers and a unique token that indicates the order in which the corresponding request-type event occurred on the first domain. Similarly, response-type event records are collected at a second domain within the operating system image. The request-type event records are matched with the response-type event records based on the execution identifiers and an overall order that is indicated by unique tokens included in the records. The matching of request-type event records with response-type event records indicate a number of inter-domain transactions which are recorded in a correlation data store. | 07-11-2013 |
20130226985 | MONITORING A PATH OF A TRANSACTION ACROSS A COMPOSITE APPLICATION - At each intermediate transaction hop from among multiple transaction hops in a transaction flow through a composite application, an entry with tracking data for a current transaction hop of the multiple transaction hops is inserted into a tracking envelope associated with the transaction flow and the tracking envelope is passed to a next transaction hop of the transaction hops in the transaction flow. At a final transaction hop of the multiple transaction hops, a final entry with tracking data for the final transaction hop is inserted into the tracking envelope and the multiple entries with tracking data for each of the transaction hops in the tracking envelope are exposed in a single tracking event. | 08-29-2013 |
20130227121 | MONITORING A PATH OF A TRANSACTION ACROSS A COMPOSITE APPLICATION - At each intermediate transaction hop from among multiple transaction hops in a transaction flow through a composite application, an entry with tracking data for a current transaction hop of the multiple transaction hops is inserted into a tracking envelope associated with the transaction flow and the tracking envelope is passed to a next transaction hop of the transaction hops in the transaction flow. At a final transaction hop of the multiple transaction hops, a final entry with tracking data for the final transaction hop is inserted into the tracking envelope and the multiple entries with tracking data for each of the transaction hops in the tracking envelope are exposed in a single tracking event. | 08-29-2013 |
20140006606 | Message Queue Transaction Tracking Using Application Activity Trace Data | 01-02-2014 |
20140108641 | TRANSACTION MIDDLEWARE BASED APPLICATION LEVEL TRANSACTION INSTANCE TRACKING ACROSS A COMPOSITE APPLICATION - Responsive to transactional middleware for a particular domain processing a particular transaction instance at a processing point specified in transaction telemetry standards as a tracking point along a flow of the particular transaction, a facility of the middleware accesses correlation data for the particular transaction instance in the particular domain and extracts application level context information about the particular transaction instance from the particular domain, wherein the transaction telemetry standards specify a same set of standards for application by each separate transactional middleware instance of a composite application. At least one facility of the transactional middleware creates a tracking event comprising the correlation data and the application level context information formatted into an event structure defined by the transaction tracking standards. At least one facility of the transactional middleware surfaces the tracking event in compliance with the transaction telemetry standards. | 04-17-2014 |
20140108646 | TRANSACTION MIDDLEWARE BASED APPLICATION LEVEL TRANSACTION INSTANCE TRACKING ACROSS A COMPOSITE APPLICATION - Responsive to transactional middleware for a particular domain processing a particular transaction instance at a processing point specified in transaction telemetry standards as a tracking point along a flow of the particular transaction, a facility of the middleware accesses correlation data for the particular transaction instance in the particular domain and extracts application level context information about the particular transaction instance from the particular domain, wherein the transaction telemetry standards specify a same set of standards for application by each separate transactional middleware instance of a composite application. At least one facility of the transactional middleware creates a tracking event comprising the correlation data and the application level context information formatted into an event structure defined by the transaction tracking standards. At least one facility of the transactional middleware surfaces the tracking event in compliance with the transaction telemetry standards. | 04-17-2014 |