JP2002278799A - Method, system and program for grasping client operating state - Google Patents

Abstract

PROBLEM TO BE SOLVED: To grasp a client operating state by utilizing a business log that is generated in a normal business application execution process. SOLUTION: This program P1 can be performed by a server 10 in a client/ server system 1 in which clients #1 (20) to #3 (40) capable of operating a plurality of business applications X (22) to W (25) and the server 10 are connected through a communication network N in a communicable way. The server 10 is made to function as a communication process 11 with a client for extracting business start log data representing a business start and business end log data representing a business end extracted among a plurality of pieces of business log data issued in accordance with at least one business application operation based on the processing of the respective clients #1 (20) to #3 (40), the business log registration processes 12 of the clients and a client operating state detection process 15 for grasping the operating states of the respective clients #1 (20) to #3 (40) on the basis of at least either the extracted business start log data or the extracted business end log data.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a client / server system in which a client and a server capable of operating at least one business application are communicably connected via a communication network, for ascertaining the operating state of the client. The present invention relates to a client operating state grasping method and system, and a client operating state grasping program.

[0002]

2. Description of the Related Art A client (client computer) and a server (server computer) which are communicably connected via a communication network.
In a server system, the following mechanism (a program and a function corresponding to the program) is generally used to grasp the operating state of the client on the server side.
Must be built into the server and client respectively.

That is, the client side must incorporate a mechanism for detecting the operating state of the client itself and a mechanism for communicating the operating state to the server in the active state. A communication mechanism for the client must be incorporated.

[0004] As a method of notifying the operation status of the client to the server on the client side, there is the following method.

That is, as a first method, a method of periodically notifying an operation state from a client side to a server side,
As a second method, when the operating state of the client changes, the operating state is notified from the client to the server. As a third method, when a request for transmitting the operating state is transmitted from the server to the client. There is a method of notifying the operating state from the client side to the server side.

The above-described first to third methods are selectively used depending on the purpose of managing the state of the client.

[0007]

However, in the conventional client operating state grasping method, an operating state detecting mechanism and an operating state communication mechanism with the server are provided on the client side.
Since the operating state communication mechanism with the client must be specially installed on the server side, the processing load based on the mechanism built into the client itself and the server itself, and the processing load on the communication path (communication line) based on the operating state communication. Respectively, resulting in a possibility that the speed of the original business application processing of the client and the communication speed via the communication path between the client and the server may be reduced.

Further, in any of the first to third methods for notifying the server of the operating state of the client to the server, the CPUs on the client side and the server side are used.
And the load on the communication path between the server and the client, the processing speed of the business application of the client and the processing speed via the communication path with the server may be reduced.

SUMMARY OF THE INVENTION The present invention has been made in view of the above circumstances, and occurs in a normal business application execution process without specially incorporating an operating state detection mechanism and an operating state communication mechanism with a server on a client side. It is an object of the present invention to provide a method and system for ascertaining a client operating state and a program for ascertaining a client operating state that enable the operating state of a client to be ascertained by utilizing a business log.

[0010]

According to a first aspect of the present invention, a client and a server capable of operating at least one business application can communicate via a communication network. At least one of the client and the server in the connected client / server system is an executable program, and executes at least one of the client and the server based on the processing of the client. Means for extracting business start log data representing a business start and business end log data representing a business end extracted from a plurality of business log data issued in response to the operation of a business application; At least one of the business end log data Based on, to function as a means to grasp the operating state of the client.

In a first aspect, the client is capable of running a plurality of business applications,
The extracting means includes means for extracting business start log data and business end log data corresponding to the business application from each business log data issued by executing each of the business applications, and the operating state grasping means includes: A means for setting the corresponding business application and the corresponding client to the operation state by the business start log data for the business application, and setting the corresponding business application to the operation end state by the business end log data for the business application set to the operation state Means for recognizing the client as a non-operation state when all the business applications corresponding to the client set to the business operation state are set to the operation end state by the operation end state setting means. Preparation There.

According to a second aspect of the present invention, to solve the above-described problem, the operating status of a client capable of operating at least one business application connected to a server via a communication network is determined. A task start log data indicating a start of a task and a task indicating a task end from a plurality of pieces of task log data issued in response to at least one task application operation based on the processing of the client. Extraction means for extracting the end log data, and operation state grasping means for grasping the operation state of the client based on at least one of the extracted business start log data and business end log data.

According to a third aspect of the present invention, to solve the above-described problem, it is possible to grasp an operating state of a client capable of operating at least one business application connected to a server via a communication network. Client operation state grasping method, comprising: business start log data representing a business start and business representing a business end from a plurality of business log data issued in response to at least one business application operation based on the processing of the client. The method includes the step of extracting end log data, and the step of grasping the operating state of the client based on at least one of the extracted business start log data and business end log data.

[0014]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The embodiments of the method and system for ascertaining the client operating state and the program for ascertaining the client operating state according to the present invention will be described below with reference to the accompanying drawings.

(First Embodiment) FIG. 1 is a block diagram showing a schematic configuration of a client / server system 1 including a client operation state grasping system according to a first embodiment of the present invention.

As shown in FIG. 1, the client / server system 1 includes, as a function, a client operating state grasping system according to the present embodiment, and includes a server 10 for providing services to clients described later. The server 10 is a computer including a CPU, a memory, and the like.

The server 10 has, in its memory, a program P1 including middleware, which is basic software (platform) of a distributed computer environment for constructing a client / server system. The program P1 is described below. A process (means) is realized.

That is, the server 10 executes the program P1
Thus, the communication process 11 for communication with the client via the communication network N and the business log data for one client (hereinafter simply referred to as the business log) 1
And a client operation status detection process 15 for detecting the client operation status based on the operation log 14 and updating the client operation status table 16 as necessary. It is working.

On the other hand, the client / server system 1
Are a plurality of clients (in FIG. 1, three clients # 1,
# 2, $ 3 (20, 30, 40)), and each of the clients # 1 (20) to # 3 (40)
It is a computer including a PU, a memory, a display, an input unit, and the like.

Each client # 1 (20) to $ 3 (4
0) are middleware as a base software (platform) of a distributed computer environment for constructing a client / server system and a plurality of business applications (programs; abbreviated as “business applications” in the drawings) X to X). A program P2 including W is held, and according to the program P2, the following processes (means) are realized.

For example, the client # 1 (2
0) corresponds to the communication network N according to the program P2.
A communication process 21 for communication with the server 10 via
Business application process X (22) based on business application X, business application process Y (23) based on business application Y, business application process Z (24) based on business application Z, and business application process based on business application W Each function as W (25).

Note that the other clients {2 (30) to {2}}
3 (40) also has a functional configuration substantially equivalent to that of the client # 1 (20).

Further, the client / server system 1
Is provided with an operation management terminal (computer having a CPU, a memory, a display, an operation unit, etc.) 100 capable of communicating with the server 10 via the communication network N and monitoring client operation management in the server 10; This operation management terminal 100 is operated by an operator's instruction,
Alternatively, the client operating state table 16 in the server 10 is referred to according to a predetermined cycle, and the operating state of the client can be displayed on the screen.

In this specification, "business log data (business log)" means message data generated in the course of executing a business application, and includes business start log data indicating the start of a business application, business business log data, and the like. Log data representing the content of each process based on the application, business end log data representing the end of the business application, business start log data representing the start of the business application, and the like. Each time it is issued on the (20)-# 3 (22) side, it is transmitted to the server 10 one by one.

FIG. 2 is a diagram conceptually showing the data structure of one business log 14 in the present embodiment.

As shown in FIG. 2, the business log 14 includes a client name 1 as identification information of a corresponding client.
4C, a corresponding business application name 14N, a message number 14B corresponding to the content of a message described later, and a message character string 14M representing the message content.

Hereinafter, regarding the overall processing of this embodiment, in particular, the client operating state detection process 1 of the server 10
5 will be mainly described.

At least one of the clients # 1 (20) to # 3 (40) has a plurality of business application processes X (22) to W (25).
In the process of executing at least one of the business application processes, the business log 14 issued by the processing of the corresponding client is transmitted by the communication process 21 of that client every time it is issued (that is, one by one). N to the server 10.

At this time, the communication process 11 of the server 10
Receives the business log 14 transmitted via the communication network N, and passes the business log 14 to the business log registration process 12 (for example, by writing / reading data via a memory, the next process 12 The business log registration process 12 writes the passed business log 14 into the business log file 13 as a record including the registration date and time.
The business log 14 is registered, and then one business log 14
To the client operating state detection process 15.

FIG. 3 is a diagram showing a configuration example of the business log file 13. As shown in FIG. 3, the business log 14 is sequentially stored in the business log file 13 as a first record, a second record,. Written (registered).

Client operation status detection process 15
Starts when the registration process 12 registers the business log 14 in the business log file 13.
2 receives the business log 14 passed from the server 2 and executes the following operation.

That is, the client operation state detection process 15 of the server 10 receives (reads from the memory) one business log 14 passed by the registration process 12, and obtains a client name 14C, a business application name 14N, and a message number 14B. And the message character string 14M (step S1).

Next, the process 15 examines the message number 14B of the business log 14 to determine whether it is a business start business log (business start log) (Step S).
2).

If it is determined in step S2 that the job log 14 indicates that the job has started, the process proceeds to the next step S3, otherwise, the process proceeds to step S10.

As a method of determining whether the contents of the business log in step S2 is business start or business end, there is a method of determining a character string of a message in addition to a message number. The method will be described.

If the determination in step S2 is YES (business log →
If the record is a business start log), the process 15 determines whether or not the record having the client name 14C of the business log 14 has already been written in the client operation state table 16.

FIG. 4 shows the client operation state table 1
6 is a diagram illustrating a configuration example of FIG.

As shown in FIG. 4, the client operation status table 16 contains an operation status client name 161.
C, data 161S indicating the state of the client (in operation / non-operation), the business application name 1 (161N1) to the business application name 4 (161N4) in which the client is working, and the first record, the second record, Are stored as...

That is, the process 15 includes the client name 161 C of the first record 161, the client name 162 C of the second record 162, and the third record 163 of the client operation state table 16.
C,... Are examined in order, and the client name 16iC (i =
(1, 2,...) And the client name 14C are determined (step S3).

If it is determined in step S3 that there is a record 16iC that satisfies the condition (step S3 →
If the determination is affirmative (YES in step S7), the process proceeds to step S4.

If the determination in step S3 is YES (proceed to step S7), the client corresponding to the business log 14 is running another business application (according to the business log 14 of the business application,
(If a record already exists in the table 16).

The process 15 that has proceeded to step S4 is a case where the business application is operated for the first time on the corresponding client.
Are searched in order to find an unused record (empty record; client name 16iC = 0 (clear value)) (step S4).

In this embodiment, it is assumed that the empty record is the second record 162, for example.

At this time, the process 15 executes an empty record (second record 1) in the client operation state table 16.
The value (data) instructed in the business log 14 is written to the client name and the business application name in operation in 62).

That is, the empty record is the second record 1
If it is 62, the process 15 returns to the second record 16
2, the value corresponding to the client name 14C is written as the client name 162C of the second record 162, and the name of the working application 1
The value corresponding to the business application name 14N is written as (162N1) (step S5).

Next, the process 15 checks the corresponding record (the second record 16
In 2), the status of the client is "operating", that is, a value (data) meaning "operating" is written in the client status 162S, and the process ends.

On the other hand, if the determination in step S3 is YES, that is, the client name 16iC and the client name 14C
If there is a record 16i that matches with the business log (if another business application is running on the client corresponding to the business log 14), the process 15 sets the business application name specified in the business log 14 to the client operation status table 16 Then, it is determined whether or not the record is written in the name of the business application under operation in the record 16i corresponding to.

That is, for example, assuming that the corresponding record 16i is the second record 162, the process 15
Checks the working application name 1 (162N1), the working application name 2 (162N2), the working application name 3 (162N3),... In the second record 162 in order. 14N is searched for, and as a result of the search, it is determined whether or not there is a record matching the business application 14N corresponding to the business log 14 (step S).
7).

If it is determined in step S7 that there is a matching record, there is a record of the corresponding business application despite the fact that the log is a business start log, and it is determined that there is no normal operation. Judge and end the process.

In this abnormal operation, for example, after starting the business application on the client side, a failure occurs on the client side, and the client side re-executes the business application in a state where the business end log is not notified to the server side. It is when started.

On the other hand, if there is no matching record in the judgment of step S7, the judgment of step S7 is NO.
Then, the process 15 writes the value specified in the business log 14 to the business application name in the corresponding record of the client operation status table 16.

That is, the corresponding record is the second record 1
If it is 62, the process 15 returns to the second record 1
62 business application name 1 (162N
1), working application name 2 (162N
2), working application name 3 (162N
3),... Are searched in order, and those that are not used (the name of the business application in operation = 0) are searched.

At this time, for example, when the working application name 1 (162N1) is not used, the process 15 corresponds to the working application name 1 (162N1) and the business application name 14N. The value to be written is written (step S8).

Next, the process 15 sets the client status in the corresponding record of the client operating status table 16 to “operating”, that is, the client status 162
A value (data) meaning "in operation" is written to S, and the process ends.

On the other hand, if the determination in step S2 is NO, that is, if the business log is not a business start log, the process 15
Checks the message number 14B of the business log 14 to determine whether or not it is a business end log (business end log) (step S10).

If it is determined in step S10 that the job log 14 does not indicate the end of the job (step S10 → N
O), that is, when the business log 14 is neither the business start log nor the business end log, it is determined that the business log is unnecessary for the client operation status detection process 15 and the process is terminated.

On the other hand, if the job log 14 indicates that the job has been completed (step S10 → YE)
S), the process 15 searches for a record that can be placed in the client operation state table 16 corresponding to the client name 14C of the business log 14.

That is, the process 15 includes the client name 161 C of the first record 161, the client name 162 C of the second record 162, and the client name 163 of the third record 163 of the client operation state table 16.
.. Are sequentially searched for a record 16i in which the client name 16iC and the client name 14C match (step S11).

For example, when the client name 16iC and the client name 14C match in the second record 162, the process 15 determines in the job log 14 among the names of the working application in the corresponding record of the client operation status table 16. Clear (delete) those that match the specified business application name.

For example, the corresponding record is the second record 16
If it is 2, the process 15 sequentially checks the working application name 1 (162N1), the working application name 2 (162N2), the working application name 3 (162N3), and so on. , And the one that matches the business application name 14N.

Then, for example, the business application name 1 (162N1) in operation is the business application name 1
When the value matches 4N, the process 15 deletes the value corresponding to the business application name 1 (162N1) in operation from the table 16 (that is, writes the value “0” corresponding to the clear) (step S12).

Next, the process 15 determines whether or not one or more working application names in the corresponding record of the client operation status table 16 have been written (step S13).

For example, the corresponding record is the second record 16
2, the process 15 checks the working application name 1 (162N1), the working application name 2 (162N2), the working application name 3 (162N3),. The number of business application names in which the business application name is written ($ 0) is calculated, and if the number is one or more, the determination in step S13 is YES, that is, another business application is running, Since the client corresponding to the operation end log is still operating, the process ends.

On the other hand, as a result of the judgment in step S13, N
O, that is, since there is no running business application in the client corresponding to the business end log 14, the process 15 sets the state of the corresponding client to "non-operation", that is, the client state 162S.
, A value (data) meaning “non-operation” is written, and the process ends.

FIG. 7 is a diagram showing a result of detection of the client operating state based on the processing in steps S1 to S14 described above.

That is, for example, the first business log 14
As (No. 1), when the business start log 14 of the business application X in the client # 1 (20) is registered in the client business log file 13, the record of the client # 1 (20) is still in the client operation status table 16. Has not been written, the determination in step S2 → YES, the determination in step S3 → NO, and the predetermined records in the client operation state table 16 are stored in the client operation status table 16 based on the business start log 14 by the processing in steps S4 to S6. , Client $ 1
(20) and a value indicating that the business application X is operating (working) (a value indicating the business name) are written.

Next, the second business log 14 (No.
As 2), when the business start log 14 of the business application Y in the client # 1 (20) is registered in the client business log file 13, this time, the client # 1 (20) is added to a predetermined record of the client operation status table 16. Since the value corresponding to the client name of ()) is written, the judgment in step S2 → YES, the judgment in step S3 → YES, and the value indicating that the business application Y is operating (the value indicating the business name) is Written to a predetermined record.

On the other hand, the client operation state table 16
In the state where the value indicating the operation state of the client # 1 (20) and the value indicating that the business application X and the business application Y are running are written in the predetermined record of the ninth business log 14
As (No. 9), when the work completion log 14 of the business application Y in the client # 1 (20) is registered in the client work log file 13, the determination in step S2 → NO, the determination in step S10 → YES, and By the processing of S11 to S13, the value indicating that the business application Y is operating in the predetermined record of the client operating state table 16 is cleared.

As described above, the business application X is stored in the predetermined record of the client operation status table 16.
In a state in which data indicating that the application # is operating is written, as the tenth business log 14 (No. 10), the business end log 14 of the business application X in the client # 1 (20) is the client business log file. 13, the judgment in step S2 → N
O, the determination in step S10 becomes YES → step S10
By the processing of 11 to step S13, the value indicating that the business application X is in operation in the predetermined record of the client operation state table 16 is cleared.

At this time, in the predetermined record corresponding to the client # 1 (20) existing in the predetermined record, all the values indicating that the business application is running are cleared (0), so the determination in step S13 is NO. , The status of the client # 1 (20) is inactive.

As described above in detail, according to the present embodiment, based on the business log 14 issued in the process of executing the business application of the client, the operating status of the client corresponding to the business log 14 (running or not) , Non-operating state) can be easily detected and grasped.

(Second Embodiment) FIG. 8 is a block diagram showing a schematic configuration of a client / server system 1a including a client operating state grasping system according to a second embodiment of the present invention.

In the client / server system 1a shown in FIG. 8, the contents of one business log 14a transmitted from the client, the business log file 1 of the server 10
3a, client operating status detection process 15a of server 10, client operating status table 1 of server 10
6a and client business application process X-1 (22a1), business application process X-2 (22a2), business application process Y
-1 (23a1), business application process Y-
2 (23a2) are different from the first embodiment. Since other configurations are substantially the same as those of the first embodiment, the same components are denoted by the same reference numerals and description thereof will be omitted or simplified.

That is, the business application process X (22) executes the individual business application process X-
1 (branch number 1) and X-2 (branch number 2).
The business application process Y (22) includes individual business application processes Y-1 (branch number 1) and Y-2 at the time of multitask processing of the corresponding client.
(Branch number 2).

FIG. 9 is a diagram conceptually showing the data structure of one job log 14a in this embodiment.

As shown in FIG. 9, the business log 14a includes a client name 14C, a business application name 14N, a message number 14B, and a message character string 14M, which are the same as those in the first embodiment. Data 14K.

FIG. 10 is a diagram showing a configuration example of the business log file 13a according to the present embodiment. As shown in FIG.
The business log 14a includes a first record, a second record,
.. Are written (registered) in the business log file 13a.

FIG. 11 is a diagram showing a configuration example of the client operation state table 16a of the present embodiment.

As shown in FIG. 11, the client operating status table 16a includes
1C, data 161S representing the state of the client (active / non-active), the business application name 1 (161N1) and its branch number of the client working, the business application name 4 (161N4) and the branch number of the working business application 4 Is the first record, the second record, etc.
・ It is stored as

On the other hand, the client operation status detection process 15a in the present embodiment is started at the timing when the registration process 12 registers the business log 14a in the business log file 13a, and receives the business log 14a passed from the registration process 12, The following operation is performed.

That is, the client operating state detection process 15a of the server 10 is executed in step S shown in FIG.
After executing the processing of 1 to S4 (however, the business log is 14a) (after it is determined that the business application has run for the first time on the corresponding client and an unused record (for example, the second record 162) has been searched). In the empty record (second record 162) of the client operation status table 16a, the value (data) instructed in the business log 14 is assigned to the client name, the name of the working business application, and the branch number of the working business application name. Write.

That is, the empty record is the second record 1
62, the process 15a determines that the second record 1
62, the value corresponding to the client name 14C is written as the client name 162C of the second record 162, and
The value corresponding to the business application name 14N is written as (162N1), and the branch number of the working business application name 1 (162N1) is set to 162K1.
Branch number 14 of business application name during multitasking
Write K (step S5a).

Next, the process of step S6 is performed, and the state of the corresponding client is set to "operating".

On the other hand, if the judgment in the step S3 is YES, that is, the client name 16iC and the client name 14C
If there is a record 16i that matches (if another business application is running on the client corresponding to the business log 14a), the process 15a executes the business application name specified in the business log 14a, It is determined whether or not the branch number of the name is written in the corresponding record 16i of the client operation state table 16a.

That is, for example, assuming that the record 16i is the second record 162, the process 15
a is a set of the working application name 1 (162N1) and the branch number 162K1 of the working application name in the second record 162, the business application name 2 (162N2) and the branch number 162K2 of the working application name. Set, business application name 3 (1
62N3). A set of branch numbers 162K3 of the name of the business application under operation,... Is sequentially examined to find a match with the set of the business application name 14N and the branch number 14K of the business application name during multitasking. As a result, the business application 1 corresponding to the business log 14a
It is determined whether there is a record that matches the set of the branch number 14K of the business application name at the time of 4N multitasking (step S7a).

If it is determined in step S7a that there is a matching record, similarly to step S7, it is determined that the operation is not performed normally, and the process ends.

On the other hand, if it is determined in step S7a that there is no matching record, the determination in step S7a is NO, and the process 15a uses the business log 14a as the business application name in the corresponding record in the client operation status table 16a. Write the indicated value.

That is, the corresponding record is the second record 1
If it is 62, the process 15a determines that the business application name 1 (162N
1), working application name 2 (162N
2), working application name 3 (162N
3),... Are searched in order, and those that are not used (the name of the business application in operation = 0) are searched.

At this time, for example, when the working application name 1 (162N1) is not used, the process 15 corresponds to the working application name 1 (162N1) and the business application name 14N. Then, the branch number 14K of the business application name at the time of multitasking is written in the branch number of the business application name 1 (162N1) in operation (step S8a).

Then, the process of step S9 is performed, and the status of the corresponding client in the corresponding record is set to "operating".

On the other hand, the judgment in step S2 is NO (the job log 14a is not the job start log), the judgment in step S10 is YES (the job log 14a is the job end (step S10 → YES)), and the judgment in step S11 is By processing, the client name 16iC and the client name 14C
16i (for example, the second record)
Is found, the process 15a determines a set of the working application name 1 (162N1) and the branch number 162K1 of the working application name, the business application name 2 (162N2) and the branch of the working application name. The set of the number 162K2, the set of the business application name 3 (162N3) and the branch number 162K3 of the working application name,... Find a match for the pair.

For example, a set of the working application name 1 (162N1) / working application name branch number 162K1 is the business application name 14N / working application name branch number 1
When matching the 4K set, the process 15a deletes the value corresponding to the working application name 1 (162N1) from the table 16a (that is, writes the value “0” corresponding to clear), and then The branch number 162K1 of the business application name 1 in operation is cleared (step S12a).

Next, the process 15a determines whether or not one or more sets of the working application name / working application name branch number in the corresponding record of the client operation status table 16a have been written (step 15a). Step S13a).

As a result of the determination in step S13a, the number of business application names of (# 0) in which a set of the name of the business application in progress and the branch number of the business application in progress is written, is calculated. If the number is one or more, the determination in step S13a is YES, and the client corresponding to the task end log 14a is still operating, and thus the process ends.

On the other hand, as a result of the determination in step S13a, N
O, that is, since there is no running business application in the client corresponding to the business end log 14a, the process 15a sets the state of the corresponding client to "non-operation" and ends the processing.

Here, FIG. 14 is a flowchart showing the processing in step S1 described above.
~ Step S5a ~ Step S7a, Step S8a ~
Step S12a, Step S13a, Step S14
FIG. 15 is a diagram showing a result of detection of a client operation state based on the processing of FIG. 15; FIG. 15 is a view showing a result of detection of a client operation state when the processing of steps S1 to S14 described in the first embodiment is applied at the time of multitasking; It is.

That is, as shown in FIG. 15, if the branch number at the time of multitasking is not considered, both the business applications X-1 and X-2 are recognized as the same business application X. 1 and No. According to the business log 14 of No. 3, when the business applications X-1 and X-2 in the client # 1 (20) are operating, the client # 1 (No. 6) is set as the sixth business log 14 (No. 6). When the task completion log 14 of the task application X in 20) is registered, the task application X is terminated, that is, it is determined that the task application is in the non-operation state, although the task application X-2 is operating. .

However, according to the client operating status detection process 15a of the present embodiment, the operating status of the business application is set for each set of the business application name and the branch number of the business application name in operation, that is, for each branch number of the business application. Is determined,
No. 1 and No. 3, the business application X in the client # 1 (20)
When -1 and X-2 are in operation,
As the sixth business log 14a (No. 6), the business application X-1 in the client # 1 (20)
Is registered, only the running business application X-1 is set to the end state, and the state of the running business application X-2 is maintained as it is.

Therefore, erroneous detection of the client operating state during multitasking can be reliably avoided.

(Third Embodiment) FIG. 16 is a block diagram showing a schematic configuration of a client / server system 1b including a client operating state grasping system according to a third embodiment.

In the client / server system 1b shown in FIG. 16, each client is a new business application U (26) in addition to the business applications X (22) to W (25) similar to the first embodiment. And business application V (27), and these business applications X (22) to
A plurality of business applications other than the business application W in the business application V (27) are shown in FIG.
As shown in FIG. 7, the business application X (22) is placed at the top of the startup hierarchy, and the business application Y (23) and the business application Z (2) are placed at the lower startup hierarchy.
4), a starting hierarchical structure is formed such that the business application U (26) and the business application V (27) are further lower than the business application Y.

That is, a business application in a lower startup hierarchy is an application that can be started in a state where the business application has been started. Therefore, when an application higher in level than its own application is terminated, a startup hierarchy lower than that application is used. Will also be terminated at the same time.

On the other hand, the server 10 in the client / server system 1b of the present embodiment stores a client business application start lower layer information (hereinafter, abbreviated as start lower layer information) table 17 in its memory.

FIG. 18 is a diagram showing an example of the configuration of the activation lower hierarchy information table 17 stored in the server 10.

As shown in FIG. 18, the activation lower layer information table 17 stores, for each business application X (22) to business application V (27) of each client,
Information indicating the business application name and the business application name in the upper hierarchy is sequentially stored as records (first record 171, second record 172,..., Sixth record 176).

Further, the client operating state detection process 15b of the server 10 executes a process partially different from that of the first embodiment.

The other components are substantially the same as those of the first embodiment. Therefore, the same components are denoted by the same reference characters and description thereof will be omitted or simplified.

Hereinafter, the processing of the client operating state detection process 15b of this embodiment will be described.

The processing in steps S1 to S14 of the client operating state detection process 15b is the same as the processing in steps S1 to S14 in FIG. 5 and will not be described.

That is, in the client operating state detection process 15b of the present embodiment, the determination in step S3 is YE
S, that is, when there is a record 16i in which the client name 16iC matches the client name 14C (when another business application is running on the client corresponding to the business log 14), the process 15b
The business application name designated in the business log 14 and the business application name of the activation lower layer thereof correspond to the corresponding record 16 in the client operation status table 16.
It is determined whether or not it is written in the work application name of i.

That is, for example, assuming that the record 16i is the second record 162, the process 15
b sequentially checks the working application name 1 (162N1), the working application name 2 (162N2), the working application name 3 (162N3),... in the second record 162. Search for a name that matches the name 14N.
It is determined whether or not a record matching the business application 14N corresponding to the business log 14 exists (step S7b).

If it is determined in step S7b that there is a matching record, the process 15b executes the job specified in the job log 14 among the names of the working application in the corresponding record in the client operation status table 16. A process of clearing the application name and the business application name in the lower hierarchy of the application is performed (step S20).

Hereinafter, the processing in step S20 of the process 15b will be described in detail.

For example, it is assumed that the corresponding record is the second record and the business application name is “business application”.

[1] Name of business application in operation i
Is set to i = 1.

[2] Name of working application i
Check whether (162Ni) is "valid".

[3] If "valid", go to [4],
If "invalid", proceed to [6].

[4] Name of working business application i
It is checked whether (162i) matches the business application name 14N.

As a result, if they match, the business application name i (162Ni) being worked on is cleared, and [5]
Proceed to.

[5] The business application name of the startup lower hierarchy of the business application name 14N is obtained from the startup lower hierarchy information 17.

<1> The target record is the first record 171
And

<2> Check whether the business application name of the target record is written.

For example, the target record is the first record 17
Let it be 1. At this time, business application name 1
If 71N has been written, the process proceeds to <3>, otherwise, the process proceeds to <6>.

<3> It is checked whether the application name of the upper layer of the target record is written. For example, it is assumed that the target record is the first record 171. At this time, the process proceeds to <4> when the business application name 171P of the upper hierarchy is written, and proceeds to <6> when it is not written.

<4> It is checked whether or not the business application name in the upper hierarchy matches the business application name 14N. For example, the target record is the first record 171. At this time, the business application name 17 in the upper hierarchy
If 1P matches the business application name 14N,
The business application name 171N is stored as the activation lower hierarchy of the business application name 14N. On the other hand, if they do not match, proceed to <5>.

<5> For example, assuming that the target record is the first record, the upper-level business application name 1
The j-th record with 71P = business application name 17jN is searched for by the following processes a to c. a. If the business application name 17jP of the upper hierarchy exists and matches the business application name 14N, the business application name 171P is recorded as the activation lower hierarchy of the business application 14N, and the process proceeds to <6>. b. In the case where the business application name 17jP of the upper hierarchy exists and does not match the business application name 14N, the business application name 17jP of the upper hierarchy further becomes the k-th business application name 17kN.
Find the record and return to a. c. When the business application name 17jP of the upper hierarchy is not written, the process proceeds to <6>.

<6> It is determined whether or not all records of the client business application activation lower layer information have been processed. As a result of this determination, if all records have been processed, the process proceeds to <7>, otherwise, the process proceeds to <2> with the target record as the next record.

<7> Go to [6]. Note that the above <2>
Describes that processing can be performed even when the hierarchy is the upper and lower four levels (parent, child, grandchild, and great-grandchild). For example, when the business application name 14N = application X, the starting lower layers are application Y, application Z, application U, and application V. In the case where the business application name 14N = application Z, there is no lower hierarchy for activation.

[6] Client Operation Status Table 16
If the name of the working application in the corresponding record matches the name of the business application in the startup lower hierarchy of the business application name 14N stored in [5], the name of the working application is cleared.

For example, client operation state table 1
If the corresponding record of No. 6 is the second record, the working application name 1 (162N1), the working application name 2 (162N2), the working application name 3 (162N3),. Is checked to see if it matches the business application name of the business application name 14N stored in the lower hierarchy of the business application name stored therein, and only the business application name under the matching work is cleared.

Next, the process 15b writes the value indicated in the business log to the name of the business application in operation in the corresponding record of the client operation status table 16.

For example, the corresponding record is the second record 16
If it is 2, the process 15b executes the working application name 1 (162N1), the working application name 2 (162N2), the working application name 3 (162N3),.
Are searched in order, and those that are not used (the name of the business application in operation = 0) are searched. For example, it is assumed that the name of the business application under operation 1 (162N1).

Next, the process 15b writes the value corresponding to the business application name 14N to the business application name 1 (162N1) in operation (Step S).
21).

Next, the process 15b changes the client status in the corresponding record of the client operating status table 16 to “operating”, that is, the client status 16
A value (data) meaning "in operation" is written to 2S, and the process ends.

Here, FIG. 20 is a flowchart showing the processing in step S1 described above.
~ Step S7b ~ Step S14, Step S20 ~
FIG. 21 is a diagram illustrating a detection result of the client operation state based on step S22. FIG. 21 illustrates the client operation state when the business application of the client ends abnormally in the processing of steps S1 to S14 described in the first embodiment. It is a figure showing a detection result.

That is, as shown in FIG. 1
-No. 4 based on the operation log 14, the client # 1
When the business applications X, Y, W, and Z of (20) are operating, respectively, the business application Y
When the business application X, which is the upper layer of the application programs Z and Z, terminates abnormally, the business application
And Z also terminate abnormally. At this time, the business end log 14
Is not registered in the business log file 13, the business applications X, Y, and Z in the client operation state table 16 are in the operating state despite the abnormal termination, and the client # 1 (20) The operating status becomes inaccurate.

Thereafter, when the business application X is restarted in the client # 1 (20) (No. 4)
Since the business start log 14 is registered), the value indicating that the business application X is already running is already written in the client running state table 16, so both steps S 3 and S 7 in FIG. 5 are YES.
Since the client operation state detection process 15 ends the processing, the business applications Y and Z are recognized in the server 10 in an incorrect state, and the client # 1 (20) actually performs the work. As a result, the ended business applications Y and Z are left as working.

However, according to the present embodiment, FIG.
As shown in FIG. 1 to No. According to the business log 14 of No. 4, when the business applications X, Y, W and Z of the client # 1 (20) are each in the operating state,
The business application X, which is the upper layer of the business applications Y and Z, ends abnormally and the client # 1
When the business application X is restarted in the client # 1 (20) when the operation state of (20) becomes inaccurate (the business start log 14 of No. 4 is registered),
The determination in step S3 is YES, and in the process of step S7b, the business application X and the business applications Y and Z of the activation lower hierarchy are detected. Is set to
The value indicating the activation state of the business applications Y and Z, which are the lower layers, is cleared.

Therefore, even when the business application X in the upper tier ends abnormally (no business end log),
The state of the business applications Y and Z, which are the lower layers, can be accurately grasped.

(Fourth Embodiment) FIG. 22 is a block diagram showing a schematic configuration of a client / server system 1c including a client operating state grasping system according to a fourth embodiment.

The business application X (2
2) to the business application W (25) have the startup control hierarchical structure shown in FIG. 18 as in the third embodiment.

In the present embodiment, a part of the processing of the client operating state detection process 15c of the server 10 in the client / server system 1c shown in FIG. 22 is different from that of the first embodiment.

The other components are substantially the same as those of the first embodiment. Therefore, the same components are denoted by the same reference characters and description thereof will be omitted or simplified.

The processing in steps S1 to S14 of the client operating state detection process 15c is the same as the processing in steps S1 to S14 in FIG. 5 described above, and a description thereof will be omitted.

That is, the client operation status detection process 15c according to the present embodiment determines that the job log 14 has not been completed (step S10).
10 → NO), that is, if the business log 14 is neither the business start log nor the business end log, the business log 14
The message number 14B is checked to determine whether it is a business start-up log (business start-up log) (step S3).
0).

As a result of the determination in step S30, when the business log 14 is not a business startup (step S30 → N
O), that is, if the business log 14 is not any of the business start log, the business end log, and the business start-up log, it is determined that the business log is unnecessary for the client operation status detection process 15 and the process is terminated.

On the other hand, according to the judgment in step S30, when the business log 14 is set up for business (step S30 → YE)
S), the process 15c is a client operation status table 16 corresponding to the client name 14C of the business log 14.
Find records that can be placed in

That is, the process 15c is configured to execute the client name 161C of the first record 161 of the client operation status table 16, the client name 162C of the second record 162, and the client name 161C of the third record 163.
3C,... Are sequentially searched for a record 16i in which the client name 16iC matches the client name 14C (step S31).

For example, when the client name 16iC matches the client name 14C in the second record 162, the process 15c executes the work application name 1 (162N1), The business application name 2 (162N2), the business application name 3 (162N3),... That are being worked on are all deleted from the table 16 (that is, the value “0” corresponding to the clear is written) (step 32).

Next, the process 15c sets the client status in the corresponding record of the client operating status table 16 to "non-operation", that is, the client status 1
A value (data) meaning "non-operation" is written to 62S, and the process ends (step S33).

According to the present embodiment, as shown in FIG. 1 to No. 4, the business application X, Y, W of the client # 1 (20)
When the business application X, which is the upper layer of the business applications Y and Z, terminates abnormally while the operation status of the client # 1 (20) becomes inaccurate while the operation status of the client 1 (2
0) (No. 6 business startup log 14 is registered), the determination in step S10 is NO, the determination in step S30 is YES, and steps S31 to S32 are performed.
, All the business applications X to W are cleared. Therefore, the abnormally terminated client # 1 is transmitted via the client operation status table 16.
The operation state of (20) can be accurately grasped.

(Fifth Embodiment) FIG. 25 is a block diagram showing a schematic configuration of a client / server system 1d including a client operating state grasping system according to a fifth embodiment.

FIG. 26 is a diagram conceptually showing the data structure of one job log 14b in this embodiment.

As shown in FIG. 26, the business log 14b is
In addition to the same client name 14C, business application name 14N, message number 14B, and message character string 14M as in the first embodiment, data 14T representing the registration date and time registered in the client business log file 13
Contains.

FIG. 27 is a diagram showing a configuration example of the client operation state table 16d of the present embodiment.

As shown in FIG. 27, the client operating status table 16d contains the operating client name 16
1C, data 161T representing the update date and time of the client,
Data 1 indicating the status of the client (running / not running)
61S, the work application name 1 (161N1) of the client working, the work start date / time 161NT1 of the working application name 1 of the working application 1 to the working application name 4 (161N4) of the working application, and the working application name 4 (161NT4) of the working application ) ・ ・ ・
Are sequentially stored as a first record, a second record,....

On the other hand, the client operating state detection process 15d in the present embodiment performs a process partially different from the process 15 in the first embodiment.

The other components are substantially the same as those of the first embodiment. Therefore, the same components are denoted by the same reference characters and description thereof will be omitted or simplified.

That is, the client operation state detection process 15d of the server 10 is executed in the step S shown in FIG.
After the processing of 1 to step S5 (the business log is 14b), the value of the target record of the work data file is written in the date and time information in the corresponding record of the client operation status table 16.

For example, if the corresponding record is the second record 16
2 and the name of the business application 1 (162
Assuming that a value is set in N1), the process 15d executes the work start date and time 162
A value corresponding to the registration date and time 14T is written into N1T, and then a value corresponding to the registration date and time 14T is written into the state update date and time 162T (step S40).

Next, by the process of step S6, a value (data) meaning "in operation" is written in the client status 162S.

Also, by the processing of steps S7 to S8, the name of the working application 1 (162N
After the value corresponding to the business application name 14N is written in 1), the process 15d executes the work start date and time 162N1T of the working business application name 1
, A value corresponding to the registration date and time 14T is written into the state update date and time 162T, and then a value corresponding to the registration date and time 14T is written to the state update date and time 162T (step S41).

On the other hand, if the job log is the job end log 14 (step S10 → YES), steps S11 to S11 are executed.
After finishing the business application clearing process in step S12, the process 15d writes the value of the target record of the work data file to the date and time information in the corresponding record of the client operation status table 16.

For example, the corresponding record is the second record 16
2 and the name of the business application 1 (162
Assuming that a value is set in N1), the process 15d executes the work start date and time 162
A value corresponding to the registration date and time 14T is written into N1T, and then a value corresponding to the registration date and time 14T is written into the state update date and time 162T (step S41).

Next, steps S13 to S14
As a result, the state of the corresponding client is set to "non-operation" only when there is no running business application.

On the other hand, FIG. 30 shows a client operation status display function 101 of the operation management terminal 100 in this embodiment.
6 is a flowchart showing an operation based on the.

That is, the operation management terminal 100 reads the client operation state table 16d from the server 10, and then sets the first record 161 of the client operation state table 16d as a target record, and records the target record.
Then, the system detects the idle state of the working business application corresponding to the client name of the application (step S52).

For example, assuming that the target record is the first record, the operation management terminal 100 performs the following processing as the processing of step S52. [1] It is determined whether or not the client name 161C has been written. If it has been written, go to [2], otherwise go to (4). [2] Target business application name 1 in operation. [3] It is determined whether the target business application name has been written. For example, business application name 1
161N1. Business application name 1 161
If N is written, go to [4], otherwise go to [6]. [4] The difference between the work start date and time and the current date and time of the name of the business application under work is calculated. For example, in the case of the business application name 1, the difference between the work start date and time 161N1T of the business application name 1 and the current date and time is calculated. [5] When the difference exceeds a certain value, warning data indicating the status of abandoned work is added to the target business application name. If the difference does not exceed the fixed value, the process proceeds to [6]. [6] It is determined whether or not processing has been performed for all the business application names that are being worked on.

As a result of this determination, if the processing has been performed, the process proceeds to step S53. If there is an unprocessed business application, the process returns to [3] for the next business application name, and the above processing is repeated.

On the other hand, if the processing is completed for all the working application names, the process 15d
Determines whether all records in the client operation state table 16d have been processed (step S5).
3).

As a result of the determination in step S53, when all records have been processed (step S53 → YE
S), the process proceeds to step S55, and if there is an unprocessed record, the process proceeds to step S54.

Subsequently, the process 15d sets the target record to the next record (for example, if the target is the first record, sets the next record to the second rate 162) and proceeds to step S5.
The processing shifts to the processing of step 2, and the processing after step S52 is executed again for the next record (step S54).

In this way, the work start date and time 161N1 for all applications in all records
When the process of determining whether or not the difference between T and the current date and time has exceeded a certain value and the process of giving warning data to the corresponding business application when the difference has exceeded the certain value have been completed,
The determination in step S53 is YES, and the operation management terminal 1
00 displays the client operating status table 16d, that is, the client operating status table 16d in a state where warning data is added to the business application determined to be in the idle state, as client operating status display data on the screen (step S55), the process ends.

That is, according to the present embodiment, when the difference between the work start date and time and the current date and time of each business application of the client exceeds a certain value, in other words, when the state of leaving the work exceeds a certain time, Since the warning data can be given to the business application and the data indicating the client operating state in the state where the warning data has been given can be displayed on the screen, the operation management terminal 100 sends the corresponding client to the corresponding client based on the display data. On the other hand, since the data for warning that the work has been left can be notified, it is possible to avoid the business application leaving state on the client side.

The processing based on the client operation status display function 101 of the operation management terminal 100 is performed by the server 1
It is also possible to execute on the 0 side.

(Sixth Embodiment) FIG. 31 is a block diagram showing a schematic configuration of a client / server system 1e including a client operating state grasping system according to a sixth embodiment of the present invention.

In this embodiment, the business log registration process 12a of the server 10 writes the business log 14 passed from the communication process 11 into the business log file 13 as a record including the registration date and time.
Is registered, and the client operation state detection process 15e is executed periodically or in the operation management terminal 1.
In response to an instruction from the operator via the service log file 00, only the data necessary for detecting the client operating state is extracted from the business log 14 written in the business log file 13 and written into the work data file 18, and the work data The client operating state detection processing is performed based on the data written in the file 18 to update the client operating state table 16.

Note that the other configuration is substantially the same as the configuration of the first embodiment. Therefore, the same components are denoted by the same reference characters and description thereof will be omitted or simplified.

In the following description, the client operating state detection process 15e is described as a method of sequentially updating the records of the client operating state table 16, but the present invention is not limited to this method. The following method is also easily feasible.

That is, [1] a method of updating the entire table at once after creating it in another storage area of the memory,
[2] A method of detecting a change for each client and updating only the record of the changed client can be realized.

The overall processing of the present embodiment will be described below, in particular, in the client operating state detection process 1 of the server 10.
5e will be mainly described.

At least one of the clients # 1 (20) to # 3 (40) has a plurality of business application processes X (22) to W (25).
In the process of executing at least one of the business application processes, the business log 14 issued by the processing of the corresponding client is transmitted by the communication process 21 of that client every time it is issued (that is, one by one). N to the server 10.

At this time, the communication process 11 of the server 10
Receives the business log 14 transmitted via the communication network N, passes the business log 14 to the business log registration process 12a, and the business log registration process 12a
The business log 14 is registered by writing the passed business log 14 into the business log file 13 as a record including the registration date and time.

As a result, the business log 14 sequentially transmitted to the server 10 is registered in the business log file 13.

At this time, the client operation status detection process 15e of this embodiment reads the client operation log file 13 periodically, for example, and executes the processing shown in FIG.

In the following description, it is assumed that the records of the business log 14 of the business log file 13 are sorted (rearranged) in the order of the registration date and time.

If the records in the business log file 13 are not sorted in chronological order, a sort process may be added.

That is, the client operation status detection process 15 e extracts only the job log 14 indicating the start and end of the job from the job log file 13 and writes it in the work data file 18 as the process of step S 61.

Next, the client operating state detection process 15e performs the processing of step S62 by adding the client name and the record to the record of the work data file 18.
For each set of business application names, only the log record of the business start with the latest date and time is left, and the other records are invalidated.

Subsequently, the client operating state detection process 15e creates data of the client operating state table 16 based on the work data file 18 as the processing of step S63.

FIG. 33 is a flow chart for describing in detail the processing of step S61 (processing for extracting a business start log and a business end log) of the client operating state detection process 15e of this embodiment.

The process 15e includes (1) step S61
01, the business log file 13 is read,
Next, (2) as the process of S6102, the first record of the business log file 13, that is, the first business log record 131 is targeted.

Subsequently, the process 15e determines (3) whether or not the job log indicates the start or end of the job as the process of step S6103.

For example, it is assumed that the target record of the business log file 13 is the business log second record 132.

At this time, as a process of step S6103, the process 15e checks [1] the message number 132B of the target record, checks whether the content of the business log is the start or end of the business, and [2] determines whether the target record is the business start. Alternatively, if the job log is a job log indicating that the job has been completed, the process proceeds to step S6104 in (4), otherwise (5).
The process proceeds to step S6105.

The process 15e writes the target record in the work data file 18 (writes the data in order from the first record) as the process of step S6104.

FIG. 34 is a diagram showing a configuration example of the work data file 18. As shown in FIG.

For example, it is assumed that the target record of the business log file 13 is the business log second record 132, and the empty record of the work data file 18 is the first record 181.

At this time, the process 15e writes [1] the value of the client name 132C as the client name 181C, and [2] writes the value of the business application name 132N as the business application name 181N.
[3] Message number 1 as message number 181B
Write the value of 32B.

Then, the process 15e sets the target record of the business log file 13 as the next record (for example, if the target record of the business log file 13 is the second record of the business log, at step S6105). Then, the third record of the business log is set as the next processing target.

Subsequently, the process 15e includes (6) S61
In the process 06, it is determined whether or not all records in the business log file have been processed.

As a result of this judgment, if all records in the business log file 13 have been processed (step S
6106 → YES), the process ends, and if there is an unprocessed record (step S6106 → NO),
Returning to the processing of step S6103 of (3), the above processing is repeated.

As a result, only the work log 14 indicating the start and end of the work is extracted and written in the work data file 18.

FIG. 35 is a flow chart for explaining in detail the processing of step S62 (the processing of extracting the log record of the business start at the latest date and time) of the client operating state detection process 15e of this embodiment.

In the following description, a method is described in which an unnecessary record is set in a data invalid state without physically removing the record, but the physical removal can be easily realized.

That is, the process 15e includes (1) the work data file 1 as the process of step S6201.
The last record of No. 8, that is, the L-th record 18L is the target record.

Next, the process 15e determines (2) whether the target record is a business start or a business end as the process of step S6202.

For example, assuming that the target record is the L-th record, the process 15e checks [1] whether the message number 18LB is the start or end of the operation, and [2] if the message number 18LB is the start or end of the operation (3) Step S620
Go to 3; otherwise (invalid) go to (7).

The process 15e includes (3) step S62
In the process of 03, it is determined whether or not the target record is a business start.

For example, assuming that the target record is the L-th record, the process 15e determines that [1] if the message number 18LB is a business start (4) step S6204
If not (end of business), go to (5) Step S6205.

The process 15e includes (4) step S62
In the process 04, of all records younger than the target record, those whose client name and business application name match the value of the target record are all invalidated.

For example, if the target record is the L-th record 18
L, the records younger than the position of the target record are the L-1 record, the L-2 record,.
The third record, the second record, and the first record are obtained.

That is, the process 15e is [1] the first
From the record 181 to the L-1st record 18L- ₁ , the client name 18iC = the client name 18L
C and the business application name 18iN = all records i (1
8i) clear (invalidate) the record, [2]
(7) Proceed to step S6207.

[0214] Next, the process 15e performs (5) the processing of step S6205, out of all the records younger than the target record, invalidates all the records whose client name and business application name match the value of the target record. To

For example, if the target record is the L-th record 18
If it is L, records younger than the position of the target record are the L-1 record, the L-2 record,..., The third record, the second record, and the first record.

That is, the process 15e is [1] the first
From the record 181 to the L-1st record 18L- ₁ , the client name 18iC = the client name 18L
C, and all records i for which the business application name 18iN = the business application name 18LN
The record (18i) is cleared (invalid).

Subsequently, the process 15e invalidates the target record as the process of (6) Step S6206.

For example, if the target record is the L-th record 18
If it is L, [1] the record of the L-th record 18L is cleared (invalid).

Next, the process 15e includes (7) the work data file 18 as the process of step S6207.
Is the next record.

That is, for example, if the current target record is the L-th record 18L, the next record is 1
The preceding L-1th record 18L- ₁ is obtained.

The process 15e includes (8) the work data file 18 as the process of step S6208.
Judge whether or not all records have been processed,
[1] When the first record has been processed as the target record, the process is terminated. If there is an unprocessed record in the work data file 18, (2) the process proceeds to step S6202 and the above-described process is repeated.

As a result, only the work start log 14 of the latest date and time is left in the work data file 18.

FIG. 36 illustrates in detail the process of step S63 (the process of creating data of the client operating status table 16 based on the work data file 18) in the client operating status detecting process 15e of the present embodiment. It is a flowchart of FIG.

That is, the process 15e includes step S
In the process of 6301, the client operation state table 16 is initialized (cleared).

That is, the first record 161, the second record 162, the third record
Clear all data items in the records 163,...

Next, the process 15e includes (2) the work data file 18 as the process of step S6302.
Of the first record, that is, the first record 181. (3) In the process of step S6303, it is determined whether or not the target record is a business start. For example, if the target record is the first record 181, If a value indicating the start of the job is set in the message number 181B, the process proceeds to (4) Step S6304; otherwise, the process proceeds to (8) Step S6308.

The record is obtained by the processing in step S62 (steps S6201 to S6208).
It should be only the record of the business start log,
It is invalid unless it is a business start log.

Subsequently, the process 15e determines whether (4) the client name of the target record has already been written in the client operation table 16 in the same manner as in step S3 of the first embodiment. Judge.

That is, the process 15e is executed in [1] the client name 161 of the client operation status table 16.
C, client name 162C, client name 163
.. Are sequentially examined to determine whether or not there is a record 16i in which the client name 16iC = the client name 14C.

Next, if the record 16i that satisfies the condition [2] exists (that is, if the relevant client is already in operation due to the operation of another business application), the process 15e proceeds to (7) step S6307 and does not exist. In this case (when the corresponding client is not operating), the process proceeds to the next (5) step S6305.

The process 15e corresponds to steps S4 to S5 of the first embodiment (5) Step S63
05, the client operation state table 16
Write the value of the target record in the work data file to the client name in the empty record and the name of the working business application.

For example, it is assumed that the target record of the work data file is the second record 182, and the empty record of the client operation status table is the first record 161.

At this time, the process 15e executes [1]
The value of the client name 182C is written as the client name 162C of the record, and [2] the value of the business application name 182N is written as the value of the working business application name 1 (162N1) of the first record.

Next, the process 15e sets the status of the client in the corresponding record of the client operating status table 16 to "operating" as (6) step S6306 corresponding to step S6 of the first embodiment.

For example, if the first record 161 of the client operation status table is the corresponding record, the process 15e sets the client status 161S as
Write a value indicating "in operation" and end the process.

On the other hand, the process 15e corresponds to the steps S7 to S8 of the first embodiment. Write the value of the target record in the data file.

For example, it is assumed that the target record of the work data file is the second record 182 and the corresponding record of the client operation status table is the first record 161.

At this time, the process 15e performs [1]
Business application name 1 (161)
N1), the name of the business application under operation 2 (161N)
2), working application name 3 (161N
3), ... are checked in order and cleared (unused)
Look for things.

For example, assuming that the name of the working application 1 (161N2) is working, the value corresponding to the business application name 182N is written in [2] Working application name 1 (161N2).

Next, the process 15e performs (8) the processing of the work data file 18 as step S6308.
Is the next record.

For example, if the target record of the work data file 18 is the second record 182, the next target record is set to the third record 183.

Next, the process 15e includes (9) the processing of the work data file 18 as the process of step S6309.
Judge whether or not all records have been processed,
[1] When the processing for all records is completed, the entire processing is terminated. If there is an unprocessed record in the work data file 18, (3) the process proceeds to step S6303 and the above-described processing is repeated. .

In the present embodiment, similarly to the first embodiment, based on the business log 14 issued in the process of executing the business application of the client, the operating state of the client corresponding to the business log 14 (running Or non-operating state) can be easily detected and grasped.

In particular, according to the present embodiment, the client operating state detection process 1 can be performed without modifying the existing process (client business log registration process 12a).
Since 5e can be introduced, the introduction is very easy.

Furthermore, according to the present embodiment, since the entire operation log file 13 can be processed collectively, the client operation state grasping process can be executed more efficiently by adjusting the read interval. be able to.

(Seventh Embodiment) FIG. 37 is a block diagram showing a schematic configuration of a client / server system 1f including a client operation status grasping system according to a seventh embodiment of the present invention.

In the client / server system 1f of the present embodiment, the client operating state detection process 15f of the server 10 and the work data file 18a
Are respectively different from the configuration of the second embodiment and the configuration of the sixth embodiment, and the other configurations are substantially the same as the configurations of the second and sixth embodiments. The description is omitted or simplified.

FIG. 38 is a diagram showing an example of the configuration of the work data file 18a according to the present embodiment. As shown in FIG. 18a, the work data file 18a includes a business start log and a business end log sequentially. Are written (registered) as one record, second record,...

That is, according to the present embodiment, as shown in FIG. 39, the process 15f includes the above-described step S6.
After executing the process 1 (business start log and business end log extraction process), as a process of step S62a, a client name
For each set of business application name / business application name branch number, only the log record of business start with the latest date and time is left, and the other records are invalidated.

This embodiment is characterized in the processing of step S62a.

That is, the process 15f includes the step S
As details of the process of 62a, as shown in FIG. 40, after executing the processes of steps S6201 to S6203 described above, if the message number 18LB indicates that the job has started, the process corresponds to step S12a of the second embodiment. In the processing of S6204a, of all records younger than the position of the target record, all records whose set of the client name / business application name / business application name branch number matches the value of the target record are invalidated.

For example, if the target record is the L-th record 18
If it is L, records younger than the position of the target record are the L-1 record, the L-2 record,..., The third record, the second record, and the first record.

That is, the process 15f performs [1] the first
The following actions on the L-1 records _{18L -1} from the record 181.

<1> Client name 18iC = Client name 18LC, <2> Business application name 18i
N = business application name 18LN, <3> branch number 18LK of business application name in multitasking 18i = branch number 18LK of business application name in multitasking
Are cleared (invalidated) for all records i (18i) where all of

Next, the process 15f performs [2] (7)
Proceed to step S6207.

On the other hand, when the message number 18LB indicates that the operation has been completed, the process 15f performs the processing of step S6205a corresponding to step S12a of the second embodiment, among all records younger than the position of the target record. Client name, business application name,
Invalidate all the business application name branch number pairs that match the value of the target record.

For example, if the target record is the L-th record 18
If it is L, records younger than the position of the target record are the L-1 record, the L-2 record,..., The third record, the second record, and the first record.

That is, the process 15f includes [1] the first
The following actions on the L-1 records _{18L -1} from the record 181.

<1> Client name 18iC = Client name 18LC, <2> Business application name 18i
N = business application name 18LN, <3> branch number 18iK of the business application name at the time of multitasking = branch number 18L of the business application name at the time of multitasking
Clear (invalidate) all records i (18i) that satisfy all of K.

The following is the same as the processing of FIG.

Then, as shown in FIG. 41, the process 15f executes the processes of steps S6301 to S6304 described above, and then corresponds to step S5a of the second embodiment. The value of the target record of the working data file is written to the client name, the working business application name, and the branch number of the working business application name in the empty record of the status table.

For example, it is assumed that the target record of the work data file is the second record 182, and the empty record of the client operation status table is the first record 161.

At this time, the process 15f executes [1]
Write the value of the client name 182C as the client name 162C of the record, and [2] write the value of the business application name 182N as the value of the working application name 1 (162N1) of the first record,
[3] The value of the branch number of the business application name at the time of multitasking is written as the branch number 162K1 of the business application name 1 in operation of the first record.

On the other hand, the process 15f corresponds to the step S8a of the second embodiment (7) Step S6307a
In the process of (1), the value of the target record of the work data file is written to the name of the business application in operation and the branch number of the business application name in the corresponding record of the client operation status table 16a.

For example, it is assumed that the target record of the work data file is the second record 182 and the corresponding record of the client operation status table is the first record 161.

At this time, the process 15f executes [1]
Business application name 1 (161)
N1), the name of the business application under operation 2 (161N)
2), working application name 3 (161N
3), ... are checked in order and cleared (unused)
Look for things.

For example, assuming that the name of the working business application 1 161N2 is [2] the value corresponding to the business application name 182N is written in the working business application name 1 (161N2), and [3] the working business name. Branch number 182 of business application name at the time of multitasking is added to branch number 161K2 of application name 1
Write K.

The following is the same as steps S6308 to S6309 described above.

That is, according to the present embodiment, similarly to the second embodiment, the operating state of the business application can be determined for each branch number of the business application, and erroneous detection of the client operating state during multitasking can be performed. It can be avoided reliably.

(Eighth Embodiment) FIG. 42 is a block diagram showing a schematic configuration of a client / server system 1g including a client operation state grasping system according to an eighth embodiment of the present invention.

In the client / server system 1g of the present embodiment, the client operating state detection process 15g of the server 10 is different from the configuration of the third embodiment and the configuration of the sixth embodiment. Since the configurations are substantially the same as those of the third and sixth embodiments, the same components are denoted by the same reference numerals and description thereof will be omitted or simplified.

That is, according to the present embodiment, the process 15g executes the above-described processing of step S61 (the processing of extracting the business start log and the business end log) and then executes the processing of step S61.
In the process of 62b, only the log record of the business start with the latest date and time is left for each set of the client name, business application name, and branch number of the business application name, and the other records are invalid. To

This embodiment is characterized in the processing of step S62b.

That is, the process 15g includes the step S
As details of the processing of 62a, as shown in FIG. 40, after executing the processing of steps S6201 to S6204 described above, it is determined whether or not the business application name of the target record has a starting lower hierarchy (step S7000).

In this embodiment, similarly to the third embodiment, as shown in FIG. 17, when the business application name is the application X (22), the starting lower hierarchy is
Application Y (23), Application Z (2
4), application U (26) and application V (27).

The business application names are application Z (24), application W (25), application U (26), application V (2
In the case of 7), there is no activation lower hierarchy.

That is, the process 15g includes the step S
In the process of 7000, first, the business application name of the activation lower hierarchy of the target business application name is obtained from the activation lower hierarchy information 17.

That is, the process 15g sets [1] the target record as the first record 171 and [2] checks whether the business application name of the target record is written.

For example, the target record is the first record 17
If it is 1, the process 15g proceeds to [3] if the business application name 171N is written,
Otherwise, proceed to [6].

When the business application name 171N has been written, the process 15g checks whether the application name of the upper layer of the [3] target record has been written.

For example, if the target record is the first record 17
1 and the business application name 17 in the upper hierarchy
If 1P has been written, the operation proceeds to [4]. If not, the operation proceeds to [6].

The business application 171P of the upper hierarchy
Is written, it is checked whether or not [4] the business application name 171P in the upper hierarchy matches the target business application name.

For example, when the business application name 171P in the upper hierarchy matches the corresponding business application name, the business application name 171N is stored as the starting lower hierarchy of the relevant business application name, and when they do not match, the procedure proceeds to [5].

If they do not match, the process 15g
[5] For example, assuming that the target record is the first record, the j-th record in which the business application name 171P of the upper hierarchy = the business application name 17jN is searched.

Next, process 15g comprises: a. When the business application name 17jP of the upper hierarchy exists and matches the target business application name, the business application name 171P is recorded as the activation lower hierarchy of the business application 14N, and the process proceeds to [6].

The process 15g is executed by b. If the business application name 17jP of the upper hierarchy exists and does not match the target business application name, the k-th record in which the business application name 17jP of the upper hierarchy = business application name 17kN is further searched, and the process returns to a.

Next, the process 15g includes: c. When the business application name 17jP of the upper layer is not written, the process proceeds to [6].

Then, the process 15g determines whether or not all records of the client business application activation lower layer information have been processed [6]. If all the records have been processed, the process proceeds to [7]. If there is, the process proceeds to [2] with the target record as the next record.

The process 15g is a process of [7],
The process moves to the process of step S7001 of (8).

It should be noted that the above-described processing is described so that the processing can be performed even when the hierarchy is a hierarchy of four generations (parent, child, grandchild, and great-grandchild).

Then, the process 15g is described in (8) S70
In the process 01, the work end data of the work names of all the start lower layers of the business application are additionally written at a position before the target record of the work data file 18.

[0292] For example, if the target record is a 18L, process 15g is [1] between the target record 18L and the L-1 record _{18L -1} (7) of the number of items of the business application name stored in Insert a record. In this case, there are four business applications Y, business application Z, business application U, and business application V.

[2] That is, [2]
If R, the process 15g has the client name 18R
A value corresponding to the client name 18LC is written as C, a business application Y, a business application Z, a business application U, and a business application V are respectively written in the four records as the business application name 18RN, and the message number is further written. A number indicating the end of the job is written as 18RB, and a message character string indicating the end of the job is written as the message character string 18RM.

Then, the process 15g shifts to the processing of the above-mentioned steps S6207 to S6208,
The processing described above is executed for all records in the work file 18.

That is, according to this embodiment, when the business application is restarted in the client, a record with the same business application name exists at a position younger than the position of the record. Invalidate the record (step S620
4) Next, since the end of business data can be added to all the business application names in the startup hierarchy for the disabled business application, the upper hierarchy business can be added as in the third embodiment. Even when an application terminates abnormally (without a task termination log), it is possible to accurately grasp the status of all the task applications at the lower hierarchical level of the application.

(Ninth Embodiment) FIG. 45 is a block diagram showing a schematic configuration of a client / server system 1h including a client operating state grasping system according to a ninth embodiment of the present invention.

In the client / server system 1h of the present embodiment, the client operation state detection process 15h of the server 10 is different from the configuration of the fourth embodiment and the configuration of the sixth embodiment. Since the configurations are substantially the same as those of the third and sixth embodiments, the same components are denoted by the same reference numerals and description thereof will be omitted or simplified.

That is, according to the present embodiment, the process 15h performs the process of extracting the business start log in addition to the business start log and the business end log as the process of step S61b. S62c
Of the work data file 18, only the log record of the latest date and time of the business start is left for each set of the client name, business application name, and branch number of the business application name, and the other records are invalidated. Is performing processing.

That is, after the process 15h performs the processes of steps S6101 to S6102, as a process of step S7005, the process log is any one of a business start log, a business end log, and a business startup log. Determine whether or not.

[0300] If the result of this determination is that the target record is any of a business start log, a business end log, and a business startup log, the flow shifts to the next step S7006, where the target record is a business start log, a business end log. If it is not any of the business start-up logs, the flow shifts to the process of step S6105 described above.

At step S7006, process 1
5h writes the target record, that is, any one of the log data of the business start log, the business end log, and the business start-up log to the work data file 18 (data is written in order from the first record).

As described above, only the business start log, the business end log, and the business start log are extracted and written in the work data file 18 of the present embodiment.

At this time, step S62c of the present embodiment
Processing (extracting the log record of the business start at the latest date and time)
After executing the above-described processes of steps S6201 to S6203, that is, when the target record is not the business start, it is determined whether or not the message number 18LB is the business end (step S7100). (Step S7100 → YES), out of all records younger than the position of the target record, those whose client name and business application name match the value of the target record are invalidated (Step S7100).
7101).

On the other hand, as a result of the determination in step S7100,
If the job is not completed (step S7100 → N
O), the process 15h determines that the target record is a business start-up log, and as a process of step S6205, among all records younger than the target record, its client name and business application name are set to the value of the target record. Invalidate all matches.

For example, if the target record is the L-th record 18
If it is L, records younger than the position of the target record are the L-1 record, the L-2 record,..., The third record, the second record, and the first record.

That is, the process 15h is performed according to [1]
From the record 181 to the L-1st record 18L- ₁ , the client name 18iC = the client name 18L
C, and all records i for which the business application name 18iN = the business application name 18LN
The record (18i) is cleared (invalid).

Subsequently, the process 15h proceeds to step S6
In step 206, the target record is invalidated.

For example, if the target record is the L-th record 18
If it is L, [1] the record of the L-th record 18L is cleared (invalid).

Next, the process 15h proceeds to step S6
In the process of 207, the target record of the work data file 18 is set as the next record.

That is, for example, if the current target record is the L-th record 18L, the next record is 1
The preceding L-1th record 18L- ₁ is obtained.

Then, the process 15h is executed in step S6.
In the process of 208, it is determined whether or not all records in the work data file 18 have been processed. [1] When the first record has been processed as a target record, the process is terminated, and the unprocessed record becomes the work data. If it exists in the file 18, (2) the process shifts to the process of step S6202 and the above process is repeated.

As a result, in the work data file 18, only the work start log 14 of the latest date and time excluding the work end log and the work start log is left.

As described above, according to the present embodiment,
For example, when the business application X, which is the upper layer of the business applications Y and Z, terminates abnormally and the operating status of the client becomes inaccurate, when the client is started up (the business start-up log 14 The determination in steps S6203 and S7100 is NO, and the processing in step S6205 determines the records corresponding to all business application names in the lower-level startup hierarchy for the business application corresponding to the target record. Since it can be invalidated, the operating status of the abnormally terminated client can be accurately grasped via the client operating status table 16 as in the fourth embodiment.

(Tenth Embodiment) FIG. 47 is a block diagram showing a schematic configuration of a client / server system 1i including a client operation status grasping system according to a tenth embodiment of the present invention.

In the client / server system 1i of the present embodiment, the client operating state detection process 15i of the server 10 and the work data file 18b
Are respectively different from the configuration of the fifth embodiment and the configuration of the sixth embodiment, and other configurations are substantially the same as the configurations of the fifth and sixth embodiments. The description is omitted or simplified.

FIG. 48 is a diagram showing an example of the configuration of the work data file 18b of the present embodiment. As shown in FIG. 48, the work data file 18b includes The log and the task end log are sequentially written (registered) as a first record, a second record,...

FIG. 49 is a diagram showing a configuration example of the client operation state table 16d of the present embodiment.

As shown in FIG. 49, the client operating status table 16i stores the operating client name 16
1C, data 161T representing the update date and time of the client,
Data 1 indicating the status of the client (running / not running)
61S, the name of the business application 1 that is working on the client (161N1), the work start date and time 161NT1 of the business application 1 that is working, and the work release detection presence / absence information of the business application 1 that is working—the business application name 4 that is working (161N4), the working application name 4 (161NT4) and the work release detection presence / absence information of the working application name 1 are sequentially recorded in the first record, the second record,.
・ It is to be memorized as.

According to the present embodiment, the process 1
5i, as shown in FIG.
After executing the processes of S01 to S6305, as a process of step S7200 corresponding to step S40 of the fifth embodiment, the value of the target record of the work data file 18b is added to the date and time information in the corresponding record of the client operation status table 16. Write.

For example, the target record in the work data file 18b is the second record 182, and the corresponding record in the client operation status table 16 is the first record 1
If it is 61, the process 15i writes the value of the registration date and time 182T with respect to [1] the work start date and time 162N1T of the working application name 1 in the first record, and then [2] the state of the first record Update date 162
The value of the registration date 182T is written to T.

[0321] Hereinafter, by the processing in step S6306,
The status of the client in the corresponding record of the client operation status table 16 is set to “operating”.

On the other hand, as the processing of step S6307 corresponding to steps S7 to S8 of the first embodiment,
When the value of the target record of the work data file is written to the name of the working business application in the corresponding record of the client operation status table 16, the process 1
5i writes the value of the target record of the work data file 18b in the date and time information in the corresponding record of the client operation status table 16 as the process of Step S7201 corresponding to Step S41 of the fifth embodiment.

For example, the target record of the work data file 18b is the second record 182, and the corresponding record of the client operation status table 16 is the first record 1
If it is 61, the process 15i writes the value of the registration date and time 182T with respect to [1] the work start date and time 162N1T of the working application name 1 in the first record, and then [2] the state of the first record Update date 162
The value of the registration date 182T is written to T.

[0324] Hereinafter, the process 15i includes step S63.
In step 08, the target record in the work data file 18 is set as the next record, and in step S6309, it is determined whether all records in the work data file 18b have been processed. When the processing for all the records is completed, the process proceeds to step S7202. If an unprocessed record exists in the work data file 18b, the process proceeds to step S6303 to repeat the above process.

Then, the process 15i is executed in step S7.
As the processing of 202, the operation management terminal 100 of FIG.
The following processing is performed in the same manner as the processing of (1).

[1] Client Operation Status Table 16
The first record 161 of i is a target record.

[2] For example, assume that the first record 161 is the target record. <1> Business application name 1 (16
1N1). <2> Check whether the name of the target working application is written. For example, if the target is the business application name 1, the business application name 1 in operation
It is checked whether (161N1) has been written. At this time, if it has been written, the difference between the work start date and time 161N1T of the business application name 1 under work and the current time is obtained, and the process proceeds to <3>. If it has not been written, the process proceeds to <4>. move on. <3> If the difference is larger than a certain value, the presence / absence detection of presence / absence detection of the work corresponding to the target business application name is set to “detected”. For example, assuming that the target is the business application name 1 in operation, the presence / absence detection 161N1W of the work application name 1 in operation is detected. <4> Check whether all business application names in the record have been processed. At this time, if the processing has been completed for all business application names in the record, the process proceeds to <5>. On the other hand, if the unprocessed business application name is AR, <2> is set for the next business application name. Go to>. For example, if the target is business application name 1, the next target is business application name 2. <5> It is checked whether all records in the client operation state table 16i have been processed. At this time, if there is an unprocessed record, the process 15i sets the target record to the next record (for example, if the target is the first record, sets the next record to the second rate 162) and sets <2
And the processing of <2> to <5> is performed again. <6> On the other hand, if there is no unprocessed record,
The process 15i includes a client operation state table 16
i, that is, for the business application determined to be in the abandoned state, the client operating state table 16i to which the operation abandonment detection data is added is displayed on the screen as client operating state display data, and the processing is terminated. .

In other words, according to the present embodiment, when the difference between the work start date and time and the current date and time of each business application of the client exceeds a certain value, in other words, when the state of leaving work exceeds a certain time, Since the data indicating that the work application has been left unattended can be added to the business application, and the data indicating the client operating state in a state where the data indicating that the work has been left unattended has been added can be displayed on the screen, the server 10 can use the data based on the display data. It is possible to notify the corresponding client of data for warning that the work has been left unattended, and it is possible to avoid leaving the business application unattended on the client side.

In each of the above embodiments, the server 1
Although 0 is one server, the present invention is not limited to this, and can be applied to a plurality of servers.

Further, in each of the above-described embodiments, the client operating state grasping system (client operating state grasping program, grasping function) is mounted on the server 10 side. However, the present invention is not limited to this. It can also be installed on the client side.

[0331]

As described above, according to the client operating state grasping method and system and the client operating state grasping program according to the present invention, the business start log and the business start log in the business log generated in the process of executing the business application of the client. The operation status of the client can be ascertained by using at least one of the business end logs, so the operation status detection mechanism on the client side, the communication mechanism for the operation status with the server, and the operation on the server side with the client There is no need to specially incorporate the status communication mechanism.

Therefore, the processing load based on the mechanism built into the client itself and the server itself and the processing load on the communication line based on the operating state communication are eliminated, and the speed of the original business application processing of the client and the communication between the client and the server are eliminated. The communication speeds via the communication paths can be improved.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a schematic configuration of a client / server system including a client operating state grasping system according to a first embodiment of the present invention.

FIG. 2 is a diagram conceptually showing a data configuration of one business log in the first embodiment.

FIG. 3 is a view showing an example of the arrangement of a business log file according to the first embodiment;

FIG. 4 is a diagram illustrating a configuration example of a client operation state table according to the first embodiment.

FIG. 5 is a schematic flowchart illustrating an example of processing of a client operation state detection process of the server according to the first embodiment.

FIG. 6 is an exemplary flowchart illustrating an example of processing of a client operating state detection process of the server according to the first embodiment;

FIG. 7 is a diagram showing a detection result of a client operating state based on the processing of steps S1 to S14 in the client operating state detecting process of the server.

FIG. 8 is a block diagram showing a schematic configuration of a client / server system including a client operating state grasping system according to a second embodiment of the present invention.

FIG. 9 shows one business log 14 in the second embodiment.
The figure which shows notionally the data structure of FIG.

FIG. 10 is a view showing a configuration example of a task log file according to the second embodiment;

FIG. 11 is a diagram illustrating a configuration example of a client operation state table according to the second embodiment.

FIG. 12 is a schematic flowchart illustrating an example of processing of a client operating state detection process of a server according to the second embodiment.

FIG. 13 is a schematic flowchart illustrating an example of processing of a client operation state detection process of a server according to the second embodiment.

FIG. 14 is a view showing a result of detection of a client operation state based on the processing of a client operation state detection process of a server according to the second embodiment.

FIG. 15 is a view showing a client operation state detection result when the processing of the server client operation state detection process described in the first embodiment is applied at the time of multitasking.

FIG. 16 is a block diagram showing a schematic configuration of a client / server system including a client operating state grasping system according to a third embodiment of the present invention.

FIG. 17 is a diagram illustrating a starting hierarchical structure of a business application according to the third embodiment.

FIG. 18 is a diagram illustrating a configuration example of an activation lower layer information table stored in a server according to the third embodiment.

FIG. 19 is a schematic flowchart illustrating an example of processing of a client operation state detection process of a server according to the third embodiment.

FIG. 20 is a view showing a result of detection of a client operation state based on the processing of a client operation state detection process of a server according to the third embodiment.

FIG. 21 is a diagram illustrating a result of detecting a client operating state when a business application of the client ends abnormally in the processing of the client operating state detecting process described in the first embodiment.

FIG. 22 is a block diagram showing a schematic configuration of a client / server system including a client operating state grasping system according to a fourth embodiment of the present invention.

FIG. 23 is a schematic flowchart illustrating an example of processing of a client operating state detection process of a server according to the fourth embodiment.

FIG. 24 is a view showing a result of detection of a client operation state based on the processing of a client operation state detection process of a server according to the fourth embodiment.

FIG. 25 is a block diagram showing a schematic configuration of a client / server system including a client operating state grasping system according to a fifth embodiment of the present invention.

FIG. 26 is a diagram conceptually illustrating a data configuration of one business log in the fifth embodiment.

FIG. 27 is a diagram illustrating a configuration example of a client operation state table according to the fifth embodiment.

FIG. 28 is a schematic flowchart illustrating an example of processing of a client operation state detection process of a server according to the fifth embodiment.

FIG. 29 is a schematic flowchart showing an example of processing of a client operating state detection process of a server according to the fifth embodiment.

FIG. 30 is a flowchart showing an operation based on a client operation status display function of the operation management terminal according to the fifth embodiment.

FIG. 31 is a block diagram showing a schematic configuration of a client / server system including a client operating state grasping system according to a sixth embodiment of the present invention.

FIG. 32 is a schematic flowchart showing an example of processing of a client operating state detection process of a server according to the sixth embodiment.

FIG. 33 is a flowchart for explaining in detail the processing in step S61 of the client operating state detection process according to the sixth embodiment;

FIG. 34 is a diagram showing a configuration example of a work data file according to the sixth embodiment.

FIG. 35 is a flowchart for explaining in detail the processing in step S62 of the client operating state detection process according to the sixth embodiment;

FIG. 36 is a flowchart for explaining in detail the processing in step S63 of the client operating state detection process according to the sixth embodiment;

FIG. 37 is a block diagram showing a schematic configuration of a client / server system including a client operating state grasping system according to a seventh embodiment of the present invention.

FIG. 38 is a view showing a configuration example of a work data file according to the seventh embodiment.

FIG. 39 is an exemplary flowchart illustrating an example of the processing of a client operating state detection process of the server according to the seventh embodiment;

FIG. 40 is a flowchart for describing the processing in step S62a of the client operating state detection process according to the seventh embodiment in detail;

FIG. 41 is a flowchart for explaining in detail the processing in step S63 of the client operating state detection process according to the seventh embodiment;

FIG. 42 is a block diagram showing a schematic configuration of a client / server system including a client operating state grasping system according to an eighth embodiment of the present invention.

FIG. 43 is a flowchart for describing in detail the processing in step S62b of the client operating state detection process according to the eighth embodiment;

FIG. 44 is a block diagram showing a schematic configuration of a client / server system including a client operating state grasping system according to a ninth embodiment of the present invention.

FIG. 45 is a flowchart for describing in detail the processing in step S61b of the client operating state detection process according to the ninth embodiment;

FIG. 46 is a flowchart for explaining in detail the processing in step S62c of the client operating state detection process according to the ninth embodiment;

FIG. 47 is a block diagram showing a schematic configuration of a client / server system including a client operating state grasping system according to a tenth embodiment of the present invention.

FIG. 48 is a view showing a configuration example of a work data file according to the tenth embodiment;

FIG. 49 is a view showing a configuration example of a client operation state table according to the tenth embodiment;

FIG. 50 is an exemplary flowchart for explaining in detail the process of step S63 of the client operating state detection process according to the tenth embodiment;

[Explanation of symbols]

1, 1a-1i Client / server system 10 Server 11 Communication process with client 12, 12a Client business log registration process 13, 13a Client business log file 14, 14a, 14b One business log 15, 15, a, 15b , 15c, 15d, 15e, 15
f, 15g, 15h, 15i Client operating state detection process 16, 16a, 16b, 16c, 16i Client operating state table 17 Client business application start lower layer information table 18, 18a, 18b Work data file 20 Client # 1 21 Server Communication process 22 business application process X 22a1 business application process X-1 22a2 business application process X-2 23 business application process Y 23a1 business application process Y-1 23a2 business application process Y-2 24 business application process Z 25 business application process W 30 Client # 2 40 Client # 3 100 Operation management terminal 101 Client Operation status display function

Claims (12)

[Claims] 1. A program executable by at least one of the client and server in a client / server system in which a client and server capable of running at least one business application are communicably connected via a communication network. Wherein at least one of the client and the server is at least one based on the processing of the client.
Means for extracting business start log data indicating a business start and business end log data indicating a business end extracted from a plurality of business log data issued according to one business application operation, and extracted business start log data And a function for ascertaining the operating state of the client based on at least one of the operation end log data and a client end state log data. 2. The client operating state grasping program according to claim 1, wherein the client is capable of running a plurality of business applications, and the extracting unit is configured to execute each of the business applications. Means for extracting, from the business log data, business start log data and business end log data corresponding to the business application, wherein the operating state grasping means uses the business start log data corresponding to the business application to Means for setting a client to be operated to an operation state, means for setting a corresponding business application to an operation end state based on the operation end log data for the business application set to the operation state, and operation operation state by the operation end state setting means. To Means for recognizing the client as a non-operational state when all business applications corresponding to the set clients are set to an operation end state. 3. The client operating state grasping program according to claim 2, wherein the business log data is a message indicating corresponding client identification information, identification information of a corresponding business application, and business contents of the corresponding business application. The operation state setting means, when the business start log data is extracted by the extraction means, whether client identification information corresponding to the business start log data is written in a table prepared in advance. Means for determining whether or not the client and the business application are set to the operating state by writing the client identification information and the business application identification information in association with each other if the result of the determination indicates that the client and the business application have not been written And the end of the operation Ending state setting means, when the extraction means extracts the business end log data, a determination means for determining whether business application identification information corresponding to the business end log data is written in the table. Means for erasing the business application identification information written in the table when the result of the determination indicates that the business application identification information has been written. Determining means for determining, when the information is deleted, whether other business application identification information corresponding to the client identification information based on the deleted business application identification information is written in the table, and a result of the determination; , If not written, the client will be inactive A client operating state grasping program, comprising: a recognition unit. 4. The client operating state grasping program according to claim 2, wherein the business log data includes identification information corresponding to the multitask when the corresponding business application is executed by the multitask. The operating state setting means includes means for setting the operating state of the business application and the corresponding client based on the corresponding business application identification information based on the business start log data for each business application; Has a means for setting the business application based on the corresponding identification information to the operation end state according to the business end log data, and the non-operation state setting means sets the operation application to the business operation state by the operation end state setting means. All identification numbers corresponding to the client When the business applications based is set in the operation end state, the client operating state grasping program, characterized in that the client had a means for recognizing the non-operating state. 5. The client operating state grasping program according to claim 2, wherein at least a part of the plurality of business applications among the plurality of business applications has a startup hierarchical structure, and the operating state setting is performed. The means is configured such that when a plurality of business applications forming the startup hierarchy structure are set to the operating state, when the business start log data for the business application of the higher startup hierarchy is extracted again by the extraction means,
A client operating status grasping program, comprising: means for setting an operating status of a business application lower in the hierarchy than a business application in an upper startup hierarchy to an operation end status. 6. The program according to claim 2, wherein the extracting unit extracts business start log data and a business start log data corresponding to the business application from business log data issued by executing the business application. In addition to the end log data, it is means for extracting business start-up log data representing the start of the business application. And a means for setting all the business applications set in the operation state to the end state by the operation state setting means. 7. The client operating status ascertaining program according to claim 3, wherein the operating status setting means includes information indicating a business application start date and time in addition to the client identification information and the business application identification information. Means for setting the client and the business application in the operating state by writing in association with each other; and when the difference between the date and time information of the business application written in the table and the current date and time is equal to or more than a certain value, the difference is constant. A means for executing a process for warning a client that a task has been left unattended based on a business application having a value greater than or equal to a value. 8. The client status grasping program according to claim 1, wherein the extraction unit is configured to execute a task start log data and a task start log data based on a task log data for each case passed by a task application execution process of the client. A client state grasping program, comprising: means for extracting task end log data indicating the end of a task. 9. The client status grasping program according to claim 1, wherein the client is capable of running a plurality of business applications, and the extracting unit is sequentially created by business application execution processing of the client. Means for reading a business log file including a plurality of business log data, and extracting only business start log data and business end log data from the read business log file; and Means for extracting only the latest business start log data for each of the client and each business application, wherein the operating state grasping means sets the business application and the corresponding client corresponding to the extracted business start log data to the operating state. Having means to do A client state grasping program characterized by the following. 10. A client operating state grasping system for grasping an operating state of a client capable of running at least one business application connected to a server via a communication network, wherein at least one client operating state grasping system based on processing of the client is provided. Extraction means for extracting business start log data indicating a business start and business end log data indicating a business end from a plurality of business log data issued according to one business application operation, and the extracted business start log data and business A client operating state grasping system comprising: operating state grasping means for grasping the operating state of the client based on at least one of the end log data. 11. The client operating state grasping system according to claim 10, wherein the extracting means and the operating state grasping means are realized as at least one of the function of the server and the client. Operation status grasp system. 12. A client operating state grasping method for grasping an operating state of a client capable of running at least one business application connected to a server via a communication network, the method comprising: Extracting business start log data indicating a business start and business end log data indicating a business end from a plurality of business log data issued according to one business application operation, and extracting the extracted business start log data and business end Grasping the operating state of the client based on at least one of the log data.