User interface for system management applications

[0002] 1. Field of the Invention

[0003] The invention relates in general to user interfaces for computer systems, and more particularly, to a user interface for system management applications.

[0004] 2. Description of Related Art

[0005] Computer systems have become increasingly more complex as computers are used to perform more tasks in both the business and personal environments. Consequently, performance monitoring and system management of the computer systems has become more difficult, because the system interconnections, larger number of users, geographically diverse sources of data, and other items have made system management more complicated.

[0006] Further, each user of the system has different needs and desires for performance data presentation and system management data presentation. In conventional computer performance monitoring applications, the monitoring application generates a request for data, such as “How busy is the CPU?”. This request is sent by the monitoring application to a data subsystem having such information via the network transport system. The data subsystem returns the information requested to the monitoring application which then processes the data as required. Typically, the data is presented in a standardized format.

[0007] The systems to be monitored often include complex computer networks that may include mainframes, minicomputers, workstations, etc. The information to be monitored continuously becomes more complicated so that there are enormous amounts of information to be analyzed. In order to reduce the amount of data to be reviewed by the system operators, some techniques have been developed to further filter the data before it is reviewed by the operator. One example is the display by exception technique once the data has been collected, wherein the internal logic of the system displays data to the operator in accordance with a predicate logic test. The data that has been retrieved is compared to a predetermined predicate or threshold level and is displayed to the operator if and only if the data exceeds the predicate or threshold.

[0008] As the computer network systems to be monitored grow in size and complexity, the data to be monitored and tested grows the same way. What are needed are improvements in the presentation of system management data and performance data to reduce the substantial computational time, and other overhead requirements, of conventional monitoring applications.

[0009] It can be seen, then, that there is a need in the art for a management system that can manage diverse data sources. It can also be seen, then, that there is a need in the art for a management system that can present data in different formats.

[0010] To overcome the limitations in the prior art described above, and to overcome other limitations that will become apparent upon reading and understanding the present specification, the present invention discloses a system for presenting performance and system management data on a computer monitor. The system comprises a network, one or more presentation views, a data server, and a controller. The network interconnects a plurality of computer systems. The presentation views are defined in a memory of one of the computer systems in the network, receive commands for collecting selected performance data on the presentation view's associated computer system, and collect and present the selected performance data. The data server is executed by one of the computer systems in the network, generates requests for the selected performance data, and stores the collected selected performance data returned in response to the requests. The controller is executed by one of the computer systems in the network, translates the requests generated by the data server into the commands for the presentation views, transmits the commands to the presentation views, and forwards the collected performance data to the data server for storage.

[0011] The present invention allows for various data sources to be presented and compared within one window that is definable by the user, as opposed to multiple windows pre-defined by the authors of the System Management product(s). This allows users more flexible access to data, as well as better and more efficient use of computer resources.

[0012] These and various other advantages and features of novelty which characterize the invention are pointed out with particularity in the claims annexed hereto and form a part hereof. However, for a better understanding of the invention, its advantages, and the objects obtained by its use, reference should be made to the drawings which form a further part hereof, and to the accompanying detailed description, in which there is illustrated and described specific examples of a method, apparatus, and article of manufacture in accordance with the invention.

[0013] Referring now to the drawings in which like reference numbers represent corresponding parts throughout:

[0014] FIG. 1 is an exemplary hardware environment used to implement the preferred embodiment of the invention;

[0015] FIG. 2 illustrates an architectural view of a client according to the preferred embodiment of the present invention;

[0016] FIG. 3 illustrates the object request broker and object services of the present invention;

[0017] FIG. 4 illustrates an end-to-end data flow of the present invention;

[0018] FIG. 5 illustrates the workspace view of the present invention;

[0019] FIG. 6 illustrates a Properties view of the Workspace of the present invention;

[0020] FIGS. 7A-7B illustrate the filtering functions of the properties page of the present invention;

[0021] FIG. 8 illustrates the functions definitions for the filtered data of the properties page of the present invention;

[0022] FIGS. 9-11 illustrate the advanced filters dialogs used for manipulating the data of the present invention;

[0023] FIG. 12 is a flowchart that illustrates the general logic of a message or event-driven computer 12 performing the steps of the present invention; and

[0024] FIG. 13 is a flowchart illustrating the steps performed in practicing the present invention.

[0025] In the following description of the preferred embodiment, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration a specific embodiment in which the invention may be practiced. It is to be understood that other embodiments may be utilized and structural changes may be made without departing from the scope of the present invention.

[0026] Overview

[0027] The present invention discloses a system for presenting performance and system management data on a computer monitor. The system comprises a network, one or more workspaces, a data server, and a controller. The network interconnects a plurality of computer systems. The workspaces are defined in a memory of one of the computer systems in the network, receive commands for collecting selected performance data on the workspace's associated computer system, and collect and present the selected performance data. The data server is executed by one of the computer systems in the network, generates requests for the selected performance data, and stores the collected selected performance data returned in response to the requests. The controller is executed by one of the computer systems in the network, translates the requests generated by the data server into the commands for the workspaces, transmits the commands to the workspaces, and forwards the collected performance data to the data server for storage.

[0028] The present invention allows for various data sources to be presented and compared within one window that is definable by the user, as opposed to multiple windows pre-defined by the authors of the System Mangement product(s). This allows users more flexible access to data, as well as better and more efficient use of computer resources.

[0029] The present invention is a graphical user interface incorporating a user-authorable, multi-pane set of visual presentations that provide filtered views on one or more sets of data. The design introduces the concept of a workspace that associates a set of data of arbitrary origin with an extensible set of specific visual presentations, filtered by user-authorable logical expressions. The complete definition of a workspace is preserved in an external data store. The definitions can be associated with specific end-user identifiers, e.g., logon ID's, or can be generically keyed to allow access by a wider set of end-users, e.g., by department or user group. The definitions can also be linked together and parameterized to facilitate contextual navigation between workspaces. Each workspace can be assigned a name, called a workspace alias, that allows direct retrieval of a workspace by the end-user. The user interface supports multiple, independent frame windows being active concurrently, thus allowing multiple, independent workspaces to be viewed simultaneously.

[0030] Hardware Environment

[0031] FIG. 1 is a block diagram that illustrates an exemplary hardware environment for the present invention. The present invention is typically implemented using a computer network 10, which includes a plurality of interconnected computer systems 12, each of which may comprise mainframes, minicomputers, workstations, LAN servers, personal computers, etc., and each of which may execute any number of different application programs. The exemplary environment illustrated in FIG. 1 is not intended to limit the present invention. Indeed, other alternative hardware environments may be used without departing from the scope of the present invention. Each computer system 12 typically contains a processor 14 and a data storage device 16. Some computer systems 12 have external data storage devices 16 as shown.

[0032] The present invention is a network 10 monitoring system comprised of Data Servers 18, Agents 20, and Clients 22. Although only an exemplary configuration of Data Servers 18, Agents 20, and Clients 22 is illustrated in FIG. 1, any number of such components may be used in accordance with the present invention.

[0033] Generally, the Data Servers 18, Agents 20, and Clients 22 comprise computer programs that are tangibly embodied in a computer-readable medium or carrier, e.g. fixed and/or removable data storage and/or data communication devices. These computer programs may be loaded from such devices into the random access memory of one or more of the computer systems 12 for execution. These computer programs comprise instructions which, when read and executed by a computer system 12, cause the computer system 12 to perform the steps necessary to execute the steps or elements of the present invention.

[0034] Data Server

[0035] The Data Server 18 collects and stores performance data from one or more computer systems 12 in the network 10. In the preferred embodiment, a relational database model is described, although persons of ordinary skill in the art could easily use other types of databases. As a relational database, the Data Server 18 is equipped with one or more data retrieval engines, such as those using conventional structured query language (SQL) statements. Data is stored in the Data Server 18 and retrieved therefrom by one or more application programs, including the Clients 22.

[0036] Each Data Server 18 may be located on any of the computer systems 12 or on a specialized computer system 12 which is linked with networked computer systems 12 by the network 10. Preferably, if there are multiple Data Servers 18 in the computer network 10, one of them is designated a Hub Data Server 18 that centrally manages and/or accumulates data from the other Data Servers 18.

[0037] Any application program may direct data and instructions to and from the Data Server 18 for storage and/or retrieval therein. Thereafter, by submitting an appropriate inquiry, such as an SQL statement, any application program may request the retrieval of such data in the Data Server 18.

[0038] Agent

[0039] The Agent 20 works in conjunction with the Data Server 18, and provides communication services with the Clients 22. The Agent 20 also translates requests received from the Data Server 18 into commands, collects data from the Clients 22, and forwards the data to the Data Server 18 for storage therein.

[0040] The Client 22 is illustrated as a single client, but can be many clients 22 to show that each user can define a unique Client that is customized to the user's desires and needs. There can be a global Client 22 or multiple Clients 22 on a single node or workstation 12 within the system 10.

[0041] Relationships and Operation

[0042] FIG. 2 illustrates an architectural view of a client according to the preferred embodiment of the present invention.

[0043] FIG. 2 illustrates Client 22 as it relates to the present invention. Client 22 acts as an interface between data server 18, input devices 200, and display device 202. Within client 22, there are several functions performed by model 204, workplace object 206, view 208, and controller 210. Workplace object 206 acts as a visual proxy for model 204. View 208 (also called presentation view, workspace, or presentation) is managed by workplace object 206 and uses controller 210 objects to interact with the outside world, i.e., input devices 200. Model 204, workplace object 206, and view 208 use the Observer pattern to communicate and synchronize state changes. Model 204 interacts with data server 18 to request and receive data for presentation via model 204, workplace object 206, and view 208. Each client 22 can have one or more model 204, workplace object 206, view 208, and controller 210 for display of data from data server 18 on display device 202.

[0044] This client 22 architecture is also influenced by a dimension of IBM's Systems Application Architecture (SAA) known as “Common User Access” (CUA '91). CUA '91 is a set of design guidelines for building object-oriented user interfaces. CUA '91 promotes separation of application data (models 204) from the presentation of the application data (views 208). The architecture introduces workplace objects 206 and containment. Workplace objects 206 are “visual proxies” associated with some underlying model 204 object. The workplace objects 206 allow the user to indirectly manipulate the state of underlying models 204 and launch different presentations (views 208) of that model 204. In this way, the workplace object 206 acts as a visual intermediary between the model 204 and the set of views 208 providing presentations of the state of that model 204.

[0045] FIG. 3 illustrates the object request broker and object services of the present invention. Client 22 needs a medium for communicating with data server 18 to obtain data, distribute objects, etc. from data server 18. Object request broker (ORB) 300 is the medium used in the present invention. Within client 22, an interface 302 is used to standardize the requests, etc. from view 208 to ORB 300. Similarly, interface 304 is used to standardize the interactions between data server 18 and ORB 300.

[0046] Data server 18 provides object-based services 306 to access, report, and otherwise manipulate the data requested by client 22. These services 306 are comprised of query service 308, reporting service 310, status service 312, authorization service 314, and other services 316. Further, data server 18 is comprised of an information base 318, a data server requester 320, and transport and other data handlers 322.

[0047] The query service 308 provides a general capability to support query operations on a collection of objects within data server 18. Query service 308 comprises general manipulation operations including selection, insertion, updating, and deletion of objects, as well as reading object contents. Query service 308 uses pluggable evaluator objects that are dynamically located and attached for each request sent to data server 18. The evaluator objects are responsible for interfacing with and transforming the results from a query.

[0048] The object reporting service 310 is responsible for generating reports based on pre-defined report definitions and ad-hoc report queries. The reporting service 310 generates report definitions directly as opposed to generating client 22 program packages based on pre-defined code template files. The object reporting service 310 interprets the definitions at run-time, formulates the appropriate query, applies any post-query data transformations to the query results (formatting, filtering, sorting, etc.), and delivers these results to the client 22 in some optimal form. This optimal form delivery scheme is an attempt to reduce the number of transformations a given set of data must go through to eventually be used at the client 22 in a view 208 context. For example, the optimal form for report data that is to be shown in a view 208 in chart form might be a delimited data series sequence, whereas a report being presented in a view 208 as a topological graph may be optimally organized as an ordered list of nodes and edge objects.

[0049] The object status service 312 is responsible for managing those object types that have active, non-static operational states. Examples include managed objects, managed systems, and work lists. The status service 312 is a distributed component and thus makes no assumptions about the location of interested observers. The status service supports distributed notification by utilizing the ORB 300 (typically the Common Object Request Broker Architecture, known as CORBA) Event Service, which is a standardized mechanism for implementing the observer pattern.

[0050] Authorization service 314 provides user authorization support for data server 18 to determine levels of access that can be granted to client 22. Some data stored on data server 18 may be protected from access by client 22, and authorization service 314 controls that access.

[0051] Other services 318 include a presentation service that provides access to the information base 318 containing presentation-related information. The presentation service maintains presentation information at a userid level, while still providing the capability for users to share presentation (view 208) data. Examples of the presentation data maintained by this service include contexts, workspaces, and presentation properties (e.g., background color associated with a chart, images used as tree view nodes, and fonts associated with object labels).

[0052] Information base 318 is a database of the data, objects, etc. that is accessed by data server 18. The information base 318 is accessed through data server requester 320, and transportation and other data manipulation of the information base 318 is provided through transport 322.

[0053] FIG. 4 illustrates an end-to-end data flow of the present invention.

[0054] Data server 18, with object services 306, i.e., query service 308, reporting service 310, status service 312, authorization service 314, and presentation and other services 316, sends object data, etc. via ORB 300 to client 22. Within client 22, the object data is divided into models 204, workplace objects 206, and finally, view 208. View 208 is presented in a certain context 400, which has root 402, panes 404 of view 208, adapters 406, and filters 408. Context 400 allows the user to customize the view 208 to present the object data in a specific manner.

[0055] FIG. 5 illustrates the workspace view of the present invention.

[0056] To present the data to the user, display device 202 typically presents windows of data and text. As shown in FIG. 5, display device 202 presents view 208 to the user, which is also known as a workspace. Within view 208, there are selection tools 500, presentation types 502, status line 504, panes 506, tabs 508, and pane tools 510.

[0057] Selection tools 500 allow the user to select presentations 502 that are available for the selected object. Tool 512, for example, allows a user to select a stacking bar chart for the view 208.

[0058] Presentations 502 are different visual presentations of the data model associated with the currently selected object. Tree 514 is illustrated in pane 506 and is known as the navigator pane 506. Tree 514 illustrates a tree structure that shows logical interactions between presentations and files. Workspace 516 is highlighted to illustrate to the user that is currently selected. The presentations 502 within panes 506 are all related to the context 516 that is currently selected.

[0059] Presentation 518 is a line graph of the data associated with the currently selected context 516. Presentation 520 is a chart of the data associated with the currently selected context 516.

[0060] Status line 504 gives the user the status of the data, e.g., ready, busy, reading, etc. This lets the user know that the data is either fully presented or is still being processed.

[0061] Panes 506 are user created areas within view 208 that present the data in a manner that the user selects. The panes 506 are “splittable,” e.g., they can be sized, separated, or otherwise manipulated to fit within view 208.

[0062] Tabs 508 illustrate that there are various views 208 associated with the currently selected workspace 516. Any number of tabs 508 show the user that there are one, two, or several views 208 associated with the currently selected workspace 516. As shown in FIG. 5, there are five views 208 (Workspaces A through E) associated with workspace 516.

[0063] Pane tools 510 are tools to manipulate or otherwise view the data within that given pane 506.

[0064] This multiple, user-definable data view 208 on display 202 allows for a user to correlate data in various formats and from various sources. For a user that is only concerned with a small amount of data within the system, a single pane 506 may be sufficient. However, for a computer system manager, a usage by process bar chart or pie. chart may be more useful, and multiple panes 506 or multiple tabs 508 for several views 208 may be more suitable.

[0065] Each Client 22 can be associated with a given specific identifier to allow a user to access the Client 22. One specific identifier that can be used is user logon identifications (logon ID). This way, each user will, upon logging on to the system, have access to and, if desired, be placed in, Client 22, and therefore views 208, that they created and are most familiar with.

[0066] Each user can define more than one view 208, as shown by tabs 508, depending on the data and the tasks that the user wishes to monitor. Thus, a user can have multiple views 208 that the user can choose from, or, alternatively, have running simultaneously, so that the user can monitor data from several different places at once on different Clients 22, and possibly on different computer systems 12.

[0067] FIG. 6 illustrates a Properties view of the Workspace of the present invention.

[0068] Display 202 is also used by the user to tailor the views within the Workspace to better present the data to the user's needs and desires. Properties window 600 contains several visual aids that assist the user in determining what view 208 will look like once the user has set all of the properties in the properties window 600. One area of the Properties window 600 is the object property tree 602, which organizes and groups the properties of the Workspace 400 for perusal and traversal by the user. For each property of the Workspace 400, the user can select a view 604, e.g., Database Vitals, and the remainder of properties window 600 will give the user a presentation preview pane 606 and a tabbed set of property styles, filters, and functions panes 608 associated with that view 604. Other panes are possible depending on the view 604 selected. Each specific graphical presentation or view within a Workspace 400 is grouped by presentation type, e.g., bar chart, and is listed as a node (also known as a leaf node) in the property category tree 602.

[0069] The presentation preview pane (or dialog) 606 shows the user what the presentation will look like when shown in the Workspace 208. The presentation preview pane 606 is a representation of the visual presentation that will appear in one of the panes 506 when the Workspace 208 is selected. The tabbed pane 608 typically comprises one or more sub dialogs, such as a property group style dialog 610 and a selectable image map 612. A status line 614 is also provided for user information purposes.

[0070] The user can then customize view 208 to present the data selected (i.e., Database Vitals) in a manner most suitable to the user. In the case of properties window 600, the user has selected to view Database Vitals as a bar chart, shown in presentation window 606, with a header and a legend selected from selectable image map 612, and has selected to show the header, reading “Database Vitals,” in a twelve point Helvetica Bold font, selected from selectable image map 610.

[0071] FIGS. 7A-7B illustrate the filtering functions of the properties page of the present invention.

[0072] As shown in FIG. 7, properties window 600, and tabbed panes 608 can be selected to show the filters tab for the selected property 604. For the filter tabbed pane 608, the data is presented to show data snapshot 700, a toggle 704 to determine visibility of the data, a criteria selector 706, and advanced options 708 for other presentations of the data.

[0073] For any given set of data, certain data or certain events are crucial to users. The filters pane 608 allows the user to select those criteria and presentation formats that will alert the user to desired or critical events. The data snapshot 700 provides the user a set of data that is “frozen” in time. This allows the user to see how the data presentation will change as the user changes the values in filter pane 608. This is done using the presentation preview pane 606.

[0074] The user can also select whether or not to see the data using the visibility toggles 704. For each selected data criteria, the user can select criteria using the criteria selector 706. As shown, the user only wants to see percentage of CPU usage (%CPU) when it is greater than six (>6.0). If the user wants to perform more advanced data filtering, the advanced options selector 708 provides the user more flexibility in performing data manipulation and presentation.

[0075] FIG. 7B illustrates the threshold function page for the filtered data. For a given snapshot 700, the user can set a threshold for each specific piece of data to make the data easier to identify and determine if there is a problem within the system. Selector 710 allows a user to define a visual signal for each piece of data that, when the data exceeds a predefined threshold, will change the color or other presentation of the data within snapshot 700. Signals 712-716 are shown as examples of defining threshold data visual identifiers for the user. Signal 712 is a severe or urgent flag, usually a red color, but can be another identifier. Signal 714 is a warning or moderate alarm or visual flag, which is a notification to the user that something is approaching critical or severe limits, but has not reached the level of signal 712. Signal 714 usually a yellow color, but can be another identifier. Signal 716 is a notification or lesser alarm than signal 714, and is typically a blue color, but can be another identifier. There can be more signals 712-716 if desired, and the red, yellow, and blue signals indicated for signals 712-716 are not intended to limit the present invention.

[0076] FIG. 8 illustrates the functions definitions for the filtered data of the properties page of the present invention.

[0077] Using the data snapshot 700, the user can define new values for presentation based on the filtered data specified on the filters pane 608. The user can specify an expression on the expressions pane 800, e.g., “SUM,” to provide a defined value for that variable. Other defined values, such as average, greatest, least, etc., are also definable by the user.

[0078] FIGS. 9-11 illustrate the advanced filters dialogs used for manipulating the data of the present invention.

[0079] FIGS. 9-11 illustrate tabbed dialogs within window 900. Window 900 is activated and shown to the user on display 202 when the user selects the advanced button 708 shown in FIG. 7. The user can select any of the tabbed dialogs 902-906. Tabbed dialog 902 shown in FIG. 9 allows the user to turn sorting on and off, sort the attributes in ascending or descending order, and choose which attributes are to be sorted for a given view 208.

[0080] FIG. 10 shows dialog 904, which allows the user to select limits on the filter and activate or deactivate the limits selected. FIG. 11 shows dialog 906, which allows the user to create groups of attributes and select criteria to group attributes for display within view 208.

[0081] Logic of the Management Interface

[0082] FIG. 12 is a flowchart that illustrates the general logic of a message or event-driven computer 12 performing the steps of the present invention. In such a computer 12, operations are performed when transitions are made, based upon the receipt of messages or events, from present or current states to new states.

[0083] Generally, the flowchart begins by waiting at block 1200 for an event (e.g., a mouse button click). It should be appreciated that during this time, other operating system tasks, e.g., file, memory, and video tasks, etc., may also be carried out. When an event occurs, control passes to block 1202 to identify the event. Based upon the event, as well as the current state of the system determined in block 1204, a new state is determined in block 1206. In block 1208, the logic transitions to the new state and performs any actions required for the transition. In block 1210, the current state is set to the previously determined new state, and control returns to block 1200 to wait for more input events.

[0084] The specific operations that are performed by block 1208 when transitioning between states will vary depending upon the current state and the event. The various operations required to implement and maintain the Client of the present invention represent particular events handled by the logic. However, it should be appreciated that these operations represent merely a subset of all of the events handled by the computer 12.

[0085] FIG. 13 is a flowchart illustrating the steps performed in practicing the present invention.

[0086] Block 1300 represents the client 22 generating a request for data from the data server 18.

[0087] Block 1302 represents the computer system 12 translating the request for data into a collect data command at the controller.

[0088] Block 1304 represents the computer system 12 transmitting the command from the controller to the data server 18.

[0089] Block 1306 represents the computer system 12 collecting the requested data from the data server 18 at the client 22.

[0090] Block 1308 represents the computer system 12 presenting the requested data in a defined presentation view at the Client 22.

[0091] In parallel with block 1308, block 1310 represents the computer system 12 forwarding the collected data from the Client 22 to the data server. Block 1312 represents the computer system 12 storing the data at the data server, either at the data storage device or other storage media.

[0092] This concludes the description of the preferred embodiment of the invention. The following describes some alternative embodiments for accomplishing the present invention. For example, any type of computer, such as a mainframe, minicomputer, or personal computer, could be used with the present invention. In addition, any software program adhering (either partially or entirely) to the technique of multi-threading and/or object-oriented programming could benefit from the present invention.

[0093] In summary, the present invention discloses a system for presenting performance and system management data on a computer monitor. The system comprises a network, one or more presentation views, a data server, and a controller. The network interconnects a plurality of computer systems. The presentation views are defined in a memory of one of the computer systems in the network, receive commands for collecting selected performance data on the presentation view's associated computer system, and collect and present the selected performance data. The data server is executed by one of the computer systems in the network, generates requests for the selected performance data, and stores the collected selected performance data returned in response to the requests. The controller is executed by one of the computer systems in the network, translates the requests generated by the data server into the commands for the presentation views, transmits the commands to the presentation views, and forwards the collected performance data to the data server for storage.

[0094] The present invention allows for various data sources to be presented and compared within one window that is definable by the user, as opposed to multiple windows defined by the authors of the operating system for the computer. This allows users more flexible access to data, as well as better and more efficient use of computer resources.

[0095] The foregoing description of the preferred embodiment of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto.