KR102567658B1 - Method and System for developing business components in isolation using multi-transactions - Google Patents

Abstract

A business component isolation development system and method using multi-transaction according to the present invention relates to a system and method, in which, in a development environment, a first database including at least one business table corresponding to a business area and a first request from a development application ( A first server that receives a request), accesses the first database through individual work accounts having different access rights, creates and processes a plurality of transactions, and includes at least one work table corresponding to a work area in an operating environment. A second database that operates, a second server that receives a second request from an operating application, accesses the second database through a single operating account, and processes one transaction, and different environments for each of the first server and the second server. Contains a configuration server that provides properties.

Description

Method and System for developing business components in isolation using multi-transactions}

The present invention relates to a method and system for developing business component isolation using multi-transaction.

Recently, a system including a database composed of hundreds of tables or a plurality of databases classified according to the scope of business and a plurality of applications is being developed.

These applications provide services to users using information stored in databases. In particular, applications provide services to users by acquiring information stored in databases classified according to business scopes through transactions.

At this time, the application may request information stored in the database and execute transactions in tables and databases corresponding to a plurality of business scopes through one database account. In this case, it is difficult to track transactions executed for tables and databases classified according to the scope of work, which may cause problems in system maintenance.

On the other hand, if a transaction is executed on a table or database classified according to the business scope by using a database account classified according to the business scope in order to remove the dependency between jobs, a problem in which the consistency of the database cannot be guaranteed may occur. .

The present invention is to solve the above problems, and to provide a method and system for developing business component isolation using multi-transaction as its technical task.

One aspect of the present invention relates to a business component isolation development system using multi-transaction, wherein the system includes, in a development environment, a first database including at least one business table corresponding to a business area and a first request from a development application. A first server that receives a (Request) input, accesses the first database through individual work accounts having different access rights, creates and processes a plurality of transactions, and in an operating environment, at least one work table corresponding to a work area A second server that receives a second request from a second database and an operating application, accesses the second database through a single operating account, and processes one transaction; and an environment setting server providing different environment information (properties) to each of the first server and the second server.

The first server of the system includes at least one business component, and includes a first business logic unit that processes the first request, and response information from the first database through a plurality of transactions generated by the first request. and a first framework for obtaining and providing the response information to the business component, wherein the first framework generates the plurality of transactions for the first database in response to the first request. 1 may include a transaction manager.

In addition, the first transaction manager completes the processing of the plurality of transactions for the first database through the commit preparation step and the commit execution step, and when the commit preparation step of all of the plurality of transactions is completed, the plurality of transactions The commit execution step can be executed. The first transaction manager may access a corresponding work table of the first database using a work account corresponding to a work scope of each of the plurality of transactions.

In the commit preparation step, the first transaction manager transmits a commit preparation message for each of a plurality of transactions to the first database, receives a response message to the commit preparation message from the first database, and transmits the commit preparation message to the first database. If all of the response messages for are ready to commit messages, the commit execution step may be executed, and in the commit execution step, a commit execution message of each of the plurality of transactions may be transmitted to the first database.

Meanwhile, in the commit preparation step, the first transaction manager transmits a commit preparation message to a work area corresponding to each of the plurality of transactions, receives a response message to the commit preparation message from the first database, and commits the commit preparation message. If at least one of the response messages to the preparation message is a commit preparation failure message, all ongoing steps of the plurality of transactions may be rolled back.

In another embodiment, the second server may include a second business logic unit including at least one business component that processes a second request, and the second database through one transaction corresponding to the second request. and a second framework for obtaining information from and providing the obtained information to the business component. In addition, the second framework may include a second transaction manager that generates the one transaction in response to the first request and accesses the second database using a single operating account.

The second transaction manager completes the commit of the one transaction to the second database through the commit execution step, and in the commit execution step, the commit execution message for the one transaction is sent to the second database of the second database. It may be transmitted to a management system and a response message to the commit execution message may be received from the second database management system.

Another aspect of the present invention relates to a method for developing business component isolation using multi-transaction, which is operated by a server in a development environment, comprising: receiving a first request from a development application; generating a plurality of transactions corresponding to the first request through a transaction manager of the framework; sending a commit preparation message to a first database through the transaction manager; and acquiring response information corresponding to the commit preparation message from the first database through the plurality of transactions. Transactions are sent to each business area.

Optionally, the method further comprises sending a commit execution message for a plurality of transactions to the first database when the response information obtained in the acquiring step is a commit ready message for all transactions of the plurality of transactions. can include In addition, if at least one of the response information obtained in the obtaining step is a commit preparation failure message, all of the steps performed for the plurality of transactions may be rolled back. Meanwhile, the framework may receive development environment information (properties), which is environment information corresponding to the development environment, from a configuration server, load the provided development environment information, and build the development environment.

Since the business component isolation development method and system using multi-transaction according to the present invention processes transactions through different processes in the development environment and the operating environment, it eliminates the dependency between tasks in both the development environment and the operating environment, Database consistency can be guaranteed and transactions can be processed quickly.

Business component isolation development method and system using multi-transaction according to the present invention accesses a table or database classified according to each business scope using a database account according to each business scope in a development environment, and prepares to commit a plurality of transactions. And since it is executed through the commit execution step, it is possible to restrict access to each table or database, thereby facilitating maintenance and repair of the database during the development process and ensuring the consistency of the database.

In addition, since the business component isolation development method and system using multi-transaction according to the present invention accesses the database using one database account in the operating environment and executes one transaction through the commit execution step, the transaction is processed quickly and , it has the effect of ensuring the consistency of the database.

In addition, in the business component isolation development method and system using multi-transactions according to the present invention, since the first transaction manager transmits a commit preparation message for each of a plurality of transactions corresponding to each of a plurality of business areas, physically separated or Even in the case of other DBMS products, it has the effect of guaranteeing consistency.

1 is a block diagram showing a business component isolation development system using multi-transactions according to an embodiment of the present invention.
Figure 2a is a block diagram showing a business component isolation development system using multi-transaction in a development environment according to an embodiment of the present invention.
Figure 2b is a block diagram showing a business component isolation development system using multi-transaction in an operating environment according to an embodiment of the present invention.
3 is a diagram illustrating an operation of a first framework of a first server according to an embodiment of the present invention.
4 is a diagram illustrating an operation of a second framework of a second server according to an embodiment of the present invention.
5 is a flowchart of a method for developing business component isolation using multi-transaction.
6A is a sequence diagram illustrating how transactions are processed in a development environment according to one embodiment of the present invention.
6B is a sequence diagram illustrating how transactions are processed in an operating environment in accordance with one embodiment of the present invention.

Like reference numbers throughout the specification indicate substantially the same elements. In the following description, detailed descriptions of components and functions not related to the core components of the present invention and known in the art may be omitted. The meaning of terms described in this specification should be understood as follows.

Advantages and features of the present invention, and methods of achieving them, will become clear with reference to the detailed description of the following embodiments taken in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but will be implemented in various different forms, only these embodiments make the disclosure of the present invention complete, and common knowledge in the art to which the present invention belongs. It is provided to fully inform the holder of the scope of the invention, and the present invention is only defined by the scope of the claims.

The shapes, sizes, ratios, angles, numbers, etc. disclosed in the drawings for explaining the embodiments of the present invention are illustrative, so the present invention is not limited to the details shown. Like reference numbers designate like elements throughout the specification. In addition, in describing the present invention, if it is determined that a detailed description of related known technologies may unnecessarily obscure the subject matter of the present invention, the detailed description will be omitted.

When 'includes', 'has', 'consists', etc. mentioned in this specification is used, other parts may be added unless 'only' is used. In the case where a component is expressed in the singular, the case including the plural is included unless otherwise explicitly stated.

In interpreting the components, even if there is no separate explicit description, it is interpreted as including the error range.

In the case of a description of a temporal relationship, for example, 'immediately' or 'directly' when a temporal precedence relationship is described in terms of 'after', 'following', 'next to', 'before', etc. It can also include non-continuous cases unless is used.

Although first, second, etc. are used to describe various components, these components are not limited by these terms. These terms are only used to distinguish one component from another. Therefore, the first component mentioned below may also be the second component within the technical spirit of the present invention.

The term “at least one” should be understood to include all possible combinations from one or more related items. For example, "at least one of the first item, the second item, and the third item" means not only the first item, the second item, or the third item, but also two of the first item, the second item, and the third item. It may mean a combination of all items that can be presented from one or more.

Each feature of the various embodiments of the present invention can be partially or entirely combined or combined with each other, technically various interlocking and driving are possible, and each embodiment can be implemented independently of each other or can be implemented together in a related relationship. may be

Hereinafter, a business component isolation development system using multi-transaction according to an embodiment of the present invention will be described in detail with reference to FIGS. 1 to 2B. 1 is a block diagram showing a business component isolation development system using multi-transactions according to an embodiment of the present invention. Figure 2a is a block diagram showing a business component isolation development system using multi-transactions in a development environment according to an embodiment of the present invention, Figure 2b is a business using multi-transactions in an operating environment according to an embodiment of the present invention It is a block diagram representing a component isolation development system.

Referring to FIG. 1, a system for executing optimized transactions in a development environment and an operating environment includes a first database 100, a first server 200, a development terminal 300, a second database 400, and a second server. 500, a customer terminal 600, an operating terminal 700, and an environment setting server 800.

The first database 100 stores information on development applications. The first database 100 is composed of a plurality of tables or a plurality of databases, and the plurality of tables or databases are divided into business areas according to business scopes. Each work area can be accessed through a work account corresponding to each work area. That is, the first database 100 is divided into business areas according to the business scope, and may include a plurality of business accounts that can respectively access each business area.

The first database 100 includes a first database management system. The first database management system is an application program that provides functions for creating, storing, and managing data and data sets in the first database 100 . In this case, since the first database 100 may include a plurality of databases as well as a plurality of tables, the first database management system may include a database management system of a plurality of databases included in the first database 100. .

According to one embodiment of the present invention, the first database management system processes a transaction input from the first server 200 . A transaction is a unit of logical work executed in a database, and may include database operations required to perform one work. In other words, a transaction means a unit of work in which the framework initiates a request to the database through the transaction manager (creating Tx Begin) and receives a response from the database (creating Tx Commit). It is based on the transaction ID (TID) generated in In particular, according to one embodiment of the present invention, a transaction between the first database 100 and the first server 200 is committed by the first framework 220 to the first database 100 through the first transaction manager. It refers to a unit of work that transmits a preparation message and receives a response message to a commit execution message from the first database 100 . As described above, messages for one transaction between the first database 100 and the first server 200 may have the same transaction ID (TID). Specifically, until a transaction ID is generated when a commit preparation message for starting a transaction is transmitted between the first database 100 and the first server 200, and a reply message to the commit execution message for terminating the transaction is transmitted. Messages for one transaction can have the same transaction ID.

The first database management system processes a plurality of transactions respectively corresponding to the business scope of the first database 100 through a commit preparation step and a commit execution step. At this time, the commit execution step refers to an irrevocable state in which an update is executed for information stored in the database, and is distinguished from a commit prepare step in which a commit is prepared to be executed. This will be described later in detail with reference to FIG. 3 .

The first server 200 provides a development application to the development terminal 300 and generates at least one transaction for a request input through the provided application.

The first server 200 acquires information from the first database 100 through the first framework 220 to process the input request, and provides a service through an application using the acquired information. can

As shown in FIG. 2A , the first server 200 includes a first business logic unit 210 and a first framework 220 .

The first business logic unit 210 may include code implementing business logic for an application. As shown in FIG. 2A , the first business logic unit 210 includes a plurality of business components including codes for implementing each business logic. These business components provide services through applications using information obtained from the first database 100 through the first framework 220 . In this case, the plurality of business components may be classified according to the business scope. For example, if the application is a bank-related application, the first business logic unit 210 may include a business component including code implementing account-related business logic, a business component including code implementing credit-related business logic, or It may include business components including code that implements card-related business logic. This business component acquires information from the first database 100 through the first framework 220 and provides a service through an application using the acquired information. In particular, according to one embodiment of the present invention, each business component is stored in the first database 100 using a plurality of business accounts corresponding to each business area of the first database 100 through the first framework 220. It is possible to obtain information from the first database 100 through a plurality of transactions corresponding to each work area.

The first framework 220 builds an environment in which business components of the first business logic unit 210 are executed. Specifically, the first framework 220 receives development environment information (properties), which is environment information corresponding to the development environment, from a configuration server (configuration server, 800), and the business component of the first business logic unit 210 You can build an environment to run on. The first framework 220 is provided from the environment setting server 800 that stores development environment information and loads development environment information in which a specific key value is defined. The first framework 220 may build an environment in which business components of the first business logic unit 210 are executed by using the loaded development environment information. For example, an environment in which a business component of the first business logic unit 210 is executed may be established using development environment information including a 'iamf.global.xa.use' characteristic defined as 'true'. This means that consistency for multiple transactions can be guaranteed, and consistency for different accounts and even for different databases is supported.

According to an embodiment of the present invention, the configuration of the first transaction manager of the first framework 220 is determined by the development environment information. This will be described later in detail with reference to FIG. 6A.

According to an embodiment of the present invention, the first framework 220 may receive development environment information corresponding to the development environment from the environment setting server 800 in the form of JSON (JavaScript Object Notation). At this time, the JSON format is a format that uses text that can be read by a user to transmit data consisting of "property-value pairs" or "key-value pairs". Specifically, the environment setting server 800 converts the development environment information into JSON form and provides it to the first framework 220, and the first framework 220 converts the JSON form provided from the environment setting server 800 The converted development environment information is analyzed, and environment information is loaded by defining a specific key value of the environment setting file of the first framework 220 according to the analyzed development environment information.

According to another embodiment of the present invention, the first framework 220 may receive development environment information corresponding to the development environment in the form of a file from the environment setting server 800 . Specifically, the first framework 220 may download and receive development environment information in the form of a file from the environment setting server 800 . The first framework 220 loads environment information according to development environment information downloaded from the environment setting server 800 . At this time, the development environment information in the form of a file downloaded from the environment setting server 800 may be a file in which a specific key value is defined.

That is, the first framework 220 may load environment information using development environment information corresponding to the development environment from the environment setting server 800, and build an environment in which a development application is executed according to the loaded environment information. .

According to one embodiment of the present invention, the first framework 220 determines a first transaction manager managing a session for acquiring data from a work area of the first database 100 according to development environment information.

According to one embodiment of the present invention, the business component of the first business logic unit 210 provides a service to the user using information stored in the first database 100 according to a request input through a development application. To do this, the first transaction manager generates a plurality of transactions corresponding to the input request and corresponding to each work area of the first database 100 . At this time, each transaction may be carried out through a work account accessible to each work area of the first database 100 . When the transaction generated from the first transaction manager transmits a commit readiness message to the first database 100 and the first transaction manager checks the commit readiness state for all generated transactions, the first transaction manager sends the first database (100). 100), a commit execution message is sent for all transactions. When the first transaction manager receives commit execution result information as a response message to the commit execution message, the transaction is terminated. Specifically, if the first transaction manager creates a transaction before the business logic is executed and data is added or changed in the first database 100 due to the business logic, the first transaction manager As the commit preparation message is transmitted, the DBMS stores the data in the temporary storage area. When the first transaction manager checks the commit preparation stage for all transactions and requests a commit to the first database 100, the data stored in the temporary area is stored as a table area and a response message to the commit execution message is sent from the DBMS. received and the transaction ends.

According to an embodiment of the present invention, a development environment built by the development environment information provided by the environment setting server 800 is established, and a request of the first server 200 is established by a request input from a development application. 1 transaction manager generates a plurality of transactions corresponding to a plurality of work areas through a plurality of work accounts respectively accessible to a plurality of work areas of the first database 100 .

The development terminal 300 is a terminal that develops an application and receives the developed application from the first server 200, and may transmit a request to the first server 200 through the provided application.

The second database 400 stores information about applications that have been developed and operated. The second database 400 is composed of a plurality of tables or a plurality of databases. According to one embodiment of the present invention, the second database 400 may include a plurality of tables of the second database 400 or one operating account capable of accessing a plurality of databases.

The second database 400 includes a second database management system. The second database management system is an application program that provides functions for creating, storing, and managing data and data sets in the second database 400 . At this time, since the second database 400 may include a plurality of databases as well as a plurality of tables, the second database management system may include a database management system of a plurality of databases included in the second database 400. .

According to one embodiment of the present invention, the second database management system processes transactions generated from the second server 500 . As described above, a transaction refers to a unit of work in which the framework initiates a request to the database through a transaction manager (generating Tx Begin) and receives a response from the database (generating Tx Commit). This is done based on the transaction ID (TID) generated at the start of the request. In particular, according to one embodiment of the present invention, a transaction between the second database 400 and the second server 500 is committed by the second framework 520 to the second database 400 through the second transaction manager. It refers to a unit of work that transmits an execution message and receives a response message to the commit execution message from the second database 400 . Messages for one transaction between the second database 400 and the second server 500 may have the same transaction ID (TID). Specifically, until a transaction ID is generated when a commit execution message for starting a transaction is transmitted between the second database 400 and the second server 500, and a reply message to the commit execution message for ending the transaction is transmitted. Messages for one transaction can have the same transaction ID.

The second database management system processes one transaction input from the second server 500 through a commit execution step. At this time, the commit execution step refers to an irreversible state in which an update is executed for information stored in the database. This will be described later in detail with reference to FIG. 4 .

The second server 500 is developed, provides an operation application to the customer terminal 600, and generates one transaction for a request input through the application provided to the customer terminal 600.

The second server 500 acquires information from the second database 400 through the second framework 520 to process the input request, and provides a service through an application using the acquired information. can

As shown in FIG. 2B , the second server 500 includes a second business logic unit 510 and a second framework 520 .

The second business logic unit 510 may include code implementing business logic for an application. As shown in FIG. 2B , the second business logic unit 510 includes a plurality of business components each including code implementing the business logic. In this case, the plurality of business components may be classified according to the business scope. For example, if the application is a bank-related application, the second business logic unit 510 may include a business component including code implementing account-related business logic, a business component including code implementing credit-related business logic, or It may include business components including code that implements card-related business logic. This business component acquires information from the second database 400 through the second framework 520 and provides a service through an application using the acquired information. In particular, according to one embodiment of the present invention, each business component accesses the second database 400 using one operating account of the second database 400 through the second framework 520, and performs one transaction. It is possible to obtain information from the second database 400 through.

The second framework 520 builds an environment in which business components of the second business logic unit 510 are executed. Specifically, the second framework 520 receives operating environment information (properties), which is information corresponding to the operating environment, from the environment setting server 800 and builds an environment in which business components of the second business logic unit 510 are executed. can do. The second framework 520 is provided from the environment setting server 800 storing the operating environment information, and loads the operating environment information in which a specific key value is defined. The second framework 520 may build an environment in which business components of the second business logic unit 510 are executed by using the loaded operating environment information. For example, an environment in which a business component of the second business logic unit 510 is executed may be established using development environment information including a 'iamf.global.xa.use' characteristic defined as 'false'. This means that the consistency of database data additions/changes performed within a single transaction is guaranteed. In this setting environment, the consistency of different accounts or different databases is not guaranteed.

According to an embodiment of the present invention, the configuration of the second transaction manager of the second framework 520 is determined by the operating environment information. This will be described later in detail with reference to FIG. 6B.

According to an embodiment of the present invention, the second framework 520 may receive operating environment information corresponding to the operating environment in JSON form from the environment setting server 800 . Specifically, the environment setting server 800 converts the operating environment information into JSON form and provides it to the second framework 520, and the second framework 520 converts the JSON form provided from the environment setting server 800. The converted operating environment information is analyzed, and a specific key value of the environment setting file of the second framework 520 is defined according to the analyzed operating environment information, thereby establishing an environment in which the operating application is executed.

According to another embodiment of the present invention, the second framework 520 may receive operating environment information corresponding to the operating environment from the environment setting server 800 in the form of a file. Specifically, the second framework 520 may download operating environment information in the form of a file from the environment setting server 800 and receive the provided information. The second framework 520 loads environment information according to operating environment information downloaded from the environment setting server 800 . At this time, the development environment information in the form of a file downloaded from the environment setting server 800 may be a file in which a specific key value is defined.

That is, the second framework 520 may load environment information using operating environment information corresponding to the operating environment from the environment setting server 800, and build an environment in which operating applications are executed according to the loaded environment information. .

According to one embodiment of the present invention, the second framework 520 determines a second transaction manager that manages a session for acquiring data from a work area of the second database 400 according to development environment information.

According to one embodiment of the present invention, the second transaction manager executes a business component of the second business logic unit 510 in response to a request input through an operation application, and each of the second database 400 Create one transaction corresponding to the business area. At this time, one transaction may proceed through an operating account accessible to all business areas of the second database 400 . The transaction created from the second transaction manager transmits a commit execution message to the second database 400, and one generated transaction receives a response message to the commit execution message from the second database 400, and the transaction ends. do. Specifically, if the second transaction manager creates a transaction before the business logic is executed and data is added or changed in the second database 400 due to the business logic, the second transaction manager stores the data in the second database 400. As the commit execution message is transmitted, the DBMS immediately stores the data in the table area. When the second transaction manager receives the response message to the commit ready message, the second transaction manager terminates the transaction.

According to an embodiment of the present invention, an operating environment built by the operating environment information provided by the environment setting server 800 is built, and a request of the second server 500 is established by a request input from an operating application. 2 The transaction manager creates one transaction through one operational account accessible to the second database 400 .

The customer terminal 600 is a terminal that receives an operating application from the second server 500 and may transmit a request to the second server 500 through the provided application.

The operating terminal 700 is a terminal that operates an application provided by the second server 500 and can manage application settings and states through the second server 500 of the operating application.

The environment setting server 800 includes development environment information corresponding to the development environment and operating environment information corresponding to the operating environment. Specifically, the environment setting server 800 provides development environment information in which the 'iamf.global.xa.use' property is defined as 'true' and operating environment information in which the 'iamf.global.xa.use' property is defined as 'false'. includes

The environment setting server 800 provides development environment information corresponding to the development environment to the first server 200 and provides operating environment information corresponding to the operating environment to the second server 500 . Specifically, the environment setting server 800 provides development environment information in which the 'iamf.global.xa.use' characteristic is defined as 'true' to the first server 200, and the 'iamf.global.xa.use' characteristic Operating environment information defined as 'false' is provided to the second server 500 . Accordingly, the first framework 220 receives the development environment information in which 'iamf.global.xa.use' is set to 'true' from the environment setting server 800 to build a development environment, and in the built development environment. Drives the first transaction manager set by As described above, global transaction means that it can guarantee consistency for multiple transactions, and it supports consistency for different accounts and even for different databases.

In addition, the second framework 520 receives operating environment information in which the 'iamf.global.xa.use' characteristic is set to 'false' from the environment setting server 800 to build an operating environment, and to the built operating environment. The second transaction manager set by As described above, a single transaction means that the consistency of DB data additions/changes (changes processed in business logic) performed within a single transaction is guaranteed. do not support The first transaction manager driven by the development environment and the second transaction manager driven by the operating environment will be described in detail later with reference to FIGS. 3 and 4 .

Hereinafter, operations of the first framework of the first server and the second framework of the second server according to an embodiment of the present invention will be described with reference to FIGS. 3 and 4 .

3 is a diagram illustrating an operation of a first framework of a first server according to an embodiment of the present invention. 4 is a diagram illustrating an operation of a second framework of a second server according to an embodiment of the present invention.

As described above, the first database 100 according to an embodiment of the present invention is divided into work areas according to work scopes. For example, when an application includes business logic for finance and the first database 100 includes finance-related data, the first database 100 is classified according to the business scope, as shown in FIG. 3 . It can be divided into an account table as a first work area, a credit table as a second work area, and a card table as a third work area.

In addition, the first database 100 includes work accounts classified according to work scopes, and each work area can be accessed using a work account of the same work scope as the corresponding work area. For example, Account Table, the first business area, can only be accessed through the first business account, depapp, and Credit Table, the second business area, can only be accessed through the second business account, Ionapp. The in-card table can only be accessed through a third-party account, capapp. That is, according to one embodiment of the present invention, in the work area of the first database 100, the work area table can be accessed only through the work account corresponding to each work area, and indiscriminate data access is prevented through this method. This enables stable and efficient operation.

The first framework 220 according to an embodiment of the present invention builds a development environment using development environment information (properties) in which the 'iamf.global.xa.use' property is defined as 'true', and Determines the configuration of the transaction manager. The first transaction manager generates a plurality of transactions corresponding to business areas of the first database 100 in response to a request input from the development terminal 300 . Specifically, as shown in FIG. 3 , when a request is input to the first framework 220 through a development application, the first transaction manager of the first framework 220 responds to the request within a business range. A first transaction T1, a second transaction T2, and a third transaction T3 classified according to may be generated. The generated first transaction T1 , second transaction T2 , and third transaction T3 may be respectively processed through the work account of the first database 100 corresponding to the corresponding work area. For example, the first transaction manager processes the first transaction T1 in the first work area (account table) through the first work account (depapp), and processes the first transaction (T1) through the second work account (Ionapp) in the second work area. The second transaction T2 may be processed in the credit table, and the third transaction T3 may be processed in the third work area (card table) through the third work account capapp.

According to one embodiment of the present invention, the first transaction manager processes a plurality of transactions respectively corresponding to the business areas of the first database 100 through a commit preparation step and a commit execution step. This will be described in detail later with reference to FIGS. 5 and 6A.

According to an embodiment of the present invention, the first server 200 processes a plurality of transactions in each business area using a business account corresponding to each business area of the first database 100 . Specifically, since the first server 200 processes a plurality of transactions through a commit preparation step and a commit execution step, it is possible to restrict access to tables and databases in other business areas of the first database 100 during the development process. Maintenance and repair of the database becomes easy, and there is an effect of ensuring the consistency of the database.

The second database 400 according to an embodiment of the present invention, when the application includes business logic for finance and the second database 400 includes finance-related data, the second database 400 includes a plurality of Includes tables and databases. For example, as shown in FIG. 4 , the second database 400 may include an account table, a credit table, and a card table.

The second database 400 according to an embodiment of the present invention includes one operating account, and all tables and databases can be accessed through this operating account.

The second framework 520 according to an embodiment of the present invention builds an operating environment using operating environment information (properties) in which 'iamf.global.xa.use' is set to 'false', and the second transaction manager determine the composition of The second transaction manager generates a single transaction corresponding to each business area of the second database 400 in response to a request input from the customer terminal 600 . Specifically, as shown in FIG. 4 , when a request is input to the second framework 520 through an operating application, the second transaction manager of the second framework 520 sends one request to the second framework 520 . You can create a transaction (To). One generated transaction (To) may be processed through one operating account of the second database 400 . At this time, one transaction (To) can add/change processing for a plurality of tables classified according to the business scope. For example, the second transaction manager may process one transaction To for an account table, credit table, and card table through one operating account To.

The second transaction manager processes one transaction for the second database 400 through a commit execution step. This will be described later in detail with reference to FIGS. 5 and 6B.

According to the present invention, the second server 500 processes one transaction (To) for a plurality of business scopes using one operating account (To). Specifically, since the second server 500 processes one transaction through a commit execution step, there is an effect of quickly processing the transaction and guaranteeing the consistency of the second database 400 .

According to the present invention, since the first server 200 and the second server 500 are driven in different environments and thus generate and process transactions through different processes, the environment such as the product type of the database is irrelevant. It is possible to ensure the consistency of the first database 100 and the second database 400 and to quickly process transactions.

Referring to FIG. 5 , a method of executing an optimized transaction in a development environment and an operating environment according to an embodiment of the present invention will be described in detail.

5 is a flowchart of a method for developing business component isolation using multi-transaction.

Referring to FIG. 5 , transactions are created and processed through different processes in a development environment and an operating environment. That is, as described above, the environment setting server 800 provides development environment information (properties) corresponding to the development environment to the first server 200 and operating environment information (properties) corresponding to the operating environment to the second server 200 . It is provided to the server 500. Accordingly, the first transaction manager of the first framework 220 and the second transaction manager of the second framework 520 are determined to have different configurations and generate and process transactions through different methods.

In the development environment, the development environment information stored in the environment setting server 800 is provided to the first framework 220 of the first server 200 and applied to the environment setting (S511). Specifically, the first framework 220 may determine the configuration of the first transaction manager according to development environment information including the 'iamf.global.xa.use' characteristic defined as 'true'.

The first transaction manager accesses the work area corresponding to each work scope through the work account (S512). For example, as described above, the first framework 220 of the first server 200 accesses the first work area (account table) through the first work account (depapp), and the second work account ( You can access the second work area (loan table) through Ionapp).

The first server 200 and the first database 100 perform a commit preparation step (S513). Specifically, the first transaction manager of the first server 200 and the first database management system DBMS1 of the first database 100 perform a commit preparation step. In the commit preparation step, the first transaction manager transmits a commit preparation message to the first database management system (DBMS1) and receives a response message to the commit preparation message from the first database management system. In this case, the response message to the commit preparation message may be a commit preparation completion message or a commit preparation failure message. In particular, according to an embodiment of the present invention, the first transaction manager generates a plurality of transactions corresponding to a plurality of work areas in response to a request received from an application, and the first transaction manager sends a commit preparation message for all transactions. Upon receiving the commit preparation completion message as a response message to , the first transaction manager and the second database management system proceed with a commit step (S514).

A commit preparation step (S513) and a commit execution step (S514) of the first transaction manager and the first database management system will be described later in detail with reference to FIG. 6A.

In the operating environment, the operating environment information stored in the environment setting server 800 is provided to the second framework 520 of the second server 500 and applied to the environment setting (S521). Specifically, the second framework 520 may determine the configuration of the second transaction manager according to development environment information including the 'iamf.global.xa.use' characteristic defined as 'false'.

The second transaction manager accesses a plurality of business scopes of the second database 400 through one operating account (To) (S522). For example, the second transaction manager may access a plurality of business scopes (account table, credit table) through the operating account To.

The second server 500 and the second database 400 perform a commit execution step (S523). Specifically, the second transaction manager of the second server 500 and the second database management system of the second database 400 perform a commit execution step.

The commit execution step of the second transaction manager and the second database management system will be described in detail with reference to FIG. 6B.

Referring to FIGS. 6A and 6B , a commit preparation step and a commit step performed in a development environment and a commit step performed in an operating environment will be described in detail.

6A is a sequence diagram illustrating how a transaction is processed in a development environment according to an embodiment of the present invention, and FIG. 6B is a sequence diagram illustrating how a transaction is processed in an operating environment according to an embodiment of the present invention.

As described above, the first transaction manager, to which environment settings corresponding to the development environment are applied, and the second transaction manager, to which environment settings corresponding to the operating environment are applied, each process a transaction through a different process. Specifically, the first transaction manager runs in the development environment built by applying the development environment information (properties) in which 'iamf.global.xa.use' is defined as 'true' to the first framework 220, and 1 A transaction manager processes multiple transactions through a commit preparation phase and a commit execution phase. Meanwhile, in the operating environment built by applying the operating environment information (properties) in which 'iamf.global.xa.use' is defined as 'false' to the second framework 520, the second transaction manager performs a commit execution step. Process one transaction.

Referring to FIG. 6A , the first transaction manager processes a plurality of transactions through two stages: a commit preparation stage and a commit execution stage.

In the commit preparation step, the first transaction manager transmits a commit preparation message to the first database management system (DBMS1) (S611). At this time, as described above, the first transaction manager generates a plurality of transactions respectively corresponding to a plurality of work areas in response to the request received from the application. That is, the first transaction manager transmits a commit preparation message for each of a plurality of transactions to the first database management system DBMS1. In particular, according to an embodiment of the present invention, since the first transaction manager transmits a commit preparation message for each of a plurality of transactions corresponding to each of a plurality of business areas, consistency is maintained even if they are physically separated or different DBMS products. There are benefits to this guaranteed.

Thereafter, the first transaction manager receives a response message for each commit preparation message of a plurality of transactions from the first database management system (DBMS1) (S612). In this case, the response message to the commit preparation message may be a commit preparation completion message or a commit preparation failure message. If the response messages to the commit preparation messages of the plurality of transactions are all commit preparation complete messages, the first transaction manager proceeds with a commit execution step. On the other hand, if at least one of the response messages to the commit preparation messages of the plurality of transactions is a commit preparation failure message, the first transaction manager may roll back steps in progress of all transactions. Specifically, rollback means withdrawing the commit preparation phase from a transaction.

If the response messages to the commit preparation messages of the plurality of transactions are all commit preparation completion messages, the first transaction manager transmits a commit execution message to the first database management system DBMS1 (S613).

Thereafter, the first transaction manager transmits a commit execution message to the first database management system (DBMS1) (S614). In this case, the response message to the commit execution message may be a commit execution completion message or a commit execution failure message. If all of the response messages to the commit execution messages of the transaction are commit execution completion messages, the first transaction manager may determine that the commit of all transactions is completed.

As shown in FIG. 6B , the second transaction manager of the second framework 520 processes one transaction through a commit execution phase in order to quickly process the transaction.

The second transaction manager transmits the commit execution message to the second database management system (DBMS2) (S621).

Thereafter, the second transaction manager transmits a commit execution message to the first database management system (DBMS1) (S622). In this case, the response message to the commit execution message may be a commit execution completion message or a commit execution failure message. If a response message to the commit execution message of one transaction is a commit execution complete message, the second transaction manager may determine that the commit is completed.

Those skilled in the art to which the present invention pertains will be able to understand that the above-described present invention may be embodied in other specific forms without changing its technical spirit or essential features.

Additionally, the methods described herein may be implemented, at least in part, using one or more computer programs or components. This component may be provided as a set of computer instructions via a computer readable medium including volatile and nonvolatile memory or a machine readable medium. The instructions may be provided as software or firmware, and may be implemented in whole or in part in hardware configurations such as ASICs, FPGAs, DSPs, or other similar devices. The instructions may be configured for execution by one or more processors or other hardware components, which upon executing the series of computer instructions perform or perform all or part of the methods and procedures disclosed herein. make it possible

Therefore, it should be understood that the embodiments described above are illustrative in all respects and not limiting. The scope of the present invention is indicated by the following claims rather than the detailed description above, and all changes or modifications derived from the meaning and scope of the claims and equivalent concepts should be construed as being included in the scope of the present invention. do.

100: database 200: first server
300: development terminal 400: second database
500: second server 600: customer terminal
700: operating terminal 800: environment setting server

Claims (12)

As a business component isolation development system using multi-transaction,
In a development environment, a first database including at least one work area classified based on a business scope classified by business logic;
A first server that receives a first request from a development application, accesses the first database through individual work accounts having different access rights, and generates and processes a plurality of transactions;
In an operating environment, a second database including at least one work area classified based on the work scope;
a second server that receives a second request from an operating application, accesses the second database through a single operating account, and processes one transaction; and
The business component isolation development system using multi-transaction, characterized in that it comprises an environment setting server that provides different environment information (properties) to each of the first server and the second server. According to claim 1,
The first server,
a first business logic unit including at least one business component and processing the first request; and
A first framework for acquiring response information from the first database through a plurality of transactions generated by the first request and providing the response information to the business component;
The first framework,
and a first transaction manager generating the plurality of transactions for the first database in response to the first request. According to claim 2,
The first transaction manager,
completing the processing of the plurality of transactions for the first database through a commit preparation step and a commit execution step;
When the commit preparation step of all of the plurality of transactions is completed, the work component isolation development system using multi-transaction, characterized in that to execute the commit execution step of the plurality of transactions. According to claim 3,
The first transaction manager accesses a business area of the first database corresponding to a business range of each of the plurality of transactions using a business account corresponding to the business range of each of the plurality of transactions. Business component isolation development system using . According to claim 3,
The first transaction manager,
In the commit preparation step, a commit preparation message for each of a plurality of transactions is transmitted to the first database, a reply message to the commit preparation message is received from the first database, and all reply messages to the commit preparation message are sent to the first database. If it is a commit ready message, the commit execution step is executed,
In the commit execution step, the business component isolation development system using multi-transaction, characterized in that for transmitting the commit execution message of each of the plurality of transactions to the first database. According to claim 3,
The first transaction manager,
In the commit preparation step, a commit preparation message is transmitted to a business area of the first database corresponding to the business scope of each of the plurality of transactions, and a response message to the commit preparation message is received from the first database,
If at least one of the response messages to the commit preparation message is a commit preparation failure message, all in-progress steps for the plurality of transactions are rolled back. According to claim 1,
The second server,
A second business logic unit including at least one business component that processes the second request; and
A second framework for acquiring information from the second database through one transaction corresponding to the second request and providing the acquired information to the business component;
The second framework,
and a second transaction manager that generates the one transaction in response to the one request and accesses the second database using a single operating account. According to claim 7,
The second transaction manager,
Completing the commit of the one transaction to the second database through a commit execution step;
In the commit execution step, a commit execution message for the one transaction is transmitted to a second database management system of the second database;
A business component isolation development system using multi-transaction, characterized in that for receiving a response message to the commit execution message from the second database management system. In the business component isolation development method using multi-transaction, which is operated by a server in a development environment,
Receiving a first request from a development application;
generating a plurality of transactions corresponding to the first request through a transaction manager of the framework;
sending a commit preparation message to a first database through the transaction manager; and
Acquiring response information corresponding to the commit preparation message from the first database through the plurality of transactions, respectively;
In the transmitting step, the transaction is transmitted to each work area of the first database classified based on the work scope classified by the business logic using individual work accounts having different access rights. Component isolation development methodology. According to claim 9,
When the response information obtained in the acquiring step is a commit ready message for all of the plurality of transaction transactions, transmitting a commit execution message for a plurality of transactions to the first database, multi-transaction Business component isolation development method used. According to claim 9,
Characterized in that, if at least one of the response information acquired in the acquiring step is a commit preparation failure message, all of the steps in progress for the plurality of transactions are rolled back. According to claim 9,
The framework receives development environment information (properties), which is environment information corresponding to the development environment, from a configuration server, loads the provided development environment information, and builds the development environment. Business component isolation development method using multi-transaction.

Images