JP2003288221A - Data processing system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To make users feel less stress and enhance operational efficiency by reducing the waiting time of a client computer after the transmission of a processing request to a server computer. <P>SOLUTION: In this data processing system, the server computer 51 executes a task matching a data processing request transmitted by the client computer 11, and the result is sent back to the client computer 11. The data processing system is provided with a reception managing part 51A which receives data processing requests from the client computer 11; an execution managing part 51D for creating statistical information on the processing requests received by the managing part 51A and for executing the task 51E corresponding to the processing request on the database 52; and a manager's computer 53 which newly registers or changes the attributes of the task 51E using the statistical information so that the execution time of the task 51E decreases. <P>COPYRIGHT: (C)2004,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a data processing system in which a client computer and a server computer are connected by a communication line, and belongs to the technical field of computer networks.

[0002]

2. Description of the Related Art Conventionally, a corporate intranet using the Internet technology is generally constructed as follows.
A web server is installed in a server computer in a computer center of the head office, and a web browser is installed in a client computer of a branch office. The client computer accesses the server computer via the Internet by designating the address of the Web server with the URL, and sends a data processing request such as registration or inquiry to the database of the head office on the browser screen. Upon receiving the processing request, the server computer executes the processing task corresponding to the request and returns the processing result to the client computer. In this way, a series of operations of transmitting a processing request from the client side to the server side, executing a task on the server side, and returning a processing result from the server side to the client side are performed.

[0003]

Therefore, if it takes a long time to execute a task on the server side, the client side has to wait until the result is returned, which increases the user's stress. Further, the client computer occupies a long time, and for example, once a group of processing requests is once issued, another processing request cannot be immediately added again, which wastes time and results in work efficiency. Is reduced.

The present invention addresses the above-mentioned inconvenience, and shortens the unnecessary waiting time on the client side after transmitting a processing request as much as possible, thereby reducing the user's feeling of stress and working efficiency. The main issue is to improve The present invention will be described in detail below, including other problems.

[0005]

In order to solve the above-mentioned problems, according to the invention described in claim 1, the server computer executes a task according to the data processing request transmitted by the client computer, A data processing system for returning a result to a client computer, the processing request receiving unit receiving a data processing request from the client computer, the statistical information creating unit creating statistical information of the processing request received by the receiving unit, Based on the task execution means for executing the task corresponding to the processing request received by the reception means to the database and the statistical information created by the statistical information creation means, the task execution time is shortened so that the task execution time is shortened. The task setting means for newly registering the task executed by the means or changing the attribute Vignetting wherein the are.

According to the present invention, the task is newly registered or the attribute is changed based on the statistical information of the processing request from the client side so that the task execution time on the server side is shortened. For example, when a certain processing request is concentrated in a certain time zone, a task corresponding to the processing request is newly registered so that as many tasks as possible are handled. Alternatively, the number of requests fetched once is increased so that as many requests as possible are processed at once. As a result, the task execution time on the server side is shortened as much as possible, and the unnecessary waiting time on the client side after sending the processing request is shortened as much as possible, resulting in less stress to the user and Work efficiency is improved.

Next, the invention described in claim 2 is the same as claim 1.
In the invention described in (3), based on the reply request accepting means for accepting a reply request for the processing result from the client computer and the reply request accepted by the accepting means, when the processing result is obtained, the processing result is If not, a reply means for replying to the client computer indicating that the processing is in progress is provided.

According to the present invention, when the processing result is returned from the client side, if the task is already completed and the processing result is output, the processing result is returned to the client side, while the task is still executed. Not completed,
Even when the processing result is not displayed, the fact that the processing is being performed is reported to the client side, so that the user's feeling of stress and anxiety is reduced even while waiting for the reply of the result.

In other words, according to the first aspect of the invention, the task execution time on the server side is shortened as much as possible to shorten the waiting time of the user, thereby reducing the feeling of stress. On the other hand, in the invention described in claim 2, from the viewpoint different from whether the task execution time is short on the server side, the progress status that the processing result is being processed until the processing result is returned. By notifying the user, the user's stress and the skepticism and anxiety about whether or not the requested processing is being performed are alleviated.

Next, the invention described in claim 3 is the same as claim 1
Alternatively, the processing request accumulating means for accumulating the processing request accepted by the processing request accepting means is provided, and the task executing means performs the accepting operation of the accepting means for accepting the processing request accumulated by the accumulating means. It is characterized by processing sequentially in an asynchronous manner.

According to the present invention, by using a queuing method, for example, the acceptance of the processing request and the execution of the task can be separated and individually operated, and the task is operated by the user operating the client computer. Progressing in the background. As a result, the user sends a processing request to the server computer, and after the server computer accepts the processing request, the user is not bound by the presence or absence of the result reply from the server computer or the timing thereof, and again (even if the previous It is possible to continue sending other requests (even if the server computer has not yet received a reply to the request sent to. Therefore, even if the processing on the server side takes a long time and the result reply comes back with a considerable delay in time, the user does not have to wait in front of the client computer during that time, and the feeling of stress does not increase, Further, the decrease in work efficiency is also eliminated.

That is, according to the first aspect of the present invention, the task execution time on the server side is shortened as much as possible to shorten the waiting time of the user, thereby reducing stress and reducing work efficiency. On the other hand, in the invention described in claim 3, from the viewpoint different from whether or not the task execution time on the server side is short, transmission of a processing request from the client side to the server side is performed. , The execution of the task on the server side is asynchronous, not as a series of operations,
By making the operations independent of each other, it is intended to reduce the user's feeling of stress and improve work efficiency.

Next, the invention according to claim 4 relates to claim 1
The invention described in any one of (1) to (3) is characterized in that the client computer and the server computer are connected via the Internet.

According to the present invention, in a corporate intranet or the like using the Internet technology in which http is adopted as the communication protocol, the same effects as those of the inventions according to claims 1 to 3 can be obtained. In this case, for example, the Web server of the server computer is in charge of only a function having a comparatively light load, such as receiving a processing request or a reply request from the client side. On the other hand, execution of a task with a heavy load is performed by an independent / dedicated, for example, database server resident in the server computer. By doing this, http, which is a simple one-time communication protocol
Is involved only in the operation of accepting a lightly loaded request between the client and the server, the waiting time for the user can be short. Then, the requested processing task is executed asynchronously in the background separated from the communication between computers by http. Less than,
The present invention will be described in more detail through the embodiments of the invention.

[0015]

DESCRIPTION OF THE PREFERRED EMBODIMENTS As shown in FIG. 1, the data processing system according to this embodiment is applied to an intranet of a company, such as a bank or a trading company, which utilizes the Internet X. Two computer computers 51 and 52 are provided in the computer center of the head office. A web server is installed in one server 51 and the other server 5
2 is equipped with a database server. The server computer 51 has a transaction function linked with the database server 52. Of course, they may be integrated into one computer. These server computers 51 and 52 are connected to a large number of nodes in the head office by LAN, including the client computer 53 for the system administrator. The system administrator uses the management client computer 53 to manage the operation performance of the intranet, and performs new registration and attribute change of the task according to the totalization / statistical results.

A LAN is also constructed in each of the regional branches (only two branches are shown). The client computers 11 and 21 handled by the person in charge at each branch are equipped with Web browsers. The clients 11 and 21 specify the Web server address with the URL
AN routers 19, 29, Internet X, main store LA
It is connected to the server computer 51 via the N router 59.

In such a networked computer system, conventionally, a Web server is generally mounted on the server 51, and the client computers 11 and 21 of the user update or inquire the database 52 on the browser screen. Make a request for. The request is received by the Web server 51 using the http protocol, a process according to the request is performed, and the result is returned to the terminals 11 and 21. This is a general form of a data registration / inquiry system using the Internet technology / Web technology. In such a network system, only the Web browser needs to be installed on the client side. On the other hand, in the so-called order-made corporate information system that does not use the Web technology, it is necessary to install all necessary applications in each client computer in accordance with the server and the system. Therefore, the use of the Web technology as described above has an advantage over the client / server system in that the user's client computer only needs a browser, and the data communication system and the data processing system can be easily introduced. . On the other hand, however, the following problems occur in update work such as data registration and inquiry work such as form inquiry.

First, there is a problem of processing continuity. The update / query request is basically made to the Web server on the server. The Web server activates the update / query processing program for the database in response to this request. And We
The b server waits for this inquiry result,
The general form is to notify the requesting browser. This is because the Web server itself does not have a function of processing or replying to one request asynchronously with the request or having a function of replying the result. Strictly speaking, this is the Web
This is because the http protocol used in (1) is a one-time simple protocol in which a request is issued once and the response is completed. Therefore,
When the http protocol is used or when the Web server is used, the processing of request, update or inquiry, and reply have to be implemented as an indivisible series of processing in terms of the system. Then, in the case where many users simultaneously make requests and the processing time extends for several minutes, this method causes inconvenience. That is, the performance of the database and the performance of the registration / query processing directly affect the waiting time of the Web server. And, when a large number of users concentrate at once, the problem becomes more serious. Here, the processing on the server side takes time as described above, for example, when performing processing tasks such as data registration and inquiry to a database that stores a huge amount of information, or As described above, there are cases where requests are concentrated on the same task.

The second problem is that the browser is occupied on the client side. For example, the operation and control of the browser on the terminal side are occupied until the required data is input on the browser screen, the update request is issued, and then the database on the server is actually updated. That is, as described above, since the request reception process and the update / query process are performed as a series of processes, the next request cannot be made until the output of the result for one request is completed.

Thirdly, there is a problem of load distribution. Considering the load distribution on the server computer in such a system, it is possible to prepare a plurality of Web servers. However, the problem is how to distribute the Web server for each type of request, or for each department or branch that makes a request. For example, if a simple allocation method such as one Web server for one branch is used, It is not possible to respond and change flexibly according to changes, making it difficult to operate the system efficiently.

Therefore, in the present system, first, the operation of accepting requests from the clients 11 and 21 is made independent of the task execution operation of the servers 51 and 52 by adopting the queuing method. That is, the request reception process, the update or inquiry process, and the result reply process are not implemented as an inseparable series of processes but implemented as individual functions that can be independently executed asynchronously with each other.

In this system, (1) "acceptance management" (acceptance) until the user's request is accepted and entered (until the request is inserted into the request acceptance management tables 51B and 51C shown in FIG. 2 and added to the queue). Management unit 51A) and (2) request entries 51B and 51C are regularly monitored, taken out, and handed over to execution module 51E.
“Execution management” (performed by the execution management unit 51D) that reflects the end status in the request entries 51B and 51C,
(3) "Return management" (return management unit 51G) that returns the result processed by the processing module 51E in response to a user request.
3A independent functions 51A, 51
Equipped with D and 51G. Each function 51A, 51D, 51G
Are executed independently of each other and asynchronously.

Upon receiving the request from the client computers 11 and 21, the reception management unit 51A enters the request in the request management tables (queues) 51B and 51C.
The execution management unit 51D uses the request management tables 51B and 51C.
Is monitored at regular intervals, and if there is a new entry, registration / inquiry processing 51E for the corresponding database 52 is activated. Then, after the processing is completed, the request entries 51B and 51C
The status of is updated to process complete. When the user issues a reply request for the result to the request entries 51B and 51C that have completed processing, the return management unit 51G returns the processing result (form inquiry result file) 51F to the client computers 11 and 21.

Here, the Web server 51 is in charge of only the functions of "reception management" 51A and "return management" 51G which are relatively light in load. "Execution management" 51D
Another resident dedicated task on the server 51 takes charge and
b "Reception management" 51A and "Return management" 51 performed by the server
Processing is performed asynchronously with G. Of course, instead of this, for example, the database server 52 uses the “execution management” 51.
You may be in charge of D.

The features of this system configured as described above are as follows.
First, the degree of freedom of operation on the user side computers 11 and 21 is increased. On the user side, the required request can be repeated asynchronously with the execution processing 51D on the server 51 side and continuously within a short time (51
A), the cycle of issuing a request can be significantly shortened. As for the status inquiry (51G), it is possible to print it all together in a batch later, so that the time can be used efficiently.

Secondly, in this system, the module 51
Not only the result file 51F processed by E but also the processing progress information is returned to the user if the file is still being processed. The user can inquire the status information of the request reception queues 51B and 51C, and can grasp the progress of the data processing request issued by the user. As a result, the result file 51F is created, and the stress that the user has to wait until the result is finally returned or returned to the user and the skepticism and anxiety about whether the process is being executed are reduced. Further, since the task execution 51D is performed asynchronously with the processing request reception 51A, it is possible to execute a processing task that takes a relatively long time and has a heavy load without worrying about it. Further, as in this example, the Web server 51 (reception management 51
A, the return management 51G) and the database server 52 (execution management 51D) can be easily arranged by function as separate machines.

Conventionally, when a plurality of processes are requested / requested from a browser at a time, the result is not returned until all the processes are completed. Therefore, subsequent processes (for example, additional processes) are completed until all the processes are completed. It was not possible to continuously perform a processing request or a processing such as a user inputting a comment or the like to the inquired form and printing it.
On the other hand, in this system, after requesting multiple processes at once and the server computer accepts the processes, the next request is always accepted, so do not hesitate to perform the subsequent processes. In addition, since the progress of each process can be known, subsequent processes (for example, a process of printing after inputting the comment described above) can be sequentially performed from the completed process. In other words, there is an advantage that the work can be continued without waiting time.
Further, there is an advantage that the user can make a request to the server for a plurality of processing requests without worrying about the surroundings (without worrying about the processing time).

Thirdly, in this system, the management client computer 53 changes / corrects the attribute of the task that monitors the reception management tables 51B and 51C, thereby enabling flexible load distribution control. A plurality of tasks for monitoring the request reception queues 51B and 51C can be activated, and attributes such as the type of request, department, maximum extraction number, extraction interval, or operating time are registered in advance. be able to. It is also possible to dynamically start a new processing task. As a result, a large number of processing tasks can be assigned to departments with high request frequency or types with high request frequency, and many tasks can be automatically started during the time when requests are concentrated. Load control is possible on one web server.

Fourthly, the present system has a statistical information totalizing function, which makes it possible to support the load balancing plan. The request reception queues 51B and 51C can be stored for any number of days, for example. This includes information such as the request reception time, the type of request, the department that issued the request, the user, and the processing time. For example, statistical information can be obtained for each time zone of the request and the processing state. By using this information as the situation analysis information at the time of setting the processing task, it becomes possible to make a more efficient load distribution plan.

The server computer 51 stores a task schedule table 51H as shown in FIG. For each task, use start date, task ID, timer interval to activate (time interval), target branch number (store number), target form ID, maximum number of retrieval (in one operation Various attributes such as the maximum number of cases to be processed collectively, start time and end time of processing are recorded.

Similarly, the server computer 51 is shown in FIG.
The inquiry reception management table 51C as shown in FIG. Each time there is one processing request, the receipt numbers are serially numbered and the store number is recorded.
Various data such as D and the ID of the corresponding task are registered / inserted in the table 51C in the order of reception (queuing). Although not shown, the registration acceptance management table 5
1B has the same configuration. Also, each of these tables 5
1B, 51C, 51H can be monitored by the management computer 53.

Next, in this data processing system,
Various operations performed by the user of the branch by accessing the server computer 51 of the head office from the terminals 11 and 21 will be described.
First, the form inquiry work will be described. FIG. 5 shows a form inquiry screen that appears when the user clicks “form inquiry” in the form inquiry task in the menu on the left side of the browser screen when the user logs in to the server computer 51 with the client computers 11 and 21. is there.
The user inputs necessary items such as a store number, a course, an account number, a form to be inquired, and clicks the execute button 101.
At this time, it is possible to input a plurality of items. In the example shown in the figure, 10 items can be entered together, and 4 of them are to be entered together and the form inquiry is being performed (slip 1
~ 4).

When the execute button 101 is clicked, an inquiry request is transmitted to the server computer 51, and the terminal side 11 or 21 shifts to the situation inquiry (form) screen shown in FIG. In the processing status column, "waiting for processing" or "processing in progress" is displayed, indicating that none of the inquiries for the slips 1 to 4 has been completed yet. Therefore, the edit and print fields are also displayed as "impossible". This is because not much time has passed since the inquiry request was issued. Note that “waiting for processing” refers to a state in which the transmitted request has been entered in the inquiry reception management table 51C, but the corresponding task has not been started or executed yet, and “processing in progress” means that the corresponding task is It is up and running,
It means that the form inquiry result file 51F has not been created yet.

In this state, if the latest state button 102 is clicked after a little time has passed, the state inquiry (form) screen shown in FIG. 7 is displayed. “Completed” is displayed in all columns of the processing status, indicating that all the inquiry tasks of the slips 1 to 4 have been completed. That is, slips 1 to 4
The form inquiry result file 51F, which is a collection of the data necessary for inquiring, is created for all cases (invoices 1 to 4). However, the slip 2 is locked so that it cannot be edited. However, printing is possible for all slips 1 to 4 (execution by clicking the check box). As a result, if you click the edit button 103,
As shown in FIG. 8, application software for tabulation is activated, and a page displaying a form (slip 1 in the illustrated example) appears. At that time, the data collected in the form inquiry result file 51F is pasted and expanded on this page.

As described above, the user can confirm the current progress status of the processing requested by the user at any time by appropriately pressing the latest status button 102 until the form inquiry is finally completed. As a result, the user is relieved of the feeling of stress and anxiety. Note that FIG.
In the figure, the state in which all four cases (slips 1 to 4) have been processed is shown, but the present invention is not limited to this, and even if only one case is processed, editing / printing is possible from that case. As a result, the waiting time for the user is shortened as much as possible, the feeling of stress is further reduced, and the work efficiency is also improved.

An example of specific control for realizing the above operation will be described with reference to FIGS. 9 to 13. First, FIG.
In the flowchart of FIG. 3, after the task ID is acquired from the schedule table 51H (see FIG. 3) that manages the tasks, the inquiry reception management record is acquired by the inquiry reception management table 5.
This is the operation until additional registration (entry: queuing) in 1C. That is, this is an operation performed by the reception management unit 51A when the user sends a processing request. On the form inquiry screen of FIG. 5, after selecting the form to inquire, execute button 101
Press to start this program. For reference, FIG. 2 shows the numbers of the steps described below as much as possible.

First, in step S1, the schedule table 51H shown in FIG. 3 is searched using the reception shop number, the form ID, and the current time. As a result, step S2
Then, the task ID is acquired (calculated). Then, in step S3, one record is inserted into the inquiry reception management table 51C shown in FIG. 4 (entry: queuing). As shown in step S3, the record includes the reception number (serial number), the reception user ID, etc., the progress status code is set to "waiting for processing", and the processing start time is set to the current time. Also, the processing end time is "not yet".
Enter.

Next, FIG. 10 shows the situation inquiry (form) of FIG.
This is an operation started when the latest state button 102 is pressed on the screen. That is, this is an operation performed by the return management unit 51G when the user sends a result reply request. Step S11
Then, the inquiry reception management table 51C is searched to extract the matter in which the result reply request or the situation inquiry request is sent from the user side by the reception user ID, and then step S12.
Then, the result is displayed on the situation inquiry screen of the client terminals 11 and 21. However, only the inquiry processing registered by oneself is displayed on the screen, and the inquiry made by another person is not displayed.

Next, FIG. 11 shows an operation which is started when the edit button 103 is pressed on the situation inquiry (form) screen containing at least one completed matter as shown in FIG. This is also an operation performed by the return management unit 51G when the user sends a result reply request. The tabulation application software for creating a table, which is a form of a form, is started up, and the form inquiry result data 51F is expanded and set on the page. That is, in step S21, the form inquiry result file 51F
Is downloaded from the server computer 51 to the terminals 11 and 21. Next, in step S22, the application software for tabulating is started, and the corresponding record in the form inquiry result file 51F is updated by the server computer 5.
1 to the client computers 11 and 21.

On the other hand, FIG. 12 and FIG. 13 show the tasks performed by the execution management unit 51D operating in the background, asynchronously and asynchronously with the above-mentioned interaction between the Web server and the client computers 11 and 21. This is an execution process. FIG. 12 is a main flowchart of the task, and refers to the schedule table 51H and the inquiry reception management table 51C to extract the inquiry process to be executed.
In step S31, the current time has passed (processing start time + timer interval) and the status code is "execution".
(A task can be selectively switched to either "execution" or "stop": see the task monitoring button in the system monitoring task of FIG. 23, for example.) Extract the inquiry reception management record within the maximum number of retrieval cases . Then, in step S32, it is determined whether or not all the extracted records have been processed, and in step S33, the inquiry processing task is repeatedly executed for the maximum number of inquiry reception management records until all are processed.

FIG. 13 shows the detailed contents of the inquiry process in step S33 of FIG. That is, in step S41, the progress status code of the corresponding record in the inquiry reception management table 51C is rewritten to "being processed". Until then, the progress status code was "waiting for processing" (see step S3 in FIG. 9). In addition, the next step S4
In 3, the progress status code is rewritten to “complete”. Needless to say, the recording of these progress status codes is reflected in the column of processing status in FIGS. 6 and 7. Then, in step S42, the form inquiry result file 51F (data file to be passed to the tabulation application) is output, and then in step S43, the processing end time is updated to the current time (up to that time, the processing end time is shown in step S3 of FIG. 9). As described above, the progress status code is rewritten to “complete” as described above. The above operation is performed in step S44.
Then, it is repeatedly executed until it is determined that all extracted cases have been processed.

Next, the work related to data registration will be described. First, FIG. 14 shows a menu on the left side of the browser screen when the user accesses the server computer 51 with the client computers 11 and 21.
This is the screen for inquiring about the registered content that appears when you click on "Inquiry about registered content". The user inputs necessary items such as store number, subject, account number, data to be inquired, and the execute button 10
When 4 is clicked, the screen shifts to the registration content list screen shown in FIG. This allows the user to know what kind of data is registered.

Next, in FIG. 16, when the user clicks "Data Inquiry" in the data registration task in the menu on the left side of the browser screen when the user accesses the server computer 51 with the client computers 11 and 21. It is a screen for data inquiry that appears. As in the case of the form inquiry business, the user can enter the store number, subject, account number,
Enter the required items such as the data you want to inquire, and click the execute button
Click 05. At this time, it is possible to input a plurality of items. In the example shown in the figure, it is possible to input 10 items at a time, and 5 items out of them are to be collectively referred to as data.

When the execute button 105 is clicked, a data inquiry request is transmitted to the server computer 51, and the terminal side 11 or 21 shifts to the situation inquiry (data) screen shown in FIG. "Processing" in the processing status column
And "completion" are mixed. When the edit button 106 for the completed processing is clicked, as shown in FIG.
The application software starts and data (in this case,
A page displaying the transaction status 1) appears. To change / correct the registered contents, click the registration sheet creation button 107 on this page. Then, although not shown, a registration sheet dedicated to rewriting data appears, and the work for changing the registration content is performed on the sheet.

After that, the data registration screen of FIG. 19 is displayed, the latest state button 108 is pressed, and after confirming that there is no error in the work of changing the registered contents, the registration button 109 at the lower left of the screen is clicked. The registration request is entered in the registration reception management table 51B.

An example of specific control for realizing the above operation will be described with reference to FIGS. 20 to 22. First, the flowchart of FIG. 20 shows an operation that starts when the registration sheet creation button 107 of FIG. 18 is pressed.
At 51, registration data is created on the client computers 11 and 21. The flow chart of FIG. 21 corresponds to that of FIG.
It is an operation that is started by pressing the latest status button 108 of
In step S61, the registration reception management table 51B is searched to extract the registration request sent from the user side by the reception user ID. Then, in step S62, the result is the data of the client terminals 11 and 21. Display on the registration screen. The flowchart of FIG. 22 shows an operation that is started when the registration button 109 of FIG. 19 is pressed.
At 71, the registration data is transferred to the client computer 11,
21 to the server computer 51. And
In step S72, one record is inserted into the registration reception management table 51B (entry: queuing).
The record includes the reception number (serial number), the reception user ID, and the like, as in step S3 of the form inquiry work, the progress status code is “waiting for processing”, the processing start time is the current time,
"Not yet" is entered at the processing end time.

Next, in this data processing system,
System monitoring work performed by the system administrator of the head office by operating the management client computer 53, particularly registration /
Explain the inquiry status monitoring work. 23. In the menu on the left side of the screen of the system management computer 53, FIG.
This is a status monitoring screen that appears when the inquiry status monitoring button 111 is clicked. In the example in the figure, for the slip 3, individual statistical information is created every 60 minutes between 8:00 am and 8:00 pm, regarding the distribution of data registration and inquiry requests. The case is shown. And
When the status monitor button 111 is clicked again, FIG.
As shown in, the statistical result is displayed in a graph. In this case, 7 inquiries only from 8 am to 9 am,
From 9 am to 10 am, it can be seen that 3 inquiry requests are concentrated.

A flowchart of this operation is as shown in FIG. That is, in step S81,
The inquiry reception management table 5 using the date and time (eg, from 8:00 am to 8:00 pm of yesterday) and the form ID (eg, card 1, slip 1 etc.) of the aggregation target as search conditions.
The corresponding record is extracted from 1C and the registration reception management table 51B. Then, in step S82, the totaling result of the extracted record is input to the management computer 5 at each input time interval (for example, every 60 minutes).
Display on screen 3.

Based on this statistical information, the system administrator operates the management computer 53 to newly register the task or change the task attribute so that the task execution time is shortened. FIG. 26 is a task registration screen that appears when the task registration (new registration / attribute change) button is clicked in the menu on the left side of the system management computer 53. When the new registration button 112 on the upper right of this page is pressed, one task can be additionally registered as shown in step 91 of FIG. In that case, in the above example, a task corresponding to the inquiry request for the slip 3 may be added between 8:00 and 9:00 or 10:00. Alternatively, the attributes of each task can be changed by directly operating the list of FIG. In that case, for example, the maximum number of extracted tasks corresponding to the inquiry request for the slip 3 may be increased. In either case, as a result, the task execution time on the server 51 side is shortened, and as a result, the unnecessary waiting time on the client 11, 21 side after transmitting the processing request is shortened as much as possible, and as a result, the user's sense of stress is felt. Is reduced and work efficiency is improved.

When the client 11 or 21 requests to send back the processing result, if the task has already been completed and the processing result 51F is output, the processing result 51
While F is returned to the clients 11 and 21, the task is not completed yet and the processing result 51F is not completed, the status is "processing in progress" or "waiting for processing" as shown in FIG. Since the effect is reported to the clients 11 and 21, the user's stress and anxiety are reduced even while waiting for the reply of the result.

Further, the processing request acceptance 51A and the task execution 51D can be separated and individually operated, and the task 51E proceeds in the background where the user operates the client computers 11 and 21. . As a result, the user, after transmitting the processing request to the server computer 51, is not bound by the presence or absence of the result reply from the server computer 51 and the timing thereof, and the server computer 51 sends the processing request to the previously transmitted processing request. Even if the reply that the processing is completed has not arrived yet, after accepting the processing, it is possible to use the client computers 11 and 21 again to continuously send the next request to the server computer 51. Therefore, even if the processing on the server 51 side takes a long time and the reply of the result 51F is returned with a considerable delay in time, the user is still in the meantime.
There is no need to wait for people before 1 and 21, stress does not increase and work efficiency is reduced.

Further, the Web server of the server computer 51 is in charge of only functions having a comparatively light load, such as reception of processing requests and reply requests 51A and 51G from the clients 11 and 21, and execution of a heavy load task 51E. Is
Since an independent / dedicated, for example, database server 51D that is resident in the server computer 51 is made to perform this, http, which is a simple one-time communication protocol,
Since it is involved only in the operation of accepting a lightly loaded request between the client computers 11 and 21 and the server computer 51, the waiting time of the user can be short. Then, the requested processing tasks 51D and 51E are asynchronously executed in the background separated from the communication between computers by http.

Needless to say, the above-described embodiments can be variously modified without departing from the spirit of the present invention, and the page configuration on the screen shown in the drawings and each element The layout is just an example.

[0054]

As described above, according to the present invention,
It is possible to reduce unnecessary waiting time on the client side after transmitting the processing request as much as possible, thereby reducing the user's stress and improving work efficiency. INDUSTRIAL APPLICABILITY The present invention can be expected to be widely used for a data processing system such as an intranet in a company in which a client computer and a server computer are connected by a communication line, and further for general computer networks.

[Brief description of drawings]

FIG. 1 is an overall configuration diagram of a data processing system according to an embodiment of the present invention.

FIG. 2 is a block diagram of a main part of the system.

FIG. 3 is a task schedule table stored in a server computer of the system.

FIG. 4 is also an inquiry reception management table.

FIG. 5 is a form inquiry screen that appears on the screen of the client computer.

FIG. 6 is also a status inquiry screen.

FIG. 7 is also a status inquiry screen.

FIG. 8 is a screen in a state in which application software representing a form is activated.

FIG. 9 is a flowchart showing an example of a specific operation of the form inquiry work.

FIG. 10 is the same flowchart.

FIG. 11 is a flowchart of the same.

FIG. 12 is the same flowchart.

FIG. 13 is a flowchart of the same.

FIG. 14 is a registration content inquiry screen appearing on the screen of the client computer.

FIG. 15 is also a registration content list screen.

FIG. 16 is also a data inquiry screen.

FIG. 17 is also a status inquiry screen.

FIG. 18 is a screen showing a state in which application software representing data is activated.

FIG. 19 is also a data registration screen.

FIG. 20 is a flowchart showing an example of a specific operation of data registration work.

FIG. 21 is the same flowchart.

FIG. 22 is the same flowchart.

FIG. 23 is a registration / inquiry status monitoring screen appearing on the screen of the client computer.

FIG. 24 is a screen for displaying statistical information of registration / inquiry status as a graph.

FIG. 25 is a flowchart showing a specific example of a statistical operation of registration / inquiry status.

FIG. 26 is a task registration screen appearing on the screen of the client computer.

FIG. 27 is a flowchart showing a specific example of a task registration operation.

[Explanation of symbols]

11, 21 Client Computer 51 Server Computer 51A Reception Management Unit (Processing Request Receiving Means) 51B Registration Reception Management Table (Processing Request Storage Means) 51C Inquiry Reception Management Table (Processing Request Storage Means) 51D Execution Management Unit (Statistical Information Creation Means, Task execution means) 51E Update / inquiry module (task) 51F Form inquiry result file (processing result) 51G Return management unit (reply request acceptance means, reply means) 51H Task schedule table 52 Database 53 Management computer (task setting means) X the Internet

Claims (4)

[Claims] 1. A data processing system in which a server computer executes a task in response to a data processing request sent by a client computer and sends back the result to the client computer, the processing request receiving a data processing request from the client computer. Accepting means, statistical information creating means for creating statistical information of the processing request accepted by the accepting means, task executing means for similarly executing a task corresponding to the processing request accepted by the accepting means to the database, and Based on the statistical information created by the statistical information creating means, a task setting means for newly registering or changing the attribute of the task executed by the task executing means is provided so as to shorten the task execution time. And data processing system. 2. A reply request accepting means for accepting a reply request for a processing result from a client computer, and based on the reply request accepted by the accepting means, the processing result is output when the processing result is output, and the processing result is output. If not, a reply means for replying to the client computer to the effect that processing is in progress is provided.
The data processing system described in. 3. The processing request accumulating means for accumulating the processing request accepted by the processing request accepting means is provided, and the task executing means sequentially executes the processing requests accumulated by the accumulating means asynchronously with the acceptance operation of the accepting means. The data processing system according to claim 1, wherein the data processing system performs processing. 4. The data processing system according to claim 1, wherein the client computer and the server computer are connected via the Internet.