Publishing Messages from Data Synchronization

More and more JumpMind is enhancing SymmetricDS with new data integration features that leverage SymmetricDS’s Change Data Capture capabilities for replication, synchronization, and transformation of data from one system to another. In this article, we will cover how to use the data replication server to map data into a JMS message destination, which could be part of an enterprise strategy for SOA Data Integration and Messaging.

Within the next month we be releasing a simple and flexible data mapping and transformation feature in 2.4. Later, towards the end of the summer, we will be making a foray in the mobile world with a new 3.0 client that runs on Android devices.

While we are hard at work expanding the feature set of SymmetricDS, one of the hardened mainstays that has been very handy for integrating with other systems has been our messaging extension point.

Out the box, an extension point can be configured in XML to publish an XML representation to any number of messaging providers. A JMS (Java Message Service) connector can be used via configuration. Other messaging subsystems can be published to by implementing a very simple interface that receives the message to be published. If you have a messaging system that you would like to integrate SymmetricDS with, contact us and we might just add support.

Messages can be published from two different points in the SymmetricDS architecture.

1 – Messages can be published from the source node, after data is captured in the process of routing the data. You might want to use this scenario if you want to use SymmetricDS solely as a tool to capture and publish changes.

2 – Messages can also be published at the target node during the process of data loading. You might want to use this scenario if you are trickling data from a multitude of remote nodes into one central repository and you need to integrate data to other systems.