JP2016024700A - Web application system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a web application system capable of dynamically allocating a processing which is executable at both a terminal unit and a server to the terminal unit or the server depending on the load.SOLUTION: A server side load measurement unit measures the respective loads of unit processing executed by the server side processing execution section, and writes the value of the load obtained as a result of measurement in processing execution history information. The server side processing execution section executes a unit processing which is allotted to a server side processing distribution section or a terminal unit side processing distribution section at the server side. The server side processing distribution section determines which of the server side and the terminal unit side should execute the respective unit processing included in the processing execution schedule information based on the load value included in the processing execution history information. Either of the server side processing execution section or the terminal unit side processing execution section executes the unit processing based on the determined result.SELECTED DRAWING: Figure 2

Description

  Embodiments described herein relate to a web application system.

  The web application is application software used via a network such as the Internet (or intranet). In many cases, these applications run by the cooperation of a program in a programming language (for example, JavaScript (registered trademark)) that runs on the browser of the terminal and a program on the server side, and the user runs it on the browser of the terminal. Used in.

  With the spread of the Internet in recent years and technological progress, functions that have been implemented as desktop applications in the past have been increasingly provided as web applications. Examples of web applications include blogs, electronic bulletin boards, Internet banking, online trading by securities companies, and shopping carts for online sales such as online shopping malls.

JP 2013-101523 A

  In web applications, there was a need to adjust the load and responsiveness according to the computer resources of each terminal. For example, in a power control system, a high-performance terminal device is used in the central control room, but each worker can execute a web application at a higher speed in an environment using a hand-held terminal device that is not so high in performance. In order to achieve this, it is necessary to appropriately distribute processing between each terminal device and the server.

  Further, there is a need to adjust the load and responsiveness in the web application, but it is difficult to develop the web application according to the types of various terminal devices from the viewpoint of man-hour / maintenance.

In addition, in the web application, there is a problem that it is difficult to move the process from the terminal device to the server (or vice versa). This is due to the following reason.
(1) Because there are ubiquitous processes depending on data sources and GUI parts. (2) It is difficult to change from a screen transition web application to a non-screen transition web application. (3) There are various terminals. (4) Because it is not simple load averaging

  An object of the present invention is to provide a web application system capable of dynamically allocating processing that can be executed in both a terminal device and a server to a terminal device or a server according to a load.

The embodiment of the present invention is proposed as a web application system.
The web application system includes a first storage unit, a first measurement unit, a first determination unit, a second storage unit, a second measurement unit, a first measurement unit, and a first measurement unit. Determination means.

  The first storage means includes processing execution plan information that is information describing processing using unit processing, information for specifying unit processing, information for specifying a request source of processing, and an execution environment for the unit processing. Information to be identified and first process execution history information having the load value of the unit process are stored.

The first measurement unit measures the load of each unit process executed by the first execution unit, and writes the load value obtained as a result of the measurement in the first process execution history information.
The first execution means executes the unit process designated by the first determination means or the second determination means in the first execution environment.

  The first execution means is included in the first process execution history information as to whether each unit process included in the process execution plan information is performed in the first execution environment or the second execution environment. The determination is made based on the load value, and each unit process is executed by either the first execution means or the second execution means based on the result of this determination.

  The second storage means includes the same information as the process execution plan information, information specifying a unit process, information specifying a process request source, information specifying an execution environment of the unit process, and the unit The process load value and the second process execution history information are stored.

The second measuring unit measures the load of each unit process executed by the second executing unit, and writes the load value obtained as a result of the measurement in the second process execution history information.
The second execution means executes the unit process designated by the first determination means or the second determination means in the second execution environment.

  The second determination means determines whether each unit process included in the process execution plan information is performed in the first execution environment or the second execution environment, and includes a load included in the second process execution history information. The unit processing is executed by either the first execution unit or the second execution unit based on the determination result.

  In the web application system, the first determination unit refers to a load value included in the first process execution history information, and the load value of the unit process in the first execution environment, By comparing the load value of the unit process in the second execution environment with the total value of the load on communication, it is determined which of the first execution means and the second execution means the unit process is executed. The second determination means refers to the load value included in the second process execution history information, and determines the load value of the unit process and the load on communication in the first execution environment. The total and the load value of the unit process in the second execution environment are compared to determine which of the first execution unit and the second execution unit to execute the unit process. May be.

  Further, the web application system includes a first management unit that transmits terminal type information that is information specifying a type or type of the terminal device, and the second process execution history information based on the terminal type information. A record in which information corresponding to the terminal type information is stored as information for specifying the execution environment, and a record in which information indicating a server is stored as information for specifying the execution environment And a second management unit for generating the third process execution history information and transmitting the same to the first management unit, wherein the first management unit includes the third process execution history information. The information may be stored in the first storage unit as new second process execution history information.

  Furthermore, in the web application system, the first management unit transmits the first process execution history information to the second management unit, and the second management unit receives the received first first The second process execution history information may be updated based on the process execution history information.

  Furthermore, in the web application system, the first storage means includes information for specifying a unit process described in the process execution plan information, and information for specifying a unit process to be executed by the first execution means. Is further stored, and the second storage means includes information for specifying a unit process described in the process execution plan information, and the second execution means You may make it further memorize | store the process corresponding | compatible table information which is the information which matched and described the information which specifies the unit process to perform.

The block diagram which shows the structural example of the web application system concerning this Embodiment Functional block diagram showing a configuration example of a server according to an embodiment The figure which shows the data structural example of the process execution log | history information memorize | stored in the server side process execution log | history memory | storage part The figure which shows the data structural example of the terminal device side process execution log | history information produced | generated from the process execution log | history information shown in FIG. The figure which shows the example of the flow (process execution plan) which consists of five unit processes from the unit process 1 and the unit process 3 to the unit process 6 The figure which showed the data structural example of the process execution plan information which described the flow of the process shown in FIG. Diagram showing an example of the data structure of processing correspondence table information Functional block diagram showing a configuration example of a terminal device according to an embodiment Sequence diagram showing an example of initialization processing in the web application system An example of processing execution plan information is shown The figure which shows the process execution log | history information which stored the value of the load assumed to be obtained when the load of the unit process 1 to the unit process 4 is measured The figure which shows the process correspondence table information memorize | stored in the terminal device side process correspondence table memory | storage part. The figure which shows the process correspondence table information memorize | stored in the server side process correspondence table memory | storage part. Sequence diagram showing an example of the execution operation of the process execution plan at the terminal device starting point in the web application system FIG. 14 is a sequence diagram illustrating an example of the execution operation of the process execution plan at the terminal device starting point in the web application system. Data example of terminal-side process execution history information stored in the terminal-side process execution history storage unit and server-side process execution history information stored in the server-side process execution history storage unit before the initialization process starts Figure showing The figure which shows the data example of the terminal device side process execution history information and server side process execution history information at the time of complete | finishing from step S101 to step S103 The figure which shows the example of a data of the terminal side process execution history information and the server side process execution history information at the time of complete | finishing from step S201 to step S205 after the state shown in FIG. The figure which shows the data example of a terminal device side process execution history information, and a server side process execution history information The figure which shows the data example of a terminal device side process execution history information, and a server side process execution history information The figure which shows the data example of a terminal device side process execution history information, and a server side process execution history information The figure which shows the data example of a terminal device side process execution history information, and a server side process execution history information The flowchart which showed an example of the process distribution process which is main operation | movement of a terminal device side process distribution part and a server side process distribution part Flowchart following FIG. The flowchart which showed an example of the terminal device side communication time measurement process which is one of the main operations of the terminal device side management part. The flowchart which showed an example of the terminal device side communication time measurement request reception process Flow chart showing an example of server side communication time measurement processing The flowchart which showed an example of processing at the time of server side communication time measurement request reception

Hereinafter, a web application system according to an embodiment of the present invention will be described with reference to the drawings.
[0. Definition of terms]
Definitions of terms used in this specification will be described.

[0.1. Web application]
“Web application” refers to an application that runs on a web browser. The “web application system” refers to a system that executes a web application.

[0.2. server]
“Server” refers to an environment (hardware) for operating a web application.

[0.3. Terminal device]
A “terminal device” refers to an environment (hardware) in which a web application running on a server is loaded and executed.

[0.4. GUI parts]
“GUI component” refers to a component constituting a GUI (Graphical User Interface) of a web application.

[0.5. Data source]
A “data source” refers to a device that holds data.

[0.6. Screen transition web application]
A “screen transition type web application” refers to a web application that involves a change in URL (Uniform Resource Locator).

[0.7. Non-screen transition web application]
A “non-screen transition type web application” refers to a web application that does not involve a URL change.

[1. Embodiment]
[1.1. Configuration example]
One embodiment of the present invention is proposed as a web application system. This web application system is a system that executes a web application while dynamically allocating processes that can be executed by both the terminal device and the server to the terminal device or the server according to the load.

  FIG. 1 is a block diagram showing a configuration example of a web application system according to the present embodiment. The web application system 1 includes a server 10 and a terminal device 20. The terminal device 20 may not be the same device, the same model, the same specification model, or the like. The server 10 is connected to the network 30. Each of the terminal devices 20 is connected to or connectable to the network 30. The server 10 and each terminal device 20 can exchange data with each other via the network 30.

[1.1.1. server]
The server 10 is a device that provides an environment for executing a web application. The server 10 is an apparatus realized by an information processing apparatus such as a computer or a workstation. The information processing apparatus includes an arithmetic processing unit (CPU), a main memory (RAM), a read only memory (ROM), an input unit. An output device (I / O) and, if necessary, a device provided with an external storage device such as a hard disk device. The server 10 corresponds to the second execution environment of this embodiment.

  A configuration example of the server 10 according to the embodiment of the present invention will be described. FIG. 2 is a functional block diagram illustrating a configuration example of the server 10 according to the present embodiment. Note that the constituent elements shown in the functional block diagram are the functions of the server 10 that are collectively regarded as a block as a block, and the web application system has a physical structure such as a board, a device, a circuit, and a component corresponding to each constituent element. It does not mean that it must have a physical component. In addition, “connection” means that data, information, instructions, etc. can be transmitted and / or received, received, delivered, etc., and is physically connected such that they are connected to each other by wiring. The meaning is not limited to. The same applies to the description of the functional block diagrams of the other components in this specification.

  The server 10 includes a server-side communication unit 101, a server-side management unit 102, a server-side process distribution unit 103, a server-side load measurement unit 104, a server-side process execution unit 105, a data operation function unit 106, a data A source unit 107, a server-side process execution history storage unit 108, a server-side process execution plan storage unit 109, and a server-side process correspondence table storage unit 110 are included.

  The server side communication unit 101 is connected to the network 30. The server side management unit 102 is connected to the server side communication unit 101 and the server side processing execution history storage unit 108. The server-side process distribution unit 103 is connected to the server-side management unit 102, and is also connected to the server-side process execution history storage unit 108, the server-side process execution plan storage unit 109, and the server-side process correspondence table storage unit 110. . The server side load measurement unit 104 is connected to the server side processing distribution unit 103. The server side process execution unit 105 is connected to the server side process distribution unit 103. The data operation function unit 106 is connected to the data source unit 107. The server side load measurement unit 104 is connected to the server side process execution history storage unit 108 and the server side process execution unit 105.

[1.1.1.1. Server side communication section]
The server side communication unit 101 has a function of performing data transmission / reception between the terminal device 20 server 10 via the network 30. The server side communication unit 101 is realized by, for example, a network adapter, a LAN board, or the like.

[1.1.1.2. Server side management department]
The server-side management unit 102 has a function of controlling execution of each process in the server 10. The server side management unit 102 corresponds to the second management unit of the present embodiment.

[1.1.1.3. Server-side processing distribution unit]
The server-side process distribution unit 103 determines whether each unit process included in the process execution plan information is performed by the terminal device 20 or the server 10, and based on the determination result, each unit process is performed by the terminal device 20 or the server 10. It has a function to be executed in. The server-side processing distribution unit 103 corresponds to the second determination unit of the present embodiment.

[1.1.1.4. Server-side process execution history storage unit]
The server-side process execution history storage unit 108 has a function of storing process execution history information. The server-side process execution history storage unit 108 corresponds to the second storage unit of the present embodiment.

  FIG. 3 shows a data configuration example of the process execution history information stored in the server-side process execution history storage unit 108. The process execution history information 500S is data having one record 510 for each unit process, and each record 510 has a field 521 for storing information (for example, process name) for identifying the corresponding unit process, a process request. The field 522 stores information for specifying the source, the field 523 stores information for specifying the execution location of the unit process, and the field 524 stores the load value of the unit process.

[1.1.1.5. Server-side processing execution plan storage unit]
The server-side process execution plan storage unit 109 has a function of storing process execution plan information, which is information describing the entire process executed by the system 1 using a combination of small processes (“unit processes”). This corresponds to the second storage means of the present embodiment.

  FIG. 5 shows an example of a process flow (process execution plan) including unit process 1 and five unit processes from unit process 3 to unit process 6. This process starts from the unit process 1 and proceeds to the unit process 3, the unit process 4, and the unit process 5 in that order, and the unit process 5 ends the process. Further, after the unit process 3 is executed, the unit process 6 is also executed. The unit processing 1 and the unit processing 5 are executed only by the terminal device 20, the unit processing 4 and the unit processing 6 are executed only by the server 10, and the unit processing 3 is a unit that can be executed by either the terminal device 20 or the server 10. It is assumed that it is a process.

  FIG. 6 is a diagram illustrating a data configuration example of the process execution plan information describing the flow of the process illustrated in FIG. The process execution plan information 600 is data having one record 610 for one unit process. Each record 610 includes a field 621 for storing information (for example, a process name) for specifying a corresponding unit process, and a field 622 for storing information (for example, a process name) for specifying a unit process to be executed next to the unit process. And a field 623 for storing information for specifying the execution place of the unit process.

[1.1.1.6. Server-side processing correspondence table storage unit]
The server-side process correspondence table storage unit 110 is process correspondence table information that is information in which unit information described in the process execution plan information is associated with information that identifies unit processes that are actually executed. Has a function of storing. The server-side processing correspondence table storage unit 110 corresponds to the second storage unit of the present embodiment.

  The server-side process distribution unit 103 switches the process to be actually executed according to the process request source (eg, terminal device, server). If the processing correspondence table information does not exist, the requested processing name is used as it is, and the server side processing execution unit 105 is instructed to execute the corresponding unit processing.

  FIG. 7 is a diagram illustrating a data configuration example of the processing correspondence table information. The process correspondence table information 700 is data having one record 710 for one unit process. Each record 710 includes a field 721 for storing information (for example, a process name) for specifying a corresponding unit process, information for specifying a request source of the unit process (for example, a value for distinguishing terminal equipment or serverization, a character string) ) And a field 723 for storing information for specifying a unit process to be actually executed.

[1.1.1.7. Server-side load measurement unit]
The server-side load measurement unit 104 measures the load of each unit process executed in the server 10, and the load value obtained as a result of the measurement is stored in the server-side process execution history storage unit 108. It has a function to write information. The server side load measuring unit 104 corresponds to the second measuring unit of the present embodiment.

[1.1.1.8. Server side processing execution unit]
The server-side process execution unit 105 has a function of executing a unit process that the server-side process distribution unit 103 determines to be executed by the server 10. The server-side process execution unit 105 corresponds to the second execution unit of the present embodiment.

  The server-side process execution unit 105 includes all unit processes 111 whose execution environment is the server 10 and unit processes 111 whose execution environment is both the server 10 and the terminal device 20. The unit process 111 that is both the server 10 and the terminal device 20 is provided with information (for example, a process name) for specifying different unit processes on the server 10 side and the terminal device 20 side, and the process execution plan information The information for specifying the unit processing at the server 10, the information for specifying the unit processing at the server 10 side, and the information for specifying the unit processing at the server 10 side are associated with each other by the processing correspondence table information. For example, for the unit process described as “Process 3” in the process execution plan information, the process correspondence table information indicates that the process name of the unit process executed on the server 10 side corresponding to Process 3 is “Unit Process 3S” The process name of the unit process executed on the terminal device 20 side corresponding to the unit process 3 is described as “unit process 3T”.

[1.1.1.9. Data operation function part]
The data operation function unit 106 has a function for operating the data source (database) stored in the data source unit 107. The data operation function unit 106 is, for example, a DBMS (database management system).

[1.1.1.10. Data source section]
The data source unit 107 has a function of storing a set of data and storing data used in the web application.

[1.1.2. Terminal device]
The terminal device 20 is a device that provides an environment for loading and executing a web application that runs on the server 10. The terminal device 20 is a device realized by an information processing device such as a computer, a mobile phone, a tablet PC, a smartphone, or a business communication terminal. The information processing device includes an arithmetic processing device (CPU) and a main memory (RAM). ), A read-only memory (ROM), an input / output device (I / O), and, if necessary, an external storage device such as a hard disk device. The terminal device 10 corresponds to the first execution environment of the present embodiment.
A configuration example of the terminal device 20 according to the embodiment of the present invention will be described. FIG. 8 is a functional block diagram showing a configuration example of the terminal device 20 according to the present embodiment.

  The terminal device 20 includes a terminal device side communication unit 201, a terminal device side management unit 202, a terminal device side processing distribution unit 203, a terminal device side load measurement unit 204, a terminal device side processing execution unit 205, and a GUI component. An operation function unit 206, a GUI component unit 207, a terminal device side process execution history storage unit 208, a terminal device side process execution plan storage unit 209, and a terminal device side process correspondence table storage unit 210 are provided.

  The terminal device side communication unit 201 is connected to the network 30 or can be connected to the network 30. The terminal device side management unit 202 is connected to the terminal device side communication unit 201 and the terminal device side processing execution history storage unit 208. The terminal device side processing distribution unit 203 is connected to the terminal device side management unit 202, and also includes a terminal device side processing execution history storage unit 208, a terminal device side processing execution plan storage unit 209, and a terminal device side processing correspondence table storage unit 210. It is connected to the. The terminal device side load measurement unit 204 is connected to the terminal device side process distribution unit 203, the terminal device side process execution history storage unit 208, and the terminal device side process execution unit 205. The terminal device side processing execution unit 205 is connected to the terminal device side processing distribution unit 203. The GUI component operation function unit 206 is connected to the GUI component unit 207.

[1.1.2.1. Terminal device side communication section]
The terminal device side communication unit 201 has a function of performing data transmission / reception between the terminal device 20 and the server 10 via the network 30. The terminal device side communication unit 201 is realized by a wireless LAN board, a network adapter, or the like, for example.

[1.1.2.2. Terminal device side management unit]
The terminal device side management unit 202 has a function of controlling execution of each process of each unit in the terminal device 20. The terminal device side management unit 202 corresponds to the first management unit of the present embodiment.

[1.1.2.3. Terminal device side processing distribution unit]
The terminal device side processing distribution unit 203 determines whether each unit process included in the process execution plan information is performed by the terminal device 20 or the server 10, and based on the determination result, each unit process is performed by the terminal device 20 or the server. 10 has a function to be executed. The terminal device side processing distribution unit 203 corresponds to the first determination unit of the present embodiment.

[1.1.2.4. Terminal device side process execution history storage unit]
The terminal device side process execution history storage unit 208 has a function of storing process execution history information. The process execution history information has the same data configuration as the process execution history information stored by the server-side process execution history storage unit 108. The terminal device side process execution history storage unit 208 corresponds to the first storage unit of the present embodiment.

  The process execution history information (referred to as “terminal device side process execution history information”) stored in the terminal device side process execution history storage unit 208 is stored in the server side process execution history storage unit 108 during the initialization process described later. Only the record 510 whose execution location is the same as the terminal type of the terminal device 20 or the record 510 whose execution location is the server 10 is extracted from the processing execution history information (referred to as “server-side processing execution history information”) The data composed of these extracted records 510 is stored as terminal device side process execution history information.

  FIG. 4 shows a data configuration example of the terminal apparatus side process execution history information generated from the process execution history information 500S shown in FIG. Similarly to the process execution history information 500S, the terminal apparatus side process execution history information 500T is data having one record 510 for each unit process, and each record 510 is information for identifying a corresponding unit process (for example, A field 521 for storing a unit process name), a field 522 for storing information for specifying a request source of the process, a field 523 for storing information for specifying the execution location of the unit process, and a load value of the unit process. Field 524 is included.

[1.1.2.5. Terminal device side processing execution plan storage unit]
The terminal device-side process execution plan storage unit 209 has a function of storing process execution plan information, which is information describing processes executed by the system 1 by connecting small processes (“unit processes”). The terminal device side process execution plan storage unit 209 corresponds to the first storage unit of the present embodiment.
This process execution plan information is data having the same data configuration as the process execution plan information stored in the server-side process execution plan storage unit 109.

[1.1.2.6. Terminal device side processing correspondence table storage unit]
The terminal device side process correspondence table storage unit 210 is a process correspondence table that is information in which information specifying unit processes described in the process execution plan information is associated with information specifying unit processes to be actually executed. It has a function of storing information. The terminal device side processing correspondence table storage unit 210 corresponds to the first storage unit of the present embodiment. This processing correspondence table information is data having the same data configuration as the processing correspondence table information stored in the server side processing correspondence table storage unit 110 described above.

[1.1.2.7. Terminal device side load measurement unit]
The terminal device side load measurement unit 204 measures the load of each unit process executed in the server 10, and the load value obtained as a result of the measurement is stored in the terminal device side process execution plan storage unit 209. It has a function of writing in execution history information. The terminal device side load measuring unit 204 corresponds to the first measuring unit of the present embodiment.

[1.1.2.8. Terminal device side processing execution unit]
The terminal device side process execution unit 205 has a function of executing a unit process determined to be executed by the terminal device 20 by the terminal device side process distribution unit 203. The terminal device side process execution unit 205 corresponds to the first measurement unit of the present embodiment.

  The terminal apparatus side process execution unit 205 has all unit processes 111 whose execution environment is the terminal apparatus 20 and all unit processes 111 whose execution environment is both the server 10 and the terminal apparatus 20. Note that the unit processing 111 in which the execution environment is both the server 10 and the terminal device 20 is provided with information (for example, processing name) for specifying different unit processing on the server 10 side and the terminal device 20 side. The information for specifying the unit process in the execution plan information, the information for specifying the unit process on the server 10 side, and the information for specifying the unit process on the server 10 side are associated with each other by the process correspondence table information.

[1.1.2.9. GUI parts]
The GUI component unit 207 functions as a component constituting a GUI (Graphical User Interface) of the web application.

[1.1.2.10. GUI part operation function part]
The GUI component operation function unit 206 provides a function for operating the GUI component provided by the GUI component unit 207.

[1.2. Example of operation]
[1.2.1. Example of overall system operation]
The overall operation of the web application system 1 according to the present embodiment will be described. FIG. 9 is a sequence diagram showing an example of initialization processing in the web application system 1. FIG. 10 shows a data example of the process execution plan information 600 stored in the terminal device side process execution plan storage unit 209 and the server side process execution plan storage unit 109 at the time of starting the initialization process. The process execution plan information 600 shown in FIG. 10 describes a process execution plan whose contents are to execute the unit process 1, the unit process 3, and the unit process 4 in order. The unit process 1 and the unit process 4 are described as processes that can be executed by the “terminal device”, and the unit process 3 is described as a process that can be executed by both the server and the terminal device.

  Moreover, in the web application system 1, the load value obtained when the load of each unit process is measured by the terminal device 20 or the server 10 is assumed as shown in FIG. FIG. 11 is a diagram showing process execution history information storing a load value assumed to be obtained when the loads of the unit processes 1 to 4 are measured.

  12 shows processing correspondence table information 700T stored in the terminal device side processing correspondence table storage unit 210, and FIG. 13 shows processing correspondence table information stored in the server side processing correspondence table storage unit 110. 700S is shown. Note that the processing correspondence table information 700S does not have any unit processing records.

[1.2.1. Initialization process]
The operation of the initialization process of the web application system 1 will be described with reference to FIG. This “initialization process” is a process for matching the process execution history information between the terminal device 20 and the server 10.

  In the initialization process, when the terminal device 20 is activated by power-on or the like, the terminal device 20, more specifically, the terminal device side management unit 202 transmits terminal type information to the server 10, more specifically, the server side management unit 102 ( S101). The terminal type information is information that identifies the model of the terminal device 20 and the like.

The server 10, more specifically, the server-side management unit 102, causes the terminal device 20 to use the process execution history information stored in the server-side process execution history storage unit 108 based on the terminal type information. Process execution history information is generated (S102). The process execution history information to be used by the terminal device 20 is a record 510 in which type information corresponding to the terminal device 20 is stored in a field 523 that stores an execution location (synonymous with execution environment, the same applies hereinafter), And the processing execution history information rewritten so as to include only the record 510 in which the information indicating the server is stored in the field 523 for storing the execution location. The server 10, more specifically, the server-side management unit 102 transmits the process execution history information generated in step S102 to the terminal device 20 (S103).
This is the end of the initialization process.

[1.2.2. Process execution starting from terminal device]
With reference to FIGS. 14 and 15, an operation of executing a process execution plan when a process execution request is issued from the terminal device 20 in the web application system 1 will be described. FIG. 14 is a sequence diagram illustrating an example of the execution operation of the process execution plan at the terminal device starting point in the web application system 1, and FIG. 15 is a sequence diagram subsequent to FIG.

  First, the terminal device 20, more specifically, the terminal device side management unit 202 receives a process execution request input from a user (S201). The process execution request input is, for example, an icon tap, an application activation, or the like.

  The terminal device 20 that has received the processing execution request input, more specifically, the terminal device side management unit 202 passes the processing execution request to the terminal device side processing distribution unit 203 (S202). It is assumed that information specifying an execution environment, information indicating a processing request source, and information indicating a communication load are added to the processing execution request.

  The terminal device side processing distribution unit 203 that has received the processing execution request is stored in the information specifying the execution environment, the information indicating the processing request source, the information indicating the communication load, and the terminal device side processing execution plan storage unit 209. The estimated value of the processing load is calculated from the processing execution plan information and the terminal device side processing execution history storage unit 208 processing execution history information (S203).

  Next, the terminal device-side process distribution unit 203 performs the unit process up to the terminal device 20 out of a plurality of series of unit processes included in the process execution plan information based on the estimated value of the processing load calculated in step S203. In step S204, it is determined whether to execute the process. The unit processing range determined in step S204 is referred to as “terminal-side processing range”.

  Next, the terminal device side process distribution unit 203 executes each of the unit processes included in the terminal side process range in the order described in the process execution plan information (S205). However, the terminal device side processing distribution unit 203 reads the processing correspondence table information stored in the terminal device side processing correspondence table storage unit 210 when executing the unit processing, and performs processing (for example, unit processing) described in the processing execution plan information. A unit process corresponding to the process 4), which is described in the process correspondence table information (unit process 4A) is executed.

  In accordance with the execution of step S205, the terminal device side load measuring unit 204 measures each load of the unit processing included in the terminal side processing range (S206). The terminal device side load measurement unit 204 writes the load value obtained as a result of the above measurement into the process execution history information stored in the terminal device side process execution history storage unit 208 (S207).

  Next, the terminal device side processing distribution unit 203 passes to the terminal device side management unit 202 an instruction to request the server 10 to execute the unit processing after the terminal side processing range in the processing execution plan (S208). Receiving this command, the terminal device side management unit 202 transmits an execution request message for requesting execution of unit processing after the terminal side processing range in the processing execution plan to the server 10, more specifically to the server side management unit 102 (S209). ).

  Further, the terminal device side management unit 202 reads out the process execution history information stored in the terminal device side process execution history storage unit 208, and transmits this process execution history information to the server 10, more specifically, to the server side management unit 102. (S210).

  The server-side management unit 102 that has received the process execution history information replaces the process execution history information stored in the server-side process execution history storage unit 108 with the process execution history information received from the terminal device 20 in step S210 (update). (S211).

  The server-side management unit 102 requests the server-side process distribution unit 103 to execute the unit process (there may be a plurality of cases) specified in the execution request message transmitted in step S209 (S212).

  The server-side process distribution unit 103 requested to execute the unit process has the process execution plan information stored in the server-side process execution plan storage unit 109 and the process stored in the server-side process execution history storage unit 108. Based on the execution history information, an estimated value of the processing load of each unit process specified in the execution request message is calculated (S213).

Based on the estimated value, the server-side process distribution unit 103 determines how many unit processes to be executed by the server 10 among the unit processes included in the process execution plan information (S214). The unit processing range determined in step S214 is referred to as a “server-side processing range”.
The server-side process distribution unit 103 sequentially executes unit processes (multiple cases in this case) included in the server-side process range determined in step S214 (S215).

  After the execution of the unit processes included in the server-side processing range is completed, the server-side process distribution unit 103 passes to the server-side management unit 102 an instruction for requesting execution of the unit processes after the server-side processing range in the process execution plan ( S216). Upon receiving this command, the server-side management unit 102 transmits an execution request message for requesting execution of a unit process after the server-side processing range in the processing execution plan to the terminal device 20, more specifically, to the terminal device-side management unit 202 ( S217).

  In addition, the server-side management unit 102 includes, in the process execution history information stored in the server-side process execution history storage unit 108, data in a row where the “execution location” matches the terminal type of the terminal device 20, or “ Data of records (rows) whose “execution location” matches the server 10 is extracted, and the data of these records (rows) is transmitted to the terminal device side management unit 202 as processing execution history information (S218).

Thereafter, the terminal device side management unit 202 returns to the above-described step S202, and continues the processing after step S202.
When the web application system 1 completes the execution of all the unit processes included in the process execution plan, the web application system 1 ends the process execution plan process that is the operation at the terminal side starting point.
This is the end of the description of the process execution at the terminal device starting point.

[Concrete example]
A specific example of the initialization process and the process execution of the terminal device starting point will be shown.
FIG. 16 shows the process execution history information stored in the terminal device side process execution history storage unit 208 before starting the initialization process (referred to as “terminal device side process execution history information 500T” for distinction), and the server side. A data example of the process execution history information stored in the process execution history storage unit 108 (referred to as “server-side process execution history information 500S” for distinction) is shown. In FIG. 16, (A) is the terminal apparatus side process execution history information 500T, and (B) is the server side process execution history information 500S. Before the start of the initialization process, both the terminal device side process execution history information 500T and the server side process execution history information 500S are empty.

  FIG. 17 shows a data example of the terminal-side process execution history information 500T and the server-side process execution history information 500S at the time when the steps S101 to S103 are completed after the state shown in FIG. Since the server-side process execution history information 500S remains empty, the terminal device-side process execution history information 500T is also empty.

  FIG. 18 shows a data example of the terminal-side process execution history information 500T and the server-side process execution history information 500S at the time when the steps S201 to S205 are completed after the state shown in FIG. The terminal device side process execution history information 500T illustrated in FIG. 18 stores the load value measured by the terminal device side load measurement unit 204. This value is based on the data shown in FIG. The server-side process execution history information 500S remains empty at this point.

  In step S201 to step S205, the terminal device side processing distribution unit 203 that receives the processing request for unit processing 1 from the terminal device side management unit 202 executes unit processing 1 on the terminal device 20 or causes the server 10 to execute it. Is determined based on the terminal device side process execution history information 500T. The load value of the unit process 1 is “14” when executed by the terminal device 20 and “0” when executed by the server 10, so communication (load value is 20). Is selected), the execution of the unit process 1 in the terminal apparatus 20 is selected, the execution of the unit process 1 is instructed to the terminal apparatus side process execution unit 205, and the terminal apparatus side process is executed. The unit 205 executes unit processing 1. Since the execution of the unit process 1 is now completed, the terminal device side process distribution unit 203 does not transmit a process request for the unit process 1 to the terminal device side management unit 202.

  Next, the terminal device side processing distribution unit 203 that has received the processing request for the unit processing 3 from the terminal device side management unit 202 determines whether to execute the unit processing 3 on the terminal device 20 or on the server 10 side. The determination is made based on the process execution history information 500T. Since the load value of the unit process 3 is “100” when executed by the terminal device 20 and the load value when “executed by the server 10 is“ 0 ”, communication (load value is 20). The terminal unit side management unit 202 is instructed to request the server 10 to execute the unit process 3. At this time, the terminal device side management unit 202 transmits the terminal device side processing execution history information 500T shown in FIG.

  The server 10 that has received the terminal device side processing execution history information 500T, more specifically, the server side processing distribution unit 103, uses the server side processing execution history information 500S stored in the server side processing execution history storage unit 108 as the terminal device. The side processing execution history information 500T is updated to be captured.

  Next, the server 10, more specifically, the server-side process distribution unit 103, determines whether the unit process 3 is to be executed by the terminal device 20 or executed by the server 10 based on the server-side process execution history information 500S. Since the load value of the unit process 3 is “100” when executed by the terminal device 20 and the load value when “executed by the server 10 is“ 0 ”, communication (load value is 20). The terminal unit side management unit 202 is instructed to request the server 10 to execute the unit process 3.

  In response to the execution request for the unit process 3 received from the terminal device side management unit 202, the server side process execution unit 105 is instructed to execute the unit process 3, and the server side process execution unit 105 executes the unit process 3. The server-side load measuring unit 104 measures the load value of the unit process 3, and writes the measured load value in the server-side process execution history information 500S. As a result, a record having the process name “process 3”, the request source “terminal”, the execution location “server”, and the load “10” is added to the server-side process execution history information 500S. A data example of the terminal device side process execution history information 500T and the server side process execution history information 500S in this state is shown in FIG.

  Next, since the execution environment of the unit process 4 is only the terminal device 20, the server side process distribution unit 103 instructs the server side management unit 102 to request the terminal device 20 to execute the unit process 4. The server side management unit 102 transmits an execution request message for the unit process 4 to the terminal device 20, more specifically, to the terminal device side management unit 202.

  At this time, the server-side management unit 102 generates processing execution history information for the terminal device from the server-side processing execution history information 500S shown in FIG. 19, and process execution history information for the terminal device. It transmits to the apparatus side management part 202.

  The terminal device 20 that has received the processing execution history information for the terminal device, more specifically, the terminal device side management unit 202 is stored in the terminal device side processing execution history storage unit 208 based on the processing execution history information. The contents of the side process execution history information 500T are updated.

Further, the terminal device 20, more specifically the terminal device side management unit 202, passes the execution request for the unit process 4 to the terminal device side process distribution unit 203 based on the execution request for the unit process 4 from the server 10. The terminal apparatus side process distribution unit 203 requests the terminal apparatus side process execution unit 205 to execute the unit process 4, and the terminal apparatus side process execution unit 205 executes the unit process 4. The terminal device side load measuring unit 204 measures the load value of the unit process 4 (the load when the server 10 is the request source and the execution environment is the terminal device), and receives the measurement result. 203 writes the value of this load in the terminal apparatus side process execution history information 500T. FIG. 20 shows data examples of the terminal apparatus side process execution history information 500T and the server side process execution history information 500S at this point.
Thereafter, the terminal device 20 continues the description on the assumption that the process execution plan including the unit process 1, the unit process 3, and the unit process 4 is further executed.

  When the terminal device-side management unit 202 requests the terminal device-side process distribution unit 203 to execute the unit process 1, the terminal device-side process distribution unit 203 causes the terminal device-side process execution unit 205 to execute the unit process 1.

  Next, the terminal device side processing distribution unit 203 determines whether the unit processing 3 is executed by the terminal device 20 or the server 10 based on the content of the terminal device side processing execution history information 500T illustrated in FIG. . In the terminal device side process execution history information 500T, with respect to the load value of the unit process 3, the load value when executed by the terminal device 20 is “100”, and the load value when executed by the server 10 is “10”. Since it is described that the terminal device side processing distribution unit 203 considers communication (the load value is measured as 20), the unit in the server 10 having a smaller load value is used. The execution of the process 3 is selected, and the terminal device side management unit 202 is instructed to request the server 10 to execute the unit process 3. At this time, the terminal device side management unit 202 transmits the terminal device side processing execution history information 500T shown in FIG.

  The server 10 that has received the terminal device side process execution history information 500T shown in FIG. 20, more specifically, the server side management unit 102, stores the server side process execution history information 500S stored in the server side process execution history storage unit 108. The terminal device side process execution history information 500T is updated so as to be taken in. FIG. 21 shows a data example of the terminal device side process execution history information 500T and the server side process execution history information 500S at this time.

  Next, the server 10, more specifically, the server-side management unit 102, instructs the server-side process distribution unit 103 to execute the unit process 3 in response to the execution request for the unit process 3 received from the terminal device-side management unit 202. The server-side process distribution unit 103 determines whether to cause the terminal device 20 to execute the unit process 3 or the server 10 based on the contents of the server-side process execution history information 500S illustrated in FIG. In the server-side process execution history information 500S, the load value of the unit process 3 is “100” when it is executed by the terminal device 20, and “10” when it is executed by the server 10. Therefore, the terminal device side processing distribution unit 203 considers communication (assuming that the load value is measured as 20), and unit processing 3 in the server 10 having a smaller load value. And execution of the unit process 3 is instructed to the server side process execution unit 105, and the server side process execution unit 105 executes the unit process 3. The server-side load measuring unit 104 measures the load value of the unit process 3, and writes the measured load value in the server-side process execution history information 500S.

  Next, since the execution environment of the unit process 4 is only the terminal device 20, the server side process distribution unit 103 instructs the server side management unit 102 to request the terminal device 20 to execute the unit process 4. The server side management unit 102 transmits an execution request for the unit process 4 to the terminal device 20, more specifically, to the terminal device side management unit 202.

  At this time, the server-side management unit 102 transmits the process execution history information generated for the terminal device from the terminal device-side process execution history information 500T illustrated in FIG. 21 to the terminal device 20, and more specifically to the terminal device-side management unit 202.

  The terminal device 20 that has received the process execution history information, more specifically, the terminal device side management unit 202, based on the process execution history information, stores the terminal device side process execution history stored in the terminal device side process execution history storage unit 208. The contents of the information 500T are updated.

Further, the terminal device 20, more specifically the terminal device side management unit 202, passes the execution request for the unit process 4 to the terminal device side process distribution unit 203 based on the execution request for the unit process 4 from the server 10. The terminal apparatus side process distribution unit 203 requests the terminal apparatus side process execution unit 205 to execute the unit process 4, and the terminal apparatus side process execution unit 205 executes the unit process 4. The terminal device side load measuring unit 204 measures the load value of the unit process 4 (the load when the server 10 is the request source and the execution environment is the terminal device), and receives the measurement result. 203 writes the value of this load in the terminal apparatus side process execution history information 500T. FIG. 22 shows data examples of the terminal apparatus side process execution history information 500T and the server side process execution history information 500S at this time.
This is the end of the description of the specific example.

[1.2.2.2. Example of operation of terminal device side processing distribution unit and server side processing distribution unit]
Next, operations of the terminal device side processing distribution unit 203 and the server side processing distribution unit 103 will be described. FIG. 23 shows a flowchart showing an example of the main operation (referred to as “process distribution processing”) of the terminal device side processing distribution unit 203 and the server side processing distribution unit 103, and FIG. 24 shows a flowchart following FIG. . In the following description, the processing distribution processing by the “terminal device side processing distribution unit” will be described.
In the process distribution process, the terminal apparatus side process distribution unit 203 reads one process execution plan information from the terminal apparatus side process execution plan storage unit 209 (S301).

  Next, the terminal device-side process distribution unit 203 is a unit process that does not include its own execution environment as an execution environment of the unit process in the series of unit processes described in the process execution plan information read in step S301. Thus, the first unit process to be executed (referred to as “unit process A”) is extracted (S302).

  Next, the terminal device side process distribution unit 203 determines whether or not the unit process A satisfying the above condition exists in the series of unit processes (S303). If it is determined in step S303 that the unit process A satisfying the above condition exists in the series of unit processes (S303, Yes), the terminal device side process distribution unit 203 selects any one of the series of unit processes. Two unit processes (referred to as unit process B and unit process C) are selected (S304). However, the unit process C must be a unit process that is executed at the same time as or later than the unit process B, and the total amount of load from the execution of the unit process B to the execution of the unit process C (the load amount BC and Must be smaller than the total load (load amount BC) when the execution of the unit process B to the execution of the unit process C is executed in the other execution environment.

Next, the terminal device side processing distribution unit 203 calculates the total amount of loads (referred to as load amount S) when all the series of unit processes are executed in its own environment (S305).
Next, the terminal device side processing distribution unit 203 determines whether or not the load amount S is equal to or less than the load amount BC (S306).

  In step S306, when it is determined that the load amount S is equal to or less than the load amount BC (S306, Yes), the terminal device side process distribution unit 203 sequentially performs each of the series of unit processes in its own execution environment. (S307). However, for the first unit process, the process request source is the passed process request source, and the subsequent processes are their own execution environment. It is assumed that the unit process to be actually executed is determined from the process request source and the process correspondence table.

Next, the terminal apparatus side process distribution unit 203 updates the process execution history information stored in the terminal apparatus side process execution history storage unit 208 based on the load value of each unit process executed in step S307 ( Rewrite) (S308).
The terminal device side process distribution unit 203 ends the process distribution process for the process execution plan information.

  Returning to step S303 described above, the description of the process distribution process is continued. In step S303, when it is determined that the unit process A that satisfies the above condition does not exist in the series of unit processes (S303, No), the terminal device side process distribution unit 203 selects any one of the series of unit processes. A unit process (referred to as unit process D) is selected (S309). However, the unit process D is a unit process that is processed the same as or earlier than the unit process A, and the unit process group after the unit process D in the series of unit processes is executed in the other execution environment. Assume that the total amount of load at the time is minimal. In the calculation of the total amount of loads here, only the load up to the unit process A is considered, and the loads after the unit process A are ignored.

  Next, the terminal apparatus side process distribution unit 203 executes each unit process before the unit process D in the series of unit processes (S310). However, for the first unit process to be executed, the request source of the process is the request source of the passed process, and the subsequent unit process is the own execution environment. It is assumed that the unit process to be actually executed is determined from the process request source and the process correspondence table.

  Next, the terminal device side process distribution unit 203 updates the process execution history information stored in the terminal device side process execution history storage unit 208 based on the load value of each unit process executed in step S310 ( Rewrite) (S311).

  Next, the terminal device side processing distribution unit 203 requests the terminal device side management unit 202 to execute the unit process D (S312). Thereafter, the terminal apparatus side process distribution unit 203 ends the process distribution process for the process execution plan information.

  Returning to step S306 described above, the description of the process distribution process is continued. If it is determined in step S306 that the load amount S is not less than or equal to the load amount BC (S306, No), the terminal device side process distribution unit 203 redefines the unit process B as a unit process D (S313). . The unit process D is a unit process that meets the conditions described in step S309. After step S313, the terminal device side processing distribution unit 203 proceeds to step S310 described above, and continues the processing distribution processing.

  This is the end of the description of the process distribution process. In the above description, the processing distribution processing has been described as the operation of the terminal device side processing distribution unit 203. However, the terminal device side processing distribution unit 203 is replaced with the server side processing distribution unit 103, and the terminal device side management unit is described. By replacing 202 with the server-side management unit 102 and replacing the terminal device-side process execution plan storage unit 209 with the server-side process execution plan storage unit 109, the processing distribution process in the server-side process distribution unit 103 is explained.

[1.2.2.2. Operation example of terminal device side management unit]
Below, operation | movement of the terminal device side management part 202 is demonstrated.
[1.2.2.2.1. Terminal device side communication time measurement processing]
A terminal device side communication time measurement process which is one of the processes executed by the terminal device side management unit 202 will be described. FIG. 25 is a flowchart showing an example of the terminal device side communication time measurement process which is one of the main operations of the terminal device side management unit 202.

  In the terminal device side communication time measurement process, the terminal device side management unit 202 transmits a communication time measurement request message to the server side management unit 102 via the network 30 (S401). Next, the terminal device side management unit 202 receives a response message returned from the server side management unit 102 via the network in response to the communication time measurement request message, and based on the reception time of the response message. The communication time is calculated, and the calculated communication time is stored (S402). Thus, the terminal device side management unit 202 ends the terminal device side communication time measurement process. Note that the terminal device side communication time measurement process may be performed at any time, but may be performed using, for example, the execution of step S101 described above as a trigger, or at a predetermined timing, for example, when the terminal device 20 is turned on. You may make it perform every progress of predetermined time.

[1.2.2.2.2. Terminal device side communication time measurement request reception processing]
The terminal device side communication time measurement request reception process, which is one of the processes executed by the terminal device side management unit 202, will be described. FIG. 26 is a flowchart showing an example of processing at the time of receiving a terminal device side communication time measurement request, which is one of the main operations of the terminal device side management unit 202. The terminal device side communication time measurement request reception process is a process executed by the terminal device 20 when the terminal device 20 receives a communication time measurement request message from the server 10.

  In the terminal device side communication time measurement request reception process, the terminal device side management unit 202 generates a response message, which is a message indicating that the communication time measurement request message has been received, and sends the response message to the server side management unit 102. Send via (S501). Thus, the terminal device side management unit 202 ends the terminal device side communication time measurement request reception process.

[1.2.2.3. Operation example of server side management unit]
Next, the operation of the server side management unit 102 will be described.
[1.2.2.3.1. Server side communication time measurement process]
The server side communication time measurement process which is one of the processes executed by the server side management unit 102 will be described. FIG. 27 is a flowchart showing an example of server-side communication time measurement processing that is one of the main operations of the server-side management unit 102.

  In the server side communication time measurement process, the server side management unit 102 transmits a communication time measurement request message to the terminal device side management unit 202 via the network 30 (S601). Next, the server side management unit 102 receives a response message returned from the terminal device side management unit 202 via the network 30 in response to the communication time measurement request message, and based on the reception time of the response message. The communication time is calculated and the calculated communication time is stored (S602). Thus, the server side management unit 102 ends the server side communication time measurement process. The server side communication time measurement process may be performed at any time, but may be performed every time a predetermined timing and a predetermined time come.

[1.2.2.3.2. Processing when server side communication time measurement request is received]
FIG. 28 is a flowchart showing an example of a server-side communication time measurement request reception process, which is one of the main operations of the server-side management unit 102. The server side communication time measurement request reception process is a process executed by the server 10 when the server 10 receives a communication time measurement request message from the terminal device 20.

  In the server-side communication time measurement request reception process, the server-side management unit 102 generates a response message that indicates that the communication time measurement request message has been received, and sends the response message to the terminal device-side management unit 202 via the network 30. Send via (S701). Thus, the server-side management unit 102 ends the server-side communication time measurement request reception process.

[4. advantage]
A unit process that can be executed by both the terminal device 20 and the server 10 is dynamically allocated to and executed by either the terminal device 20 or the server 10 according to the amount of load when executed in each execution environment. Is possible.

  Further, according to the present embodiment, since the server 10 and the terminal device 20 accumulate the process execution history information 500, the unit process execution place determination by the terminal device side process distribution unit 203 and the server side process distribution unit 103 is determined. The method makes it possible to converge to an appropriate distribution method.

  Depending on the flow of the process (whether or not the process 3 is executed on the server), the process can be automatically switched (for example, when the process 3 is executed on the terminal device 20, the process 4A is executed on the server 10). If so, process 4B).

[5. Summary, etc.]
As mentioned above, although embodiment of this invention was described, this invention is not limited to these, A various change, addition, a combination, etc. are possible in the range which does not deviate from the meaning of invention.

  DESCRIPTION OF SYMBOLS 1 ... Web application system; 10 ... Server; 20 ... Terminal device; 30 ... Network; 102 ... Server side management part; 103 ... Server side process distribution part; 104 ... Server side load measurement part; 202 ... Terminal device side management unit; 203 ... Terminal device side processing distribution unit; 204 ... Terminal device side load measurement unit; 205 ... Terminal device side processing execution unit

Claims (5)

Process execution plan information, which is information describing a process using a unit process, information specifying a unit process, information specifying a request source of the process, information specifying an execution environment of the unit process, and the unit First storage means for storing the value of the processing load and the first processing execution history information having;
A first measurement unit that measures the load of each unit process executed by the first execution unit, and writes the value of the load obtained as a result of the measurement in the first process execution history information;
First execution means for executing the unit processing designated by the first determination means or the second determination means in the first execution environment;
Determining whether to execute each unit process included in the process execution plan information in the first execution environment or the second execution environment based on the load value included in the first process execution history information And first determination means for causing each of the unit processes to be executed by either the first execution means or the second execution means based on the result of the determination;
The same information as the process execution plan information, information specifying a unit process, information specifying a process request source, information specifying an execution environment of the unit process, and a load value of the unit process Second storage means for storing second processing execution history information;
A second measuring unit that measures the load of each unit process executed by the second executing unit, and writes the value of the load obtained as a result of the measurement in the second process execution history information;
Second execution means for executing the unit processing designated by the first determination means or the second determination means in a second execution environment;
Determining whether to execute each unit process included in the process execution plan information in the first execution environment or the second execution environment based on a load value included in the second process execution history information Then, based on the result of this determination, second determination means for causing each of the unit processes to be executed by either the first execution means or the second execution means,
A web application system. The first determination means refers to the load value included in the first process execution history information, and determines the load value of the unit process in the first execution environment and the second execution environment. Compare the value of the load of the unit process with the total value of the load on communication, determine which of the first execution unit and the second execution unit to execute the unit process,
The second determination means refers to the load value included in the second process execution history information, and the load value of the unit process in the first execution environment and the total load of communication, 2. The web according to claim 1, wherein a load value of the unit process in the second execution environment is compared to determine which of the first execution unit and the second execution unit to execute the unit process. Application system. First management means for transmitting terminal type information, which is information specifying the type or type of the terminal device;
Based on the terminal type information, from the second process execution history information, a record storing information corresponding to the terminal type information as information for specifying the execution environment, and information for specifying the execution environment A second management unit that extracts a record in which information indicating the server is extracted, generates third processing execution history information including the extracted record, and transmits the third processing execution history information to the first management unit; And
The web application system according to claim 1 or 2, wherein the first management means stores the third process execution history information in the first storage means as new second process execution history information. The first management means transmits the first process execution history information to the second management means,
4. The web application system according to claim 3, wherein the second management unit updates the second process execution history information based on the received first process execution history information. The first storage means is information in which information specifying a unit process described in the process execution plan information is associated with information specifying a unit process executed by the first execution means. Further storing processing correspondence table information,
The second storage means is information in which information for specifying a unit process described in the process execution plan information is associated with information for specifying a unit process to be executed by the second execution means. 5. The web application system according to claim 1, further storing processing correspondence table information.

Images