JP2005292872A - Database use system and database use program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To realize a database use system having a user interface of the same level as a dedicated application program while supposing a Web system. <P>SOLUTION: A front-end server 16 interposed between a DB server 14 and a client terminal 12 has: a means transmitting a retrieval condition transmitted from the client terminal 12 to the DB server 14 to request retrieval; a means storing a data list transmitted from the DB server 14 into a first buffer 40; a means taking out the data list inside the first buffer 40, and storing it into a cache 38: a means taking out the data list corresponding to one page having the number of lines according to a screen design from the cache 38, and storing it into a second buffer 41; a means filling the data list inside the second buffer 41 into a template reflecting the screen design to generate a screen-displaying Web file; and a means transmitting the Web file to the client terminal 12. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a database utilization technique, and in particular, a front-end server is installed between a client terminal and a database server, and registered data in the database server is used from a Web browser program of the client terminal via the front-end server. The present invention relates to a database utilization system and a database utilization program having a mechanism.

Database usage forms can be broadly divided into “reference systems” simply for the purpose of data search and display, and “registration systems” for correcting, adding, and deleting data.
FIG. 11 shows an example of a conventional usage form. A front-end server 72 having a Web server function and an AP (Application) server function is installed in a preceding stage of a DB (Database) server 70, and the Internet, an intranet, etc. A state in which the server 72 is connected to a large number of client terminals 76 via the communication network 74 is depicted.
Each client terminal 76 has a web browser program set up. When a search request for a specific database is transmitted to the front-end server 72 through the web browser, the front-end server 72 passes the search conditions to the DB server 70. Request a search process.
When the search result is transmitted from the DB server 70, the front end server 72 processes it into a Web file and transmits it to the client terminal 76.
As a result, the user can browse the search results on a general-purpose Web browser displayed on the display of the client terminal 76 (see “Table List” in Non-Patent Document 1).

On the other hand, for the task of changing data in the DB server 70, a client terminal 78 equipped with a dedicated application program optimized for registration processing is often used (see Non-Patent Document 2). .
This application program is generally coded in a fourth generation language such as Visual Basic (registered trademark) suitable for designing a so-called user interface, such as the arrangement of operation buttons and the configuration of input / display fields.
itBASE design screen sample [March 2, 2004 search] Internet URL: http://219.118.162.84/eaccess/servlet/eAccess?PAGE=00005&acountid=access&accessid=itbase&UPAGE=00002&FILENM=pageclip&FILENO=00002&FILEID=000061&CLIPTABLE=&FORMNO= page00002 & REPORTNO Sample screen of input processing [March 2, 2004 search] Internet URL: http://it.e-otsuka.com/ryutsu/images/food_sft1.gif

Originally, the use of the database was realized by installing a dedicated application program in the client terminal for both the reference system and the registration system. However, with the spread of the Web system centering on the Internet, the design can be referred to easily. As for the system, there is a history that the use of the web base has progressed quickly.
As database reference usage through the Web system expands, the inefficiencies of coding registration and reference programs in different languages and installing dedicated application programs on individual client terminals 78 At present, there is a growing demand for Web-based registration processing as well.

However, the Web browser program basically does not have the concept of “page”, so when a registration Web form is displayed on the display, the record list is paged by a predetermined number of lines. There is a problem that it makes it difficult for a user who is used to the operability of a dedicated application program with a fixed number of display lines to feel uncomfortable.
Actually, when the number of records is large, operation buttons such as “registration” and “deletion” arranged below the last line are displayed as is clear from the “form field specification” screen of Non-Patent Document 1. Therefore, it is necessary to scroll the screen many times, and the user feels great stress.
Of course, the problem of the user interface in this Web system occurs in the same way in the usage form of the reference system, but it will be recognized more prominently when performing registration work.

  In addition, since the server is responsible for managing the status and execution of client terminals, the number of connected client terminals will be enormous (for example, 1,000 or more) no matter how much memory is installed on the server side. Then, there arises a problem that the response is lowered or the operation becomes unstable.

  Furthermore, since the exchange of information between the client terminal and the server increases, the load on the network increases as the number of client terminals increases.

  The present invention has been devised to solve the above-mentioned problems, and the user interface on the client terminal side is the same as that of the dedicated application program on the assumption that registration-based processing is realized on a Web basis. It is an object of the present invention to provide a database utilization technique that can be maintained at the level of the above, and that can save memory resources and reduce the amount of communication on the server side.

  In order to achieve the above object, a database utilization system according to claim 1 is a database utilization system comprising a front-end server interposed between a database server and a client terminal, wherein the front-end server includes Means for transmitting a search condition transmitted from the client terminal to the database server and requesting a search; means for storing a data list of search results transmitted from the database server in the first buffer; and the first buffer. Means for taking out the data list from the cache and storing it in the cache; means for taking out the data list for one page having the number of lines corresponding to the screen design from the cache and storing it in the second buffer; Take out the data list in the buffer and fill it with a template that reflects the screen design. Means for generating a Web file for screen display and is characterized by having a means for transmitting the Web files to the client terminal.

  The database utilization system according to claim 2 is based on the system of claim 1, and further, when the front-end server transmits information indicating that the specific data in the display screen has been corrected from the client terminal In addition, when a means for modifying the corresponding data in the cache and information indicating that the data is added on the display screen are transmitted from the client terminal, the corresponding data is added to the data list in the cache. And means for recording data for specifying the deletion target in the cache when the information indicating that the specific data in the display screen is selected as the deletion target is transmitted from the client terminal, and updating the data from the client terminal. When a request is sent, the data in the cache is And means for outputting the Ffa, transmits the data stored in the first buffer to the database server, it is characterized by comprising a means for requesting to update the data.

The database utilization system according to claim 3 is based on the system according to claim 1 or 2, and further, when information indicating that the front-end server has closed the screen is transmitted from the client terminal, the screen is displayed. It is characterized by comprising means for deleting data related to the above-mentioned cache and each buffer.
As a premise for this, the client terminal side is provided with means for constantly monitoring input information from the input device and, when detecting an input operation for closing the screen, immediately transmitting information indicating that to the front-end server. It has been.

The database utilization system according to claim 4 is based on the system according to claims 1 to 3, and further, when the front end server does not perform an input operation for a predetermined time on the screen of the client terminal, Means for temporarily saving data related to the cache from the cache and each buffer to the hard disk and information indicating that the input operation has been resumed on the screen from the client terminal. And means for restoring data from the hard disk to the cache and each buffer.
As a premise, a function for monitoring the idle time of communication for each session ID is provided in the front-end server.

  The database use program according to claim 5 is a database use program applied to a front-end server interposed between a database server and a client terminal, wherein the search is transmitted from the client terminal to the front-end server. Means for sending a condition to the database server to request a search; means for storing a data list of search results sent from the database server in a first buffer; and taking out the data list in the first buffer and storing it in a cache Means for taking out a data list for one page having the number of lines according to the screen design from the cache, storing it in the second buffer, taking out the data list in the second buffer, and reflecting the screen design Web file for screen display by filling the template Resulting unit is characterized in that to function as means for transmitting the Web files to the client terminal.

  The database utilization program according to claim 6 is based on the program of claim 5, and further, when information indicating that the specific data in the display screen has been corrected is transmitted from the client terminal to the front-end server. Means for correcting the corresponding data in the cache, and means for adding data corresponding to the data list in the cache when information indicating that the data has been added in the display screen is transmitted from the client terminal. When data indicating that specific data in the display screen has been selected for deletion is sent from the client terminal, means for recording data for specifying the deletion target in the cache, and a data update request is sent from the client terminal Data in the cache is Means for outputting the file, and transmits the data stored in the first buffer to the database server, is characterized in that to function as means for requesting the updating of the data.

The database utilization program according to claim 7 is based on the program according to claim 5 or 6, and when the information indicating that the screen is closed is transmitted from the client terminal to the front-end server, It is characterized by functioning as a means for deleting data related to the above-mentioned cache and each buffer.
As a premise, the client terminal side constantly monitors the input information from the input device, and when detecting an input operation that closes the screen, the client terminal as a means for immediately transmitting information indicating that to the front-end server. A program has been set up to make the terminal work.

The database utilization program according to claim 8 is based on the program according to claims 5 to 7, and further, when the front-end server has not been operated for a predetermined time on the screen of the client terminal, Means for temporarily saving the data related to the cache from the cache and each buffer to the hard disk, and the data related to the screen when the information indicating that the input operation has been resumed on the screen is transmitted from the client terminal. Is functioned as a means for restoring from the hard disk to the cache and each buffer.
As this premise, this database utilization program has a function of monitoring idle time of communication in session ID units.

In the database utilization system according to claim 1 and the database utilization program according to claim 5, the data list delivered from the database server is stored in the cache, and is managed as a page for each number of lines defined by the screen design. In addition, since the data list for one page is transmitted to the client terminal as a Web file, it is possible to display a list of data in units of pages of a predetermined number of lines on the Web browser of the client terminal.
Further, since data is transmitted in units of one page from the front end server to the client terminal in this way and the entire data list is not transmitted at a time as in the prior art, the corresponding amount between the front end server and the client terminal. The amount of data communication can be reduced.

  In the database utilization system according to claim 2 and the database utilization program according to claim 6, correction, addition, and deletion selection data are transmitted from the client terminal in units of displayed screens (in units of one page). Since it is not necessary to send back the entire data list to the front-end server each time correction, addition, or deletion is selected, the amount of data communication between the front-end server and the client terminal can be reduced.

  According to the database utilization system of claim 3 and the database utilization program of claim 7, when the database utilization screen is closed on the client terminal, the memory space on the front-end server side can be immediately released, Effective use of resources becomes possible.

  According to the database utilization system of claim 4 and the database utilization program of claim 8, when the work on the client terminal is interrupted for a predetermined time, it is immediately unnecessary from the memory space on the front end server side to the hard disk. Data can be saved and resources can be used effectively. In addition, when the work is resumed, the original state can be restored without delay.

FIG. 1 is a conceptual diagram showing the overall configuration of a database utilization system 10 according to the present invention, and a front-end server 16 having a Web server function and an AP server function between a large number of client terminals 12 and a DB server 14. Is arranged.
Each client terminal 12 and the front-end server 16 are connected via a communication network 18 such as the Internet or an intranet.
The front-end server 16 and the DB server 14 are also network-connected via a LAN.
Each client terminal 12 is set up with a general-purpose web browser program.

FIG. 2 is a block diagram showing functional configurations of the client terminal 12 and the front-end server 16.
First, the client terminal 12 includes a computer such as a PC to which an input device 20 such as a mouse or a keyboard and a display 22 are connected, and includes a status notification unit 24, a web page display unit 26, and a processing request unit 28. ing.
Here, the Web page display unit 26 and the processing request unit 28 are realized by the CPU of the client terminal 12 executing necessary processing according to a general-purpose Web browser program or the like. The status notification unit 24 is realized by the CPU executing necessary processing according to a dedicated program (JavaScript) and a web browser program distributed from the front-end server 16.

The front-end server 16 includes a control unit 30, a business processing unit 32, a screen generation unit 34, a cache 38, a first buffer 40, a second buffer 41, a memory management unit 42, and a save area 44. And.
Although details will be described later, when the user accesses the front-end server 16 from the client terminal 12 and selects one service from the service menu displayed on the Web browser, the server 16 side uses the application program X1 dedicated to the service. Is started, and the CPU of the server 16 executes necessary processing in accordance with this, whereby the control unit 30, the business processing unit 32, and the screen generation unit 34 are realized.
When the user selects another service, the other application programs X2, X3,... Are activated separately, and the control unit 30, the business processing unit 32, and the screen generation unit 34 optimized for the service. Will appear in parallel.
On the other hand, the memory management unit 42 is realized by middleware in the front-end server 16 that is independent of the application programs for each service.
The cache 38, the first buffer 40, and the second buffer 41 are secured in the memory space of the front-end server 16, and the save area 44 is provided in the hard disk of the server 16.

Hereinafter, the processing procedure in the system 10 will be described with reference to the flowcharts of FIGS.
First, when the user accesses the front-end server 16 from the client terminal 12 and clears the authentication step that involves inputting the ID and password, a web file (Html file or the like) for menu display is transmitted from the server 16 (S10), A menu screen (not shown) of services available to the user is displayed on the Web browser (S11).
When the user selects one service from this menu, for example, “master maintenance / color deletion”, the processing request unit 28 of the client terminal 12 sends a distribution request for the usage screen related to the service to the front-end server 16. (S12).
In response to this, in the front-end server 16, the application program X1 corresponding to the service is started (S13), a dedicated control unit 30, a business processing unit 32, and a screen generation unit 34 are formed, and in the memory space. A cache 38, a first buffer 40, and a second buffer 41 are set.

  Next, the control unit 30 instructs the screen generation unit 34 to transmit the corresponding Web file, and the screen generation unit 34 generates a Web file for the initial screen of the service according to a pre-designed screen template, and the client It transmits to the terminal 12 (S14).

As a result, the initial screen 46 of the master maintenance / color deletion service is displayed on the browser of the client terminal 12 as shown in FIG. 5 (S15).
On the other hand, when the user inputs a specific code number, for example, “01” in the color type code input field 47 and clicks the search button 48, the processing request unit 28 of the client terminal 12 sends the color type to the front-end server 16. A search request for the database with code = 01 is transmitted (S16).
Receiving this, the control unit 30 sets the request in the first buffer 40 (S17).

In response to this, the task processing unit 32 retrieves the search condition (color type code = 01) from the first buffer 40 and requests the DB server 14 to perform the search process (S18).
Then, when the list of data stored in the database of color type code = 01 is transmitted from the DB server 14, the business processing unit 32 sets this in the first buffer 40 (S19).

Next, the control unit 30 takes out the data in the first buffer 40, copies it to the cache 38 (S20), and stores a part (one page) of the data in the second buffer 41 (S22).
In response to this, the screen generation unit 34 extracts a data list from the second buffer 41, fills each data in the template for the service, generates a search result display Web file, and transmits it to the client terminal 12 ( S23).
As a result, as shown in FIG. 6, the registration data of color type code = 01 is displayed in a list on the Web browser of the client terminal 12 (S24).

Of the 101 registered data with the color type code = 01, only 15 data are displayed on the screen 46.
When referring to other data, the user clicks the down scroll button 49 or presses the “Page Down” key on the keyboard.
As a result, a data distribution request for the second page is transmitted from the processing request unit 28 of the client terminal 12 to the front-end server 16 (S25).
Receiving this, the control unit 30 takes out the next 15 pieces of data stored in the cache 38 and stores them in the second buffer 41 (S26).
The screen generation unit 34 fills the template with these data, generates a Web file with the page notation updated, and transmits it to the client terminal 12 (S27).
As a result, although not shown, the display screen for the second page is displayed on the Web browser (S28).

Next, when the user checks the check box 50 of arbitrary data (S29) and generates a page scrolling event, the status notification unit 24 of the client terminal 12 sends a notification for the checked line to the front end server 16. (S30).
Receiving this, the control unit 30 adds checked information to the data of the corresponding line in the currently displayed page among the data stored in the cache 38 (S31).
The control unit 30 can determine the page currently displayed on the client terminal 12 from the number of pieces of data stored in the cache 38 and the number of lines per page.
When the user requests to display the next page, the Web file in which the data of the third page is embedded is transmitted from the screen generation unit 34 to the client terminal 12 and displayed on the Web browser.
In this case, the check box 50 of each data is not checked yet. Here, when the user checks an arbitrary record, a checked notification specifying a line is transmitted from the status notification unit 24 of the client terminal 12 to the front-end server 16 as described above, and the control unit 30 Information indicating that the corresponding data in the cache 38 has been selected as a deletion target is added.
When the user clicks the up scroll button 51 to request redisplay of the second page, the control unit 30 passes the 15 pages of data for the second page to the screen generation unit 34, and the display screen of the second page is displayed. It is transmitted to the client terminal 12.
In this case, as a matter of course, a check mark indicating that the user has already checked is reproduced in the data checked by the user first.

As described above, when the user completes the check for the data to be deleted among the 101 data, the user clicks the delete button 52.
As a result, a check data deletion request is transmitted from the processing request unit 28 of the client terminal 12 to the front-end server 16 (S32).
Receiving this, the control unit 30 takes out the data list in the cache 38 and data for specifying the deletion target, and sets them in the first buffer 40 (S34).

Next, the business processing unit 32 is activated, takes out the data list set in the first buffer 40 and data for specifying the deletion target, and requests the DB server 14 to delete (S37).
When the deletion process in the DB server 14 is completed, the job processing unit 32 receives all the deleted data from the DB server 14 and sets it in the first buffer 40 (S38).
Next, the control unit 30 is activated to copy all data in the first buffer 40 to the cache 38 (S40) and store data for one page in the second buffer 41 (S41).
The screen generation unit 34 fills this data into a template to generate a Web file, and transmits it to the client terminal 12 (S42).
As a result, the remaining data excluding the deleted data is displayed on a page basis on the Web browser of the client terminal 12 (S43).

As described above, the control unit 30 stores all the data in the first buffer 40 in the cache 38 and manages them in units of pages having the number of lines required by the screen design. Since the data list for one page is sequentially transmitted via the second buffer 41 and the screen generation unit 34, the data corresponding to the determined number of lines is always displayed on the Web browser. As shown, the positions of the search button 48 and the delete button 52 are also fixed on the screen 46.
As a result, an easy-to-view user interface similar to the case where a screen is generated by a conventional dedicated application program can be realized.

In the case of this system 10, a unique screen design (screen template) is designed for each service, and the operations of the control unit 30 and the screen generation unit 34 need to be changed accordingly.
For example, when a 20-line list display field is provided for a deletion screen of a certain database, the control unit 30 and the screen generation unit 34 treat 20 data as one page.
In addition, as a method of selecting the deletion target, if the screen design of the method of checking the record to be deleted instead of checking the record to be deleted as described above is adopted, the control unit 30 is not checked. Data indicating that the data has been selected for deletion is recorded in the cache 38.

In addition, when coding the control unit 30 and the screen generation unit 34 according to the screen design, the basic operation part common to each screen is created in advance as an application base, and the number of lines per page and It is only necessary to rewrite the data selection method and the meaning when it is selected (whether the checked item is deleted or the unchecked item is deleted).
In particular, when coding each part in the Java (registered trademark) language, it is possible to easily use the code of the application base part by using the inheritance mechanism, so that the design change of the screen design is facilitated.

By the way, as shown in FIG. 1, a plurality of client terminals 12 are connected to the front-end server 16, and a plurality of service use screens can be started simultaneously on each client terminal 12. Regardless of how much of the 16 on-board memories are secured, there is a concern about resource shortages.
Therefore, this system 10 has a function for realizing efficient use of the memory.

FIG. 7 illustrates an image of using the memory space in the front-end server 16 and represents the memory space in which the session information in the figure is reserved for each client terminal 12. Each session information is identified by a session ID.
Further, the upper circle mark α in one session information corresponds to the session ID, and the middle circle β corresponds to each service.
Further, a lower circle γ indicates a memory area necessary for individual processing included in each service.

The memory management procedure in the system 10 will be described below with reference to the flowchart of FIG.
First, when the user closes a specific service use screen, the information is transmitted from the status notification unit 24 of the client terminal 12 to the front-end server 16.
In response to this, the memory management unit 42 (S50), as shown in FIG. 7B, data relating to the corresponding service use screen from the memory (cache 38, first buffer 40, and second buffer 41). And the memory space (the portion indicated by the dotted line in the figure) is released (S51).

  Conventionally, even if a specific service usage screen is closed on the client terminal 12, the fact cannot be recognized on the server 16 side, and resources are wasted until the session itself is terminated by logoff. In the system 10, information indicating that the screen is closed is transmitted to the front-end server 16 without delay by the status notification unit 24 of the client terminal 12, so that unnecessary data can be immediately deleted from the memory space. .

In addition, the memory management unit 42 of the front-end server 16 constantly monitors the communication state with the client terminal 12, and the user does not perform any operation on any service usage screen for a predetermined time (for example, 30 minutes). When it is detected (S52), as shown in FIG. 7C, the memory management unit 42 moves all the data on the memory space allocated to the client terminal 12 to the save area 44 on the hard disk and releases the memory space. (S53).
Thereafter, when the user resumes the operation on the service use screen and communication occurs with the client terminal 12 (S54), the memory management unit 42 moves the data related to the client terminal 12 from the save area 44 to the memory. 7 (a) or (b) is restored (S55).

Conventionally, there is a concept of timeout, and when there is no communication with the client terminal 12 for a certain period of time, the data related to the client terminal 12 has been deleted from the memory space, but the user resumes the work. In this case, it is necessary to start again from login, and there is a problem that the progress of the work is not reproduced.
On the other hand, in the case of this system 10, since data is temporarily moved to the save area 44 in the hard disk as described above, the progress is immediately restored when the work is resumed. It is possible to avoid a wasteful occupation state of resources while ensuring the performance.

  The above monitoring operation by the memory management unit 42 is continued until the session with the client terminal 12 ends (S56) and all data is erased from the memory space allocated to the client terminal 12 (S57).

In the above, the “master maintenance / color deletion” requesting the DB server 14 to delete specific data is exemplified as an example of the service, but the client terminal 12 may also request the DB server 14 to add or modify data. Of course it is possible.
For example, when the user selects “master maintenance / color registration” from the service menu, the process request unit 28 of the client terminal 12 transmits a use screen distribution request for the service to the front-end server 16.
In response to this, the front-end server 16 starts an application program corresponding to the service, forms a dedicated control unit 30, a business processing unit 32, and a screen generation unit 34. One buffer 40 and a second buffer 41 are set.

Next, the control unit 30 instructs the screen generation unit 34 to transmit the corresponding Web file, and the screen generation unit 34 generates a Web file for the initial screen of the service according to a pre-designed screen template, and the client Transmit to terminal 12.
As a result, the master maintenance / color registration service initial screen 53 is displayed on the browser of the client terminal 12 as shown in FIG.
On the other hand, when the user inputs a specific code number, for example, “01” in the color type code input field 54 and clicks the search button 55, the processing request unit 28 of the client terminal 12 sends the color type to the front-end server 16. A search request for the database with code = 01 is transmitted.
Receiving this, the control unit 30 sets the request in the first buffer 40.

In response to this, the task processing unit 32 retrieves the search condition (color type code = 01) from the first buffer 40 and requests the DB server 14 to perform a search process.
When the record stored in the database with the color type code = 01 is transmitted from the DB server 14, the task processing unit 32 sets this in the first buffer 40.

Next, the control unit 30 takes out the data in the first buffer 40, copies it to the cache 38, and writes a part of the data (one page = 15 lines) to the second buffer 41.
On the other hand, the screen generation unit 34 generates a search result display Web file by filling each template in the service template and transmits it to the client terminal 12.
As a result, on the Web browser of the client terminal 12, as shown in FIG. 10, a list of registered data with color type code = 01 is displayed.

On the other hand, when the user corrects arbitrary data and generates a page scroll event, the status notification unit 24 of the client terminal 12 sends the corrected data and the notification indicating the correction content to the front end server 16. .
Receiving this, the control unit 30 makes a corresponding correction to the data of the corresponding line on the currently displayed page among the data stored in the cache 38.
When the user clicks the down scroll button 56 to request the display of the next page, the web file in which the data of the second page is embedded is transmitted from the screen generation unit 34 to the client terminal 12 and displayed on the web browser. Is displayed.
Here, when the user clicks the up scroll button 57 to request redisplay of the first page, the control unit 30 passes 15 pieces of data of the first page to the second buffer 41, and the screen generation unit 34. The display screen of the first page is transmitted to the client terminal 12.
As a result, the data previously corrected by the user is reproduced on the screen.

A user who desires additional registration of data newly inputs a color code, a color kanji name, and a color kana name in a blank input field provided on the last page (not shown).
Also in this case, when the page scroll event is generated, new input data specifying the line is transmitted from the state notification unit 24 to the front-end server 16, and the control unit 30 adds the data to the data list of the corresponding page in the cache 38. Added.

As described above, the user who has completed the necessary corrections or additions clicks the update button 58 in the screen.
As a result, a data update request is transmitted from the processing request unit 28 of the client terminal 12 to the front end server 16.
Receiving this, the control unit 30 takes out the corrected or added data list stored in the cache 38 and sets it in the first buffer 40.
Next, the business processing unit 32 is activated, takes out the data list set in the first buffer 40, and requests the DB server 14 to update.

It is a conceptual diagram which shows the whole structure of the database utilization system which concerns on this invention. It is a block diagram which shows the function structure of a client terminal and a front end server. It is a flowchart which shows the process sequence of this system. It is a flowchart which shows the process sequence of this system. It is a layout figure which shows the initial screen of a master maintenance and a color deletion service. It is a layout figure which shows the data list screen of a master maintenance and a color deletion service. It is a conceptual diagram which shows the utilization image of the memory space in a front end server. It is a flowchart which shows the procedure of the memory management in this system. It is a layout figure which shows the initial screen of a master maintenance and color registration service. It is a layout figure which shows the data list screen of a master maintenance and color registration service. It is a conceptual diagram which shows an example of the utilization form of the conventional database.

Explanation of symbols

10 Database usage system
12 Client terminal
14 DB server
16 Front-end server
18 Communication network
20 Input device
22 display
24 Status notification section
26 Web page display area
28 A processing request unit 28 is provided.
30 Control unit
32 Business Processing Department
34 Screen generator
38 cache
40 First buffer
41 Second buffer
42 Memory management
44 Evacuation area
46 Master Maintenance / Color Deletion Service Initial Screen
47 Color type code input field
48 Search button
49 Down scroll button
50 check box
51 Up scroll button
52 Delete button
53 Master Maintenance / Color Registration Service Initial Screen 53
54 Color type code input field
55 Search button
56 Scroll button
57 Up scroll button
58 Refresh button
X1, X2, X3 application program

Claims (8)

A database utilization system comprising a front-end server interposed between a database server and a client terminal,
The front-end server
Means for sending a search condition sent from the client terminal to the database server and requesting a search;
Means for storing a data list of search results transmitted from the database server in a first buffer;
Means for retrieving the data list in the one buffer and storing it in the cache;
Means for taking out a data list for one page having the number of lines according to the screen design from the cache and storing it in a second buffer;
Means for taking out a data list in the second buffer, filling a template reflecting the screen design, and generating a Web file for screen display;
Means for sending this web file to the client terminal;
A database utilization system characterized by comprising: The front-end server
Means for modifying the corresponding data in the cache when information indicating that the specific data in the display screen has been modified is transmitted from the client terminal;
Means for adding corresponding data to the data list in the cache when information indicating that data has been added in the display screen is transmitted from the client terminal;
Means for recording data specifying the deletion target in the cache when information indicating that the specific data in the display screen is selected as the deletion target is transmitted from the client terminal;
Means for outputting the data in the cache to the first buffer when a data update request is transmitted from the client terminal;
Means for sending the data stored in the first buffer to the database server and requesting an update of the data;
The database utilization system according to claim 1, further comprising:   The front-end server includes means for deleting data related to the screen from the cache and each buffer when information indicating that the screen is closed is transmitted from the client terminal. Item 3. The database utilization system according to item 1 or 2. The front-end server
Means for temporarily saving data related to the screen from the cache and each buffer to the hard disk when an input operation is not performed on the screen of the client terminal for a predetermined time;
Means for restoring data related to the screen from the hard disk to the cache and each buffer when information indicating that the input operation has been resumed on the screen is transmitted from the client terminal;
The database utilization system according to any one of claims 1 to 3, further comprising: A database utilization program applied to a front-end server interposed between a database server and a client terminal,
The above front-end server
Means for sending a search condition sent from a client terminal to a database server and requesting a search;
Means for storing a data list of search results transmitted from the database server in a first buffer;
Means for retrieving the data list in the first buffer and storing it in a cache;
Means for taking out a data list for one page having the number of lines according to the screen design from the cache and storing it in a second buffer;
Means for taking out the data list in the second buffer and filling it into a template reflecting the screen design to generate a Web file for screen display;
Means to send this web file to the client terminal,
Database utilization program characterized by functioning as The above front-end server
Means for correcting the corresponding data in the cache when information indicating that the specific data in the display screen has been corrected is transmitted from the client terminal;
Means for adding corresponding data to the data list in the cache when information indicating that data was added in the display screen is transmitted from the client terminal;
Means for recording data for specifying the deletion target in the cache when information indicating that the specific data in the display screen is selected as the deletion target is transmitted from the client terminal;
Means for outputting data in the cache to the first buffer when a data update request is transmitted from the client terminal;
Means for sending the data stored in the first buffer to the database server and requesting an update of the data;
The database utilization program according to claim 5, wherein the database utilization program is made to function as:   When the information indicating that the screen is closed is transmitted from the client terminal, the front-end server functions as means for deleting data related to the screen from the cache and each buffer. Item 7. The database utilization program according to item 5 or 6. The above front-end server
Means for temporarily saving data related to the screen from the cache and each buffer to the hard disk when an input operation is not performed on the screen of the client terminal for a predetermined time;
Means for restoring data related to the screen from the hard disk to the cache and each buffer when information indicating that the input operation has been resumed on the screen is transmitted from the client terminal;
The database utilization program according to any one of claims 5 to 7, wherein

Images