US20130179448A1 - Linking Single System Synchronous Inter-Domain Transaction Activity - Google Patents

Linking Single System Synchronous Inter-Domain Transaction Activity Download PDF

Info

Publication number
US20130179448A1
US20130179448A1 US13/344,385 US201213344385A US2013179448A1 US 20130179448 A1 US20130179448 A1 US 20130179448A1 US 201213344385 A US201213344385 A US 201213344385A US 2013179448 A1 US2013179448 A1 US 2013179448A1
Authority
US
United States
Prior art keywords
type event
event records
request
response
domain
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US13/344,385
Other languages
English (en)
Inventor
Bret William Dixon
Scot Dixon
Simon Teverey Huband
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
International Business Machines Corp
Original Assignee
International Business Machines Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by International Business Machines Corp filed Critical International Business Machines Corp
Priority to US13/344,385 priority Critical patent/US20130179448A1/en
Assigned to INTERNATIONAL BUSINESS MACHINES CORPORATION reassignment INTERNATIONAL BUSINESS MACHINES CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: DIXON, BRET WILLIAM, DIXON, SCOT, HUBAND, SIMON TEVEREY
Priority to DE102012224270A priority patent/DE102012224270A1/de
Priority to CN2013100010047A priority patent/CN103279380A/zh
Priority to GB1300166.4A priority patent/GB2499877A/en
Priority to US13/754,851 priority patent/US10216600B2/en
Publication of US20130179448A1 publication Critical patent/US20130179448A1/en
Priority to US16/176,814 priority patent/US10824646B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/28—Databases characterised by their database models, e.g. relational or object models
    • G06F16/284—Relational databases
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/466—Transaction processing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data

Definitions

  • the present disclosure relates to an approach that links synchronous transaction activity that occurs in different domains.
  • the present disclosure links the activity without use of static correlators.
  • Transaction tracking technologies focus on tracking composite applications across multiple technologies, protocols, domains (middleware stacks) and operating systems. Tracking is often achieved by instrumenting targeted software with tracking agents which generate tracking events at strategic points in the application flow. Collected tracking events can be analyzed to determine application metrics and topology.
  • One of the challenges for transaction tracking is topology building. Making the necessary associations between requests from an application in one domain with the corresponding requests in the adjacent domain can be difficult. For example, a first transaction process running on an operating system may request a service from a second process, such as a queue manager. Transaction tracking needs be able to match the request from the first transaction process with the response from the second process in order to track the interaction between the two processes.
  • Traditional transaction tracking technologies generally employ a correlator to make the association between corresponding inter-domain transaction interactions.
  • a correlator may be passed from the source domain to the target domain (static correlator) or may be generated independently on each domain using common but unique data (dynamic correlator). In either case, matching correlators are used to associate transaction interactions.
  • 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.
  • response-type event records are collected at a second domain within the operating system image, with each of the response-type event records also including the execution identifiers and a unique token that indicates the order in which the corresponding response-type event occurred.
  • 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.
  • an approach that intercepts an inter-domain event that occurs between a first domain and a second domain.
  • the type of the inter-domain event is identified as being either a “request” or a “response” event.
  • Execution identifiers pertaining to the inter-domain event are gathered, such as the system identifier, the process identifier, and the thread identifier.
  • a unique token that indicates an order that the inter-domain event occurred is generated, such as a timestamp-based token.
  • the gathered execution identifiers, generated unique token, and the type of inter-domain event are stored in a data store for future transaction correlation processing with data gathered from another domain.
  • FIG. 1 is a block diagram of a data processing system in which the methods described herein can be implemented
  • FIG. 2 provides an extension of the information handling system environment shown in FIG. 1 to illustrate that the methods described herein can be performed on a wide variety of information handling systems which operate in a networked environment;
  • FIG. 3 is a high-level diagram showing instrumentation collecting data at two domains without use of common correlators
  • FIG. 4 is a flowchart showing steps taken by processes running on two domains within a common operating system and collecting instrumentation data for future process correlation;
  • FIG. 5 is a flowchart showing steps performed by data collector process running on each domain.
  • FIG. 6 is a flowchart showing steps performed by the correlation process to correlate the instrumentation data gathered during execution of processes running on the domains of the operating system.
  • FIG. 1 A computing environment in FIG. 1 that is suitable to implement the software and/or hardware techniques associated with the invention.
  • FIG. 2 A networked environment is illustrated in FIG. 2 as an extension of the basic computing environment, to emphasize that modern computing techniques can be performed across multiple discrete devices.
  • FIG. 1 illustrates information handling system 100 , which is a simplified example of a computer system capable of performing the computing operations described herein.
  • Information handling system 100 includes one or more processors 110 coupled to processor interface bus 112 .
  • Processor interface bus 112 connects processors 110 to Northbridge 115 , which is also known as the Memory Controller Hub (MCH).
  • Northbridge 115 connects to system memory 120 and provides a means for processor(s) 110 to access the system memory.
  • Graphics controller 125 also connects to Northbridge 115 .
  • PCI Express bus 118 connects Northbridge 115 to graphics controller 125 .
  • Graphics controller 125 connects to display device 130 , such as a computer monitor.
  • Northbridge 115 and Southbridge 135 connect to each other using bus 119 .
  • the bus is a Direct Media Interface (DMI) bus that transfers data at high speeds in each direction between Northbridge 115 and Southbridge 135 .
  • a Peripheral Component Interconnect (PCI) bus connects the Northbridge and the Southbridge.
  • Southbridge 135 also known as the I/O Controller Hub (ICH) is a chip that generally implements capabilities that operate at slower speeds than the capabilities provided by the Northbridge.
  • Southbridge 135 typically provides various busses used to connect various components. These busses include, for example, PCI and PCI Express busses, an ISA bus, a System Management Bus (SMBus or SMB), and/or a Low Pin Count (LPC) bus.
  • PCI and PCI Express busses an ISA bus
  • SMB System Management Bus
  • LPC Low Pin Count
  • the LPC bus often connects low-bandwidth devices, such as boot ROM 196 and “legacy” I/O devices (using a “super I/O” chip).
  • the “legacy” I/O devices ( 198 ) can include, for example, serial and parallel ports, keyboard, mouse, and/or a floppy disk controller.
  • the LPC bus also connects Southbridge 135 to Trusted Platform Module (TPM) 195 .
  • TPM Trusted Platform Module
  • Other components often included in Southbridge 135 include a Direct Memory Access (DMA) controller, a Programmable Interrupt Controller (PIC), and a storage device controller, which connects Southbridge 135 to nonvolatile storage device 185 , such as a hard disk drive, using bus 184 .
  • DMA Direct Memory Access
  • PIC Programmable Interrupt Controller
  • storage device controller which connects Southbridge 135 to nonvolatile storage device 185 , such as a hard disk drive, using bus 184 .
  • ExpressCard 155 is a slot that connects hot-pluggable devices to the information handling system.
  • ExpressCard 155 supports both PCI Express and USB connectivity as it connects to Southbridge 135 using both the Universal Serial Bus (USB) the PCI Express bus.
  • Southbridge 135 includes USB Controller 140 that provides USB connectivity to devices that connect to the USB. These devices include webcam (camera) 150 , infrared (IR) receiver 148 , keyboard and trackpad 144 , and Bluetooth device 146 , which provides for wireless personal area networks (PANs).
  • webcam camera
  • IR infrared
  • keyboard and trackpad 144 keyboard and trackpad 144
  • Bluetooth device 146 which provides for wireless personal area networks (PANs).
  • USB Controller 140 also provides USB connectivity to other miscellaneous USB connected devices 142 , such as a mouse, removable nonvolatile storage device 145 , modems, network cards, ISDN connectors, fax, printers, USB hubs, and many other types of USB connected devices. While removable nonvolatile storage device 145 is shown as a USB-connected device, removable nonvolatile storage device 145 could be connected using a different interface, such as a Firewire interface, etcetera.
  • Wireless Local Area Network (LAN) device 175 connects to Southbridge 135 via the PCI or PCI Express bus 172 .
  • LAN device 175 typically implements one of the IEEE 802.11 standards of over-the-air modulation techniques that all use the same protocol to wireless communicate between information handling system 100 and another computer system or device.
  • Optical storage device 190 connects to Southbridge 135 using Serial ATA (SATA) bus 188 .
  • Serial ATA adapters and devices communicate over a high-speed serial link.
  • the Serial ATA bus also connects Southbridge 135 to other forms of storage devices, such as hard disk drives.
  • Audio circuitry 160 such as a sound card, connects to Southbridge 135 via bus 158 .
  • Audio circuitry 160 also provides functionality such as audio line-in and optical digital audio in port 162 , optical digital output and headphone jack 164 , internal speakers 166 , and internal microphone 168 .
  • Ethernet controller 170 connects to Southbridge 135 using a bus, such as the PCI or PCI Express bus. Ethernet controller 170 connects information handling system 100 to a computer network, such as a Local Area Network (LAN), the Internet, and other public and private computer networks.
  • LAN Local Area Network
  • the Internet and other public and private computer networks.
  • an information handling system may take many forms.
  • an information handling system may take the form of a desktop, server, portable, laptop, notebook, or other form factor computer or data processing system.
  • an information handling system may take other form factors such as a personal digital assistant (PDA), a gaming device, ATM machine, a portable telephone device, a communication device or other devices that include a processor and memory.
  • PDA personal digital assistant
  • the Trusted Platform Module (TPM 195 ) shown in FIG. 1 and described herein to provide security functions is but one example of a hardware security module (HSM). Therefore, the TPM described and claimed herein includes any type of HSM including, but not limited to, hardware security devices that conform to the Trusted Computing Groups (TCG) standard, and entitled “Trusted Platform Module (TPM) Specification Version 1.2.”
  • TCG Trusted Computing Groups
  • TPM Trusted Platform Module
  • the TPM is a hardware security subsystem that may be incorporated into any number of information handling systems, such as those outlined in FIG. 2 .
  • FIG. 2 provides an extension of the information handling system environment shown in FIG. 1 to illustrate that the methods described herein can be performed on a wide variety of information handling systems that operate in a networked environment.
  • Types of information handling systems range from small handheld devices, such as handheld computer/mobile telephone 210 to large mainframe systems, such as mainframe computer 270 .
  • handheld computer 210 include personal digital assistants (PDAs), personal entertainment devices, such as MP3 players, portable televisions, and compact disc players.
  • PDAs personal digital assistants
  • Other examples of information handling systems include pen, or tablet, computer 220 , laptop, or notebook, computer 230 , workstation 240 , personal computer system 250 , and server 260 .
  • Other types of information handling systems that are not individually shown in FIG. 2 are represented by information handling system 280 .
  • the various information handling systems can be networked together using computer network 200 .
  • Types of computer network that can be used to interconnect the various information handling systems include Local Area Networks (LANs), Wireless Local Area Networks (WLANs), the Internet, the Public Switched Telephone Network (PSTN), other wireless networks, and any other network topology that can be used to interconnect the information handling systems.
  • Many of the information handling systems include nonvolatile data stores, such as hard drives and/or nonvolatile memory.
  • Some of the information handling systems shown in FIG. 2 depicts separate nonvolatile data stores (server 260 utilizes nonvolatile data store 265 , mainframe computer 270 utilizes nonvolatile data store 275 , and information handling system 280 utilizes nonvolatile data store 285 ).
  • the nonvolatile data store can be a component that is external to the various information handling systems or can be internal to one of the information handling systems.
  • removable nonvolatile storage device 145 can be shared among two or more information handling systems using various techniques, such as connecting the removable nonvolatile storage device 145 to a USB port or other connector of the information handling systems.
  • FIG. 3 is a high-level diagram showing instrumentation collecting data at two domains without use of common correlators.
  • Common operating system image 300 executes a number of domains, such as processes, subsystems, applications, and the like. Two such domains are shown being executed by operating system image 300 in FIG. 3 .
  • These domains, Domain “A” ( 310 ) and Domain “B” ( 320 ) are each executing within common operating system image 300 with one, or both, of the domains providing a service, or functionality, to the other domain (e.g., Domain “A” ( 310 ) “puts” a request to Domain “B” ( 320 ) via an Application Programming Interface (“API”) call, etc.).
  • Each of the domains has common execution identifiers with the other domain. These execution identifiers can include a system identifier, a process identifier, a thread identifier, etc.
  • instrumentation When tracking transactions through the system, instrumentation is enabled in each of the domains. This instrumentation acts to intercept inter-domain events that occur between the domains (e.g., request events and response events, etc.). In addition, the instrumentation generates a unique token at each domain, such as a timestamp-based token or an incremental token such as an integer counter, etc., that can be used to determine the order in which events occurred.
  • one of the domains e.g., Domain “A” is the “requestor” that generates request-type events when requesting services from the other domain and the other domain (e.g., Domain “B”) is the responder that provides the service and generates response-type events.
  • Request-type events generate request-type event records by the instrumentation.
  • the request-type event records include the execution identifiers (e.g., a system identifier, a process identifier, a thread identifier, etc.), the type of event (in this case indicating that it is a “request” event), and the unique token that was generated by the requesting domain.
  • the responding domain provides the service and generates response-type event records.
  • the response-type event records include the same execution identifiers (e.g., a system identifier, a process identifier, a thread identifier, etc.) as the counterpart response-type event record.
  • the type of event now indicates that it is a “response” event, and the unique token is generated at the response domain and is not based on the requestor's unique token per se, however the scheme or algorithm used to generate the responder's unique token can be the same as the scheme or algorithm that was used to generate the requestor's unique token (e.g., a timestamp-based unique token, etc.).
  • the request-type event records generated by the instrumentation running on Domain “A” are stored in data store 330 (e.g., a memory, nonvolatile storage, etc.) which is local to Domain “A”.
  • the response-type event records generated by the instrumentation running on Domain “B” are stored in data store 340 which is local to Domain “B”.
  • Correlation process 350 is performed to match request-type event records (e.g., generated by Domain “A”) with their respective response-type event records (e.g., generated by Domain “B”) without the use of any static, or common, correlators or tokens. Instead, the request-type event records are merged with the response-type event records and sorted using the unique tokens that were generated by the instrumentation. The correlation process selects request-type event records from the merged data and then searches for a matching response-type event record (a record with the same execution identifiers) and ensures that there are no intervening request-type event records with the same execution identifiers.
  • request-type event records e.g., generated by Domain “A”
  • response-type event records e.g., generated by Domain “B”
  • the correlation process selects request-type event records from the merged data and then searches for a matching response-type event record (a record with the same execution identifiers) and ensures that there are no intervening request-type event records with
  • a request-type event record When a request-type event record is matched with a response-type event record, the matched pair indicates an inter-domain transaction that is written to correlated transaction data store 360 .
  • the correlation process continues to select request-type event records and find their matching response-type event records for as many other records in the merged data that are desired for processing.
  • the resulting inter-domain transaction data are written to correlated transaction data store 360 for eventual analysis.
  • transaction tracking software 370 analyzes the inter-domain transactions stored in data store 360 and generates one or more analyses of the inter-domain transactions (analysis 380 ). System administrators and developers can then review the analysis of inter-domain transactions in order to identify bottlenecks or other areas of improvement in either of the domains.
  • FIG. 4 is a flowchart showing steps taken by processes running on two domains within a common operating system and collecting instrumentation data for future process correlation.
  • Domain “A” 400
  • CICS Customer Information Control SystemTM
  • Domain “B” 450
  • WQ WebSphere Messaging QueueTM
  • Domain “A” has a data collector that collects process information when instrumentation is enabled.
  • Domain “B” also has a data collector that collects process information when instrumentation is enabled.
  • Processing by Domain “A” data collector commences at 410 whereupon, at step 415 , the domain runs a process (such as CICSTM) with instrumentation enabled.
  • the instrumentation software intercepts inter-domain events (e.g., API calls, etc.) and collects relevant process data (see FIG. 5 and corresponding text for processing details).
  • the collected data e.g., request-type event records, etc.
  • a decision is made as to whether processing has ended or terminated (decision 430 ).
  • decision 430 branches to the “no” branch which loops back to continue running the process (e.g., CICSTM, etc.) and continue collecting the relevant process data. This looping continues until process ends, at which point decision 430 branches to the “yes” branch and processing by the data collector running on Domain “A” ends at 435 .
  • process e.g., CICSTM, etc.
  • processing by Domain “B” data collector commences at 460 whereupon, at step 465 , the domain runs a process (such as WMQTM) with instrumentation enabled.
  • the instrumentation software intercepts inter-domain events (e.g., response events resulting from WMQ handling the request from CICS, etc.) and collects relevant process data (see FIG. 5 and corresponding text for processing details).
  • the collected data e.g., response-type event records, etc.
  • a decision is made as to whether processing has ended or terminated (decision 480 ).
  • decision 480 branches to the “no” branch which loops back to continue running the process (e.g., WMQTM, etc.) and continue collecting the relevant process data. This looping continues until process ends, at which point decision 480 branches to the “yes” branch and processing by the data collector running on Domain “B” ends at 485 .
  • process e.g., WMQTM, etc.
  • FIG. 5 is a flowchart showing steps performed by data collector process running on each domain.
  • Data collection processing commences at 500 .
  • the data collection processing runs on each domain where instrumentation has been enabled.
  • the data collector intercepts an inter-domain event such as a request (call) to another domain from this domain or a response to another domain by this domain.
  • the type of event is identified (e.g., a request-type event, a response-type event, etc.).
  • data pertaining to the inter-domain event is gathered with this data forming an execution identifier.
  • the execution identifier is formed from one or more identifiers such as the system identifier, the process identifier, and the thread identifier. For a given transaction, the execution identifier is the same on both the requesting domain as well as the responding domain.
  • a unique token is generated with the token indicating an order in which inter-domain events occurred (e.g., timestamp-based token, incremented integer based token, etc.).
  • the gathered request data that forms the execution identifier is stored along with the type of the event (request or response) as well as the generated unique token. This data is stored in local data store 560 , such as a memory area, that is local to the domain that is running the data collector process.
  • decision 570 A decision is made as to whether data collector processing is being terminated on this domain (decision 570 ). If data collector processing is not being terminated on this domain, then decision 570 branches to the “yes” branch which loop back to continue intercepting inter-domain requests and responses and storing the relevant data as described above. This looping continues until data collector processing is being terminated on this domain, at which point decision 570 branches to the “yes” branch whereupon data collector processing ends at 595 .
  • FIG. 6 is a flowchart showing steps performed by the correlation process to correlate the instrumentation data gathered during execution of processes running on the domains of the operating system.
  • Correlation process commences at 600 whereupon, at step 610 the local data stores are sorted based on the unique tokens included in the event records if they are not already sorted (e.g., first local data store 425 is sorted by the unique tokens resulting in sorted first local data store 615 and second local data store 475 is sorted by the unique tokens resulting in sorted second local data store 620 ).
  • the sorted event records are merged with the resulting merge file ( 630 ) also being sorted based on the unique token included in each event record.
  • Resulting merge file 630 is then processed to identify the inter-domain transactions as discussed below.
  • the first request-type event record in merge file 630 is selected.
  • an indicator was inserted in each event record indicating whether the event corresponded to a request or a response.
  • a decision is made as to whether an request-type event record was found in merge file 630 (decision 650 ). If a request-type event record was found in merge file 630 , then decision 650 branches to the “yes” branch whereupon, at step 660 , the process searches for a matching response-type event record (e.g., a response-type record with the same execution identifier).
  • the correlation process ensures that there were not any addition (intervening) request-type events with the same execution identifier that occurred before the response-type record was found.
  • a decision is made by the correlation process as to whether a valid response-type event record was found before any intervening request-type event records were encountered (decision 670 ). If a valid response-type event record was found, then the request-type event record and the matched response-type event record indicate an inter-domain transaction. In this case, decision 670 branches to the “yes” branch whereupon, at step 675 , the inter-domain transaction data is written to correlated inter-domain transactions data store 360 .
  • Inter-domain transaction data can include the execution identifiers as well as timing data that indicates when the request was made by the requesting domain as well as when the response was sent by the responding domain. Processing then loops back to step 640 to select the next request-type event record from merged data store 630 .
  • decision 670 if a valid response-type record was not found (e.g., an intervening request-type event record was encountered, no response was found, etc.), then decision 670 branches to the “no” branch whereupon, at step 680 , a record of the error can be written to error log data store 685 to indicate the request-type event record for which no valid response-type event record was found. Processing then loops back to step 640 to select the next request-type event record from merged data store 630 .
  • next request-type event record is selected from merge file data store 630 and the processing described above searches for a matching response-type event record. This looping continues until all request-type event records have been processed, at which point decision 650 branches to the “no” branch and processing ends at 695 .
  • One of the preferred implementations of the invention is a client application, namely, a set of instructions (program code) or other functional descriptive material in a code module that may, for example, be resident in the random access memory of the computer.
  • the set of instructions may be stored in another computer memory, for example, in a hard disk drive, or in a removable memory such as an optical disk (for eventual use in a CD ROM) or floppy disk (for eventual use in a floppy disk drive).
  • the present invention may be implemented as a computer program product for use in a computer.
  • Functional descriptive material is information that imparts functionality to a machine.
  • Functional descriptive material includes, but is not limited to, computer programs, instructions, rules, facts, definitions of computable functions, objects, and data structures.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Computing Systems (AREA)
  • Databases & Information Systems (AREA)
  • Mathematical Physics (AREA)
  • Software Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Debugging And Monitoring (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
US13/344,385 2012-01-05 2012-01-05 Linking Single System Synchronous Inter-Domain Transaction Activity Abandoned US20130179448A1 (en)

Priority Applications (6)

Application Number Priority Date Filing Date Title
US13/344,385 US20130179448A1 (en) 2012-01-05 2012-01-05 Linking Single System Synchronous Inter-Domain Transaction Activity
DE102012224270A DE102012224270A1 (de) 2012-01-05 2012-12-21 Verbinden einer synchronen domänenübergreifenden Transaktionsaktivität in einem einzelnen System
CN2013100010047A CN103279380A (zh) 2012-01-05 2013-01-04 信息处理系统和方法
GB1300166.4A GB2499877A (en) 2012-01-05 2013-01-07 Correlating transaction data
US13/754,851 US10216600B2 (en) 2012-01-05 2013-01-30 Linking single system synchronous inter-domain transaction activity
US16/176,814 US10824646B2 (en) 2012-01-05 2018-10-31 Linking single system synchronous inter-domain transaction activity

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US13/344,385 US20130179448A1 (en) 2012-01-05 2012-01-05 Linking Single System Synchronous Inter-Domain Transaction Activity

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/754,851 Continuation US10216600B2 (en) 2012-01-05 2013-01-30 Linking single system synchronous inter-domain transaction activity

Publications (1)

Publication Number Publication Date
US20130179448A1 true US20130179448A1 (en) 2013-07-11

Family

ID=47748007

Family Applications (3)

Application Number Title Priority Date Filing Date
US13/344,385 Abandoned US20130179448A1 (en) 2012-01-05 2012-01-05 Linking Single System Synchronous Inter-Domain Transaction Activity
US13/754,851 Active 2036-03-10 US10216600B2 (en) 2012-01-05 2013-01-30 Linking single system synchronous inter-domain transaction activity
US16/176,814 Active US10824646B2 (en) 2012-01-05 2018-10-31 Linking single system synchronous inter-domain transaction activity

Family Applications After (2)

Application Number Title Priority Date Filing Date
US13/754,851 Active 2036-03-10 US10216600B2 (en) 2012-01-05 2013-01-30 Linking single system synchronous inter-domain transaction activity
US16/176,814 Active US10824646B2 (en) 2012-01-05 2018-10-31 Linking single system synchronous inter-domain transaction activity

Country Status (4)

Country Link
US (3) US20130179448A1 (zh)
CN (1) CN103279380A (zh)
DE (1) DE102012224270A1 (zh)
GB (1) GB2499877A (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160156806A1 (en) * 2013-06-06 2016-06-02 Open Text S.A. Systems, methods and computer program products for fax delivery and maintenance
US20160277252A1 (en) * 2015-03-20 2016-09-22 International Business Machines Corporation High performance topology resolution for non-instrumented nodes
US10372482B2 (en) * 2017-09-28 2019-08-06 Ca, Inc. Domain transversal based transaction contextualization of event information
US10824646B2 (en) 2012-01-05 2020-11-03 International Business Machines Corporation Linking single system synchronous inter-domain transaction activity

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9916229B2 (en) 2015-10-14 2018-03-13 International Business Machines Corporation Decomposing application topology data into transaction tracking data
US10205610B2 (en) 2016-02-29 2019-02-12 Alcatel Lucent Uplink packet routing in a system-on-a-chip base station architecture
US10303636B2 (en) 2016-02-29 2019-05-28 Nokia Of America Corporation Routing paging packets in a system-on-a-chip base station architecture
CN105930471A (zh) * 2016-04-25 2016-09-07 上海交通大学 演讲摘要生成方法及装置
US11044145B2 (en) * 2016-12-13 2021-06-22 International Business Machines Corporation Configuring and naming of cloud provisioning entities
US11153273B2 (en) 2016-12-13 2021-10-19 International Business Machines Corporation Generating and managing names of instances
US10394628B1 (en) * 2018-02-26 2019-08-27 Microsoft Technology Licensing, Llc In-line event handlers across domains
CN113965536B (zh) * 2021-10-19 2023-06-02 广州华多网络科技有限公司 消息令牌更新方法及其装置、设备、介质、产品

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040123293A1 (en) * 2002-12-18 2004-06-24 International Business Machines Corporation Method and system for correlating transactions and messages
US20070060367A1 (en) * 2005-09-14 2007-03-15 International Business Machines Corporation End-to-end transaction tracking in the enterprise
US20070294224A1 (en) * 2006-06-16 2007-12-20 Jean-Jacques Heler Tracking discrete elements of distributed transactions
US20100153835A1 (en) * 2008-12-17 2010-06-17 Business Objects, S.A. Linking annotations to document objects

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3426428B2 (ja) 1995-10-27 2003-07-14 富士通株式会社 トランザクションのトレース装置
US6883162B2 (en) 2001-06-06 2005-04-19 Sun Microsystems, Inc. Annotations for transaction tracing
US7516209B2 (en) 2003-06-27 2009-04-07 Microsoft Corporation Method and framework for tracking/logging completion of requests in a computer system
US7607138B2 (en) * 2004-06-17 2009-10-20 Cisco Technology, Inc. System and method for optimizing inter-domain event services
US7493302B2 (en) 2006-06-26 2009-02-17 International Business Machines Corporation Federated transaction path and service level agreement monitoring across service oriented application partner domains
US7904457B2 (en) * 2007-05-30 2011-03-08 International Business Machines Corporation Semantic correlation for flow analysis in messaging systems
US8892726B2 (en) * 2008-03-30 2014-11-18 Correlsense Ltd. Apparatus and method for tracking requests in a multi threaded multi tier computerized environment
US8584123B2 (en) * 2009-10-08 2013-11-12 International Business Machines Corporation Linking transactions
US20130179448A1 (en) 2012-01-05 2013-07-11 International Business Machines Corporation Linking Single System Synchronous Inter-Domain Transaction Activity

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040123293A1 (en) * 2002-12-18 2004-06-24 International Business Machines Corporation Method and system for correlating transactions and messages
US20070060367A1 (en) * 2005-09-14 2007-03-15 International Business Machines Corporation End-to-end transaction tracking in the enterprise
US20070294224A1 (en) * 2006-06-16 2007-12-20 Jean-Jacques Heler Tracking discrete elements of distributed transactions
US20100153835A1 (en) * 2008-12-17 2010-06-17 Business Objects, S.A. Linking annotations to document objects

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10824646B2 (en) 2012-01-05 2020-11-03 International Business Machines Corporation Linking single system synchronous inter-domain transaction activity
US20160156806A1 (en) * 2013-06-06 2016-06-02 Open Text S.A. Systems, methods and computer program products for fax delivery and maintenance
US9762769B2 (en) * 2013-06-06 2017-09-12 Open Text Sa Ulc Systems, methods and computer program products for fax delivery and maintenance
US10136023B2 (en) 2013-06-06 2018-11-20 Open Text Sa Ulc Systems, methods and computer program products for fax delivery and maintenance
US10306097B2 (en) 2013-06-06 2019-05-28 Open Text Sa Ulc Systems, methods and computer program products for fax delivery and maintenance
US10554852B2 (en) 2013-06-06 2020-02-04 Open Text Sa Ulc Systems, methods and computer program products for fax delivery and maintenance
US10674034B1 (en) 2013-06-06 2020-06-02 Open Text Sa Ulc Systems, methods and computer program products for fax delivery and maintenance
US20160277252A1 (en) * 2015-03-20 2016-09-22 International Business Machines Corporation High performance topology resolution for non-instrumented nodes
US9912545B2 (en) * 2015-03-20 2018-03-06 International Business Machines Corporation High performance topology resolution for non-instrumented nodes
US10372482B2 (en) * 2017-09-28 2019-08-06 Ca, Inc. Domain transversal based transaction contextualization of event information
US11068300B2 (en) 2017-09-28 2021-07-20 Ca, Inc. Cross-domain transaction contextualization of event information

Also Published As

Publication number Publication date
DE102012224270A1 (de) 2013-07-11
US20190065575A1 (en) 2019-02-28
US10216600B2 (en) 2019-02-26
GB2499877A (en) 2013-09-04
GB201300166D0 (en) 2013-02-20
US10824646B2 (en) 2020-11-03
CN103279380A (zh) 2013-09-04
US20130179446A1 (en) 2013-07-11

Similar Documents

Publication Publication Date Title
US10824646B2 (en) Linking single system synchronous inter-domain transaction activity
US20180095730A1 (en) Optimizing Performance of Applications Driven by Microservices Architecture
Pagani et al. Introducing the temporal dimension to memory forensics
US8683489B2 (en) Message queue transaction tracking using application activity trace data
US8584123B2 (en) Linking transactions
US8683268B2 (en) Key based cluster log coalescing
US20130254121A1 (en) Software Portfolio Management Based on Feature Usage
US9612641B2 (en) Adjusting the connection idle timeout in connection pools
US11106562B2 (en) System and method for detecting anomalies based on feature signature of task workflows
US8626959B2 (en) Discovery and configuration of new devices added via dynamic reconfiguration
JP6266008B2 (ja) 仮想マシン・イメージをコンピュータ・システムに適用する方法、情報処理システム、コンピュータ・プログラム
US8484342B2 (en) Organizing individual java client request flows into a single server transaction
US8316126B2 (en) Stitching transactions
US10157117B2 (en) Processing transaction timestamps
US9117013B2 (en) Combining monitoring techniques
US8479184B2 (en) General purpose emit for use in value profiling
US20170123964A1 (en) Finding Duplicates in Prior Runs of Static Analysis Tools
US11843523B1 (en) Microservices anti-pattern discovery
WO2022195739A1 (ja) 活動痕跡抽出装置、活動痕跡抽出方法および活動痕跡抽出プログラム
US20130179396A1 (en) Defining and Detecting Bundle Information in Databases
US20120005653A1 (en) Correlating software management facility data with product inventory data

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:DIXON, BRET WILLIAM;DIXON, SCOT;HUBAND, SIMON TEVEREY;REEL/FRAME:027490/0161

Effective date: 20111114

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION