JP4495783B2 - Database usage system - Google Patents

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 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 a horizontal direction, but it is desirable 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-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 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 The search condition sent from the client terminal is sent to the database server to request a search, and the search result record sent from the database server is stored in the buffer. A data conversion unit for converting data constituting a record into a data list in which data belonging to a plurality of records is arranged in one line by distributing the data constituting a record in a matrix according to an arrangement rule defined by the screen design; And store this in the cache The data list for one page having the number of lines specified by the screen design is taken out from one cache, the control unit for storing in the second cache, the data list in the second cache is taken out, and the screen design is reflected. A screen generation unit that fills the template and generates a Web file for screen display and transmits the Web file to the client terminal, and the business processing unit, the data conversion unit, the control unit, and the screen generation unit, Each service that is selected for use in each client terminal is generated on the front-end server, and the buffer, the first cache, and the second cache are stored in the memory space of the front-end server for each service. The specific data on the display screen has been corrected from the above client terminal. When the information indicating is transmitted, the control unit executes processing for correcting the corresponding data in the first cache, and confirms that the data has been added on the display screen from the client terminal. When the information indicating is transmitted, the control unit executes processing for adding the corresponding data to the data list in the first cache, and from the client terminal, the page including the corrected data or the additional data is executed. When a request for redisplay is transmitted, the control unit executes a process of taking out a data list for one page including corrected data or additional data from the first cache and storing it in the second cache. The screen generation unit takes out the data list in the second cache, fills the template, and displays the Web file for screen display. When the update request based on the corrected data or the additional data is transmitted from the client terminal, the control unit executes the process of transmitting the web file to the client terminal. A process of outputting the data list in one cache to the data conversion unit is executed, and the data conversion unit converts the data list into a data list in which data is arranged in a row in units of records and stores the data list in the buffer. The business processing unit executes processing, and transmits the data stored in the buffer to the database server, and executes processing for requesting data update .

The database utilization system according to claim 2 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 search transmitted from the client terminal. Send the conditions to the database server to request a search, and display the list of search result records sent from the database server in the buffer, and display on the screen design from each record stored in this buffer A data conversion unit that generates a data list obtained by extracting data related to the data item required, stores the data list in the first cache, and includes the number of lines defined by the screen design from the first cache. The data list for one page is taken out and the second cache Take out the data list in the second cache and the control unit stored in the queue, fill it with a template reflecting the screen design and generate a Web file for screen display, and send this Web file to the client terminal A screen generation unit, and the business processing unit, the data conversion unit, the control unit, and the screen generation unit are generated on the front end server for each service selected for use in each client terminal, and the buffer The first cache and the second cache are secured in the memory space of the front-end server for each service, and information indicating that the specific data in the display screen has been corrected is transmitted from the client terminal. If so, the control unit corrects the corresponding data in the first cache. The control unit adds data corresponding to the data list in the first cache when the client terminal transmits information indicating that data has been added on the display screen. When the request for redisplaying the page including the corrected data or the additional data is transmitted from the client terminal, the control unit adds the corrected data or the additional data from the first cache. A data list for one page including data is extracted and stored in the second cache, and the screen generation unit extracts the data list in the second cache, fills the template, and displays the screen. A web file for the client is generated and the process for sending the web file to the client terminal is executed. When the update request based on the corrected data or the additional data is transmitted, the control unit executes a process of outputting the data list in the first cache to the data conversion unit, and the data conversion unit Fills the data list with missing data items and executes the process of storing the data in the buffer, and the business processing unit transmits the data stored in the buffer to the database server. And processing for requesting data update is executed .

The database utilization system according to claim 3 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 search transmitted from the client terminal. A request is sent to the database server to request a search, and a business processing unit that stores a list of search result records sent from the database server in a buffer, and data constituting the records stored in this buffer A check box is added, and a data conversion unit that converts the data list into a data list in which data belonging to a plurality of records is arranged in one line by sorting them in a matrix according to the arrangement rule defined by the screen design, and this data list In the first cache And a control unit that takes out the data list for one page having the number of lines specified by the screen design from the first cache and stores it in the second cache, and the data list in the second cache. A screen generation unit that takes out and fills a template reflecting the screen design to generate a Web file for screen display and transmits the Web file to the client terminal, and includes the business processing unit, data conversion unit, and control unit And the screen generation unit is generated on the front-end server for each service selected for use in each client terminal, and the buffer, the first cache, and the second cache are stored in the front-end for each service. It is secured in the memory space of the end server. When a notification indicating that the check has been added is transmitted, the control unit executes processing for adding the checked information to the corresponding data in the first cache, and the client terminal checks When a request for redisplay of a page including data is transmitted, the control unit takes out a data list for one page including data to which checked information is added from the first cache, The screen generation unit executes processing to be stored in the cache, takes out the data list in the second cache, fills the template, generates a Web file for screen display, and stores the Web file in the client terminal Request to delete the data selected based on the presence or absence of the check from the client terminal. When a list is transmitted, the control unit executes a process of outputting the data list in the first cache to the data conversion unit, and the data conversion unit stores the data in a row in units of records. Processing to convert to an arrayed data list, processing to delete other data leaving only the data to be deleted selected according to the presence or absence of checking, and this if the check box is added to the data to be deleted And processing for storing the data to be deleted in the buffer, and the business processing unit transmits the data stored in the buffer to the database server and executes processing for requesting the deletion. It is characterized in that.

The database utilization system according to claim 4 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 search transmitted from the client terminal. Send the conditions to the database server to request a search, and display the list of search result records sent from the database server in the buffer, and display on the screen design from each record stored in this buffer A data conversion unit that extracts data related to data items required and generates a data list to which a check box is added, stores the data list in the first cache, and a screen design from the first cache. One page of data list with a specified number of lines And take out the data list in the second cache and fill it with a template reflecting the screen design to generate a Web file for screen display. A screen generation unit that transmits a message to the client terminal, and the business processing unit, the data conversion unit, the control unit, and the screen generation unit are generated on the front-end server for each service selected for use in each client terminal. In addition, the buffer, the first cache, and the second cache are secured in the memory space of the front-end server for each same service, and the specific data in the display screen is checked from the client terminal. When a notification indicating that the above has been transmitted, the control unit places the first cache in the first cache. When the processing for adding the checked information to the corresponding data is executed and a request for redisplaying the page including the checked data is transmitted from the client terminal, the control unit reads from the first cache. Take out a data list for one page including data to which checked information is added, and execute a process of storing the data list in a second cache. The screen generation unit takes out the data list in the second cache, Create a Web file for screen display by filling the above template and execute a process to send this Web file to the client terminal. When transmitted, the control unit outputs the data list in the first cache to the data conversion unit. The data conversion unit replenishes the data of the missing data item with respect to this data list, and leaves only the data to be deleted selected based on the presence or absence of the check. A process to delete, a process to remove the check box if the check target data is added, and a process to store the data to be deleted in the buffer. The data stored in the buffer is transmitted to the database server, and processing for requesting the deletion is executed .

The database utilization system according to claim 5 is based on the system according to claims 1 to 4, and further, the data conversion unit stores the data list in the buffer at any time before passing the data list to the control unit. Any time before the data conversion unit stores the data list output from the control unit in the buffer. Thus, a process of converting each data constituting the data list into a data type specific to each data item is executed.

In the database utilization system according to claim 1, a data list passed from the database server and subjected to a predetermined conversion process is stored in the first cache, and is managed as a page for each number of lines defined by the screen design. 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 the determined 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 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.
When requesting the database server to update the data based on the data list that has been modified or added, the data arranged in a matrix is returned to the original array, so consistency with the data structure in the database server is ensured. Can be secured.

Also in the case of the database utilization system according to claim 2, a data list passed from the database server and subjected to a predetermined conversion process is stored in the first 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.
Furthermore, in the records passed from the database server, data that does not need to be displayed due to screen design is excluded in advance, and only the data that needs to be displayed is sent to the client terminal, further enhancing the effect of reducing the amount of communication. Can do.
When requesting the database server to update the data based on the data list that has been modified or added, the data of the missing data items will be supplemented, so ensure consistency with the data structure in the database server. Can do.

Also in the database utilization system according to claim 3, the data can be displayed in a list in a page unit of the number of lines determined on the Web browser of the client terminal, and the data is transferred from the front end server to the client terminal in a unit of one page. The effect of suppressing the amount of communication by being transmitted can be exhibited.
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 display of the client terminal. It becomes possible.
In addition, since it is possible to convert the data required to have a check box on the screen design into a data type with a check box, a check box for the data is displayed on the Web browser of the client terminal. Is possible.
In addition, when the screen design stipulates that the deletion target is specified by checking the check box, it is possible to extract only the data that has already been checked and send it to the database server and request the deletion. it can. 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.
Or, if the screen design stipulates that the deletion target is specified by not checking the check box, only the data for which the check is not entered is extracted and sent to the database server, and the deletion is requested. can do.

In the case of the database utilization system of claim 4 as well, data can be displayed as a list in page units of a predetermined number of lines on the Web browser of the client terminal, and the data is transferred from the front end server to the client terminal in units of one page. The effect of suppressing the amount of communication by being transmitted can be exhibited.
In addition, in the records passed from the database server, data that does not need to be displayed due to screen design is excluded 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.
In addition, since it is possible to convert the data required to have a check box on the screen design into a data type with a check box, a check box for the data is displayed on the Web browser of the client terminal. Is possible.
In addition, when the screen design stipulates that the deletion target is specified by checking the check box, it is possible to extract only the data that has already been checked and send it to the database server and request the deletion. it can. 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.
Or, if the screen design stipulates that the deletion target is specified by not checking the check box, only the data for which the check is not entered is extracted and sent to the database server, and the deletion is requested. can do.

In the case of the database utilization system according to claim 5, 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. It becomes possible to simplify.
Further, when requesting the database server to update the data, the data type is returned from the general-purpose data type to the data type specific to each data item, so that consistency with the data structure in the database server can be ensured.

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 such a 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 conversion unit 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 a check box and restores the data to 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.

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 (5)

A database utilization system comprising a front-end server interposed between a database server and a client terminal,
The front-end server
A search condition sent from the client terminal to the database server to request a search, and a business processing unit for storing a list of search result records sent from the database server in a buffer;
A data conversion unit that converts data constituting the records stored in the buffer into a data list in which data belonging to a plurality of records is arranged in one line by distributing the data in a matrix according to an array rule defined by the screen design;
A control unit for storing the data list in the first cache, taking out the 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;
A screen generation unit that takes out the data list in the second cache, fills a template reflecting the screen design to generate a Web file for screen display, and transmits the Web file to the client terminal,
The business processing unit, the data conversion unit, the control unit, and the screen generation unit are generated on the front end server for each service selected for use in each client terminal, and the buffer, the first cache, and the first generation unit 2 cache is secured in the memory space of the front-end server for each service,
When the information indicating that the specific data in the display screen has been corrected is transmitted from the client terminal, the control unit executes a process for correcting the corresponding data in the first cache. ,
When information indicating that data has been added on the display screen is transmitted from the client terminal, the control unit executes processing for adding corresponding data to the data list in the first cache. ,
When a request for redisplaying a page including corrected data or additional data is transmitted from the client terminal, the control unit stores one page including corrected data or additional data from the first cache. The screen generation unit extracts the data list from the second cache and executes the process of storing it in the second cache. The screen generation unit extracts the data list in the second cache, fills the template, and generates a Web file for screen display. At the same time, execute processing to send this Web file to the client terminal,
When an update request based on corrected data or additional data is transmitted from the client terminal, the control unit executes a process of outputting a data list in the first cache to the data conversion unit,
The data conversion unit converts the data list into a data list in which data is arranged in a row in record units, and executes a process of storing in the buffer.
The database utilization system , wherein the business processing unit transmits the data stored in the buffer to a database server, and executes a process for requesting data update . A database utilization system comprising a front-end server interposed between a database server and a client terminal,
The front-end server
A search condition sent from the client terminal to the database server to request a search, and a business processing unit for storing a list of search result records sent from the database server in a buffer;
From each record stored in this buffer, a data conversion unit that generates a data list obtained by extracting data related to data items that are required to be displayed on the screen design,
A control unit for storing the data list in the first cache, taking out the 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;
A screen generation unit that takes out the data list in the second cache, fills a template reflecting the screen design to generate a Web file for screen display, and transmits the Web file to the client terminal,
The business processing unit, the data conversion unit, the control unit, and the screen generation unit are generated on the front end server for each service selected for use in each client terminal, and the buffer, the first cache, and the first generation unit 2 cache is secured in the memory space of the front-end server for each service,
When the information indicating that the specific data in the display screen has been corrected is transmitted from the client terminal, the control unit executes a process for correcting the corresponding data in the first cache. ,
When information indicating that data has been added on the display screen is transmitted from the client terminal, the control unit executes processing for adding corresponding data to the data list in the first cache. ,
When a request for redisplaying a page including corrected data or additional data is transmitted from the client terminal, the control unit stores one page including corrected data or additional data from the first cache. The screen generation unit extracts the data list from the second cache and executes the process of storing it in the second cache. The screen generation unit extracts the data list in the second cache, fills the template, and generates a Web file for screen display. At the same time, execute processing to send this Web file to the client terminal,
When an update request based on corrected data or additional data is transmitted from the client terminal, the control unit executes a process of outputting a data list in the first cache to the data conversion unit,
The data conversion unit replenishes the data of the missing data item with respect to this data list, and then executes the process of storing in the buffer.
The database utilization system , wherein the business processing unit transmits the data stored in the buffer to a database server, and executes a process for requesting data update . A database utilization system comprising a front-end server interposed between a database server and a client terminal,
The front-end server
A search condition sent from the client terminal to the database server to request a search, and a business processing unit for storing a list of search result records sent from the database server in a buffer;
A check box is added to the data constituting the records stored in this buffer, and the data belonging to a plurality of records is arranged in one line by allocating them in a matrix according to the arrangement rules defined by the screen design. A data conversion unit for converting the data list;
A control unit for storing the data list in the first cache, taking out the 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;
A screen generation unit that takes out the data list in the second cache, fills a template reflecting the screen design to generate a Web file for screen display, and transmits the Web file to the client terminal,
The business processing unit, the data conversion unit, the control unit, and the screen generation unit are generated on the front end server for each service selected for use in each client terminal, and the buffer, the first cache, and the first generation unit 2 cache is secured in the memory space of the front-end server for each service,
When the notification indicating that the specific data in the display screen is checked is transmitted from the client terminal, the control unit adds the checked information to the corresponding data in the first cache Run
When a request for re-displaying a page including checked data is transmitted from the client terminal, the control unit stores one page including data with the checked information added from the first cache. A process for taking out the data list and storing it in the second cache is executed, and the screen generation unit takes out the data list in the second cache, fills the template, and generates a Web file for screen display. At the same time, execute processing to send this Web file to the client terminal,
When a request for deleting data selected based on the presence or absence of a check is transmitted from the client terminal, the control unit executes a process of outputting a data list in the first cache to the data conversion unit. ,
The data conversion unit converts the data list into a data list in which the data is arranged in a row in units of records, a process of deleting other data leaving only the deletion target data selected based on the presence or absence of a check, When a check box is added to the deletion target data, a process of removing the check box and a process of storing the deletion target data in the buffer are executed.
The database utilization system , wherein the business processing unit transmits the data stored in the buffer to a database server and executes a process for requesting the deletion . A database utilization system comprising a front-end server interposed between a database server and a client terminal,
The front-end server
A search condition sent from the client terminal to the database server to request a search, and a business processing unit for storing a list of search result records sent from the database server in a buffer;
From each record stored in this buffer, a data conversion unit that extracts data related to a data item that is required to be displayed on the screen design and generates a data list with a check box added thereto;
A control unit for storing the data list in the first cache, taking out the 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;
A screen generation unit that takes out the data list in the second cache, fills a template reflecting the screen design to generate a Web file for screen display, and transmits the Web file to the client terminal,
The business processing unit, the data conversion unit, the control unit, and the screen generation unit are generated on the front end server for each service selected for use in each client terminal, and the buffer, the first cache, and the first generation unit 2 cache is secured in the memory space of the front-end server for each service,
When the notification indicating that the specific data in the display screen is checked is transmitted from the client terminal, the control unit adds the checked information to the corresponding data in the first cache Run
When a request for re-displaying a page including checked data is transmitted from the client terminal, the control unit stores one page including data with the checked information added from the first cache. A process for taking out the data list and storing it in the second cache is executed, and the screen generation unit takes out the data list in the second cache, fills the template, and generates a Web file for screen display. At the same time, execute processing to send this Web file to the client terminal,
When a request for deleting data selected based on the presence or absence of a check is transmitted from the client terminal, the control unit executes a process of outputting a data list in the first cache to the data conversion unit. ,
The data conversion unit performs processing for replenishing data of missing data items to this data list, processing for deleting other data while leaving only deletion target data selected based on the presence or absence of checking, and the deletion When a check box is added to the target data, a process of removing the check box and a process of storing the deletion target data in the buffer are executed.
The database utilization system , wherein the business processing unit transmits the data stored in the buffer to a database server and executes a process for requesting the deletion . The data converter is
At any point before passing the data list to the control unit, execute a process of converting each data constituting the record stored in the buffer to a general data type,
Also, at any point before the data list output from the control unit is stored in the buffer, a process for converting each data constituting the data list into a data type specific to each data item is executed. The database utilization system according to any one of claims 1 to 4 .

Images