Remotely monitoring a data processing system via a communications network

• US 7,389,341 B2
• Filed: 08/31/2001
• Issued: 06/17/2008
• Est. Priority Date: 01/31/2001
• Status: Active Grant

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture LLP (Accenture PLC)
• Inventors: Donoughe, Clifford, Krahn, Richard R., Sweeney, Michael S., Huffman, Arnold Z., Cornelius, Shawn S.
• Primary Examiner(s): Follansbee; John
• Assistant Examiner(s): DIVECHA, KAMAL B
• Application Number:
  US09/943,964
• Publication Number:
  US 20020103900A1
• Time in Patent Office: 2,482 Days
• Field of Search: 709/244, 709/224, 709/217, 709/223, 714/25, 370/242
• US Class Current: 709/224
• CPC Class Codes: G06F 11/0715 in a system implementing multitasking multitasking per se G06F9/46
• CPC Class Codes: G06F 11/0751 Error or fault detection not based on redundancy power supply failures G06F1/30; network fault management H04L41/06
• CPC Class Codes: G06F 11/079 Root cause analysis, i.e. error or fault diagnosis in a hardware test environment G06F11/22; in a software test environment G06F11/36
• CPC Class Codes: G06F 11/2294 by remote test
• CPC Class Codes: G06F 11/3017 where the computing system is implementing multitasking multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/302 where the computing system component is a software system
• CPC Class Codes: G06F 11/3051 Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs verification or detection of system hardware configuration G06F11/2247
• CPC Class Codes: G06F 11/3055 Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction by redundancy in operation G06F11/14; error detection or correction by redundancy in hardware G06F11/16
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/083 for increasing network speed
• CPC Class Codes: H04L 41/0836 to enhance reliability, e.g. reduce downtime
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 43/0817 by checking functioning

Abstract

A remote data processing system facilitates monitoring of the remote data processing system. The remote data processing system receives a data message via a communications network. The remote data processing system cascades at least a first stage software component and a second stage software component to form an installed remote software module for accepting the received data message. The remote data processing system detects the data message or a derivative at a group of logical nodes within the installed remote software module to determine flow of the data message, or a derivative thereof, between the logical nodes. The remote data processing system identifies a deficient software component of the installed remote software module as any of said software stage components that blocks or disrupts the flow of the data message between two adjacent logical nodes.

Claims

1. A remote data processing system comprising:

a data receiver for receiving a data message;

a remote software module arranged to receive the data message from the data receiver, the remote software module including at least a first stage software component cascaded with a second stage software component; and

a fault detector associated with the first software stage component and the second software stage component to detect a fault in the remote software module by detecting whether the data message or a derivative thereof flows entirely through at least one of the first stage software component and the second stage software component, wherein the fault detector has logical connections including a connection with an input of the first software stage component, an output of the first software stage component, and an output of second software stage component and wherein the fault detector identifies the first software stage as a faulty software component if the data message is present at an input of the first software stage, but not the output of the first software stage.

2. A remote data processing system comprising:

a data receiver for receiving a data message;

a remote software module arranged to receive the data message from the data receiver, the remote software module including at least a first stage software component cascaded with a second stage software component; and

a fault detector associated with the first software stage component and the second software stage component to detect a fault in the remote software module by detecting whether the data message or a derivative thereof flows entirely through at least one of the first stage software component and the second stage software component, wherein the fault detector has logical connections including a connection with an input of the first software stage component, an output of the first software stage component, and an output of second software stage component and wherein the fault detector identifies the second software stage as a faulty software component if the data message is present at an input of the second software stage, but not the output of the second software stage.

3. A remote data processing system comprising:

a data receiver for receiving a data message;

a remote software module arranged to receive the data message from the data receiver, the remote software module including at least a first stage software component cascaded with a second stage software component; and

a fault detector associated with the first software stage component and the second software stage component to detect a fault in the remote software module by detecting whether the data message or a derivative thereof flows entirely through at least one of the first stage software component and the second stage software component, wherein the fault detector has logical connections including a connection with an input of the first software stage component, an output of the first software stage component, and an output of second software stage component and wherein the fault detector identifies the first software stage as a faulty software component if a derivative of the data message is present at an input of the first software stage, but not the output of the first software stage.

4. A remote data processing system comprising:

a data receiver for receiving a data message;

a remote software module arranged to receive the data message from the data receiver, the remote software module including at least a first stage software component cascaded with a second stage software component; and

a fault detector associated with the first software stage component and the second software stage component to detect a fault in the remote software module by detecting whether the data message or a derivative thereof flows entirely through at least one of the first stage software component and the second stage software component, wherein the fault detector has logical connections including a connection with an input of the first software stage component, an output of the first software stage component, and an output of second software stage component and wherein the fault detector identifies the second software stage as a faulty software component if a derivative of the data message is present at an input of the second software stage, but not the output of the second software stage.

5. A method of monitoring a business-to-business system, the method comprising:

transmitting a status code from a base data processing system to a remote data processing system via a communications network;

receiving the status code at a data receiver in the remote data processing system;

inputting the status code into a remote software module of the remote data processing system;

determining whether the remote software module provides a logical data path of continuity to the status code;

outputting the status code from an output of the remote software module if the determining determines that the remote software module provides a logical data path of continuity to the status code; and

transmitting the outputted status code back to the base data processing system via the communications network as feedback indicative of the proper end-to-end continuity of communications in a business-to-business environment.

6. The method according to claim 5, the method further comprising:

storing the status code from an output of the remote software module as a dummy transaction in the database; and

retrieving the status code as the dummy transaction in the database and feeding the retrieved status code for transmission to the base data processing system if the database provides a logical data path of continuity for the status code.