Deployment Synchronizer provides capability to synchronize deployment artifacts across the nodes of a product cluster. The artifact
A product's repository typically contains user-uploaded service archives, modules, service metadata, scheduled tasks etc. which These artifacts are typically shared across the multiples nodes of in a cluster. Therefore, in a clustered environment, the artifact repository of (in WSO2 products (, by default, it is <product-home>/repository/deployment/server) should be in-sync between all the cluster nodes, in order to maintain consistency. This is synchronization functionality is provided by the following feature in the WSO2 feature repository:
...
If it is not included in your product by default, you can add by installing the above feature using the instructions given in section, Feature Management.
In summary, the WSO2 deployment synchronizer has a number of Deployment Synchronizer has the following use cases:
- Maintaining an up-to-date backup of the artifact repository.
- Sharing a single artifact repository among multiple servers in a cluster.
- Enforcing artifact updates to be deployed on a server at runtime.
Currently, The the WSO2 Deployment Synchronizer feature (DepSync) uses an SVN-based repository for storing shared deployment artifacts. The Subversion repository is used to sync the contents in the sync directory (the axis2 repo directory, <PRODUCT_HOME>/repository/deployment/server, by default). This method is efficient and high-performant. The synchronization process is as follows:
...