Service provision system and service provision program

Abstract

To provide a service provision system and a service provision program capable of executing a migration requiring a change in interpretation of data.SOLUTION: The service provision system is provided with a connection control unit which, when a connection request is input, transfers the connection request to an application execution system which executes an application used by a user, and the connection control unit specifies an application execution system to which the connection request is transferred according to a transfer table and a tenant ID included in the connection request (S121 to S123).SELECTED DRAWING: Figure 10

Description

[Technical Field]

[0001] The present invention relates to a service providing system and a service providing program for providing a service to a user. [Background technology]

[0002] Conventionally, a method for migrating data has been known (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] International Publication No. 2019 / 005753 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the conventional method has a problem in that it is not possible to perform migration that requires a change in the interpretation of data.

[0005] Therefore, an object of the present invention is to provide a service providing system and a service providing program that can execute migration that requires a change in the interpretation of data. [Means for solving the problem]

[0006] The service providing system of the present invention includes a connection control unit that, when a connection request is input, forwards the connection request to an application execution system that executes an application used by a user, and the connection control unit identifies the application execution system to which the connection request is to be forwarded based on forwarding information indicating the relationship between the content of the connection request and the destination of the connection request, and the content of the connection request.

[0007] With this configuration, the service providing system of the present invention identifies the application execution system to which the connection request is to be transferred based on the transfer information and the contents of the connection request, and transfers the connection request to the identified application execution system.Therefore, an application execution system that interprets data differently from the application execution system from which the migration is made can be used as the migration destination, and as a result, it is possible to perform a migration that requires a change in the interpretation of data.

[0008] The service providing system of the present invention may one-way synchronize changes in the database of the application execution system of the migration source with the database of the application execution system of the migration destination.

[0009] With this configuration, the service providing system of the present invention does not synchronize changes in the database of the migration-destination application execution system with the database of the migration-source application execution system, thereby reducing the possibility that changes in the database of the migration-destination application execution system will affect the user's use of the migration-source application execution system, and as a result, reducing the possibility that a service outage of the application execution system being used by the user will occur due to changes in the database of the migration-destination application execution system.

[0010] In the service providing system of the present invention, the application execution system at the migration source and the application execution system at the migration destination may be realized by different computer systems.

[0011] With this configuration, the service provision system of the present invention is realized by different computer systems for the source application execution system and the destination application execution system, thereby reducing the possibility that the load caused by the generation of the destination application execution system will affect the user's use of the source application execution system, and as a result, reducing the possibility that the generation of the destination application execution system will cause a service outage of the application execution system used by the user.

[0012] The service provision program of the present invention causes a computer to implement a connection control unit that, when a connection request is input, transfers the connection request to an application execution system that executes an application used by a user, and the connection control unit identifies the application execution system to which the connection request is to be transferred based on transfer information indicating the relationship between the content of the connection request and the destination of the connection request, and the content of the connection request.

[0013] With this configuration, a computer executing the service provision program of the present invention identifies an application execution system to which the connection request is to be transferred based on the transfer information and the contents of the connection request, and transfers the connection request to the identified application execution system.Therefore, an application execution system that interprets data differently from the application execution system from which the migration is originated can be used as the migration destination, and as a result, it is possible to perform a migration that requires a change in the interpretation of data. [Effects of the Invention]

[0014] The service providing system and service providing program of the present invention can perform migration that requires a change in the interpretation of data. [Brief explanation of the drawings]

[0015] [Figure 1] 1 is a block diagram of an example of a system according to an embodiment of the present invention. [Figure 2]FIG. 2 is a diagram showing an example of a system table shown in FIG. [Figure 3] FIG. 2 is a diagram showing an example of a transfer table shown in FIG. [Figure 4] FIG. 2 is a diagram showing an example of a one-way synchronization table shown in FIG. [Figure 5] FIG. 2 is a diagram illustrating an example of a computer that realizes the connection control unit illustrated in FIG. 1. [Figure 6] FIG. 10 is a block diagram of a service providing system including only one application execution system. [Figure 7] FIG. 3 is a diagram showing an example of a system table different from the example shown in FIG. 2. [Figure 8] 4 is a diagram showing an example of a transfer table different from the example shown in FIG. 3. FIG. [Figure 9] 7 is a sequence diagram of the operation of the application execution system shown in FIG. 6 when a user terminal is connected to the system. [Figure 10] 10 is a flowchart of the operation of the service providing system shown in FIG. 1 when identifying access information to be used for transferring a connection request. [Figure 11] 10 is a flowchart of the operation of the service providing system shown in FIG. 1 when a migration destination application execution system is added. [Figure 12] 10 is a flowchart of the operation of the service providing system shown in FIG. 1 when changes in a database of a migration-source application execution system are one-way synchronized with a database of a migration-destination application execution system. [Figure 13] 2 is a flowchart of a migration method for the application execution system shown in FIG. 1. [Figure 14] 7 is a sequence diagram of the operation of the system shown in FIG. 1 when a user terminal is connected to an application execution system different from the application execution system shown in FIG. 6. FIG. [Figure 15] 9 is a diagram showing an example of a transfer table different from the examples shown in FIGS. 3 and 8. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0016] An embodiment of the present invention will now be described with reference to the drawings.

[0017] First, the configuration of the system according to this embodiment will be described.

[0018] FIG. 1 is a block diagram of an example of a system 10 according to the present embodiment.

[0019] As shown in Fig. 1, the system 10 includes a service providing system 20 for providing services to users. The service providing system 20 may be configured with a single computer such as a PC (Personal Computer), or may be configured with multiple computers. The service providing system 20 may be realized on the cloud.

[0020] The service providing system 20 may include multiple application execution systems that execute applications used by users. For example, the service providing system 20 may include an application execution system 30 and an application execution system 40. The application execution system 30 and the application execution system 40 may be realized by different computer systems.

[0021] The service providing system 20 includes a connection control unit 51 that connects a user terminal used by a user to either the application execution system 30 or the application execution system 40, and a control database 52 that stores data used by the connection control unit 51.

[0022] The application execution system 30 includes an application 31 used by a user. The application execution system 30 can include at least one other application used by a user in addition to the application 31. The application execution system 30 includes a platform 32 that serves as an execution platform for applications such as the application 31, and a database 33 that stores data used by applications such as the application 31 and the platform 32. The data stored in the database 33 includes tenant management data for managing tenants. The tenant management data includes, for each tenant, for example, the name of the tenant subscriber, the name and email address of the tenant administrator, the names and email addresses of the tenant users, identification information for applications subscribed to by the tenant subscriber, and data of the tenant users, such as saved documents (hereinafter referred to as "user data"). The data stored in the database 33 includes information regarding the consistency of the tenant management data. The information regarding the consistency of the tenant management data includes index tables and reference relationships that facilitate searches for user data.

[0023] The application execution system 40 includes an application 41 that is used by a user. The application execution system 40 can include at least one other application that is used by a user in addition to the application 41. The application execution system 40 includes a platform 42 that is the execution platform for applications such as the application 41, and a database 43 that stores data used by applications such as the application 41 and the platform 42. The data stored in the database 43 is the same as the data stored in the database 33.

[0024] The control database 52 can store a system table 52a that indicates information about the application execution system.

[0025] FIG. 2 is a diagram showing an example of the system table 52a.

[0026] As shown in FIG. 2, the system table 52a includes, as items, a system ID as identification information for an application execution system, and access information as information for accessing the application execution system.

[0027] The access information is a uniform resource locator (URL) or an internet protocol (IP) address of the application execution system.

[0028] In the system table 52a shown in FIG. 2, the system ID "S001" of the application execution system 30 is associated with the URL of the application execution system 30, "https: / / example.com / ", and the system ID "S002" of the application execution system 40 is associated with the URL of the application execution system 40, "https: / / example.net / ".

[0029] As shown in FIG. 1, the control database 52 can store a transfer table 52b as transfer information used to transfer a connection request input from a user terminal to an application execution system.

[0030] FIG. 3 is a diagram showing an example of the transfer table 52b.

[0031] 3, forwarding table 52b includes, as items, a tenant ID as identification information of the tenant to which the user belongs, and forwarding destination information indicating a forwarding destination of a connection request input from a user terminal. In other words, forwarding table 52b is information indicating the relationship between a tenant ID and a forwarding destination of a connection request.

[0032] The transfer destination information is indicated by the system ID of the application execution system.

[0033] The transfer table 52b always includes a record with a tenant ID of "T000". The transfer destination information in the record with a tenant ID of "T000" is default transfer destination information. Note that a tenant with a tenant ID of "T000" does not actually exist.

[0034] In the transfer table 52b shown in FIG. 3, the record having the tenant ID "T000" is associated with "S001" as the transfer destination information, and the records having the tenant IDs "T001" to "T010" are associated with "S002" as the transfer destination information.

[0035] As shown in FIG. 1, the control database 52 can store a one-way synchronization table 52c that is used to one-way synchronize changes in the database of the migration source application execution system with the database of the migration destination application execution system.

[0036] FIG. 4 is a diagram showing an example of the one-way synchronization table 52c.

[0037] As shown in FIG. 4, the one-way synchronization table 52c includes, as items, the system ID of the application execution system at the migration source and the system ID of the application execution system at the migration destination.

[0038] In the one-way synchronization table 52c shown in FIG. 4, the system ID of the application execution system at the migration source is shown as "S001", which is the system ID of the application execution system 30, and the system ID of the application execution system at the migration destination is shown as "S002", which is the system ID of the application execution system 40.

[0039] 1, the system 10 may include a user terminal 90 used by a user. The system 10 may include at least one other user terminal used by a user in addition to the user terminal 90. The user terminal 90 may be configured by a computer such as a PC or a smartphone.

[0040] FIG. 5 is a diagram showing an example of a computer 60 that realizes the connection control unit 51.

[0041] As shown in Figure 5, computer 60 includes an operation unit 61, which is an operation device such as a keyboard or mouse through which various operations are input; a display unit 62, which is a display device such as an LCD (Liquid Crystal Display) that displays various information; a communication unit 63, which is a communication device that communicates with external devices via a network such as a LAN (Local Area Network) or the Internet, or directly via a wired or wireless connection without using a network; a memory unit 64, which is a non-volatile memory device such as a semiconductor memory or an HDD (Hard Disk Drive) that stores various information; and a control unit 65 that controls computer 60 as a whole.

[0042] The storage unit 64 can store a service provision program 64a for providing services to users. The service provision program 64a may be installed in the computer 60 during the manufacturing stage of the computer 60, or may be additionally installed in the computer 60 from an external storage medium such as a USB (Universal Serial Bus) memory, or may be additionally installed in the computer 60 from a network.

[0043] The control unit 65 includes, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory) that stores programs and various data, and a RAM (Random Access Memory) that serves as a memory used as a work area for the CPU of the control unit 65. The CPU of the control unit 65 executes programs stored in the storage unit 64 or the ROM of the control unit 65.

[0044] The control unit 65 realizes the connection control unit 51 by executing the service providing program 64a.

[0045] The above describes an example in which the connection control unit 51 is configured by one computer 60. However, the connection control unit 51 may be configured by a plurality of computers.

[0046] The operation of the system 10 will now be described.

[0047] First, the operation of the system 10 when a user terminal 90 is connected to the application execution system 30 will be described.

[0048] Fig. 6 is a block diagram of the system 10 in which the service providing system 20 is equipped only with the application execution system 30 as the application execution system. Fig. 7 is a diagram showing an example of the system table 52a that is different from the example shown in Fig. 2. Fig. 8 is a diagram showing an example of the transfer table 52b that is different from the example shown in Fig. 3. Fig. 9 is a sequence diagram of the operation of the system 10 in which a user terminal 90 is connected to the application execution system 30.

[0049] 6, the system table 52a and the transfer table 52b are as shown in FIGS. 7 and 8, respectively, and the one-way synchronization table 52c is not stored in the control database 52. When the identification information of the tenant to which the user of the user terminal 90 belongs is "T001," if the user instructs the user terminal 90 to connect to the application execution system, the user terminal 90 transmits a connection request to the application execution system to the connection control unit 51 (S101), as shown in FIG. 9. Here, the user terminal 90 includes "T001" as the tenant ID of the tenant to which the user of the user terminal 90 belongs in the connection request transmitted to the connection control unit 51 in S101.

[0050] When the connection control unit 51 receives the connection request sent by the user terminal 90 in S101, it acquires the system table 52a and the transfer table 52b from the control database 52 (S102).

[0051] When the process of S102 is completed, the connection control unit 51 identifies the access information to be used for transferring the connection request based on the system table 52a and transfer table 52b acquired in S102 (S103).

[0052] FIG. 10 is a flowchart showing the operation of the service providing system 20 when identifying access information to be used for transferring a connection request.

[0053] As shown in FIG. 10, the connection control unit 51 determines whether the tenant ID included in the connection request sent by the user terminal 90 and received by the connection control unit 51 is included in the transfer table 52b (S121).

[0054] When the connection control unit 51 determines in S121 that the tenant ID included in the connection request sent by the user terminal 90 and received by the connection control unit 51 is included in the transfer table 52b, it identifies the access information associated in the system table 52a with the transfer destination information associated in the transfer table 52b with the tenant ID included in the connection request sent by the user terminal 90 and received by the connection control unit 51 as the access information to be used for transferring the connection request (S122).

[0055] When the connection control unit 51 determines in S121 that the tenant ID included in the connection request sent by the user terminal 90 and received by the connection control unit 51 is not included in the transfer table 52b, it identifies the access information associated in the system table 52a with the transfer destination information associated in the transfer table 52b with the tenant ID "T000" as the access information to be used for transferring the connection request (S123).

[0056] When the process of S122 or S123 is completed, the connection control unit 51 ends the operation shown in FIG.

[0057] If the tenant ID of the tenant to which the user of user terminal 90 belongs is "T001" and system table 52a and forwarding table 52b are as shown in Figures 7 and 8, respectively, connection control unit 51 determines in S121 that "T001," which is the tenant ID included in the connection request sent by user terminal 90 and received by connection control unit 51, is not included in forwarding table 52b, and identifies in S123, "https: / / example.com / ," which is the access information associated in system table 52a with "S001," which is the forwarding destination information associated in forwarding table 52b with "T000" as the tenant ID, as the access information to be used for forwarding the connection request.

[0058] As shown in FIG. 9, when the processing of S103 is completed, the connection control unit 51 transfers the connection request sent by the user terminal 90 in S101 and received by the connection control unit 51 to the application execution system 30 based on the access information "https: / / example.com / " identified in S103 (S104).

[0059] Therefore, the user terminal 90 is connected to the application execution system 30 .

[0060] The above describes a case where the system 10 is in the state shown in Figure 6, the system table 52a and the transfer table 52b are as shown in Figures 7 and 8, the one-way synchronization table 52c is not stored in the control database 52, and the tenant ID of the tenant to which the user of the user terminal 90 belongs is "T001." However, similarly, when the system 10 is in the state shown in Figure 6, the system table 52a and the transfer table 52b are as shown in Figures 7 and 8, the one-way synchronization table 52c is not stored in the control database 52, and the tenant ID of the tenant to which the user of the user terminal belongs is other than "T001," the user terminal is connected to the application execution system 30.

[0061] Next, the operation of the service providing system 20 when a migration destination application execution system 40 is added will be described.

[0062] FIG. 11 is a flowchart of the operation of the service providing system 20 when a migration-destination application execution system 40 is added.

[0063] When the system 10 is in the state shown in FIG. 6, the system table 52a and the transfer table 52b are as shown in FIG. 7 and FIG. 8, respectively, and the one-way synchronization table 52c is not stored in the control database 52, if the application execution system 30 is the migration source and the administrator of the service providing system 20 instructs the connection control unit 51 to add a migration destination application execution system whose access information is "https: / / example.net / ", the connection control unit 51 changes the system table 52a to that shown in FIG. 2, as shown in FIG. 11 (S141).

[0064] When the process of S141 ends, the connection control unit 51 copies the application, platform 32, and database 33 of the migration source application execution system 30 to generate the migration destination application execution system 40 as shown in FIG. 1 (S142).

[0065] When the process of S142 is completed, the connection control unit 51 generates the one-way synchronization table 52c shown in FIG. 4 in the control database 52 (S143), and then ends the operation shown in FIG.

[0066] Next, the operation of the service providing system 20 when changes in the database 33 of the application execution system 30 at the migration source are one-way synchronized with the database 43 of the application execution system 40 at the migration destination will be described.

[0067] FIG. 12 is a flowchart of the operation of the service providing system 20 when changes in the database 33 of the application execution system 30 at the migration source are one-way synchronized with the database 43 of the application execution system 40 at the migration destination.

[0068] When the one-way synchronization table 52c is stored in the control database 52, the connection control unit 51 executes the operation shown in FIG.

[0069] 12 , the connection control unit 51 determines whether or not there has been a change in the database 33 of the application execution system 30 at the migration source until it determines that there has been a change in the database 33 of the application execution system 30 at the migration source (S161). For example, when an application of the application execution system 30 is used by a user terminal, data related to the application used by the user terminal may be changed in the database 33.

[0070] When the connection control unit 51 determines in S161 that there has been a change in the database 33 of the application execution system 30 at the migration source, it synchronizes the change in the database 33 of the application execution system 30 at the migration source with the database 43 of the application execution system 40 at the migration destination (S162) and executes the processing of S161.

[0071] Next, a method for migrating an application execution system will be described.

[0072] FIG. 13 is a flowchart of a method for migrating an application execution system.

[0073] 13 , the administrator of the service providing system 20 instructs the connection control unit 51 to change the applications, platform 42, and database 43 of the migration-destination application execution system 40 to those appropriate for the purpose of migration (S181). For example, if the license model for a tenant in the migration-source application execution system 30 is either a user license model based on the number of users who use the application execution system 30 and the contract period, or a device license model based on the number of electronic devices, such as image forming devices, connected to the application execution system 30 and the contract period, and the purpose of migration is to change the license model for the tenant to a subscription-based license model for a specific period, such as one month or one year, the administrator of the service providing system 20 can instruct the connection control unit 51 to change the applications, platform 42, and database 43 of the migration-destination application execution system 40 to those for the subscription-based license model. Upon receiving the instruction from the administrator of the service providing system 20, the connection control unit 51 changes the applications, platform 42, and database 43 of the migration-destination application execution system 40 in accordance with the received instruction.

[0074] The connection control unit 51 does not synchronize changes in the database 43 of the migration-destination application execution system 40 with the database 33 of the migration-source application execution system 30. Therefore, even if the connection control unit 51 changes the migration-destination application execution system 40 in S181 while a user is using the application execution system 30, no service outage of the application execution system 30 occurs.

[0075] When the step of S181 is completed, the administrator of the service providing system 20 instructs the connection control unit 51 to change the transfer destination information associated in the transfer table 52b with the tenant IDs of at least some of the tenants in the service providing system 20 to the system ID of the application execution system 40 that is the migration destination (S182). Upon receiving the instruction from the administrator of the service providing system 20, the connection control unit 51 changes the transfer table 52b in accordance with the received instruction. For example, the connection control unit 51 changes the transfer table 52b to the one shown in FIG. 3.

[0076] Next, the operation of the system 10 when the user terminal 90 is connected to the application execution system 40 will be described.

[0077] FIG. 14 is a sequence diagram of the operation of the system 10 when the user terminal 90 is connected to the application execution system 40. In FIG.

[0078] 1, and the system table 52a, transfer table 52b, and one-way synchronization table 52c are as shown in FIGS. 2, 3, and 4, respectively, when the identification information of the tenant to which the user of the user terminal 90 belongs is "T001," if the user instructs the user terminal 90 to connect to the application execution system, the user terminal 90 transmits a connection request to the application execution system to the connection control unit 51, as shown in FIG. 14 (S201). Here, the user terminal 90 includes "T001" as the tenant ID of the tenant to which the user of the user terminal 90 belongs in the connection request transmitted to the connection control unit 51 in S201.

[0079] When the connection control unit 51 receives the connection request sent by the user terminal 90 in S201, it acquires the system table 52a and the transfer table 52b from the control database 52 (S202).

[0080] When the process of S202 is completed, the connection control unit 51 identifies the access information to be used for transferring the connection request based on the system table 52a and transfer table 52b acquired in S202 (S203).

[0081] If the tenant ID of the tenant to which the user of user terminal 90 belongs is "T001" and the system table 52a and the transfer table 52b are as shown in Figures 2 and 3, respectively, the connection control unit 51 determines in S121 (see Figure 10) that the tenant ID "T001" contained in the connection request sent by the user terminal 90 and received by the connection control unit 51 is included in the transfer table 52b, and identifies in S122 (see Figure 10) the access information "https: / / example.net / " that is associated in the system table 52a with the transfer destination information "S002" that is associated in the transfer table 52b with the tenant ID "T001".

[0082] When the processing of S203 is completed, the connection control unit 51 transfers the connection request sent by the user terminal 90 in S201 and received by the connection control unit 51 to the application execution system 40 based on the access information "https: / / example.net / " identified in S203 (S204).

[0083] Therefore, the user terminal 90 is connected to the application execution system 40 .

[0084] The above describes a case where the tenant ID of the tenant to which the user of the user terminal 90 belongs is "T001" when the system 10 is in the state shown in Figure 1, the system table 52a, the transfer table 52b, and the one-way synchronization table 52c are respectively shown in Figures 2, 3, and 4. However, when the system 10 is in the state shown in Figure 1, the system table 52a, the transfer table 52b, and the one-way synchronization table 52c are respectively shown in Figures 2, 3, and 4, and the tenant ID of the tenant to which the user of the user terminal belongs is "T002" to "T010," the user terminal is similarly connected to the application execution system 40. On the other hand, when the system 10 is in the state shown in FIG. 1 and the system table 52a, transfer table 52b, and one-way synchronization table 52c are as shown in FIGS. 2, 3, and 4, respectively, if the tenant ID of the tenant to which the user of the user terminal belongs is other than "T001" to "T010," the user terminal is connected to the application execution system 30 as shown in FIG. 9.

[0085] The administrator of the service providing system 20 monitors the use of the application execution system 40 by the tenants with tenant IDs "T001" to "T010" for a specific period of time, and if there are no particular problems, changes the transfer table 52b to the one shown in FIG. 15.

[0086] FIG. 15 is a diagram showing an example of the transfer table 52b that is different from the examples shown in FIGS.

[0087] When the system 10 is in the state shown in FIG. 1 and the system table 52a, transfer table 52b, and one-way synchronization table 52c are as shown in FIG. 2, FIG. 15, and FIG. 4, respectively, the user terminal is connected to the application execution system 40 regardless of the tenant ID of the tenant to which the user of the user terminal belongs.

[0088] As described above, the service providing system 20 identifies the application execution system to which the connection request is to be transferred based on the transfer table 52b and the tenant ID as the content of the connection request (S121 to S123), and transfers the connection request to the identified application execution system (S104 or S204). Therefore, the application execution system 40 that interprets data differently from the application execution system 30 that is the source of the migration can be set as the migration destination, and as a result, it is possible to perform a migration that requires a change in the interpretation of data.

[0089] Since the service providing system 20 does not synchronize changes in the database 43 of the migration-destination application execution system 40 with the database 33 of the migration-source application execution system 30, it is possible to reduce the possibility that changes in the database 43 of the migration-destination application execution system 40 will affect the user's use of the migration-source application execution system 30, and as a result, it is possible to reduce the possibility that a service outage of the application execution system 30 used by the user will occur due to changes in the database 43 of the migration-destination application execution system 40.

[0090] In the service providing system 20, the source application execution system 30 and the destination application execution system 40 are realized by different computer systems, so that the load caused by the generation of the destination application execution system 40 can be reduced to reduce the possibility that it will affect the user's use of the source application execution system 30, and as a result, the possibility of a service outage of the application execution system 30 used by the user occurring due to the generation of the destination application execution system 40 can be reduced.

[0091] In this embodiment, the content of the connection request used to identify the application execution system to which the connection request is to be transferred is a tenant ID. However, the content of the connection request used to identify the application execution system to which the connection request is to be transferred may be information other than the tenant ID. [Explanation of symbols]

[0092] 20 Service Delivery System 30 App Execution System 31 Applications 33 Databases 40 App Execution System 41 Applications 43 Databases 51 Connection control section 52b Transfer table (transfer information) 60 Computers 64a Service Delivery Program

Claims

1. a connection control unit that, when a connection request is input, transfers the connection request to an application execution system that executes an application used by a user; a connection control unit that identifies the application execution system to which the connection request is to be transferred based on the content of the connection request, transfer information indicating the relationship between the content of the connection request and the transfer destination of the connection request, and the content of the connection request.

2. 2. The service providing system according to claim 1, wherein changes in the database of the application execution system of the migration source are synchronized one-way with the database of the application execution system of the migration destination.

3. 2. The service providing system according to claim 1, wherein the application execution system at the migration source and the application execution system at the migration destination are realized by different computer systems.

4. a connection control unit that, when a connection request is input, transfers the connection request to an application execution system that executes an application used by a user; The connection control unit is a service providing program characterized in that it identifies the application execution system to which the connection request is to be transferred based on the content of the connection request, transfer information indicating the relationship between the content of the connection request and the transfer destination of the connection request, and the content of the connection request.

Images