JP2024003320A - System and control method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve the problem that the same ID cannot be registered even in a different region when a tenant with the same sales ID is desired to create on two regions in a parallel transfer if there is the constraint which cannot change a sales ID before or after transfer.

SOLUTION: A system for managing tenant information is characterized by having: reception means for receiving a designation of a first tenant to be a transfer target and a region; identification means for identifying tenant information of a second tenant to be subordinate to the first tenant related to the designation among the managed tenant information; and changing means for changing the region of the tenant information of the identified second tenant to the region related to the designation.

SELECTED DRAWING: Figure 4

COPYRIGHT: (C)2024,JPO&INPIT

Description

The present invention relates to a system and control method for managing tenant information.

Services that provide various IT resources such as computing, databases, storage, and applications on the Internet on demand have become popular in recent years. When managing corporate resources on this service, a multi-tenant system is generally used in which services of multiple companies coexist in one system. Each tenant basically exists independently and can only be accessed by authorized users. Furthermore, there are tenants that provide and sell services, and tenants that are customers that enjoy services (referred to as sales tenants and customer tenants, respectively). The sales tenant is located in a higher hierarchy than the customer tenant, and has a relationship of managing one or more customer tenants. Additionally, the sales tenant itself may have multiple levels.

The services that form the basis of this system operate in regions around the world. Basically, users use the system that operates in the region closest to where they live.

Furthermore, each tenant is assigned an ID that serves as an identifier, and is managed in a database. There are several types of IDs; in addition to IDs managed within the system, there are also IDs specified and assigned by the user. For example, an ID given by a user to a sales tenant is called a sales ID. Assuming that there is a restriction that the sales ID must be unique in all regions, the sales ID is managed not only in a tenant management table that manages sales tenants but also in an ID management table to ensure uniqueness. When creating a new sales tenant, check the ID management table and prohibit assignment of the same ID.

If writing between the tenant management table and the ID management table fails, the table may become unusable even though the ID of a tenant does not exist. For example, when creating a new sales tenant, the ID is first written into the ID management table. Next, the ID is written in the tenant management table, but if that process fails, the tenant creation process will fail. If the database cannot perform transaction processing, the value will remain only in the ID management table, and even if the tenant does not exist, the ID will be rejected by the ID management table's duplicate check and cannot be used. Can not.

To avoid this situation, registration of duplicate IDs in the ID management table is permitted if the following conditions are met. The conditions are that the existing ID and the newly assigned ID in the ID management table are "tenant creation in the same region" and "a certain amount of time has passed since the creation of the existing ID." This condition was designed to eliminate user operational errors or malicious designation of the same sales ID. This makes it possible to register the same ID even in a situation where the writing process seems to have failed.

Now, consider a case where you want to use the same ID in multiple regions. For example, when migrating a system from one region to another, there is a case where it is desired to reuse the ID without changing it for operational reasons. As a method for reusing IDs, a method has been considered in which a certain identifier is held in a server and a unique identifier is reused from a plurality of user agents (Patent Document 1).

Japanese Patent Application Publication No. 2006-120139

As mentioned above, multiple tenants may be migrated to another region due to issues such as communication responsiveness and personal information protection. During migration, if you temporarily stop the system that was previously running, copy the data, and restart it in the new region, the service will be temporarily suspended. Furthermore, if a failure occurs during migration, it is desirable to take measures to return the system to its pre-migration state, but this incurs the cost of rebuilding the pre-migration state. Therefore, a method of migrating while running the systems in the old and new regions in parallel (referred to as parallel operation) can be considered. However, as mentioned above, there is a restriction that the sales ID cannot be changed before and after migration, and when you want to create tenants with the same sales ID in two regions in parallel operation, the problem is that the same ID cannot be registered even in different regions. emerges.

Therefore, the present invention aims to migrate tenants without changing sales IDs while running systems in two regions in parallel, based on the above-described processing.

In order to solve the above-mentioned problems, the present invention provides a system for managing tenant information, comprising: an accepting means for accepting the designation of a first tenant and a region to be migrated; and a changing means for changing the region of the tenant information of the identified second tenant to the specified region. It is characterized by

According to the present invention, it is possible to migrate tenants without changing sales IDs while running systems in two regions in parallel.

FIG. 1 is a diagram showing a system configuration. FIG. 2 is a configuration diagram of a tenant management server according to the present embodiment. FIG. 3 is a diagram showing software functions according to the present embodiment. 12 is a flowchart of a process of rewriting a value of a region to be migrated in an ID management table according to the present embodiment. It is a flowchart of the process at the time of tenant creation in an ID management table based on this Embodiment. FIG. 7 is a diagram showing software functions according to the second embodiment. It is a flowchart of the process which deletes the information of the migrated tenant in the tenant management table based on the 2nd form of this embodiment.

DESCRIPTION OF THE PREFERRED EMBODIMENTS The best mode for carrying out the present invention will be described below with reference to the drawings.

FIG. 1 is a system configuration diagram according to the present embodiment. Connected to the Internet 100 are tenant management servers 101 and 111, databases 102 and 112, and a client terminal 103. Furthermore, there are two regions in the Internet 100, 121 indicates region A, and 122 indicates region B. The tenant management server 101 and database 102 are operating in region A, and the tenant management server 111 and database 112 are operating in region B. However, in this embodiment, when explaining operations that are the same in all regions, the number of region A will be used.

The tenant management server 101 is a server that performs processing related to multi-tenant management, and searches for, registers, updates, and deletes tenants. The tenant management server 101 may operate on a serverless service in which a server is not constructed as an instance. Furthermore, middleware such as a WEB server may operate on the tenant management server 101 or on another server.

The database 102 manages tenant information using a tenant management table, an ID management table, and the like. A tenant management table is stored in each region of the databases 102 and 112, but one ID management table is stored in all regions, that is, in this embodiment, only in the database 102 of region A.

The client terminal 103 is a terminal operated by a user. For example, a web page provided by the tenant management server 101 is accessed through a browser to create or edit a tenant. In addition, a tenant migration instruction is also issued from the client terminal 103 to the tenant management server 101. The terminal is typically a PC or a mobile terminal, but other devices may also be used.

Other components and processes that are not directly related to this embodiment will not be described.

FIG. 2 is a diagram showing the hardware configuration of the tenant management server 101. The hardware diagram shown in FIG. 2 corresponds to a hardware diagram of a general information processing device, and the hardware configuration of a general information processing device can be applied to the terminal of this embodiment.

In FIG. 2, a CPU 201 executes a program such as an OS or an application stored in a program ROM of a ROM 203 or loaded into a RAM 202 from an external memory 211 such as a hard disk (HD). Here, OS is an abbreviation for an operating system that runs on a computer. Processing in each flowchart described later can be realized by executing this program. The RAM 202 functions as the main memory, work area, etc. of the CPU 201. A keyboard controller 205 controls key input from a keyboard 209 or a pointing device (not shown). Display controller 206 controls the display on display 210. A disk controller 207 controls data access in an external memory 211 such as a hard disk (HD) or floppy disk (FD) that stores various data. The network controller 208 is connected to a network and executes communication control processing with other devices connected to the network.

In all the explanations that will be given later, unless otherwise specified, the CPU 201 is the hardware entity that executes programs in the terminal, and the application program installed in the external memory 211 is the software entity.

FIG. 3 is a diagram showing the functions of the tenant management server 101 according to this embodiment. Each functional unit shown in FIG. 3 is realized by the CPU 201 included in the tenant management server 101 executing a control program. Descriptions of functional units not related to this embodiment will be omitted.

The tenant management server 101 includes a request reception section 301, a tenant selection section 302, a region change section 303, a tenant creation section 304, and a database communication section 305.

The request receiving unit 301 receives a request from the client terminal 103. The request is, for example, creating or updating a tenant.

The tenant selection unit 302 selects a tenant whose region is to be migrated from the request received by the request reception unit 301. If the request covers all the tenants to be migrated, the information can be directly passed to the region update unit 303. However, in this embodiment, once one upper tenant is specified, processing is performed to select the lower tenant from the database 102, assuming that the lower tenant is to be migrated.

The region update unit 303 updates the region value of the migration target tenant in the ID management table to the migration destination region value based on the data received by the request reception unit 301.

The tenant creation unit 304 creates new records in the ID management table and tenant management table based on the data received by the request reception unit 301. If the sales ID is duplicated in the ID management table, it is determined whether the record can be updated.

The database communication unit 305 communicates with the database 102 and updates the values of the database 102 in response to instructions from the region update unit 303.

An example of the ID management table held by the database 102 is shown below. Table 1 is an example before updating the region value.

The ID management table includes items such as sales ID, last update date and time, and region. Explanation of items not directly related to this embodiment will be omitted.

Table 2 is an example of the ID management table after updating the region values.

In this example, the sales ID is "DIST0101" and "DIST0102" are the tenants to be migrated, and the region value in the record has been updated from "US" to "CA".

FIG. 4 is a flowchart of the process of updating the region value of the ID management table according to this embodiment.

The request receiving unit 301 of the tenant management server 101 receives from the client terminal 103 the designation of a sales tenant to be a parent to be migrated (S401). The tenant selection unit 302 then checks whether there is a sales tenant under the received sales tenant (S402). If the tenant exists, the tenant selection unit 302 obtains the sales ID of the sales tenant to identify the subordinate tenant (S403), and searches for the next sales tenant. After completing the search for the subordinate sales tenant, the region update unit 303 updates the region value of the tenant searched by the tenant selection unit 302 in the ID management table (S404). The value of the region to be updated is the value received by the request receiving unit 301.

FIG. 5 is a flowchart of the process of creating or updating records in the ID management table when creating a sales tenant, according to the present embodiment.

The request receiving unit 301 of the tenant management server 101 receives an instruction to create a new sales tenant from the client terminal 103 (S501). This tenant creation instruction includes specification of a sales tenant and region. The tenant creation unit 304 checks whether the received sales ID is duplicated in the ID management table (S502). If there are no duplicates, a new record is created (S503).

If there is a duplicate, the tenant creation unit 304 obtains the region value associated with the duplicate sales ID from the ID management table, and compares it with the region received by the request receiving unit 301 (S504). If the values are the same, the tenant creation unit 304 next obtains the last update date and time associated with the duplicate sales ID, and compares it with the current date and time during processing (S505). If a certain period of time or more has elapsed, the tenant creation unit 304 updates the record including the last update date and time (S506). By waiting for a certain period of time to elapse, specifying the same sales ID due to operational errors or malicious intent can be prevented to some extent, but this is just an example and other means may be used.

If the regions are different in S504, or if a certain period of time has not elapsed in S505, the creation of a new tenant will fail (S507).

As described above, according to the present embodiment, it is possible to migrate the tenant without changing the ID of the sales tenant while running the systems in parallel in different regions.

(Example 2)
Next, a second embodiment of the present invention will be described with reference to the drawings. Note that the explanation of the parts common to the first embodiment will be omitted, and only the different parts will be explained below.

After tenant migration is completed, the record of the migrated tenant must be deleted from the migration source tenant management table. As shown in the first embodiment, when a tenant is migrated, the region value of the tenant to be migrated in the ID management table is changed. Therefore, in this embodiment, the record to be deleted from the migration source tenant management table is determined based on the record whose region has been rewritten in the ID management table.

FIG. 6 is a diagram showing the functions of the tenant management server 101 according to the second embodiment. Each functional unit shown in FIG. 6 is realized by the CPU 201 included in the tenant management server 101 executing a control program. Descriptions of functional units not related to this embodiment will be omitted.

The tenant storage unit 601 stores tenants whose region values have been rewritten in the ID management table during tenant migration.

The tenant deletion unit 602 deletes the tenant that matches the tenant stored in the tenant storage unit 601 from the tenant management table.

FIG. 7 is a diagram showing a flow of processing for deleting a record of a migrated tenant from the tenant management table after tenant migration in the tenant management server 101 according to the second embodiment. Although not shown, in S406 of FIG. 4, the tenant storage unit 601 of the tenant management server 101 stores the tenant whose region value has been updated. For example, a new column may be added to the ID management table.

The tenant storage unit 601 of the tenant management server 101 reads the stored tenant (S701). Records are read one by one (S702), and tenants that match the migrated tenant are deleted from the tenant management table of the region before change (S703). Finish the process after deleting all tenants.

As described above, according to the second embodiment, by storing records for updating regions at the time of tenant migration, it is possible to determine which records in the tenant management table should be deleted after tenant migration.

(Other examples)
The present invention also includes devices or systems configured by appropriately combining the embodiments described above, and methods therefor.

Here, the present invention is a device or system that is the main body that executes one or more software (programs) that implements the functions of the embodiments described above. The present invention also includes a method for implementing the above-described embodiments executed by the device or system. Further, the program is supplied to the system or device via a network or various storage media, and the program is read and executed by one or more computers (CPU, MPU, etc.) of the system or device. In other words, the present invention further includes the program itself or various computer-readable storage media storing the program. Further, the present invention can also be realized by a circuit (for example, an ASIC) that realizes the functions of the embodiments described above.

101, 111 Tenant management server 102, 112 Database 103 Client terminal

Claims (10)

A system for managing tenant information,
an acceptance means for accepting the specification of a first tenant and region to be migrated;
Specifying means for specifying tenant information of a second tenant that is subordinate to the specified first tenant among the managed tenant information;
A system comprising: changing means for changing the region of the tenant information of the identified second tenant to the specified region. It has a first management means that manages tenant information common to each region,
2. The system according to claim 1, wherein the changing unit changes the region of the tenant information of the second tenant managed by the first managing unit to the specified region. a receiving means for receiving a tenant creation instruction including specification of a tenant and a region;
a creation means for creating a tenant specified in the tenant creation instruction, if the tenant information of the tenant specified in the tenant creation instruction does not overlap with the tenant information managed by the first management means; 3. The system of claim 2, comprising: a second management means for managing tenant information for each region;
The system according to claim 1, further comprising a deletion unit for deleting the tenant information of the second tenant from the tenant information of the region before the change by the change unit managed by the second management unit. . 2. The system according to claim 1, wherein the accepting means accepts a designation of a first tenant and a region to be migrated from a client terminal. A control method for a system that manages tenant information, the method comprising:
an acceptance step of accepting the designation of the first tenant and region to be migrated;
A specifying step of specifying tenant information of a second tenant that is subordinate to the specified first tenant among the managed tenant information;
A control method comprising the step of changing the region of the tenant information of the identified second tenant to the specified region. It has a first management process that manages tenant information common to each region,
7. The control method according to claim 6, wherein in the changing step, the region of the tenant information of the second tenant managed in the first management step is changed to the specified region. a receiving step of receiving a tenant creation instruction including specification of a tenant and region;
If the tenant information of the tenant specified in the tenant creation instruction does not overlap with the tenant information managed in the first management step, a creation step of creating a tenant specified in the tenant creation instruction; 8. The control method according to claim 7, further comprising: a second management step of managing tenant information for each region;
7. A deletion step of deleting the tenant information of the second tenant from the tenant information of the region before the change in the change step managed in the second management step. Control method. 7. The control method according to claim 6, wherein in the accepting step, designation of the first tenant and region to be migrated is accepted from the client terminal.

Images