JP2006031130A - Database-using system and database-using program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To realize a database-using system provided with a user interface which is equivalent to an exclusive application on the assumption that a Web system is used. <P>SOLUTION: A front end server 16 is provided with a function which refers to maximum horizontal width information of a list table 50 and display width information of each data item, and determines data items to be displayed in the list table 50, a function which extracts data strings related with the display items for the predetermined number of lines from a first cache 38 in which a data list transmitted from a DB server 14 is stored, and stores those data strings in a second cache 40, a function which generates a Web file by filling this in a template, and transmits the Web file to a client terminal 12, a function which refers to the maximum horizontal width information and the display width information of each data item when a horizontal scroll event is transmitted from the client terminal 12, and determines data items to be displayed after horizontal scroll, a function which extracts data strings related with the display item for the predetermined number of lines from the first cache 38, and stores them in the second cache 40, and a function which generates the Web file on the basis of this, and transmits the Web file to the client terminal 12. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

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

Originally, in order to use (refer to or update) a database managed by a database server in a client terminal, a dedicated application program has been set up in the client terminal.
This dedicated application program is generally coded in a fourth generation language suitable for the design of so-called user interfaces, such as the arrangement of operation buttons and the configuration of input / display fields, such as Visual Basic (registered trademark). As shown in Patent Document 1, it has an advantage that a screen excellent in visibility and listability can be displayed on a display when referring to and updating a database.
In recent years, however, the inefficiency of installing dedicated application programs on individual client terminals has been recognized, and the use of Web systems centered on the Internet has led to widespread use of general-purpose Web browser programs. There is an increasing demand for using the database to refer to and update databases.

FIG. 1 shows an example of a database usage mode using such a Web system. A front-end server 16 having a Web server function and an AP (Application) server function in the preceding stage of a DB (Database) server 14 is shown. The server 16 is connected to a large number of client terminals 12 via a communication network 18 such as the Internet or an intranet.
Each client terminal 12 has a web browser program set up. When a database use request is sent to the front-end server 16 through this web browser, the front-end server 82 extracts the corresponding data from the DB server 14. Ask.
Then, when data is transmitted from the DB server 14, the front end server 16 processes it into a Web file and transmits it to the client terminal 12.
As a result, the user can browse data on a general-purpose Web browser displayed on the display of the client terminal 12 (see “Table List” in Non-Patent Document 2).
When the user adds or corrects data on the Web browser and an update request is sent from the client terminal 12, the front-end server 16 sends these update information to the DB server 14 to update the database. Request processing.
Sample screen for input processing [Search June 7, 2004] Internet URL: http://it.e-otsuka.com/ryutsu/images/food_sft1.gif 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

  As described above, when the database can be used via the general-purpose web browser program installed in the client terminal 12, the initial cost and running cost can be reduced compared to the case where a dedicated application program is installed in the client terminal 12. And the maintenance can be completed on the server 16 side.

However, general-purpose Web browser programs basically do not have the concept of “page”, so when a database usage screen is displayed on a display, a list of records is paged by a predetermined number of lines. There is a problem that it makes it difficult for a user who is used to the operability of a dedicated application program with a fixed number of display lines to feel uncomfortable.
Actually, when the number of records is large, operation buttons such as “registration” and “deletion” arranged below the last line are displayed as is clear from the “form field designation” screen of Non-Patent Document 2. Therefore, it becomes necessary to perform vertical scrolling of the screen itself many times, and the user feels great stress.

In addition, if the number of data items included in the record is large, it is possible to display hidden data items by repeating horizontal scrolling in the right direction on the Web browser. The part other than is hidden at the left edge of the display, and the entire image of the screen is lost.
By defining a scroll area inside the screen, it is possible to scroll horizontally only within that area, but it is not possible to switch the display contents on an item-by-item basis. There is also a design problem due to the display of items that are cut off halfway.
In the case of the dedicated application program described above, it is possible to implement a function to horizontally scroll the display contents by item while fixing the outer frame of the data list, so that the record that extends in the horizontal direction without destroying the overall image of the screen It is also possible to switch and display items by item, but this could not be desired by a general-purpose Web browser program.

Furthermore, since the exchange of information between the client terminal 12 and the server 16 increases, the load on the network increases as the number of client terminals 12 increases.
In particular, when a record stored in the DB server 14 has many data items, only a part of the record can be displayed on the client terminal 12 by using a technique called hidden. However, since this is based on the premise that the client terminal 12 and the server 16 are reciprocated even for non-displayed data, the amount of data communication is increased.

  The present invention has been devised to solve the above-described problems, and is based on the assumption that a database managed by a DB server on a Web basis is used, but the user interface on the client terminal side is a dedicated application program. It is an object of the present invention to provide a database utilization technique that can realize a reduction in 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 determines the data items to be displayed in the list on the initial screen by referring to the maximum width information of the list specified by the screen design and the display width information of each data item, and the data list sent from the database server Extracts the data string related to the data item from the first cache stored, stores it in the second cache, extracts the data list in the second cache, and fills the template reflecting the screen design Function to generate a Web file for screen display and this Web file to the client Data to be displayed after the horizontal scrolling by referring to the maximum horizontal width information and the display width information of each data item when a function to be transmitted to the terminal and a horizontal scroll event for the list being displayed are transmitted from the client terminal. A function that determines an item, a function that extracts a data string related to the data item from the first cache, stores it in the second cache, and a data list in the second cache that reflects the screen design 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 “maximum width information of the list” is set in consideration of the resolution in the display of the client terminal, the area ratio of the list in the screen, and the like.
The “horizontal scroll event” refers to moving the display content in the horizontal direction in page units in addition to the left column scroll event and the right column scroll event that require the display content in the list to be moved in the horizontal direction in item units. The concept includes a desired left page scroll event and right page scroll event (the same applies hereinafter).

  The database utilization system according to claim 2 is a database utilization system including a front-end server interposed between a database server and a client terminal, wherein the front-end server defines a list defined by a screen design. A function that determines the data items to be displayed in the list in addition to the fixed display item on the initial screen, by referring to the maximum width information of each item, the display width information of each data item, and the fixed display item information. A function for extracting the data string related to the data item and the data string related to the fixed display item from the first cache in which the data list is stored and storing the data string in the second cache, and the data in the second cache Take out the list, fill it with a template that reflects the screen design, and display the web file for screen display. When the horizontal scroll event for the list being displayed is transmitted from the client terminal, the maximum width information, the display width information of each data item, and A function for referring to the fixed display item information and determining a data item to be displayed in the list in addition to the fixed display item after the horizontal scroll, and a data string and a fixed display item related to the data item from the first cache Extracts the data string and stores it in the second cache, extracts the data list in the second cache, fills it with a template reflecting the screen design, and generates a Web file for screen display after scrolling It is characterized by having a function and a function of transmitting this Web file to the client terminal.

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 is a list defined by a screen design. A first cache storing a data list transmitted from the database server and a function for determining data items to be displayed in the list on the initial screen by referring to the maximum horizontal width information and display width information of each data item From the data items related to the above data items, the number of records corresponding to the number of rows in the list specified by the screen design is extracted, the function of storing in the second cache, and the data list in the second cache are extracted, and the screen A function that generates a Web file for screen display by filling a template that reflects the design, and this When a function for transmitting a Web file to a client terminal and a horizontal scroll event for a list being displayed are transmitted from the client terminal, the maximum horizontal width information and the display width information of each data item are referred to, and after the horizontal scroll A function for determining a data item to be displayed, and a function for extracting the data string related to the data item from the first cache by the number corresponding to the number of rows in the list defined by the screen design 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, generates a Web file for screen display after scrolling, a function that transmits this Web file to the client terminal, When a vertical scroll event is sent from the client terminal to the displayed list, the first key A portion corresponding to each line to be displayed after the vertical scrolling is extracted from the data row related to the data item from the cache, and a function for storing in the second cache and a data list in the second cache are extracted. A feature is that it includes a function of 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 “vertical scroll event” refers to moving the display content in the vertical direction in units of pages in addition to the previous line scroll event and the next line scroll event that require the display content in the list to be moved in the vertical direction. This is a concept including the previous page scroll event and the next page scroll event to be obtained (the same applies hereinafter).

  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 defines a list defined by a screen design. A function that determines the data items to be displayed in the list in addition to the fixed display item on the initial screen, by referring to the maximum width information of each item, the display width information of each data item, and the fixed display item information. From the first cache in which the data list is stored, the data sequence related to the data item and the data sequence related to the fixed display item are extracted by the number corresponding to the number of rows in the list defined by the screen design, and the second The function to store in the cache and the data list in the second cache are taken out, the screen design When a function to generate a web file for screen display by filling in the projected template, a function to send this web file to the client terminal, and a horizontal scroll event for the displayed list from the client terminal are sent, A function for referring to the maximum width information, display width information of each data item, and fixed display item information, and determining a data item to be displayed on the list in addition to the fixed display item after the horizontal scroll; From the above data items and the data columns related to the fixed display items for the number of rows corresponding to the number of rows in the list specified by the screen design and stored in the second cache, and in the second cache The data list is taken out, filled in a template that reflects the screen design, and the web file for screen display after scrolling Function, a function for transmitting the Web file to the client terminal, and a data string and a fixed data related to the data item from the first cache when a vertical scroll event for the list being displayed is transmitted from the client terminal. In the data string corresponding to the display item, a part corresponding to each line to be displayed after the vertical scrolling is extracted and stored in the second cache, and a data list in the second cache is extracted, It is characterized by having a function of generating a Web file for screen display after filling a template and scrolling, and a function of transmitting this Web file to a client terminal.

  The database utilization system according to claim 5 is based on the system according to claims 1 to 4, and further comprises a function in which the front-end server stores a list of records transmitted from the database server in a buffer, and the record A function for extracting a combination of data related to data items that are required to be displayed on the screen design, and a function for storing a data list including the combination of the data in the first cache. It is characterized by.

  The database utilization system according to claim 6 is based on the system according to claims 1 to 5, and further comprises a function in which the front-end server stores a list of records transmitted from the database server in a buffer, and the record And a function of converting at least a part of the data into a general-purpose data type, and a function of storing a data list including the converted data in the first cache.

  The database use program according to claim 7 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 defined by a screen design. Means for determining the data items to be displayed in the list on the initial screen, from the first cache storing the data list transmitted from the database server, with reference to the maximum horizontal width information and the display width information of each data item Extracting the data string related to the above data items, storing it in the second cache, taking out the data list in the second cache, filling in the template reflecting the screen design, and generating the Web file for screen display Means to send this Web file to the client terminal, Means for determining a data item to be displayed after the horizontal scrolling by referring to the maximum horizontal width information and the display width information of each data item when a horizontal scroll event for the list being displayed is transmitted from the ant terminal; Means for extracting a data string related to the data item from one cache, storing it in the second cache, taking out the data list in the second cache, filling the template reflecting the screen design, and displaying the screen after scrolling It is characterized by functioning as means for generating a Web file for use, and means for transmitting the Web file to a client terminal.

  The database use program according to claim 8 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 defined by a screen design. Means for determining the data items to be displayed in the list in addition to the fixed display item on the initial screen, referring to the maximum width information of each item, the display width information of each data item, and the fixed display item information. Means for extracting a data string relating to the data item and a data string relating to the fixed display item from the first cache in which the data list is stored and storing the data string in the second cache; and a data list in the second cache. Take out and fill in a template that reflects the screen design, and display the web file for screen display. Means for generating a file, means for sending this Web file to the client terminal, and when the horizontal scroll event for the list being displayed is sent from the client terminal, the maximum width information, the display width information of each data item, and the fixed Means for determining data items to be displayed in the list other than the fixed display items after the horizontal scrolling, referring to the display item information, a data string related to the data items from the first cache, and data related to the fixed display items Means for extracting columns and storing them in the second cache; means for taking out a data list in the second cache and filling in a template reflecting the screen design to generate a web file for screen display after scrolling; It is characterized by functioning as a means for transmitting a Web file to a client terminal.

  The database use program according to claim 9 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 defined by a screen table defined by a screen design. Means for determining the data items to be displayed in the list on the initial screen, from the first cache storing the data list transmitted from the database server, with reference to the maximum horizontal width information and the display width information of each data item , Means for extracting the number of data rows corresponding to the data items corresponding to the number of rows in the list specified by the screen design, storing in the second cache, taking out the data list in the second cache, A method for creating a Web file for screen display by filling the reflected template. Means for sending a Web file to the client terminal, when a horizontal scroll event is sent from the client terminal to the displayed list, the maximum width information and the display width information of each data item are referred to and displayed after the horizontal scroll. Means for determining a data item to be extracted, means for extracting a data string related to the data item from the first cache by the number corresponding to the number of rows in the list defined by the screen design, and storing the data string in the second cache; The data list in the cache of 2 is taken out, filled in a template reflecting the screen design, and a Web file for screen display after scrolling is generated, the Web file is transmitted to the client terminal, and displayed from the client terminal If a vertical scroll event is sent for a list of the first cache, Means for extracting a portion corresponding to each line to be displayed after the vertical scrolling in the data string relating to the data item, storing it in a second cache, taking out a data list in the second cache, and the template It is characterized by functioning as means for generating a Web file for screen display after filling and scrolling, and means for transmitting the Web file to the client terminal.

  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 defined by a screen table defined by a screen design. Means for determining the data items to be displayed in the list in addition to the fixed display item on the initial screen, referring to the maximum width information of each item, the display width information of each data item, and the fixed display item information. From the first cache in which the data list is stored, the data columns related to the data items and the data columns related to the fixed display items are extracted by the number corresponding to the number of rows in the list specified by the screen design, and the second Means for storing in the cache, fetching the data list in the second cache, screen design If a template that reflects the above is used to generate a Web file for screen display, this Web file is sent to the client terminal, and a horizontal scroll event is sent from the client terminal to the displayed list, the above Means for determining data items to be displayed in the list in addition to the fixed display items after the horizontal scroll, referring to the maximum horizontal width information, the display width information of each data item, and the fixed display item information; Means for extracting data columns related to the data items and data columns related to the fixed display items for the number of rows corresponding to the number of rows in the list defined by the screen design, and storing them in the second cache; a data list in the second cache Is taken out and filled in a template reflecting the screen design to generate a web file for screen display after scrolling Means for transmitting the Web file to the client terminal, and when a vertical scroll event for the list being displayed is transmitted from the client terminal, the data string and the fixed display item relating to the data item are transferred from the first cache. Means for extracting a portion corresponding to each row to be displayed after the vertical scrolling in the corresponding data string, storing 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 11 is based on the program according to claims 7 to 10, further comprising means for storing the front end server in a buffer with a list of records transmitted from the database server. A means for extracting a combination of data relating to a data item that is required to be displayed on the screen design, and a function for storing a data list including the combination of the data in the first cache. Yes.

  A database utilization program according to a twelfth aspect of the invention is based on the program of the seventh to eleventh aspects, and further comprises the front end server, means for storing a list of records transmitted from the database server in a buffer, and the record. It is characterized by functioning as means for converting at least a part of data into a general-purpose data type and means for storing a data list composed of the converted data in the first cache.

According to the database utilization system of claim 1 and the database utilization program of claim 7, the horizontal width of the list based on the maximum width information of the list set in advance according to the screen design and the display width information of each data item. The display range in the direction is determined, and only this display data is extracted from the first cache of the front-end server and transmitted to the client terminal.
In other words, even if the number of data items in the record is large, only the data items that fit within the maximum width are sent and displayed. It is possible to switch the contents in item units. For this reason, there is no need to perform horizontal scrolling of the entire screen or fine adjustment of display contents in the scroll area to display hidden data as in the past, while using a general-purpose web browser program. It is possible to dramatically improve the design of the usage screen.
Further, it is possible to reduce the amount of data communication between the front-end server and the client terminal as compared to the case where all data is transmitted to the client terminal at once as in the past.

  In the database utilization system according to claim 2 and the database utilization program according to claim 8, in addition to the effects described in claims 1 and 7, the setting of fixed display items that are always displayed when the list is scrolled horizontally Has the advantage of being possible.

The database utilization system according to claim 3 and the database utilization program according to claim 9 are based on the maximum width information of the list, the display width information of each data item, and the number of lines information set in advance according to the screen design. Thus, the range of display data in the list is determined, and only this display data is extracted from the first cache of the front-end server and transmitted to the client terminal.
In other words, even if the number of data items and the number of records is large, only the data within the range of the maximum width and the set number of lines is sent and displayed, and if it exceeds this, wait for the horizontal scroll event or vertical scroll event. Since data is transmitted and displayed, the screen layout may be corrupted according to the number of data items and the number of items, and the entire screen must be scrolled horizontally or vertically to display hidden data. In addition, the amount of data communication between the front-end server and the client terminal can be further reduced.

  In the database utilization system according to claim 4 and the database utilization program according to claim 10, in addition to the effects described in claims 3 and 9, setting of fixed display items that are always displayed when the list is scrolled horizontally Has the advantage of being possible.

  According to the database utilization system of claim 5 and the database utilization program of claim 11, in the record delivered from the database server, data that does not need to be displayed on the screen design is excluded in advance, and only data that needs to be displayed is stored. Since it is transmitted to the client terminal, the effect of reducing the communication amount can be further enhanced.

  According to the database utilization system of claim 6 and the database utilization program of claim 12, even if the record passed from the database server includes various types of data, it is converted to a general-purpose data type in advance. Since it is converted, the subsequent processing can be simplified.

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.
The above application program is described in, for example, Java (registered trademark) which is one of object-oriented languages.

A processing procedure when referring to registered data using the system 10 will be described below 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 from this menu, for example, “Department Budget / Actual List”, the processing request unit 24 of the client terminal 12 sends a distribution request for the usage screen related to the service to the front-end server 16. (S12).
In response to this, in the front-end server 16, the application program X1 corresponding to the service is started (S13), 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 request for extracting departmental budget / result information is transmitted from the business processing unit 36 to the DB server 14 (S14).
Then, when a list of records stored in the departmental budget / result database is transmitted from the DB server 14, the business processing unit 36 stores it in the buffer 42 (S15).

On the other hand, the data conversion unit 34 is preset in the screen design as to be displayed in the list of the departmental budget / result list screen from the data items constituting each record stored in the buffer 42. Only data relating to the existing data item is extracted (S16).
For example, as shown in FIG. 6 (a), even if the budget / result database for each department stores budget data and record data for each year in addition to the department code and department name, In order to simplify the display items, the department name, current year's budget and actual results, and results prior to the previous year are displayed, and department codes and budgets prior to the previous year are not displayed Is set, the data conversion unit 34 extracts only the data surrounded by the dotted line in the figure, and generates a data list in which these data are linked as shown in FIG. 6 (b). .
Thus, by thinning out the non-displayed data before transmitting the data to the client terminal 12, useless data is not transmitted to the client terminal 12, and the amount of data communication can be reduced.
Hiding unnecessary data items on the Web browser of the client terminal 12 itself has been realized by using a technique called hidden, but in this case, it is hidden data. However, since the client terminal 12 and the server 16 are reciprocated, the amount of data communication is increased accordingly.

Next, the data conversion unit 34 converts the configuration data of this data list into a general-purpose data type (S17), 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 data list, and program codes for realizing the control unit 30 and the screen generation unit 32 are provided. It can be simplified.

The control unit 30 temporarily stores the data list received from the data conversion unit 34 in the first cache 38 (S18).
Next, the control unit 30 refers to the number-of-line information (for example, 1 page = 5 lines) of the data list set in advance in the program code based on the screen design, and stores the upper 5 stored in the first cache 38. The data list is extracted and stored in the second cache 40 (S19).

On the other hand, the screen generation unit 32 sets the definition information of the data list provided in the screen for the data list stored in the second cache 40 (S20).
This definition information includes at least the following items.
(1) Maximum table width information
(2) Display width information for each data item
(3) Information that identifies fixed display items

The definition information is transmitted to the data list stored in the first cache 38 through the pointer function of the Java (registered trademark) language, so that the control unit 30 can recognize it.
Next, the control unit 30 determines the range of data items to be displayed in the list on the initial screen based on the definition information (1) to (3) (S21).
For example, when the maximum width of the list = 750 dots, the fixed display item = department name, and the display width of each data item is as follows, the control unit 30 determines the department name (200 dots), the 2004 budget (100 Dot), 2004 results (100 dots), 2003 results (200 dots) are recognized as displayable data item ranges.
[Display width of each display item]
Department name: 200 dots Recent budget: 100 dots Recent results: 100 dots Previous year results: 200 dots Each previous year result: 250 dots

  Next, the control unit 30 displays the above display from the top five data lists stored in the first cache 38 in accordance with the number of lines (1 page = 5 lines) specified in the screen design. Data relating to a possible data item range (department name, 2004 budget, 2004 performance, 2003 performance) is extracted and stored in the second cache 40 (S22).

The screen generation unit 32 extracts the display data for one page from the second cache 40, fills it with a template dedicated to the service, generates a Web file for the departmental budget / result list, and the client terminal 12 is transmitted (S23).
As a result, the initial screen of the departmental budget / result list is displayed on the Web browser of the client terminal 12 as shown in FIG. 7A (S24).

As shown in the drawing, a data list 50 is provided on the departmental budget / result list screen.
In the list 50, the budget and actual items for the most recent years (2004) are omitted from the fiscal year, and the words “budget” and “actual” are simply displayed as column names, whereas the previous year (2003). As for the result item, “last year result” is displayed as the column name.
These column names are defined in advance in the screen design, and are described on a Web file template (text file) managed by the screen generation unit 32. The display width of each data item is set according to the length of the column name.

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, a predetermined number of lines (5 lines) are always displayed on the Web browser. The data list is displayed, and the positions of the end button 52 and the print button 54 are fixed on the screen as shown in FIG.
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.

Here, when the user desires to view the past performance information before last year (2003), the right column scroll button 56 is clicked.
As a result, a right column scroll event is transmitted from the processing request unit 24 of the client terminal 12 to the front-end server 16 (S25 in FIG. 4).
Receiving this, the control unit 30 extracts data to be displayed in the list after scrolling the right column from the first cache 38 (S26), and stores it in the second cache 40 (S27).
The range of the display data after the right column scroll is determined by the control unit 30 as follows.

First, since the maximum width is 750 dots and the display width of the “department name” that is a fixed display item is 200 dots, the width that can be assigned to the remaining display items is within 550 dots.
Next, since the display width of the 2002 record is 250 dots, the display width that can be assigned to other display items is within 300 dots.
Further, since the display width of the 2003 actual result is 200 dots and the display width of the 2004 actual result is 100 dots, even if both are displayed, they are within 300 dots.
As a result of the above, the display items after scrolling to the right are the department name, the 2004 results, the 2003 results, and the 2002 results.
Next, the control unit 30 extracts the data related to the above items from the data list stored in the first cache 38 for the top five items, and stores it in the second cache 40.

The screen generation unit 32 extracts the display data after scrolling the right column from the second cache 40, fills the template with the display data, generates a Web file for the departmental budget / result list, and sends it to the client terminal 12. Transmit (S28).
As a result, as shown in FIG. 7B, the departmental budget / result list screen after scrolling the right column is displayed on the Web browser of the client terminal 12 (S29).
In the list 50 on this screen, in addition to the “department” corresponding to the department name as a fixed display item, items of “actual result”, “actual result of last year”, and “actual result of 2002” are displayed.

Here, when the user wishes to view the budget / actual information other than the steel product to the information communication department, the user clicks the next line scroll button 58 of the list 50.
As a result, the next line scroll event is transmitted from the processing request unit 24 of the client terminal 12 to the front end server 16 (S30).
Receiving this, the control unit 30 extracts data to be displayed after scrolling the next line from the first cache 38 (S31), and stores it in the second cache 40 (S32).

The display data after the next line scroll is specifically determined in the following manner.
First, since the display items are not changed, the data of the department name, the 2004 actual result, the 2003 actual result, and the 2002 actual result are recognized as extraction targets, as described above.
Next, data from the non-ferrous product department to the food department arranged in the next line of the information communication department is extracted from the first cache 38 and stored in the second cache 40.

The screen generation unit 32 extracts the display data from the second cache 40 and fills the template with the display data to generate a Web file for the departmental budget / result list after scrolling the next line. Transmit (S33).
As a result, as shown in FIG. 7C, the departmental budget / result list screen after scrolling the next line is displayed on the Web browser of the client terminal 12 (S34).
As shown in the drawing, in the list 50 after scrolling the next line, the data relating to the steel product sector is not displayed, and instead the data relating to the food sector is displayed.

Here, when the user wishes to view the budget for the current fiscal year related to the food department, the user clicks the left column scroll button 60 of the list 50.
As a result, a left column scroll event is transmitted from the processing request unit 24 of the client terminal 12 to the front end server 16 (S35).
Receiving this, the control unit 30 extracts data to be displayed after scrolling the left column from the first cache 38 (S36), and stores it in the second cache 40 (S37).
The display item range after scrolling the left column is recognized as a department name, a 2004 budget, a 2004 result, and a 2003 result according to the same logic as described above.

The screen generation unit 32 extracts the display data from the second cache 40 and fills the template with the display data to generate a Web file for the departmental budget / result list after scrolling the left column. Transmit (S38).
As a result, as shown in FIG. 7D, a departmental budget / result list screen is displayed on the Web browser of the client terminal 12 (S39).
As shown in the figure, in this list 50 after scrolling to the left, the current year budget for the food sector is displayed.
It goes without saying that when the user clicks the previous line scroll button 62, the initial screen of FIG. 7A is displayed.

When the user clicks the right page scroll button 64 of the list 50 on the initial screen of FIG. 7A, an event of right page scroll is sent from the processing request unit 24 of the client terminal 12 to the front-end server 16. It is transmitted (S40 in FIG. 5).
Here, the right-page scroll event is a request to replace all display items in the list 50 with the non-display data existing on the right side. Data to be displayed in the list after page scrolling is extracted (S41) and stored in the second cache 40 (S42).
The range of display data after scrolling the right page is determined by the control unit 30 as follows.

First, since the maximum width of the list 50 is 750 dots and the display width of the “department name” that is a fixed display item is 200 dots, the display width that can be assigned to the remaining display items is within 550 dots.
Next, the display width of the 2002 results and the 2001 results reaches 250 dots in total, reaching a total of 500 dots, and the 2000 results cannot be included in the display range.
As a result, the display items after scrolling the right page are the department name, the 2002 results, and the 2001 results.
Next, the control unit 30 extracts the data related to the above items from the data list stored in the first cache 38 for the top five items, and stores it in the second cache 40.

The screen generation unit 32 extracts the display data after scrolling the right page from the second cache 40, fills the template with the display data, generates a Web file for the departmental budget / result list, and sends it to the client terminal 12. Transmit (S43).
As a result, as shown in FIG. 8, the departmental budget / result list screen after scrolling the right page is displayed on the Web browser of the client terminal 12 (S44).
In the list 50 on this screen, items of “department”, “2002 results”, and “2001 results” are displayed.

When the user clicks the next page scroll button 66 of the list 50 on the initial screen of FIG. 7A, the next page scroll event is sent from the processing request unit 24 of the client terminal 12 to the front-end server 16. It is transmitted (S45).
Here, the next page scroll event is a request to replace all display items in the list 50 with the data items existing in the downward direction. Data to be displayed in the list after page scrolling is extracted (S46) and stored in the second cache 40 (S47).
The range of display data after scrolling the next page is determined by the control unit 30 as follows.

First, since there is no change in the display items, as in the above case, the data of the department name, the 2004 budget, the 2004 results, and the 2003 results are certified as extraction targets.
Next, 5 cases from the food department on the next line of the information and communication department should be extracted, but only 9 records are originally stored in the departmental budget / result database. The control unit 30 extracts the data for the four items after the food sector from the first cache 38 and stores them in the second cache 40.

The screen generation unit 32 extracts the display data from the second cache 40 and fills the template with the display data to generate a Web file for the departmental budget / result list after scrolling the next page. Transmit (S48).
As a result, the departmental budget / result list screen is displayed on the Web browser of the client terminal 12 as shown in FIG. 9 (S49).
As shown in the drawing, in the list 50 after scrolling to the next page, the data related to the steel products to the information and communication department is hidden, and instead the data related to the food to the machinery department is displayed.

The column names in the screen data list 50 are expected to be changed by reviewing the screen design, and the display width varies depending on the data items accordingly. Further, it may be necessary to change the display width in accordance with the length of data to be displayed.
On the other hand, as described above, the maximum width of the data list 50 and the display width of each display item are set in the definition file managed by the screen generation unit 32, and are displayed by referring to the control unit 30. If it is configured to determine the data items to be changed, it is possible to cope with changes in the screen design simply by correcting the description in the definition file, and it is necessary to modify the program code for realizing the control unit 30 There is no.
For example, instead of simply displaying “Budget” for the current year's budget as shown above, if the screen design is changed to display “2004 Budget” for a long time, the item following “Department” (the most recent budget item) It is sufficient to modify the description on the template so that the column name of () matches the field name of the database, and there is no need to modify the code of the control unit 30.

However, according to the present invention, the definition information held by the screen generation unit 32 is set in the data list stored in the second cache 40 as described above, and this is set using the pointer function of Java (registered trademark). It is not limited to the system in which the information is transmitted to the original data list stored in the cache 38 and the control unit 30 recognizes the definition information.
For example, the maximum width information of the list, the display width information of each data item, and the information for specifying the fixed display items are described in advance in the program for realizing the control unit 30, so that the screen generating unit 32 It is also possible to configure so that the control unit 30 can independently determine the display data range of the list 50 without waiting for definition information to be provided.

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 10 lines / page is adopted in a reference screen of a certain database, the control unit 30 and the screen generation unit 32 are required to process 10 data as one page.
On the other hand, the business processing unit 36 is completely separated from the screen design, and can simply concentrate on the process of requesting the DB server 14 to extract records and storing the transmitted records in the buffer 42.
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 when the screen design is changed, it is sufficient to modify the screen templates and definition files managed by the screen generation unit 32, the code of the control unit 30 and the data conversion unit 34, and the code of the business processing unit 36. Does not need to be corrected.

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 the part that specifies the number of hit lines and the range of data items to be displayed.
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.

In the above, an example in which horizontal scrolling and vertical scrolling are possible is shown in the data list 50, but the present invention is not limited to this.
For example, when the number of records to be displayed is originally small and frequent vertical scrolling is not required, the control unit 30 extracts all necessary data items from the data list in the first cache 38, and the second Output to the cache 40.
On the other hand, the screen generation unit 32 fills the data as it is into the template to generate a Web file, and transmits it to the client terminal 12.
As a result, the vertical scroll button is omitted on the browser of the client terminal 12, and the list 50 having only the horizontal scroll button is displayed.

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 this system. It is a flowchart which shows the process sequence in this system. It is a flowchart which shows the process sequence in this system. It is a conceptual diagram which shows the data extraction process in a data converter. It is a layout figure which shows the structural example of the screen in a client terminal. It is a layout figure which shows the structural example of the screen in a client terminal. It is a layout figure which shows the structural example of the screen in a client terminal.

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 List of data
52 Exit button
54 Print button
56 Right column scroll button
58 Next line scroll button
60 Left column scroll button
62 Previous scroll button
64 Right page scroll button
X1, X2, X3 application program

Claims (12)

A database utilization system comprising a front-end server interposed between a database server and a client terminal,
The front-end server
A function for determining the data items to be displayed in the list on the initial screen with reference to the maximum width information of the list specified by the screen design and the display width information of each data item,
A function of extracting a data string related to the data item from a first cache storing a data list transmitted from a database server and storing the data string in a 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 determining a data item to be displayed after the horizontal scrolling by referring to the maximum horizontal width information and the display width information of each data item when a horizontal scroll event is transmitted from the client terminal to the displayed list;
A function of extracting a data string related to the data item 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 after scrolling;
A function to send this web file to the client terminal,
A database utilization system characterized by 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 determines the data items to be displayed in the list in addition to the fixed display items on the initial screen by referring to the maximum width information of the list specified by the screen design, the display width information of each data item, and the fixed display item information. When,
A function of extracting a data string relating to the data item and a data string relating to the fixed display item from the first cache storing the data list transmitted from the database server, and storing the data string 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 horizontal scroll event is sent from the client terminal to the displayed list, the maximum horizontal width information, the display width information of each data item, and the fixed display item information are referred to, and after the horizontal scroll, other than the fixed display item A function to determine the data items to be displayed in the list,
A function of extracting the data string related to the data item and the data string related to the fixed display item from the first cache and storing them 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 after scrolling;
A function to send this web file to the client terminal,
A database utilization system characterized by 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 for determining the data items to be displayed in the list on the initial screen with reference to the maximum width information of the list specified by the screen design and the display width information of each data item,
From the first cache in which the data list transmitted from the database server is stored, the data columns related to the data items are extracted by the number corresponding to the number of rows in the list defined by the screen design, and stored in the second cache. The function to store,
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 determining a data item to be displayed after the horizontal scrolling by referring to the maximum horizontal width information and the display width information of each data item when a horizontal scroll event is transmitted from the client terminal to the displayed list;
A function of extracting a data string related to the data item from the first cache by the number corresponding to the number of rows in the list defined by the screen design, and storing the data 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 after scrolling;
A function to send this web file to the client terminal,
When a vertical scroll event is sent from the client terminal to the list being displayed, the portion corresponding to each row to be displayed after the vertical scroll is extracted from the first cache from the data row related to the data item. A function to store in the second cache;
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: 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 determines the data items to be displayed in the list in addition to the fixed display items on the initial screen by referring to the maximum width information of the list specified by the screen design, display width information of each data item, and fixed display item information When,
From the first cache in which the data list transmitted from the database server is stored, the number of data columns corresponding to the number of rows of the list defined by the screen design for the data columns related to the data items and the data columns related to the fixed display items. The ability to extract and store in a 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 horizontal scroll event is sent from the client terminal to the displayed list, the maximum horizontal width information, the display width information of each data item, and the fixed display item information are referred to, and after the horizontal scroll, other than the fixed display item A function to determine the data items to be displayed in the list,
A function of extracting the data string related to the data item and the data string related to the fixed display item from the first cache by the number corresponding to the number of rows in the list specified by the screen design, and storing the data string 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 after scrolling;
A function to send this web file to the client terminal,
When a vertical scroll event is sent from the client terminal to the list being displayed, it is displayed after the vertical scroll in the data row corresponding to the data item and the data row corresponding to the fixed display item from the first cache. A function of extracting a portion corresponding to each power line and storing it in a second cache;
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 that stores a list of records sent from the database server in a buffer;
A function for extracting 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 a data list including a combination of the data in the first cache;
The database utilization system according to any one of claims 1 to 4, further comprising: 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;
The database utilization system according to any one of claims 1 to 5, 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 determining the data items to be displayed in the list on the initial screen with reference to the maximum width information of the list defined by the screen design and the display width information of each data item;
Means for extracting a data string related to the data item from a first cache storing a data list transmitted from a database server and storing the data string in a 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 determining a data item to be displayed after the horizontal scrolling by referring to the maximum horizontal width information and the display width information of each data item when a horizontal scroll event for the list being displayed is transmitted from the client terminal;
Means for extracting a data string related to the data item from the first cache and storing it in the second cache;
Means for taking out the data list in the second cache, filling the template reflecting the screen design, 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 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 determining the data items to be displayed in the list other than the fixed display items on the initial screen by referring to the maximum width information of the list specified by the screen design, the display width information of each data item, and the fixed display item information ,
Means for extracting a data string relating to the data item and a data string relating to the fixed display item from the first cache storing the data list transmitted from the database server, and storing the data string 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 horizontal scroll event is sent from the client terminal to the displayed list, the maximum horizontal width information, the display width information of each data item, and the fixed display item information are referred to, and after the horizontal scroll, other than the fixed display item Means for determining the data items to be displayed in the list,
Means for extracting a data string relating to the data item and a data string relating to the fixed display item from the first cache and storing them in a second cache;
Means for taking out the data list in the second cache, filling the template reflecting the screen design, 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 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 determining the data items to be displayed in the list on the initial screen with reference to the maximum width information of the list defined by the screen design and the display width information of each data item;
From the first cache in which the data list transmitted from the database server is stored, the data columns related to the data items are extracted by the number corresponding to the number of rows in the list defined by the screen design, and stored in the second cache. Means for storing,
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 determining a data item to be displayed after the horizontal scrolling by referring to the maximum horizontal width information and the display width information of each data item when a horizontal scroll event for the list being displayed is transmitted from the client terminal;
Means for extracting a data string related to the data item from the first cache for the number of rows corresponding to the number of rows in the list defined by the screen design, and storing it in the second cache;
Means for taking out the data list in the second cache, filling the template reflecting the screen design, and generating a web file for screen display after scrolling;
Means to send this web file to the client terminal,
When a vertical scroll event is sent from the client terminal to the list being displayed, the portion corresponding to each row to be displayed after the vertical scroll is extracted from the first cache from the data row related to the data item. Means for storing in a 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;
Means to send this web file to the client terminal,
Database utilization program characterized by functioning 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 determining the data items to be displayed in the list other than the fixed display items on the initial screen by referring to the maximum width information of the list specified by the screen design, the display width information of each data item, and the fixed display item information ,
From the first cache in which the data list transmitted from the database server is stored, the number of data columns corresponding to the number of rows of the list defined by the screen design for the data columns related to the data items and the data columns related to the fixed display items. Means for extracting and storing in a 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 horizontal scroll event is sent from the client terminal to the displayed list, the maximum horizontal width information, the display width information of each data item, and the fixed display item information are referred to, and after the horizontal scroll, other than the fixed display item Means for determining the data items to be displayed in the list,
Means for extracting from the first cache a data sequence related to the data item and a data sequence related to the fixed display item for the number of rows corresponding to the number of rows in the list defined by the screen design, and storing in the second cache;
Means for taking out the data list in the second cache, filling the template reflecting the screen design, and generating a web file for screen display after scrolling;
Means to send this web file to the client terminal,
When a vertical scroll event is sent from the client terminal to the list being displayed, it is displayed after the vertical scroll in the data row corresponding to the data item and the data row corresponding to the fixed display item from the first cache. Means for extracting a portion corresponding to each power line and storing it in a 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;
Means to send this web file to the client terminal,
Database utilization program characterized by functioning as The above front-end server
Means for storing a list of records sent from the database server in a buffer;
Means for extracting a combination of data relating 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 a combination of the data;
The database utilization program according to any one of claims 7 to 10, wherein 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;
The database utilization program according to any one of claims 7 to 11, wherein

Images