JP5552991B2 - Application deployment apparatus, application deployment method, and application deployment program - Google Patents

Description

  The present invention relates to an application deployment apparatus, an application deployment method, and an application deployment program.

  Conventionally, in a Web application system, it is known that processing is distributed to a plurality of servers, and a large amount of access is processed by distributing a load to the plurality of servers.

  In such a Web application system, when there is a single database server connected to the Web server, the single database server performs processing, so the database server becomes a bottleneck and processing may be delayed. . For this reason, in order to improve scalability, connecting a plurality of database servers to a Web server has been implemented.

  Specifically, the Web application system includes a reference database server (hereinafter referred to as a reference DB server) and an update database server (hereinafter referred to as an update DB server) as database servers. Here, the Web application system will be specifically described with reference to FIG. As shown in FIG. 17, it has a load balancer (described as LB in the example of FIG. 17), a plurality of Web servers, a reference DB server, an update DB server, and a backup DB server. The load balancer distributes the process to any one of a plurality of prepared Web servers.

  In such a Web application system, the Web server holds a reference application and an update application. When the Web server receives an update request via the load balancer, the update application accesses the update DB server and updates the update DB. When the Web server receives a reference request via the load balancer, the reference application accesses the reference DB server and refers to the reference DB.

  Here, the Web application system ensures the consistency between the data in the reference DB and the data in the update DB by performing a replication process that periodically copies the data stored in the update DB to the reference DB. doing. However, the contents of the reference DB and the update DB may not match until replication processing is performed, and a user who updates data may inquire of the update database.

  For example, in a website such as a diary, there is a possibility that the written diary cannot be read for several seconds to several minutes until the replication process is performed. In other words, the owner of the diary cannot confirm whether the diary is actually registered unless the result is reflected in real time. For this reason, the content owner (hereinafter referred to as the content owner) may make an inquiry to the update DB that holds the latest data.

  For example, as a method for the content owner to make an inquiry to the update DB, the URL of the reference DB and the update DB is described in the application, and the program is manually described so as to change the connection destination database in the Web application. It is possible. Processing when such a Web application is executed will be described with reference to FIG. For example, as shown in FIG. 18, when a user ID is input at the time of login from a browser (see (1) in FIG. 18), the AP server stores the user ID in the session information storage unit used on the Web. Store (see FIG. 18B).

  When receiving a data request from the browser (see (3) in FIG. 18), the AP server refers to the user ID (see (4) in FIG. 18), and the owner ID of the data to be read is the user ID. Is matched, the update DB is inquired. If not, the reference DB is inquired (see (5) in FIG. 18).

JP 2002-132568 A JP 2006-4328 A

  By the way, the above-described method for manually describing a program for changing the connection destination database has a problem that it takes development cost for describing the program and cost for testing the program after the change.

  In one aspect, an object is to appropriately distribute an access destination database without manually changing a program.

  In the first proposal, the application deployment device adds a program for storing the identifier of the content owner to the content access program for accessing the content. Then, the application deployment apparatus converts the content access program into a program for accessing the update storage unit or the reference storage unit using the identifier of the user who requests the content reference and the identifier stored by the program.

  The access destination database can be appropriately distributed without manually changing the Web application.

FIG. 1 is a block diagram illustrating the configuration of the application deployment apparatus according to the first embodiment. FIG. 2 is a diagram illustrating the configuration of the Web application system according to the second embodiment. FIG. 3 is a diagram illustrating the configuration of the deployment server according to the second embodiment. FIG. 4 is a diagram illustrating processing for adding a filter element to the deployment descriptor. FIG. 5 is a diagram for explaining DB connection conversion processing. FIG. 6 is a diagram illustrating an example of a listener class program. FIG. 7 is a diagram illustrating an example of a filter class program. FIG. 8 is a diagram for explaining processing of the Web application system. FIG. 9 is a diagram illustrating processing when the content owner refers to content. FIG. 10 is a diagram for explaining processing when a content reader refers to content. FIG. 11 is a flowchart for explaining the deployment descriptor change procedure of the deployment server according to the second embodiment. FIG. 12 is a flowchart for explaining the DB connection conversion procedure of the deployment server according to the second embodiment. FIG. 13 is a flowchart for explaining the processing procedure when adding content in the Web application system according to the second embodiment. FIG. 14 is a flowchart for explaining a processing procedure when referring to contents in the Web application system according to the second embodiment. FIG. 15 is a diagram illustrating the configuration of the deployment server according to the third embodiment. FIG. 16 is a diagram for explaining processing of the Web application system. FIG. 17 is a diagram for explaining a conventional Web application system. FIG. 18 is a diagram for explaining processing of a conventional Web application system.

  Hereinafter, embodiments of an application deployment apparatus, an application deployment method, and an application deployment program disclosed in the present application will be described in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

  First, the configuration of the application deployment apparatus according to the first embodiment will be described with reference to FIG. FIG. 1 is a block diagram illustrating the configuration of the application deployment apparatus according to the first embodiment.

  The application deployment apparatus 1 according to the first embodiment includes a program addition unit 1 a and a program conversion unit 1 b and is connected to the application server 2. The application server 2 is connected to the user terminal 3, the update storage unit 4, and the reference storage unit 5, respectively. In response to a request from the user terminal 3, the application server 2 accesses the update storage unit 4 and the reference storage unit 5 and executes the application.

  The user terminal 3 transmits a content update request or reference request to the application server 2. The update storage unit 4 is accessed by the application server 2 and holds the latest content. The reference storage unit 5 is accessed by the application server 2 and holds a copy of the content held by the update storage unit 4.

  The program adding unit 1a of the application deployment device 1 adds a program for storing the identifier of the content owner stored in the update storage unit 4 and the reference storage unit 5 to the content access program for accessing the content. The program conversion unit 1b converts the content access program into a program for accessing the update storage unit 4 or the reference storage unit 5 using the identifier of the user who requests the reference of the content and the identifier stored by the program. .

  As described above, the application deployment apparatus 1 automatically adds and converts a content access program for accessing content, and distributes either the update storage unit 4 or the reference storage unit 5 as an access destination. As a result, the application deployment apparatus 1 can appropriately distribute access destinations by reducing the cost of development and testing for writing a program without manually changing the program.

  In the following embodiment, the configuration of the Web application system, the deployment server, and the processing flow according to the second embodiment will be described in order, and finally the effects of the second embodiment will be described.

[Web application system configuration]
First, the configuration of the entire Web application system including the deployment server will be described with reference to FIG. FIG. 2 is a diagram illustrating the configuration of the Web application system according to the second embodiment. As shown in FIG. 2, the Web application system 100 includes a deployment server 10, a plurality of AP (Application) servers 20, a browser 30, an LB (Load Balancer) 40, a reference DB (DataBase) 50, and an update DB 60.

  The deployment server 10 is connected to the AP server 20, reads the War file and the DB definition information file that are the file format of the web application arranged on the AP server 20, and reads the web application created on the deployment server 10. Deploy on the AP server 20.

  The AP server 20 has a container function that is a platform for providing external communication and memory access means, and executes a Web application developed as a War file. The web application can store session information and the like in a memory in the AP server 20. Further, an update DB 60 and a reference DB 50 are connected behind the AP server 20.

  The AP server 20 updates the data in the update DB 60 when an update request is received via the load balancer 40, and the reference DB 50 when a reference request is received via the load balancer 40. Refer to the data. Further, the AP server 20 stores DB definition information in which URLs for connecting to the DBs 50 and 60 are described. This DB definition information is saved as, for example, an XML file. In addition, the AP server 20 performs a replication process that periodically copies the data stored in the update DB 60 to the reference DB 50, thereby ensuring consistency between the data in the reference DB 50 and the data in the update DB 60. ing.

  The browser 30 is software for a user to browse information on a user terminal connected to the load balancer 40 via the Internet. Specifically, the browser 30 receives a user request, transmits the request to the load balancer 40, and displays a web page received from the load balancer on the user terminal.

  The load balancer 40 is connected to a plurality of AP servers 20 and performs load distribution of a plurality of requests. Specifically, when receiving a request from the browser 30, the load balancer 40 selects one of the plurality of prepared AP servers 20 and transmits the request to the selected AP server 20.

  Next, the configuration of the deployment server 10 shown in FIG. 2 will be described with reference to FIG. FIG. 3 is a block diagram illustrating the configuration of the deployment server according to the second embodiment. As illustrated in FIG. 3, the deployment server 10 includes a file decompression unit 11, a deployment descriptor conversion unit 12, a DB connection conversion unit 13, a Web content conversion unit 14, and a file compression unit 15. The processing of each of these units will be described below.

  The file decompression unit 11 reads a War file, which is a compressed web application file, and decompresses it into a normal file. Here, the War file is a deployment descriptor for defining which program is called in response to a request according to the Servlet specification defined by JCP (Java (registered trademark) Community Process), and a Java program body. It consists of class files, Web contents such as HTML and JSP.

  The deployment descriptor conversion unit 12 adds a Servlet filter to the deployment descriptor for defining which program is called for the request. Specifically, the deployment descriptor conversion unit 12 adds a Servlet filter that stores, in the HTTP session information, the HTTP query text associated with the HTTP request text when the password is included in the HTTP request.

  Here, the process of adding a filter element to the deployment descriptor will be described with reference to FIG. FIG. 4 is a diagram illustrating processing for adding a filter element to the deployment descriptor. First, the deployment descriptor conversion unit 12 determines whether there is a <listener> element in the deployment descriptor. As a result, when it is determined that there is no <listener> element, the deployment descriptor conversion unit 12 adds a <listener-class> element as shown in FIG. If the deployment descriptor conversion unit 12 determines that there is a <listener> element, the deployment descriptor conversion unit 12 adds a <listener-class> element at the end of the <listener> element.

  Subsequently, the deployment descriptor conversion unit 12 determines whether there is a <filter> element. As a result, when the deployment descriptor conversion means 12 determines that there is no <filter> element, as shown in FIG. 4, the <filter> element (see (1) in FIG. 4) immediately before the <servlet> element. ) And <filter-mapping> element (see (2) in FIG. 4).

  If the deployment descriptor conversion unit 12 determines that there is a <filter> element, it adds a <filter> element immediately after the last <filter> element, and immediately after the last <filter-mapping> element. To the <filter-mapping> element.

  By changing the deployment descriptor in this way, the listener class “com.fujitsu.ServletListener” is executed when the web application starts, and the filter class “com.fujitsu.PasswordFilter” is executed at the beginning of all request processing. Can be defined. The listener class and the filter class will be described in detail later with reference to FIGS.

  The DB connection conversion unit 13 generates a connection to the update DB 60 and includes the owner ID if the owner class ID is included in the executed SQL for the Java class that accesses the database. For example, a program for generating a connection to the reference DB 50 is embedded by aspect-oriented technology.

  For example, the DB connection conversion unit 13 generates code for creating an object for executing a query, such as a “Connection # createStatement ()” method and a “Connection # prepareStatement ()” method, as a static analysis technology such as an aspect-oriented language. To search from within the Java class file.

  Then, in the case of the program as shown in the upper part of FIG. 5, the DB connection conversion unit 13 is a candidate for whether or not it is a content owner ID before the code part for generating the connection (see FIG. 5 (3)). A code (see FIG. 5 (4)) for acquiring the list is added.

  Thereafter, the DB connection conversion unit 13 determines whether or not the owner ID is included in the executed SQL, and if included, generates a connection to the update DB 60, and if not included, for reference A code for generating a connection to the DB 50 (see (5) in FIG. 5) is added. In addition, when executing SQL for updating the database such as update and create, a code for generating a connection to the update DB is used.

  The Web content conversion unit 14 searches the HTML file and the JSP file, and determines whether there is an <input> element whose type attribute is “password”. As a result, when there is an <input> element with a password attribute, the Web content conversion unit 14 is a hidden message “<input type =“ hidden ”name =“ CONTAINS_PASSWORD_FIELD ”Value =“ TRUE ”in the same form element. The process of adding “>” is performed.

  In other words, if the HTML input form includes password information and the owner has determined that there is a high possibility that the ID has been input, and if "CONTAINS_PASSWORD_FIELD" is included, the value at that time is hidden to be stored in the session. Add a message. Note that the same input form is often used for the ID and the password, and there is a high probability that the ID information is included in the information input together with the password.

  The file compression unit 15 compresses the post-conversion deployment descriptor, the post-conversion class file, and the post-conversion web content together with the listener class and the filter class, and generates a post-conversion application. The converted application is transferred and deployed on the AP server 20 via the network, and is executed on the execution system.

  Here, the listener class will be described using the example of FIG. FIG. 6 is a diagram illustrating an example of a listener class program. The listener class is executed only once when the deployed web application is activated. As shown in FIG. 6, the listener class has a function of storing the URLs of the update DB and the reference DB extracted from the DB definition file in a memory so that they can be used later in the application. ing. Specifically, it is used in the code (5) shown in FIG.

  FIG. 7 is a diagram illustrating an example of a filter class program. The filter class is called at the beginning of a request according to the Servlet specification, and can read information of an HTTP request. The filter class “PasswordFilter” searches the HTTP request information and checks whether a parameter named CONTAINS_PASSWORD_FIELD exists. If the CONTAINS_PASSWORD_FIELD parameter exists, a helper class (ScaleoutHelper) is called and the contents of all parameters are stored in the session (memory information for each user). This content is a candidate for the owner ID.

  Here, content reference processing in the Web application system will be described with reference to FIG. FIG. 8 is a diagram for explaining processing of the Web application system. As shown in FIG. 8, in the Web application system 100, when an input of a user ID is accepted from the browser 30 at the time of login, the user ID is transmitted to the LB 40 (see (1) in FIG. 8). In the Web application system 100, when the user ID is transmitted from the LB 40 to the AP server 20, the filter identifies the character string sent together with the password as the user ID, and stores the user ID in the session information ( (See (2) in FIG. 8).

  Thereafter, when receiving a data reference request from the browser 30 (see (3) in FIG. 8), the Web application system 100 transmits the data reference request to the AP server 20 via the LB 40. And the application of AP server 20 will issue SQL, if a data reference request is received. Subsequently, the DB distribution engine of the AP server 20 analyzes the SQL and refers to the user ID of the session information to see if there is one or more items matching the user ID in the where clause (see (4) in FIG. 8). ). As a result, if there is one or more items that match the user ID in the where clause, the update DB 60 is inquired. If there is no item that matches the user ID, the reference DB 50 is inquired (if there is no item that matches the user ID ( (See (5) in FIG. 8).

  For example, a process in the case where the content owner registers the content and confirms it himself will be described with reference to FIG. FIG. 9 is a diagram illustrating processing when the content owner refers to content. The HTML content on the top page has an input form for ID and password. Since this input form has an <input> element of type = password, the ID entered at the same time as the password becomes session information through the helper class. Saved. For example, as shown on the left side of FIG. 9, when “tanaka” is input as the ID, a character string “takana” is stored in the session information.

  Thereafter, the content user registers content such as a diary and displays a list of content created by the content user again. At that time, when the code as shown in the upper right of FIG. 9 is executed, since the character string “takana” is entered in the id part of the statement object, this character string matches the character string of the session information and is used for the update. The DB URL is used.

  In addition, processing when a content reader refers to content will be described with reference to FIG. FIG. 10 is a diagram for explaining processing when a content reader refers to content. As shown in FIG. 10, when the content reader “suzuki” logs in with an ID different from the content owner “tanaka”, “suzuki” is stored in the session information. Next, when the content reader “Suzuki” presses Tanaka's content list display, the code shown in the upper right of FIG. 10 is executed. Here, since the character string “takana” is entered in the id portion of the statement object, this character string does not match the character string of the session information, and the URL of the reference DB is used.

[Processing by Deployment Server]
Next, processing performed by the deployment server 10 according to the second embodiment will be described with reference to FIGS. 11 and 12. FIG. 11 is a flowchart for explaining the deployment descriptor change procedure of the deployment server according to the second embodiment. FIG. 12 is a flowchart for explaining the DB connection conversion procedure of the deployment server according to the second embodiment.

  As shown in FIG. 11, when the deployment server 10 reads the deployment descriptor (step S101), the deployment server 10 determines whether there is a <listener> element (step S102). As a result, when the deployment server 10 determines that there is a <listener> element (Yes in step S102), the deployment server 10 adds a <listener-class> element at the end of the <listener> element (step S103).

  If the deployment server 10 determines that there is no <listener> element (No in step S102), it adds a <listner-class> element (step S104).

  Subsequently, the deployment server 10 determines whether there is a <filter> element (step S105). As a result, when the deployment server 10 determines that there is a <filter> element (Yes in step S105), the deployment server 10 adds a <filter> element immediately after the last <filter> element (step S106). Then, a <filter-mapping> element is added immediately after the last <filter-mapping> element (step S107).

  If the deployment server 10 determines that there is no <filter> element (No in step S105), it adds a <filter> element and a <filter-mapping> element immediately before the <servlet> element (step S108). .

  Next, the DB connection conversion process will be described with reference to FIG. As shown in FIG. 12, the deployment server 10 reads the Java program (step S201) and determines whether there is a connection acquisition part (step S202). As a result, when there is no connection acquisition part (No at Step S202), the deployment server 10 ends the DB connection conversion process. Further, when there is a connection acquisition part (Yes at Step S202), the deployment server 10 adds a command for acquiring the owner ID candidate list to the head of the program method (Step S203).

  Then, the deployment server 10 generates a connection to the update DB 60 if the SQL to be executed includes the owner ID for the code part for generating the connection, and the reference DB 50 if the owner ID is not included. A code for generating a connection to is added (step S204). Thereafter, the deployment server 10 adds a <filter-mapping> element immediately after the last <filter-mapping> element (step S205).

[Processing by Web application system]
Next, processing performed by the Web application system 100 according to the second embodiment will be described with reference to FIGS. 13 and 14. FIG. 13 is a flowchart for explaining the processing procedure when adding content in the Web application system according to the second embodiment. FIG. 14 is a flowchart for explaining a processing procedure when referring to contents in the Web application system according to the second embodiment.

  As shown in FIG. 13, the AP server 20 reads the deployment descriptor (step S301), executes the listener class (step S302), and stores the URLs of the reference DB 50 and the update DB 60 in the memory of the AP server 20. Save (step S303). Then, when the content owner inputs the URL of the top page of the site from the browser 30 to access the load balancer 40 (step S304), the load balancer 40 transmits an HTTP request to the AP server 20 (step S305).

  Subsequently, the AP server 20 receives an HTTP request from the load balancer 40, and returns the corresponding Web page according to the deployment descriptor (step S306). Since the Web page includes an input of a password, a “CONTAINS_PASSWORD_FIELD” parameter is added.

  Then, the content owner inputs “ID” and “password” from the browser 30 and logs in (step S307). Then, “ID” and “password” are notified from the browser 30 to the load balancer 40, and the load balancer 40 transmits the same again to the same AP server 20 (step S308).

  Then, the AP server 20 calls the filter program and adds the content owner ID to the session information because the “CONTAINS_PASSWORD_FIELD” parameter exists (step S309). Subsequently, the AP server 20 calls the class file corresponding to the URL according to the deployment descriptor, performs authentication, and returns the web page to the content owner (step S310).

  Thereafter, when the content owner inputs content such as a diary from the browser and presses the registration button (step S311), the content is transmitted to the AP server 20 via the load balancer 40, and the class file corresponding to the URL is called ( Step S312). Since the registration program is an update system, writing is performed to the update DB 60 (step S313), and the AP server 20 returns a registration completion page to the content owner (step S314).

  Subsequently, when the content owner presses the content list selection button to request the reference of the content list registered by himself / herself (step S315), the request is transmitted to the AP server 20 via the load balancer 40, The class file corresponding to the URL is called (step S316). The AP server 20 uses the list display screen as a reference system and the owner's ID is included in the SQL, so the connection of the update DB 60 is used and the update DB 60 is referred to (step). S317).

  Next, content reference processing will be described with reference to FIG. As shown in FIG. 14, the AP server 20 reads the deployment descriptor (step S401), executes the listener class (step S402), and stores the URLs of the reference DB 50 and the update DB 60 in the memory of the AP server 20. Save (step S403). Then, when the content reader enters the URL of the top page of the site from the browser 30 and accesses the load balancer 40 (step S404), the load balancer 40 transmits an HTTP request to the AP server 20 (step S405).

  Subsequently, the AP server 20 receives an HTTP request from the load balancer 40, and returns a corresponding Web page according to the deployment descriptor (step S406). Since the Web page includes an input of a password, a “CONTAINS_PASSWORD_FIELD” parameter is added.

  Then, the content reader inputs “ID” and “password” from the browser 30 and logs in (step S407). Then, “ID” and “password” are notified from the browser 30 to the load balancer 40, and the load balancer 40 transmits the same again to the same AP server 20 (step S408).

  Then, the AP server 20 calls the filter program and adds the content reader ID to the session information because the “CONTAINS_PASSWORD_FIELD” parameter exists (step S409). Subsequently, the AP server 20 calls the class file corresponding to the URL according to the deployment descriptor, performs authentication, and returns the Web page to the content reader (step S410).

  Thereafter, when the content reader selects a content owner to be read and presses the content list button (step S411), a request is transmitted to the AP server 20 via the load balancer 40, and a class file corresponding to the URL is called ( Step S412). The AP server 20 uses the list display screen as a reference system, and the owner's ID is not included in the SQL, so the connection of the reference DB 50 is used and the reference DB 50 is referred to (step). S413). Note that the latest content may not be seen depending on the replication timing.

[Effect of Example 2]
As described above, the deployment server 10 uses the content owner stored in the update DB 60 that holds the latest content and the reference storage unit 50 that holds a copy of the content held in the update DB 60. A Servlet filter that stores the user ID is added to the deployment descriptor. Then, the deployment server 10 accesses the database with a program that accesses the update DB 60 or the reference DB 50 by using the user ID of the user who requests content reference and the user ID stored by the program. Embed in Java class.

  Therefore, the deployment server 10 can appropriately distribute the access destination database by reducing the cost for development and testing for describing the program without manually changing the program.

  Further, according to the second embodiment, the deployment server 10 uses the request text describing the request as the user ID of the content owner when the program added by the program adding unit includes a password in the user's request. save. For this reason, the same input form is often used for the ID and the password, and the user ID can be appropriately acquired.

  According to the second embodiment, the deployment server 10 adds a program for storing the owner's user ID, creates connection information for the update DB 60 and the reference DB 50, and uses the connection information for update. A program that accesses the DB 60 or the reference DB 50 is embedded in a Java class that accesses the database. As a result, it is possible to access the update DB 60 and the reference DB 50 using connection information created in advance.

  By the way, in Example 2 described above, the same applies when the Servlet filter detects “<input type =“ password ”name =“ *** ”>” in the HTML file instead of the Web content conversion unit 14. <Input type = “hidden” name = “CONTAINS_PASSWORD_FIELD” value = “TRUE”> may be added in the form element.

  Therefore, in Example 3 below, the Servlet filter converts the HTML information output by the application and detects “<input type =“ password ”name =“ *** ”>” in the HTML file. In this case, <add type = “hidden” name = “CONTAINS_PASSWORD_FIELD” value = “TRUE”> is added ”in the same form element” according to the third embodiment using FIG. 15 and FIG. The deployment server will be described. FIG. 15 is a diagram illustrating the configuration of the deployment server according to the third embodiment. FIG. 16 is a diagram for explaining processing of the Web application system.

  First, the configuration of the deployment server 10a according to the third embodiment will be described. As shown in FIG. 15, the deployment server 10 a is different from the deployment server 10 shown in FIG. 3 in that the web content conversion unit 14 is not provided and a filter class A is newly included. In the deployment server 10a, the filter class A includes a preprocessing filter for performing preprocessing and a postprocessing filter for performing postprocessing. Although the role of the preprocessing filter is the same as that of the filter class of the third embodiment, the postprocessing filter performs processing for changing the HTML information as postprocessing.

  The post-processing converts the HTML output by the application, and, like the Web content conversion unit 14 of the first embodiment, “<input type =“ password ”name =“ *** ”>” in the HTML file. Is detected, <input type = “hidden” name = “CONTAINS_PASSWORD_FIELD” value = “TRUE”> is added ”in the same form element.

  As a result, it is possible to provide an equivalent function with a flow substantially equivalent to that of the second embodiment. Further, the third embodiment has an advantage that conversion is performed on finally outputted HTML information.

  Here, the processing of the Web application system according to the third embodiment will be described with reference to FIG. FIG. 16 is a diagram for explaining processing of the Web application system. As shown in FIG. 16, in the Web application system according to the third embodiment, when the input of the user ID is accepted from the browser 30 at the time of login, the user ID is transmitted to the LB 40 (see (1) in FIG. 16). When the user ID is transmitted from the LB 40 to the AP server 20, the filter A identifies the character string sent together with the password as the user ID, and stores the user ID in the session information ((2 in FIG. 16). )reference).

  Thereafter, when a data reference request is received from the browser 30 (see (3) in FIG. 16), the data reference request is transmitted to the AP server 20 via the LB 40. And the application of AP server 20 will issue SQL, if a data reference request is received. Subsequently, the DB distribution engine of the AP server 20 analyzes the SQL, and refers to the user ID of the session information to see if there is one or more items matching the user ID in the where clause (see (4) in FIG. 16). ).

  As a result, if there is one or more items that match the user ID in the where clause, the update DB 60 is inquired. If there is no item that matches the user ID, the reference DB 50 is inquired.

  As described above, according to the third embodiment, when the HTML information is generated directly from the Servlet class without using the SP file or the HTML file, the HTML information that is finally output can be converted. .

  Although the embodiments of the present invention have been described so far, the present invention may be implemented in various different forms other than the embodiments described above. Accordingly, another embodiment included in the present invention will be described below as a fourth embodiment.

(1) System Configuration, etc. Further, each component of each illustrated apparatus is functionally conceptual and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. For example, the file decompression unit 11 and the deployment descriptor conversion unit 12 may be integrated.

(2) Program The application deployment method described in the present embodiment can be realized by executing a program prepared in advance on a computer such as a personal computer or a workstation. This program can be distributed via a network such as the Internet. The program can also be executed by being recorded on a computer-readable recording medium such as a hard disk, a flexible disk (FD), a CD-ROM, an MO, and a DVD and being read from the recording medium by the computer.

DESCRIPTION OF SYMBOLS 1 Application deployment apparatus 1a Program addition part 1b Program conversion part 2 Application server 3 User terminal 4 Update storage part 5 Reference storage part 10 Deployment server 11 File decompression part 12 Deployment descriptor conversion part 13 DB connection conversion part 14 Web content Conversion unit 15 File compression unit 20 AP server 30 Browser 40 Load balancer 50 Reference DB
60 DB for update

Claims (5)

Causes the computer to execute processing for storing the identifier of the content owner stored in the update storage unit that holds the latest content and the reference storage unit that holds a copy of the content held in the update storage unit A program code adding unit for adding the code of the storage program to the code of the content access program that causes the computer to execute a process of accessing the content;
To access program for executing processing for accessing said update storage unit or the reference memory unit by using the result stored identifier to the execution of the stored program and the user identifier to request a reference to the content on the computer And a program conversion unit for converting the content access program. The content access program to which the code has been added by the program code adding unit, when a password is included in the user's request in the code of the content access program, the request text describing the request is replaced with the identifier of the content owner The application deployment apparatus according to claim 1, wherein the application deployment apparatus is a program that causes a computer to execute processing to be stored as a program . The program code adding unit is a code of an information creation program for creating connection information of the update storage unit and the reference storage unit together with a code of the storage program for causing a computer to execute a process of storing the identifier of the owner To the content access program code ,
The program conversion unit, the update storage unit or a process of accessing the reference storage unit to the access program to be executed by a computer, and converting the content access program using the connection information The application deployment apparatus according to claim 1 or 2. Causes the computer to execute processing for storing the identifier of the content owner stored in the update storage unit that holds the latest content and the reference storage unit that holds a copy of the content held in the update storage unit A program code adding step for adding the code of the storage program to the code of the content access program causing the computer to execute a process of accessing the content;
To access program for executing processing for accessing said update storage unit or the reference memory unit by using the result stored identifier to the execution of the stored program and the user identifier to request a reference to the content on the computer And a program converting step for converting the content access program. Causes the computer to execute processing for storing the identifier of the content owner stored in the update storage unit that holds the latest content and the reference storage unit that holds a copy of the content held in the update storage unit A program code addition procedure for adding the code of the storage program to the code of the content access program causing the computer to execute a process of accessing the content;
To access program for executing processing for accessing said update storage unit or the reference memory unit by using the result stored identifier to the execution of the stored program and the user identifier to request a reference to the content on the computer An application deployment program that causes a computer to execute a program conversion procedure for converting the content access program.

Images