KR101614890B1 - Method of creating multi tenancy history, server performing the same and storage media storing the same - Google Patents
Method of creating multi tenancy history, server performing the same and storage media storing the same Download PDFInfo
- Publication number
- KR101614890B1 KR101614890B1 KR1020140063697A KR20140063697A KR101614890B1 KR 101614890 B1 KR101614890 B1 KR 101614890B1 KR 1020140063697 A KR1020140063697 A KR 1020140063697A KR 20140063697 A KR20140063697 A KR 20140063697A KR 101614890 B1 KR101614890 B1 KR 101614890B1
- Authority
- KR
- South Korea
- Prior art keywords
- history
- transaction
- data
- message
- change
- Prior art date
Links
Images
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present invention relates to a multi-tenancy history generating server, comprising: receiving a request for processing a transaction from a tenant user and checking whether the received transaction is associated with a data change; if the transaction is associated with the data change, Generating a history message for the transaction by checking whether the history message is associated with the predetermined history management object, and transmitting the generated history message to the history database management server through a message channel connected to the history database management server . Therefore, it is possible to record and manage changed history information on a platform based on a Software as a Service (SaaS).
Description
The present invention relates to a multi-tenancy history generation technique, and more particularly, to a multi-tenancy history generation method capable of recording and managing changed history information on a SaaS (Software as a Service) And a recording medium storing the multi-tenancy history generating server.
Generally, the history management system continuously maintains past and present data generated in accordance with the passage of time in one business unit, generates a history table in units of physical tables, and stores the changed data in the business process with metadata And stores the history data in the history table to manage the history data. The history data may be classified into a change history for managing both the data before and after the change, a history of occurrence occurring in time order, and a progress history for managing the status information of the task according to the progress of the task. Or for data analysis, such as using statistical data.
Software as a Service (SaaS) system refers to the way software services are provided through the Internet without installing the software on their computers. SaaS supports multiple tenants, allowing a single virtual machine instance to serve multiple tenants.
Korean Patent No. 10-0793342 discloses a history data management system and management method of a network management apparatus capable of efficiently storing and restoring a network management apparatus by designing a table using a partition technique of a database do. This technique can solve the problem of database space fragmentation that occurs when the network management apparatus is operated for a long time, and can improve the speed of data retrieval.
Korean Patent Registration No. 10-1173587 collects unique user information stored in an RFID card issued for the user's history management and can perform history management for each user on a per tenant basis through an operation server based on a SaaS platform Which is provided as a service. This technology can efficiently manage multiple histories and access user information for each tenant, so you can earn and manage mileage points when you use RFID card
One embodiment of the present invention is to provide a multi-tenancy history generation method capable of recording and managing history information changed on a SaaS (Software as a Service) based platform for each user.
One embodiment of the present invention is to provide a multi-tenancy history generation method capable of efficiently managing a physical storage space and a change history by defining a history management database as an attribute unit.
One embodiment of the present invention is to provide a multi-tenancy history generation method capable of managing a history based on a history subject defined by an administrator and a history subject defined for each user.
In embodiments, a method for generating a multi-tenancy history includes receiving a transaction processing request from a tenant user and checking whether the received transaction is associated with a data change, and if the transaction is associated with a data change, Generating a history message for the transaction by checking whether the history message is associated with a predetermined history management object, and transmitting the generated history message to the history database management server through a message channel connected to the history database management server .
In one embodiment, the method may further include determining the history management subject based on a basic history item previously specified by the system administrator or a history item of interest predetermined by the tenant user.
The basic history item and the interest history item may correspond to a database field managed by the history database management server.
In one embodiment, the step of checking whether the received transaction is associated with a data change determines that the transaction is not associated with a change in the data if the transaction corresponds to a data query, And determining that the transaction is associated with a modification of the data if the modification corresponds.
The step of generating the history message for the transaction may include generating a software as a service (SaaS) related header and generating a transaction body including the type of the transaction and the processing result of the transaction. The message channel may be implemented in a variable queue format.
Among the embodiments, a history database generation method includes receiving a history message generated by a multi-tenancy history generation server through a message channel connected to a multi-tenancy history generation server, Comparing the stored history management objects, and storing the history change data for the history management object by detecting the changed data in the history management subject according to the comparison.
In one embodiment, upon receiving a change history inquiry request for the history management object from the tenant user, the step of providing the history change data may include providing history change data for the history management object.
The providing of the history change data for the history management object may include providing the history change data according to the storage time of the history change data or providing a snapshot associated with the history change data for each of the history management objects can do.
Among the embodiments, the multi-tenancy history generation server includes a memory for storing computer-readable instructions and a processor electrically connected to the memory and executing the following functions through the stored instructions in response to a user's request: The processor receives a transaction processing request from a tenant user to check whether the received transaction is associated with a data change and if the transaction is associated with the data change, whether the transaction is associated with a predetermined history management object And generates a history message for the transaction, and transmits the generated history message to the history database management server through a message channel connected to the history database management server.
In one embodiment, the system may further include a data history setting unit that determines the history management subject based on a basic history item previously designated by the system administrator or a history item of interest predetermined by the tenant user.
Among the embodiments, the history database management server includes a memory for storing computer-readable instructions and a processor electrically connected to the memory and executing the following functions via the stored instructions in response to a user's request: Receiving a history message generated by the multi-tenancy history generating server through a message channel connected to the multi-tenancy history generating server, comparing a processing result of a transaction included in the history message with a previously stored history management object, And a data history recording unit for detecting changed data in the previously stored history management subject and storing history change data for the history management subject.
And a data history inquiry unit for providing the history change data for the history management object upon receiving a change history inquiry request for the history management object from the tenant user.
In embodiments, the history management system may receive a transaction processing request from a tenant user to check whether the received transaction is associated with a data change, and if the transaction is associated with the data change, A multi-tenancy history generating server for generating a history message for the transaction by checking whether the history message is associated with an object, transmitting the history message to a history database management server separated through a message channel, A history message generated by the tenancy history generating server is received, the processing result of the transaction included in the history message is compared with the previously stored history management object, the changed data is detected in the previously stored history management subject according to the comparison The history management table Storing a history of data changes on the management server includes a history database.
Among the embodiments, a computer-readable recording medium on which a program for implementing the multi-tenancy history generating method is recorded includes a program for implementing a multi-tenancy history generating method performed in the multi-tenancy history generating server, A computer readable recording medium comprising: a function for receiving a transaction processing request from a tenant user and checking whether the received transaction is associated with a data change; if the transaction is associated with a data change, A function of generating a history message for the transaction by checking whether the history message is associated with the history management object, and a function of transmitting the generated history message to the history database management server through a message channel connected to the history database management server do.
Among the embodiments, the computer-readable recording medium on which the program for implementing the history database management method is recorded includes a computer-readable recording medium in which a program for implementing a history database management method performed in the history database management server is recorded, The multi-tenancy history generating server includes a function of receiving a history message generated by the multi-tenancy history generating server through a message channel connected to the multi-tenancy history generating server, a processing result of a transaction included in the history message, And a function of storing the history change data for the history management object by detecting the changed data in the history management subject in accordance with the comparison.
The multi-tenancy history generating method according to an embodiment of the present invention can record and manage changed history information on a SaaS (Software as a Service) based platform for each user.
The multi-tenancy history generating method according to an embodiment of the present invention can efficiently manage a physical storage space and a change history by defining a history management database as an attribute unit.
The multi-tenancy history generating method according to an embodiment of the present invention can manage the history based on a history subject defined by an administrator and a history subject defined for each user.
1 is a block diagram illustrating a history management system according to an embodiment of the present invention.
FIG. 2 is a diagram illustrating an internal configuration of the multi-tenancy history generating server and the history database managing server shown in FIG. 1. FIG.
FIG. 3 is a block diagram illustrating the functions of the multi-tenancy history generating server shown in FIG. 1 in isolation.
FIG. 4 is a block diagram illustrating the functions of the history database management server shown in FIG. 1 in isolation.
FIG. 5 is a flowchart illustrating a multi-tenancy history management process performed by the multi-tenancy history generating server shown in FIG. 1. FIG.
6 is a flowchart illustrating a history database management process performed by the history database management server shown in FIG.
7 is a view illustrating a history message generated by the multi-tenancy history generating server shown in FIG.
8 is a diagram illustrating history change data generated by the history database management server shown in FIG.
The description of the present invention is merely an example for structural or functional explanation, and the scope of the present invention should not be construed as being limited by the embodiments described in the text. That is, the embodiments are to be construed as being variously embodied and having various forms, so that the scope of the present invention should be understood to include equivalents capable of realizing technical ideas. Also, the purpose or effect of the present invention should not be construed as limiting the scope of the present invention, since it does not mean that a specific embodiment should include all or only such effect.
Meanwhile, the meaning of the terms described in the present application should be understood as follows.
The terms "first "," second ", and the like are intended to distinguish one element from another, and the scope of the right should not be limited by these terms. For example, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component.
It is to be understood that when an element is referred to as being "connected" to another element, it may be directly connected to the other element, but there may be other elements in between. On the other hand, when an element is referred to as being "directly connected" to another element, it should be understood that there are no other elements in between. On the other hand, other expressions that describe the relationship between components, such as "between" and "between" or "neighboring to" and "directly adjacent to" should be interpreted as well.
It is to be understood that the singular " include " or "have" are to be construed as including the stated feature, number, step, operation, It is to be understood that the combination is intended to specify that it does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.
In each step, the identification code (e.g., a, b, c, etc.) is used for convenience of explanation, the identification code does not describe the order of each step, Unless otherwise stated, it may occur differently from the stated order. That is, each step may occur in the same order as described, may be performed substantially concurrently, or may be performed in reverse order.
The present invention can be embodied as computer-readable code on a computer-readable recording medium, and the computer-readable recording medium includes any type of recording device that stores data that can be read by a computer system . Examples of the computer-readable recording medium include a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like, and also implemented in the form of a carrier wave (for example, transmission over the Internet) . In addition, the computer-readable recording medium may be distributed over network-connected computer systems so that computer readable codes can be stored and executed in a distributed manner.
All terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs, unless otherwise defined. Commonly used predefined terms should be interpreted to be consistent with the meanings in the context of the related art and can not be interpreted as having ideal or overly formal meaning unless explicitly defined in the present application.
1 is a block diagram illustrating a multi-tenancy history management system according to an embodiment of the present invention.
Referring to FIG. 1, a multi-tenancy
The multi-tenancy
The multi-tenancy
In one embodiment, the multi-tenancy
The history
The history
In one embodiment, the history
The
The present invention includes a multi-tenancy
FIG. 2 is a diagram illustrating an internal configuration of the multi-tenancy history generating server and the history database managing server shown in FIG. 1. FIG.
Referring to FIG. 2, the multi-tenancy
The
The storage unit 240 corresponds to a recording medium on which a computer can be permanently read.
At least one of the
The
The user may access the
The user may receive information (e.g., history change data) from the
In one embodiment, the display screen may display information received from the
The multi-tenancy
FIG. 3 is a block diagram illustrating the functions of the multi-tenancy history generating server shown in FIG. 1 in isolation.
Referring to FIG. 3, the multi-tenancy
The data
In one embodiment, the data
The
The
The
The
The
FIG. 4 is a block diagram illustrating the functions of the history database management server shown in FIG. 1 in isolation.
Referring to FIG. 4, the history
The data
The data
The data
In one embodiment, the data
The data
In one embodiment, the data
In another embodiment, the data
The
5 is a flowchart illustrating a multi-tenancy history generating process performed by the multi-tenancy history generating server shown in FIG.
Referring to FIG. 5, the data
The
The
The
If the transaction received from the tenant user corresponds to a data inquiry, the
The
The
6 is a flowchart illustrating a history database management process performed by the history database management server shown in FIG.
Referring to FIG. 6, the data
The data
The data
For example, in FIG. 8, the history change data may be implemented in a table form and may include a history work table including history job information (e.g., job number, job date, worker and article ID) (E.g., history sequence, job number, data ID, attribute ID, history item, and history data) for the data history table and data change management (e.g., job number, data ID, And may include a data property history table. Here, the history work table and the data history table are implemented in a 1: N relationship, and the data history table and the data property history table can be implemented in a 1: N relationship.
When receiving the change history inquiry request for the history management object from the tenant user, the data
It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit and scope of the present invention as defined by the following claims It can be understood that
100: History management system
110: Multi-tenancy history generating server
120: History database management server
130: User terminal
310: Data history setting unit
320: Data access unit
410: Data history log
420: Data history inquiry unit
330, and 430:
Claims (16)
Checking whether the transaction is associated with a predetermined history management object if the transaction is associated with the data change, and generating a history message for the transaction; And
And transmitting the generated history message to the history database management server through a message channel connected to the history database management server,
The step of generating a history message for the transaction
Generating a SaaS (Software as a Service) related header including a processing date of the transaction, an identifier for the tenant user requesting the transaction processing, and a key value of the master information; And
Generating a transaction body comprising a type of the transaction and a result of processing the transaction
A method for generating a multi-tenancy history.
Further comprising the step of determining the history management subject based on a basic history item previously specified by the system administrator or a history item of interest predetermined by the tenant user.
And a database field managed by the history database management server.
Determining that the transaction is not associated with a change in the data if the transaction corresponds to a data query and determining that the transaction is associated with a change in the data if the transaction is a data registration, Wherein the multi-tenancy history generating method comprises:
Wherein the data is implemented in a variable queue format.
Comparing a processing result of the transaction included in the history message with a previously stored history management object; And
And storing history change data for the history management object by detecting changed data in the history management subject stored in advance according to the comparison,
The history message
A software as a service (SaaS) related header including a transaction date, an identifier for a tenant user requesting processing of the transaction, and a key value of the master information, and a transaction body including the type of the transaction and the processing result of the transaction Included
How to manage the history database.
Further comprising the step of providing history change data for the history management object upon receiving a change history inquiry request for the history management object from the tenant user.
Providing the history change data according to the storage time of the history change data or providing a snapshot associated with the history change data for each history management object.
And a processor electrically connected to the memory and executing the following functions through the stored instructions in response to a user's request:
Receiving a transaction processing request from a tenant user to check whether the received transaction is associated with a data change, checking whether the transaction is associated with a predetermined history management object if the transaction is associated with the data change And a data access unit for generating a history message for the transaction and transmitting the generated history message to the history database management server through a message channel connected with the history database management server,
The history message
A software as a service (SaaS) related header including a transaction date, an identifier for a tenant user requesting processing of the transaction, and a key value of the master information, and a transaction body including the type of the transaction and the processing result of the transaction Included
Multi-Tenancy History Creation Server.
Further comprising a data history setting unit for determining the history management subject based on a basic history item previously specified by the system administrator or a history item of interest predetermined by the tenant user.
And a processor electrically connected to the memory and executing the following functions through the stored instructions in response to a user's request:
Receiving a history message generated by the multi-tenancy history generating server through a message channel connected to the multi-tenancy history generating server, comparing a processing result of a transaction included in the history message with a previously stored history management object, And a history history storage unit for storing history change data for the history management target by detecting changed data in the history management subject ,
The history message
A software as a service (SaaS) related header including a transaction date, an identifier for a tenant user requesting processing of the transaction, and a key value of the master information, and a transaction body including the type of the transaction and the processing result of the transaction Included
Historical database management server.
Further comprising a data history inquiry unit for providing history change data on the history management target when receiving a change history inquiry request for the history management target from a tenant user.
Receiving a history message generated at the multi-tenancy history generating server through the message channel, comparing a processing result of a transaction included in the history message with a previously stored history management object, And a history database management server for detecting changed data in an object and storing history change data for the history management object,
The history message
A software as a service (SaaS) related header including a transaction date, an identifier for a tenant user requesting processing of the transaction, and a key value of the master information, and a transaction body including the type of the transaction and the processing result of the transaction Included
History management system.
Receiving a transaction processing request from a tenant user and checking whether the received transaction is associated with a data change;
A function of generating a history message for the transaction by checking whether the transaction is associated with a predetermined history management object when the transaction is associated with the data change; And
And a function of transmitting the generated history message to the history database management server through a message channel connected to the history database management server,
The history message
A software as a service (SaaS) related header including a transaction date, an identifier for a tenant user requesting processing of the transaction, and a key value of the master information, and a transaction body including the type of the transaction and the processing result of the transaction Included
A computer-readable recording medium on which a program for implementing a multi-tenancy history generating method is recorded.
A function of receiving a history message generated by the multi-tenancy history generating server through a message channel connected to the multi-tenancy history generating server;
Comparing a processing result of a transaction included in the history message with a previously stored history management object; And
And storing history change data for the history management object by detecting changed data in the history management subject in accordance with the comparison,
The history message
A software as a service (SaaS) related header including a transaction date, an identifier for a tenant user requesting processing of the transaction, and a key value of the master information, and a transaction body including the type of the transaction and the processing result of the transaction Included
A computer readable recording medium on which a program for implementing a history database management method is recorded.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| KR1020140063697A KR101614890B1 (en) | 2014-05-27 | 2014-05-27 | Method of creating multi tenancy history, server performing the same and storage media storing the same |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| KR1020140063697A KR101614890B1 (en) | 2014-05-27 | 2014-05-27 | Method of creating multi tenancy history, server performing the same and storage media storing the same |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| KR20150136338A KR20150136338A (en) | 2015-12-07 |
| KR101614890B1 true KR101614890B1 (en) | 2016-04-22 |
Family
ID=54872323
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| KR1020140063697A KR101614890B1 (en) | 2014-05-27 | 2014-05-27 | Method of creating multi tenancy history, server performing the same and storage media storing the same |
Country Status (1)
| Country | Link |
|---|---|
| KR (1) | KR101614890B1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20230001582A (en) | 2021-06-28 | 2023-01-05 | 주식회사 이수시스템 | Hr content multi-tenant support methods utilizing intermediate language interpreting and computer programs stored in recording media for executing the same |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106375415B (en) * | 2016-08-31 | 2019-10-22 | 东软集团股份有限公司 | The dynamic setting method and device in rental period |
| WO2022107931A1 (en) * | 2020-11-20 | 2022-05-27 | 한국전자기술연구원 | Data storage method for preventing data redundancy, and data platform using same |
| CN114553762B (en) * | 2022-01-30 | 2023-12-26 | 阿里巴巴（中国）有限公司 | Method and device for processing flow table items in flow table |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2011221635A (en) * | 2010-04-06 | 2011-11-04 | Mitsubishi Electric Corp | Project management system |
-
2014
- 2014-05-27 KR KR1020140063697A patent/KR101614890B1/en active IP Right Grant
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2011221635A (en) * | 2010-04-06 | 2011-11-04 | Mitsubishi Electric Corp | Project management system |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20230001582A (en) | 2021-06-28 | 2023-01-05 | 주식회사 이수시스템 | Hr content multi-tenant support methods utilizing intermediate language interpreting and computer programs stored in recording media for executing the same |
Also Published As
| Publication number | Publication date |
|---|---|
| KR20150136338A (en) | 2015-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10237295B2 (en) | Automated event ID field analysis on heterogeneous logs | |
| US9235636B2 (en) | Presenting data in response to an incomplete query | |
| US10546021B2 (en) | Adjacency structures for executing graph algorithms in a relational database | |
| CN107133309B (en) | Method and device for storing and querying process example, storage medium and electronic equipment | |
| JP2019532370A (en) | User authority data search method and electronic device | |
| CN109522357A (en) | A kind of data processing method, device, server and storage medium | |
| US20160092059A1 (en) | Web-based user interface dataflow editor | |
| AU2011247915B2 (en) | Enhancing an inquiry for a search of a database | |
| US10963842B1 (en) | Communication platform for email management | |
| KR101614890B1 (en) | Method of creating multi tenancy history, server performing the same and storage media storing the same | |
| TWI579715B (en) | Search servers, end devices, and search methods for use in a distributed network | |
| US20170032136A1 (en) | Autocomplete of searches for data stored in multi-tenant architecture | |
| US11165726B2 (en) | Contextual sharing for screen share | |
| US11625408B2 (en) | Systems and methods for expedited large file processing | |
| CN112104734A (en) | Method, device, equipment and storage medium for pushing information | |
| US9170780B2 (en) | Processing changed application metadata based on relevance | |
| US10033737B2 (en) | System and method for cross-cloud identity matching | |
| US11550792B2 (en) | Systems and methods for joining datasets | |
| CN112328658B (en) | User profile data processing method, device, equipment and storage medium | |
| US9607072B2 (en) | System and method for implementing nested relationships within a schemaless database | |
| US10262061B2 (en) | Hierarchical data classification using frequency analysis | |
| US9542457B1 (en) | Methods for displaying object history information | |
| CN110709870B (en) | Intelligent member management | |
| US9275358B1 (en) | System, method, and computer program for automatically creating and submitting defect information associated with defects identified during a software development lifecycle to a defect tracking system | |
| US9323817B2 (en) | Distributed storage system with pluggable query processing |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| A201 | Request for examination | ||
| E902 | Notification of reason for refusal | ||
| E701 | Decision to grant or registration of patent right | ||
| GRNT | Written decision to grant | ||
| FPAY | Annual fee payment |
Payment date: 20190401 Year of fee payment: 4 |