Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

Described below is how to configure Deployment Synchronizer (DepSync) for a WSO2 product cluster using two cluster nodes (manager, and one worker) with a shared registry (WSO2 Governance Registry). For information on clustering, refer to section Clustered Distributed Deployment.

SVN-based deployment synchronizer uses a Subversion repository as the central repository to sync the contents in the sync directory (by default the axis2 repo directory <PRODUCT_HOME>/repository/deployment/server). This method is efficient and transparent to the user. In SVN-based DepSync, when changes to the contents of axis2 repo directory are made, the Read-Write nodes commit those to the Subversion (central) repository. Then, this node sends an Axis2 cluster message to all other (worker) nodes specifying that the repo is updated. When the slave nodes receive the message, they update their axis2 repo directory with what is in the svn repository.

...