Deployment Synchronizer or Dep-Sync is used to synchronize artifacts within nodes in a cluster. This topic provides instructions on how to set up the registry-based deployment synchronizer to sync artifacts within two WSO2 ESB nodes. There are other synchronization methods available in WSO2 servers such as Subversion (SVN)-based deployment synchronizer, but they need third-party software and are a bit hard to configure compared to registry-based deployment synchronizer.
Registry-based deployment synchronizer uses a common registry space to store the deployment artifacts. In this mechanism, the recommended clustering pattern is to have one READ-WRITE product node and the rest are READ-ONLY. Once you deploy an artifact from the READ-WRITE node, the artifacts will be stored in the relevant collection in the configuration registry. The other nodes of the cluster will use the registry checkin-checkout client and checkout the deployment artifacts to their file system. Then with the hot deployment functionality, the artifacts will get deployed in the cluster nodes.
Before doing the actual registry-based deployment synchronizer configurations, we first need to mount ESB's /_system/config collection to a single database. To get a clear idea on registry mounting read this.
...
Configuring the manager node
You configure DepSync in the <PRODUCT_HOME>/repository/conf/carbon.xml file on the manager node by making the following changes in the <DeploymentSynchronizer> tag:
| Code Block | ||
|---|---|---|
| ||
<DeploymentSynchronizer>
<Enabled>true</Enabled>
<AutoCommit>true</AutoCommit>
<AutoCheckout>false</AutoCheckout>
<RepositoryType>registry</RepositoryType>
</DeploymentSynchronizer> |
...