JP7081313B2 - Relay server - Google Patents

Description

The present invention relates to a relay server.

In the application system 1, the server may be stopped due to maintenance, malfunction, etc., and the server side identifies the client that accessed at the time of this stop, and responds to the client that the access could not be responded to. There is a need. In the technique disclosed in Patent Document 1, the time when communication fails is saved as a time stamp on the client side, and the time stamp is sent to the server in the next communication. The server side keeps the stop period, and if the time stamp received from the client side indicates the time within this stop period, the client that sent the time stamp is accessed by the client when the server is stopped. Specify as.

Patent No. 5981683

The present invention provides a technique for recording an access from an application while the server is stopped in a system including a client device running an application that requests processing from the server, regardless of the function of the application. The purpose is to do.

The relay server according to claim 1 includes a first receiving unit that receives a request from a client device, a monitoring unit that monitors whether a specific server device is operating or stopped, and the first receiving unit that requests the request. When the server device is operating in the case of receiving the request, the transfer unit that transfers the request to the server device and the server device are stopped when the first receiving unit receives the request. When, it has a writing unit that writes the date and time when the request was made to the database.
The relay server according to claim 2 is the relay server according to claim 1, and the writing unit writes to the database the time zone in which the server device was stopped by using the monitoring result in the monitoring unit.
The relay server according to claim 3 is the relay server according to claim 1 or 2, wherein the request includes identification information of the client device or a user of the client device, and the writing unit includes the identification information together with the request. To the database.
The relay server according to claim 4 is a client device or a user of the client device whose database records that the request was transmitted when the server device was stopped in the relay server according to claim 3. On the other hand, it has a granting unit that grants benefits.
The relay server according to claim 5 is the relay server according to claim 4, and the granting unit gives the privilege by weighting according to the attribute of the request recorded in the database.
The relay server according to claim 6 is the relay server according to any one of claims 3 to 5, wherein the database includes an application program and a function of retransmitting a request in the application program. It is recorded in the database that the request contains the identification information of the application program, and the writing unit has a function of retransmitting the request by the application program that transmitted the request when the receiving unit receives the request. If so, the date and time of the request is not written to the database even if the server device is stopped.
The relay server according to claim 7 has a second receiving unit that receives a notification that the server device has changed from a stopped state to an operating state in the relay server according to any one of claims 1 to 6.
The relay server according to claim 8 has a changing unit for changing the frequency of monitoring whether the server device is operating or stopped in the relay server according to any one of claims 1 to 7.
The relay server according to claim 9 is the relay server according to claim 8, and the change unit is monitored when the number or frequency of the requests received when the server device is stopped is larger than the standard. Increase the frequency.
The relay server according to claim 10 has an acquisition unit for acquiring information indicating a time zone in which the server device is scheduled to stop in the relay server according to claim 8, and the change unit is indicated by the information. If the time to the recovery time falls below the threshold, the frequency of the monitoring is increased.
The relay server according to claim 11 is the relay server according to any one of claims 8 to 11, and the monitoring of the server device performed by the monitoring unit includes monitoring by the first method, which is light in processing, and the first method. Monitoring by the second method, which is heavier than the first method, is included, and the changing unit changes the method of monitoring whether the server device is operating or stopped.
The relay server according to claim 12 is the relay server according to claim 11, and the changing unit uses the first method as a monitoring method when increasing the frequency of monitoring.

According to the relay server according to claim 1, when the server device is operating when the request from the client device is received, the request is transferred to the server device, and when the request is received, the server device transfers the request. When the server device is stopped, the date and time when the request is made is written in the database, so that the client device that accessed when the server device is stopped can be specified regardless of the function of the client device.
According to the second aspect of the present invention, since the time zone in which the server device was stopped is written in the database, the client device that has accessed when the server device is stopped can be easily specified.
According to the relay server according to claim 3, the request includes the identification information of the client device or the user of the client device, and the writing unit writes the identification information to the database together with the request, so that when the server device is stopped. It is possible to accurately identify the client device that has accessed.
According to the relay server according to claim 4, since the privilege is given to the client device or the user of the client device that has transmitted the request when the server device is stopped, the trust from the user of the client device is gained. Can be enhanced.
According to the relay server according to claim 5, since the privilege is given by weighting according to the attribute of the request recorded in the database, it is possible to give an appropriate privilege according to the attribute of the request.
According to the relay server according to claim 6, when the request from the application program that retransmits the request when the request is not received is received, the request is made even if the server device is stopped. Do not write the date and time to the database. Therefore, the request date and time can be written to the database by limiting the range to only the client device that has lost the opportunity of the request due to the stop of the server device.
According to the relay server according to claim 7, since the notification that the server device has changed from the stopped state to the operating state is received, it is possible to quickly respond to the recovery of the server device.
According to the eighth aspect of the present invention, since it has a changing unit for changing the frequency of monitoring whether the server device is operating or stopped, it is possible to appropriately control the monitoring load related to the server device.
According to the relay server according to claim 9, when the number or frequency of requests made when the server device is stopped is higher than the standard, the change unit increases the frequency of monitoring and the stop period of the server device. In order to improve the measurement accuracy, the request is sent during the down period of the server device, but the request is not specified during the down period of the client device, or the request is sent during the operation period of the server device. It is possible to reduce the probability that a client device that is specified to have transmitted the message will occur.
According to the relay server according to claim 10, when the time until the recovery time of the server device falls below the threshold value, the frequency of the monitoring is increased, so that the request is transmitted during the stop period of the server device as described above. Probability of occurrence of a client device that is not specified to that effect, or a client device that is specified to have sent a request during the outage period even though the request was sent during the operating period of the server device. Can be lowered.
According to claim 11, the monitoring of the server device is switched between monitoring by the first method, which is lighter in processing, and monitoring by the second method, which is heavier than the first method. , The monitoring load of the server device can be controlled appropriately.
According to the relay server according to claim 12, when the frequency of monitoring is increased, the first method is used as the monitoring method, so that the monitoring load of the server device can be appropriately controlled.

A block diagram illustrating the configuration of an application system according to an embodiment. A block diagram illustrating the configuration of a relay server. A flowchart illustrating the request reception process executed by the relay server. The figure which illustrates the serial number-user ID correspondence table. The figure which illustrates the access date and time record table. A flowchart illustrating the monitoring process executed by the relay server. The figure which illustrates the stop period recording table. The sequence diagram which illustrates the 1st operation example. The sequence diagram which illustrates the 2nd operation example. The sequence diagram which illustrates the 3rd operation example. The figure which exemplifies the stop period list. The figure which exemplifies the access failure request list. The figure which exemplifies the list of the access times during stop. The figure which exemplifies the stop encounter time list.

1. 1. Configuration Figure 1 is a block diagram illustrating the configuration of the application system 1 according to the embodiment of the present invention. As shown in FIG. 1, the application system 1 includes a relay server 100, an application server 200, a DB (database) 300, and a client device 400.

The DB 300 stores identification information of various application programs executed by the application server 200 and various data for managing and controlling the application system 1. The application server 200 executes the application program in the DB 300 according to the request from the client device 400, and provides the service to the client device 400. The application server 200 is an example of a server device for monitoring in the present embodiment. The relay server 100 is a server that relays between the client device 400 and the application server 200, and also responds to the stoppage of the application server 200. More specifically, the relay server 100 monitors whether the application server 200 is operating or stopped, and if the request from the client device 400 to the application server 200 is received within the operating period of the application server 200, the relay server 100 monitors. When the request is transferred to the application server 200 and the request from the client device 400 to the application server 200 is received within the stop period of the application server 200, the date and time (time stamp) of the request is written in the DB 300.

FIG. 2 is a block diagram showing a configuration example of the relay server 100. In this example, the relay server 100 includes a processor 101, a storage unit 102 including a volatile storage unit and a non-volatile storage unit, a communication unit 103 having a function of communicating via a network, a liquid crystal display, and the like. It is a computer device having a display unit 104 and an operation unit 105 including an operation unit such as a keyboard and a mouse. Various programs executed by the processor 101 are stored in the non-volatile storage unit of the storage unit 102. The application server 200 is also a computer device having the same configuration as the relay server 100. The client device 400 is, for example, a general-purpose computer device, specifically, a personal computer, a tablet terminal, or a smartphone.

In FIG. 1, in the block showing the relay server 100, a communication unit 110 including a first receiving unit 111 and a second receiving unit 112, a monitoring unit 120, a transfer unit 130, a writing unit 140, and an imparting unit 150 are included. , The change unit 160 and the acquisition unit 170 are shown. These are the functions realized by the processor 101 of FIG. 2 executing the program in the non-volatile storage unit of the storage unit 102.

The first receiving unit 111 is a means for receiving a request from the client device 400 to the application server 200. This request includes identification information of the client device 400 or the user of the client device 400. The second receiving unit 112 is a means for receiving various information other than the request from the client device 400.

The monitoring unit 120 is a means for monitoring whether the application server 200 is operating or stopped. The transfer unit 130 is a means for transferring the request to the application server 200 when the application server 200 is operating when the first receiving unit 111 receives the request.

When the application server 200 is stopped when the first receiving unit 111 receives the request, the writing unit 140 writes the date and time when the request was made and the identification information specifying the source of the request to the DB 300. Is. Further, the writing unit 140 writes the time zone in which the application server 200 has been stopped to the DB 300 by using the monitoring result of the monitoring unit 120.

The granting unit 150 is a means for granting a privilege to the client device 400 or the user of the client device 400 in which it is recorded in the DB 300 that the request is transmitted when the application server 200 is stopped. Here, the granting unit 150 assigns a weight according to the attribute of the request recorded in the DB 300 and grants the privilege.

The change unit 160 is a means for controlling the monitoring process by the monitoring unit 120. The acquisition unit 170 is a means for acquiring control information used for control performed by the change unit 160.

2. 2. Operation FIG. 3 is a flowchart showing a request reception process executed by the relay server 100 in the present embodiment. This request reception process is executed by the first receiving unit 111 receiving a request from the client device 400.

Upon receiving the request from the client device 400, the first receiving unit 111 of the relay server 100 determines whether or not the server stop flag is ON (step S101). This server stop flag is a flag that is switched by the monitoring unit 120, and is turned ON when the application server 200 is stopped and turned OFF when the application server 200 is running.

When the determination result in step S101 is "YES", that is, when the application server 200 is stopped, in the relay server 100, the writing unit 140 generates a request on the date and time when the request received by the first receiving unit 111 was made. Write to the DB 300 together with the identification information that identifies the source (step S122). Then, the communication unit 110 of the relay server 100 returns the result to the client device 400, which is the source of the request, that is, transmits information that the request has not been accepted (step S131). This ends the request reception process.

On the other hand, when the determination result in step S101 is "NO", that is, when the application server 200 is operating, the transfer unit 130 transfers the request received by the first reception unit 111 to the application server 200 in the relay server 100. (Step S102). Then, in the relay server 100, the second receiving unit 112 receives the result for the request from the application server 200 (step S103), and determines whether or not the result has been successfully received (step S111).

When the determination result in step S111 is "YES", in the relay server 100, the communication unit 110 transmits the result returned from the application server 200 to the client device 400 which is the transmission source of the request (step S131). This ends the request reception process.

If the result is not normally returned from the application server 200 in response to the request transfer, or if the result is not returned and the timeout occurs even after a predetermined time has elapsed from the transmission of the request, the determination result in step S111 is The result is "NO", and in the relay server 100, the monitoring unit 120 turns on the server stop flag (step S121).

Then, in the relay server 100, the writing unit 140 writes the date and time of the request to the DB 300 together with the identification information that identifies the source of the request received by the first receiving unit 111 (step S122). Then, the communication unit 110 of the relay server 100 transmits information to the effect that the request has not been accepted to the client device 400, which is the transmission source of the request (step S131). This ends the request reception process.

In the process of step S122, the writing unit 140 refers to the serial number-user ID correspondence table in the DB 300 and writes to the access date / time recording table in the DB 300.

FIG. 4 is a diagram showing a serial number-user ID correspondence table in the DB 300. Further, FIG. 5 is a diagram showing an access date / time recording table in the DB 300.

In the present embodiment, a serial number is assigned to all users who receive the service of the application server 200, and a serial number-user ID correspondence table for associating the serial number of each user with the user ID is stored in the DB 300. In the process of step S122, the writing unit 140 obtains a serial number from the user ID of the user who is the sender of the request by referring to the serial number-user ID correspondence table, and the request is made using this serial number as identification information. It is written in the access date / time recording table together with the date / time (access date / time in FIG. 5).

FIG. 6 is a flowchart showing a monitoring process executed by the monitoring unit 120 of the relay server 100 in the present embodiment. First, the monitoring unit 120 transmits to the application server 200 a life-and-death confirmation request for confirming whether the application server 200 is stopped or operating (step S201). Then, the result of the life-and-death confirmation request is received from the application server 200 (step S211), and it is determined whether or not the application server 200 is operating (step S212).

When the information indicating that the application server 200 is operating is received, the determination result in step S212 is "YES", and the monitoring unit 120 turns off the server stop flag (step S221).

On the other hand, when the information indicating that the application server 200 is stopped is received, or when the information indicating that the application server 200 is operating is not received and the predetermined time elapses and the timeout occurs. , The determination result in step S212 is "NO", and the monitoring unit 120 turns on the server stop flag (step S222).

When the step S221 or S222 is completed, the monitoring unit 120 waits for an arbitrary time (step S331). Then, the process returns to step S201 and the process is repeated.

The monitoring unit 120 obtains a stop start date and time when the server stop flag changes from OFF to ON and a stop end date and time when the server stop flag changes from ON to OFF by repeating the above monitoring process, and stops from the stop start date and time. Information indicating the suspension period until the date and time is written in the suspension period table in the DB 300.

FIG. 7 is a diagram showing a stop period table in the present embodiment. As shown in FIG. 7, the stop period table shows information on the stop start date and time and the stop end date and time for each of the stop periods of the application server 200.

FIG. 8 is a sequence diagram showing a first operation example of the present embodiment. In this operation example, when the request from the client device 400 is received by the relay server 100 (step S301), the server stop flag is OFF, so the request is transferred from the relay server 100 to the application server 200 (step S302). ). Then, the application server 200 executes the processing according to the request, and the result is returned to the relay server 100 (step S303). Then, the result of this processing is transferred to the client device 400 by the relay server 100 (step S304).

FIG. 9 is a sequence diagram showing a second operation example of the present embodiment. In this operation example, when the request from the client device 400 is received by the relay server 100 (step S311), the server stop flag is ON. Therefore, the relay server 100 writes the date and time when the request was made and the identification information of the source of the request to the DB 300 (step S312). Then, the relay server 100 returns to the client device 400, which is the source of the request, the result that the request was not accepted because the application server 200 is stopped (step S313).

FIG. 10 is a sequence diagram showing a third operation example of the present embodiment. In this operation example, when the request from the client device 400 is received by the relay server 100 (step S321), the server stop flag is OFF, so the request is transferred from the relay server 100 to the application server 200 (step S322). ). However, the result is not returned from the application server 200 to the relay server 100 because the application server 200 has stopped or some trouble has occurred. Therefore, in the relay server 100, the server stop flag is turned ON (step S323), and the date and time when the request was made and the identification information of the source of the request are written in the DB 300 (step S324). Then, the relay server 100 returns to the client device 400, which is the source of the request, the result that the request was not accepted because the application server 200 is stopped (step S325).

Next, various processes executed by the operation of the operation unit 105 of the relay server 100 will be described.

FIG. 11 is a diagram showing a list of stop periods of the application server 200 displayed on the display unit 104 of the relay server 100. In the relay server 100, when the operation unit 105 instructing the display of the stop period list is performed, the grant unit 150 refers to the stop period recording table (see FIG. 7) in the DB 300 and displays the list of the stop periods. It is displayed in the unit 104. As shown in FIG. 11, on the display unit 104, the start date and time and the end date and time of the stop period are displayed, and a soft button including the character string "See details" in association with the stop period, "Delete". A soft button containing the string of is displayed.

Here, when an operation for instructing a soft button including the character string "delete" is performed, the granting unit 150 deletes the information regarding the stop period corresponding to the soft button from the stop period recording table. On the other hand, when the operation of instructing the soft button including the character string "see details" is performed, the granting unit 150 gives detailed information about the stop period corresponding to the soft button, specifically, within the stop period. Information indicating the occurrence status of the request to the application server 200 is displayed on the display unit 104.

FIG. 12 is a diagram showing a list of access failure requests displayed on the display unit 104 in the present embodiment. This is the first example of the information indicating the occurrence status of the request to the application server 200 during the outage period. This access failure request list includes the date and time when the request occurred within the stop period specified by the "View Details" soft button, and the serial number and user ID that specify the source of the request. This information is associated with the access date / time and serial number recorded in the access date / time recording table (see FIG. 5) during the suspension period and the serial number in the serial number-user ID correspondence table (see FIG. 4). It is generated based on the user ID.

In the access failure request list, a check box is provided on the left side of the access date and time. In addition, at the bottom of the access failure request list, a soft button containing the character string of "grant privilege" and a soft button containing the character string of "send apology contact email" are displayed. When the check box on the left side of a certain access date and time is checked and a soft button containing the character string of "privilege grant" is instructed, the granting unit 150 gives the user who accessed the access date and time when the check box is checked. , For example, granting a privilege such as granting one license. In addition, when the check box on the left side of a certain access date and time is checked and a soft button containing the character string "Apology contact mail is sent" is instructed, the granting unit 150 accesses the access at the checked access date and time of the check box. We will send an apology contact email to the user who performed the above.

FIG. 13 is a diagram showing a list of stopped access times displayed on the display unit 104 in the present embodiment. This is the second example of the information indicating the occurrence status of the request to the application server 200 during the outage period. This list of stopped access times summarizes the requests generated within the stopped period specified by the "View details" soft button (see FIG. 11) for each user who is the source of the request, and requests for each user. It is a count of the number of occurrences. Further, in the example shown in FIG. 13, the number of requests generated during the stop period for each user is sorted in descending order of the number of requests. The information referred to in generating this stopped access count list is the same as in the case of the above-mentioned access failure request list.

At the bottom of the access failure request list, a soft button including the character string "weighted privilege grant" and the character string "top 33%, middle 33%, bottom 34%" are displayed. In the present embodiment, when the soft button of "weighted privilege grant" is instructed, the granting unit 150 sets the user who sent the request within the corresponding suspension period as a group whose access count is within the top 33%. , The group corresponding to the middle 33% or less and the group corresponding to the lower 34% or less are divided, and the privilege with different weighting is given to each group. In this way, the granting unit 150 gives a privilege by weighting according to the attribute of the user stored in the DB 300, specifically, the number of requests generated within the suspension period. In this case, the benefits may be an increase in the number of licenses, an extension of the license period, an increase in the capacity available for the service, a cost discount, coupon distribution, and the like. The reason why the privilege is weighted according to the attribute of the user is to give the user a privilege according to the disadvantage suffered.

FIG. 14 is a diagram showing a list of stop encounter times displayed on the display unit 104 in the present embodiment. This is the third example of the information indicating the occurrence status of the request to the application server 200 during the outage period. This stop encounter time list summarizes the requests generated within the stop period specified by the "View details" soft button (see FIG. 11) for each user who is the source of the request, and is accessed first by the user. The elapsed time from the first access date and time during the stoppage to the last access date and time during the stoppage that was last accessed is measured as the stop encounter time. Further, in the example shown in FIG. 14, the stop encounter time within the stop period for each user is sorted in descending order of time. The information referred to in generating this stop encounter time list is the same as in the case of the access failure request list described above.

At the bottom of the stop encounter time list, there is a soft button containing the character string "weighted privilege grant" and "top 33% middle 33%" as in the above access failure request list (see Fig. 13).
The character string "Lower 34%" is displayed. The meaning of these displays is the same as the above-mentioned access failure request list. In this way, the granting unit 150 gives a privilege by weighting according to the attribute of the user stored in the DB 300, specifically, the stop encounter time within the stop period.

As described above, according to the present embodiment, when the application server 200 is operating when the request from the client device 400 is received, the relay server 100 transfers the request to the application server 200. When the application server 200 is stopped when the request is received, the date and time when the request was made is written in the DB 300. Therefore, the client device 400 that accessed when the application server 200 was stopped is not limited to the function of the client device 400. Can be identified. Further, according to the present embodiment, since the time zone in which the relay server 100 and the application server 200 are stopped is written in the DB 300, the client device 400 that has accessed when the application server 200 is stopped can be easily specified. Further, according to the present embodiment, the request from the client device 400 includes the user's identification information, and the writing unit 140 writes the identification information to the database together with the request, so that the application server 200 is accessed. The client device 400 can be accurately identified. Further, according to the present embodiment, the relay server 100 grants a privilege to the client device 400 or the user of the client device that has transmitted the request when the application server 200 is stopped. It is possible to increase the trust of users. Further, according to the present embodiment, the relay server 100 gives a privilege by weighting according to the attribute of the request recorded in the DB 300, and therefore, grants an appropriate privilege according to the attribute of the request. Can be done.

3. 3. Modifications The present invention is not limited to the above-described embodiment, and various modifications can be carried out. Hereinafter, a modified example will be described. Two or more of the following modifications may be used in combination.

(1) The relay server 100 may change its correspondence depending on the version of the application program executed by the client device 400 to send a request to the application server 200. In this example, the DB 300 stores information indicating whether or not the application program that sends the request to the application server 200 has a function of retransmitting the request in association with the identification information of the application program. This information is provided in advance by, for example, the provider of the application program. Further, the client device 400 transmits a request including the identification information of the application program as the above-mentioned request. When it is recorded in the DB 300 that the writing unit 140 of the relay server 100 has a function of retransmitting the request when the first receiving unit 111 receives the request, the application server Even if 200 is stopped, the date and time when the request was made is not written to the DB 300. According to this aspect, the request date and time is written in the DB 300 by narrowing down the range to only the client device 400 that does not have the request retransmission function and has lost the opportunity of the request due to the stop of the application server 200. Therefore, the DB 300 can be made smaller.

(2) The method by which the relay server 100 confirms whether the application server 200 is in the stopped state or the operating state is not limited to the method exemplified in the embodiment. For example, instead of or in addition to sending an inquiry from the relay server 100 to the application server 200, when the application server 200 changes from the stopped state to the operating state, a notification to that effect is sent to the relay server 100. You may. The second receiving unit 112 of the relay server 100 receives this notification and hands it over to the monitoring unit 120, and the monitoring unit 120 turns off the server stop flag. According to this aspect, it is possible to quickly respond to the recovery of the application server 200.

(3) The change unit 160 may change the frequency of monitoring whether the application server 200 is running or stopped. Specifically, the change unit 160 refers to the access date / time recording table (see FIG. 5) and the stop period recording table (see FIG. 7) in the DB 300, so that the request that was within the stop period of the application server 200 can be requested. Determine if the number or frequency is higher than the standard and increase the frequency of monitoring if it is higher than the standard. According to this aspect, the monitoring load related to the application server 200 can be appropriately controlled. Further, when the number or frequency of requests during the stop period of the application server 200 is higher than the standard, the change unit 160 increases the frequency of monitoring and improves the measurement accuracy of the stop period. Therefore, the change unit 160 makes a request during the stop period of the application server 200. The client device 400 is not specified to that effect even though The probability that 400 will occur can be reduced.

(4) The monitoring unit 120 may be capable of executing a plurality of monitoring methods including monitoring by the first method, which is lighter in processing, and monitoring by the second method, which is heavier than the first method. In this case, the changing unit 160 may change the monitoring method in the monitoring unit 120. Specifically, the change unit 160 uses the first method as the monitoring method when increasing the frequency of monitoring. As a first method with light processing, for example, a method of confirming whether or not the connection with the application server 200 is successfully established can be considered. The time required for this process is, for example, about 0.1 second. As a second method, which is heavier than the first method, a method of transmitting dummy processing data from the relay server 100 to the application server 200 and confirming whether or not a correct result is returned can be considered. The time required for this process is, for example, about 10 seconds. According to this aspect, the monitoring load on the application server 200 can be appropriately controlled.

(5) When the time zone in which the application server 200 is scheduled to be stopped is known in advance, the change unit 160 may increase the frequency of monitoring the application server 200 when the scheduled recovery time is approaching. In this case, the acquisition unit 170 acquires information indicating a time zone in which the application server 200 is scheduled to stop. The change unit 160 increases the frequency of monitoring of the application server 200 when the time to the recovery time indicated by this information falls below the threshold value. According to this aspect, when the time until the recovery time of the application server 200 falls below the threshold value, the frequency of monitoring the application server 200 is increased, so that the request is transmitted during the stop period of the application server 200 as described above. However, the client device 400 that is not specified to that effect, or the client device 400 that is specified to have sent the request during the stop period even though the request was sent during the operating period of the application server 200. The probability of occurrence can be reduced.

(6) The correspondence between the functional element and the hardware element in the application system 1 is not limited to that exemplified in the embodiment. For example, a group of devices including a plurality of computer devices may have a function as a relay server 100 as a whole.

(7) The UI screen and various information shown in the embodiment are merely examples. For example, some UI elements may be omitted from the screens shown in the embodiments. Further, the program executed by the processor 101 or the like may be recorded and provided on a recording medium such as a CD-ROM, or may be provided in a state of being stored in a server device on the network.

1 ... Application system, 100 ... Relay server, 200 ... Application server, 300 ... DB, 400 ... Client device, 110 ... Communication unit, 111 ... First receiving unit, 112 ... Second receiving unit, 120 ... Monitoring unit, 130 ... Transfer unit, 140 ... Writing unit, 150 ... Adding unit, 160 ... Changing unit, 170 ... Acquisition unit, 101 ... Processor, 102 ... Storage unit, 103 ... Communication unit, 104 ... Display unit, 105 ... Operation unit.

Claims (12)

The first receiver that receives the request from the client device,
A monitoring unit that monitors whether a specific server device is running or stopped,
When the server device is operating when the first receiving unit receives the request, a transfer unit that transfers the request to the server device and a transfer unit.
A relay server having a writing unit that writes the date and time when the request was made to the database when the server device is stopped when the first receiving unit receives the request. The relay server according to claim 1, wherein the writing unit writes the time zone in which the server device was stopped to the database by using the monitoring result of the monitoring unit. The request includes identification information of the client device or a user of the client device.
The relay server according to claim 1 or 2, wherein the writing unit writes the identification information to the database together with the request. The relay according to claim 3, further comprising a granting unit that grants a privilege to the client device or the user of the client device whose transmission of the request is recorded in the database when the server device is stopped. server. The relay server according to claim 4, wherein the granting unit is weighted according to the attribute of the request recorded in the database and grants the privilege. The database includes the identification information of the application program and the presence or absence of the ability to retransmit the request in the application program.
The request contains the identification information of the application program.
When it is recorded in the database that the writing unit has a function of retransmitting the request when the receiving unit receives the request, the server device is stopped. The relay server according to any one of claims 3 to 5, which does not write the date and time when the request is made to the database. The relay server according to any one of claims 1 to 6, further comprising a second receiving unit for receiving a notification that the server device has changed from a stopped state to an operating state. The relay server according to any one of claims 1 to 7, which has a changing unit for changing the frequency of monitoring whether the server device is operating or stopped. The relay server according to claim 8, wherein the change unit increases the frequency of the monitoring when the number or frequency of the requests made when the server device is stopped is higher than the standard. It has an acquisition unit that acquires information indicating a time zone in which the server device is scheduled to stop.
The relay server according to claim 8, wherein the change unit increases the frequency of the monitoring when the time until the recovery time indicated by the information falls below the threshold value. The monitoring of the server device performed by the monitoring unit includes monitoring by the first method, which is lighter in processing, and monitoring by the second method, which is heavier than the first method.
The relay server according to any one of claims 8 to 10, wherein the changing unit changes a method of monitoring whether the server device is operating or stopped. The relay server according to claim 11, wherein the changing unit uses the first method as a monitoring method when increasing the frequency of monitoring.

Images