METHOD, SERVER AND COMPUTER-READABLE RECORDING MEDIA FOR SETTING TRANSACTIONS OF MULTIPLE DATA OBJECTS

• US 20170249352A1
• Filed: 04/28/2016
• Published: 08/31/2017
• Est. Priority Date: 02/26/2016
• Status: Active Grant

• Current Assignee: Tmaxsoft. Co., Ltd.
• Original Assignee: Tmaxsoft. Co., Ltd.
• Inventors: Hwang, Jong Yun
• Granted Patent: US 9,870,387 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/2471 Distributed queries
• CPC Class Codes: G06F 16/289 Object oriented databases

Abstract

A method for setting transactions of multiple data objects is provided. The method includes steps of: (a) a server acquiring information on multiple data objects used for a service object, and obtaining information on data sources which are set to correspond respectively to the data objects by referring to a setting file; and (b) the server determining the multiple data objects to be used by local transactions or distributed transactions by referring to the information on the data source.

Claims

1. A method for setting transactions of multiple data objects, comprising steps of:

(a) a server acquiring information on multiple data objects used for a service object, and obtaining information on data sources that are set to correspond respectively to the data objects by referring to a setting file, wherein each of the data objects is a class configured to access a database where one or more specific data sources belong, and the service object is a class including one or more references to specific data objects for handling a database; and

(b) the server determining the multiple data objects to be used by local transactions by referring to the information on the data source if the information on the data source is determined to be homogenous and determining the multiple data objects to be used by distributed transactions by referring to the information on the data source if the information on the data source is not determined to be homogeneous,

wherein, before the step of (a), the server analyzes whether the information on the data sources exists or not by analyzing codes of the data objects, and as a result of analysis, if there are at least two data objects with the information on the data sources, the steps of (a) and (b) are performed on the at least two data objects.

2. The method of claim 1, wherein the multiple data objects include data used and returned to Create, Read, Update or Delete (CRUD) data in database.

4. The method of claim 1, wherein, at the step of (b2), the server determines the multiple data objects to be used by the distributed transactions by using global transactions and extended architecture (“

XA”

) data sources.

5. The method of claim 1, wherein information on aliases designated respectively to the data sources is pre-stored in the setting file, and at the step of (a), the server acquires information on one or more specific aliases designated to one or more particular data sources corresponding respectively to the multiple data objects, and obtains the information on the data sources corresponding respectively to the information on the specific aliases from the setting file.

6. The method of claim 1, wherein, if there is a data object designated to a local transaction in a code among the multiple data objects, the server excludes the data object designated to the local transaction from the execution of the step (b).

8. The method of claim 1, wherein the information on the data sources corresponding to the multiple data objects is set on a framework.

9. The method of claim 1, wherein the information on the data sources corresponding to the multiple data objects is pre-set by using codes corresponding thereto.

10. The method of claim 1, wherein the setting file includes a configuration file.

11. The method of claim 1, further comprising a step of:

(c) injecting the multiple data objects determined to be used by the local transactions or the distributed transactions into the service object.

12. The method of claim 1, wherein the step of (a) further includes steps of:

(a1) the server getting a service query; and

(a2) the server searching the service object among multiple pre-stored service objects by referring to the gotten query, and deciding the multiple data objects used for the searched service object.

3. (canceled)

7. (canceled)

13. A server for setting transactions on multiple data objects, comprising:

a communication part for acquiring the multiple data objects used in a service object; and

a processor for (i) obtaining information on data sources that are set to correspond respectively to the data objects, by referring to a configuration file, wherein each of the data objects is a class configured to access a database where one or more specific data sources belong, and the service object is a class including one or more references to specific data objects for handling a database; and

(ii) determining or allowing to determine the multiple data objects to be used by local transactions by referring to the information on which data sources are set to correspond respectively to the data objects if the information on the data source is determined to be homogenous and determine the multiple data objects to be used by distributed transactions by referring to the information on which data sources are set to correspond respectively to the data objects if the information on the data source is not determined to be homogeneous,

wherein, before the execution of (i), the processor analyzes whether the information on the data sources exists or not by analyzing codes of the data objects, and as a result of analysis, if there are at least two data objects with the information on the data sources, (i) and (ii) are performed on the at least two data objects.

14. The server of claim 13, wherein the multiple data objects include data used and returned to Create, Read, Update or Delete (CRUD) data in database.

16. The server of claim 13, wherein the processor determines or supports to determine the multiple data objects to be used by the distributed transactions by using global transactions and extended architecture (“

XA”

) data sources.

17. The server of claim 13, wherein information on aliases designated to the individual data sources is pre-stored in the setting file and the processor acquires information on one or more specific aliases designated to one or more particular data sources corresponding respectively to the multiple data objects, and obtains the information on the data sources corresponding respectively to the information on the specific aliases from the setting file.

18. The server of claim 13, wherein, if there is a data object designated to a local transaction in a code among the multiple data objects, the processor excludes the data object designated to the local transaction from the execution of (ii).

20. The server of claim 13, wherein the information on the data sources corresponding to the multiple data objects is set on a framework.

21. The server of claim 13, wherein the information on the data sources corresponding to the multiple data objects is pre-set by using codes corresponding thereto.

22. The server of claim 13, wherein the setting file includes a configuration file.

23. The server of claim 13, wherein, after the execution of (ii), the processor injects the multiple data objects determined to be used by the local transactions or the distributed transactions into the service object.

24. The server of claim 13, wherein, while performing (i), the processor gets a service query, searches the service object among multiple pre-stored service objects by referring to the gotten query, and decides the multiple data objects used for the searched service object.

15. (canceled)

19. (canceled)