Method, system, and computer program for monitoring performance of applications in a distributed environment

• US 8,037,205 B2
• Filed: 09/23/2008
• Issued: 10/11/2011
• Est. Priority Date: 06/25/2002
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Lam, Robert S., Chong, James C., Tsang, Arthur, Zychowski, Christopher M., Tang, Henry, Chan, Joseph L., So, Chi Hong, Banks, Jerome D., Patel, Tushar M., Heler, Jean Jacques, Chow, Raymond
• Primary Examiner(s): Nguyen; Tammy
• Application Number:
  US12/236,461
• Publication Number:
  US 20090019441A1
• Time in Patent Office: 1,113 Days
• Field of Search: 709/230, 709/246, 707/4, 707/102
• US Class Current: 709/246
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3072 where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
• CPC Class Codes: G06F 11/328 Computer systems status display G06F11/327 takes precedence
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 16/11 File system administration, e.g. details of archiving or snapshots file system backup G06F11/14
• CPC Class Codes: G06F 2201/81 Threshold
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 2201/88 Monitoring involving counting
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

A method, system, and computer program include receiving a request string, and mapping the received request string to a distinguishable request string and a collapsible request string. The received request string may be in the form of a JSP, a servlet, and remote Enterprise Java Bean calls. A user may be prompted to create rules for mapping of a received request string to a distinguishable request string and a collapsible request string.

Claims

1. A method for processing of requests, comprising:

receiving, using a computer, a request string from an application, wherein the request string is used for two different purposes, wherein a first purpose is as a request for identification, and wherein a second purpose is to represent a business request for the application;

receiving user created rules for mapping the received request string to one of a distinguishable request string and a collapsible request string;

mapping the received request string to two separate, distinct strings that are used for the different purposes by applying the received user created rules and;

mapping the received request string to the distinguishable request string; and

mapping the received request string to the collapsible request string;

performing a problem determination function of an active request search on the distinguishable request string; and

performing a performance management function of decomposition by request on the collapsible request string.

2. The method of claim 1, wherein the received request string is in the form of one of a JSP, a servlet, and remote Enterprise Java Bean calls.

3. The method of claim 1, further comprising:

prompting a user to create rules for mapping of the received request string to one of the distinguishable request string and the collapsible request string; and

applying the received user created rules to map the received request string to one of the distinguishable request string and the collapsible request string.

4. The method of claim 1, wherein the request string is a same form for the different purposes for an end user, and wherein the distinct strings representing the request string are used by an administrator during problem determination.

5. The method of claim 1, wherein the request string has implicit dual meanings associated with the two different purposes.

6. The method of claim 1, wherein the request string for the different purposes is in the same form for a portal site receiving the string request.

7. The method of claim 1, wherein the request string is a URL.

15. The method of claim 1, wherein the received request string is in the form of one of a JSP, a servlet, and remote Enterprise Java Bean calls.

8. A system for handling requests, comprising:

computer hardware and software for;

receiving a request string from an application, wherein the request string is used for two different purposes, wherein a first purpose is as a request for identification, and wherein a second purpose is to represent a business request for the application;

receiving user created rules for mapping the received request string to one of a distinguishable request string and a collapsible request string;

mapping the received request string to two separate, distinct strings that are used for the different purposes by applying the received user created rules and;

mapping the received request string to the distinguishable request string; and

mapping the received request string to the collapsible request string;

performing a problem determination function of an active request search on the distinguishable request string; and

performing a performance management function of decomposition by request on the collapsible request string.

9. The system of claim 8, wherein the received request string is in the form of one of a JSP, a servlet, and a remote Enterprise Java Bean call.

10. The system claim 8, further comprising:

the computer hardware and software for;

prompting a user to create rules for mapping of the received request string to one of the distinguishable request string and the collapsible request string; and

applying the received user created rules to map the received request string to one of the distinguishable request string and to the collapsible request string.

11. The system of claim 8, wherein the request string is a same form for the different purposes for an end user, and wherein the distinct strings representing the request string are used by an administrator during problem determination.

12. The system of claim 8, wherein the request string for the different purposes is in the same form for a portal site receiving the string request.

13. The system of claim 8, wherein the request string is a URL.

14. A computer program for processing of requests, said program consisting of instructions stored on a nontransitory computer storage medium, said instructions, when executed on a processor causing the processor to execute:

receiving a request string from an application, wherein the request string is used for two different purposes, wherein a first purpose is as a request for identification, and wherein a second purpose is to represent a business request for the application;

receiving user created rules for mapping the received request string to one of a distinguishable request string and a collapsible request string;

mapping the received request string to two separate, distinct strings that are used for the different purposes by applying the received user created rules and;

mapping the received request string to the distinguishable request string; and

mapping the received request string to the collapsible request string;

performing a problem determination function of an active request search on the distinguishable request string; and

performing a performance management function of decomposition by request on the collapsible request string.

16. The computer program of claim 14, wherein said instructions, when executed on a processor causing the processor to execute:

prompting a user to create rules for mapping of the received request string to one of the distinguishable request string and the collapsible request string; and

applying the received user created rules to map the received request string to one of the distinguishable request string and the collapsible request string.

17. The computer program of claim 14, wherein the request string is a same form for the different purposes for an end user, and wherein the distinct strings representing the request string are used by an administrator during problem determination.

18. The computer program of claim 14, wherein the request string has implicit dual meanings associated with the two different purposes.

19. The computer program of claim 14, wherein the request string for the different purposes is in the same form for a portal site receiving the string request.

20. The computer program of claim 14, wherein the request string is a URL.