Synchronous application of heterogeneous database based on Windows service

With the development and application of electronic information, each unit of each enterprise has developed and applied its own information system. Different development technologies and back-end databases are used between the units, and they are separate and not related. Enterprise integration can not only create a three (presentation layer, business layer, data access layer) layer application structure, but also can make an application distributed to multiple computers. In a distributed application, a single layer cannot be run on its own, and each application in an integrated application can run independently, and their time is accomplished by coupling. Asynchronous messaging architecture to integrate multiple applications, synchronization of heterogeneous databases is a problem that needs to be solved in real projects

1 System Requirements

The main task of electronic data interchange is to realize the data exchange and system integration between different systems and different services, the following figure is the distribution diagram of each system in a real project (Figure 1), each system is independent of each other, using different database. First, the enterprise through a one-stop declaration platform declaration information to the customs by the Customs for the approval of the work, if the customs approval, the corresponding enterprise information status is changed, and then the enterprise to send vehicle information to the Logistics Park station system, the station system received the customs end of the The line information and the vehicle information sent by the enterprise are carried out by the vehicle through the release work.

Figure 1

Figure 2

The entire system is through their own independent Windows services to monitor their own database, the corresponding table changes after the creation of the changed XML message, through the routing of MQ Message queue to send the message to the receiver, the receiving service received the MQ message, The received XML message parsing is entered into the receiving End database. Each message definition is accomplished using a schema definition, and only the reporting wisdom that conform to the schema rule definition can enter message queues for transmission. For example, the customer relationship schema message definition (Figure 2) shows that only the wisdom of the schema format can generate an XML message for transmission.