This documentation is for WSO2 Enterprise Integrator version 6.1.1 . View documentation for the latest release in the 6.x.x family and the latest release in the 7.x.x family.

All docs This doc

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • For a high rate of changes (i.e., if changes happen very frequently):
    -  network file shareNetwork File Share (NFS)
  • For a medium rate of change
    -  rsyncRemote Synchronization (Rsync)
  • For a low rate of changes (i.e., if changes happen once a week):
    - use the configuration management system to handle artifactartifacts
    - other deployment options (e.g., Puppet, Chef etc.)

However, using a shared file system is the first preference that WSO2 recommends to synchronize the artifacts among the nodes, because you can publish synapse artifacts to any of the nodes, avoiding the vulnerability of a single point of failure that is present when using remote synchronization (rsync). 



Using Network File Share (NFS)

You can use a common shared file system such as Network File System (NFS) or any other shared file system that is available to configure a shared file system as the content synchronization mechanism. You need to mount the <API-M_HOME>/repository/deployment/server directory of the two nodes to the shared file system to share all the artifacts between all the nodes. 

Using Remote Synchronization (Rsync)

Another common approach for synchronizing artifacts across all cluster nodes is to use rsync tool, which is a file copying tool. Therefore, you can first deploy artifacts in one node of the cluster and then  use rsync to copy those artifacts to other nodes as described below.