JP4777285B2 - Process control system - Google Patents

Description

  The present invention relates to a network distributed processing technology that distributes service requests to a plurality of physical servers, and in particular, can reduce the labor of a system administrator when changing the physical configuration or logical configuration of a network distributed processing environment. It relates to a process control system.

As a distributed system having a plurality of physical servers that provide a service in response to a service request, for example, a database system described in Patent Document 1 is known. In this system, a standby physical server that is the switching destination in the event of a failure is defined in advance for the active physical server that provides the database service, and a failure of the active physical server is detected. Then, system switching from the active physical server to the standby physical server is performed.
JP 2001-282863 A

  By the way, in a distributed system having a plurality of physical servers that logically configure a virtual server that provides a service in response to a service request, the physical configuration is changed (physical server is added or deleted) or the logical configuration is changed ( When a startup process is added, deleted, or the number of startups is changed), the system administrator reviews the distributed arrangement of processes for physical servers. Accordingly, the system administrator needs to reset the process to be started for each physical server. As described above, the system administrator is required to perform complicated resetting operations in order to cope with changes in the physical configuration or logical configuration of the system.

  Therefore, an object of the present invention is to provide a process control system capable of reducing the work cost required for changing the physical configuration and logical configuration in a network distributed processing environment.

  A process control system according to an embodiment of the present invention includes a plurality of physical servers configuring a virtual server that provides a service, and a database server including a shared database that can be referred to by each of the physical servers. The at least one first physical server included in the plurality of physical servers includes physical node list information related to one or more physical servers constituting the virtual server, and service list information defining a plurality of services provided by the virtual server. And an allocation table in which any of the processes related to the plurality of services is allocated to each physical server constituting the virtual server based on the received physical node list information and service list information. Allocation table creating means. And the said allocation table is registered into the said shared database, Each physical server which comprises the said virtual server performs the process allocated to each physical server with reference to the said allocation table.

  In a preferred embodiment, the device further comprises a console terminal that receives input of the physical node list information and the service list information and transmits an allocation table creation request to the first physical server, and the allocation table creation means includes the In response to an allocation table creation request, the physical node list information and the service list information may be acquired from the console terminal, and the allocation table may be generated based on the physical node list information and the service list information. .

  In a preferred embodiment, the console terminal may include a trigger generation unit that generates a start trigger specifying a process to be started and provides the start trigger to each physical server. At this time, each physical server is identified by the activation trigger with reference to the allocation table when receiving the activation trigger and the data storage means storing the program for realizing the process related to the service. A process for realizing the process to be activated specified by the activation trigger is read from the data storage means if the process is allocated to the own physical server. And a process activation means for activating the activation target process.

  In a preferred embodiment, the console terminal may include a trigger generation unit that generates a start trigger specifying a process to be started and provides the start trigger to each physical server. At this time, when each physical server includes data storage means storing a program for realizing the process related to the service, and the given message includes identification information of the own physical server, the message A process starting unit that reads a program that realizes the process specified in step 1 from the data storage unit and starts the start target process by executing the program, and starts the process of the physical server to which the start trigger is given The means acquires the identification information of the physical server to which the activation target process specified in the activation trigger is allocated with reference to the allocation table, and includes the designation of the activation target process and the identification information of the physical server A message may be given to each physical server.

  In a preferred embodiment, the allocation table creating unit generates an allocation table further including a definition of a state of a process allocated to each physical server, and the process activation unit of each physical server refers to the allocation table. Then, it is determined whether or not the status of the startup target process is before startup, and if the status of the startup target process is before startup, the startup target process is started and the physical server in the allocation table The state of the activation target process may be updated.

  In a preferred embodiment, the allocation table creating unit generates an allocation table further including a definition of the number of processes started allocated to each physical server, and the process startup unit of each physical server includes the allocation table The activation target process may be activated so that the number of activation target processes indicated by the defined activation number is being activated in the physical server.

  In a preferred embodiment, the console terminal may be a second physical server included in the plurality of physical servers.

  Hereinafter, a process control system according to an embodiment of the present invention will be described with reference to the drawings.

  FIG. 1 is a schematic configuration diagram of a process control system according to the present embodiment.

As shown in the figure, this process control system includes physical servers 10 and 10A that logically configure virtual servers that provide services in response to external service requests, and job schedules on each physical server 10. An operation management server 20 to be managed, a database server 30 having a database that can be referred to from all the physical servers 10 and 10A, and a console terminal 40 that receives data input from a user such as a system administrator are provided. The information processing apparatuses 10, 10A, 20, 30, 40 such as each server are connected to a LAN (Local
Are connected to each other via a network 50 such as an area network or the Internet.

  The console terminal 40 may be realized as a dedicated terminal by an independent server machine, or may be realized by mounting the function on any of the physical servers 10.

  Each of the physical servers 10, 10A, the operation management server 20, the database server 30, and the console terminal 40 is configured by, for example, a general-purpose computer system, and each of the servers, etc. 10, 10A, 20, 30, 40 described below Individual components or functions are realized, for example, by executing a computer program.

  Each of the physical servers 10 and 10A includes a data storage unit 11 in which a program for realizing a service process is stored, a monitoring unit 14 for monitoring the operating state of the own physical server, and a program and a monitoring unit for realizing a service process. 14 includes a process activation unit 13 that activates a program or the like that implements 14, and a transmission / reception unit 12 that transmits and receives data via the network 50.

  As will be described later in detail, the process activation unit 13 refers to an allocation table 311 of the database server 30 and reads a predetermined program from the data storage unit 11 to activate a process allocated to the own physical server.

  As will be described later in detail, the monitoring unit 14 acquires a trigger from the network 50 via the transmission / reception unit 12.

  Furthermore, any one physical server 10A has an allocation table generation unit 15 that generates an allocation table in which allocation of service processes to the physical servers 10 and 10A is defined.

  The allocation table generation unit 15 generates an allocation table that is referred to by all the physical servers 10 and 10 </ b> A and registers it in the shared database 31 of the database server 30. Here, any one physical server 10A has the allocation table creation unit 15. However, all the physical servers 10, 10A have the same allocation table generation unit 15 provided to all the physical servers 10, 10A. Therefore, the allocation table may be registered (new registration or update registration) in the shared database 31 of the database server 30.

  The database server 30 includes a shared database 31 in which the allocation table 311 is stored, and a database processing unit 32 that executes database processing in response to an external request.

  The shared database 31 can be referred to from each physical server 10, 10A. Therefore, each physical server 10, 10 </ b> A can refer to the allocation table 311 stored in the shared database 31.

  The console terminal 40 includes an input / output processing unit 41 that controls the input device and the output device, a data storage unit 44 that stores information received by the input / output processing unit 41, and a virtual on each physical server 10 and 10A. It has a trigger processing unit 42 that generates a process activation trigger that triggers the start of server operation, and a transmission / reception unit 43 that transmits and receives data via the network 50.

  The input / output processing unit 41 receives input of data such as node list information that is a list of the physical servers 10 and 10A belonging to the node group that constitutes the virtual server, and service list information that is a list of services provided by the virtual server. .

  The data storage unit 44 stores node list information 441, service list information 442, and the like.

  The trigger processing unit 42 generates a process activation trigger according to an instruction from the job scheduler 21 and outputs the process activation trigger to the network 50 via the transmission / reception unit 43.

  The operation management server 20 has a job scheduler 21 that gives a service start instruction to the console terminal 40 according to a predetermined schedule.

  The job scheduler 21 gives a service start instruction to the console terminal 40 as a trigger for generating a process activation trigger.

  Next, the data structure of the allocation table 311 and the data structures of the node list information 441 and the service list information 442 used for generation thereof will be described.

  FIG. 2 is a diagram for explaining the data structure of the allocation table 311, and FIGS. 3A and 3B are diagrams for explaining the data structure of the node list information 441 and the service list information 442.

  The allocation table 311 shown in FIG. 2 stores allocation information for each physical server. Each allocation information includes physical server name information 3111 which is identification information of the physical server, and process information 3112 for each service allocated to the physical server. For example, when a plurality of services (two services in this case) are allocated to one physical server, as shown in the record 3113, the allocation information includes the number of services associated with the physical server name information 3111. Process information (here, two process information 3112A and 3112B) are included. The process information 3112 includes service name information 31121 that is service identification information, an activation process number 31122 that is the activation number of the service process, and status information 31123 that is information representing the operating state of the service process. It is.

  In the node list information 441 shown in FIG. 3A, group information for each node group constituting the virtual server is stored. Each group information includes group name information 4411 which is node group identification information and physical server name information 4412 of one or more physical servers belonging to the node group.

  In addition, service list information 442 shown in FIG. 3B stores service information for each service. Each service information includes service name information 4421 of the service, number of activation processes 4422 indicating the number of activation of the required service processes, and group name information 4423 of the node group to which the service is allocated.

  Next, processing executed in the process control system of FIG. 1 will be described. The process executed in the process control process is divided into a process control process and a pre-process executed prior to the process control process. These processes will be described in the order of pre-processing and process control processing.

  FIG. 4 is a flowchart of the preprocessing. Here, it is assumed that all the physical servers 10A and 10 have equivalent processing performance.

  When the user instructs the console terminal 40 to register group information (group name information, physical server name information) for each node group using the input device, the input / output processing unit 41 responds to the instruction with the node list information. 441 is generated, and the inputted group information is registered as a record of the node list information 441. The input / output processing unit 41 stores the node list information 441 in the data storage unit 44 (S100).

  Further, when the user instructs the console terminal 40 to register service information (service name information, number of activation processes, group name information) for each service using the input device, the input / output processing unit 41 responds to the instruction. The service list information 442 is generated, and the input service information is registered as a record of the service list information 442. The input / output processing unit 41 stores the service list information 442 in the data storage unit 44 (S110).

  Thereafter, when the user instructs the console terminal 40 to create an allocation table using the input device, the input / output processing unit 41 sends an allocation table creation request via the transmission / reception unit 43 in advance according to the instruction. It transmits to one defined physical server 10A.

  In the physical server 10 </ b> A, when the allocation table creation unit 15 receives an allocation table creation request from the console terminal 40 via the transmission / reception unit 12, it sends a reference request for the node list information 441 and service list information 442 to the transmission / reception unit 12. To the console terminal 40. In response to the reference request, the transmission / reception unit 43 of the console terminal 40 reads the node list information 441 and the service list information 442 from the data storage unit 44 and sends back.

  Thereafter, in the physical server 10A, when the allocation table creation unit 15 receives the node list information 441 and the service list information 442 from the console terminal 40 via the transmission / reception unit 12, each virtual server is based on the information 441 and 442. Allocates the service provided by the physical node in the corresponding node group. For example, group information is read from the physical node list information 441, and all service information including group name information 4423 that matches the group name information 4411 of the group information is extracted from the service list information 442. The number of application processes corresponding to the number of activation processes 4422 of each service information is determined with the number of startable processes obtained by a performance test performed in advance in the physical server 10A as the maximum number of activation processes per physical server. The physical server corresponding to the physical server name information 4412 in the group information is distributed.

  And the allocation table preparation part 15 produces | generates allocation information based on the result of such allocation. In the status information 31123 of the process information 3112 of each allocation information generated here, information “SBY” indicating that the process is in a pre-startup state is registered. Furthermore, the allocation table creation unit 15 generates an allocation table 311 and registers the allocation information generated at this time in the allocation table 311 (S120).

  Thereafter, the allocation table creation unit 15 transmits a registration request for the allocation table 311 to the database server 30 via the transmission / reception unit 12. In response to this registration request, the database processing unit 32 of the database server 30 registers the allocation table 311 in the shared database 31 (S130). Thereby, the allocation table 311 is centrally managed in the shared database 31, and all the physical servers 10A and 10 can refer to the common allocation table 311.

  Thereafter, in the physical server 10 </ b> A, when the allocation table creation unit 15 receives a registration success notification from the database server 30 via the transmission / reception unit 12, it instructs the process activation unit 13 to activate the process that implements the monitoring unit 14. At the same time, a monitoring process activation request is transmitted to another physical server 10 via the transmission / reception unit 12. Thereby, the process starting part 13 starts the process which implement | achieves the monitoring part 14, Similarly, the process starting part 13 starts the process which implement | achieves the monitoring part 14 also in the other physical server 10 (S140).

  Through the above preprocessing, the allocation table 311 that can be referred to by all the physical servers 10A and 10 is registered in the shared database 31 of the database server 30, and the monitoring unit 14 on all the physical servers 10A and 10 Start monitoring the operating status of the server. Thereafter, in the process control system, process control processing for starting activation of the service process on the virtual server is executed at a timing scheduled in advance.

  FIG. 5 is a flowchart of the process control process.

  The job scheduler 21 of the operation management server 20 transmits a process activation message including a service process designation to the console terminal 40 according to a predetermined schedule. In the console terminal 40, when the trigger processing unit 42 receives this process activation message via the transmission / reception unit 43, a process activation trigger including service name information corresponding to the designated service process is sent to all the physical servers 10A and 10. Send.

  On each physical server 10A, 10, when the process activation unit 13 receives a process activation trigger via the transmission / reception unit 12 (S200), the service name included in this process activation trigger via the transmission / reception unit 12 A reference request including the information and the physical server name information of the own physical server is transmitted to the database server 30. When the database processing unit 32 of the database server 30 receives this reference request, the process information 3112 of the allocation information is obtained from the allocation table 311 of the shared database 31 using the service name information and physical server name information included therein as keys. Search is performed (S210).

  As a result, if the corresponding process information 3112 (the process information including the specified service name information in the allocation information including the specified physical server name information) is not obtained, that is, the specified service process is assigned to the specified physical server. If not assigned (S220: No), the database processing unit 32 returns a message indicating that the search has failed. The physical server that has received this reply message, that is, the physical server to which the designated service process is not assigned performs no processing.

  On the other hand, if the process information 3112 of the corresponding allocation information is obtained, that is, if the designated service process is assigned to the designated physical server (S220: Yes), the database processing unit 32 returns the process information. The process activation unit 13 of the physical server that has received this process information, that is, the physical server to which the designated service process is allocated, indicates that the status information included in this process information is the state before activation. It is determined whether or not it is “SBY” (S230).

  As a result, if the status information is not “SBY”, the process activation unit 13 discards the process activation trigger. In other words, even if the designated service process is assigned to the physical server, if the process is being activated or stopped, the process activation trigger is discarded (S260).

  If the status information is “SBY”, the process activation unit 13 reads a program corresponding to the service name information included in the process activation trigger from the storage unit 11, and the number of activation processes 31122 in the process information 3112 obtained in S220. The program is executed so that the processes of the number indicated by are activated on the own physical server (S240).

  As a result, when the designated service process starts operation by the number corresponding to the number of activated processes 31122 in the allocation table 311, the process activation unit 13 determines the service name information corresponding to the activated process and the physical server name information of the own physical server. An update request including new status information (“RUN” indicating the activated state) is transmitted to the database server 30 via the transmission / reception unit 12.

  In response to this update request, the database processing unit 32 of the database server 30 updates the allocation table 311 of the shared database 31. As a result, among the process information 3112 in the allocation information including the physical server name information 3111 that matches one key, the status information 31123 of the process information 3112 that includes service name information that matches the other key is in a state before starting. Is updated from “SBY” representing that the current state is “RUN” representing the active state (S250).

  In addition to the service name information, the process activation trigger generated by the trigger processing unit 42 may include physical server name information to which a process related to the service name information is assigned. This is because when the trigger processing unit 42 receives a process activation message from the job scheduler 21, the trigger processing unit 42 transmits a reference request including service name information corresponding to the designated service process to the database server 30, and the allocation table of the shared database 31. In 311, the physical server name information to which the service name information is assigned is acquired.

  In this way, the physical server 10 that has received the process activation trigger can determine whether or not there is a service assigned to the own physical server in step S220 by using the process activation trigger without performing step S210 of the above processing. Thereby, the processing performance of the physical server 10 that has received the process activation trigger can be improved, and the processing load on the database server 30 can be reduced.

  According to the pre-processing and process control processing according to the present embodiment, since the allocation table in which the allocation of service processes to physical servers is defined is managed centrally in a shared database that can be referenced from all physical servers, Based on the allocation information in the allocation table, the physical server starts the process allocated to itself. For this reason, for example, when changing the physical configuration of the system (adding and deleting physical servers) and changing the logical configuration (adding and deleting active processes, changing the number of startups), the allocation registered in the shared database It is sufficient to update only the table. That is, it is sufficient for the system administrator to edit the node list information and the service list information on the console terminal 40 in order to update the shared database allocation table, and to create the allocation table. There is no need to reconfigure the process to be started. For this reason, the work cost required for changing the physical configuration and the logical configuration of the network distributed processing environment can be reduced.

  In this embodiment, a process activation trigger including service name information corresponding to a designated service process is given to all physical servers 10A and 10, and the designated service process is assigned to the own physical server in all physical servers. It is not always necessary to do this.

  For example, a process activation trigger including service name information corresponding to a designated service process is given to only one physical server, and the process activation unit of this physical server has process information 3112 including service name information corresponding to the designated service process and Corresponding physical server name information 3111 may be acquired from the allocation table 311 of the shared database 31 and a message including such information may be notified to all the physical servers in cooperation. If the physical server name information is included in the cooperation notification message, the process activation unit of each physical server that has received the notification determines that the cooperation notification message is addressed to itself, and the process is the same as in the above case. Based on the information, execute the corresponding program so that the specified service process is active for the number of startup processes on the local physical server, and if the physical server name information is not included in the link notification message, the link notification It may be determined that the message is not addressed to itself and the cooperation notification message is discarded.

  In the present embodiment, the case where only one allocation table is registered in the shared database 31 is exemplified. For example, calendar information is defined in the service list information, and the operation calendar provided by the operation management server 20 is provided. An allocation table may be generated and registered for each. Thereby, for example, the allocation table referred to by the physical server can be switched in conjunction with the operation calendar provided by the operation management server 20.

  By the way, in the process control system according to the present embodiment, if any failure or the like occurs in any physical server, the service process assigned to the physical server is reassigned to another physical server. . This will be described below. Here, a case where a stop cause event such as a failure occurs in the physical server 10 is taken as an example.

  When the monitoring unit 14 on the physical server 10 detects the occurrence of a stop cause event such as a failure, the physical server name information of the own physical server 10 and the service (stop) assigned to the own physical server 10 are transmitted via the transmission / reception unit 12. Service) and a reallocation request including the number of processes (the number of stopped processes) is transmitted to a predetermined physical server 10A.

  Alternatively, a monitoring unit that monitors the state of the other physical server 10 is further provided on the physical server 10, and when this monitoring unit detects the occurrence of a stop cause event of the physical server 10, the physical server 10 A reallocation request including server name information may be transmitted to the physical server 10A.

  In the physical server 10A, when the allocation table generation unit 15 accepts the reassignment request via the transmission / reception unit 12, the status update request using the physical server name information in which the cause of the stoppage occurred included in the request as a key. Is transmitted to the database server 30 via the transmission / reception unit 12. This status update request includes information for updating the status information (“STP” indicating that the status is stopped). In response to this status update request, the database processing unit 32 of the database server 30 updates the allocation table 311 of the shared database 31. As a result, the status information 31123 of the process information 3112 of the allocation information including the physical server name information 3111 matching the key, that is, the status information 31123 of the stop service is “RUN” indicating that it is in the active state. It is updated to “STP” indicating that it is in a stopped state.

  Further, in the physical server 10A, the allocation table generation unit 15 reallocates processes for the number of stopped processes to, for example, other normally operating physical nodes in the node group to which the physical server 10 in which the stop cause event has occurred belongs. To do. The reassignment at this time may be performed according to any rule, but an example thereof is as follows.

  First, the allocation table generation unit 15 transmits a reference request for the node list information 441 to the console terminal 40 via the transmission / reception unit 12. In response to this reference request, the transmission / reception unit 43 of the console terminal 40 reads the node list information 441 from the data storage unit 44 and returns it to the physical server 10A.

  Thereafter, when the allocation table generation unit 15 receives the node list information 441 via the transmission / reception unit 12, the allocation table generation unit 15 obtains the physical server name information of other physical servers belonging to the same node group as the source of the reallocation request, as the node list information. Read from 441. Of those physical servers, the allocation information of physical servers that are operating normally (allocation information including physical server name information that matches the physical server name information read from the node list information 441) A search request for the status information of the process information is not “STP”) is transmitted to the database server 30 via the transmission / reception unit 12. In response to this search request, the database processing unit 32 of the database server 30 reads allocation information corresponding to the search condition from the allocation table 311 of the shared database 31 and returns it to the physical server 10A.

  When the allocation table creation unit 15 receives the allocation information that matches the search condition via the transmission / reception unit 12, any allocation process of the physical server is started based on the number of startup processes of the process information included in the allocation information. The number of stop service processes corresponding to the number of stop processes is allocated to normally operating physical servers belonging to the same node group as the source of the reallocation request so that the number does not exceed the above-described upper limit of start processes.

  The allocation table creation unit 15 generates allocation information of physical nodes to which the stop service process is newly allocated based on the result of such reallocation. Of the process information included in the allocation information generated at this time, information “SBY” indicating the pre-startup state is registered in the status information 31123 of the process information 3112 including the service name information of the stop service.

  Thereafter, the allocation table creation unit 15 transmits an allocation information update request using the physical node name information of the physical node to which the stop service process is newly allocated as a key to the database server 30 via the transmission / reception unit 12. This allocation information update request includes allocation information of the physical node to which the stop service process is newly allocated.

  In response to this allocation information update request, the database processing unit 32 of the database server 30 updates the allocation table 311 of the shared database 31. As a result, the allocation information including the physical server name information 3111 that matches the key is updated with new allocation information.

  When the allocation table is updated in this way, the allocation table creation unit 15 transmits a process activation message specifying the stop service process as an activation target to the console terminal 40 via the transmission / reception unit 12. In the console terminal 40, when the trigger processing unit 42 receives this process activation message via the transmission / reception unit 43, the process activation trigger including the service name information corresponding to the designated service process, as described above, It transmits to all the physical servers 10A and 10.

  As a result, each physical server 10A, 10 refers to the allocation table 311 of the shared database 31 by the same processing as described above, and the allocated activation is performed only when the stop service process in the pre-activation state is allocated. The program corresponding to the stop service process is executed so that the stop service processes for the number of processes are activated on the local physical server.

  According to the process control system according to the present embodiment, the system administrator resets the process to be started for each physical server when the physical configuration and logical configuration of the network distributed processing environment are changed. Since it is not necessary, the work cost required for changing the physical configuration and logical configuration of the network distributed processing environment can be reduced.

  The above-described embodiments of the present invention are examples for explaining the present invention, and are not intended to limit the scope of the present invention only to those embodiments. Those skilled in the art can implement the present invention in various other modes without departing from the gist of the present invention.

1 is a schematic configuration diagram of a process control system according to an embodiment of the present invention. It is a conceptual diagram of the data structure of an allocation table. (A) is a conceptual diagram of the data structure of node list information, (B) is a conceptual diagram of the data structure of service list information. It is a flowchart of the pre-process performed prior to a process control process. It is a flowchart of a process control process.

Explanation of symbols

10, 10A Physical server 11 Data storage unit 12 Transmission / reception unit 13 Process activation unit 14 Monitoring unit 15 Assignment table generation unit 20 Operation management server 21 Job scheduler 30 Database server 31 Shared database 32 Database processing unit 40 Console terminal 41 Input / output processing unit 44 Data storage unit 42 Trigger processing unit 43 Transmission / reception unit 50 Network

Claims (9)

A plurality of physical servers constituting a virtual server that provides services;
A database server having a shared database that can be referred to by each of the physical servers,
At least one first physical server included in the plurality of physical servers includes:
Means for receiving physical node list information relating to one or more physical servers constituting the virtual server, and service list information defining a plurality of services provided by the virtual server;
Allocation table creating means for generating an allocation table in which any of the processes related to the plurality of services is allocated to each physical server constituting the virtual server based on the received physical node list information and service list information And comprising
In the shared database, the allocation table is registered,
Each physical server that constitutes the virtual server specifies a process assigned to each physical server with reference to the assignment table , and executes the specified process. A console terminal that accepts input of the physical node list information and the service list information and transmits an allocation table creation request to the first physical server;
The allocation table creating means acquires the physical node list information and the service list information from the console terminal in response to the allocation table creation request, and the allocation table is created based on the physical node list information and the service list information. The process control system according to claim 1, wherein: The console terminal is
A trigger generation unit that generates a start trigger that identifies a process to be started and provides the start trigger to each physical server;
Each physical server is
Data storage means storing a program for realizing the process related to the service;
When the activation trigger is received, it is determined whether or not the process specified by the activation trigger is allocated to the own physical server with reference to the allocation table. If the process is allocated to the own physical server, the activation is performed. 3. The process control system according to claim 2, further comprising: a process activation unit that reads out a program for realizing the activation target process specified by the trigger from the data storage unit and activates the activation target process. The console terminal is
A trigger generation unit that generates a start trigger that identifies a process to be started and provides the start trigger to each physical server;
Each physical server is
Data storage means storing a program for realizing the process related to the service;
When the given message includes identification information of the own physical server, the program that realizes the process specified in the message is read from the data storage unit, and the process to be started is started by executing the program And a process starting means,
The process starting means of the physical server to which the start trigger is given,
Referring to the allocation table, the identification information of the physical server to which the activation target process specified in the activation trigger is allocated is acquired, and the message including the designation of the activation target process and the identification information of the physical server is The process control system according to claim 2, wherein the process control system is provided to each physical server. The allocation table creating means generates an allocation table further including a definition of a state of a process allocated to each physical server;
The process activation means of each physical server refers to the allocation table to determine whether or not the state of the activation target process is pre-activation, and if the state of the activation target process is pre-activation, 5. The process control system according to claim 3, wherein the process to be started is started and the state of the process to be started of the physical server in the allocation table is updated. The allocation table creating means generates an allocation table further including a definition of the number of processes started allocated to each physical server,
The process activation unit of each physical server activates the activation target process so that the number of activation target processes indicated by the activation number defined in the allocation table is activated in the physical server. The process control system according to any one of claims 3, 4, and 5.   The process control system according to claim 2, wherein the console terminal is a second physical server included in the plurality of physical servers. In a process control system comprising a plurality of physical servers constituting a virtual server providing a service, and a database server comprising a shared database that can be referred to by each of the physical servers,
At least one first physical server included in the plurality of physical servers includes:
Receiving physical node list information on one or more physical servers constituting the virtual server and service list information defining a plurality of services provided by the virtual server;
Based on the received physical node list information and service list information, generate an allocation table in which any of the processes related to the plurality of services is allocated to each physical server constituting the virtual server,
The database server registers the allocation table in the shared database;
A process control method, characterized in that each physical server constituting the virtual server identifies a process allocated to each physical server with reference to the allocation table and executes the identified process. A computer program for a process control system comprising a plurality of physical servers constituting a virtual server that provides a service, and a database server comprising a shared database that can be referred to by each of the physical servers,
When the computer program is executed,
At least one first physical server included in the plurality of physical servers includes:
Receiving physical node list information on one or more physical servers constituting the virtual server and service list information defining a plurality of services provided by the virtual server;
Based on the received physical node list information and service list information, generate an allocation table in which any of the processes related to the plurality of services is allocated to each physical server constituting the virtual server,
The database server registers the allocation table in the shared database;
A computer program characterized in that each physical server constituting the virtual server specifies a process assigned to each physical server with reference to the assignment table and executes the specified process .

Images