JP4128971B2 - Grid computing system - Google Patents

Description

The present invention, in any of the client device that requested to provide the service to the server apparatus enjoys the service from the server device grid computing system relates.

In general, a grid computing system includes a management search device that monitors an operating state of a server device that provides a service. The client device of the grid computing system determines which server device can provide the service by inquiring of the search device for management which server device can provide the target service. After the determination, the server apparatus is requested to provide a service to the determined server apparatus.

  In the above-described conventional grid computing system, the client device determines whether to request the server device to execute the target service based on information obtained from the management search device. The management search device must be able to always provide real-time information about each server device to the client device.

  However, since it is impossible in reality to construct a robust search device that never goes down, even if the client device makes an inquiry to the down search device, information about each server device is obtained. There was a problem that could not be obtained.

  In order to solve such a problem, a method of preparing a plurality of search devices having the same information can be considered. However, when a plurality of search devices are prepared, a problem of so-called synchronization shift that a content of information shifts in time with respect to each server device to be shared among the search devices is newly generated.

  The present invention has been made in view of the conventional problems as described above, and the problem is to provide each client device with real-time information regarding each server device even if the management search device goes down. It is to provide a grid computing system that can.

  Another object of the present invention is to provide a server device, a search device, and a client device that constitute such a grid computing system, and an information providing program that causes the computer to function as such a server device. is there.

A grid computing system devised to solve the above problem is a grid computing system in which a client device requests a service from any server device to receive the service from the server device. a I ring system, each pre-hexa over server device, and dynamic information indicating its own operation status, and dynamic information indicating the operating status of at least one other server unit stores, self When dynamic information changes, its own dynamic information recorded in another server device is updated. When the client device requests its own dynamic information, the client device receives If the client device requests dynamic information of another server device by providing its own dynamic information to the client device, Providing broadcast for the client device, the client connected to a plurality of retrieval devices, both, in order to identify the service server identification information and the server device can be provided for identifying the server device Static information that associates service identification information with server identification information of other server apparatuses that store dynamic information of the server apparatus is stored for each server apparatus, and from any client apparatus, When the service identification information is received, server identification information corresponding to the service identification information is provided to the client device, and the client device acquires the server identification information of the server device that can provide the target service. Server identification information to determine whether to request the server device to provide service If the dynamic information is obtained from the server device and cannot be obtained from the server device, the dynamic information is obtained from another server device that stores the dynamic information of the server device. , With features.

  As described above, if the information recorded in the search device is limited to only static information that associates the server device with the service provided by the server, the same static information is recorded in a plurality of search devices. However, the search result provided to the client device does not differ for each search device. For this reason, even if some of the plurality of search devices go down, it is possible to always provide normal processing to the client device.

  In addition, when dynamic information indicating the operating status of the server device is recorded in some server devices different from the server device and the server device, and when the dynamic information of the server device has changed, When the dynamic information recorded in all of the other server devices is configured to be updated with the dynamic information after the change, the client device dynamically changes the server device that provides the target service. Even if the information cannot be obtained directly from the server device, the dynamic information having the same content as the dynamic information can be obtained from another server device, so that the client device can always provide the target service. It is possible to determine whether or not to request the provision of services.

  A server device invented to solve the above problem is a server device that provides a service to a client device when a client device of the grid computing system is requested to provide the service. Dynamic information indicating its own operating status and dynamic information indicating the operating status of at least one other server device are stored, and recorded in other server devices when changes occur in its own dynamic information. If the client apparatus requests dynamic information from the client apparatus, the client apparatus provides its own dynamic information to the client apparatus, and the client apparatus When dynamic information is requested, dynamic information of another server device is provided to the client device.

  Further, a search device invented to solve the above problem is a search device connected to a client device that enjoys a service from each server device in a grid computing system, and identifies each server device. Static information for associating server identification information for service with service identification information for identifying a service that the server device can provide is stored, and when any service identification information is received from any client device The server identification information corresponding to the service identification information is provided to the client device.

  A client device invented to solve the above problems is a client device for receiving a service from a server device of a grid computing system, and includes server identification information for identifying each server device and its client device. Any service from a search device storing static information that associates service identification information for identifying a service that can be provided by the server device with server identification information of another server device that stores dynamic information of the server device In order to acquire server identification information corresponding to the identification information and determine whether to request the server apparatus of the acquired server identification information to provide a service, the dynamic information is transmitted from the server apparatus of the server identification information. If the dynamic information cannot be obtained from the server device, the dynamic information of the server device is stored. That from another server apparatus that acquires the dynamic information, it is characterized.

  Accordingly, the server device, the search device, and the client device function as the server device, the search device, and the client device that constitute the grid computing system according to the present invention described above.

  In addition, an information providing program invented to solve the above-described problems provides information to a computer that provides a service to a client device when the client device of the grid computing system is requested to provide the service. An information providing program for adding a providing function, wherein the computer includes dynamic information indicating its own operating status, and dynamic information indicating an operating status of any server device of the grid computing system, Storing means in the storage device, when there is a change in its own dynamic information, updating means for updating its own dynamic information recorded in another server device, and other from the client device When the receiving device receives the information requesting the dynamic information of the server device, the client device Of that dynamic information of the server device to function as a communication means for transmitting via a transmission device is characterized.

  Therefore, according to this information providing program, the computer can function as an apparatus equivalent to the server apparatus according to the present invention described above.

  As described above, according to the present invention, even if the management search device goes down, real-time information regarding each server device can be provided to each client device.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments for carrying out the present invention will be described with reference to the accompanying drawings.

  FIG. 1 is a schematic diagram of a grid computing system according to an embodiment of the present invention. The grid computing system includes a client device 10, a service providing device 20, and a service search device 30, and these devices 10 to 30 are connected to each other via a network N.

  The client device 10 is a terminal device operated by a user who enjoys various services provided by each service providing device 20. Specifically, the client device 10 is a so-called personal computer, and includes a display device such as a liquid crystal display, an input device such as a keyboard and a mouse, and a main body connected to these devices. The main body includes a CPU [Central Processing Unit], a RAM [Random Access Memory], a communication adapter, an FDD [Flexible Disk Drive], a CDD [Compact Disk Drive], and an HDD [Hard Disk Drive]. In addition to the operating system program, the client program 11 is installed.

  The client program 11 is a program for receiving instructions from the operator and requesting each service providing apparatus 20 to enjoy the service. The contents of processing executed by the CPU according to the client program 11 will be described later.

  The service providing device 20 is a server device for providing various services to each client device 10. Specifically, the service providing apparatus 20 is a so-called general-purpose computer, and includes a CPU, a RAM, a communication adapter, and a storage device. In addition to the operating system program, one or more service providing programs among the service providing programs Sa to Se are installed in the storage device.

  The service providing programs Sa to Se are programs for adding a function for providing a service to the client device 10 to the general-purpose computer. Specific examples of services include physical, astronomical, and genetic advanced calculations, database search for product information and customer information, and processing by applications such as remote conferencing and remote monitoring. The service providing device 20 can provide services to the client device 10 by the number of service providing programs installed in the storage device. Further, as described above, the same service providing program may be installed in two or more service providing apparatuses 20.

  In the present embodiment, seven service providing apparatuses 20 are connected to the network N, and a service providing program Sa for providing the service A is recorded in the storage device of the first service providing apparatus 20. The service providing program Sb for providing the service B is recorded in the storage device of the second service providing device 20, and the service for providing the service C is stored in the storage device of the third service providing device 20. The providing program Sc is recorded, the service providing program Sd for providing the service D is recorded in the storage device of the fourth service providing device 20, and the service E is stored in the storage device of the fifth service providing device 20. A service providing program Se for providing the service is recorded. Further, a service providing program Sa for providing service A is recorded in the storage device of the sixth service providing device 20, and services C, D, and E are stored in the storage device of the seventh service providing device 20. Service providing programs Sc to Se for providing each are recorded.

  In addition, in addition to some of the service providing programs Sa to Se described above, the table group 20a and the program group 20b according to the present invention are installed in the storage device of the service providing apparatus 20. FIG. 2 is an explanatory diagram showing the table group 20a and the program group 20b installed in the storage device of the service providing apparatus 20. The table group 20a and the program group 20b shown in FIG. 2 are examples of the seventh service providing apparatus 20 on the rightmost side in the page of FIG.

  The table group 20 a includes a queue management table 21, an operation history management table 22, a schedule management table 23, and an operation status management table 24. Among these, the contents of the records recorded in the set of management tables 21 to 23 excluding the operation status management table 24 change from time to time in providing the service, and correspond to dynamic information.

  In this embodiment, a copy of the set of management tables 21 to 23 stored in the storage device by the service providing device 20 is recorded in the storage device of at least one other service providing device 20. Therefore, in addition to the set of management tables 21 to 23 used by the service providing apparatus 20 to manage its own dynamic information, other service providing apparatuses themselves are stored in the storage device of the service providing apparatus 20. In some cases, a copy of the management tables 21 to 23 used for managing the dynamic information is installed. In other words, the storage device of one service providing device 20 may store the management tables 21 to 23 for its own device and the management tables 21 to 23 for other devices. In this case, the management tables 21 to 23 for other devices stored in the storage device may be one set or two or more sets. In the case of two or more sets, the service providing devices 20 that use the management tables 21 to 23 are different for each set.

  Further, for example, two service providing apparatuses 20 may have management tables 21 to 23 for their own apparatuses and management tables 21 to 23 for other apparatuses. At this time, the management tables 21 to 23 for the own device and the management tables 21 to 23 for the other devices are recorded one by one in the storage device of one service providing device 20, and the other service providing device 20 is recorded. Similarly, one set for the own device and one for the other device are recorded in the storage device. Three or more service providing apparatuses 20 may have management tables 21 to 23 for their own apparatuses and management tables 21 to 23 for other apparatuses. At this time, one set of management tables 21 to 23 for the own apparatus and two or more sets of management tables 21 to 23 for other apparatuses are recorded in the storage device of one service providing apparatus 20.

  Below, the management tables 21-24 which the service provision apparatus 20 has memorize | stored in an own memory | storage device for its own apparatuses are demonstrated.

  The queue management table 21 is a table for managing execution instructions received from the client device 10 by the service providing device 20. FIG. 3 is a diagram illustrating an example of the data structure of the queue management table 21. The records in the queue management table 21 in FIG. 3 include “request management ID”, “request source”, “service name”, “parameter name”, “route server name”, “status”, and “status change date”. Field.

  Here, the “request management ID” is a field in which a request management ID, which is identification information uniquely assigned to each request in order to individually identify requests for executing the service providing programs Sa to Se, is recorded. . The “request source” is a field in which the address of the client apparatus 10 that has requested execution of the service is recorded. The “service name” is a field in which the name of the service requested to be executed by the client device 10 is recorded. The “parameter name” is a field in which the name of the parameter received as an argument from the client apparatus 10 together with the service execution request is recorded.

  In addition, the “route server name” is recorded as the route server name, which is the name of another service providing apparatus 20 that has received a request for execution of a service from the client apparatus 10 instead of the own apparatus and has been temporarily stored. It is a field. Note that when the client device 10 directly requests execution of a service from the client device 10, the “route server name” field is blank. “Status” is a field in which status information indicating whether this service has been executed, is being executed, or is waiting is recorded. The “status change date / time” is a field in which the year / month / day / hour / minute / second when the status information was last changed is recorded as status change date / time information.

  The operation history management table 22 includes events in the service providing apparatus 20 (accepting service execution requests to the own apparatus, starting execution of services, ending execution of services, terminating abnormally, and proxying service execution requests to other apparatuses) Etc.) is a table for recording information relating to such information. FIG. 4 is a diagram illustrating an example of the data structure of the operation history management table 22. The record in the operation history management table 22 of FIG. 4 has fields of “request management ID”, “event type”, “event occurrence date / time”, “target server name”, and “target service name”. Yes.

  Here, the “request management ID” is a field in which the request management ID is recorded. This request management ID is also assigned to a service execution request to another device received by this service providing device 20 on behalf of another device. However, the request management ID assigned to the request to the other apparatus in this way is not recorded in the queue management table 21 described above.

  The “event type” is a field in which the type of the event is recorded. The “event occurrence date / time” is a field in which the year / month / day / hour / minute / second when the event was performed is recorded as event occurrence date / time information. The “target server name” is a field in which the name of the service providing apparatus 20 for which a service execution request is made from the client apparatus 10 is recorded as the target server name. The “target service name” is a field in which the name of the service requested by the client device 10 is recorded.

  The schedule management table 23 is a table for managing a scheduled period in which the service providing apparatus 20 is stopped due to maintenance. FIG. 5 is a diagram illustrating an example of the data structure of the schedule management table 23. The record in the schedule management table 23 in FIG. 5 has fields of “schedule information” and “schedule time”.

  Here, “schedule information” is a field in which information indicating the start or stop of the operation of the service providing apparatus 20 is recorded. The “scheduled time” is a field in which a scheduled time at which the operation is started or stopped is recorded. These pieces of information are recorded in advance in the table 23 by the administrator.

  The operating status management table 24 is an operating status of the service providing device 20 and an operating status of the service providing device 20 that originally uses the management tables 21 to 23 for other devices recorded in the storage device of the service providing device 20. It is a table for recording. FIG. 6 is a diagram illustrating an example of the data structure of the operation status management table 24. The record in the operation status management table 24 of FIG. 6 has fields of “server name”, “operation status”, and “own / other information”.

  Here, the “server name” is the server name of the service providing apparatus 20 and the service providing apparatus 20 that originally uses the management tables 21 to 23 for other apparatuses recorded in the storage device of the service providing apparatus 20. The server name is a recorded field. The “operating status” is a field in which operating status information indicating whether each service providing apparatus 20 is operating or stopped is recorded. The “self-other information” is a field in which self-other information indicating whether the service providing apparatus 20 indicated by the server name is the own apparatus or another apparatus is recorded.

  The service search device 30 in FIG. 1 is a device for searching from which service providing device 20 each service is provided. Specifically, the service search device 30 is a general-purpose computer, and includes a CPU, a RAM, a communication adapter, and a storage device. In addition to the operating system program, a static information management table 31, a holding relationship management table 32, and a service search program 33 are installed in the storage device.

  The static information management table 31 is a table for recording information about the service providing apparatus 20 that provides each service. FIG. 7 is a diagram illustrating an example of the data structure of the static information management table 31. The record in the static information management table 31 of FIG. 7 has fields of “service name”, “server name”, “program name”, and “program argument”.

  Here, “service name” is a field in which the name of the service is recorded. The “server name” is a field in which the server name of the service providing apparatus 20 that provides the service is recorded. The “program name” is a field in which a name of a service providing program executed when providing the service is recorded. The “program argument” is a field in which all arguments that can be given as execution conditions at the time of execution of the service providing program whose name is recorded in the “program name” field of the same record are recorded. When the same service is provided from a plurality of service providing apparatuses 20, the static information management table 31 has as many records as the number of service providing apparatuses 20 that provide the service. .

  The holding relationship management table 32 is a table for recording which service providing device 20 holds a copy of the management tables 21 to 23 recorded for the own device in the storage device of the service providing device 20. is there. FIG. 8 is a diagram illustrating an example of the data structure of the possession relationship management table 32. The records in the holding relationship management table 32 in FIG. 8 have fields of “server name” and “copy holding server name”.

  Here, the “server name” is a field in which the server name of the service providing apparatus 20 is recorded. “Copy holding server name” stores a copy of the management tables 21 to 23 recorded for the own device in the storage device of the service providing device 20 in which the server name is recorded in the “server name” field of the same record. This is a field in which the server name of the service providing apparatus 20 possessed by the apparatus is recorded.

  The service search program 33 is a program for adding a function for searching in which service providing apparatus 20 each service is provided to a general-purpose computer. When the CPU according to the service search program 33 receives a request from any of the client devices 10, it corresponds to the server name of the service providing device 20 that provides the service specified for the client device 10 and the server name. The copy holding server name to be searched is searched from each of the tables 31 and 32, and the search result is notified to the client device 10.

  Hereinafter, the content of the process performed in the grid computing system of this embodiment comprised as mentioned above is demonstrated.

  In the service providing device 20, every time a predetermined time (for example, 10 minutes) elapses, the queue execution program 25 is read from the storage device by the CPU, and execution of the queue execution processing is started. FIG. 9 is a flowchart showing the contents of the queue execution process.

  In the first step S101 after the start of the queue execution process, the service providing device 20 records “standby” in the “status” field from the queue management table 21 stored in the storage device for its own device. Search for records. When the service providing apparatus 20 determines that the record having the status information of “standby” cannot be detected from the queue management table 21 for the own apparatus (S101; NO), the service providing apparatus 20 ends the queue execution process, If it is determined that a record having status information of “medium” has been detected from the queue management table 21 for the device itself (S101; YES), the process proceeds to step S102.

  In step S102, the service providing apparatus 20 includes the year / month / day / hour / minute / second indicated by the status change date / time information recorded in the “status change date / time” field among the records detected from the queue management table 21 for the own apparatus in step S101. Identify the record with the oldest value.

  In the next step S103, the service providing apparatus 20 reads the service providing program indicated by the service name recorded in the “service name” field of the record identified in step S102 from the storage device, and starts its execution. To do.

  In the next step S104, the service providing apparatus 20 switches the value in the “status” field of the record identified in step S102 from “standby” to “running”.

  In the next step S105, the service providing device 20 adds a new record to the operation history management table 22 recorded in its own storage device for its own device. In the “request management ID” field of this new record, the same request management ID in the “request management ID” field of the record identified in step S102 is recorded, and in the “event type” field, “service type” “Start” is recorded.

  In the next step S106, the service providing apparatus 20 has identified in step S102 for all the service providing apparatuses 20 that have a copy of the queue management table 21 recorded in its own storage device for its own apparatus. Notify event information including that the value in the “status” field of the record should be switched from “waiting” to “running” and the address of the requesting client device 10, the target service name, and the parameter name To do.

  In the next step S107, the service providing device 20 sends an operation history management table 22 to all the service providing devices 20 that have a copy of the queue management table 21 recorded in its own storage device for its own device. Event information including that a new record is to be added to and information (request management ID, event type, etc.) included in the new record is notified.

  In the next step S108, the service providing apparatus 20 stands by until the execution of the service providing program started in step S103 is completed (S108; NO). When the execution of the service providing program ends (S108; YES), the service providing apparatus 20 advances the process to step S109.

  In step S109, the service providing apparatus 20 switches the value in the “status” field of the record identified in step S102 from “executing” to “executed”.

  In the next step S110, the service providing device 20 adds a new record to the operation history management table 22 recorded in its own storage device for its own device. In the “request management ID” field of this new record, the same request management ID in the “request management ID” field of the record identified in step S102 is recorded, and in the “event type” field, “service type” “End” is recorded.

  In the next step S111, the service providing apparatus 20 specifies in step S102 for all the service providing apparatuses 20 that have a copy of the queue management table 21 recorded in its own storage device for its own apparatus. Notification of event information including the value in the “status” field of the record to be switched from “running” to “executed” and the address of the requesting client device 10, the target service name, and the parameter name To do.

  In the next step S112, the service providing device 20 sends an operation history management table 22 to all the service providing devices 20 that have a copy of the queue management table 21 recorded in its own storage device for its own device. Event information including that a new record is to be added to and information (request management ID, event type, etc.) included in the new record is notified. After the notification, the CPU 30 ends the queue execution process.

  Further, in the service providing apparatus 20, any client apparatus 10 or any service providing apparatus 20 that holds a copy of the management tables 21 to 23 recorded in its own storage device for its own apparatus. When the event information is transmitted, the event reception program 26 is read from the storage device by the CPU using the reception thereof as a trigger, and the execution of the event reception process is started. 10 and 11 are flowcharts showing the contents of the event reception process.

  In the first step S201 after the start of the event reception process, the service providing apparatus 20 is one of the service providing apparatuses 20 whose event information transmission source has copies of the management tables 21 to 23 for the own apparatus. It is determined whether or not there is. When the service providing apparatus 20 determines that the event information transmission source is not any of the service providing apparatuses 20 that have copies of the management tables 21 to 23 for the own apparatus (S201; NO), the event It is determined that the information is received from any client device 10, and the process proceeds to step S202.

  In step S202, the service providing apparatus 20 determines whether or not the received event information is information indicating a service execution request to itself. If it is determined that the received event information is not information indicating a service execution request to itself (S202; NO), the service providing device 20 records the event information in its own storage device for other devices. The management table 21 to 23 is determined to be information indicating a service execution request to the service providing apparatus 20, and the process proceeds to step S203.

  In step S203, the service providing apparatus 20 generates a new request management ID.

  In the next step S204, the service providing apparatus 20 adds a new record to the operation history management table 22 recorded in its own storage device for its own apparatus. The request management ID generated in step S203 is recorded in the “request management ID” field of this new record, “request accepted” is recorded in the “event type” field, and the “target server name” field is recorded. The server name of the service providing apparatus 20 that has received this service execution request is recorded.

  In the next step S205, the service providing apparatus 20 requests the service providing apparatus 20 that uses the management tables 21 to 23 recorded in its storage device for other apparatuses to execute a service addressed to the apparatus 20. The information received by the proxy, the fact that the respective tables 21 to 23 for the device related to the request should be updated, and various information necessary for updating the respective tables 21 to 23 for the device (of the client device) Event information including the address, the service name of the service requested to be executed, etc.).

  In the next step S206, the service providing apparatus 20 determines whether or not there is a response from the service providing apparatus 20 that has notified the event information in step S205. The response means that the service providing apparatus 20 transmits information related to the update of each table 21 to 23 based on the request addressed to the apparatus 20 accepted by the proxy. If it is determined in step S205 that there is no response from the service providing apparatus 20 that has notified the event information (S206; NO), the service providing apparatus 20 advances the process to step S207.

  In step S207, the service providing apparatus 20 changes the value in the “operating status” field of the record for the service providing apparatus 20 that did not respond in step S206 in the operating status management table 24 from “operating” to “stopped”. Switch to. After switching, the service providing apparatus 20 ends the event reception process.

  On the other hand, if the service providing apparatus 20 determines in step S206 that there is a response from the service providing apparatus 20 that has notified the event information in step S205 (S206; YES), the process proceeds to step S208.

  In step S208, the service providing apparatus 20a updates the management tables 21 to 23 recorded in its own storage device for the service providing apparatus 20 that has responded in step S206, based on various types of information received as a response. After the update, the service providing apparatus 20a ends the event reception process.

  On the other hand, if the service providing apparatus 20 determines in step S202 that the received event information is information indicating a service execution request to itself (S202; YES), the process proceeds to step S211.

  In step S211, the service providing apparatus 20 generates a new management ID.

  In the next step S212, the service providing apparatus 20 adds a new record to the queue management table 21 recorded in its own storage device for its own apparatus. The request management ID generated in step S211 is recorded in the “request management ID” field of this new record, “request accepted” is recorded in the “event type” field, and the “target server name” field is recorded. Records the server name of its own device.

  In the next step S213, the service providing apparatus 20 adds a new record to the operation history management table 22 recorded in its own storage device for its own apparatus. The request management ID generated in step S211 is recorded in the “request management ID” field of this new record, and “request acceptance” is recorded in the “event type” field.

  In the next step S214, the service providing apparatus 20 transmits the service addressed to the self apparatus to all the service providing apparatuses 20 having copies of the management tables 21 to 23 recorded in the storage apparatus for the self apparatus. The fact that the execution request has been received, the fact that the tables 21 to 23 for the own device related to the request should be updated, and various information necessary for updating the tables 21 to 23 for the own device (client device) Event information including the address of the service and the service name of the service requested to be executed). After the notification, the service providing apparatus 20 ends the event reception process.

  In step S201, the service providing apparatus 20 determines that the event information transmission source is any of the service providing apparatuses 20 that have copies of the management tables 21 to 23 for the own apparatus (S201). YES), the process proceeds to step S221.

  In step S221, the service providing apparatus 20 determines whether or not the value of the “operating status” field of the record for the service providing apparatus 20 that is the transmission source of the event information is “operating” in the operating status management table 24. Determine. Then, the service providing apparatus 20 determines that the value of the “operating status” field of the record for the service providing apparatus 20 that is the transmission source of the event information is “operating” in the operating status management table 24 (S221; YES). If the process proceeds to step S224 and it is determined in the operation status management table 24 that the value of the “operation status” field of the record for the service providing device 20 that is the transmission source of the event information is not “in operation” ( (S221; NO), the process proceeds to step S222.

  In step S222, the CPU switches the value of the “operation status” field of the record for the service providing apparatus 20 that is the transmission source of the event information from “stopped” to “active” in the operation status management table 24.

  In the next step S223, the service providing apparatus 20 reads records whose “target server name” field is not the server name of the own apparatus from the operation history management table 22 stored in the own storage apparatus for the own apparatus. The record is transmitted to the service providing apparatus 20 that is the event information transmission source. After the transmission, the service providing apparatus 20 advances the process to step S224.

  In step S224, the service providing apparatus 20 determines whether or not the received event information is information indicating a service execution request addressed to the own apparatus. If it is determined that the received event information is information indicating an execution request for a service addressed to the own apparatus (S224; YES), the service providing apparatus 20 advances the process to step S225.

  In step S225, the service providing apparatus 20 generates a new management ID.

  In the next step S226, the service providing device 20 adds a new record to the queue management table 21 recorded in its own storage device for its own device. The request management ID generated in step S225 is recorded in the “request management ID” field of this new record, “request accepted” is recorded in the “event type” field, and the “target server name” field is recorded. Records the server name of its own device.

  In the next step S227, the service providing apparatus 20 adds a new record to the operation history management table 22 recorded in its own storage device for its own apparatus. The request management ID generated in step S225 is recorded in the “request management ID” field of this new record, and “request acceptance” is recorded in the “event type” field.

  In the next step S228, the service providing apparatus 20 transmits the service addressed to the self apparatus to all the service providing apparatuses 20 having copies of the management tables 21 to 23 recorded in the storage apparatus for the self apparatus. The fact that the execution request has been received, the fact that the tables 21 to 23 for the own device related to the request should be updated, and various information necessary for updating the tables 21 to 23 for the own device (client device) Event information including the address of the service and the service name of the service requested to be executed). After the notification, the service providing apparatus 20 ends the event reception process.

  On the other hand, if it is determined in step S224 that the received event information is not information indicating a service execution request to itself (S224; NO), the service providing apparatus 20 advances the process to step S229.

  In step S229, the service providing device 20 updates the management tables 21 to 23 stored in its own storage device for other devices based on the received event information. For example, if the event information is status information switching (event information based on S106, S111, S214, or S228 executed by another service providing apparatus 20), the service providing apparatus 20 uses the queue management table 21 for other apparatuses. Switch the status information of the corresponding record in. If the event information is the addition of a new record to the operation history management table 22 (event information based on S107, S112, 205, or S223 executed in another service providing apparatus 20), the operation history management for other apparatuses is performed. A record having corresponding information is added to the table 22. After executing this step S229, the service providing apparatus 20 ends the event reception process.

  On the other hand, in the client device 10, when the execution of the client program is instructed by operating the input device, the CPU reads the client program from the HDD and starts the execution of the client process. 12 to 14 are flowcharts showing the contents of the client process.

  In the first step S301 after the start of the client process, the client device 10 displays an operation screen on the display device. FIG. 15 is a diagram illustrating an example of the operation screen 41.

  The operation screen 41 in FIG. 15 shows a text box 41a for inputting a service name. Further, on the operation screen 41 of FIG. 15, when the service providing apparatus 20 that can provide the service with the service name is searched and the search result is displayed, the service providing apparatus 20 is displayed in the speed priority order described later. Or two radio buttons 41b and 41c for selecting whether to display in order of quality priority.

  In addition, the operation screen of FIG. 15 shows a list 41d on which the search results are displayed. A record recorded as a search result in each row of the list 41d includes the server name, the server name of the service providing apparatus 20 that holds a copy of the dynamic information of the service providing apparatus 20 of the server name, and all the planned records. Each field includes a scheduled time when the execution of the service ends and a current operation state.

  Further, in the operation screen of FIG. 15, a search button 41e to be clicked when a service name is entered in the text box 41a, and a line to be clicked when any row in the list 41d is selected. An execution button 41f and a stop button 41g for clicking when ending the client process are shown.

  Note that nothing is listed in the list 41d of the operation screen 41 displayed on the display device in step S301. The execution button 41f is disabled so that it cannot be clicked. After displaying such an operation screen on the display device, the client device 10 advances the processing to step S302.

  In step S302, the client device 10 stands by until one of the search button 41e and the cancel button 41g on the operation screen 41 is clicked (S302; NO). When either the search button 41e or the cancel button 41g on the operation screen 41 is clicked (S302; YES), the client device 10 advances the process to step S303.

  In step S303, the client device 10 determines whether the clicked button is the search button 41e. When the client device 10 determines that the clicked button is not the search button 41e (S303; NO), the client device 10 ends the client process and determines that the clicked button is the search button 41e (S303; YES). ), The process proceeds to step S304.

  In step S304, the client device 10 searches the static information management table 31 using the service name input in the text box 41a when the search button 41e is clicked as a search condition, and holds the search result as the search condition. The service search device 30 is requested to search the relationship management table 32. In the service search device 30 that has received this request, the service search program is activated, service search processing is executed using the service name as a search condition, and each server name obtained as a result of the search is the client device 10. Sent to.

  In the next step S305, the client device 10 stands by until receiving each record as a search result from the service search device 30 (S305; NO). When each server name is received as a search result from the service search device 30, the client device 10 executes a first processing loop L1.

  In the first processing loop L1, the client device 10 sequentially executes steps S361 to S363 for all server names by specifying each server name received as a search result as a processing target one by one.

  In step S361, the client apparatus 10 requests the service providing apparatus 20 indicated by the processing target server name to transmit all the dynamic information (management tables 21 to 23) for the own apparatus.

  In the next step S362, the client device 10 determines whether or not dynamic information has been acquired from the service providing device 20. If the client device 10 determines that the dynamic information has been acquired from the service providing device 20 (S362; YES), the client device 10 ends the execution of the first processing loop L1 for the processing target server name, and the service providing device. If it is determined that the dynamic information could not be acquired from 20 (S362; NO), the process proceeds to step S363.

  In step S363, the client apparatus 10 receives a copy of the management tables 21 to 23 stored in the storage device by the service providing apparatus 20 indicated by the processing target server name. The dynamic information for the service providing apparatus 20 indicated by the processing target server name is acquired. Note that when there are a plurality of service providing apparatuses 20 having copies, the client apparatus 10 sequentially requests the apparatuses 20 to transmit dynamic information, and when the dynamic information can be acquired, step S363. The execution of is terminated. After execution of step S363, the client device 10 ends the execution of the first processing loop L1 for this processing target server name.

  After executing the first processing loop L1 for all server names received as search results, the client device 10 advances the process to step S306.

  In step S306, the client apparatus 10 determines which radio button 41b or 41c is selected when the search button 41e is clicked. When it is determined that the radio button selected when the search button 41e is clicked is the speed-priority radio button 41b (S306; YES), the client device 10 executes the second processing loop L2.

  In the second processing loop L2, the client device 10 sequentially executes steps S371 to S373 for all server names by specifying each server name received as a search result as a processing target one by one.

  In step S371, the client apparatus 10 counts the number of waiting queues by referring to the queue management table 21 of the processing target server name.

  In the next step S372, the client device 10 refers to the operation history management table 22 of the processing target server name, and determines the processing time when the service providing device 20 executes the service of the specified service name as the service Calculated from the start event occurrence date and time and the service end event occurrence date and time. When the service providing apparatus 20 has executed this service a plurality of times, the processing time is calculated by the number of times. Then, the client device 10 calculates the average processing time by dividing the calculated total processing time by the number.

  In step S373, when the service providing device 20 with the processing target server name is stopped, the client device 10 refers to the schedule management table 23 to calculate the time until the operation is resumed, The time obtained by adding the time to the average processing time calculated in step S372 is set as the scheduled required time. In addition, when the service providing apparatus 20 with the processing target server name is stopped, the client apparatus 10 sets the average processing time as the scheduled required time as it is. Thereafter, the client device 10 ends the execution of the first processing loop L2 for this processing target server name.

  After executing the second processing loop L2 for all server names received as search results, the client apparatus 10 advances the process to step S307.

  In step S307, the client apparatus 10 rearranges the records having the server names and the estimated required time as search results in the order of the estimated required time. After the rearrangement, the client device 10 advances the process to step S309.

  On the other hand, when the client apparatus 10 determines in step S306 that the radio button selected when the search button 41e is clicked is the quality-priority radio button 41c (S306; NO), the client apparatus 10 The third processing loop L3 is executed.

  In the third processing loop L3, the client device 10 sequentially executes steps S381 to S383 for all server names by specifying each server name received as a search result as a processing target one by one.

  In step S <b> 381, the client apparatus 10 counts the number of service providing apparatuses 20 that hold copies of the management tables 21 to 23 stored in its own storage apparatus for the service providing apparatus 20 having the server name to be processed. .

  In the next step S382, the client device 10 ends abnormally from the operation history management table 22 for each of the service providing devices 20 that owns a copy of the dynamic information for the own device of the service providing device 20 with the processing target server name. The frequency of occurrence (number of occurrences per unit time) is calculated.

  In the next step S383, the client apparatus 10 calculates the quality value by calculating the reciprocal of each occurrence frequency and then adding all the reciprocals. Thereafter, the client device 10 ends the execution of the third processing loop L3 for this processing target server name.

  The client device 10 executes the third processing loop L3 for all server names received as search results, and then proceeds to step S308.

  In step S308, the client device 10 rearranges records having the server names and quality values as search results in descending order of quality values. After the rearrangement, the client device 10 advances the process to step S309.

  In step S309, the client device 10 displays the server name as a search result and the scheduled end time of execution of the designated service by the service providing device 20 of the server name in the list 41d of the operation screen 41 being displayed on the display device. The records that are included are listed in the order rearranged in step S307 or S308. In addition, when the service providing device 20 with the server name is stopped, the service providing device 20 (dynamically) that receives a service execution request in place of the service providing device 20 is further included in the server name record. The server name of the service providing device 20) that holds a copy of the information is included. In addition, when both the service providing apparatus 20 with the server name and the service providing apparatus 20 with the copy are stopped, “service stopped” is described in the “status” field of the record having the server name. Is done. FIG. 16 is a diagram illustrating an example of the operation screen 41 in a state where search results are listed in the list 41d. In the operation screen 41 of FIG. 16, each row in the list 41d functions as a button that can select that row. When any row in the list 41d is selected, various types of information in the service providing apparatus 20 having the server name indicated in the row are displayed as a list box. FIG. 17 is a diagram illustrating an example of the operation screen 41 when the list box is displayed.

  In the next step S310, the client device 10 stands by until any one of the buttons 41e to 41g on the operation screen 41 is clicked (S310; NO). And when any one of each button 41e-41g in the operation screen 41 is clicked (S310; YES), the client apparatus 10 will advance a process to step S311.

  In step S311, the client device 10 determines whether the clicked button is the execution button 41f. When the client device 10 determines that the clicked button is the execution button 41f (S311; YES), the client device 10 executes the fourth processing loop L4.

  In the fourth processing loop L4, the client device 10 sequentially executes steps S391 to S395 for all records by specifying the records listed in the list 41d of the operation screen 41 as processing targets one by one. To do.

  In step S391, the client device 10 notifies the service providing device 20 having the server name in the processing target record of event information that requests execution of the designated service.

  In the next step S392, the client device 10 starts executing the standby process. Specifically, when the service providing program is an interrogation type, the client device 10 can obtain a response to the execution completion from the service providing program for periodically transmitting an inquiry about whether the execution has been completed. Repeat until. This process is executed in parallel with other processes in the client device 10. When the service providing program is an interrupt type, the client device 10 maintains the standby state without performing other processes until the end of execution is notified from the service providing program. In any case, the client device 10 displays “in execution” in the status field of the record in the list 41 d of the operation screen 41. FIG. 18 is a diagram illustrating an example of the operation screen 41 when “execution” is indicated in the status field of one record in the list 41d.

  In the next step S393, the client device 10 stands by until the scheduled end time of the processing target record elapses (S393; NO). Then, when the scheduled end time has elapsed (S393; YES), the client device 10 advances the process to step S394.

  In step S394, the client apparatus 10 determines whether or not the service providing apparatus 20 has successfully executed the service. If the service providing apparatus 20 determines that the execution of the service has not ended normally (S394; NO), the client apparatus 10 advances the process to step S395.

  In step S395, the client apparatus 10 performs service execution on the service providing apparatus 20 that has a copy of the management tables 21 to 23 stored in the storage apparatus by the service providing apparatus 20 that is requesting execution of the service. Event information including that the abnormal termination has occurred in the middle service providing apparatus 20 and that each of the management tables 21 to 23 related to the abnormal termination should be updated is notified. After the notification, the client device 10 displays “abnormal end” in the status field of the record in the list 41d of the operation screen 41. FIG. 19 is a diagram showing an example of the operation screen 41 when “abnormal end” is shown in the status field of one record in the list 41d. After performing such display switching, the client device 10 ends the execution of the fourth processing loop L4 for this processing target record.

  When the second processing loop L2 is executed for all the records listed in the list 41d of the operation screen 41, the client apparatus 10 returns the process to step S310.

  On the other hand, when the service providing apparatus 20 determines that the execution of the service has ended normally during execution of the fourth processing loop L4 (S394; YES), the client apparatus 10 exits from the fourth processing loop L4 and performs step S312. Proceed to the process.

  In step S312, the client apparatus 10 displays “normal end” in the status field of the record in the list 41d of the operation screen 41. FIG. 20 is a diagram illustrating an example of the operation screen 41 when “normal end” is indicated in the status field of one record in the list 41d. After performing such display switching, the client device 10 returns the process to step S310.

  On the other hand, when the client device 10 determines in step S311 that the clicked button is not the execution button 41f (S311; NO), the process proceeds to step S313.

  In step S313, the client device 10 determines whether the clicked button is the search button 41e. When the client device 10 determines that the clicked button is the search button 41e (S313; YES), the client apparatus 10 returns the process to step S304, and determines that the clicked button is not the search button 41e (S313; NO), it is determined that the cancel button 41g has been clicked, and the client process is terminated.

  Since the processing as described above is executed, the grid computing system according to the present embodiment has the following operations and effects.

  In the service search device 30, the service providing device 20 and the service provided by the service providing device 20 are recorded in the static information management table 31 in a state of being associated with each other. The record in the static information management table 31 is static information that is constant in time regardless of the operating status of the service providing apparatus 20. Therefore, a plurality of service search devices 30 can be prepared for the grid computing system of the present embodiment. By preparing a plurality of service search devices 30 in this way, even if any service search device 30 goes down, the other search devices continue to operate. You can always get search results from. However, in any service search device 30, the content of the static information management table 31 does not change with time, so that the search result acquired from any service search device 30 always has the same content. . Therefore, the service search device 30 can always provide normal processing to the client device 10.

  In addition, dynamic information indicating the operating status of the service providing apparatus 20 is recorded in several service providing apparatuses 20 different from the service providing apparatus 20 and the service providing apparatus 20, and the dynamic information of the service providing apparatus 20 is further recorded. When a change occurs in the information, the dynamic information recorded in all of the other service providing devices 20 is updated with the changed dynamic information (S104 to S107, S109 to S112, S204 to S204). S206, S212 to S214, S223, S226 to S228). For this reason, even if the client device 10 cannot directly acquire the dynamic information of the service providing device 20 that provides the target service from the service providing device 20, the dynamic information having the same content as the dynamic information is It can be acquired from another service providing apparatus 20. Therefore, the client device 10 can always and accurately determine whether or not to request the service providing device 20 that can provide the target service to provide the service.

  When the user of the grid computing system wants to enjoy any service that can be provided by the system, the user starts the client program 11 by operating the input device of his / her client device 10. Then, an operation screen 41 as shown in FIG. 15 is displayed on the display device of the client device 10 (S301). The user inputs the name of the desired service in the text box 41a of the operation screen 41, clicks either the speed priority radio button 41b or the quality priority radio button 41c, and clicks the search button 41e. (S302, S303; YES). Then, in the list 41d of the operation screen 41 displayed on the display device of the client device 10, as shown in FIG. 16, the server name of the service providing device 20 that can provide the service specified by the user. Are listed in the order of speed priority or quality priority selected by the user (S304 to S309, L1, S361 to S363, L2, S371 to S373, L3, S381 to S383). When the user clicks the execution button 41f, the service providing apparatus 20 listed in the list 41d is requested to provide the service specified by the user (L4, S391). . Therefore, when the user wants to enjoy any service that can be provided by this system, the user only needs to determine the service name and the priority order of the search results, and the optimum service for providing the desired service. The providing apparatus 20 can be requested to provide a service.

(Appendix 1)
A grid computing system in which a client device receives a service from the server device by requesting the server device to provide the service,
Each server device stores dynamic information indicating its own operating status and dynamic information indicating the operating status of at least one other server device, and when its own dynamic information changes In addition, it updates its own dynamic information recorded in another server device, and provides its own dynamic information to the client device when the client device requests its own dynamic information. When the dynamic information of the other server device is requested from the client device, the dynamic information of the other server device is provided to the client device,
Each of the one or more search devices connected to the client includes server identification information for identifying each server device, service identification information for identifying a service that the server device can provide, and operation of the server device. Static information that associates server identification information with other server devices that store the target information, and when any service identification information is received from any client device, the service identification information Server identification information corresponding to the
When the client device acquires the server identification information of the server device that can provide the target service, the client device determines whether to request the server device to provide the service from the server device of the server identification information. The dynamic information is acquired, and when the dynamic information cannot be obtained from the server device, the dynamic information is acquired from another server device that stores the dynamic information of the server device. Grid computing system.

(Appendix 2)
When requested to provide a service from a client device of the grid computing system, the server device provides a service to the client device,
Storing dynamic information indicating its own operating status and dynamic information indicating the operating status of at least one other server device;
When a change occurs in its own dynamic information, it updates its own dynamic information recorded in other server devices,
When dynamic information is requested from the client device, the client device provides its own dynamic information,
A server device characterized in that when the client device requests dynamic information of another server device, the server device provides the client device with dynamic information of another server device.

(Appendix 3)
A search device connected to a client device that enjoys a service from each server device in a grid computing system,
Storing static information associating server identification information for identifying each server device with service identification information for identifying a service that the server device can provide;
A search device characterized in that, when any service identification information is received from any client device, server identification information corresponding to the service identification information is provided to the client device.

(Appendix 4)
A client device for receiving a service from a server device of a grid computing system,
Static information that associates server identification information for identifying each server device, service identification information for identifying services that can be provided by the server device, and server identification information of other server devices that store dynamic information of the server device. Server identification information corresponding to any service identification information is obtained from the search device storing the target information;
In order to determine whether or not to request the server apparatus of the acquired server identification information to provide a service, the dynamic information is acquired from the server apparatus of the server identification information, and the dynamic information is received from the server apparatus. If not obtained, the client apparatus obtains the dynamic information from another server apparatus that stores the dynamic information of the server apparatus.

(Appendix 5)
An information providing program for adding an information providing function to a computer that provides a service to a client device when requested to provide the service from a client device of the grid computing system,
The computer,
Storage means for storing in the storage device dynamic information indicating its own operating status and dynamic information indicating the operating status of any of the server devices of the grid computing system;
Updating means for updating own dynamic information recorded in another server device when a change occurs in the own dynamic information; and
When the receiving device receives information requesting the dynamic information of another server device from the client device, the client device functions as a communication unit that transmits the dynamic information of the other server device via the transmitting device. An information providing program characterized by that.

(Appendix 6)
An information providing program for adding an information providing function to a computer connected to a client device that receives a service from each server device in a grid computing system,
The computer,
Static information that associates server identification information for identifying each server device, service identification information for identifying services that can be provided by the server device, and server identification information of other server devices that store dynamic information of the server device. Storage means for storing information in the storage device, and
Receiving means for receiving any service identification information in the receiving device from any one of the client devices; and
An information providing program that causes server identification information corresponding to service identification information received by the receiving unit to be read from the storage device and to function as a transmitting unit that transmits to the client device in a transmitting device.

Schematic diagram of a grid computing system according to an embodiment of the present invention Explanatory drawing which shows the table group and program group which are installed in the memory | storage device of a service provision apparatus. The figure which shows an example of the data structure of a queue management table The figure which shows an example of the data structure of an operation history management table The figure which shows an example of the data structure of a schedule management table The figure which shows an example of the data structure of an operation condition management table The figure which shows an example of the data structure of a static information management table The figure which shows an example of the data structure of a holding relationship management table Flow chart showing the contents of the queue execution process Flow chart showing the contents of event reception processing Flow chart showing the contents of event reception processing Flow chart showing the contents of client processing Flow chart showing the contents of client processing Flow chart showing the contents of client processing The figure which shows an example of the operation screen The figure which shows an example of the operation screen The figure which shows an example of the operation screen The figure which shows an example of the operation screen The figure which shows an example of the operation screen The figure which shows an example of the operation screen

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Client apparatus 11 Client program 20 Service provision apparatus 21 Queue management table 22 Operation history management table 23 Schedule management table 24 Operation status management table 25 Queue execution program 26 Event reception program Sa to Se Service provision program 30 Service search apparatus 31 Static information Management table 32 Holding relationship management table 33 Service search program 41 Operation screen 41a Text box 41b Radio button 41c Radio button 41d List table 41e Search button 41f Execution button 41g Cancel button N Network

Claims (2)

A grid computing system in which a client device receives a service from a server device by requesting the server device to provide the service,
Each pre Kisa over server apparatus, the dynamic information indicating its own operation status, and dynamic information indicating the operating status of at least one other server unit stores, is a change in the dynamic information of the self When this occurs, the self-dynamic information recorded in the other server device is updated, and when the client device requests its own dynamic information, its own dynamic information is sent to the client device. Providing information, and when the dynamic information of another server device is requested from the client device, providing the dynamic information of the other server device to the client device;
Dynamic information of a plurality of retrieval devices connected to the client, both the server identification information for identifying the server device and the service identification information for the server device to identify the services that can be provided a server device Is stored for each of the server devices , and when any service identification information is received from any client device, Providing server identification information corresponding to the service identification information to the client device;
When the client device acquires the server identification information of the server device that can provide the target service, the client device determines whether to request the server device to provide the service from the server device of the server identification information. The dynamic information is acquired, and if the dynamic information cannot be obtained from the server device, the dynamic information is acquired from another server device that stores the dynamic information of the server device. Grid computing system. The grid computing system according to claim 1, wherein the dynamic information is information indicating whether the server device is operating or stopped.

Images