KR20110051779A - Data transferring system and data transferring method for the same - Google Patents

Abstract

PURPOSE: A data transferring system and a data transferring method for the same are provided to control the data transferring system through one time command. CONSTITUTION: A search thread(120) searches a data from a first storage media and temporarily stores the searched data to a local queue(110). Business process threads(130) pop the data from the local queue, apply the popped data to a second storage media, and delete the popped data from a first storage media. A first storage medium mutex(140) controls the competition of the search threads and the business process threads. A local queue mutex(150) controls the competition of the search threads and the business process threads about the local queue.

Description

Data Transfer System and Data Transferring Method for the Same}

The present invention relates to a data transfer system, and more particularly, to a data transfer system and a data transfer method for improving data transfer performance between storage media.

Most enterprise systems created over the last few decades can be broadly divided into account systems and information systems, depending on the key features they provide.

Taking the banking system as an example, the accounting system is an essential part of the banking system that processes customers' transactions in real time.It is a deposit, withdrawal, transfer, bank, bank account based on the data of a business ledger that stores important data of each business in a table form. It handles tasks such as opening and closing a bankbook and storing it as data. The information system transfers and processes the data created in the accounting system to produce information such as statistics of the records, predictions found by the records, performance measures, and settlement of accounts.

In general, the data stored by the accounting system through the business process is transferred to the information system using the bank's non-business hours, mainly night, and processed into a form that is easy for analysis. That is, the information system produced information by processing the previous day data of the account system. Recently, however, this data migration and processing is handled in real time. To this end, the information system is to query the data recorded in the storage medium of the account system in real time to reflect the storage medium of the information system.

In order to reflect the information system in real time on various transactions of the account system, it is necessary to improve the performance of the data delivery system for data inquiry and reflection.

In order to improve the performance of such a data delivery system, a method of processing data transfer in parallel has been used. This is a method of creating a plurality of processes and delivering a plurality of data at one time.

However, according to the data parallel transfer method using the plurality of processes, a plurality of processes may deliver duplicate data. The data recorded on the storage medium of the accounting system is maintained without being deleted even if it is inquired by any process of the information system. Is deleted by If one process inquires and reflects specific data, that is, the specific data may be inquired and duplicated by other processes without being deleted. In this case, the same data may be repeatedly reflected in the information system due to duplicated data.

In parallel data transmission using a plurality of processes, a group ID was set when data was stored in a storage medium of an accounting system in order to solve the data duplication inquiry and reflection problem. In the accounting system, a specific number of group IDs are set to store data, and in the information system, the same number of processes are generated to process data for each group ID. In this way, a plurality of data can be delivered simultaneously without duplication, thereby improving data transmission speed.

However, the parallel data transfer using a plurality of processes causes inconvenience to the administrator. The data delivery system cannot be controlled by one command, and there is an administrative burden of transmitting the same command to each group ID process. In the parallel data transfer method using a plurality of processes, a group ID must be set by artificially adjusting data requirements in advance. Otherwise, a process with a certain group ID is delayed in data transmission, and another process with a group ID waits after completing data transmission, resulting in inefficiency of system resource utilization.

Accordingly, the present invention has been proposed to solve the above-mentioned general problems, and the present invention has a first object to allow the administrator to control the data transfer system with a single command.

The second purpose of the method is to sequentially transmit data in order of generating data without setting a specific group ID.

The objects of the present invention are not limited to the above-mentioned objects, and other objects that are not mentioned will be clearly understood by those skilled in the art from the following description.

In accordance with another aspect of the present invention, a second storage medium (Database, Message Queue, File, etc.) of an information system may be searched for data from a first storage medium (Database) of an accounting system. A data delivery system reflected in the data storage system, comprising: a local queue for temporarily storing data selected from the first storage medium; An inquiry thread for inquiring data from the first storage medium, and temporarily storing the inquired data by pushing it to the local queue; A plurality of work processing threads for popping data from the local queue, reflecting the popped data to the second storage medium, and deleting from the first storage medium; A first storage medium controlling the contention of the query thread and the plurality of business process threads for the first storage medium so that only one of the query thread and the plurality of business process threads uses the first storage medium; Mutex; A local queue mutex that controls use contention of the query thread and the plurality of business process threads for the local queue so that only one of the query thread and the plurality of business process threads uses the first local queue; Characterized in that configured to include.

The data transfer system further includes a signal processing thread that manages all signals generated while inquiring data from the first storage medium and reflecting the data to the second storage medium. And when the process executed in the data delivery system or the data delivery system abnormally terminates, record an abnormal termination of the data delivery system or the process executed in the data delivery system in a file, and the inquiry thread and the Roll back the work performed by each of the plurality of business process threads before returning it, return the usage rights acquired by each one, terminate each other, and terminate the signal processing thread itself to restart all operations for normal operation. It is characterized by releasing system resources.

According to another preferred embodiment of the present invention, a data delivery method of a data delivery system in which data is retrieved from a first storage medium (Database) of an accounting system and reflected to a second storage medium (Database, Message Queue, File, etc.) of the information system. A data retrieval step of causing a retrieval thread to retrieve data from the first storage medium; A data pushing step of causing the inquiry thread to push the data queried from the first storage medium to a local queue; A data pop step in which one of the plurality of business processing threads pops data from the local queue; A data reflection and deletion step system in which one of the plurality of work processing threads pops work from the local queue to the second storage medium and deletes the data from the first storage medium; It is characterized by performing.

The inquiry thread executes the data inquiry step, repeats the data pushing step until all data inquired from the first storage medium in the data inquiry step is pushed to the local queue, and in the data inquiry step, When the business processing of all data inquired from the first storage medium is completed, the data inquiry step is executed again, and each of the plurality of business processing threads executes the data pop step, and from the local queue in the data pop step. If the popped data is present, the data reflection and deletion step is executed, the data popping step is performed again, and if there is no data popped from the local queue in the data popping step, the data popping step is performed again. It is characterized by.

The data delivery method of the data delivery system may be configured such that the data reflection and deletion of each of the plurality of business processing threads is stopped while the data inquiry step of the inquiry thread is performed, and one of the plurality of business processing threads is executed. While the data reflection and deletion step of the work processing thread of the data processing step of the inquiry thread and the data reflection and deletion of each of the remaining business processing thread of the plurality of business processing thread is processed to stop, While the data popping step of each of the plurality of business processing threads is stopped while the data pushing step of the inquiry thread is executed, while the data popping step of one of the business processing threads is executed. Remind me of the lookup thread The data pushing step and the data popping step of each of the remaining business processing threads among the plurality of business processing threads are processed to be stopped.

The data retrieving step may include: a retrieval authority acquiring step, wherein the retrieval thread acquires a use right for the first storage medium; An inquiry step of the inquiry thread for inquiring data from the first storage medium; And the inquiry authority returning step of returning the authority for use of the first storage medium by the inquiry thread.

The data pushing step may include: a push right obtaining step, wherein the inquiry thread obtains a use right for the local queue; Pushing, by the inquiry thread, the data queried from the first storage medium in the data inquiry step to the local queue; And a push permission return step of returning a use right for the local queue by the inquiry thread.

The data popping step may include: a pop authority acquiring step, wherein one task thread among the plurality of task threads acquires a use right for the local queue; Popping, by one of the plurality of task threads, a task thread to pop data from the local queue; And a pop right returning step of returning a use right for the local queue by one of the plurality of work processing threads.

The data reflecting and deleting step may include: obtaining, by a task processing thread of the plurality of task processing threads, a usage right for the first storage medium; A reflection and deletion step of one of the plurality of business processing threads reflecting data popped out of the local queue in the data popping step to the second storage medium and deleting from the first storage medium; And a delete right returning step of returning a use right to the first storage medium by one of the plurality of work processing threads.

The data transfer method of the data transfer system includes: a signal management step of managing, by a signal processing thread, all signals generated while inquiring data from the first storage medium and reflecting the data to the second storage medium; When the data delivery system or the process executed in the data delivery system abnormally terminates, the abnormal termination of the data delivery system or the process executed in the data delivery system is recorded in a file, and the inquiry thread and the plurality of processes are executed. Roll back the work performed by each of the task processing threads before returning it, return the usage rights acquired by each one, terminate each other, and terminate the signal processing thread itself to restart all systems for normal operation. System resource release step of releasing resources; characterized in that performed.

As described above, according to the present invention, the data transfer system can be controlled by one command by transferring data using one process having a plurality of threads, thereby reducing the administrative burden of the administrator.

In addition, system resources can be efficiently utilized by sequentially transmitting data in order of generating data without setting a specific group ID.

When the data delivery system or the process running in the data delivery system is abnormally terminated, all the system resources are reliably released to enable normal operation when the data delivery system or process is restarted.

Referring to the data delivery system and a preferred embodiment of the data delivery method according to the present invention configured as described above in detail with reference to the accompanying drawings as follows. In the following description of the present invention, detailed descriptions of well-known functions or configurations will be omitted if it is determined that the detailed description of the present invention may unnecessarily obscure the subject matter of the present invention. It is to be understood that the following terms are defined in consideration of the functions of the present invention, and may be changed according to the intention of the user, the operator, or the precedent, and the meaning of each term should be interpreted based on the contents will be.

1 is a diagram conceptually illustrating a data delivery system (hereinafter, referred to as a 'data delivery system') according to an exemplary embodiment of the present invention. As shown in FIG. 1, the data delivery system 100 is included in the information system 2 to query data from the first database 10 of the accounting system 1 so that the data system 2 can be searched for. ) To the second storage medium (Database, Message Queue, File, etc.) 20.

The data delivery system 100 may include a local queue 110, a query thread 120, a plurality of business processing threads 130, a first storage medium mutex 140, and a local queue mutex. 150, signal processing thread 160, and the like.

The local queue 110 temporarily stores data queried from the first storage medium 10 by the inquiry thread 120 to be described later. The temporarily stored data is reflected in the second storage medium 20 by a plurality of work processing threads 130 to be described later.

The inquiry thread 120 selects data from the first storage medium 10, and pushes the inquired data to the local queue 110 to temporarily store the data. The inquiry thread 120 obtains a usage right for the first storage medium 10, inquires data, and returns the usage right. In addition, the inquiry thread 120 acquires a usage right for the local queue 110, pushes one of the inquired data from the first storage medium 10, and returns the usage right. The inquiry thread 120 repeats the process of acquiring, pushing, and returning the authority for the above-described local queue 110 until all data inquired from the first storage medium 10 is pushed to the local queue 110. do. After pushing all data inquired from the first storage medium 10 to the local queue 110, the inquiry thread 120 stores the first data again when the processing of all data inquired from the first storage medium 10 is completed. The data is queried from the medium 10. If necessary, the inquiry thread 120 may edit the data in the process of inquiring data from the first storage medium 10 and pushing the data to the local queue 110.

Each of the plurality of work processing threads 130 pops data temporarily stored in the local queue 110, works the popped data on the second storage medium 20, and then stores the first storage medium 10. Delete from). Each of the plurality of business processing threads 130 obtains the usage rights for the local queue 110, pops data, and returns the usage rights. If there is data popped from the local queue 110, the task thread 130 obtains a right to use the first storage medium 10, and stores the data popped from the local queue 110 in the second storage medium 20. ) Is deleted from the first storage medium 10, and the usage right is returned. The business process thread 130 that returns the usage right for the first storage medium 10 again pops the data temporarily stored in the local queue 110. If there is no data popped from the local queue 110, the work processing thread 130 pops the data temporarily stored in the local queue 110 again. Each of the plurality of business process threads 130 may edit the data in the process of popping data from the local queue 110 and reflecting the data to the second storage medium 20 if necessary.

The first storage medium mutex 140 controls the use contention of the inquiry thread 120 and the plurality of work processing threads 130 for the first storage medium 10. As described above, each of the inquiry thread 120 and the plurality of job processing threads 130 attempts to acquire a usage right for the first storage medium 10 for data inquiry and data deletion. However, when two or more of the inquiry thread 120 and the plurality of work processing threads 130 use the first storage medium 10 at the same time, it may affect each other's work and cause an incorrect result. To prevent this, the first storage medium mutex 140 manages the use rights of the first storage medium 10 so that two or more can not use the first storage medium 10 at the same time. That is, while the inquiry thread 120 acquires the usage right of the first storage medium 10 and retrieves data, each of the plurality of work processing threads 130 may acquire the usage right of the first storage medium 10. The data cannot be reflected and deleted, and the inquiry thread 120 and the rest of the business processing thread while the arbitrary processing thread 130 acquires the use authority of the first storage medium 10 to reflect and delete the data. 130, each cannot obtain a right to use the first storage medium 10, and thus cannot respectively search for data and reflect and delete data.

The local queue mutex 150 controls the use contention of the inquiry thread 120 and the plurality of business processing threads 130 for the local queue 110. As described above, each of the inquiry thread 120 and the plurality of business processing threads 130 attempts to obtain a usage right for the local queue 110 for data push and data pop. However, when two or more of the inquiry thread 120 and the plurality of business processing threads 130 use the local queue 110 at the same time, it may affect each other's work and cause an incorrect result. In order to prevent this, the local queue mutex 150 manages the usage rights of the local queue 110 so that two or more local queues 110 cannot use the local queue 110 at the same time. That is, while the inquiry thread 120 acquires the usage rights of the local queue 110 and pushes the data, each of the plurality of business processing threads 130 cannot acquire the usage rights of the local queue 110 and thus obtains a data pop. Each of the lookup thread 120 and the rest of the processing thread 130 may not be able to do so, while any processing thread 130 obtains the usage rights of the local queue 110 to pop data. You can't get permission to do data push and data pop, respectively.

The signal processing thread 160 generates all signals generated while the data delivery system 100 delivers the data, that is, retrieves the data from the first storage medium 10 and reflects the data to the second storage medium 20. Signal) The signal generated from the data delivery system 100 is monitored, and information of the generated signal is recorded in a file (logging). In response to each signal, it is determined whether or not the data delivery system 100 is terminated, and when the data delivery system 100 ends, the data delivery system 100 is terminated. In addition, when the process executed in the data delivery system 100 or the data delivery system 100 is abnormally terminated, the signal processing thread 160 of the process that was executed in the data delivery system 100 or the data delivery system 100 may be used. Record abnormal termination to file and reliably release all system resources for normal operation upon restart. That is, the signal processing thread 160 rolls back the work performed by each of the inquiry thread 120 and the plurality of business processing threads 130 before the execution, and returns the usage rights that each has obtained. Ends, and itself ends.

The data transfer process (hereinafter, referred to as a “data transfer process”) by the data transfer system 100 will be described in detail with reference to FIGS. 2 to 5 as follows.

2 is a view sequentially illustrating a data transfer process. 3 is a view sequentially showing the operation of the inquiry thread of the data delivery system. 4 is a view sequentially showing the operation of each of the plurality of business process threads of the data delivery system. 5 is a view sequentially showing the operation of the signal processing thread of the data delivery system.

As shown in FIG. 2, the data stored in the first storage medium 10 includes a data inquiry step (S210), a data push step (S220), a data pop step (S230), and a data reflection and deletion step (S240). Through it is reflected to the second storage medium (20).

Data stored in the first storage medium 10 is inquired by the inquiry thread 120 (S210). The data inquired by the inquiry thread 120 is pushed to the local queue 110 by the inquiry thread 120 and temporarily stored (S220). Data temporarily stored in the local queue 110 is popped by each of the plurality of work processing threads 130 (S230). Data popped by each of the plurality of work processing threads 130 is reflected on the second storage medium 20 by the work processing thread 130 and deleted from the first storage medium 10 (S240).

This data transfer process will be described in more detail based on the components of the data delivery system 100 as follows.

As shown in FIG. 3, the inquiry thread 120 performs a data inquiry step S210 and a data pushing step S220.

The inquiry thread 120 performs an inquiry authority obtaining step S211, an inquiry step S212, and an inquiry authority returning step S213 to inquire data from the first storage medium 10 (S210). The inquiry thread 120 obtains a use right for the first storage medium 10 through the first storage medium mutex 140 (S211). The inquiry thread 120 obtaining the use right for the first storage medium 10 inquires data from the first storage medium 10 (S212). The inquiry thread 120 that has completed the data inquiry from the first storage medium 10 returns a use right for the first storage medium 10 (S213).

After completing the data inquiry (S210), the inquiry thread 120 performs the push permission acquisition step (S221), the push step (S222), and the push permission return step (S223) to search the data inquired from the first storage medium (10). Push to local queue 110 (S220). After completing the data inquiry (S210), the inquiry thread 120 obtains a use right for the local queue 110 through the local queue mutex 150 (S221). The inquiry thread 120 that obtains the usage right for the local queue 110 pushes the data inquired from the first storage medium 10 to the local queue 110 (S222). The inquiry thread 120 that has finished pushing data to the local queue 110 returns a usage right for the local queue 110 (S223).

After the data push (S220), the inquiry thread 120 receives the number of data inquired from the first storage medium 10 (hereinafter referred to as 'view count') and the number of data pushed to the local queue 110 (hereinafter referred to as 'number of push'). Is compared (S301). If the comparison result is greater than the number of pushes, the above-described data pushing step S220 is repeated. The comparison of the number of inquiry and the number of pushes (S301) is always performed after the data pushing step (S220) until the inquiry thread 120 pushes all the data inquired from the first storage medium 10 to the local queue 110. The data pushing step S220 is repeated.

When the inquiry thread 120 pushes all data inquired from the first storage medium 10 to the local queue 110, that is, when the number of inquiries is equal to the number of pushes, the inquiry thread 120 pushes data (S220). Stop the repetition of and waits for the completion of the processing of all data inquired from the first storage medium (10) (S302). That is, all data pushed by the inquiry thread 120 from the first storage medium 10 and pushed to the local queue 110 are popped from the local queue 110 by the plurality of work processing threads 130, and the second It is reflected on the storage medium 20 and waits for the deletion from the first storage medium 10 to be completed.

When the processing of all the data inquired from the first storage medium 10 is completed, the inquiry thread 120 performs the data inquiry step (S210) again.

In addition, even after the inquiry thread 120 performs the data inquiry step (S210), the inquiry thread is compared with the number of push cases (S301). In this case, since the number of inquiries is larger than the number of pushes in the "0" state, the data push step S220 is performed.

For reference, if the inquiry thread 120 performs the data inquiry step (S210) but there is no data in the first storage medium 10 and the inquiry count becomes "0", the number of pushes is also equal to the "0" push count. Step S220 is not performed. Since a new task does not occur, the task processing is maintained in a completed state, and the inquiry thread 120 performs the data inquiry step (S210) again.

In addition, although not shown in FIG. 3, the inquiry thread 120 may edit the data as needed in the process of inquiring data from the first storage medium 10 and pushing the data to the local queue 110.

As shown in FIG. 4, each of the plurality of business process threads 130 performs a data pop step S230 and a data reflection and deletion step S240.

Each of the plurality of work processing threads 130 performs a pop right obtaining step (S231), a pop step (S232), and a pop right returning step (S233) to pop data from the local queue 110 (S230). Each of the plurality of work processing threads 130 obtains a use right for the local queue 110 through the local queue mutex 150 (S231). The task processing thread 130 that has obtained the use authority for the local queue 110 pops data from the local queue 110 (S232). The work processing thread 130 that has finished popping data from the local queue 110 returns a usage right for the local queue 110 (S233).

The task processing thread 130 that has finished the data pop S230 determines the presence of data popped from the local queue 110 (S401). If the data exists in the local queue 110 and the data is popped by the task processing thread 130 performing the data pop step (S230), the determination result becomes the data and the data does not exist in the local queue 110. Therefore, if the task processing thread 130 performs the data pop step (S230), but the popped data does not exist, the determination result is no data.

If the pop data existence determination (S401) results in the presence of data, the work processing thread 130 that has finished the data pop (S230) may have a deletion authority obtaining step (S241), a reflection and deletion step (S242), and a deletion authority returning step ( In operation S243, data popped from the local queue 110 is reflected on the second storage medium 20 and deleted from the first storage medium 10 (S240). The task processing thread 130 that has finished the data pop S230 obtains a right to use the first storage medium 10 through the first storage medium mutex 140 (S241). The business process thread 130 having obtained the use right for the first storage medium 10 reflects the data popped from the local queue 110 to the second storage medium 20 and deletes it from the first storage medium 10. (S242). After the data is reflected on the second storage medium 20 and the data is deleted from the first storage medium 10, the corresponding work processing thread 130 returns a right to use the first storage medium 10 (S243).

When the reflection and deletion of the data popped from the local queue 110 is completed, the task processing thread 130 performs the data pop step (S230) again.

If the result of the pop data determination (S401) is no data, the data reflection and deletion step (S240) is not performed. The task processing thread 130 again performs a data pop step (S230).

Although not shown in FIG. 4, each of the plurality of work processing threads 130 may edit data as necessary in the process of popping data from the local queue 110 and reflecting the data to the second storage medium 20.

As shown in FIG. 5, the signal processing thread 160 performs a signal management step S510, a system shutdown logging step S520, and a system resource release step S530.

The signal processing thread 160 performs a signal monitoring step (S511), a received signal logging step (S512), and the system termination determination step (S513) to manage the signal (S510). The signal processing thread 160 monitors all signals generated while the data delivery system 100 inquires data from the first storage medium 10 and reflects the data to the second storage medium 20 (S511). When the signal processing thread 160 that monitors the signal receives the signal generated by the data delivery system 100, the signal processing thread 160 writes information of the received signal to a file (S512). The signal processing thread 160 that records the information of the received signal determines whether or not the data transfer system 100 ends in response to the received signal (S513). If the determination result of the termination of the data transfer system 100 is not finished, the signal processing thread 160 performs the signal monitoring step S511 again. That is, the signal processing thread 160 repeats the signal management step S510 until the determination result of whether the data transfer system 100 ends is finished.

If the result of determining whether the data delivery system 100 is terminated is an end, for example, when the process executed in the data delivery system 100 or the data delivery system 100 is abnormally terminated, the signal processing thread 160 logs system shutdown. Step S520 and system resource release step S530 are performed. If the result of determining whether the data delivery system 100 ends is terminated, the signal processing thread 160 records in the file that the data delivery system 100 ends (S520). The signal processing thread 160 which recorded the end of the data delivery system 100 in the file returns the work that each of the inquiry thread 120 and the plurality of work processing threads 130 are performing before the execution, and the use that each has acquired. Each authority terminates after returning the authority, and thus, all system resources are released by ending itself (S530). The data delivery system 100 then ends.

For reference, the reception signal logging step S512 and the system termination logging step S520 of the signal processing thread 160 may or may not be performed by an administrator.

Although the present invention has been described in more detail with reference to the examples, the present invention is not necessarily limited to these embodiments, and various modifications can be made without departing from the spirit of the present invention. Therefore, the embodiments disclosed in the present invention are not intended to limit the technical idea of the present invention but to describe the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The protection scope of the present invention should be interpreted by the claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of the present invention.

1 is a diagram conceptually illustrating a data delivery system according to an embodiment of the present invention.

2 is a view sequentially illustrating a data delivery process of a data delivery system according to an embodiment of the present invention.

3 is a view sequentially showing the operation of the inquiry thread of the data delivery system according to an embodiment of the present invention.

4 is a view sequentially showing the operation of each of the plurality of business processing thread of the data delivery system according to an embodiment of the present invention.

5 is a view sequentially showing the operation of the signal processing thread of the data delivery system according to an embodiment of the present invention.

Explanation of symbols on the main parts of the drawings

1: Accounting System

2: information system

10: first storage medium

20: second storage medium

100: data delivery system

110: local queue

120: lookup thread

130: task processing thread

140: first storage medium mutex

150: local cue mutex

160: signal processing thread

Claims (10)

A data delivery system for inquiring data from a first storage medium of an accounting system and reflecting the data to a second storage medium of an information system. A local queue for temporarily storing data selected from the first storage medium; An inquiry thread for inquiring data from the first storage medium, and temporarily storing the inquired data by pushing it to the local queue; A plurality of work processing threads for popping data from the local queue, reflecting the popped data to the second storage medium, and deleting from the first storage medium; A first storage medium controlling the contention of the query thread and the plurality of business process threads for the first storage medium so that only one of the query thread and the plurality of business process threads uses the first storage medium; Mutex; A local queue mutex that controls use contention of the query thread and the plurality of business process threads for the local queue so that only one of the query thread and the plurality of business process threads uses the first local queue; Data delivery system, characterized in that configured to include. The method according to claim 1, The data delivery system, And a signal processing thread for managing all signals generated while inquiring data from the first storage medium and reflecting the data to the second storage medium. When the signal processing thread abnormally terminates the process executed in the data delivery system or the data delivery system, the signal processing thread records an abnormal termination of the process executed in the data delivery system or the data delivery system in a file, When the inquiry thread and each of the plurality of business processing threads return the work performed before the execution (Rollback), return the usage rights acquired by each end, terminate each of them, and terminate the signal processing thread itself. Data delivery system characterized by releasing all system resources for normal operation. A data transfer method of a data delivery system in which data is retrieved from a first storage medium of an accounting system and reflected to a second storage medium of an information system. A data inquiry step of causing a inquiry thread to select data from the first storage medium; A data pushing step of causing the inquiry thread to push the data queried from the first storage medium to a local queue; Popping data by one of the plurality of business processing threads to pop data from the local queue; A data reflection and deletion step of one of the plurality of business processing threads reflecting data popped from the local queue to the second storage medium and deleting from the first storage medium; A data delivery method of a data delivery system, comprising: performing. The method of claim 3, The inquiry thread, Perform the data inquiry step, Repeating the data pushing step until all data inquired from the first storage medium in the data inquiry step is pushed to the local queue, When the business processing of all data inquired from the first storage medium is completed in the data inquiry step, the data inquiry step is executed again. Each of the plurality of business processing threads, Perform the data pop step, If there is data popped from the local queue in the data pop step, the data reflection and deletion step are performed, and the data pop step is performed again. And if there is no data popped from the local queue in the data pop step, performing the data pop step again. The method according to claim 4, The data delivery method of the data delivery system, While the data inquiry step of the inquiry thread is executed, the data reflection and deletion step of each of the plurality of business process threads is processed to be stopped; Reflecting and deleting the data of the data inquiry step of the inquiry thread and the remaining work processing threads of the plurality of work processing threads while the data reflection and deletion of one of the work processing threads of the plurality of work processing threads are performed. Process the step to stop, Process the data popping step of each of the plurality of business processing threads to be suspended while the data pushing step of the inquiry thread is performed, The data pushing step of the inquiry thread and the data popping step of each of the remaining work processing threads of the plurality of work processing threads are stopped while the data popping step of one of the plurality of work processing threads is performed. Data delivery method of a data delivery system, characterized in that the processing. The method of claim 3, wherein The data inquiry step, An inquiry authority obtaining step of obtaining, by the inquiry thread, a usage right for the first storage medium; An inquiry step of the inquiry thread for inquiring data from the first storage medium; An inquiry authority return step of the inquiry thread returning a use authority for the first storage medium; A data delivery method of a data delivery system, comprising: performing. The method of claim 3, The data push step, Obtaining, by the inquiry thread, permission to use the local queue; Pushing by the inquiry thread to the local queue data retrieved from the first storage medium in the data inquiry step; A push permission return step wherein the lookup thread returns usage rights for the local queue; Data delivery method of a data delivery system comprising a. The method of claim 3, The data pop step, A pop authority acquiring step, wherein one task thread among the plurality of task threads acquires a use right for the local queue; Popping, by one of the plurality of task threads, a task thread to pop data from the local queue; A pop authority return step of one task thread of the plurality of task threads returning usage rights for the local queue; A data delivery method of a data delivery system, comprising: performing. The method of claim 3, The data reflection and deletion step, A deleting authority obtaining step of obtaining, by one of the plurality of business processing threads, the processing right of the first storage medium; A reflection and deletion step of one of the plurality of business processing threads reflecting data popped out of the local queue in the data popping step to the second storage medium and deleting from the first storage medium; A deletion authority returning step of returning a use right for the first storage medium by one of the plurality of work processing threads; A data delivery method of a data delivery system, comprising: performing. The method according to any one of claims 3 to 9, The data delivery method of the data delivery system, A signal management step in which a signal processing thread manages all signals generated while inquiring data from the first storage medium and reflecting the data to the second storage medium; When the data delivery system or the process executed in the data delivery system abnormally terminates, the abnormal termination of the data delivery system or the process executed in the data delivery system is recorded in a file, and the inquiry thread and the plurality of processes are executed. Roll back the work performed by each of the task processing threads before returning it, return the usage rights acquired by each one, terminate each other, and terminate the signal processing thread itself to resume normal operation upon restart. Releasing system resources to release system resources; A data delivery method of a data delivery system, comprising: performing.

Images