JP2000092054A - Network system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To surely and immediately inform of occurrence of a fault in a server device by executing a secondary fault notice for a prescribed client in response to the fault based on fault contents of a primary fault notice and a notice destination list only having to revise slightly the existing system. SOLUTION: Professional terminals 31,..., 3n acquire prescribed information from prescribed server devices 21,..., 2n via a network 1. When any of the server devices 21,..., 2n gets faulty, a fault detection means 5 detects it and a fault information notice means 6 transmits information relating to a defect that is detected to the network 1 as a primary fault notice. A management terminal 4 transmits a secondary fault notice denoting prescribed professional terminals 31,..., 3n in response to the fault to the network 1 based on fault contents of the primary fault notice and a notice destination list. Then a notice information display means 7 receives the secondary fault notice information to display the fault information of any of the server devices 21,..., 2n relating to the notice.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a network system in which a server device and a client device are connected via a network, and more particularly, to an improvement for notifying a user of a server device failure occurrence status. Things.

[0002]

2. Description of the Related Art In a network system in which a server device and a client device are connected via a network,
Each server device and each client device operate independently. Even if the client device itself is operable, if the server device goes down, predetermined information cannot be obtained from the server device. Sisters,
A predetermined service cannot be provided to the user of the client device. In addition, the user of the client device cannot grasp the cause of the service stoppage.

FIG. 21 shows a conventional network system.
It is a system configuration diagram showing a configuration in which a server device operation state management function for such measures is added by a minimum configuration change. In the figure, 1 is a network, 21
, 2n are connected to the network 1 respectively, server devices having unique server device names, 31,..., 3n are connected to the network 1, respectively.
, A business terminal device (client device) that acquires predetermined information from predetermined server devices 21,.
Is a management terminal device that manages the operation / stop of the server devices 21,..., 2n.

In each of the server devices 21,..., 2n, 5
Is a fault detecting means for detecting a fault occurring on the server device 21,..., 2n, and 6 is a fault information notifying means for transmitting information relating to the detected fault to the network 1 as a fault notification.

[0005] In the management terminal device 10, reference numeral 11 denotes a failure notification acquisition unit that receives the above-described failure notification, and 12 denotes a failure information display unit that displays failure information based on the failure notification.

Next, the operation will be described. , 3n acquire predetermined information from predetermined server devices 21,..., 2n via the network 1 in accordance with the operation of the user. In such an operation state, when the server device 21,..., 2n goes down, the failure detection means 5 detects the failure and the failure information notifying means 6 sends information on the detected failure to the network 1 as a failure notification. Then, the occurrence of the failure is displayed on the management terminal device 10.

[0007]

Since the conventional network system is configured as described above, the failure notification of the server devices 21,..., 2n to the business terminal devices 31,. To do
When the administrator of the management terminal device 10 operates the business terminal devices 31,.
3n must be notified, and if the server device 21,..., 2n goes down when this administrator is absent, the notification is delayed (or not notified). However, there has been a problem that unnecessary confusion or stagnation is caused in the work of the user.

In particular, in a distributed database system such as the World Wide Web in which the business terminal devices 31,..., 3n and the server devices 21,. It is difficult for the user to directly contact the administrator of the server device 21,..., 2n or the management terminal device 10, and confusion or stagnation of the business can be a serious problem.

In order to notify each user without making a significant change to the existing network system, each of the server devices 21,..., 2n most often outputs failure information in a broadcast system. Although it is an easy method, in such a notification method, the server device 2
Business terminal devices 31, ..., 3n not using 1, ..., 2n
In this case, the server devices 21,..., 2n are notified of the stoppage, which causes unnecessary confusion or stagnation in the business.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problems, and it is possible to immediately and surely cause a server device to fail in a client device by making only minor changes to an existing network system. It is an object of the present invention to provide a network system that can notify a user and that does not cause business disruption.

It is another object of the present invention to provide a network system which does not cause unnecessary confusion or stagnation in a business by notifying a client device having no relation to the client device at the same time.

[0012]

A network system according to the present invention comprises a network having a network, a server connected to the network, and a client for acquiring predetermined information from the server via the network. In the system, a primary notifying unit provided in each server device for sending the content of a fault of the server device to the network as a primary fault notification, and a notification listing a client device as a notification destination for each fault of each server device Secondary notification for executing a secondary failure notification via the network to a predetermined client device corresponding to the failure based on the failure list of the primary failure notification and the notification destination list, which is connected to the destination list and the network. Means, provided in each client device, based on the secondary failure notification. In which and a fault output unit for performing an output process.

[0013] The network system according to the present invention comprises:
The primary notification means sends a primary recovery notification to the network when the server device recovers, and the secondary notification means sends a secondary recovery notification to a predetermined client device via the network based on the primary recovery notification and the notification destination list. The failure output means executes the output processing based on the secondary recovery notification.

[0014] The network system according to the present invention comprises:
The notification destination list describes an address unique to the user of the client device, and the secondary notification means sends a secondary failure notification to the address based on the failure content of the primary failure notification and the notification destination list. To do.

[0015] The network system according to the present invention comprises:
In the notification destination list, a stop service message corresponding to the failure content of the server device is described for each failure of each server device, and the secondary notification means transmits the stop service in the secondary failure notification.

[0016] The network system according to the present invention comprises:
A priority order is described for each failure content of the server device in the notification destination list, and the secondary notification unit executes secondary failure notification to a plurality of client devices in an order based on the priority order.

The network system according to the present invention comprises:
A notification status field is provided in the notification destination list, and the secondary notification means writes an execution result of the secondary failure notification in the notification status field.

The network system according to the present invention comprises:
The secondary notification means is to notify the client device, which has not been notified, again.

The network system according to the present invention comprises:
The client device is provided with client monitoring means for outputting a start signal in response to the start, and the secondary notifying means performs notification again in response to the start signal.

The network system according to the present invention comprises:
The secondary notification means omits the secondary failure notification when receiving a recovery notification from the failed server device before receiving the activation signal.

[0021]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below. Embodiment 1 FIG. FIG. 1 is a system configuration diagram showing a configuration of a network system according to Embodiment 1 of the present invention. In the figure, reference numeral 1 denotes a network, 21..., 2 n are connected to the network 1 with unique server device names, and server devices storing databases and business programs necessary for business, and 31,. 1 via the network 1 according to the work of the user.
A business terminal device (client device) for acquiring predetermined information from 2n, and a management terminal device (notification destination list) 4 for centrally managing the operation of the entire network system including the operation / stop state of all server devices 21,. , Secondary notification means).

In each of the server devices 21,..., 2n, 5
Is a fault detecting means for detecting a fault which has occurred on each server device, and 6 is a fault information notifying means (primary notifying means) for sending information regarding the detected fault to the network 1 as a primary fault notification.

In the management terminal device 4, reference numeral 41 denotes a terminal device storing means for storing a notification destination list in which notification destinations when a failure occurs in the server device are listed, and 42 denotes an input for inputting a failure display command or the like. The means 43 performs a predetermined process in response to an input from the input means 42 or an input from the network 1. For example, a predetermined business terminal corresponding to the failure based on the failure content of the primary failure notification and the notification destination list. , 3n to the network 1, a terminal device main body for transmitting the secondary failure notification to the network 1, an output means 44 for displaying input contents, processing results, and the like;
3 is a failure notification program executed in Step 3.

In each of the business terminal devices 31,..., 3n,
Reference numeral 7 denotes a notification information display unit (failure output unit) that receives the secondary failure notification and displays the failure information of the notification.

FIG. 2 is an explanatory diagram showing a notification destination list according to the first embodiment of the present invention. As shown in the figure, in this notification destination list, each server device 21,.
n, the types of faults are classified for each of the n server device names, and the business terminal devices 31,.
Terminal device names are listed.

Next, the operation will be described. , 3n acquire predetermined information from predetermined server devices 21,..., 2n via the network 1 in accordance with the operation of the user. In such an operation state, when the server device 21,..., 2n goes down, the failure detecting means 5 detects this and the failure information notifying means 6 notifies the network 1 of information on the detected failure to the network 1 as a primary failure. Is sent out.

FIG. 3 is a flowchart showing the operation of the management terminal device 4 based on the failure notification program 45 according to Embodiment 1 of the present invention. In the figure, step ST1
Is a notification waiting step waiting for the input of a primary failure notification,
Step ST2 is a display step of displaying, on the output unit 44, notification contents such as failure information when the notification is input. Step ST3 determines whether the failure contents relating to the primary failure notification are included in the notification destination list. , 3n based on the primary failure notification and the notification destination list based on the failure content of the primary failure notification and the notification destination list. , 3n to the network 1. A step ST5 sends a secondary failure notification to the network 1 in response to the secondary failure notification for all the business terminal devices 31,..., 3n in the notification destination list. This is a notification process completion determination step for determining whether the next failure notification has been performed. By the above operation, the secondary failure notification can be executed once for each of the predetermined business terminal devices 31,..., 3n based on the primary failure notification.

Then, the notification information display means 7 of each of the business terminal devices 31,..., 3n receives the secondary failure notification, and displays the failure information of the server devices 21,. The user of the business terminal devices 31,..., 3n can grasp the suspension of the predetermined server devices 21,.

As described above, according to the first embodiment, the network 1, the server devices 21,..., 2n connected to the network 1, and the server devices 21,. , 3n in the network system having business terminal devices 31,..., 3n for acquiring predetermined information from the server, and the failure contents of the server devices 21,. The failure information notifying means 6 to be sent to the network 1 and each failure of the server devices 21,.
.., 3n, which are notification destinations, are connected to the network 1, and
.., 3n corresponding to the failure based on the failure content of the primary failure notification and the notification destination list.
, A terminal device main body 43 for executing a secondary fault notification via the network 1 for each of the business terminal devices 31,.
And a notification information display unit 7 for performing an output process based on the secondary failure notification.
By simply making minor changes to existing network systems that do not have the function of notifying failure information of 1, ..., 2n,
.., 3n, the server device 21,
, 2n can be instantly and reliably notified of the occurrence of a failure, which has the effect of preventing business confusion.

Since the terminal device main body 43 sends a notification to each of the business terminal devices 31,..., 3n based on the notification destination list instead of the notification directly from the server devices 21,. .., 3n can be prevented from being notified, and there is an effect that unnecessary confusion or stagnation does not occur in the business. Therefore, the business terminal device 3 which is a client device
, 3n and the server devices 21 and 2n are dispersedly arranged, and confusion or stagnation of business does not become serious.

As a result, the following effects are obtained.
First, since the fault information is automatically notified to the business terminal devices 31,..., 3n that need the information depending on the type of the fault, when the manager of the management terminal device 4 is out of the seat Even in this case, the person in charge of the operation is notified, and it is possible to prevent the disruption of the operation and the secondary failure. Secondly, since the failure information is notified only to the business terminal devices 31,..., 3n affected by the failure depending on the type of the failure, it is possible that a business person irrelevant to the failure can continue working. Become. Third, since the manager is not rushed to be notified of the person in charge, the manager can concentrate on the failure recovery processing, and quick recovery can be performed. Fourth, even if the business operator leaves the seat at the time of notification of the failure, the failure notification is sent to the business terminal devices 31,..., 3n, so that the worker can know the failure when returning to the seat. Yes, and there will be no missing notifications. Fifth, since the notification destination list is provided not in each of the server devices 21,..., 2n but in one management terminal device 4, it is possible to centrally manage management information and flexibly respond to system changes. can do.

Embodiment 2 FIG. In the second embodiment, the failure information notifying means 6 of each of the server devices 21,..., 2n sends a primary recovery notification to the management terminal device 4, and the terminal device main body 43 of the management terminal device 4 converts each of the business terminal devices 31. , ..., 3n
The network system is the same as that of the first embodiment except that the secondary recovery notification is sent to the business terminal devices 31,..., 3n in addition to the failure notification. The specific configuration and operation in the recovery notification are the same as the configuration and operation in the failure notification described in the first embodiment, and a description thereof will not be repeated.

As described above, according to the second embodiment, the failure information notification means 6 sends a primary recovery notification to the network 1 when the server device 21,..., 2n recovers, and the terminal device main body 43 transmits the primary recovery notification to the network 1. .., 3n via the network 1 based on the notification and the notification destination list, and the notification information display means 7 outputs based on the secondary recovery notification. Since the processing is performed, there is an effect that the business can be smoothly restarted at the same time as the recovery.

As a result, the following effects are obtained.
First, the business terminal devices 31,.
Since the notification is automatically made, the business can be quickly resumed. Secondly, even if the business person is away from the office at the time of the recovery notification, the recovery person is returned to the business terminal devices 31, ..., 3n because the recovery notification is sent to the business terminal devices 31, ..., 3n. At this time, it is possible to know that the business can be resumed.
Therefore, there is no missing in the notification.

Embodiment 3 FIG. FIG. 4 is an explanatory diagram showing a notification destination list according to the third embodiment of the present invention. As shown in the figure, in this notification destination list, the terminal device names of the business terminal devices 31,..., 3n that are the notification destinations are listed for each failure classification of the server devices 21,. A stop service message corresponding to the failure content of the server device 21,..., 2n is described. The stop service message is not a message such as a disk failure, but a message at the business level such as which business cannot be performed at present or which file cannot be accessed. Other configurations are the same as those of the second embodiment, and a description thereof will be omitted.

Next, the operation will be described. The management terminal device 4 sends the stop service message as a secondary failure notification in the notification step ST4. Then, the notification information display means 7 of each of the business terminal devices 31,..., 3n receives the secondary failure notification and displays the stop service message related to the notification. Other operations are the same as those in the second embodiment, and a description thereof will be omitted.

As described above, according to the third embodiment, the notification destination list includes, for each failure of each of the server devices 21,..., 2n, a stop corresponding to the content of the failure of the server device 21,. The service message is described, and the terminal device main body 4
3 transmits the above stop service in the secondary fault notification, so that it is possible not only to know the stop of the server device 21,..., 2n when a fault occurs, but also to know the business level stop service message due to it. In the business terminal devices 31,..., 3n used for a plurality of businesses, there is an effect that unnecessary confusion or stagnation does not occur in other businesses.

As a result, the following effects are obtained.
Since the person in charge of the work is notified of the message related to the actual work, it is possible to know which work and which work should not be actually performed, so that the work irrespective of the failure can be continued.

Embodiment 4 FIG. 5 is a system configuration diagram showing a configuration of a network system according to Embodiment 4 of the present invention. In the figure, 81,..., 8n are respectively connected to the network 1, and the business terminal devices 31,.
This is an OA terminal device in which mailboxes of n users are set.

FIG. 6 is an explanatory diagram showing a notification destination list according to the fourth embodiment of the present invention. As shown in the figure, in this notification destination list, each server device 21,.
For each of the n failure categories, the mail address of each user is listed together with the terminal device names of the business terminal devices 31,. The other configuration is the same as that of the second embodiment, and the same reference numerals are given and the description is omitted.

Next, the operation will be described. FIG. 7 is a flowchart showing the operation of the management terminal device 4 based on the failure notification program according to Embodiment 4 of the present invention. In the figure, step ST6 is a notification destination type determination step for determining whether or not the notification destination is a mail address, and step ST7 is to set the server device 2 to the notification destination mail address.
This is a mail transmission step of performing a failure occurrence notification (secondary failure notification) of 1, 2,..., 2n. Other operations are the same as those in the second embodiment, and a description thereof will be omitted.

The user of each business terminal device 31,..., 3n can grasp the stop / operation of the predetermined server device 21,.

As described above, according to the fourth embodiment, the mail addresses of the users of the business terminals 31,..., 3n are described in the notification destination list.
Executes the secondary failure notification to the above-mentioned mail address based on the failure content of the primary failure notification and the above-mentioned notification destination list, so that the users who do not use the business terminal devices 31,. , 8n specified by the address can be reliably notified of the occurrence of a failure, and there is an effect that such business confusion in the user can be prevented.

The following effects are obtained. Not only the business terminal devices 31,..., 3n but also the OA terminal devices 81,.
Even if n is used, fault information is notified and quick notification is possible.

In the fourth embodiment, a mail address is used as an example of a means for directly notifying a person in charge. However, by registering a telephone number or the like, portable information such as a pager or a portable telephone can be registered. It is also possible to contact the terminal device.

Embodiment 5 FIG. FIG. 8 is an explanatory diagram showing a notification destination list according to the fifth embodiment of the present invention. As shown in the figure, in this notification destination list, the business terminal device 31, the service terminal device 31,...
…, The business terminal device 31 with the terminal device name of 3n,
, 3n are described. Other configurations are the same as those of the second embodiment, and a description thereof will be omitted.

Next, the operation will be described. FIG. 9 is a flowchart showing the operation of the management terminal device 4 based on the failure notification program according to the fifth embodiment of the present invention. In the figure, step ST8 is a notification step of sending secondary failure notifications to the network 1 in order from the one with the highest priority (for example, the one with a smaller numerical value in which the priority is described) in the notification destination list according to the primary failure notification. is there. Other operations are the same as those in the second embodiment, and a description thereof will be omitted.

As described above, according to the fifth embodiment, the priority order is described in the notification destination list for each failure content of the server devices 21,..., 2n. A plurality of business terminal devices 31,
, 3n, the business stoppage can be notified in accordance with the urgency thereof, and there is an effect that the confusion period due to the stoppage of the server devices 21,..., 2n can be shortened.

The following effects are obtained. First, by assigning priorities to the business terminal devices 31,..., 3n to be transmitted, information can be notified in order from the device relating to the business most affected by the failure that has occurred, thereby minimizing business confusion. It becomes possible to suppress to. Second, by sending in the order of priority, the notification is sent to all the business terminal devices 31,..., Due to the network 1 being down, the management terminal 4 being down, etc.
3n, it is more likely that a notification will be made to the business terminal devices 31,..., 3n with a higher priority.

Embodiment 6 FIG. FIG. 10 is a list explanatory diagram showing a notification destination list according to Embodiment 6 of the present invention.
As shown in the figure, in this notification destination list, the business terminal device 31, the service terminal device 31,...
.., 3n are provided with a notification status field. Other configurations are the same as those of the first embodiment, and a description thereof will be omitted.

Next, the operation will be described. FIG. 11 is a flowchart showing the operation of the management terminal device 4 based on the failure notification program according to the sixth embodiment of the present invention. In the figure, step ST9 includes business terminal devices 31,.
n is a step of judging whether or not the secondary failure notification to the n has succeeded. Step ST10 is a notification completion flag “1” in the notification status field of the business terminal devices 31,. Is a success notification completion flag writing step of storing the notification completion flag "-1" in the notification status field of each of the business terminal devices 31,..., 3n for which the notification has failed. . Step ST
Reference numeral 12 denotes all the business terminal devices 31,.
Is a notification result display step of displaying on the output means 44 a notification status of the notification status field based on the notification flag of the notification status field. Step ST13 is a general notification success in which it is determined whether or not all the notification flags are “1”. This is a determination step, and step ST14 is a post-processing step of rewriting all the notified flags to “0” when all the notified flags are “1”. Other operations are the same as those in the first embodiment, and a description thereof will be omitted.

As described above, according to the sixth embodiment, the notification destination field is provided with the notification status field,
Since the terminal device main body 43 writes the execution result of the secondary failure notification in the notification status field, the business terminal devices 31,..., 3n that could not be notified due to a communication error or stop at the time of the failure are identified by the notification status field. There is an effect that it is possible to specify the countermeasure and to take a countermeasure in response to this.

The following effects are obtained. Since the administrator can know the business terminal devices 31,..., 3n that have not been notified yet, the business terminal devices 31,.
Notification omission can be prevented by, for example, individually notifying the 3n users.

Embodiment 7 FIG. FIG. 12 is a system configuration diagram showing a configuration of a network system according to Embodiment 7 of the present invention. In the figure, reference numeral 9 denotes a start notifying unit (client monitoring unit) which is provided in each of the business terminal devices 31,..., 3n and sends a start signal to the network 1 in response to the start.
, 3n is a second terminal device storage means for storing a business terminal device list in which the activation status field is set for each 3n, and 47 indicates a failure in response to a failure notification from the server device 21,. This is a failure notification program that performs notification.

FIG. 13 is an explanatory diagram showing a business terminal device list according to the seventh embodiment of the present invention. As shown in the figure, in the business terminal device list, an activation status field is set for each terminal device name of each of the business terminal devices 31,..., 3n.
The start flags corresponding to the start / stop states of 1,..., 3n are stored. In the figure, for example, a state “0” indicates that the power is off, and a state “1” indicates that it is operating. Other configurations are the same as those of the sixth embodiment, and a description thereof will be omitted.

Next, the operation will be described. FIG. 14 shows business terminal devices 31,..., 3n according to the seventh embodiment of the present invention.
6 is a flowchart showing the operation of the activation notifying means 9 of FIG.
In the figure, step ST15 is a business terminal device 31,
, 3n is a start / stop wait step for waiting for a start / stop event. Step ST16 is a start / stop notification step of sending a start signal, which is a start / end message, to the network 1 based on the start / stop event.

FIG. 15 is a flowchart showing the operation of the management terminal device 4 based on the failure notification program 47 according to Embodiment 7 of the present invention. In the figure, step ST
Reference numeral 17 denotes an input waiting step for waiting for a failure notification from the server device 21,..., 2n and an input of a start signal from the business terminal device 31,. This is an input determination step of determining whether or not the information is the one in step ST19.
Is a failure notification processing step executed when an input is a notification from the server device 21,..., 2n, and a step ST20 is a startup notification executed when the input is not a notification from the server device 21,. This is a processing step.

FIG. 16 is a flowchart showing a detailed operation of the failure notification processing according to the seventh embodiment of the present invention.
In the figure, step ST21 is a startup state determination step for determining whether or not the business terminal devices 31,..., 3n to be notified are running. Other steps are shown in FIG.
The description is omitted.

FIG. 17 is a flowchart showing a detailed operation of the activation notification processing according to the seventh embodiment of the present invention.
In the figure, step ST22 is a start signal confirming step for judging whether or not the input is a start signal, step ST23 is a start setting step for setting a start flag "1" in a start state field, and step S23 is executed.
T24 is a stop setting step of setting a start flag “0” in the start state field. Step ST25 is an unreported failure determination step for determining whether there is an unreported failure regarding the activated business terminal devices 31,..., 3n, and step ST26 is a startup for sending the unreported failure as a secondary failure notification. Time notification step, step S
T27 is a flag changing step of setting the notified flag corresponding to the notified fault to “1”, and step ST28 is to determine whether all the notified flags related to the notified fault are set to “1”. This step is a start-up general notification success determination step for determining, and step ST29 is a start-up post-processing step of rewriting all the notified flags to “0” when all the notified flags are “1”. Other operations are the same as those in the sixth embodiment, and a description thereof will be omitted.

As described above, according to the seventh embodiment, the business terminal devices 31,..., 3n are provided with the start notifying means 9 for outputting a start signal in accordance with the start thereof. Since the notification is performed again in response to the activation signal, the business terminal devices 31,..., 3n can be more reliably notified.

The following effects are obtained. Since the failure message is also notified at the time of startup to the business terminal devices 31,..., 3n that are powered off when a failure occurs, it is possible to reliably notify the business person in charge of the failure.

Embodiment 8 FIG. In the network system according to the eighth embodiment, similarly to the second embodiment, the failure information notifying means 6 of each of the server devices 21,..., 2n performs a primary recovery notification to the management terminal device 4, and Of the terminal device main body 43 of each of the business terminal devices 31,..., 3n so as to be able to notify each business terminal device 31,. Is a network system similar to that of the seventh embodiment.

Next, the operation will be described. FIG. 18 is a flowchart showing a detailed operation of the failure notification processing according to the eighth embodiment of the present invention. In the figure, step ST
Reference numeral 30 denotes a recovery notification determination step for determining whether or not an input from the server device 21,..., 2n is a primary recovery notification, and step ST31 is for determining whether or not a notification completion flag relating to the server device has been transmitted. Is a recovery time flag determination step of determining The other steps are the same as those in FIG. 16, and are denoted by the same reference numerals and description thereof is omitted. Other operations are the same as those of the seventh and second embodiments.
The description is omitted.

As described above, according to the eighth embodiment, before receiving the activation signal,
When a recovery notification is received from the failed server device 21,..., 2n, the secondary failure notification is omitted,
This has the effect of preventing business confusion due to unnecessary notifications.

The following effects are obtained. When the business terminal devices 31,..., 3n are started up, it is possible to avoid confusion of the person in charge by not sending the already restored message.

Embodiment 9 FIG. 19 is an explanatory diagram of a notification destination list according to Embodiment 9 of the present invention.
As shown in the drawing, in the notification destination list, for each failure classification of each of the server devices 21,..., 2n, the notification completion flag, the notification execution flag, the terminal device names of the business terminal devices 31,. The remaining number counter and the notification interval time are set. Other configurations are the same as those of the sixth embodiment, and a description thereof will be omitted.

Next, the operation will be described. FIG. 20 is a flowchart showing a detailed operation of the failure notification processing according to the ninth embodiment of the present invention. In the figure, step ST
Reference numeral 32 denotes a notification success determination step for determining whether or not the notification has succeeded. Step ST33 is a remaining number determination step for determining whether or not the set value of the notification execution remaining number counter is “1” or more. Step ST34 is a subtraction step of subtracting "1" from the value of the remaining notification execution counter, and step ST35 is an elapsed time waiting step of waiting for the notification interval time. The other steps are the same as those in FIG. 18, and are denoted by the same reference numerals and description thereof will be omitted. Other operations are the same as those in the sixth embodiment, and a description thereof will be omitted.

As described above, according to the ninth embodiment, the terminal device main body 43 is
, 3n are notified again, so that there is an effect that the business terminal devices 31,..., 3n can be notified more reliably.

The following effects are obtained. Eliminating missing notifications due to temporary communication failures, such as network load, enables reliable notification of failure information to the person in charge.

[0070]

As described above, according to the present invention, a network system having a network, a server connected to the network, and a client for acquiring predetermined information from the server via the network. , A primary notifying means provided in each server device for sending the content of a failure of the server device to the network as a primary failure notification, and a notification destination in which a client device as a notification destination is listed for each failure of each server device Secondary notification means connected to the network and executing a secondary failure notification via the network to a predetermined client device corresponding to the failure based on the failure content of the primary failure notification and the notification destination list And a fault that is provided in each client device and performs output processing based on the secondary fault notification. The means for providing information on the failure of the server device by simply making minor changes to the existing network system that does not have the function of notifying failure information of the server device. This has the effect of preventing business disruption.

Further, since the secondary notification means notifies each client device based on the notification destination list instead of notifying directly from the server device, the notification is made to unrelated client devices. This has the effect of not causing unnecessary confusion or stagnation in the work.

According to the present invention, the primary notification means sends a primary recovery notification to the network when the server device recovers, and the secondary notification means sends a predetermined client device to a predetermined client device based on the primary recovery notification and the notification destination list. Since the secondary recovery notification is executed via the network and the failure output means performs the output processing based on the secondary recovery notification, there is an effect that the business can be smoothly restarted simultaneously with the recovery.

According to the present invention, the address unique to the user of the client device is described in the notification destination list.
The secondary notification means performs a secondary failure notification for the address based on the failure content of the primary failure notification and the notification destination list, so that a user who is not using the client device at the time of the failure can be notified. Also, the occurrence of a failure can be reliably notified via the information processing device specified by the address, and there is an effect that such business confusion by the user can be prevented.

According to the present invention, in the notification destination list, for each failure of each server device, a stop service message corresponding to the content of the failure of the server device is described.
Since the above stop service is transmitted in the secondary fault notification, not only can the server device be stopped when a fault occurs, but also the stop service message caused by the stop service can be known. This has the effect of not causing unnecessary confusion or stagnation in other tasks.

According to the present invention, the priority order is described for each failure content of the server device in the notification destination list, and the secondary notification means sends the secondary failure notification to the plurality of client devices in the order based on the priority order. Is executed, the business stoppage can be notified according to the degree of urgency, and the confusion period due to the stoppage of the server device can be shortened.

According to the present invention, the notification destination field is provided with the notification status field, and the secondary notification means writes the execution result of the secondary failure notification to the notification status field. For example, the client device that could not be notified due to the notification status field can be specified by the notification status field, and a measure can be taken accordingly.

According to the present invention, since the secondary notifying means notifies the client device to which the notification has not been made again, there is an effect that the client device can be notified more reliably.

According to the present invention, the client device is provided with the client monitoring means for outputting an activation signal in response to the activation thereof, and the secondary notifying means performs the notification again in response to the activation signal. There is an effect that the device can be notified more reliably.

According to the present invention, if the secondary notification means receives a recovery notification from the failed server before receiving the activation signal, the secondary notification is omitted because the secondary failure notification is omitted. This has the effect of preventing confusion in business due to various notifications.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram showing a configuration of a network system according to a first embodiment of the present invention.

FIG. 2 is an explanatory diagram showing a notification destination list according to the first embodiment of the present invention.

FIG. 3 is a flowchart showing an operation of the management terminal device based on the failure notification program according to the first embodiment of the present invention.

FIG. 4 is a list explanatory diagram showing a notification destination list according to Embodiment 3 of the present invention.

FIG. 5 is a system configuration diagram showing a configuration of a network system according to a fourth embodiment of the present invention.

FIG. 6 is an explanatory diagram showing a notification destination list according to Embodiment 4 of the present invention.

FIG. 7 is a flowchart showing an operation of the management terminal device based on the failure notification program according to the fourth embodiment of the present invention.

FIG. 8 is an explanatory diagram showing a notification destination list according to Embodiment 5 of the present invention.

FIG. 9 is a flowchart showing an operation of the management terminal device based on the failure notification program according to the fifth embodiment of the present invention.

FIG. 10 is an explanatory diagram showing a notification destination list according to Embodiment 6 of the present invention.

FIG. 11 is a flowchart showing an operation of the management terminal device based on the failure notification program according to the sixth embodiment of the present invention.

FIG. 12 is a system configuration diagram showing a configuration of a network system according to a seventh embodiment of the present invention.

FIG. 13 is an explanatory diagram showing a business terminal device list according to a seventh embodiment of the present invention.

FIG. 14 is a flowchart showing the operation of the activation notification means of the business terminal device according to Embodiment 7 of the present invention.

FIG. 15 is a flowchart showing an operation of the management terminal device based on the failure notification program according to the seventh embodiment of the present invention.

FIG. 16 is a flowchart showing a detailed operation of a failure notification process according to the seventh embodiment of the present invention.

FIG. 17 is a flowchart illustrating a detailed operation of a start notification process according to the seventh embodiment of the present invention.

FIG. 18 is a flowchart showing a detailed operation of a failure notification process according to the eighth embodiment of the present invention.

FIG. 19 is a list explanatory diagram showing a notification destination list according to Embodiment 9 of the present invention.

FIG. 20 is a flowchart showing a detailed operation of a failure notification process according to Embodiment 9 of the present invention.

FIG. 21 is a system configuration diagram showing a configuration in which a server device operation state management function is added to a conventional network system with a minimum configuration change.

[Explanation of symbols]

1 network, 21, ..., 2n server device, 3
1,..., 3n business terminal device (client device), 4
Management terminal device (notification destination list, secondary notification means), 6
Failure information notification means (primary notification means), 7 notification information display means (failure output means), 9 activation notification means (client monitoring means).

Claims (9)

[Claims] 1. A network system comprising: a network; a server connected to the network; and a client for acquiring predetermined information from the server via the network. Primary notifying means for sending out the contents of a device failure to the network as a primary failure notification; a notification destination list in which client devices to be notified are listed for each failure of each server device; Secondary notification means for executing a secondary failure notification via a network to a predetermined client device corresponding to the failure based on the failure content of the notification and the notification destination list; provided in each client device; And a failure output means for performing output processing based on the next failure notification. Network system that. 2. The primary notification means sends a primary recovery notification to the network when the server device recovers, and the secondary notification means sends a network to a predetermined client device based on the primary recovery notification and the notification destination list. 2. The network system according to claim 1, wherein a secondary recovery notification is executed via the second communication unit, and the failure output unit performs an output process based on the secondary recovery notification. 3. The notification destination list describes an address unique to the user of the client device. The secondary notification means transmits the address based on the failure content of the primary failure notification and the notification destination list. The network system according to claim 1, wherein a secondary failure notification is performed. 4. The notification destination list includes a stop service message corresponding to the failure content of the server device for each failure of each server device, and the secondary notification means transmits the stop service in the secondary failure notification. The network system according to claim 1, wherein 5. The notification destination list describes a priority order for each failure content of the server device, and the secondary notification unit executes a secondary failure notification to a plurality of client devices in an order based on the priority order. 2. The network system according to claim 1, wherein: 6. The network system according to claim 1, wherein a notification status field is provided in the notification destination list, and the secondary notification unit writes an execution result of the secondary failure notification in the notification status field. . 7. The network system according to claim 6, wherein the secondary notification unit notifies the client device, which has not been notified, again. 8. The client device according to claim 1, further comprising: a client monitoring unit that outputs an activation signal in response to the activation, and wherein the secondary notification unit performs notification again in response to the activation signal. 6. The network system according to 6. 9. The secondary notifying means, when receiving a recovery notification from the failed server before receiving the activation signal, omits the secondary failure notification. 8. The network system according to 8.