End to end component mapping and problem - solving in a network environment

CROSS-REFERENCES TO RELATED APPLICATIONS, AND COPYRIGHT NOTICE

P-0001[0001] The present application is related to co-pending applications entitled Method and System for Probing in a Network Environment, application Ser. No. 10/062,329, filed on Jan. 31, 2002, Method and System for Performance Reporting in a Network Environment, application Ser. No. 10/062,369, filed on Jan. 31, 2002, and Graphics for End to End Component Mapping and Problem—Solving in a Network Environment, filed on even date herewith. These co-pending applications are assigned to the assignee of the present application, and herein incorporated by reference. A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

FIELD OF THE INVENTION

P-0002[0002] The present invention relates generally to information handling, and more particularly to end to end component mapping and problem

P-0003[0003] solving, for information handling in a network environment.

BACKGROUND OF THE INVENTION

P-0004[0004] Various approaches have been proposed for monitoring, simulating, or testing web sites. Examples include U.S. Pat. No. 6,278,966 B1 (Howard, et al., Aug. 21, 2001), “Method and System for Emulating Web Site Traffic to Identify Web Site Usage Patterns.” However, this example addresses substantially different problems (problems of simulation and hypothetical phenomena), and thus is significantly different from the present invention. Other examples include U.S. Pat. No. 6,078,956 (Bryant, et al., Jun. 20, 2000) and U.S. Pat. No. 5,787,254 (Maddalozzo, et al., Jul. 28, 1998). Other examples include services available from vendors such as Atesto Technologies Inc., Keynote Systems, and Mercury Interactive Corporation. These services may involve a script that runs on a probe computer. The examples mentioned above do not necessarily provide means for directing problem-solving efforts.

P-0005[0005] A wide variety of valuable services are provided through client-server applications, so proper performance of these applications may be very important. When a problem occurs, lack of useful information can hamper efforts to restore the proper performance of a client-server application. These applications may involve many hardware and software components in a network environment, so it may be difficult to quickly identify a component that is causing a problem. Thus there is a need for systems and methods that provide information to properly focus problem—solving efforts for client-server applications, including but not limited to web sites and web services.

SUMMARY OF THE INVENTION

P-0006[0006] An example of a solution to problems mentioned above comprises providing input from probes, with the input including events generated by an application probe, and events generated by a component probe, and correlating the events. This example solution may further comprise identifying a component problem that is a cause of a performance problem affecting a user of a client—server application.

P-0007[0007] Another example of the solutions provided comprises representing components and events with structured identifiers, each having a limited number of parameters. This example solution may further comprise employing the identifiers to do one or more tasks such as inputting data, storing data, outputting data and relating an event to a corrective action.

BRIEF DESCRIPTION OF THE DRAWINGS

P-0008[0008] A better understanding of the present invention can be obtained when the following detailed description is considered in conjunction with the following drawings. The use of the same reference symbols in different drawings indicates similar or identical items.

P-0009[0009]FIG. 1 illustrates a simplified example of an information handling system that may be used to practice the present invention.

P-0010[0010]FIG. 2 is a block diagram illustrating one example of how the present invention was implemented in a data center that hosted a web site.

P-0011[0011]FIG. 3 is a diagram showing an example of identifying a problem with one or more components, according to the present invention.

P-0012[0012]FIG. 4 is a flow chart illustrating one example of how end to end component mapping and problem solving may be implemented in an information technology consulting or design context.

P-0013[0013]FIG. 5 is a flow chart illustrating one example of how end to end component mapping and problem solving may be implemented in an operations context.

DETAILED DESCRIPTION

P-0014[0014] The examples that follow involve the use of one or more computers and may involve the use of one or more communications networks. The present invention is not limited as to the type of computer on which it runs, and not limited as to the type of network used.

P-0015[0015] The following are definitions of terms used in the description of the present invention and in the claims:

P-0016[0016] “Availability” means ability to be accessed or used.

P-0017[0017] “Business process” means any process involving use of a computer by any enterprise, group, or organization; the process may involve providing goods or services of any kind.

P-0018[0018] “Client-server application” means any application involving a client that utilizes a service, and a server that provides a service. Examples of such a service include but are not limited to: information services, transactional services, access to databases, and access to audio or video content.

P-0019[0019] “Comparing” means bringing together for the purpose of finding any likeness or difference, including a quantitative likeness or difference. “Comparing” may involve answering questions including but not limited to: “Is a measured response time greater than a threshold response time?” Or “Is a response time measured by a remote probe significantly greater than a response time measured by a local probe?”

P-0020[0020] “Component” means any element or part, and may include elements consisting of hardware or software or both.

P-0021[0021] “Computer-usable medium” means any carrier wave, signal or transmission facility for communication with computers, and any kind of computer memory, such as floppy disks, hard disks, Random Access Memory (RAM), Read Only Memory (ROM), CD-ROM, flash ROM, non-volatile ROM, and non-volatile memory.

P-0022[0022] “Measuring” means evaluating or quantifying.

P-0023[0023] “Event” means any action initiated by a computer or a user, including the sending of alerts, warnings, or other signals.

P-0024[0024] “Outputting” means producing, transmitting, or turning out in some manner, including but not limited to printing on paper, or displaying on a screen, or using an audio device.

P-0025[0025] “Performance” means execution or doing; “performance” may refer to any aspect of an application's operation, including availability, response time, time to complete batch processing or other aspects.

P-0026[0026] “Probe” means any computer used in evaluating, investigating, or quantifying the functioning of a component or the performance of an application; for example a “probe” may be a personal computer executing a script, acting as a client, and requesting services from a server.

P-0027[0027] “Response time” means elapsed time in responding to a request or signal.

P-0028[0028] “Script” means any program used in evaluating, investigating, or quantifying performance; for example a script may cause a computer to send requests or signals according to a transaction scenario. A script may be written in a scripting language such as Perl or some other programming language.

P-0029[0029] “Service level agreement” means any oral or written agreement between provider and user. For example, “service level agreement” includes but is not limited to an agreement between vendor and customer, and an agreement between an information technology department and an end user. For example, a “service level agreement” might involve one or more client—server applications, and might include specifications regarding availability, response times or problem—solving.

P-0030[0030] “Storing” data or information, using a computer, means placing the data or information, for any length of time, in any kind of computer memory, such as floppy disks, hard disks, Random Access Memory (RAM), Read Only Memory (ROM), CD-ROM, flash ROM, non-volatile ROM, and non-volatile memory.

P-0031[0031] “Structured identifier” means any definition, label, tag, or other means of identifying something, with a certain arrangement or order.

P-0032[0032] “Threshold value” means any value used as a borderline, standard, or target; for example, a “threshold value” may be derived from a service level agreement, industry norms, or other sources.

P-0033[0033]FIG. 1 illustrates a simplified example of an information handling system that may be used to practice the present invention. The invention may be implemented on a variety of hardware platforms, including embedded systems, personal computers, workstations, servers, and mainframes. The computer system of FIG. 1 has at least one processor <b>110</b>. Processor <b>110</b> is interconnected via system bus <b>112</b> to random access memory (RAM) <b>116</b>, read only memory (ROM) <b>114</b>, and input/output (I/O) adapter <b>118</b> for connecting peripheral devices such as disk unit <b>120</b> and tape drive <b>140</b> to bus <b>112</b>. The system has user interface adapter <b>122</b> for connecting keyboard <b>124</b>, mouse <b>126</b>, or other user interface devices such as audio output device <b>166</b> and audio input device <b>168</b> to bus <b>112</b>. The system has communication adapter <b>134</b> for connecting the information handling system to a data processing network <b>150</b>, and display adapter <b>136</b> for connecting bus <b>112</b> to display device <b>138</b>. Communication adapter <b>134</b> may link the system depicted in FIG. 1 with hundreds or even thousands of similar systems, or other devices, such as remote printers, remote servers, or remote storage units. The system depicted in FIG. 1 may be linked to both local area networks (sometimes referred to as Intranets) and wide area networks, such as the Internet.

P-0034[0034] While the computer system described in FIG. 1 is capable of executing the processes described herein, this computer system is simply one example of a computer system. Those skilled in the art will appreciate that many other computer system designs are capable of performing the processes described herein.

P-0035[0035]FIG. 2 is a block diagram illustrating one example of how the present invention was implemented in a data center that hosted a web site. FIG. 2 shows a simplified example of a typical e-business infrastructure, including a variety of network, server, and middleware components. These components are symbolized by server <b>270</b>, server <b>280</b>, and the boxes visible behind server <b>270</b> and server <b>280</b>. As an overview, this example comprised: providing input from a plurality of probes, including events (symbolized by arrows pointing to console <b>205</b>) generated by at least one application probe (shown at <b>221</b>) and at least one component probe (shown at <b>271</b>); and correlating the events. FIG. 2 shows application probe <b>221</b> and component probe <b>271</b> providing input (symbolized by arrows) to console <b>205</b>, which was used in correlating the events.

P-0036[0036] Turning now to some details of the example implementation, application probes such as probe <b>221</b> measured response time for requests. The double-headed arrow connecting local application probe <b>221</b> with application <b>201</b> symbolizes requests and responses.

P-0037[0037] We located application probes locally at hosting sites (e.g. local application probe shown at <b>221</b>, within data center <b>211</b>) and remotely at relevant end-user sites (not shown in this diagram). This not only exercised the application code and application hosting site infrastructure, but also probed the ability of the application and network to deliver data from the application hosting site to the remote end-user sites. End-to-end measurement of IBM external applications (symbolized by application <b>201</b> with web pages <b>202</b>) for customers or business partners, for example, involved remote application probes (RAP's) on the Internet (shown at <b>290</b>). We also measured the availability and performance of the application at the location where it was deployed (local application probe shown at <b>221</b>, within data center <b>211</b>). This provided baseline performance measurement data, that could be used for analyzing the performance measurements from the remote probes (not shown in this diagram).

P-0038[0038] Local application probe <b>221</b> was implemented with a personal computer, utilizing IBM's Enterprise Probe Platform technology, but other kinds of hardware and software could be used. A local application probe <b>221</b> was placed on the IBM network just outside the firewall at the center where the web site was hosted. A local application probe <b>221</b> was used to probe one specific site per probe. There could be multiple scripts per site. A local application probe <b>221</b> executed the script every 20 minutes. Intervals of other lengths also could be used.

P-0039[0039] Component probe <b>271</b> could be implemented with a personal computer running a script, but other kinds of hardware and software could be used. Component probe <b>271</b> could be implemented with software products (such as those available from TIVOLI, for example, or other similar products). These products provide a framework for probing infrastructure components. These products are available for various operating systems and middle ware components.

P-0040[0040] Another aspect of this example in FIG. 2 was providing an alert (i.e. an event signaling a problem) when probe <b>221</b> or probe <b>271</b> detected an error. An example of an error in application <b>201</b> would be a measured response time value greater than a corresponding threshold value. For example, if a local application probe <b>221</b> encountered a problem (e.g. it was unable to access the site or unable to complete the script) on two consecutive executions of the script, local application probe <b>221</b> generated a real time alert (problem event, symbolized by arrow pointing to console <b>205</b>), and sent it to a TIVOLI management system (shown as console <b>205</b>). Another similar kind of management system could be used. Thus an alert was provided via a system management computer. An alert message via email also could be used. Similarly, component probe <b>271</b> generated a problem event (symbolized by arrow pointing to console <b>205</b>) when a component problem was detected.

P-0041[0041] Turning now to some details of providing input from a plurality of probes, <i>Component Probes </i>measure availability, utilization and performance of infrastructure components, including servers, LAN, and services. <i>Local component probes </i>(LCPs) may be deployed locally in hosting sites, service delivery centers or data centers (e.g. at <b>211</b>).

P-0042[0042] Network Probes measure network infrastructure response time and availability. Remote Network Probes (RNPs) may be deployed in a local hosting site or data center (e.g. at <b>211</b>) if measuring the intranet or at Internet Service Provider (ISP) sites if measuring the Internet.

P-0043[0043] Application Probes measure availability and performance of applications and business processes.

P-0044[0044] Local Application Probe (LAP): Application probes deployed in a local hosting site or data center (e.g. at <b>211</b>) are termed Local Application Probes.

P-0045[0045] Remote Application Probe (RAP): An application probe deployed from a remote location is termed a Remote Application Probe.

P-0046[0046] The concept of “probe” is a logical one. Thus for example, implementing a local component probe could actually consist of implementing multiple physical probes.

P-0047[0047] Providing a script for an application probe would comprise defining a set of transactions that are frequently performed by end users. Employing a plurality of application probes would comprise placing at least one remote application probe (not shown in FIG. 2) at each location having a relatively large population of end users. Note that the Remote Application Probe transactions and Local Application Probe transactions should be the same transactions. The example measured all the transactions locally (shown at <b>221</b>), so that the local application response time can be compared to the remote application response time. This can provide insight regarding application performance issues. End-to-end measurement of an organization's internal applications for internal customers will involve a RAP on an intranet, whereas end-to-end measurement of an organization's external applications for customers, business partners, suppliers, etc. will involve a RAP on the Internet (shown at <b>290</b>). The example involved defining a representative transaction set, and deploying remote application probes at relevant end-user locations. (This simplicity is something that can only be appreciated when this example is contrasted with other more complicated models.) A benefit following from the simplicity of this example is that it is easily generalized to other environments besides web based applications. Application <b>201</b> may be any client-server application. Some examples are a web site, a web application, database management software, a customer relationship management system, an enterprise resource planning system, or an opportunity—management business process where a client directly connects to a server.

P-0048[0048] The example in FIG. 2 comprised providing an alert when an error occurred. The alert may be provided via email, for example, or may be provided in real time via a network and a system management computer <b>205</b>. A clearing message may be provided when the error no longer is detected. In the example shown in FIG. 2, local application probe <b>221</b> generated a real time alert (problem event), and sent it to a TIVOLI management system (shown as console <b>205</b>). Another similar kind of management system could be used.

P-0049[0049] The local application probe <b>221</b> automatically sent events to the management console <b>205</b> used by the operations department. In the example solution, integration was provided with the TIVOLI MANAGEMENT ENVIRONMENT and the TIVOLI EVENT CONSOLE product. The example solution generated events from the local application probe <b>221</b>, and the events were generated after two consecutive errors on the same step in the business process. This could then be adjusted to send an event on the first error, for even faster notification. The recommendation is to send events on the second occurrence initially and then adjust to sending the event on the first occurrence as the environment becomes more stable and better understood by the operational staff. The reason for the recommendation is that in a Web environment there are a number of things that can cause intermittent problems, and it is ultimately a business decision when to invoke problem determination procedures.

P-0050[0050] Consider the following example of a condition where an event was generated. This example involved probing a web site for selling computer hardware. There were executions of the probe script that failed on step two. (Regarding the steps involved, see Table 1 below.) The associated event sent to the TIVOLI ENTERPRISE CONSOLE had a severity of “Warning,” and documented the failure of step two, where the probe was unable to log on to the web site. Note that the date and time is the local time from the probe. In the examples below, “CRT” refers to a type of probe technology used by IBM. An example of an alert follows.

P-0051[0051] Tivoli alert for CRT probe failure:

P-0052[0052] Tivoli CRT Alert—PC NA

P-0053[0053] WARNING (NAQS2 [LogonFailed/1])

P-0054[0054] PCNa—Partner Commerce North America CRT Monitor

P-0055[0055] tag:auth=crtGwaFw

P-0056[0056] tag:message=PartnerCommerceNA https://ecna.partner.com Step-NAQS2-failed: Logon failed.

P-0057[0057] tag:severity=WARNING

P-0058[0058] tag:slot hostname=d03bpec18.pinfo.com

P-0059[0059] tag:slot mail_svr=CVRM

P-0060[0060] tag:slot mta=ecna.partner.com

P-0061[0061] tag:slot probe_addr=NAQS2

P-0062[0062] tag:slot probe_date=07/21

P-0063[0063] tag:slot probe time=19:58

P-0064[0064] tag:class=crt_event

P-0065[0065] tag:source=SENTRY

P-0066[0066] It is useful to automatically close opened events if a subsequent business process is executed successfully. This allows the operational staff to direct time and efforts to those events that remain in “open” status. Below is an example of such an event which was used to automatically close the previously opened event. The event was reported as severity HARMLESS and with the appropriate rules defined on the TIVOLI ENTERPRISE CONSOLE the previously opened event would be closed. This HARMLESS event was generated when the probe successfully executed the script and was able to log on to the web site. An example of such an event follows.

P-0067[0067] Tivoli alert for CRT probe failure:

P-0068[0068] Tivoli CRT Alert—PC NA

P-0069[0069] HARMLESS (NAQS2 [Recoveredzf/0])

P-0070[0070] PCNa—Partner Commerce North America CRT Monitor

P-0071[0071] tag:auth=crtGwaFw

P-0072[0072] tag:message=PartnerCommerceNA https://ecna.partner.com Step-NAQS2-failed: The problem causing the previous alert has been fixed.

P-0073[0073] tag:severity=HARMLESS

P-0074[0074] tag:slot hostname=d03 bpec18.pinfo.com

P-0075[0075] tag:slot mail svr=CVRM

P-0076[0076] tag:slot mta=ecna.partner.com

P-0077[0077] tag:slot probe_addr=NAQS2

P-0078[0078] tag:slot probe date=07/21

P-0079[0079] tag:slot probe_time=21:43

P-0080[0080] tag:class=crt_event

P-0081[0081] tag:source=SENTRY

P-0082[0082]FIG. 3 is a diagram showing an example of identifying a problem with one or more components, according to the present invention. FIG. 3 illustrates how operational staff may establish relationships among a component problem <b>301</b>, events <b>321</b> and <b>371</b> generated by probes, and performance problem <b>391</b> that affects a customer or other end user. Methods and systems are provided herein for assisting operational staff in reducing mean time to repair a component problem <b>301</b>, and thus solve a performance problem <b>391</b>, for example. In FIG. 3, a component problem <b>301</b> is a root cause of a performance problem <b>391</b>, that affects a user of a client—server application. Component problem <b>301</b> is associated with events generated by probes: event <b>321</b>, generated by an application probe, and event <b>371</b>, generated by a component probe.

P-0083[0083] Event <b>321</b> signals a performance problem with an application. For example, event <b>321</b> might be similar to the problem event described above regarding FIG. 2, where a probe was unable to log on to a web site; or event <b>321</b> might be generated when a “time out” problem is encountered at some transaction step. In this example, event <b>371</b> might alert operational staff that a disk failure has occurred on a server. In that case, component problem <b>301</b> would be a disk failure. Methods and systems are provided herein for correlating events such as event <b>321</b> and event <b>371</b>.

P-0084[0084] The example in FIG. 3 may involve component problem <b>301</b> causing a performance problem <b>391</b>, that affects a customer of a business. Thus the example in FIG. 3 may involve identifying component problem <b>301</b>'s impact on a business process that employs the component. Instead of a complete failure, performance problem <b>391</b> might be a response time that becomes too long to be acceptable for a customer. Such a situation might deserve intervention by operational staff before a complete failure occurs, depending on the importance of a business process that employs the component. Thus the example in FIG. 3 may involve directing problem—solving efforts, or identifying an opportunity to improve the performance of a client—server application, whether or not a complete failure occurs.

P-0085[0085]FIG. 4 is a flow chart illustrating one example of how end to end component mapping and problem solving may be implemented in an information technology consulting or design context. This example begins with identifying transaction steps, at block <b>410</b>. These transaction steps could be any steps that involve a client-server application. Some examples are steps involved in using a web site, a web application, web services, database management software, a customer relationship management system, an enterprise resource planning system, or an opportunity—management business process. The output from identifying transaction steps, at block <b>410</b>, may be a table containing the transaction step number, step name, and a description of what action the end user takes to execute the step. Table 1 below is an example of such a table, based on a web site for selling computer hardware. <tables id="TABLE-US-00001" num="1"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="49PT" align="left" /><colspec colname="2" colwidth="77PT" align="left" /><colspec colname="3" colwidth="77PT" align="left" /><thead><row><entry /><entry namest="OFFSET" nameend="3" align="center">TABLE 1</entry></row><row><entry /><entry /></row><row><entry /><entry namest="OFFSET" nameend="3" align="center" rowsep="1" /></row><row><entry /><entry>Step No.</entry><entry>Step name</entry><entry>Description</entry></row><row><entry /><entry namest="OFFSET" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>NAQS1</entry><entry>Open URL</entry><entry>Go to URL http://</entry></row><row><entry /><entry>NAQS2</entry><entry>Logon</entry><entry>Enter Login</entry></row><row><entry /><entry /><entry /><entry>ID/Password. Click</entry></row><row><entry /><entry /><entry /><entry>on Logon button.</entry></row><row><entry /><entry>NAQS3</entry><entry>Navigation 1</entry><entry>Click on Personal</entry></row><row><entry /><entry /><entry /><entry>Systems and</entry></row><row><entry /><entry /><entry /><entry>NETFINITY</entry></row><row><entry /><entry>NAQS4</entry><entry>Clear Form</entry><entry>Select ‘Clear the</entry></row><row><entry /><entry /><entry /><entry>form’. Click “ok” on</entry></row><row><entry /><entry /><entry /><entry>pop-up window.</entry></row><row><entry /><entry>NAQS5</entry><entry>Select Catalog</entry><entry>Select Catalog Order</entry></row><row><entry /><entry /><entry /><entry>from left hand</entry></row><row><entry /><entry /><entry /><entry>navigation bar</entry></row><row><entry /><entry>NAQS6</entry><entry>Select Printers</entry><entry>Select Printers</entry></row><row><entry /><entry>NAQS7</entry><entry>Select Printer Model</entry><entry>Select Infoprint</entry></row><row><entry /><entry>NAQS8</entry><entry>Add to Order</entry><entry>Type 1 in Quantity</entry></row><row><entry /><entry /><entry /><entry>box for 1st item</entry></row><row><entry /><entry /><entry /><entry>Click Add to Order,</entry></row><row><entry /><entry /><entry /><entry>Click OK on pop-up</entry></row><row><entry /><entry /><entry /><entry>window</entry></row><row><entry /><entry>NAQS9</entry><entry>Display Order Form</entry><entry>Click on Go to order</entry></row><row><entry /><entry /><entry /><entry>form</entry></row><row><entry /><entry>NAQS10</entry><entry>Validate Order</entry><entry>Click Save/Validate</entry></row><row><entry /><entry /><entry /><entry>Items</entry></row><row><entry /><entry>NAQS10A</entry><entry>Home Page</entry><entry>Click on “Overview”</entry></row><row><entry /><entry /><entry /><entry>link</entry></row><row><entry /><entry>NAQS11</entry><entry>Logoff</entry><entry>Click Logoff. Click</entry></row><row><entry /><entry /><entry /><entry>“ok” on popup</entry></row><row><entry /><entry namest="OFFSET" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

P-0086[0086] Another possible output from identifying transaction steps, at block <b>410</b>, may be a script to run on a local application probe or remote application probe.

P-0087[0087] Next in this example in FIG. 4 is block <b>420</b>, identifying components associated with the transaction steps; this may involve identifying application components and identifying infrastructure components. A variety of network, server, and middle ware components may be identified. This may include resources indirectly involved with transaction steps, such as a link to a back-end system providing data to web site. This link might only be used during the night to push new content to a web site. If the link becomes unavailable, the web site will contain incorrect data. This might cause customer dissatisfaction or loss of revenue.

P-0088[0088] A possible output from identifying components, at block <b>420</b>, may be a table containing the transaction step name, the name of an application supporting the step, and the data center where the application is hosted. Table 2 below is an example of such a table. <tables id="TABLE-US-00002" num="2"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="OFFSET" colwidth="21PT" align="left" /><colspec colname="1" colwidth="77PT" align="left" /><colspec colname="2" colwidth="63PT" align="left" /><colspec colname="3" colwidth="56PT" align="left" /><thead><row><entry /><entry namest="OFFSET" nameend="3" align="center">TABLE 2</entry></row><row><entry /><entry /></row><row><entry /><entry namest="OFFSET" nameend="3" align="center" rowsep="1" /></row><row><entry /><entry /><entry>Supporting</entry><entry>Data</entry></row><row><entry /><entry>Step name</entry><entry>Application</entry><entry>center</entry></row><row><entry /><entry namest="OFFSET" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>Open URL</entry><entry>Application 1</entry><entry>Boulder</entry></row><row><entry /><entry>Logon</entry><entry>Application 2</entry><entry>Southbury</entry></row><row><entry /><entry>Navigation 1</entry><entry>Application 1</entry><entry>Boulder</entry></row><row><entry /><entry>Clear Form</entry><entry>Application 1</entry><entry>Boulder</entry></row><row><entry /><entry>Select Catalog</entry><entry>Application 1</entry><entry>Boulder</entry></row><row><entry /><entry>Select Printers</entry><entry>Application 1</entry><entry>Boulder</entry></row><row><entry /><entry>Select Printer Model</entry><entry>Application 1</entry><entry>Boulder</entry></row><row><entry /><entry>Add to Order</entry><entry>Application 1</entry><entry>Boulder</entry></row><row><entry /><entry>Display Order Form</entry><entry>Application 1</entry><entry>Boulder</entry></row><row><entry /><entry>Validate Order</entry><entry>Application 3</entry><entry>Portsmouth</entry></row><row><entry /><entry>Home Page</entry><entry>Application 1</entry><entry>Boulder</entry></row><row><entry /><entry>Logoff</entry><entry>Application 1</entry><entry>Boulder</entry></row><row><entry /><entry namest="OFFSET" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

P-0089[0089] Another example of possible output from identifying components, at block <b>420</b>, may be a table such as Table 3 below. It identifies infrastructure components that support the individual applications. <tables id="TABLE-US-00003" num="3"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="56PT" align="left" /><colspec colname="2" colwidth="56PT" align="left" /><colspec colname="3" colwidth="56PT" align="left" /><colspec colname="4" colwidth="49PT" align="left" /><thead><row><entry namest="1" nameend="4" align="center">TABLE 3</entry></row><row><entry /></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row><row><entry /><entry>Infrastructure</entry><entry>Middleware</entry><entry>Network</entry></row><row><entry>Application</entry><entry>dependencies</entry><entry>dependencies</entry><entry>dependencies</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>Application 1</entry><entry>d0xx2111,</entry><entry>MQSeries</entry><entry>Link 9</entry></row><row><entry /><entry>d0xx2113,</entry><entry>Channel A</entry></row><row><entry /><entry>d0xx2115</entry></row><row><entry>Application 2</entry><entry>d0xx2112</entry><entry>MQSeries</entry><entry>Link 9,</entry></row><row><entry /><entry /><entry>Channel B</entry><entry>Link 12</entry></row><row><entry>Application 3</entry><entry>d0xx2119</entry><entry>DB/2 database</entry><entry>Link 15</entry></row><row><entry /><entry /><entry>Customer data</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

P-0090[0090] Next in this example is block <b>430</b>, providing input associated with the transaction steps, from a plurality of probes. Typically the input would include at least one event generated by an application probe, and at least one event generated by a component probe. Providing input may further comprise determining specifications to support the deployment of the probes.

P-0091[0091] Determining specifications may further comprise determining a plurality of specifications such as: a resource specification; a threshold value specification; an event severity specification; and an event class specification. For example, a resource specification would define an infrastructure resource to be probed, such as file space used on a server. A threshold value specification might be “file space 80% full,” for example. Examples of event severity specifications “warning” and “harmless” were given above in connection with FIG. 2. Regarding an event class specification, an infrastructure support team might address storage—related problems, and that team's console would be configured to receive the “sentry” class of events, for example. Various kinds of hardware and software resources would require various kinds of specifications to support the deployment of the probes.

P-0092[0092] Next in this example in FIG. 4 is block <b>440</b>, correlating events. For example, one may confirm a relationship between an event generated by an application probe, and an event generated by a component probe, as described above in connection with FIG. 3. A tool to help in correlating events is representing each of the components and each of the events with a structured identifier, where each of the identifiers has a limited number of parameters. The parameters typically would include depth, component name, parent component, business process name, and criticality. Other parameters could be used as well. Regarding the depth parameter, for example, one implementation used a hierarchy with a limited number of levels, where Level 0 was the highest level of a business process. Level 6, the lowest level, contained events generated by component probes (e.g. a component probe on server). Some examples of representing each component and each event with a structured identifier are shown below in Table 4. This example involved a business process for customer relationship management called “CRM2000,” at Level 0. Each line in Table 4 contains the same business process name, “CRM2000.” This allows correlating events, and allows identifying a component problem's impact on a business process that employs the component. <tables id="TABLE-US-00004" num="4"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 4</entry></row></thead><tbody valign="top"><row><entry /></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Examples of structured identifiers for some components</entry></row><row><entry>and events</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="5"><colspec colname="1" colwidth="35PT" align="left" /><colspec colname="2" colwidth="42PT" align="left" /><colspec colname="3" colwidth="49PT" align="left" /><colspec colname="4" colwidth="42PT" align="left" /><colspec colname="5" colwidth="49PT" align="left" /><tbody valign="top"><row><entry /><entry /><entry /><entry>BUSINESS</entry><entry /></row><row><entry>DEPTH/</entry><entry /><entry>PARENT</entry><entry>PROCESS</entry><entry /></row><row><entry>LEVEL</entry><entry>NAME</entry><entry>COMPONENT</entry><entry>NAME</entry><entry>CRITICALITY</entry></row><row><entry namest="1" nameend="5" align="center" rowsep="1" /></row><row><entry>3</entry><entry>Timeout</entry><entry>Open Leads</entry><entry>CRM2000</entry><entry>Warning</entry></row><row><entry>5</entry><entry>d0xx</entry><entry>GWA</entry><entry>CRM2000</entry><entry>Critical</entry></row><row><entry>6</entry><entry>Inetd</entry><entry>d0xx</entry><entry>CRM2000</entry><entry>Critical</entry></row><row><entry>6</entry><entry>Disk failure</entry><entry>d0xx</entry><entry>CRM2000</entry><entry>Critical</entry></row><row><entry namest="1" nameend="5" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

P-0093[0093] Table 4 shows an example using five parameters (depth, name, parent component, business process name, and criticality) to give a logical view of a business process, its components and events. This example used levels numbered from 0 to 6. Level 0 was the highest level of a business process, CRM2000. Level 1 contained components (subprocesses) of CRM2000: “Marketing” and “Sales.” Level 2 contained a subprocess of Sales: a “Lead Opportunity Management” application, with a user interface utilized by end users. Level 3 contained transaction steps, and events generated by application probes. Level 4 contained logical components in the infrastructure, such as IBM's Global Web Architecture (GWA), an environment that hosts web servers. Level 5 contained infrastructure components such as servers. Level 6, the lowest level, contained events generated by component probes. Component “d0xx” was a server. “Timeout” was an event generated by an application probe; “Inetd” and “Disk failure” were events generated by component probes.

P-0094[0094] Variations in the depth parameter are possible. Another example used levels numbered from 0 to 7, where hardware and software classes of components were at Level 6, and the events “Inetd” and “Disk failure” were at Level 7.

P-0095[0095] The event “Inetd” indicated a problem with a software component (inetd, the Internet super—server daemon, in an operating system such as UNIX, LINUX, or IBM's AIX). The event “Disk failure” indicated a problem with a hardware component (a disk).

P-0096[0096] In contrast to Table 4, a structured identifier may be expressed in plain text, following this pattern, for example: (Depth, Component Name, Parent Component, Business Process Name, Criticality). For example a software component “inetd” could have the following identifier: (6, inetd, d0xx1, CRM2000, Critical). This identifier identifies the position of each component, and retains the data pertaining to its relationships and dependencies. The same software component “inetd,” regarding its utilization in another application or business process called “CVRM,” could have the following identifier: (6, inetd, d0xx1, CVRM, Critical).

P-0097[0097] Some examples of additional parameters that could be used with the five parameters shown above are problem determination, destination, and service level agreement parameters. First, an additional parameter for problem determination (PD) can be added. The purpose of this parameter would be to associate problem determination procedures to every event generated. This parameter could be used to identify the actions or procedures to be used when this event is generated. These actions or procedures can be automatic (e.g. identifying a program or function to be automatically executed when the event occurs). Another implementation could be to use this parameter as an index into an operational repository to retrieve written instructions to be followed to correct the problem. Depending on the missions of different organizations, the operational procedures will vary. In the example in Table 4, where we had a problem with the inetd daemon, the automated PD process could be to run the appropriate shell script to restart the inetd daemon. In the case of a disk crash, the operational procedure could be a reference to a document describing how to replace broken hardware and apply the necessary backup and restore procedures. On depth level 2 the PD parameter could refer to an automated or written process for how the business owner of the process is contacted and informed about the business impact of the infrastructure problem.

P-0098[0098] A second example would be to add a destination parameter to the event. Most likely several different teams are involved in the management of an end to end business process. These teams have different missions and accordingly different roles and responsibilities. For example an eBusiness Center could have a mission to manage the end to end process from a customer perspective and the service delivery centers could perform traditional information technology services. The destination (i.e. a target audience or event console) parameter could be used to indicate that the event documenting the disk crash has been sent to an event console used by the service delivery center with a responsibility to address infrastructure problems. The service delivery center may receive the disk crash event as CRITICAL. The same event could be sent to different destinations with different values in the criticality parameter, depending on the roles and responsibilities of the target audience. The disk crash event could be sent to the eBusiness Command Center and could have a criticality value of WARNING.

P-0099[0099] Thirdly, Service Level Agreements (SLA's) are most likely in place for the whole end to end system and in many cases the individual components. Adding an SLA parameter would allow this parameter to be used as an index into a repository of existing SLA's. Again, these SLA's differ based on the missions of the organizations, so the end to end SLA documents the availability agreement for the customer process, and the SLA for infrastructure documents hardware availability etc. Since these SLA's are commitments by the service providers and could impose penalties, it is useful to direct problem resolution activities in accordance with the service level commitments. More sophisticated implementations could include automatic data collection for SLA attainment calculations.

P-0100[0100] In various situations, various combinations of these parameters may be used. For example, an enterprise could use the problem determination parameter but not the SLA parameter (they may not have an SLA). Another situation could be an enterprise who has an SLA but has not implemented automated or manual operational processes in support of their SLA commitments.

P-0101[0101] To conclude the description of FIG. 4, next in this example is block <b>450</b>, directing problem—solving efforts. Some examples of this were given above, regarding parameters and structured identifiers. Finally in this example is block <b>460</b>, improving performance; typically this would involve identifying an opportunity to improve the performance of one or more client—server applications. For example, performance degradation caused by specific components could be ascertained, and proactive measures could be taken to improve performance.

P-0102[0102]FIG. 5 is a flow chart illustrating one example of how end to end component mapping and problem solving may be implemented in an operations context. This example begins at block <b>510</b>, with providing input from a plurality of probes. Typically the input would include at least one event generated by an application probe, and at least one event generated by a component probe. Next in this example is block <b>520</b>, employing structured identifiers. Typically this would involve representing each of the components and each of the events with a structured identifier, where each of the identifiers has a limited number of parameters, as discussed above regarding Table 4. Structured identifiers may be employed to do one or more tasks such as inputting data, storing data, and outputting data. For example, operational staff could use a form similar to Table 4 above for inputting or outputting data. A form similar to Table 4 could be printed on paper or displayed on a screen. Other examples based on Table 4 would be utilizing a data structure in which each component and each event has a unique five-parameter identifier, or utilizing a programming object that includes a five-parameter identifier. Additional parameters could be used, as discussed above, with corresponding variations in forms or data structures.

P-0103[0103] Next in this example is block <b>530</b>, correlating events. As discussed above, a tool to help in correlating events is the structured identifier that identifies the position of each component and each event, and retains the data pertaining to its relationships and dependencies. For example, one may confirm a relationship between an event generated by an application probe, and an event generated by a component probe, as described above in connection with FIG. 3.

P-0104[0104] Next in this example in FIG. 5 is block <b>540</b>, identifying a component problem, followed by block <b>550</b>, solving the component problem (and thus solving the performance problem affecting a user of an application). Problem—solving examples involving hardware and software failures were given above, regarding parameters and structured identifiers. In another example mentioned above, performance degradation caused by specific components could be ascertained, and proactive measures could be taken to improve performance.

P-0105[0105] Those skilled in the art will recognize that blocks in the above-mentioned flow charts could be arranged in a somewhat different order, but still describe the invention. Blocks could be added to the above-mentioned flow charts to describe details, or optional features; some blocks could be subtracted to show a simplified example.

P-0106[0106] In conclusion, we have shown examples of methods and systems for End to end component mapping and problem—solving in a network environment.

P-0107[0107] One of the preferred implementations of the invention is an application, namely a set of instructions (program code) in a code module which may, for example, be resident in the random access memory of a computer. Until required by 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), or downloaded via the Internet or other computer network. Thus, the present invention may be implemented as a computer-usable medium having computer-executable instructions for use in a computer. In addition, although the various methods described are conveniently implemented in a general-purpose computer selectively activated or reconfigured by software, one of ordinary skill in the art would also recognize that such methods may be carried out in hardware, in firmware, or in more specialized apparatus constructed to perform the required method steps.

P-0108[0108] While the invention has been shown and described with reference to particular embodiments thereof, it will be understood by those skilled in the art that the foregoing and other changes in form and detail may be made therein without departing from the spirit and scope of the invention. The appended claims are to encompass within their scope all such changes and modifications as are within the true spirit and scope of this invention. Furthermore, it is to be understood that the invention is solely defined by the appended claims. It will be understood by those with skill in the art that if a specific number of an introduced claim element is intended, such intent will be explicitly recited in the claim, and in the absence of such recitation no such limitation is present. For non-limiting example, as an aid to understanding, the appended claims may contain the introductory phrases at least one or one or more to introduce claim elements. However, the use of such phrases should not be construed to imply that the introduction of a claim element by indefinite articles such as a or an limits any particular claim containing such introduced claim element to inventions containing only one such element, even when the same claim includes the introductory phrases at least one or one or more and indefinite articles such as a or an; the same holds true for the use in the claims of definite articles.