Replication HowTo

This Wiki is read-only for reference purposes to avoid broken links.

Summary

In this page, I will walk through the steps to deploy replication on ADempiere.

Overview

I am trying to achieve a basic scenario where customers and orders captured at a branch or store are replicated to a central store and where changes made at the central store (via a web portal) may be replicated back to the branch or store.

Discovering Replication Terms

The Type of data Replication determines the direction of the data replication.

• Reference means that the data in this system is read only
• Local means that the data in this system is not replicated to other systems
• Merge means that the data in this system is synchronised with the other system

Apache ActiveMQ

Apache ActiveMQ handles the replication. You can find out more about the project here: http://activemq.apache.org

Role of ActiveMQ

ActiveMQ resides on the server you export from (in order to ensure there is no communication link failure between the export system and this application. ADempiere exports changes to records as defined by you when these records are change by capturing the change via a special model validator and then sending xml as defined by you to the ActiveMQ server. The ActiveMQ server then keeps hold of the change records and provides them to any authorised client that listens to the specific topic. If the clients link fails, ActiveMQ keeps the change message until the client's connection is restored to the ActiveMQ server.

Configuring ActiveMQ

Please follow the instructions on the ActiveMQ website. I used ActiveMQ v 5.2.0.