Method and apparatus for network-level monitoring of queue-based messaging systems

• US 7,127,507 B1
• Filed: 09/27/2001
• Issued: 10/24/2006
• Est. Priority Date: 09/27/2001
• Status: Expired due to Term

• Current Assignee: T-Mobile Innovations LLC (Deutsche Telekom AG)
• Original Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Inventors: Hathaway, Richard, Clark, Douglas W.
• Primary Examiner(s): Follansbee, John
• Assistant Examiner(s): Nguyen, Dustin
• Application Number:
  US09/965,255
• Time in Patent Office: 1,853 Days
• Field of Search: 707/10, 707/101, 709/201, 709/213, 709/202, 709/224, 717/127, 719/313, 719/314, 705/43, 370/356, 710/54
• US Class Current: 709/224
• CPC Class Codes: H04L 43/045 for graphical visualisation of monitoring data
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 47/2475 for supporting traffic characterised by the type of applications
• CPC Class Codes: H04L 47/30 in combination with information about buffer occupancy at either end or at transit nodes
• CPC Class Codes: H04L 49/9047 including multiple buffers, e.g. buffer pools

Abstract

A distributed computing environment and associated method for monitoring a queue-based messaging system. The queue-based messaging system controls the exchange of messages between a server process and client process applications. A messaging application residing at the server computer platform and forming part of the queue-based messaging system manages a plurality of trigger-initiated local queues, each associated with one of the plurality of client process applications and having queue depth, trigger enable, get enable and put enable attributes. A monitoring tool residing on the server computer platform acquires a value for the queue depth, trigger enable, put enable and get enable attributes for a plurality of trigger-initiated local queues and generally simultaneously displays, on a user interface coupled to the server computer platform, the value for the queue depth, trigger enable, put enable and get enable attributes for each one of the plurality of trigger-initiated local queues.

Claims

1. A distributed computing environment, comprising:

(a) a server computer platform on which a server process application resides;

(b) a plurality of client computer platforms coupled to said server computer platform, each one of said plurality of client computer platforms having a client process application residing thereon;

(c) a queue-based messaging system for controlling the exchange of messages between said server process application and said plurality of client process applications, said queue-based messaging system comprising a messaging application residing at each one of said server computer platform and said plurality of client computer platforms, said messaging application residing at said server computer platform managing a plurality of queues, each one of said plurality of queues described by a plurality of attributes; and

(d) a system for monitoring said queue-based messaging system, said monitoring system allowing a user to select at least two of said plurality of queues and four attributes selected from a group consisting of put, get, trigger and depth attributes, describing one or more of said plurality of queues and generating a display which simultaneously includes a current value for said selected attributes for each one of said selected queues described thereby.

2. The distributed computing environment of claim 1, wherein each one of said plurality of queues is a local queue for receiving messages originating at a corresponding one of said plurality of client process applications and destined for said server process application.

3. The distributed computing environment of claim 2, wherein a first one of said plurality of selected attributes is common to all queues and a second one of said plurality of selected attributes is unique to local queues.

4. The distributed computing environment of claim 3, wherein said second one of said plurality of selected attributes is a depth attribute.

5. The distributed computing environment of claim 3, wherein said first one of said selected attributes is a get attribute and said second one of said selected attributes is a depth attribute.

6. The distributed computing environment of claim 2, wherein first and second ones of said plurality of selected attributes are unique to local queues.

7. The distributed computing environment of claim 6, wherein said first one of said selected attributes is a trigger attribute and said second one of said selected attributes is a depth attribute.

8. The distributed computing environment of claim 7, wherein a third one of said plurality of selected attributes is common to all queues.

9. The distributed computing environment of claim 8, wherein said third one of said plurality of selected attributes is a get attribute.

10. A distributed computing environment, comprising:

a) a server computer platform on which a server process resides; and

b) at least five client computer platforms coupled to said server computer platform, each one of said plurality of client computer platforms having a client process application residing thereon;

c) a queue-based messaging system for controlling the exchange of messages between said server process application and said at least five client process applications, said queue-based messaging system comprising a messaging application residing at each one of said server computer platform and said at least five client computer platforms, said messaging application residing at said server computer platform managing at least five trigger-initiated local queues having a queue depth attribute, each one of said at least five trigger-initiated local queues associated with a corresponding one of said at least five client process applications;

d) a monitoring tool residing on said server computer platform, said monitoring tool acquiring a value for said queue depth attribute for each one of said at least five trigger-initiated local queues;

c) a user interface coupled to said server computer platform, said monitoring tool generally simultaneously displaying, on said user interface, said value for said queue depth attribute for each one of said at least five trigger-initiated local queues;

f) each one of said at least five trigger-initiated local queues has a trigger enable attribute, a get message enable attribute and a put message enable attribute;

g) said monitoring tool acquires a value for said trigger enable attribute, said get message enable attribute and said put message enable attribute for each one of said at least five trigger-initiated local queues; and

h) said monitoring tool generally simultaneously displaying, on said user interface, said value for said queue depth attribute, said value for said trigger enable attribute, said value for said get message enable attribute and said value for said put message enable attribute for each one of said at least five trigger-initiated local queues.

11. The distributed computing environment of claim 10, wherein:

a) each one of said at least five trigger-initiated local queues has a trigger enable attribute;

b) said monitoring tool acquires a value for said trigger enable attribute for each one of said at least five trigger-initiated local queues; and

c) said monitoring tool generally simultaneously displaying, on said user interface, said value for said queue depth attribute and said value for said trigger enable attribute for each one of said at least five trigger-initiated local queues.

12. The distributed computing environment of claim 10, wherein:

a) each one of said at least five trigger-initiated local queues has a get message enable attribute;

b) said monitoring tool acquires a value for said get enable attribute for each one of said at least five trigger-initiated local queues; and

c) said monitoring tool generally simultaneously displaying, on said user interface, said value for said queue depth attribute and said value for said get message enable attribute for each one of said at least five trigger-initiated local queues.

13. The distributed computing environment of claim 10, wherein:

a) each one of said at least five trigger-initiated local queues has a put message enable attribute;

b) said monitoring tool acquires a value for said put message enable attribute for each one of said at least five trigger-initiated local queues; and

c) said monitoring tool generally simultaneously displaying, on said user interface, said value for said queue depth attribute and said value for said put message enable attribute for each one of said at least five trigger-initiated local queues.

14. For a network having a server computer platform and a plurality of client computer platforms coupled to said server platform, a method for monitoring a queue-based messaging system which control the transfer of messages from said plurality of client computer platform to a corresponding plurality of queues residing at said server computer platform, comprising:

(a) selecting at least three attributes including at least one depth attribute and at least two operations control attributes, which describe each one of said plurality of queues;

(b) acquiring, from said server computer platform, a value for each one of said at least three attributes; and

(c) generally simultaneously displaying said value for each one of said at least three attributes for all of said plurality of queues.

15. The method of claim 14, and further comprising:

g) reviewing said display of said value for each one of said at least one attribute for all of said plurality of queues; and

h) initiating corrective action to rectify messaging failures identified from said review of said display.

16. The method of claim 15, and further comprising:

i) refreshing said display of said value for each one of said at least one attribute for all of said plurality of queues; and

j) initiating corrective action to rectify messaging failures identified from a comparison of said refreshed display to said display.

17. The method of claim 14, wherein the operations control attributes are selected from a group consisting of put attribute, get attribute, and trigger attribute.

18. The method of claim 14, wherein the action of selecting at least one operations control attributes comprises selecting at least two operations control attributes selected from a group consisting of put attribute, get attribute, and trigger attribute.

19. The method of claim 14, wherein the action of selecting at least one operations control attributes comprises selecting at least three operations control attributes selected from a group consisting of put attribute, get attribute, and trigger attribute.