JP2011113103A - Multi-tenant type computer system - Google Patents

Abstract

A plurality of users can access a database of a computer system without changing an existing application.
[Solution]
When an information processing apparatus connected to a plurality of client computers receives a first request from a first client computer, information relating to the first client computer is stored in the first management information and a database is accessed. When creating an access language, information about the first client computer is read from the first management information, information about the first client computer is added to the table name included in the access language, and the access language is used to create the access language. An information processing apparatus that accesses a database.
[Selection] Figure 3

Description

  The present invention relates to a computer system used by a plurality of users (organizations), and more particularly to a server that accesses a database storing a table for each user (organization).

  Many enterprise business systems that have been implemented as desktop applications executed on clients so far have begun to be provided as SaaS (Software as a Service), which is a service on the Web.

  A characteristic of a computer system that provides SaaS is a multi-tenant computer system. The multi-tenant means a form in which a plurality of users (also referred to as organizations or tenants) access one computer system (for example, including a server and a database). In order to provide a multi-tenant computer system, it is necessary to manage data for each user in a database storing data. Here, the database refers to a relational database such as Oracle (registered trademark) Database, MySQL (registered trademark), or PostgreSQL (registered trademark in the United States). A relational database refers to a database that manages a set of data of the same type in units of tables. For example, data related to users is managed in the users table, and data related to books is managed in the books table. The table has columns that represent data attributes. For example, the user name attribute is stored in the name column of the users table.

  Patent Document 1 discloses a technique related to a method for constructing a multi-tenant database environment. With the technology described in Patent Document 1, users of a plurality of organizations can use one database.

Special table 2009-518713

  In the technique described in Patent Document 1, the structure of the database is special as described below, and various problems occur.

  The outline of the structure of the database accessed in the multi-tenant database environment described in Patent Document 1 will be described with reference to FIGS.

  FIG. 1 is a diagram illustrating an example of the structure of a database. The database includes a Data table 110, an Objects table 120, and a Fields table 130. The Data table 110 stores actual values. The Fields table 130 indicates which field the value of the Data table 110 belongs to.

FIG. 2 shows an example of the integrated table 210 managed in the multi-tenant database environment of the cited document 1. “OrgID 212” indicates an organization name (organization X, organization Y). That is, a plurality of organization tables are not managed for each organization, but are managed as an integrated table by the integrated table 210 that is one Data table.
The other columns show the following contents. The GUID 211 is a unique ID assigned to each record. ObjID 212 represents a group to which the record belongs. Related records have the same ObjID. The value of the record is stored in Value1 215, Value2 216,..., And it is grasped by referring to another Fields table which field value these are.

  As described above, in the conventional multi-tenant database environment, a new column “OrgID 212” indicating the organization name must be added and managed. There is a problem that it is necessary to develop a new application to access the application or to modify the source code of an existing application.

  An information processing apparatus for solving the above problems is an information processing apparatus connected to a plurality of client computers, and a plurality of management information for managing processing related to each request received from the plurality of client computers. A memory for storing, a processor for executing processing relating to the request with reference to the plurality of management information stored in the memory, and a plurality of tables having table names including information relating to the plurality of client computers. And a storage device for storing the database, wherein when the processor receives a first request from a first client computer included in a plurality of client computers, the processor receives information about the first client computer. Related to requests When the processor creates an access language for accessing the database based on the first request, the processor reads information on the first client computer from the first management information. An information processing apparatus characterized in that information on the first client computer is added to an access destination table name included in the access language, and the processor accesses the database using the created access language. It is.

  According to the present invention, a plurality of users can access a database of a computer system without changing an existing application.

It is a figure which shows an example of the structure of a database. An example of a table managed in a conventional multi-tenant database environment is shown. 1 is a diagram illustrating an overall configuration of a computer system in Embodiment 1. FIG. It is a figure which shows an example of the table containing the information for every structure | tissue in Example 1. FIG. 6 is a diagram illustrating an example of thread management information in Embodiment 1. FIG. 6 is a diagram illustrating an example of processing of a thread scheduling program in Embodiment 1. FIG. It is a figure which shows an example of a process of the multitenant corresponding | compatible authentication program in Example 1. FIG. It is a figure which shows an example of a process of the multi tenant corresponding | compatible database connection program in Example 1. FIG. It is a figure which shows an example of the database connection management information in Example 1. FIG. 10 is a diagram illustrating an overall configuration of a computer system according to a second embodiment. It is a figure which shows the process of the multitenant corresponding | compatible database connection program B in Example 2. FIG.

  Hereinafter, an example of an embodiment of the present invention will be described with reference to the drawings.

  Hereinafter, a first embodiment for carrying out the present invention will be described.

FIG. 3 is an overall configuration diagram of the computer system in the present embodiment.
The computer system according to the embodiment of the present invention includes a plurality of information processing apparatuses 301 and 310 connected to a network. The information processing apparatus includes one or more information processing apparatuses (hereinafter referred to as clients) 310 that are client computers, and an information processing apparatus (hereinafter referred to as servers) 301 that receives and processes requests from the clients. Although there can exist as many clients 310 as there are users, only two clients 310 are shown in FIG. Therefore, the number of clients 310 is not limited to this.

  A user who uses the client 310 belongs to “organization”. The “organization” is, for example, company A or department B, and the unit is not limited. Then, the client 310 transmits authentication information including the organization name information to the server 301 in order to use this multi-tenant compatible application. As an example of authentication information, there is a method of adding an organization name to a user ID. In the case of the user aaa belonging to the organization xxx, it is aaa @ xxx.

Hereinafter, each component will be described.
The server 301 includes a memory 302 that stores information such as a table and a program, a CPU 311 that reads and executes a program stored in the memory, and an external storage device 312 that includes a plurality of hard disks and stores data related to a database. The external storage device 312 is not limited to a hard disk, but may be a medium for storing data, and may be a flash memory or the like. In this embodiment, the external storage device 312 will be described, but it means a storage device.
The operator (administrator) of the server 301 first loads the multi-tenant compatible authentication program 305, the multi-tenant compatible database connection program 307, the database connection program 306, the application program 309, and the database management program 310 into the external storage device. Store. Since an operating system (hereinafter referred to as OS: Operating System) 317 executed by the CPU calls and executes these programs, the programs are stored in the memory, and hence these programs are stored in the memory hereinafter. . In the following, the processing to be executed will be described with the OS 317 and each program as the subject, but in practice, this means that the CPU 311 reads the OS 317 and each program from the memory 302 and executes each processing. The processing executed by each program will be described in detail later using a flowchart.

The external storage device 312 manages a database 308 that is accessed by the application program 309 through the multi-tenant compatible database connection program 306, and stores information on tables related to the database 308. The database table is divided for each organization such as an organization X table 321 and an organization Y table 322. Each table is assigned a name (for example, ID) including an information name and an organization name such as “product information @ organization X” and “product information @ organization Y”. FIG. 4 is a diagram illustrating an example of management for each organization using separate tables including product information and customer information. FIG. 4 shows product information 411 (name: product information @ organization X) of organization X, customer information 412 (name: customer information @ organization X), and product information 421 (name: product information @ organization Y) of organization Y. The table showing customer information 422 (name: customer information @ organization Y) is shown.
In the example of FIG. 3, the database 308 is stored in the external storage device 312 included in the server 301. The server 301 is connected to another database server, and the database is stored in the external storage device of the other database server. You may make it store. Further, the external storage device 312 may be configured to exist outside the server 301 as a separate storage device.

The memory 302 stores an OS 317, thread management information 313, a multi-tenant correspondence program 319, and database connection management information 323.
The OS 317 includes a thread scheduling program 318. When the server 301 accepts a request from the client 310, the OS 317 executes the thread scheduling program 318 and executes the multi-tenant correspondence program 319 to process the request. The thread scheduling program 318 creates one thread for one request. A thread refers to a state in which a program is executed, and is managed by thread management information 313.

The thread management information 313 includes a stack 414, a CPU register 415, and a thread local area 416.
FIG. 5 is a diagram illustrating an example of the thread management information 313 in the present embodiment. Note that the format of the thread management information 313 illustrated in FIG. 5 is an example, and is not limited to the format illustrated in FIG. Although a plurality of threads are managed by the OS, in this embodiment, the thread management information is held for each thread.
A local variable corresponds to the stack 414 in FIG. Local variables 1 to n are variables used locally such as functions in a program. That is, the data stored in the stack 414 cannot be shared between programs, and a specific area is assigned to a specific program.
A program counter and a stack counter correspond to the CPU register 415 in FIG. The program counter has information about where this thread is currently executing in the program. The stack counter is the current stack position.
A thread local variable corresponds to the thread local area 416 in FIG. Thread local variables are variables that can be shared between programs running in the same thread. As will be described in detail later, the organization name of the request issue source is stored in the thread local area 416.
As described above, the thread management information storage area includes an area where information cannot be shared between programs and an area where information can be shared between programs. By storing information in the thread local area 416, information can be shared between programs. In this embodiment, by storing the organization name in the thread local area 416, the organization name information can be shared by the multi-tenant authentication program 305, the multi-tenant database connection program 407, and the application program 309.

FIG. 6 is a diagram illustrating an example of processing of the thread scheduling program 318 according to the first embodiment.
When the server 301 receives a request from a certain organization, the thread scheduling program 318 determines which thread performs processing (which thread management information is used for processing). (Step 600) For example, when there is an area of thread management information that is not used for any processing, it is determined that the received request is processed using the area of the thread management information. A multi-tenant authentication program is executed (step 601). Thereafter, the thread scheduling program 318 executes the application program (step 602).

FIG. 7 is a diagram illustrating an example of processing of the multi-tenant authentication program 305 in step 601 of FIG. 6 according to the present embodiment.
The multi-tenant authentication program 305 acquires the request received from the client 310 (step 701).
The multi-tenant authentication program 305 confirms whether a session is established between the client and the server (step 702).
When the session is not established, the multi-tenant authentication program 305 confirms the presence / absence of authentication information (step 704). Here, the authentication information received from the client 310 includes information on the organization name (user name, client name, etc.) as described above.

If there is no authentication information, the multi-tenant authentication program 305 requests authentication information from the client 310 (step 707). Then, step 705 is executed.
If there is authentication information, the multi-tenant authentication program 305 determines whether or not a session can be created, and if “Yes”, creates a session (705). When creating a session, session information including information about the server that established the session and the organization name included in the authentication information is created.
Thereafter, the organization name that can be acquired from the authentication information or the created session information is stored in the thread local area included in the thread management information for managing the thread that executes the received request determined in step 600 (703).
When the session is established in step 702, the multi-tenant authentication program 305 stores the thread local area included in the thread management information for managing the thread that executes the received request determined in step 600. The organization name acquired from the session information is stored (step 703).

  FIG. 8 is a diagram illustrating an example of processing of the application program 309 in step 602 of FIG. 6 according to the present embodiment.

The application program 309 connects to the database using the database connection program specified by the database connection management information 323 shown in FIG. FIG. 9 shows an example of the database connection management information 323 in the present embodiment. The database connection management information 323 stores a database connection program name 4231, a user name 4232 for connecting to a database, and a password 4233.
In a normal application before a multi-tenant computer system configured to access a database via a server by a plurality of organizations, a normal database connection program 306 is stored in the database connection management information 323.
In the case of a multi-tenant computer system configured to access a database via a server by a plurality of organizations, the multi-tenant compatible database connection program 307 is stored in the database connection management information 323. That is, in addition to the normal database connection program 306, a program for executing processing for adding the organization name to the name of the access destination table is used.

  In the application after multi-tenancy, the application program 309 accesses the database 308 using the multi-tenant compatible database connection program 307. The processing of the multi-tenant compatible database connection program 307 will be described below. In step 802 to step 805, the multi-tenant compatible database connection program 307 uses the thread management information for managing the thread that executes the request in the table name included in the SQL (Structured Query Language) statement received from the thread scheduling program 418. The process of adding the organization name stored in the thread local area 416 included in is performed. Here, the SQL sentence is a language for accessing the database.

The multi-tenant correspondence database connection program 307 acquires the organization name from the thread local area 416 included in the thread management information received from the thread scheduling program 418 for managing the thread for executing the request (step 801).
The multi-tenant correspondence database connection program 307 decomposes the SQL sentence received from the application program 309 with a blank character (step 802). For example, when an SQL sentence “select * from users” is received, it is decomposed into four words “select”, “*”, “from”, and “users”.
The multi-tenant correspondence database connection program 307 adds an organization name to the next word after into, from, and table (step 803). This is because the words following these words are table names according to the SQL syntax rules.
The multi-tenant correspondence database connection program 307 adds the organization name to the word before the dot (step 804). This is because, according to SQL syntax rules, the word before the dot is a table name.
The multi-tenant correspondence database connection program 307 finally combines words with a blank character (step 805). For example, if the words “select”, “*”, “from”, and “X_users” are combined with a blank character, “select * from X_users” is obtained.

  The multi-tenant compatible database connection program 307 executes the database connection program 306 using the SQL statement with the organization name added (906).

  For example, if the organization name is X and the SQL statement “select users.name from users” is selected, the multi-tenant compatible database connection program 307 converts the SQL statement after conversion into an SQL statement “select X_users.name from X_users”. The database connection program 306 is executed using the database connection program 306. The database connection program 306 passes an SQL statement to the database management program 310 and requests access to data. The database management program 310 is a DBMS such as MySQL, OracleDB, or PostgreSQL. The database management program 310 can access the organization name X table 421 (product information @ organization X411 and customer information @ organization X412) with reference to the organization name (for example, X) included in the received SQL statement. .

  As described above, in this embodiment, when a request is received, the access source organization is managed by thread management information for each thread. Then, when an application executed using the thread management information of the thread accesses the database, it is possible to access an existing table by adding the access source organization name to the SQL statement. As a result, when a database that has been accessed by a single organization is changed to a form that is accessed by multiple organizations, it is possible to continue operation using existing applications and existing tables. The burden on the administrator can be reduced.

  The second embodiment for carrying out the present invention will be described below.

  FIG. 10 is a diagram illustrating an example of the overall configuration of a computer system according to the second embodiment. Except for the multi-tenant compatible database connection program B 1007 and the application program B 1009, the overall configuration of the computer system shown in FIG. Differences between the second embodiment and the first embodiment will be described below.

  The application program B 1009 inputs information on which table and what operation (reference, update, delete, generation) to the multi-tenant compatible database connection program B 1007 and executes the multi-tenant compatible database connection program B 1007 . Specifically, the application program B 1009 inputs a table name (for example, product information or customer information) to which the organization name is not added to the multi-tenant correspondence database connection program B 1007 and information on the operation content.

The multi-tenant compatible database connection program B 1007 receives, from the application program B 1009, the table name and the operation content to which the organization name to be accessed is not added.
The multi-tenant correspondence database connection program B1007 generates an SQL statement for accessing the table for each organization and returns it to the application program to B1009.

FIG. 11 shows an example of the processing flow of the multi-tenant compatible database connection program B 1007.
The multi-tenant compatible database connection program B 1007 obtains the organization name from the thread local area 416 included in the thread management information for managing the thread that executes the request received from the thread scheduling program 418 (step 1101).
The multi-tenant compatible database connection program B 1007 receives from the application program B 1009 information on the table name to be accessed and the operation content (for example, reference, update, deletion, generation). Then, an organization name is added to the received table name to be accessed, and an SQL sentence is assembled (step 1102).
The SQL statement is passed to the database connection program 407, and the database connection program 407 is executed.

  The second embodiment has an effect of reducing the burden on the application program B 1009 because the application program B 1009 does not need to assemble an SQL statement.

401: server, 402: memory, 405: multi-tenant compatible authentication program, 406: database connection program, 407: multi-tenant compatible database connection program, 409: application program, 410: client, 411: CPU, 412: external storage device, 413: Thread management information, 414: Stack area, 415: CPU register, 416: Thread local area, 317: OS, 418: Thread scheduling program, 419: Multi-tenant compatible program, 1007: Multi-tenant compatible database connection program B, 1009 : Application program B

Claims (11)

An information processing apparatus connected to a plurality of client computers,
A plurality of management information for managing processing related to each request received from the plurality of client computers; a memory for storing;
A processor that executes processing related to the request with reference to the management information stored in the memory;
A storage device for storing a database composed of a plurality of tables having table names including information relating to the plurality of client computers,
When the processor receives a first request from a first client computer included in a plurality of client computers, the processor stores information on the first client computer in first management information related to the first request. And
When creating an access language for accessing the database based on the first request, the processor reads information about the first client computer from the first management information, and accesses included in the access language Adding information about the first client computer to the destination table name;
The information processing apparatus, wherein the processor accesses the database using the created access language. The information processing apparatus according to claim 1,
When the processor receives the first request from the first client computer, the processor selects management information from the plurality of management information, and sets the selected management information as the first management information. A characteristic information processing apparatus. An information processing apparatus according to claim 2,
An information processing apparatus, wherein when selecting the management information from the plurality of management information, management information that is not used for processing related to a request received from another client computer is selected. The information processing apparatus according to claim 3,
The information processing apparatus characterized in that the processor acquires information about the first client computer based on authentication information received from the first client computer. The information processing apparatus according to claim 4,
The information processing apparatus according to claim 1, wherein the information related to the first client computer is an organization name to which the first client computer belongs. The information processing apparatus according to claim 5,
The information processing apparatus, wherein the access language is an SQL language. The information processing apparatus according to claim 6,
The first client is added to the access destination table name included in the access language by adding information on the first client computer after any of the info, from, and table words included in the access language. An information processing apparatus characterized by adding information about a computer. The information processing apparatus according to claim 6,
Adding information related to the first client computer to the access destination table name included in the access language by a process of adding information related to the first client computer before a dot included in the access language. A characteristic information processing apparatus. The information processing apparatus according to claim 7,
Each of the plurality of management information includes a first area accessible by a single program, and a second area accessible by a plurality of programs,
When information related to the first client computer is stored in the first management information related to the first request, the information processing is stored in the second area of the first management information apparatus. The information processing apparatus according to claim 9,
The plurality of management information is thread management information;
The first area includes a stack area and a CPU register area;
The second region includes a thread local region;
An information processing apparatus characterized by that. The information processing apparatus according to claim 1,
When the processor receives a second request from second client computers included in a plurality of client computers when executing processing related to the first request, the processor relates to the second client computer. Unlike the first management information, the information is stored in the second management information related to the second request,
When creating an access language for accessing the database based on the second request, the processor reads information on the second client computer from the second management information, and accesses included in the access language Adding information about the second client computer to the destination table name;
The information processing apparatus, wherein the processor accesses the database using the created access language.

Images