KR20090088375A - Method, system and program product for monitoring resources servicing a business transaction - Google Patents

Abstract

A method, system and program product for monitoring resources servicing a business transaction is provided. The method includes providing a transaction manager that monitors a business transaction serviced by one or more resources, with each of the resources and the transaction manager having a protocol stack configured to send and receive load-monitoring headers in protocol messages. The method further includes specifying, in a protocol request header in a protocol request message, collection of performance metrics for a resource, collecting, by the resources, the performance metrics specified in the protocol request message and sending the performance metrics collected to the transaction manager, in a protocol response header in a protocol response message. Further, the method includes preconfiguring with policies the protocol stack on a subset of the resources, such that the preconfigured resources can act as monitoring agents on behalf of peer resources and send alerts to a resource manager. ® KIPO & WIPO 2009

Description

METHOD, SYSTEM AND PROGRAM PRODUCT FOR MONITORING RESOURCES SERVICING A BUSINESS TRANSACTION}

The present invention relates to a method, system, and program product for monitoring resources that service business transactions in a service-oriented architecture (SOA). In particular, the present invention relates to a method, system, and computer program product for decorating a typical SOA exchange with additional monitoring information carried in the header portion of the response message along with the payload. The invention also relates to a method for cross-checking a header in a response message received by a resource. As such, the resource acts as a monitoring agent for other peer resources.

In today's business environment, customers are increasingly doing online or electronic transactions with organizations and / or businesses, such as retailers, banking services and the like. In a typical scenario, a customer seeking to trade online may need to access a business's webpage over the Internet and then provide personal information, depending on the type of online transaction. For example, if an item is purchased online, the customer typically must provide personal information identifying the customer such as name, address, credit card number, etc. to purchase the item. At all times, data for such online transactions can be processed by multiple computers on the network. Here, each computer performs one aspect of the transaction. Any of these computers, if overloaded, can cause delays in processing transactions, which will negatively affect customers. As such, there is a need for a business and / or organization to provide a cost-effective way to develop a monitoring system that can track such electronic transactions to ensure customer satisfaction.

In a first aspect of the invention, a method of monitoring a resource for servicing a business transaction in a service-oriented architecture is provided. The method includes providing a transaction manager configured to monitor a business transaction served by one or more resources in a service-oriented architecture. In one embodiment, each of the one or more resources and the transaction manager is configured with a protocol encoding configured to send one or more protocol request messages requiring a collection of performance metrics and to receive one or more protocol response messages that include the collected performance metrics. The decoding component is arranged. The method includes specifying a collection of one or more performance metrics for at least one of the one or more resources servicing a business transaction in a protocol request header in the protocol request message, and collecting one or more performance metrics specified in the protocol request message. And sending, in the protocol response header in the protocol response message, to the transaction manager one or more performance metrics collected by at least one of the one or more resources servicing the business transaction. In one embodiment, the transaction manager is configured to monitor one or more transaction metrics associated with the business transaction and to analyze one or more transaction metrics monitored for the business transaction in light of one or more performance metrics collected from one or more resources. The method further includes providing a resource manager configured to collect one or more performance metric events from one or more monitoring agents disposed on one or more of the one or more resources. The method involves associating a protocol request header in a protocol request message with an execution thread for a business transaction, and propagating the protocol request header in the protocol request message to any other request made within the same execution thread for the business transaction. It further includes. Here, the protocol request header in the protocol request message is replicated through all the exchanges associated with the business transaction. The method further includes preconfiguring, with a policy, at least each protocol encoding-decoding component corresponding to each of the one or more resources. Here, each resource checks the total value for one of the one or more performance metrics in each protocol response header received from subsequent resources. Here, each resource sends an alert to the resource manager when the preset value for the performance metric is exceeded. In one embodiment, the transmitting step adds, by each preceding one of the one or more resources, each set of performance metrics to a protocol response header in a protocol response message received from each subsequent one of the one or more resources. And sending a protocol response message to the transaction manager. Further, in one embodiment, the step of transmitting may include each of the one or more performance metrics corresponding to one of the one or more resources servicing other arbitrary requests made within the same thread of execution for a business transaction protocol response message. Counting in the protocol response headers within, and sending a protocol response message to the transaction manager. In one embodiment, this protocol includes the Simple Object Access Protocol (SOAP).

In another aspect of the present invention, a system is provided for monitoring resources serving a business transaction in a service-oriented architecture. The system includes one or more resources configured to service a business transaction, wherein a plurality of the one or more resources are arranged with a protocol stack. The system also monitors one or more performance metrics for the business transaction in which a protocol stack is deployed and serviced by the plurality of the one or more resources to a plurality of one or more resources in a protocol request header in a protocol request message. And further comprising a transaction manager configured to issue what to do. Each of the plurality of one or more resources is configured to collect one or more performance metrics for the business transaction and to aggregate one or more performance metrics in the protocol response headers in the protocol response message sent to the transaction manager. Here, the protocol request header in the protocol request message is associated with the execution thread for the business transaction, and the protocol request header in the protocol request message is propagated to any other request made within the same execution thread for the business transaction, thereby The protocol request header allows for replication through all exchanges associated with the business transaction. The system further includes a resource manager configured to collect one or more performance metric events from one or more monitoring agents deployed on the one or more resources. In one embodiment, the transaction manager is further configured to monitor one or more transaction metrics for business transactions served by one or more resources, and one that services business transactions in light of one or more performance metrics collected by one or more resources. And analyze the monitored one or more transaction metrics for the more resources. In one embodiment, the preceding resource of each of the one or more resources is configured to add each performance metric set to a protocol response header in a protocol response message received from each subsequent one of the one or more resources. In one embodiment, a protocol stack corresponding to one or more of the plurality of one or more resources compares an aggregate value of one of the one or more performance metrics received in the protocol response header with a preset value of the performance metric. Thus, one or more of the plurality of one or more resources are preconfigured with policies to send an alert to the resource manager when the preset value for that performance metric is exceeded. In one embodiment, the protocol stack is a Simple Object Access Protocol (SOAP) stack, the protocol request header is a Simple Object Access Protocol (SOAP) request header, the protocol response header is a Simple Object Access Protocol (SOAP) response header, and the protocol The request message is a Simple Object Access Protocol (SOAP) request message, and the protocol response message is a Simple Object Access Protocol (SOAP) response message.

In yet another aspect of the present invention, a computer program product for monitoring a metric associated with a business transaction is provided. The computer program product further includes first program instructions for providing a transaction manager configured to specify a collection of one or more performance metrics in a request header in a request message issued to one or more resources servicing a business transaction. Here, each of the one or more resources and the transaction manager is arranged with a protocol stack. The computer program product sends second program instructions for collecting one or more performance metrics specified in the request message and one or more performance metrics collected by the one or more resources servicing the business transaction to the transaction manager in the response header in the response message. It further comprises a third program instruction to. In one embodiment, the second program instruction associates the request header in the request message with an execution thread for a business transaction, and associates the request header in the request message with any other request messages created in the execution thread for that business transaction. It further includes instructions for propagating. Furthermore, in one embodiment, the second program instructions further include instructions for adding each set of performance metrics to a response header in a response message received from a subsequent one of the one or more resources and sending the response message to the transaction manager. Include. The computer program product compares the total value of one of the one or more performance metrics in each response header received from subsequent resources with a preset value for that performance metric and when the preset value for that performance metric is exceeded. In order to send an alert to the resource manager, the method further includes fourth program instructions for preconfiguring the protocol stack disposed on the one or more resources into policies. In one embodiment, the transaction manager is configured to monitor one or more transaction metrics associated with the business transaction and is further configured to analyze the one or more transaction metrics monitored for the business transaction in light of one or more performance metrics collected from one or more resources. It is composed. In one embodiment, the protocol stack includes a Simple Object Access Protocol (SOAP) stack, and the request header includes a Simple Object Access Protocol (SOAP) request header. In addition, the response header includes a Simple Object Access Protocol (SOAP) response header, the request message includes a Simple Object Access Protocol (SOAP) request message, and the response message includes a Simple Object Access Protocol (SOAP) response message. In one embodiment, each of the first, second, third, and fourth program instructions are stored on a computer readable medium.

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention.

1A shows a flow diagram that outlines the steps involved in an embodiment of monitoring resources for serving a business transaction in accordance with an embodiment of the present invention.

2A is a flowchart outlining the steps involved in another embodiment of monitoring a business transaction in accordance with an embodiment of the present invention, wherein one or more resources additionally serve as a monitoring agent on behalf of peer resources.

FIG. 1B is a schematic block system diagram illustrating an embodiment of a method and system for monitoring resources servicing a business transaction, corresponding to the method outlined in FIG. 1A, in accordance with an embodiment of the present invention.

FIG. 2B is a schematic block system diagram illustrating another embodiment of a method and system for monitoring resources servicing a business transaction, corresponding to the method outlined in FIG. 2A, in accordance with an embodiment of the present invention.

3 is a schematic block system diagram illustrating yet another embodiment of a method and system for monitoring resources for servicing a business transaction in a service-oriented architecture in accordance with an embodiment of the present invention.

4 is a schematic block system diagram illustrating an embodiment of a computer infrastructure for monitoring resources that service a business transaction in a service-oriented architecture in accordance with an embodiment of the present invention.

Reference throughout this specification to “an embodiment”, “an embodiment”, or similar expressions means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. do. Thus, the appearances of the phrases "in one embodiment", "in an embodiment", and similar expressions throughout this specification may, but are not necessarily, refer to the same embodiment.

In addition, the aforementioned features, structures, or characteristics of the present invention may be combined in any suitable manner in one or more embodiments. It will be apparent to those skilled in the art that various modifications and variations can be made to the embodiments of the present invention. Reference will now be made in detail to preferred embodiments of the invention.

Referring now to FIGS. 1A and 2A, there is shown a flow diagram that outlines different embodiments of a method of monitoring resource or performance metrics or information across business method invocations. The term "business method startup" refers to a simple request from one application to another, such as "checking the credit card number XYZ for a $ 70 payment." As shown in FIG. 1A, in embodiment 100a, the method for monitoring resource metrics is configured to, in step 103, request a collection of performance metrics for a business transaction in a protocol request header in a protocol request message. Providing a transaction manager (discussed in more detail below with reference to FIGS. 1B and 2B) having a protocol stack further configured to receive in a protocol response header of a protocol response message that includes performance metrics collected by a resource. To start. The method also includes providing one or more resources with a protocol stack configured to collect individual performance metrics specified in the protocol request headers in the protocol request message received by the resource in step 105. In step 107, the method includes requesting in the protocol request header a collection of one or more performance metrics by one or more resources servicing a business transaction, and in step 111, an execution thread having the same protocol request header. Associating a protocol request header in a protocol request message with an execution thread for a business transaction to propagate to any other request made therein. In addition, the method includes, at step 113, transmitting a protocol request header in the protocol request message to a first resource serving a business transaction, and at 115, by the first resource, in the protocol request message. Forwarding a protocol request header to each subsequent resource serving a business transaction. The method also includes, at step 117, adding each set of performance metrics to a protocol response header in a protocol response message received from each subsequent resource, and at 121, a protocol response comprising the performance metrics. Sending the protocol response header in the message back to the transaction manager.

In addition, as shown in FIG. 2A, in another embodiment 200a, a method for monitoring a resource serving a business transaction includes, at step 203, a protocol request for a collection of performance metrics for a business transaction. Providing a transaction manager having a protocol stack configured to receive in the protocol response header of the protocol response message that is configured to request in the protocol request header of the message and includes the collected performance metrics. Furthermore, the method provides, at step 205, one or more resources having a protocol stack configured to collect individual performance metrics specified in the protocol request headers in the received protocol request message, wherein at least one of the resources is present. Wherein said providing has a protocol stack preconfigured with a policy or rule, and in step 207 requesting a collection of one or more performance metrics in a protocol request header by one or more resources servicing a business transaction. It includes a step. Furthermore, the method further reports, at step 209, any performance metrics collected on behalf of other resources by one or more resources having a protocol stack of preconfigured policies when a predetermined preset value for the performance metrics has been exceeded. Requesting, and in step 211, associating the protocol request header of the protocol request message with the execution thread for the business transaction, such that the protocol request header is propagated to any other requests made within the same execution thread. Include. Further, the method includes, at step 213, sending a protocol request header in the protocol request message to a first resource serving a business transaction. In step 215, the method includes forwarding, by the first resource, the protocol request header in the protocol request message to each subsequent resource. As such, the method includes, at 217, adding each set of performance metrics to a protocol response header in a protocol response message received from each subsequent resource, and at 219, received from subsequent resources. Examining the aggregate values for the collected performance metrics in each protocol response header by a resource having a protocol stack preconfigured with a policy, and in step 221, trading the protocol response header in the protocol response message that includes the performance metrics. And sending back to the administrator. The method also includes, at step 223, sending an alert to the transaction manager if the total value for the performance metric exceeds the preset value for this performance metric.

1B and 2B, various embodiments of method or process steps executed by various components involved in a business transaction, as outlined above in FIGS. 1A and 2A, are shown. In particular, the method outlined above with respect to FIG. 1A corresponds to the embodiment shown in FIG. 1B, whereas the method outlined above with respect to FIG. 2A corresponds to the embodiment shown in FIG. 2B. Since there are similar aspects for both embodiments 100b and 200b, similar aspects will be described together with respect to FIGS. 1B and 2B. In contrast, distinct features will be described separately below. As shown in FIGS. 1B and 2B, a method of monitoring resources serving a business transaction may include one or more resources 110, 114, 118, and 122 (210, 214, in FIG. 22B) of a service-oriented architecture (SOA). 218, and 222), providing a transaction manager 106 (206 in FIG. 2B) configured to monitor business transactions serviced. A business transaction implemented using a service-oriented architecture (SOA) refers to a call made from a resource providing one web service to another resource providing another web service. The resource may be any device, machine, or system that services business transactions such as web servers, credit card verification systems, database servers, email servers, and the like. In addition, transaction manager 106 (206 of FIG. 2B) is an application server that monitors or collects transaction metrics or transaction data associated with the business transaction regarding what the end user is experiencing. In particular, the transaction manager 106 (206 in FIG. 2B) may determine how much time the business transaction taken from the end user perspective took and / or each resource 110, 114, 118 and / or 122 that processed the business transaction. Transaction metrics such as how much time was spent by (210, 214, 218 and / or 222 in FIG. 2B) can be tracked. Transaction manager 106 (206 in FIG. 2B) can track this transaction metric or transaction information and send details of the time spent by each resource to the remote manager so that if needed, You can take appropriate action. However, as disclosed in the method embodiments of FIGS. 1B and 2B, the transaction manager 106 (206 in FIG. 2B) services the business transaction to interpret the aggregated transaction metrics, as discussed below. Configured to track performance or resource or resource-level metrics for one or more resources. 1B and 2B show four resources, namely, resource 1 (reference numeral 110 in FIG. 1B and 210 in FIG. 2B), resource 2 (reference numeral 114 in FIG. 1B and 214 in FIG. 2B), and resource 3 (FIG. 1B). 118 of FIG. 2B and 218 of FIG. 2B), and resource 4 (reference numeral 122 of FIG. 1B and 222 of FIG. 2B) (solid arrows 112, 116, 120, 124, 126, and 128 of FIG. 1B; 2b, denoted by 212, 216, 220, 224, 226, and 228). For example, resource 1 (110 in FIG. 1B and 210 in FIG. 2B) may be a web server, and web server (110 in FIG. 1B and 210 in FIG. 2B) may refer to resource 2 (reference number in FIG. 1B) for a web service. 114 and 214 of FIG. 2B) (arrow 112, and arrow 212 of FIG. 1B), and resource 2 calls resource 3 (118 of FIG. 1B and 218 of FIG. 2B) for another web service (of FIG. 1B). 116 and 216 of FIG. 2B, and resource 3 also calls resource 4 (reference number 122 of FIG. 1B and 222 of FIG. 2B) for another web service (120 of FIG. 1B and 220 of FIG. 2B). . For example, resource 2 (reference number 114 in FIG. 1B and 214 in FIG. 2B) may be a “check out shopping cart” that a customer accesses when placing an item in a shopping cart, while resource 3 (reference number in FIG. 1B). 118 and 218 of FIG. 2B may be a “product inventory check” server that checks to see if an item is in stock, while resource 4 (reference number 122 of FIG. 1B and 222 of FIG. 2B) is supplied for a business transaction. It may be a "credit card verification" server that verifies the customer's credit card information. As an alternative, for example, resource 2 (reference number 114 in FIG. 1B and reference number 214 in FIG. 2B) may be used by a shipping unit (not shown in FIGS. 1B and 2B) to check whether an item or product is in inventory. Then, resource 2 calls resource 3 (reference number 118 in FIG. 1B and 218 in FIG. 2B) (arrow 120 in FIG. 1B and 220 in FIG. 2B), and then resource 3 is assigned to resource 4 ( Reference numeral 122 in FIG. 1B and 222 in FIG. 2B are called (arrow 120 in FIG. 1B and 220 in FIG. 2B).

Although the business transaction flow is shown in a linear manner in FIGS. 1B and 2B, as shown in FIG. 3, a business transaction may not be linear in that there are other steps or processes executed concurrently by the resource. have. As shown in the embodiment 300 of FIG. 3, the transaction manager 306 sends a request message to resource 1 310, and resource 1 then sends the messages to resource 2 314, resource 3 318. ) And resource 4 (322) at the same time. For example, resource 1 310 may be a web server that contacts resource 2 314, which may be a database server for checking inventory, while resource 3 318 is a credit card verification server and resource 4 ( 322 may be an e-mail server that sends a message regarding a business transaction. Thus, each of resource 4 322, resource 3 318, and resource 2 314 sends its own response to resource 1 310. Resource 1 sends the response back to the transaction manager 306. 3 is only used to illustrate an example of a non-linear transaction, and the teachings of FIGS. 1B and 2 will also be discussed in further detail on the assumption that it is also applicable to FIG. 3. Returning to FIGS. 1B and 2B, each of the four resources 110 (210 in FIG. 2B), 114 (214 in FIG. 2B), 118 (218 in FIG. 2B), and / or (222 in FIG. 2B), The transaction manager 106 (206 in FIG. 2B) is equipped with an installed protocol encoding-decoding component or an installed protocol stack. As an alternative, a protocol in which only a subset of the transaction manager 106 (206 in FIG. 2B) and four resources 110, 114, 118, and 122 (210, 214, 218, and 222 in FIG. 2B) is installed may be used. Can have In one embodiment, the transport protocol for a business transaction implemented using a service-oriented architecture (SOA) is the Simple Object Access Protocol (SOAP). The SOAP specification is fully described at http://www.w3.org/TR/soap. "Protocol stack" or "soap stack" or "encoding-decoding component" refers to a software layer used to encode and decode protocol messages, in particular SOAP messages. A SOAP message is a text message using the XML-Extensible Markup Language, and the messages have distinct parts, that is, a body or payload and a header. A SOAP message contains one body part but may include one or more headers. The header in the message contains information intended for the transmitting nodes between the caller and the responder (including themselves), such as "Return response to this address" or "This message is part of a larger transaction number 987". It includes. As such, each header in a SOAP message can serve a completely different purpose, such as defining security permissions, transaction markers, delivery parameters, and so forth. The body or payload includes a message intended for the responder from the caller, such as "confirm the credit card number XYZ for a $ 70 payment," or a response from the responder, such as "credit authorization". In particular, “tool protocol stack” means that in addition to the request carried in the payload of the message described above with respect to FIGS. A protocol stack with additional functionality that makes it understandable to a software layer that knows how to encode and decode SOAP messages. As such, any other protocol that implements the same concept of body / header separation in message exchange, such as SOAP, can be used to implement the methods of the preferred embodiments of the present invention.

1A and 2B, a transaction manager 106 (206 in FIG. 2B) with a tooled SOAP stack indicates a SOAP request message 108 (FIG. 2B) to resource 1 at reference numeral 110 (210 in FIG. 2B). 208). In particular, the SOAP request message 108 (208 in FIG. 2B) may be carried in an entity request and other headers carried in the body portion or payload of the SOAP request message 108 (208 in FIG. 2B). In addition to the other requests of, requesting a collection of one or more performance or resource metrics by one or more of the four resources 110, 114, 118, and 122 (210, 214, 218, and 222) serving the business transaction. Contains a SOAP header. Some examples of performance metrics that can be collected for a resource include central processing unit (CPU) usage, memory paging, disk usage, disk free space, disk fragmentation, memory utilization, thread count, process count, and bytes read (network I / O), recorded bytes (network I / O), and the like. In particular, as shown in FIGS. 1B and 2B, request information for collecting one or more performance metrics is specified and executed in a protocol request header (SOAP request header) of a protocol request message (SOAP request message), and resources. (110, 114, 118, and 122) (210, 214, 216, and 222), respectively (solid arrows 108, 112, 116, and 120; 208, 212, 216, and 220 in FIG. 2B). In contrast, performance metrics collected by one or more resources servicing a business transaction are sent back to the transaction manager 106 (206 in FIG. 2B) in the protocol response header (SOAP response header) in the protocol response message (SOAP response message). (Solid arrows 124, 126, 128, and 130; solid arrows 224, 226, 228, and 230). In addition, each of the resources 110, 114, 118, and 122 (in FIG. 2B, 210, 214, 218, and 222) executes a protocol (SOAP) request header in a protocol (SOAP) request message for a business transaction. Associate with a thread and thus propagate the Protocol (SOAP) request header in the Protocol (SOAP) request message to any other requests made within the same thread of execution for the business transaction.

As mentioned above, preferably, each of the four resources 110, 114, 118, and 122 (210, 214, 218, and 222 in FIG. 2B) as well as the transaction manager 106 (in FIG. 2B). 206 has a tooled SOAP stack so that when a SOAP request message is issued from transaction manager 106 (207 in FIG. 2B) to resource 1 (reference numeral 110 in FIG. 1B and 210 in FIG. 2B) (arrow in FIG. 1B). 108; arrow 208 of FIG. 2B), the tool-based SOAP stack on resource 1 may follow the instructions in the request header in the SOAP request message 108 (208 in FIG. 2B). Thus, resource 1 collects the performance metrics requested by transaction manager 106 (206 in FIG. 2B) in the SOAP header of SOAP request message 108 (208 in FIG. 2B). Similarly, when request message 108 (208 in FIG. 2B) is forwarded, resource 1 (reference number 110) propagates the request header included in SOAP request message 108, which is referred to as resource 2 (see FIG. 1B). Number 114 and 214 in FIG. 2B (arrow 112 in FIG. 1B; arrow 212 in FIG. 2B), so that the tooled SOAP stack on resource 2 has a transaction in the SOAP header of SOAP request message 108 (208 in FIG. 2). Collect its own performance metrics for resource 2 requested by manager 106 (206 in FIG. 2). Once again, when message 108 (208 in FIG. 2B) is forwarded from Resource 2 (114 in FIG. 1B, 214 in FIG. 2) to Resource 3 (118 in FIG. 1B, 218 in FIG. 2B), Resource 2 propagates the request header contained within SOAP request message 108 (208 in FIG. 2B) and sends it to resource 3 (arrow 116 in FIG. 1B, arrow 216 in FIG. 2B), which is a tool-based SOAP stack on resource 3 Collect its own performance metrics for resource 3 requested by transaction manager 106 (206 in FIG. 2B) in the SOAP header of this SOAP request message 108 (208 in FIG. 2B). In addition, when message 108 (208 in FIG. 2B) is forwarded from resource 3 (reference number 118 in FIG. 1B, 218 in FIG. 2B) to resource 4 (122 in FIG. 1B, 222 in FIG. 2B), the resource is 3 propagates the request header contained within the SOAP request message 108 (208 in FIG. 2B) and sends it to resource 4 (arrow 120 in FIG. 1B, arrow 220 in FIG. 2B), which results in a tool SOAP stack on resource 4 It collects its own performance metrics requested by the transaction manager 106 (206 in FIG. 2B) in the SOAP header of the SOAP request message 108 (208 in FIG. 2B). As a result, the protocol request header in the protocol request message is replicated over all exchanges or messages associated with the business transaction.

In one embodiment, the tool SOAP stack on resources 110, 114, 118, and 112 (210, 214, 218, and 222 in FIG. 2B) collects performance metric or resource metric information and collects the collected information. Append to the SOAP response header in the response message belonging to the business transaction request. In particular, the performance metrics collected by resource 4 (reference numeral 122 in FIG. 1B and 222 in FIG. 2B) range from resource 4 (reference numeral 122 in FIG. 1B and 222 in FIG. 2B) to resource 3 (reference number 118 in FIG. 1B). , 218 in FIG. 2B) (arrow 214 in FIG. 1B; arrow 224 in FIG. 2B) to the SOAP response header in the SOAP response message. In turn, resource 3 (reference number 118 in FIG. 1B, 218 in FIG. 2B) adds the performance metrics collected by resource 3 to the SOAP response header in the SOAP response message received from resource 4, which is then assigned to resource 2 (in FIG. 1B). Reference numeral 114, 214 in FIG. 2 (arrow 126 in FIG. 1B; arrow 226 in FIG. 2B). In turn, resource 2 adds its collected performance metrics to the SOAP response header in the SOAP response message received from resource 3 and sends it back to resource 1 (reference number 110 in FIG. 1B and 210 in FIG. 2B) (arrow 128). Once again, resource 1 adds its collected performance metrics to the SOAP response header in the SOAP response message received from resource 2 and sends the SOAP response message back to transaction manager 106 (206 in FIG. 2B) ( Arrow 130 in FIG. 1B; arrow 230 in FIG. 2B). In addition, the tooltip SOAP stack, in the SOAP response header of the SOAP response message sent to the transaction manager 106 (206 in FIG. 2B), is in the same thread of execution for the business transaction prior to sending the SOAP response message to the transaction manager. Aggregate each of the one or more performance metrics collected for the resource serving any other requests made in the application. In addition, since the tooled SOAP stack on each resource is responsible for collecting metrics for that resource, it is desirable, but not required, that each resource have a tooled SOAP stack capable of collecting performance metrics. Thus, if the tool SOAP stack is installed on each of the resources 110, 114, 118, and 122 (210, 214, 218, and 222 in FIG. 2B), the tool SOAP stack on the preceding resource has its own performance. The metric can be added to the response header received from the subsequent resource they called. Accordingly, the final response header in the SOAP response message sent to the transaction manager 106 (206 in FIG. 2B) (solid arrow 130 in FIG. 1B; solid arrow 230 in FIG. 2B) may include resources 110, which contribute to the generic response. One response header with performance metrics for each of 114, 118, and 122 (210, 214, 218, and 222 in FIG. 2B). However, if a resource has a SOAP stack that is non-toolless (non-tool SOAP stack), the non-tool SOAP stack simply passes performance or resource load-monitoring headers to subsequent resources without collecting its own performance metrics. Thus, performance metrics for non-tool SOAP stacks on resources will not be included in the final response header in the response message sent to the transaction manager.

In one embodiment, the method includes one disposed on one or more of the resources 110, 114, 118, and / or 122 (210, 214, 218, and / or 222 in FIG. 2B) to manage the resource. And providing a resource manager 102 (202 in FIG. 2B) configured to collect one or more performance metric events from the at least one monitoring agent. Resource manager 102 (202 in FIG. 2B) is an application configured to receive events from monitoring agents running on resources. In addition, a monitoring agent is a program that runs on one or more resources, whose task is to monitor performance or resource metrics on these resources, such as CPU data, disk usage, and the like. If the monitoring agent observes something in question, for example, observing that a CPU on a resource has reached a 70% threshold, the monitoring agent generates an event (also called a performance metric event) and reports it to the resource manager 102. (202 in Fig. 2b). For example, as shown in FIGS. 1B and 2B, resource 1 (reference numeral 110 in FIG. 1B and 210 in FIG. 2B) may include a monitoring agent 134 (234 in FIG. 2B) that collects performance metrics on resource 1. Have The performance metrics collected by the monitoring agent 134 (234 in FIG. 2B) may be different than those requested by the transaction manager 106 (206 in FIG. 2B). Monitoring agent 134 (234 in FIG. 2B) sends the performance metrics collected for Resource 1 to resource manager 102 (202 in FIG. 2B) (dashed arrow 138 in FIG. 1B; dashed arrow 238 in FIG. 2B). . Resource manager 102 (202 in FIG. 2B) is configured to monitor agent 134 running on resource 1 (reference numeral 110 in FIG. 1B and 210 in FIG. 2B) when the performance metric for resource 1 exceeds a preset value. It is configured to receive alerts from 234 in FIG. 2B (dashed arrow 138 in FIG. 1B; dashed arrow 238 in FIG. 2B) so that resource manager 102 (202 in FIG. 2B) can take the appropriate action as needed. Similarly, resource 2 (reference numeral 114 in FIG. 1B and 214 in FIG. 2B) has a monitoring agent 136 (236 in FIG. 2B) that collects performance metrics for resource 2. Once again, monitoring agent 136 (236 in FIG. 2B) sends the collected performance metrics to resource manager 102 (202 in FIG. 2B) (dashed arrow 140 in FIG. 1B; dashed arrow 240 in FIG. 2B), Send an alert when the performance metric for resource 2 exceeds a preset value or threshold. As such, resource manager 102 (202 in FIG. 2B) is responsible for the individual resources 110 and 114 (resources 210 and 214 in FIG. 2B) with monitoring agents 134 and 136 running on them, respectively. Collect all resource or performance metric events. However, resource 3 (reference numeral 118 in Fig. 1B, 218 in Fig. 2B) and resource 4 (reference numeral 122 in Fig. 1B and 222 in Fig. 2B) do not have any monitoring agents on them, and resource 1 (Fig. 1B) Only information collected by monitoring agents 134 and 136 (234 and 236 in FIG. 2B) running on reference numeral 110 and 210 in FIG. 2B and resource 2 (reference numeral 114 in FIG. 1B and 214 in FIG. 2), respectively. This resource manager 102 passes (and passes to 202 in FIG. 2B). This is, for example, if resource 4 (reference numeral 122 in FIG. 1B and 222 in FIG. 2B) is slow (symbol 132 in FIG. 1B and 232 in FIG. 2B) due to exceeded performance metrics, eg, CPU usage. This performance information may not be communicated to resource manager 102 (202 in FIG. 2B). Thus, the problem regarding resource 4 is not solved. In addition, although the resource manager 102 (202 in FIG. 2B) does not actively transmit information to the transaction manager 106 (206 in FIG. 2B), the information from the resource manager 102 (202 in FIG. 2B), If requested by transaction manager 106 (206 in FIG. 2B), it will be forwarded to transaction manager 106 (206 in FIG. 2B) (double arrow 104 in FIG. 1B and double arrow 204 in FIG. 2B).

In yet another embodiment, methods 200a and 200b are provided for monitoring a business transaction served by one or more resources, as outlined in FIG. 2A and shown in FIG. 2B. The method includes at least each tool protocol encoding corresponding to a resource of each of the one or more resources such that each resource checks a total value for a performance metric in each protocol (SOAP) response header received from a subsequent resource. Preconfiguring the decoding component (tooled SOAP stack) into a policy or rule. Further, each resource sends an alert to the resource manager when the preset value for the performance metric for subsequent resources is exceeded. Thus, a tooled SOAP stack preconfigured with a policy or rule additionally acts as a monitoring agent and alerts the resource manager for a peer resource when it is determined that a preset value or preconfigured threshold for performance metrics on the peer resource has been exceeded. Can be transmitted. The alert may be implemented as a simple message sent directly to the resource manager indicating that the metric has exceeded a threshold or preset value. For example, as shown in FIG. 2B, resource 2 (reference number 214) may be configured to act as a monitoring agent for resource 3 (reference number 218) and / or resource 4 (reference number 222) of FIG. 2B. In FIG. 2B, there is a pre-configured tool SOAP stack with symbol 242. In particular, if a predetermined criterion or value has been preset for either or both of resource 3 and resource 4 in FIG. 2B, the tool-shaped preconfigured SOAP stack on resource 2 is assigned to resource 4 (reference number 214) and / or resource. The performance metrics received and collected from 3 (reference number 218) can be compared and it can be determined whether a particular preset threshold value or criterion has been met for resource 3 and / or resource 4 in FIG. Number 214 may send an alert to resource manager 302 for resource (referred to as resource 3 218) and / or resource 4 (reference number 222) (dashed arrow 218) and thus described above with respect to FIG. 1B. Unlike the situation described above, the resource manager 202 of FIG. 2B is alerted to the preset thresholds and / or criteria met. Thus, in one embodiment, only a few tool SOAP stacks are preconfigured with policies to act as monitoring agents that report events for other resources, minimizing the number of monitoring agents required to monitor resources over the network. And, in addition to communicating with peers about normal business transactions, minimizes connectivity issues that allow each and every one resource to communicate their status to a central monitoring infrastructure. In addition, in one embodiment, resource monitoring infrastructure or resource manager 202 provides a graphical user interface, where criteria or values for one or more performance metrics may be preset. Thus, when transaction manager 206 requests monitoring information, it can request both a specific performance metric and a performance metric when a predetermined preset value has been exceeded. In addition, a monitoring agent, such as monitoring agent 236, may still have some resources (e.g., even if the installed SOAP stack on resource 2 (reference number 214) is preconfigured with policies for comparison and alert transmission to resource manager 202). For example, the resource 2 may be installed on reference numeral 214 in FIG. 2B. For example, the monitoring agent 236 may monitor a different set of performance or resource metrics than those collected by the preconfigured tooling SOAP stack 242 on resource 2 (reference numeral 214).

In yet another embodiment, different embodiments of systems 100b and 200b for monitoring resources servicing a business transaction in a service-oriented architecture as described above are provided, as shown in FIGS. 1B and 2B. The system includes one or more resources configured to service business transactions (110, 114, 118, and 122 in FIG. 1B, and 210, 214, 218, and 222 in FIG. 2B). Here, at least one of the resources is arranged with a tool protocol stack, and preferably, each resource is equipped with a tool protocol stack. The system is equipped with a tooled protocol stack and monitors one or more performance metrics for business transactions served by the four resources in the protocol request header in the protocol request message sent to the four resources of FIGS. 1B and 2B. And a transaction manager (106 in FIG. 1B and 206 in FIG. 2B), configured to issue the transaction. Also in one embodiment, each of the four resources (shown in FIGS. 1B and 2B) collects one or more performance resources for the business transaction and collects one or more performance metrics in the protocol response header in the protocol response message sent to the transaction manager. It is configured to total. Here, the protocol request header in the protocol request message is associated with an execution thread for the business transaction, such that the protocol request header in the protocol request message is propagated to any other request made within the same execution thread for the business transaction. Thus, the protocol request header in the protocol request message is duplicated over all the exchanges associated with the business transaction as described in the method above. The system includes one or more capabilities from one or more resources, in particular one or more monitoring agents (134 and 136 in FIG. 1B and 234 and 236 in FIG. 2B) deployed on resources 1 and 3 shown in FIGS. 1B and 2B. It further includes a resource manager (102 in FIG. 1B and 202 in FIG. 2B) configured to collect metric events. In one embodiment, a transaction manager (106 in FIG. 1B and 206 in FIG. 2B) is a business serviced by one or more resources (110, 114, 118 and 122 in FIG. 1B and 210, 214, 218 and 222 in FIG. 2B). It is further configured to monitor one or more transaction metrics for the transaction, and monitored for one or more resources servicing the business transaction in light of one or more performance metrics collected by the one or more resources, as described in the method described above. And to analyze one or more trading metrics. In one embodiment, each preceding resource of one or more resources, such as resource 3 (118 in FIG. 1B, 218 in FIG. 2B), is each subsequent resource of one or more resources, such as a resource. And each set of performance metrics in the protocol response header in the protocol response message received from 4 (122 in FIG. 1B and 222 in FIG. 2B). In one embodiment, as shown in FIG. 2B, the tool protocol stack corresponding to a subset of one or more resources, eg, resource 2 (214 of FIG. 2B), is exceeded when the preset value for the performance metric is exceeded. Compare the total value of the performance metric in the protocol request header in the received protocol request message with the preset value for the performance metric so that the preconfigured resource (eg, resource 2 214) sends an alert to the resource manager 202. To do so, it consists of policies (symbol 242). In one embodiment, the tooling protocol stack comprises a tooling Simple Object Access Protocol (SOAP) stack, the protocol request header comprises a Simple Object Access Protocol (SOAP) request header, and the protocol response header is a SOAP (Simple Object) An Access Protocol (ACP) response header, wherein the protocol request message includes a Simple Object Access Protocol (SOAP) request message, and the protocol response message includes a Simple Object Access Protocol (SOAP) response message.

In yet another embodiment, a computer program product for monitoring metrics associated with a business transaction is provided. Preferably, the computer program product is in a form that is accessible from a computer usable or computer readable medium that provides program code or instructions for use in or in connection with a computer or any instruction execution system. For purposes of explanation, computer usable or computer readable media may comprise, store, transmit, propagate, or transport code or instructions for use by or in connection with an instruction execution system, apparatus, or device. It may be any device present. Preferably, the medium may be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or propagation medium. More preferably, computer readable media may include semiconductor or solid state memory, magnetic tape, removable computer diskette, random access memory (RAM), read-only memory (ROM), hard magnetic disk, and optical disk. . In addition, examples of the optical disk may include CD-ROM, CD-R / W, and DVD. Embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment including both hardware and software. Preferred embodiments may be implemented in software including, but not limited to, firmware, resident software, microcode, and the like.

The computer program product further includes first program instructions for providing a transaction manager configured to specify a collection of one or more performance metrics in a request header in a request message issued to one or more resources servicing a business transaction. Here, a tool protocol stack is disposed on each of the one or more resources and the transaction manager. The computer program product sends second program instructions for collecting one or more performance metrics specified in the request message and one or more performance metrics collected by the one or more resources servicing the business transaction to the transaction manager in the response header in the response message. It further comprises a second program instruction to. In one embodiment, the second program instruction associates the request header in the request message with an execution thread for a business transaction, and associates the request header in the request message with any other request messages created in the execution thread for that business transaction. It further includes instructions for propagating. Furthermore, in one embodiment, the second program instructions further include instructions for adding each set of performance metrics to a response header in a response message received from a subsequent one of the one or more resources and sending the response message to the transaction manager. Include. The computer program product compares the total value of one of the one or more performance metrics in each response header received from subsequent resources with a preset value for that performance metric, and the preset value for that performance metric is exceeded. And further comprising fourth program instructions to preconfigure the tool protocol stack disposed on the one or more resources into policies to send an alert to the resource manager. In one embodiment, the transaction manager is further configured to monitor one or more transaction metrics associated with the business transaction and analyze one or more transaction metrics monitored for the business transaction in light of one or more performance metrics collected from one or more resources. . In one embodiment, the tool protocol stack comprises a Simple Object Access Protocol (SOAP) stack and the request header comprises a Simple Object Access Protocol (SOAP) request header. In addition, the response header includes a Simple Object Access Protocol (SOAP) response header, the request message includes a Simple Object Access Protocol (SOAP) request message, and the response message includes a Simple Object Access Protocol (SOAP) response message. In one embodiment, each of the first, second, third, and fourth program instructions are stored on a computer readable medium.

Referring to FIG. 4, illustrated is a system 400 for determining an optimal configuration for implementing a capacity management service and its associated operating costs, in accordance with embodiments of the present invention. As shown, system 400 includes computer infrastructure 402, which is intended to represent any type of computer architecture maintained in a secured environment (ie, an environment in which access control is enforced). As shown, infrastructure 402 typically includes a computer system 400 representing a server or the like. However, although not shown, infrastructure 402 may include other hardware and software components (eg, additional computer systems such as application servers, management servers, routers, firewalls, etc.).

In general, a user (any one of users 1 432 through N) may interface with infrastructure 402 to conduct a business transaction. Similarly, any manager 436 and / or service provider 444 may be configured to monitor resources such as resource 1 (reference number 440) through resource N (reference number 442) serving business transactions. May interface with the infrastructure 402 to access it. Resource 1 (reference number 440) through resource N (reference number 442) may also interface with infrastructure 402 to service business transactions. As shown, resource 1 (reference number 440) has a tool protocol stack 441, and resource N (reference number 442) is a tool protocol stack 443. In addition, a tool protocol stack 416 is disposed in the transaction manager 414. As such, each of the resources preferably has a tooled protocol stack for communicating with transaction manager 4141. In addition, the resource manager 430 provides the transaction manager 414 with any information that may be requested about any resource metrics collected by the resource manager via the monitoring agent and / or resources acting as the monitoring agent. Interface with the computer system 404. Generally, the parties may, directly or via a network via interfaces (eg, a client web browser) loaded on a computerized device (eg, a personal computer, laptop, portable device, etc.), The infrastructure 402 can be accessed. In the latter case, the network may be any type of network, such as the Internet, or any other network, such as a local area network (LAN), wide area network (WAN), virtual private network (VPN), or the like. In any case, communication with infrastructure 402 may occur via a direct physically wired connection (eg, a serial port) or through an addressable connection using any combination of wired and / or wireless transmission methods. . In addition, conventional network connections may be used, such as Token Ring, Ethernet, WiFi, or other conventional communication standards. Again, the connection may be provided by a conventional TCP / IP socket based protocol. In this example, the party may use an internet service provider to establish a connection to infrastructure 402. It should be understood that infrastructure 402 may be owned and / or operated by a party or independent entity, such as provider 444. In any event, the use of infrastructure 402 and the teachings described herein may be provided to a party on a subscriber or fee basis. In another scenario, manager 436 may support and configure infrastructure 402.

Computer system or server 404 is shown to include a CPU, memory 412, bus 410, and input / output (I / O) interface 408. Computer system 400 is also shown in communication with external I / O device 424 and storage system 422. In the embodiment as shown, the storage system 422 provides a respective tooling protocol on any of each of resource 1 through resource N (reference numbers 440 and 442) such that the preconfigured resource additionally serves as a monitoring agent. Include policies or rules 426 that can be used to preconfigure stacks 441-443. In general, the processing unit 406 executes computer program code, such as the transaction manager application 414, which includes the tool protocol stack 416, in one embodiment, the tool SOAP stack. While executing the transaction manager application 414, the processing unit 406 may read / write data to the memory 412, the storage system 422, and / or the I / O interface 408. Bus 410 provides a communication link between each of the components in computer system 400. External device 424 interacts with computer system 400 and with any device (eg, network card, modem, etc.) that enables computer system 400 to communicate with one or more other computing devices. May include any device (eg, keyboard, pointing device, display, etc.) that is intended to function.

Computer infrastructure 402 is merely an example of various types of computer infrastructure for implementing embodiments of the present invention. For example, in one embodiment, computer infrastructure 402 includes two or more devices (eg, server clusters) that communicate over a network to perform various process steps. In addition, computer system 400 merely illustrates a variety of possible computer systems that may include various combinations of hardware. In other embodiments, computer system 400 may include any particular purpose article of manufacture, including specific purpose and general purpose hardware / software combinations, including hardware and / or computer program code for performing a particular function. Any computing article of manufacture and the like. In each case, program code and hardware may be generated using standard programming and engineering techniques, respectively. In addition, the processing unit 406 may include one processing unit and may be distributed across one or more locations, for example, one or more processing units on a client and a server. Similarly, memory 412 and / or storage system may include a combination of various types of data storage and / or transmission media present in at least one or more physical locations. Further, I / O interface 408 may include any system for exchanging information with one or more external devices 424. It will also be understood that one or more components (eg, system software, arithmetic coprocessor unit, etc., not shown in FIG. 4) may be included in the computer system 400. Similarly, one or more external devices 424 (eg, displays) and / or storage system (s) 422 may be included within computer system 404, not externally as shown.

The storage system 422 can be any type of system that can store information or data, such as a policy 426 that provides rules such as what the preconfigured protocol stack on a resource should do when a preset resource metric is exceeded (e.g., , Database). The storage system 422 can include one or more storage devices, such as a magnetic disk drive or an optical disk drive. In another embodiment, the storage system 422 may include data distributed across a local area network (LAN), wide area network (WAN), or storage area network (SAN) (not shown), for example. have. Although not shown, additional components, such as cache memory, communication systems, system software, and the like, can be incorporated into the computer system 400.

Thus, in one embodiment, transaction manager 414 may monitor the transaction metrics monitored for business transactions from the end user's point of view in view of the performance metrics collected from resource 1 (reference number 440) to resource N (reference number 442). Analyze and attempt to understand performance information along with any transaction metrics collected for resources 1 through N. For example, if the CPU on a given resource has reached its peak, but that resource is still meeting the desired target time to complete a transaction request, the performance metric for that resource may be considered acceptable. In addition, transaction manager 414 may obtain information from resource manager 430, for example, when a resource serving a particular transaction is not meeting a desired target time. In particular, the transaction manager 414 uses the data obtained through the monitoring agent or resources preconfigured with policies to act as a monitoring agent based on what performance metrics or data are transported by the resource manager 430. To understand the cause). For example, the transaction manager 414 may understand that the reason a given transaction did not meet the desired target time is due to a hard disk failure or excessive disk usage, and the like. Furthermore, data collected by resource manager 430 and transaction manager 414 may be passed to manager 436 and / or provider 444, thus providing resources to manager 436 and / or provider 444. It provides a much more comprehensive understanding of.

The foregoing descriptions of specific embodiments of the present invention have been presented for purposes of illustration and description. They are not intended to limit the invention to the disclosed forms only, and obviously many modifications and various variations are possible in light of the above teachings. The embodiments have been selected and described in order to best explain the principles of the present invention and its practical application, and thus enable those skilled in the art to make modifications and adaptations to suit the particular application contemplated by the present invention and various embodiments.

Claims (10)

In a method of monitoring resources serving a business transaction with a service-oriented architecture, Providing a transaction manager configured to monitor a business transaction serviced by one or more resources in a service-oriented architecture, wherein each of the one or more resources and the transaction manager require thereon one or more collections of performance metrics; Providing a transaction manager having a protocol encoding-decoding component configured to send a protocol request message and receive one or more protocol response messages including the collected performance metrics; Specifying a collection of one or more performance metrics for at least one of the one or more resources servicing the business transaction in a protocol request header in the one or more protocol request messages; Collecting the one or more performance metrics specified in the protocol request message; Sending, in a protocol response header in a protocol response message, to the transaction manager the one or more performance metrics collected by the at least one of the one or more resources servicing the business transaction. Including a resource monitoring method. The method of claim 1, wherein the providing step, Providing the transaction manager configured to monitor one or more transaction metrics associated with the business transaction; Providing the transaction manager configured to analyze the one or more transaction metrics monitored for the business transaction in light of the one or more performance metrics collected from the one or more resources. Resource monitoring method further comprising. The method of claim 2, wherein the providing step, Providing a resource manager configured to collect one or more performance metrics from one or more monitoring agents deployed on the one or more resources. The method of claim 3, wherein the step of specifying, Associating the protocol request header in the protocol request message with an execution thread for the business transaction; Propagating the protocol request header in the protocol request message to any other request made to the same thread of execution for the business transaction, wherein the protocol request header in the protocol request message is responsible for all exchanges associated with the business transaction. Is replicated through, resource monitoring method. The method of claim 4, wherein the specifying step comprises: Preconfiguring with the policy at least each protocol encoding-decoding component corresponding to each one of the one or more resources, Wherein each resource examines an aggregate value for one of the one or more performance metrics in each protocol response header received from a subsequent resource, Wherein each resource sends an alert to the resource manager when the preset value for the performance metric is exceeded. The method of claim 4, wherein the transmitting step, Adding, by each preceding resource of the one or more resources, each set of performance metrics to a protocol request header in a protocol response message received from each subsequent one of the one or more resources; Sending the protocol response message to the transaction manager Further comprising, resource monitoring method. The method of claim 5, wherein the transmitting step, Aggregating, in the protocol response header of the protocol response message, each of the one or more performance metrics corresponding to the one or more resources serving the other arbitrary request made within the same thread of execution for the business transaction; Sending the protocol response message to the transaction manager It further comprises a resource monitoring method. 8. The method of claim 7, wherein the protocol comprises a Simple Object Access Protocol (SOAP). In a system for monitoring the resources that service business transactions in a service-oriented architecture, One or more resources configured to service a business transaction, wherein one or more resources are arranged with a protocol stack; A protocol stack is in place and the plurality of one or more resources in the protocol request header in the protocol request message are to be monitored for one or more performance metrics for the business transaction serviced by the plurality of the one or more resources. A transaction manager configured to issue, wherein each of the plurality of one or more resources collects the one or more performance metrics for the business transaction and the one in a protocol response header in a protocol response message sent to the transaction manager. And aggregate the above performance metrics, wherein the protocol request header in the protocol request message is associated with an execution thread for the business transaction, and the protocol request header in the protocol request message is the non- Which is propagated to any other requests are made within the same thread of execution for the varnish transaction, the protocol request header in the protocol request message is to be replicated across all exchanges associated with the business transaction, the transaction manager Including, resource monitoring system. A computer program product for monitoring metrics associated with a business transaction, Computer readable media; A first program instruction for providing a transaction manager configured to specify a collection of one or more performance metrics in a request header in a request message issued to one or more resources servicing a business transaction, the one or more resources and the transaction manager. Each of the first program instructions having a protocol stack disposed thereon; Second program instructions for gathering the one or more performance metrics specified in the request message; Third program instructions for sending the one or more performance metrics collected by one or more resources servicing a business transaction to a transaction manager in a response header in a response message, Wherein the first, second, and third program instructions are stored on the computer readable medium.

Images