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

Abstract

<P>PROBLEM TO BE SOLVED: To provide a database use system that has a user interface on the same level as a dedicated application program despite assumed application to a Web system. <P>SOLUTION: In the database use system 10, a front end server 16 interposed between a DB server 14 and a client terminal 12 comprises a means for storing a list of records sent from the DB server 14 in a buffer 42, a means for sorting data forming the records in a matrix according to array rules specified by a screen design to generate a data list with data belonging to a plurality of records arrayed in every row, a means for storing the list in a first cache 38, a means for fetching one page of the data list having rows specified by the screen design from the first cache 38 to a second cache 40, a means for flowing the page in a template reflecting the screen design to generate a screen display Web file, and a means for sending the 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. 12 shows an example of a conventional usage form. A front-end server 82 having a Web server function and an AP (Application) server function is installed in the preceding stage of a DB (Database) server 80, and the Internet, an intranet, etc. A state in which the server 82 is connected to a large number of client terminals 86 via the communication network 84 is depicted.
Each client terminal 86 has a web browser program set up. When a search request for a specific database is transmitted to the front-end server 82 through the web browser, the front-end server 82 passes the search condition to the DB server 80, Request a search process.
Then, when the search result is transmitted from the DB server 80, the front end server 82 processes it into a Web file and transmits it to the client terminal 86.
As a result, the user can browse data on a general-purpose Web browser displayed on the display of the client terminal 86 (see “Table List” in Non-Patent Document 1).

On the other hand, for the task of changing data in the DB server 80, a client terminal 88 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 [Search June 7, 2004] 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 [Search June 7, 2004] 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 88 are becoming inefficient. At present, there is a growing demand for Web-based registration processing as well.

However, general-purpose web browser programs basically do not have the concept of “page”, so when a registration form web form is displayed on a display, a list of records is displayed with a predetermined number of lines. There is a problem that it is difficult to turn the page, and the user who is used to the operability of the dedicated application program with a fixed number of display lines is made 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 perform vertical scrolling of the screen many times, and the user feels great stress.
In addition, it may be desirable to increase the amount of data displayed on one page by arranging data related to multiple records in one row in order to improve the data listing. It was difficult to realize this, and there was no choice but to display the records side by side in the vertical direction.
Of course, such a user interface problem in the Web system occurs in the same manner in the reference system, but it will be recognized more prominently when performing registration work.

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.
In particular, when a record stored in the DB server has many data items, it is possible to display only a part of the data on the client terminal by using a technique called hidden. However, even if it is non-displayed data, it is assumed that the data is reciprocated between the client terminal and the server, resulting in an increase in the amount of data communication.

  The present invention has been devised to solve the above-described problems, and it is assumed that a reference system and a registration system process are realized on a Web basis, but a user interface on the client terminal side is used as a dedicated application. An object of the present invention is to provide a database utilization technique that can be increased to the same level as that of a program and that can reduce the amount of data communication between a server and a client terminal.

  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 A function that stores a list of records transmitted from the database server in a buffer and at least a part of the data constituting the record is distributed in a matrix form according to an array rule defined by the screen design, and belongs to a plurality of records in one line A function for converting to a data list in which data is arranged, a function for storing this data list in the first cache, and a data list for one page having the number of lines defined by the screen design are extracted from the first cache. , The function of storing in the second cache, and the second cache The data list is taken out and filled in a template reflecting the screen design to generate a Web file for screen display, the function to send this Web file to the client terminal, and the line on the screen being displayed from the client terminal Alternatively, when a page scroll event is transmitted, a function of retrieving a data list corresponding to each line to be displayed on the screen after scrolling from the first cache and storing the data list in the second cache; It is characterized in that it has a function of retrieving a data list in the cache, filling the template, generating a Web file for screen display after scrolling, and a function of transmitting the Web file to a client terminal.

  The database utilization system described in 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 screen has been corrected from the client terminal. When a function for correcting the corresponding data in the first cache and information indicating that the data has been added from the client terminal are transmitted to the data list in the first cache. A function of adding corresponding data, and a function of converting a data list in the first cache into a data list in which data is arranged in a row in units of records when a data update request is transmitted from a client terminal; The function to store this data list in the buffer and the data list in this buffer Sent to over database server is characterized by comprising a function to request the update of data.

  The database utilization system according to claim 3 is a database utilization system including a front-end server interposed between a database server and a client terminal, wherein the front-end server transmits a record transmitted from the database server. A function for storing a list of data in a buffer, a function for extracting data or a combination of data related to a data item that is required to be displayed on the screen design from the data constituting the record, and a combination of the data or data A function for storing a data list consisting of: in the first cache; a function for taking out a data list for one page having the number of lines specified by the screen design from the first cache and storing it in the second cache; 2 The data list in the cache was taken out and the screen design was reflected. A function to generate a web file for screen display by filling a template, a function to send this web file to the client terminal, and a line or page scroll event on the screen being displayed from the client terminal A function of taking out a data list corresponding to each line to be displayed on the screen after scrolling from the first cache, storing the data list in the second cache, and taking out the data list in the second cache; And a function for generating a Web file for screen display after scrolling and a function for transmitting the Web file to a client terminal.

  The database utilization system described in claim 4 is based on the system of claim 3, and further, when the front-end server receives information indicating that the specific data in the screen has been corrected from the client terminal. When a function for correcting the corresponding data in the first cache and information indicating that the data has been added from the client terminal are transmitted to the data list in the first cache. A function for adding corresponding data, a function for supplementing a missing data item to the data list in the first cache when a data update request is transmitted from the client terminal, and The function to store in the buffer and the data list in this buffer are sent to the database server It is characterized by having a function to request the update of data.

  The database utilization system according to claim 5 is a database utilization system including a front-end server interposed between a database server and a client terminal, wherein the front-end server transmits a record transmitted from the database server. A function for storing a list of data in a buffer, a function for converting at least a part of data constituting the record into a general-purpose data type, and a function for storing a data list composed of the converted data in a first cache And taking out the data list for one page having the number of lines specified by the screen design from the first cache, storing it in the second cache, and taking out the data list in the second cache, Function to generate a web file for screen display by filling the reflected template When the web file is transmitted to the client terminal and a scroll event of a line or page on the currently displayed screen is transmitted from the client terminal, it should be displayed on the screen after the scroll from the first cache. A function for retrieving the data list corresponding to each line and storing it in the second cache, and a function for retrieving the data list in the second cache, filling the template, and generating a Web file for screen display after scrolling And a function of transmitting the Web file to the client terminal.

  The database utilization system according to claim 6 is based on the system according to claim 5, and further, when the front-end server transmits information indicating that the specific data in the screen has been modified from the client terminal. When a function for correcting the corresponding data in the first cache and information indicating that the data has been added from the client terminal are transmitted to the data list in the first cache. A function to add corresponding data and when a data update request is sent from the client terminal, each data constituting the data list in the first cache is converted to a data type specific to each data item. A function to store the data list of the converted data in a buffer, Transmits the data list in the buffer to the database server, is characterized by comprising a function to request the update of data.

The database utilization system according to claim 7 is a database utilization system comprising a front-end server interposed between a database server and a client terminal, wherein the front-end server transmits a record transmitted from the database server. A function for storing a list of data in a buffer, a function for adding a check box to at least a part of data constituting the record, and a function for storing a list of data to which the check box is added in a first cache And taking out the data list for one page having the number of lines specified by the screen design from the first cache, storing it in the second cache, and taking out the data list in the second cache, Fill the reflected template into a web file for screen display The first cache when information indicating that a check has been input for specific data on the screen being displayed is transmitted from the client terminal. If the function for recording the check input information for the corresponding data in the screen and the scroll event of the line or page on the screen being displayed from the client terminal are transmitted from the first cache after the scroll A data list corresponding to each line to be displayed on the screen is taken out and stored in the second cache, and a data list in the second cache is taken out, filled in the template, and used for screen display after scrolling. A function to generate a Web file and a function to send this Web file to the client terminal It is characterized in that was example.
The “check box” is a concept that widely includes GUI parts for selecting data on the screen, and includes a radio button and the like in addition to a check box in a narrow sense (the same applies hereinafter).

  The database utilization system described in claim 8 is based on the system of claim 7, and further, when the front-end server transmits a data deletion request from a client terminal, the data list in the first cache is stored. Among them, it is characterized by having a function of extracting data that has been checked in, a function of removing a check box from the data, and a function of sending the data to the database server and requesting the deletion.

  The database utilization system according to claim 9 is based on the system according to claim 7, and further, when the front-end server transmits a data deletion request from the client terminal, the data list in the first cache is stored. It is characterized by having a function of extracting data for which no check is input, and a function of transmitting the data to the database server and requesting the deletion.

  The database use program according to claim 10 is a database use program applied to a front-end server interposed between a database server and a client terminal, wherein the front-end server is transmitted from the database server. Means to store the list of data in a buffer, at least a part of the data constituting the record is distributed in a matrix form according to the array rules specified by the screen design, and converted into a data list in which data belonging to multiple records is arranged in one line Means for storing the data list in the first cache, means for extracting a data list for one page having the number of lines defined by the screen design from the first cache, and storing the data list in the second cache; Retrieve data list in 2 cache A means of generating a Web file for screen display by filling a template reflecting the screen design, a means of sending this Web file to the client terminal, and a line or page scroll event on the currently displayed screen is sent from the client terminal The data list corresponding to each line to be displayed on the screen after scrolling is taken out from the first cache, the means for storing in the second cache, the data list in the second cache is taken out, It is characterized by functioning as means for generating a Web file for screen display after scrolling by filling the template, and means for transmitting the Web file to a client terminal.

  The database utilization program according to claim 11 is based on the program of claim 10, and further when the information indicating that the specific data in the screen has been corrected is transmitted from the client terminal to the front-end server. , Means for correcting the corresponding data in the first cache, and corresponding to the data list in the first cache when information indicating that data has been added in the screen is transmitted from the client terminal Means for adding data, means for converting the data list in the first cache into a data list in which data is arranged in a row in units of records when a data update request is transmitted from the client terminal, and this data Means to store the list in a buffer, the data list in this buffer Sent to over database server, is characterized in that to function as means for requesting the updating of the data.

  The database use program according to claim 12 is a database use program applied to a front-end server interposed between a database server and a client terminal, wherein the front-end server is transmitted from the database server. Means for storing a list of data in a buffer, means for extracting data or a combination of data relating to a data item that is required to be displayed on the screen design from the data constituting the record, and the data or a combination of data Means for storing the data list in the first cache; means for taking out the data list for one page having the number of lines defined by the screen design from the first cache and storing it in the second cache; and in the second cache Data list was taken out and the screen design was reflected When a web page file is generated by filling a template, a web file is sent to the client terminal, and a line or page scroll event on the screen being displayed is sent from the client terminal. Means for taking out a data list corresponding to each line to be displayed on the screen after scrolling from the first cache, storing the data list in the second cache, taking out the data list in the second cache, and filling the template It is characterized by functioning as means for generating a Web file for screen display after scrolling, and means for transmitting the Web file to a client terminal.

  The database utilization program according to claim 13 is based on the program of claim 12, and further, when information indicating that the specific data in the screen has been corrected is transmitted from the client terminal to the front-end server. , Means for correcting the corresponding data in the first cache, and corresponding to the data list in the first cache when information indicating that data has been added in the screen is transmitted from the client terminal Means for adding data, means for supplementing missing data items to the data list in the first cache when a data update request is sent from the client terminal, and storing this data list in a buffer Means to send the data list in this buffer to the database server It is characterized in that to function as means for requesting the updating of the data.

  The database use program according to claim 14 is a database use program applied to a front-end server interposed between a database server and a client terminal, wherein the front-end server is transmitted from the database server. Means for storing the list of data in a buffer, means for converting at least a part of data constituting the record into a general-purpose data type, means for storing a data list comprising the converted data in a first cache, A data list for one page having the number of lines specified by the screen design is taken out from one cache, a means for storing in the second cache, a data list in the second cache is taken out, and a template reflecting the screen design is taken. A means to fill and generate a web file for screen display Means for transmitting this Web file to the client terminal, and when a line or page scroll event on the screen being displayed is transmitted from the client terminal, each line to be displayed on the screen after scrolling from the first cache. Means for taking out the corresponding data list and storing it in the second cache, means for taking out the data list in the second cache, filling the template and generating a Web file for screen display after scrolling, this Web It is characterized by functioning as means for transmitting a file to a client terminal.

  The database utilization program according to claim 15 is based on the program of claim 14, and further, when information indicating that the specific data in the screen has been corrected is transmitted from the client terminal to the front end server. , Means for correcting the corresponding data in the first cache, and corresponding to the data list in the first cache when information indicating that data has been added in the screen is transmitted from the client terminal Means for adding data, means for converting each data constituting the data list in the first cache into a data type specific to each data item when a data update request is transmitted from the client terminal Means for storing a data list comprising the converted data in a buffer; It transmits the data list in the 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 16 is a database utilization program applied to a front-end server interposed between a database server and a client terminal, wherein the front-end server is transmitted from the database server. Means for storing a list of data in a buffer, means for adding a check box to at least a part of data constituting the record, means for storing a list of data to which the check box is added in a first cache, A data list for one page having the number of lines specified by the screen design is taken out from one cache, a means for storing in the second cache, a data list in the second cache is taken out, and a template reflecting the screen design is taken. Fill the web file for screen display Means for transmitting the Web file to the client terminal, and information indicating that a check has been input for specific data on the screen being displayed is transmitted from the client terminal. Means for recording information that has been checked-in for corresponding data, and display from the first cache on the screen after scrolling when a scroll event of a line or page on the screen being displayed is transmitted from the client terminal The data list corresponding to each line to be retrieved is extracted and stored in the second cache, the data list in the second cache is extracted, filled in the template, and the web file for screen display after scrolling is generated Function as a means to send this Web file to the client terminal It is characterized in that.

  The database utilization program according to claim 17 is based on the program according to claim 16, and further, when the data deletion request is transmitted from the client terminal to the front-end server, the data list in the first cache is stored. Among them, it is characterized by functioning as means for extracting data that has already been checked in, means for removing a check box from the data, and means for sending the data to the database server and requesting deletion thereof.

  The database utilization program according to claim 18 is premised on the program of claim 16, and further, when the data deletion request is transmitted from the client terminal to the front-end server, the data list in the first cache is stored. Among them, it is characterized in that it functions as means for extracting data for which no check is input, and means for transmitting the data to a database server and requesting deletion thereof.

In the database utilization system according to claim 1 and the database utilization program according to claim 10, a data list passed from a database server and subjected to a predetermined conversion process is stored in a cache, and is stored for each number of lines defined by a screen design. Since the data list for one page is sent to the client terminal as a Web file, it is possible to display a list of data in units of pages with the number of lines determined on the Web browser of the client terminal. It becomes.
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 addition, since the necessary data in the records sent from the database server can be arranged in a matrix according to the screen design, it is possible to improve the listability when Web files are displayed on the client terminal display. It becomes possible.

  According to the database utilization system of claim 2 and the database utilization program of claim 11, when the database server is requested to update data based on the data list that has been modified or added, the data arranged in a matrix Is restored to the original array, it is possible to ensure consistency with the data structure in the database server.

In the database utilization system according to claim 3 and the database utilization program according to claim 12, the data can be displayed in a list in units of pages of a predetermined number of lines on the Web browser of the client terminal, and the data is in units of one page. Thus, it is possible to exhibit the effect of suppressing the traffic volume by being transmitted from the front-end server to the client terminal.
In addition, in the records passed from the database server, data that does not need to be displayed due to screen design is eliminated in advance, and only data that needs to be displayed is sent to the client terminal, further enhancing the effect of reducing the amount of communication. Can do.

  According to the database utilization system of claim 4 and the database utilization program of claim 13, when the database server is requested to update data based on the corrected or added data list, the missing data item is Therefore, consistency with the data structure in the database server can be ensured.

In the case of the database utilization system according to claim 5 and the database utilization program according to claim 14, the data can be displayed in a list in units of pages of a predetermined number of lines on the Web browser of the client terminal, and the data is in units of one page. Thus, it is possible to exhibit the effect of suppressing the traffic volume by being transmitted from the front-end server to the client terminal.
Moreover, even if the record passed from the database server includes various types of data, it is converted into a general-purpose data type in advance, so that subsequent processing can be simplified. .

  According to the database utilization system of claim 6 and the database utilization program of claim 15, when requesting the database server to update data based on the data list that has been modified or added, each data from a general-purpose data type Since the data type is returned to the item-specific data type, consistency with the data structure in the database server can be ensured.

In the case of the database utilization system according to claim 7 and the database utilization program according to claim 16, the data can be displayed in a list in units of pages of a predetermined number of lines on the Web browser of the client terminal, and the data is in units of one page. Thus, it is possible to exhibit the effect of suppressing the traffic volume by being transmitted from the front-end server to the client terminal.
Moreover, since data or a combination of data that is required to have a check box on the screen design can be converted to a data type with a check box, a check box for the data on the Web browser of the client terminal Can be displayed.

  According to the database utilization system of claim 8 and the database utilization program of claim 17, when the screen design defines that the deletion target is specified by checking the check box, only the data that has been checked and entered Can be extracted and sent to the database server to request deletion. At this time, since the check box is removed from the deletion target data, consistency with the data structure in the database server can be ensured.

  According to the database utilization system of claim 9 and the database utilization program of claim 18, when the screen design stipulates that the deletion target is specified by not checking the check box, the check is input. Only data that is not available can be extracted and sent to the database server to request deletion.

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 and a keyboard and a display 22 are connected, and includes a processing request unit 24 and a Web page display unit 26.
Here, the processing request unit 24 and the Web page display unit 26 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 front-end server 16 includes a control unit 30, a screen generation unit 32, a data conversion unit 34, a business processing unit 36, a first cache 38, a second cache 40, and a buffer 42. .
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, so that the control unit 30, the screen generation unit 32, the data conversion unit 34, and the business processing unit 36 are realized.
Further, when the user selects another service, other application programs X2, X3,... Are started separately, and the control unit 30, the screen generation unit 32, the data conversion unit 34, which are optimized for the service, In addition, the business processing unit 36 appears in parallel.
The first cache 38, the second cache 40, and the buffer 42 are set in the memory space of the front-end server 16 by the application program.

In the following, a procedure for updating registered data using 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, the server 16 transmits a Web file (Html file or the like) for menu display (FIG. 3). 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, for example, “master maintenance / store update” from this menu, a delivery screen distribution request for the service is transmitted from the processing request unit 24 of the client terminal 12 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), and a dedicated control unit 30, screen generation unit 32, data conversion unit 34, and business processing unit 36 are formed. At the same time, a first cache 38, a second cache 40, and a buffer 42 are set in the memory space.

Next, a store information extraction request is transmitted from the business processing unit 36 to the DB server 14 (S14).
When the list of records stored in the store database is transmitted from the DB server 14, the business processing unit 36 stores it in the buffer 42 (S15).

The data conversion unit 34 converts the configuration data of each record stored in the buffer 42 into a general-purpose data type (S16), and then outputs it to the control unit 30.
That is, one record usually contains data of different data types such as Boolean type, byte type, character type, date type, integer type, character string type, etc. At this stage, the data conversion unit 34 uniformly converts these into general-purpose data types for character string display.
As a result, the control unit 30 and the screen generation unit 32 can perform processing without being aware of the data type of each data included in the record, and the program code for realizing the control unit 30 and the screen generation unit 32 is simplified. Can be

  The control unit 30 temporarily stores the record list received from the data conversion unit 34 in the first cache 38 (S17), and then stores the data list for one page (for example, 10 items of data) defined by the screen design. The data is taken out and stored in the second cache 40 (S18).

The screen generation unit 32 takes out the data list for one page from the second cache 40 and fills it with a template dedicated to the service to generate a Web file for the store information update screen. Transmit (S19).
As a result, the store information update screen 50 is displayed on the Web browser of the client terminal 12 as shown in FIG. 5A (S20).

On the first page of this screen 50, only 10 of the 52 records are displayed.
Each record includes data items of store code, store name, store read, telephone number, location, and date of opening.

Since the display column of each data is an inputable field, for example, when the user corrects the “store read” data of the store code: 006, the cursor is moved to the corresponding display column and the correct reading is overwritten ( S21).
Next, when the user clicks the next line scroll button 52, a distribution request for a screen displaying data shifted downward by one line is transmitted from the processing request unit 24 of the client terminal 12 to the front end server 16 (S22). ).

Upon receiving this event, the control unit 30 of the front-end server 16 first overwrites the corresponding data in the first cache 38 with the display data transmitted from the client terminal 12, and reflects the above correction by the user (S23).
Next, the control unit 30 extracts the data list for displaying the page shifted down by one line from the first cache 38 and stores it in the second cache 40 (S24).
The screen generation unit 32 fills these data into the same template as described above, generates a Web file with the number notation updated, and transmits it to the client terminal 12 (S25).
As a result, as shown in FIG. 5B, a screen 50 obtained by scrolling the page down by one line is displayed on the Web browser of the client terminal 12 (S26 in FIG. 4).

When adding a new record, the user clicks the next page scroll button 54 five times to request the display of the last page (page 6).
As a result, a delivery request for the final page is transmitted from the processing request unit 24 of the client terminal 12 to the front-end server 16 (S27), and the control unit 30 that has received the request is displayed on the final page from the first cache 38. The data list to be retrieved is taken out and stored in the second cache 40 (S28).
The screen generation unit 32 fills the template with these data, generates a Web file in which the number notation and page number notation are updated, and transmits the Web file to the client terminal 12 (S29).
As a result, as shown in FIG. 6, the final page screen 50 is displayed on the Web browser of the client terminal 12 (S30).

The user types in each data (store code, store name, store read, etc.) of the new record into the blank input field 56 provided on the next line of the last record on the last page (S31).
When the user who has finished adding the necessary records clicks the previous page scroll button 58, the processing request unit 24 of the client terminal 12 displays a screen with a data list shifted up by one page from the front end server 16. A distribution request is transmitted (S32).

Upon receiving this event, the control unit 30 first inserts the additional data transmitted from the client terminal 12 into the data list of the first cache 38 (S33).
At the same time, the control unit 30 takes out the data list for displaying the page shifted up by one page from the first cache 38 and stores it in the second cache 40 (S34).
The screen generation unit 32 fills the template with the data and generates a Web file in which the page number notation is updated and transmits it to the client terminal 12 (S35).
As a result, although not shown, the screen 50 scrolled up by one page is displayed on the Web browser of the client terminal 12 (S36).

When the user who has finished correcting and adding necessary data clicks the update button 60, an update request for store information is transmitted from the processing request unit 24 of the client terminal 12 to the front-end server 16 (S37).
Upon receiving this event, the control unit 30 takes out the data list of the first cache 38 and passes it to the data conversion unit 34 (S38).
The data conversion unit 34 converts the type of each data included in the data list from a general-purpose data type to a data type unique to each data item, and stores it in the buffer 42 (S39).

The business processing unit 36 transmits the data list in the buffer 42 to the DB server 14 and requests the data update (S40).
Receiving this, the DB server 14 updates the store database with the data list received from the business processing unit 36.

As described above, the control unit 30 cuts out the data list for the number of lines of one page specified by the screen design from the data list stored in the first cache 38, and stores it in the second cache 40. Since the screen generation unit 32 takes out this, generates a display screen (Web file), and sequentially transmits it to the client terminal 12 in units of one page, the data list for the determined number of lines is always displayed on the Web browser. As shown in FIGS. 5 and 6, the positions of the end button 62 and the update button 60 are also fixed on the screen 50.
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 above example, when the user scrolls the line or page, the correction or addition of data is reflected in the first cache 38, but the update button 60 is clicked immediately after the correction or addition. In this case, the modification is reflected in the first cache 38, and at the same time, the update processing in the DB server 14 is executed.

Next, a processing procedure when the user deletes store information will be described with reference to the flowcharts of FIGS.
That is, when the user selects “master maintenance / store deletion” on the above menu screen, a processing screen distribution request for the service is transmitted from the processing request unit 24 of the client terminal 12 to the front-end server 16 (FIG. 7 S50).
In response to this, the front-end server 16 starts an application program corresponding to the service (S51), and forms a dedicated control unit 30, a screen generation unit 32, a data conversion unit 34, and a business processing unit 36. The first cache 38, the second cache 40, and the buffer 42 are set on the memory space.

Next, a store information extraction request is transmitted from the business processing unit 36 to the DB server 14 (S52).
When the list of records stored in the store database is transmitted from the DB server 14, the business processing unit 36 stores it in the buffer 42 (S53).

The data converter 34 converts the configuration data of each record stored in the buffer 42 into a general-purpose data type as described above (S54).
Next, the data conversion unit 34 extracts only the data related to “store code” and “store name”, which are data items to be displayed on the store deletion screen, from the data items constituting each record. (S55) A check box for selection is added to this data combination (S56).
Further, the data conversion unit 34 arranges the combinations of the data in a matrix form according to the distribution rule required by the design of the store deletion screen (S57), and generates a data list including data related to a plurality of records in one line. .

  The control unit 30 that has received the converted data list from the data conversion unit 34 stores the data list in the first cache 38 (S58), and then data for one page from the data list in the first cache 38. A list (for example, data for 10 lines) is taken out and stored in the second cache 40 (S59).

The screen generation unit 32 takes out the data list of the second cache 40, fills it with a template dedicated to the store deletion screen, generates a Web file, and transmits it to the client terminal 12 (S60).
As a result, as shown in FIG. 9, a store deletion screen 64 is displayed on the Web browser of the client terminal 12 (S61).

This screen 64 includes a data list of 10 lines per page, and includes store information (combination of store code and store name) related to 5 records per line.
Therefore, on the first page of this screen 64, a total of 50 pieces of store information from store codes 001 to 050 are displayed in a list.
In addition, a check box 66 for selection is added to each store information.

  On the other hand, when the user checks the store information check box 66 that the user wishes to delete (S62) and clicks the next-line scroll button 68, the processing request unit 24 of the client terminal 12 sends 1 to the front-end server 16. A distribution request for a screen having a data list shifted down by a line is transmitted (S63).

Upon receiving this event, the control unit 30 adds checked information for the corresponding data stored in the first cache 38 (S64 in FIG. 8).
Next, the control unit 30 retrieves the data list (10 lines) for displaying the page shifted down by one line from the first cache 38 and stores it in the second cache 40 (S65).
The screen generation unit 32 fills these data in the same template as described above, generates a Web file with the number notation updated, and transmits it to the client terminal 12 (S66).
As a result, although not shown, a screen 64 having a page scrolled down by one line is displayed on the Web browser of the client terminal 12 (S67).

When the user who has completed the check box for the necessary check box 66 clicks the delete button 70, a data deletion request is transmitted from the processing request unit 24 of the client terminal 12 to the front-end server 16 (S68).
Upon receiving this event, the control unit 30 passes the data list of the first cache 38 to the data conversion unit 34 (S69).

On the other hand, the data conversion unit 34 converts each data list into an original array, that is, a data list in which individual store information is arranged in a line for each record (S70).
Next, the data conversion unit 34 converts the type of each data included in the data list from a general data type to a data type specific to each data item (S71).
Next, the data conversion unit 34 supplements each store information with missing data items such as “store read” and “phone number” to restore the original record (S72).
Next, the data conversion unit 34 leaves only the record to be deleted whose check box is checked, and deletes other records (S73).
Finally, the data conversion unit 34 removes the check box from the deletion target record and stores it in the buffer 42 (S74).

The business processing unit 36 transmits the deletion target record stored in the buffer 42 to the DB server 14 and requests the deletion of the corresponding record (S75).
Receiving this, the DB server 14 deletes the corresponding record from the store database.

As described above, the control unit 30 cuts out the data list for the number of lines of one page specified by the screen design from the data list stored in the first cache 38, and stores it in the second cache 40. Since the screen generation unit 32 takes out this, generates a display screen (Web file), and sequentially transmits it to the client terminal 12 in units of one page, the data list for the determined number of lines is always displayed on the Web browser. As shown in FIG. 9, the positions of the end button 72 and the delete button 70 are also fixed on the screen 64.
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.

Further, by arranging the data in a matrix as described above, it is possible to improve the data listing.
Conventionally, when displaying a large amount of data on a Web browser, the data must be arranged in the vertical direction in units of records, and thus vertical scrolling has to be frequently performed.
On the other hand, in this system 10, since the data related to a plurality of records is concatenated into a single line and displayed on the screen by the data conversion unit 34, it is possible to suppress the number of display lines and improve the data listability. .
When returning the data to the DB server 14, the data conversion unit 34 returns the data to the original array, so that consistency with the data structure in the DB server 14 is also ensured.

The data arrangement rule is defined in advance by the screen design, and the data conversion unit 34 arranges individual data or a combination of data in a matrix according to this rule.
FIG. 10 shows the arrangement rules on the screen 64 shown in FIG. 9, in which data combinations α are arranged in units of 10 in the vertical direction and folded in the right direction, and a total of five small lists are arranged in the horizontal direction. The list of 50 data is displayed.
As a result, the first line of the display page contains data related to five records (01), (11), (21), (31), and (41), and the tenth line contains (10), (20 ), (30), (40), and (50).

On the other hand, FIG. 11 shows another arrangement rule. By arranging the data combinations α in the horizontal direction in units of 10 and folding them downward, a total of 5 rows are arranged in the vertical direction. An example of displaying data on one page is shown.
As a result, the first line of the display page contains data related to 10 records (01) to (10), and the fifth line contains data related to 10 records (41) to (50). Yes.

Further, as described above, in the system 10, the data conversion unit 34 extracts in advance only the data items that are requested to be displayed on the screen design from the records transmitted from the DB server 14, and this is controlled by the control unit. 30 and a method of transmitting to the client terminal 12 via the screen generation unit 32, and non-displayed data is not wastedly transmitted to the client terminal 12, so that the data communication amount can be reduced. .
Hiding unnecessary data items on the Web browser of the client terminal 12 has been realized so far by using a technique called hidden, but in this case it is hidden data. Since the client terminal 12 and the server 16 are reciprocated, the amount of data communication is increased accordingly.
When returning the data to the DB server 14, the original data items are restored by the data conversion unit 34, so that consistency with the data structure in the DB server 14 is also ensured.

  Furthermore, since the data in the DB server 14 is not originally provided with a check box, if it is required to add a check box due to the screen design, the data transmitted from the DB server 14 as described above is included in the data. On the other hand, it is effective that the data conversion unit 34 converts the data into check box-attached data and restores the original state when returning to the DB server 14.

  Note that the conversion processing of S54 to S57 and the conversion processing of S70 to S74 in the data conversion unit 34 are not limited to the above-described order, and the order may be changed as necessary.

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, the screen generation unit 32, and the data conversion unit 34 need to be changed accordingly.
For example, when a screen design that provides a list of 20 rows / pages for a deletion screen of a database is adopted, the control unit 30 and the screen generation unit 32 are required to process 20 data as one page.
In addition, as a method of selecting a deletion target, when adopting a screen design in which a record to be deleted is not checked as described above but a record to be left is checked, the data conversion unit 34 is controlled by the control unit 30. It is necessary to extract unchecked data from the passed data list as a deletion target and store it in the buffer 42.

On the other hand, the business processing unit 36 is completely separated from the screen design, just requests the DB server 14 to extract records, stores the transmitted records in the buffer 42, and stores them in the buffer 42 by the data conversion unit 34. It is possible to concentrate on the process of passing the record stored in 42 to the DB server 14 and requesting the necessary update or deletion.
As a result, since the program configuration of the business processing unit 36 can be simplified, there is an effect of improving reusability and stability of the code.
Even if the screen design is changed, it is sufficient to correct the screen template managed by the screen generation unit 32 and the codes of the control unit 30 and the data conversion unit 34, and the code of the business processing unit 36 is corrected. There is no need to do.

In addition, when coding the control unit 30, the screen generation unit 32, and the data conversion unit 34 according to the screen design, the basic operation part common to each screen is created in advance as an application base, and one page It is only necessary to rewrite only the parts such as the number of hit lines, the data selection method, and the meaning of the selection (whether the checked item is deleted or the unchecked item is deleted).
In particular, when coding each part in the Java (registered trademark) language, the code of the application base part can be easily used by using the inheritance mechanism, which makes it easy to modify the program when the screen design changes. Become.

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 in the case of updating registration data in this system. It is a flowchart which shows the process sequence in the case of updating registration data in this system. It is a layout figure which shows the screen for shop update. It is a layout figure which shows the screen for shop update. It is a flowchart which shows the process sequence in the case of deleting registration data in this system. It is a flowchart which shows the process sequence in the case of deleting registration data in this system. It is a layout figure which shows the screen for store deletion. It is a conceptual diagram which shows an example of the arrangement | sequence rule of data. It is a conceptual diagram which shows the other example of the arrangement | sequence rule of data. It is a conceptual diagram which shows 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 Processing request section
26 Web page display area
30 Control unit
32 Screen generator
34 Data converter
36 Business Processing Department
38 First cache
40 Second cache
42 buffers
50 Store information update screen
52 Next line scroll button
54 Next page scroll button
56 Input fields
58 Previous page scroll button
60 Refresh button
62 Exit button
64 Screen for deleting store information
66 Check box
68 Next line scroll button
70 Delete button
72 Exit button
X1, X2, X3 Application program α Data combination

Claims (18)

A database utilization system comprising a front-end server interposed between a database server and a client terminal,
The front-end server
A function that stores a list of records sent from the database server in a buffer;
A function that sorts at least a part of data constituting the record into a matrix according to an array rule defined by the screen design, and converts the data into a data list in which data belonging to a plurality of records is arranged in one line;
A function of storing this data list in the first cache;
A function of taking out a data list for one page having the number of lines defined by the screen design from the first cache and storing it in the second cache;
A function that takes out the data list in the second cache, fills it with a template reflecting the screen design, and generates a Web file for screen display;
A function to send this web file to the client terminal,
When a line or page scroll event on the screen being displayed is transmitted from the client terminal, a data list corresponding to each line to be displayed on the screen after scrolling is extracted from the first cache, and the second cache is retrieved. The function to store in
A function that takes out the data list in the second cache, fills the template, and generates a web file for screen display after scrolling;
A function to send this web file to the client terminal,
A database utilization system characterized by comprising: The front-end server
A function of performing correction corresponding to the corresponding data in the first cache when information indicating that the specific data in the screen has been corrected is transmitted from the client terminal;
A function of adding data corresponding to the data list in the first cache when information indicating that data has been added is transmitted from the client terminal in the screen;
A function of converting a data list in the first cache into a data list in which data is arranged in a row in units of records when a data update request is transmitted from a client terminal;
The ability to store this data list in a buffer;
A function to send the data list in this buffer to the database server and request data update;
The database utilization system according to claim 1, further comprising: A database utilization system comprising a front-end server interposed between a database server and a client terminal,
The front-end server
A function that stores a list of records sent from the database server in a buffer;
A function of extracting data or a combination of data related to data items that are required to be displayed on the screen design from the data constituting the record,
A function of storing in the first cache a data list comprising this data or a combination of data;
A function of taking out a data list for one page having the number of lines defined by the screen design from the first cache and storing it in the second cache;
A function that takes out the data list in the second cache, fills it with a template reflecting the screen design, and generates a Web file for screen display;
A function to send this web file to the client terminal,
When a line or page scroll event on the screen being displayed is transmitted from the client terminal, a data list corresponding to each line to be displayed on the screen after scrolling is extracted from the first cache, and the second cache is retrieved. The function to store in
A function that takes out the data list in the second cache, fills the template, and generates a web file for screen display after scrolling;
A function to send this web file to the client terminal,
A database utilization system characterized by comprising: The front-end server
A function of performing correction corresponding to the corresponding data in the first cache when information indicating that the specific data in the screen has been corrected is transmitted from the client terminal;
A function of adding data corresponding to the data list in the first cache when information indicating that data has been added is transmitted from the client terminal in the screen;
A function of supplementing a missing data item to the data list in the first cache when a data update request is transmitted from the client terminal;
The ability to store this data list in a buffer;
A function to send the data list in this buffer to the database server and request data update;
The database utilization system according to claim 3, further comprising: A database utilization system comprising a front-end server interposed between a database server and a client terminal,
The front-end server
A function that stores a list of records sent from the database server in a buffer;
A function for converting at least a part of data constituting the record into a general-purpose data type;
A function of storing the data list including the converted data in the first cache;
A function of taking out a data list for one page having the number of lines defined by the screen design from the first cache and storing it in the second cache;
A function that takes out the data list in the second cache, fills it with a template reflecting the screen design, and generates a Web file for screen display;
A function to send this web file to the client terminal,
When a line or page scroll event on the screen being displayed is transmitted from the client terminal, a data list corresponding to each line to be displayed on the screen after scrolling is extracted from the first cache, and the second cache is retrieved. The function to store in
A function that takes out the data list in the second cache, fills the template, and generates a web file for screen display after scrolling;
A function to send this web file to the client terminal,
A database utilization system characterized by comprising: The front-end server
A function of performing correction corresponding to the corresponding data in the first cache when information indicating that the specific data in the screen has been corrected is transmitted from the client terminal;
A function of adding data corresponding to the data list in the first cache when information indicating that data has been added is transmitted from the client terminal in the screen;
A function of converting each data constituting the data list in the first cache into a data type specific to each data item when a data update request is transmitted from the client terminal;
A function for storing a data list of the converted data in a buffer;
A function to send the data list in this buffer to the database server and request data update;
The database utilization system according to claim 5, further comprising: A database utilization system comprising a front-end server interposed between a database server and a client terminal,
The front-end server
A function that stores a list of records sent from the database server in a buffer;
A function of adding a check box to at least a part of data constituting the record;
A function of storing a list of data to which the check box is added in the first cache;
A function of taking out a data list for one page having the number of lines defined by the screen design from the first cache and storing it in the second cache;
A function that takes out the data list in the second cache, fills it with a template reflecting the screen design, and generates a Web file for screen display;
A function to send this web file to the client terminal,
A function of recording check input information for corresponding data in the first cache when information indicating that a check is input for specific data is transmitted from the client terminal on the screen being displayed When,
When a line or page scroll event on the screen being displayed is transmitted from the client terminal, a data list corresponding to each line to be displayed on the screen after scrolling is extracted from the first cache, and the second cache is retrieved. The function to store in
A function that takes out the data list in the second cache, fills the template, and generates a web file for screen display after scrolling;
A function to send this web file to the client terminal,
A database utilization system characterized by comprising: The front-end server
A function for extracting data that has already been checked in the data list in the first cache when a data deletion request is transmitted from the client terminal;
The ability to remove checkboxes from the data,
A function for sending the data to the database server and requesting the deletion;
The database utilization system according to claim 7, further comprising: The front-end server
A function for extracting data for which no check is entered in the data list in the first cache when a data deletion request is transmitted from the client terminal;
A function for sending the data to the database server and requesting the deletion;
The database utilization system according to claim 7, 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 storing a list of records sent from the database server in a buffer;
Means for distributing at least a part of data constituting the record in a matrix form according to an array rule defined by the screen design, and converting the data into a data list in which data belonging to a plurality of records is arranged in one line;
Means for storing the data list in a first cache;
Means for taking out a data list for one page having the number of lines defined by the screen design from the first cache and storing it in the second cache;
Means for retrieving a data list in the second cache, filling a template reflecting the screen design, and generating a Web file for screen display;
Means to send this web file to the client terminal,
When a line or page scroll event on the screen being displayed is transmitted from the client terminal, a data list corresponding to each line to be displayed on the screen after scrolling is extracted from the first cache, and the second cache is retrieved. Means for storing in,
Means for taking out the data list in the second cache, filling the template and generating a web file for screen display after scrolling;
Means to send this web file to the client terminal,
Database utilization program characterized by functioning as The above front-end server
Means for performing correction corresponding to the corresponding data in the first cache when information indicating that the specific data in the screen has been corrected is transmitted from the client terminal;
Means for adding data corresponding to the data list in the first cache when information indicating that data has been added in the screen is transmitted from the client terminal;
Means for converting a data list in the first cache into a data list in which data is arranged in a row in units of records when a data update request is transmitted from a client terminal;
Means for storing this data list in a buffer;
Means for sending the data list in this buffer to the database server and requesting data update;
The database utilization program according to claim 10, wherein the database utilization program is made to function as: 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 storing a list of records sent from the database server in a buffer;
Means for extracting data or a combination of data related to data items that are required to be displayed on the screen design from the data constituting the record;
Means for storing in the first cache a data list comprising this data or a combination of data;
Means for taking out a data list for one page having the number of lines defined by the screen design from the first cache and storing it in the second cache;
Means for retrieving a data list in the second cache, filling a template reflecting the screen design, and generating a Web file for screen display;
Means to send this web file to the client terminal,
When a line or page scroll event on the screen being displayed is transmitted from the client terminal, a data list corresponding to each line to be displayed on the screen after scrolling is extracted from the first cache, and the second cache is retrieved. Means for storing in,
Means for taking out the data list in the second cache, filling the template and generating a web file for screen display after scrolling;
Means to send this web file to the client terminal,
Database utilization program characterized by functioning as The above front-end server
Means for performing correction corresponding to the corresponding data in the first cache when information indicating that the specific data in the screen has been corrected is transmitted from the client terminal;
Means for adding data corresponding to the data list in the first cache when information indicating that data has been added in the screen is transmitted from the client terminal;
Means for replenishing a missing data item to the data list in the first cache when a data update request is transmitted from the client terminal;
Means for storing this data list in a buffer;
Means for sending the data list in this buffer to the database server and requesting data update;
The database utilization program according to claim 12, wherein the database utilization program is functioned as: 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 storing a list of records sent from the database server in a buffer;
Means for converting at least a part of data constituting the record into a general-purpose data type;
Means for storing in the first cache a data list comprising the converted data;
Means for taking out a data list for one page having the number of lines defined by the screen design from the first cache and storing it in the second cache;
Means for retrieving a data list in the second cache, filling a template reflecting the screen design, and generating a Web file for screen display;
Means to send this web file to the client terminal,
When a line or page scroll event on the screen being displayed is transmitted from the client terminal, a data list corresponding to each line to be displayed on the screen after scrolling is extracted from the first cache, and the second cache is retrieved. Means for storing in,
Means for taking out the data list in the second cache, filling the template and generating a web file for screen display after scrolling;
Means to send this web file to the client terminal,
Database utilization program characterized by functioning as The above front-end server
Means for performing correction corresponding to the corresponding data in the first cache when information indicating that the specific data in the screen has been corrected is transmitted from the client terminal;
Means for adding data corresponding to the data list in the first cache when information indicating that data has been added in the screen is transmitted from the client terminal;
Means for converting each data constituting the data list in the first cache into a data type specific to each data item when a data update request is transmitted from the client terminal;
Means for storing a data list comprising the converted data in a buffer;
Means for sending the data list in this buffer to the database server and requesting data update;
The database utilization program according to claim 14, wherein the database utilization program is made to function as: 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 storing a list of records sent from the database server in a buffer;
Means for adding a check box to at least a part of data constituting the record;
Means for storing a list of data to which the check box is added in the first cache;
Means for taking out a data list for one page having the number of lines defined by the screen design from the first cache and storing it in the second cache;
Means for retrieving a data list in the second cache, filling a template reflecting the screen design, and generating a Web file for screen display;
Means to send this web file to the client terminal,
Means for recording information that has already been checked in to corresponding data in the first cache when information indicating that a check has been input for specific data is transmitted from the client terminal. ,
When a line or page scroll event on the screen being displayed is transmitted from the client terminal, a data list corresponding to each line to be displayed on the screen after scrolling is extracted from the first cache, and the second cache is retrieved. Means for storing in,
Means for taking out the data list in the second cache, filling the template and generating a web file for screen display after scrolling;
Means to send this web file to the client terminal,
Database utilization program characterized by functioning as The above front-end server
Means for extracting checked data in the data list in the first cache when a data deletion request is transmitted from the client terminal;
Means for removing the checkbox from the data,
Means for sending the data to the database server and requesting its deletion;
The database utilization program according to claim 16, wherein the database utilization program is functioned as: The above front-end server
Means for extracting unchecked data from the data list in the first cache when a data deletion request is transmitted from the client terminal;
Means for sending the data to the database server and requesting its deletion;
The database utilization program according to claim 16, wherein the database utilization program is functioned as:

Images