JP2005173823A - Web application, and data sharing method and program thereof - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a Web application capable of preventing a reduction in response speed by minimizing accesses to a shared file system, and a data sharing method and a program therefor. <P>SOLUTION: A network 100 comprises Web clients 101, 102, and 103, and Web servers 111, 112 and 113 having local files 111a, 112a and 113a, respectively, and sharing a shared file 115, which constitute a Web server cluster for executing the Web application. The Web application assigns processing of an HTTP request from a Web client for a session to any one of the Web servers while the session is valid, and copies shared data in the shared file 115 to a local file of the session Web server when starting the session. Further, when the processing of the HTTP request from the session Web client is not a processing involving updating of a parameter necessary for creation of an HTML page, the Web application uses only a copied parameter to create the HTML page. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a web application and its data sharing method and program, and more particularly to a web application and its data sharing method and program that operate on a web server cluster composed of a plurality of web servers.

  Conventionally, when a Web application is operated on a Web server cluster composed of a plurality of Web servers, information necessary for the Web application to operate is shared using special hardware such as a shared disk device. Although it is normal (see, for example, Patent Document 1), since a shared disk device or the like is generally expensive, there has been a demand for operating a Web application on a Web server cluster without using such a device.

  On the other hand, in the OS (operating system), among files held by each of the Web servers on the Web server cluster, files that cannot be accessed from other Web servers (hereinafter referred to as “local files”) are stored on the Web. There is a function of changing the setting to a file (hereinafter referred to as “shared file”) that can be accessed from all of the Web servers on the server cluster.

Therefore, by using this OS function, the Web server on the Web server cluster can share information necessary for the operation of the Web application without using special hardware such as a shared disk device. it can.
Japanese Patent Laid-Open No. 11-96071

  However, the process of accessing a shared file takes longer than the process of each of the web servers on the web server cluster accessing its own local file. Therefore, if the frequency at which the web server accesses the shared file increases, There is a problem that the response speed of the application decreases.

  It is an object of the present invention to provide a Web application, a data sharing method, and a program that can prevent the response speed from being lowered by minimizing the access of the Web server to the shared file.

  The Web application according to claim 1 is a Web application configured by a plurality of Web servers and executing processing for requesting an HTTP request received from a Web client in session on a Web server cluster that performs a session with a plurality of Web clients. The Web server cluster includes a first file shared by all of the plurality of Web servers and a file included in each of the plurality of Web servers, and the second file cannot be accessed from other Web servers. A Web server that executes a request process for an HTTP request from any one of the plurality of Web clients at the start of a session with any one of the plurality of Web clients until the session ends. The plurality of W b) session allocation processing means for allocating to any one of the servers, and when the HTTP request from the Web client in the session is transmitted to the Web server cluster, the second Web server has the second When it is not necessary to update the data of the first file by the request processing of the HTTP request from the Web client in the session and the data copy means for copying the data of the first file to the file, the second file Request processing executing means for executing the request processing using data copied to a file.

  When the web application according to claim 2 needs to update data of the first file by request processing of an HTTP request from the web client during the session in the web application according to claim 1, the first application Both the file and the data of the second file are updated.

  The data sharing method according to claim 3, comprising: a plurality of Web servers, and data sharing for executing a request process for an HTTP request received from a Web client in session on a Web server cluster that performs a session with a plurality of Web clients. In the method, the Web server cluster includes a first file shared by all of the plurality of Web servers and a file included in each of the plurality of Web servers, and cannot be accessed from other Web servers. 2, and at the start of a session with any one of the plurality of Web clients, the HTTP request request processing from any one of the plurality of Web clients is executed until the session ends. Any of the plurality of Web servers A session time allocation step for allocating to one, and when the HTTP request from the web client in the session is transmitted to the web server cluster, the second file of the allocated web server is added to the second file. When it is not necessary to update the data of the first file by the data copy step of copying the data of one file and the request processing of the HTTP request from the Web client during the session, the data is copied to the second file. And a request processing execution step for executing the request processing using the obtained data.

  The data sharing method according to claim 4, wherein in the data sharing method according to claim 3, when it is necessary to update data of the first file by request processing of an HTTP request from the Web client in the session, The data of the first file and the second file are updated together.

  According to a fifth aspect of the present invention, there is provided a data sharing method for executing processing for requesting an HTTP request received from a Web client in a session on a Web server cluster configured by a plurality of Web servers and performing a session with a plurality of Web clients. In the program that is executed by a computer, the Web server cluster includes a first file shared by all of the plurality of Web servers, and a file included in each of the plurality of Web servers, A second file that cannot be accessed from a Web server, and at the start of a session with any one of the plurality of Web clients, from any one of the plurality of Web clients until the session ends. Execute HTTP request request processing A session processing allocation module that allocates a Web server to be assigned to any one of the plurality of Web servers, and when the HTTP request from the Web client in the session is transmitted to the Web server cluster, the allocated Web It is necessary to update the data of the first file by request processing of the HTTP request from the Web client in the session and the data copy module that copies the data of the first file to the second file of the server. A request processing execution module that executes the request processing using the data copied to the second file.

  According to the Web application according to claim 1, the data sharing method according to claim 3, and the program according to claim 5, at the start of a session with any one of a plurality of Web clients, until the session ends, A web server that executes processing for requesting an HTTP request from any one of the plurality of web clients is allocated to any one of the plurality of web servers, and an HTTP request from the web client in the session is transmitted to the web server cluster. When this is done, it is necessary to copy the data of the first file to the second file of the allocated Web server and update the data of the first file by the request processing of the HTTP request from the Web client during the session If not, copy to second file Since execution request processing using the data, by minimizing the access of the Web server to the shared file, it is possible to prevent deterioration of response speed.

  According to the Web application according to claim 2, the data sharing method according to claim 4, and the program according to claim 5, the data of the first file is updated by the request processing of the HTTP request from the Web client during the session. When necessary, both the data of the first file and the second file are updated. Therefore, it is possible to prevent the response speed from being lowered by minimizing the access of the Web server to the shared file.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a diagram showing a schematic configuration of a network that executes a Web application according to an embodiment of the present invention.

  In FIG. 1, a network 100 includes Web clients 101, 102, and 103 in which Web browsers are operating, Web servers 111, 112, and 113 that constitute a Web server cluster 110, a document management server 121, a relational database 125, and the like. These are connected to each other by local area networks 131 and 132.

  The relational database 125 stores folder and document attribute information and documents. The document management server 121 accesses the relational database 125, registers the document in the database, and manages the document. The Web server 111 also has a shared file 115 (second file). The shared file 115 can be accessed from other Web servers 112 and 113 by the file system sharing function of the operating system (OS). It is configured. Further, each Web server 111, 112, 113 has local files 111a, 112a, 113a (first files) that are prohibited from direct access from other computers.

  The Web clients 101, 102, and 103 are configured to receive an HTTP response from the Web servers 111, 112, and 113 in the Web server cluster 110 by sending an HTTP request to the Web server cluster 110.

  The Web server cluster 110 receives an HTTP request from the Web clients 101, 102, and 103, allocates the request processing to any of the Web servers 111, 112, and 113, and assigns the allocated processing to each Web server 111. , 112, 113 are operated.

  FIG. 2 is a diagram used for explaining the nodes of the Web application running on the Web server cluster 110 in FIG.

  In FIG. 2, the Web application of the Web server cluster 110 includes three nodes: a Web cluster control unit 211, a Web server unit 215, and a document management unit 220.

  The Web cluster control unit 211 performs the above-described allocation processing or transmits an HTTP response created by any of the Web servers 111, 112, and 113 to a predetermined Web client (101, 102, 103).

  The web server unit 215 performs general processing by the web servers 111, 112, and 113. Specifically, in response to an HTTP request from the Web client 101, 102, 103, the requested content such as an HTML page or an image file is transmitted as an HTTP response to the Web client, or a program execution request is sent from the Web client. In response, the program is executed, and the result is sent to the Web client as an HTTP response.

  The document management unit 220 includes a control unit 221, a request analysis unit 223, a shared data access unit 224, and a request processing unit 226.

  The control unit 221 controls data transmission / reception with the Web server unit 215 and overall processing of the Web server cluster 110. In the control unit 221, the request execution unit 223 analyzes the program execution request content of the HTTP request requested from the Web client 101, 102, 103 via the Web server 111, 112, 113, and based on the analyzed result, The shared data access unit 224, the local data access unit 225, the request processing unit 226, etc. are controlled to execute the program for which the above execution request has been made, and finally the HTML page generation unit 227 generates an HTML page corresponding to the execution content. create. In addition, the control unit 221 requests the Web server unit 215 to return an HTTP response to the Web clients 101, 102, and 103.

  The request analysis unit 223 analyzes the program execution request parameter of the HTTP request transmitted from the Web client 101, 102, 103 via the Web server unit 215, and analyzes the type of execution request. The types of execution requests include Web application activation processing, login processing, logout processing, display format change processing, document list processing, document search processing, document registration processing, and document deletion processing.

  The shared data access unit 224 accesses the shared file 115 disclosed on the Web server 111, reads data from the shared file 115, and writes data to the shared file 115. The shared file 115 stores information necessary for creating an HTML page for each user who can use the Web application. For example, the number of documents displayed on the document list screen, the item names displayed on the document list screen, and the like correspond to this.

  The local data access unit 225 accesses a local file that stores data necessary for the Web servers 111, 112, and 113 to create an HTML page within a session. As local data, in addition to the information of the shared file 115, information that is frequently updated in a session, an image file that is temporarily created, and the like are stored.

  The request processing unit 226 communicates with the document management server 121 according to the type of execution request analyzed by the request analysis unit 223, and performs login processing, logout processing, document list processing, document search processing, document registration processing, Processing such as document deletion processing is actually performed. Further, in the display format change process, the shared data access unit 224 and the local data access unit 225 also perform a process of writing to the local file and the shared file 115.

  The HTML creation unit 227 is a part that creates an HTML page based on the local data acquired by the local data access unit 225 based on the result of the processing performed by the request processing unit 226. Specifically, an HTML page is created based on the number of documents displayed on the document list screen, information on the document list screen, and the like.

  FIG. 3 is a flowchart of document management processing by the Web application of FIG.

  In FIG. 3, first, the Web application determines whether or not there is a session ID in the HTTP request transmitted from any one of the Web clients 101, 102, and 103 to the Web cluster server 110 (step S310). Hereinafter, a Web client that has transmitted an HTTP request to the Web cluster server 110 is referred to as a “session Web client”. Here, it is assumed that at least a session ID and a processing request command are assigned as parameters to the HTTP request transmitted from the session Web client. However, no parameters are assigned to the HTTP request transmitted when starting the Web application.

  As a result of the determination in step S310, when there is no session ID in the HTTP request, the Web application determines that a session has been performed for the first time with this session Web client, and any one of the Web servers 111, 112, and 113 is assigned to this session. A session setting file is created in a local file of the session Web server by allocating to a Web server (hereinafter referred to as “session Web server”) that processes an HTTP request from the Web client (step S311). Here, the session setting file is a file specified by the session ID, and is created under a predetermined session management folder in the local file of the session Web server. At this point, only an empty file is created.

  Subsequently, an HTML page of a login screen (FIG. 4) for inputting a user name, a password, and the like necessary for login on the session Web server is created, and this HTML page is returned to the session Web client (step S370). Exit. At this time, a session ID that identifies the session setting file created in step S311 is assigned as a parameter to the HTTP response to be transmitted. Thereafter, while this session is valid, that is, until the setting information in the local file is deleted in step S341 described later, the same session is used for the HTTP request and the HTTP response transmitted / received between the session Web client and the session Web server. ID is attached.

  If it is determined in step S310 that the HTTP request has a session ID, the session setting file specified by the session ID is included in any one of the local files of the Web servers 111, 112, and 113 in the Web server cluster 110. It is determined whether or not there is (step S320). As a result of this determination, when the session setting file does not exist, the Web application determines that the HTTP request has been transmitted by unauthorized access, and displays an HTML page that warns of unauthorized access as the Web server 111, 112, The HTML page is created in any one of 113, and this HTML page is returned to the session Web client (step S370), and this process is terminated.

  If it is determined in step S320 that the session setting file is present, the Web application determines that the HTTP request is a valid session and analyzes the processing request command given as a parameter of the HTTP request. Thus, it is sequentially determined whether the processing request command is a login process (step S330), a logout process (step S340), and a display format change process (step S350).

  If the result of determination in step S330 is that the HTTP request processing request command is login processing, the following login processing is executed.

  In the Web application, the user name and password are input to the HTML page of the login screen on the session Web client side, the OK button is pressed, and an HTTP request including a processing request command including login processing as a parameter is sent to the Web server cluster 110. When the request is returned, the HTTP request processing request command is determined to be login processing.

  The login process is performed after the HTML page of the above-described login screen created by the session Web server after the process of step S311 is transmitted to the session Web client.

  In the login process, first, the Web application determines whether or not the combination of the user name and password input on the login screen in FIG. 4 is in the shared file 115 on the session Web client side (step S331). As a result of the determination, when the above combination is in the shared file 115, it is determined that the login process has been normally performed, and the setting information (shared data) for the user in the shared file 115 is specified by this session ID. The shared data is acquired in the local file by storing in the session setting file to be executed (step S332). Thereafter, HTML pages of the document list screen (FIG. 5) and its display format change screen (FIG. 7) are created based on the setting information in the acquired shared data, and these HTML pages are returned to the session Web client ( Step S370), the process is terminated.

  As a result of the determination in step S331, if the above combination is not in the shared file 115, it is determined that the HTTP request using the login process as a parameter has been transmitted by unauthorized access, and HTML is issued to warn of unauthorized access. A page is created and returned to the session Web client (step S370), and this process ends.

  If the result of determination in step S340 is that the HTTP request processing request command is logout processing, the following logout processing is executed.

  In the Web application, when the logout button 500 on the HTML page of the document list screen is pressed on the session Web client side, an HTTP request including a processing request command including logout processing as a parameter is returned to the Web server cluster 110. It is determined that the HTTP request processing request command is logout processing.

  The logout process is performed after the HTML page of the document list screen (FIG. 5) is transmitted to the session Web client by the login process.

  In the logout process, first, the Web application searches for a session setting file specified by the session ID from the local file of the session Web server, and deletes the session information created in the found session setting file. (Step S341). Thereafter, an HTML page for notifying the end of the session is created on the session Web server, this HTML page is returned to the session Web client (step S370), and this process ends.

  If the result of determination in step S350 is that the HTTP request processing request command is display format change processing, the following display format change processing is performed.

  When the display setting of the document list screen is changed on the HTML page of the display setting change screen (FIG. 7) on the session Web client side, for example, as shown in FIG. When the upper OK button is pressed after changing the value on the right side of “Maximum Number of Documents to Display in a Page” from 10 to 20 using the scroll bar to change the number of documents displayed on one page Then, an HTTP request having a process request command including the session ID and display format change process as a parameter is returned to the Web server cluster 110. At this time, it is determined that the processing request command for the HTTP request is display format change processing.

  The display format change process is performed after the HTML page of the document list screen (FIG. 5) is transmitted to the session Web client by the login process.

  In the display format changing process, first, the Web application stores the content changed on the session Web client side on the display setting change screen in FIG. 7 in the session setting file specified by the session ID, and also the shared file 115. The setting value of the data set for each user is changed (step S351).

  Thereafter, the Web application creates a document list screen (FIG. 6) on the session Web server based on the changed setting value, transmits this HTML page to the session Web client (step S370), and ends this processing. .

  If it is determined in steps S330, S340, and S350 that the process is not one of the above-described login process, logout process, and display format change process, other processes are executed (step S360).

  Specifically, the Web application determines that the HTTP request processing request command is other processing, that is, other than login processing, logout processing, and display format change processing, and executes the processing. Thereafter, an HTML page indicating the processing result is created, this HTML page is transmitted to the session Web client (step S370), and this processing is terminated.

  In the above embodiment, the case where document management is performed on the Web server cluster 110 has been described as an example. However, the processing performed on the Web server cluster 110 is not limited to document management, and sharing in a shared file A rough flow of sharing data between the Web servers 111, 112, and 113 may be a process as shown in the flowchart of FIG.

  Specifically, as shown in FIG. 8, first, when an HTTP request is received, it is determined whether or not the session is in progress (step S810). If the result of this determination is that the session is not in progress, that is, the session is this HTTP request. When one of the Web servers 111, 112, and 113 is determined to have started, the session Web server allocates one of the Web servers 111, 112, and 113 to the session Web server for the session Web client, and transfers the session Web from the shared file 115 to the local file of the session Web server. The shared data necessary for processing the request of the HTTP request from the client is copied (step S830), an HTML page is created based on the information stored in the local file, and returned to the session Web client (step). S870), the process is terminated. At the start of the session, only the session Web server may be allocated, and when the next session is from the session Web client, the process of step S830 may be performed.

  As a result of the determination in step S810, it is determined whether or not the shared data of the shared file needs to be updated in order to perform HTTP request request processing during the session (step S820). When it is necessary to update both the data stored in the local file and the data of the shared file 115 (step S840), the HTTP request request processing is then performed based on the updated data in the local file. This is executed by the server (step S850). Thereafter, an HTML page indicating the processing result is created and sent back to the session Web client (step S870), and this processing is terminated. However, in this case, in order to minimize the update of the shared data in the shared file 115, it is preferable that information that is frequently updated is managed only by the local file.

  As a result of the determination in step S820, when update is not necessary (NO in step S820), the HTTP request request process is executed on the session Web server based on the shared data copied in step S830 in the local file (step S860). ), An HTML page indicating the processing result is created and transmitted to the session Web client (step S870), and the process is terminated.

  As described above, according to the present embodiment, when the Web application determines that the session is started by receiving this HTTP request (NO in step S810), the shared data in the shared file 115 is stored in the local of the session Web server. If it is copied to a file (step S830) and during the subsequent session (YES in step S810), and the HTTP request process is not a process that involves updating shared data (NO in step S820), the shared data copied to the local file Since the request processing of the HTTP request is performed based on (Step S860), the access to the shared file can be minimized, and the response speed can be prevented from being lowered.

  The present invention realizes the functions of the above-described embodiment by the program code read from a medium such as any one of the Web servers 111, 112, and 113, and the storage medium that stores the program code. The medium constitutes the present invention. As a medium such as a storage medium for supplying the program code, for example, a floppy (registered trademark) disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a CD-RW, a DVD-ROM, a DVD- RAM, DVD-RW, DVD + RW, magnetic tape, nonvolatile memory card, ROM, download via network, or the like can be used.

  Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an OS or the like running on the computer performs an actual process based on an instruction of the program code. Needless to say, the present invention includes a case where the function of the above-described embodiment is realized by performing part or all of the processing.

  Furthermore, after the program code read from a medium such as a storage medium is written in a memory provided in a function expansion board inserted in the computer or a function expansion unit connected to the computer, based on the instruction of the program code, Needless to say, the present invention includes the case where the CPU or the like provided in the function expansion board or function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

It is a figure which shows schematic structure of the network which performs the web application which concerns on embodiment of this invention. It is a figure used for demonstrating the node of the Web server cluster 110 in FIG. 2 is a flowchart of document management processing by a Web application running on the Web server cluster 110 in FIG. 1. It is an example of the login screen produced by the process of step S370 of FIG. It is an example of the document list screen produced by the process of step S370 of FIG. It is an example of the document list screen produced by the process of step S370 of FIG. It is an example of the display setting change screen created by the process of step S370 of FIG. 2 is a flowchart showing an outline of data sharing processing by a Web application running on the Web server cluster 110 in FIG. 1.

Explanation of symbols

100 Network 101, 102, 103 Web client 111a, 112a, 113a Local file 110 Web server cluster 111, 112, 113 Web server 115 Shared file 131, 132 Local area network

Claims (5)

In a Web application that is configured by a plurality of Web servers and executes processing for requesting an HTTP request received from a Web client in session on a Web server cluster that performs a session with a plurality of Web clients.
The web server cluster includes a first file shared by all of the plurality of web servers and a second file that is included in each of the plurality of web servers and cannot be accessed from other web servers. And
At the start of a session with any one of the plurality of Web clients, a Web server that executes processing for requesting an HTTP request from any one of the plurality of Web clients until the session ends. A session processing allocation means to allocate to any one of the servers;
Data copy means for copying data of the first file to the second file of the allocated Web server when an HTTP request from the Web client in the session is transmitted to the Web server cluster; ,
Request processing for executing the request processing using the data copied to the second file when it is not necessary to update the data of the first file by the request processing of the HTTP request from the Web client in the session A Web application comprising execution means.   When it is necessary to update data of the first file by request processing of an HTTP request from the Web client during the session, the data of the first file and the second file are updated together. The web application according to claim 1. In a data sharing method for executing processing for requesting an HTTP request received from a Web client in a session on a Web server cluster configured by a plurality of Web servers and performing a session with a plurality of Web clients.
The web server cluster includes a first file shared by all of the plurality of web servers and a second file that is included in each of the plurality of web servers and cannot be accessed from other web servers. And
At the start of a session with any one of the plurality of Web clients, a Web server that executes processing for requesting an HTTP request from any one of the plurality of Web clients until the session ends. A session time allocation step to allocate to any one of the servers;
A data copy step of copying data of the first file to the second file of the allocated Web server when an HTTP request from the Web client in the session is transmitted to the Web server cluster; ,
Request processing for executing the request processing using the data copied to the second file when it is not necessary to update the data of the first file by the request processing of the HTTP request from the Web client in the session And a data sharing method.   When it is necessary to update data of the first file by request processing of an HTTP request from the Web client during the session, the data of the first file and the second file are updated together. The data sharing method according to claim 3. A computer is configured to execute a data sharing method for executing a request process for an HTTP request received from a Web client in a session on a Web server cluster configured by a plurality of Web servers and performing a session with a plurality of Web clients. In the program to
The web server cluster includes a first file shared by all of the plurality of web servers and a second file that is included in each of the plurality of web servers and cannot be accessed from other web servers. And
At the start of a session with any one of the plurality of Web clients, a Web server that executes processing for requesting an HTTP request from any one of the plurality of Web clients until the session ends. A session processing allocation module that allocates to any one of the servers;
A data copy module that copies data of the first file to the second file of the allocated Web server when an HTTP request from the Web client in the session is transmitted to the Web server cluster; ,
Request processing for executing the request processing using the data copied to the second file when it is not necessary to update the data of the first file by the request processing of the HTTP request from the Web client in the session An execution module.

Images