...
- Use network attached storage (NAS) to mount a shared file system with containing the workspace that all members of the cluster will readaccess.
- Set up a source control repository (for example, git) that has a checked-in workspace.
- An external process would need to be responsible for pulling in new changes as appropriate to keep cluster members in sync. We recommend using a using
git fetch
or an equivalent command as a post-commit trigger to synchronize sharing.
- An external process would need to be responsible for pulling in new changes as appropriate to keep cluster members in sync. We recommend using a using
Virtualize Configuration
Ensure that the load balancer is configured so that changes are propagated to only one node before configuring Virtualize for load balancing.
WAR, Docker, or Kubernetes
After sharing the workspace (see Workspace Configuration), add start your deployment with the following jvm JVM argument:
-Dparasoft.auto.deploy.new=false
Desktop/Command Line
...
- Share the VirtualAssets project across the cluster. See Workspace Configuration for more information.
- Enable refreshing using native hooks or polling:
- From the GUI:
- Choose Window > Preference > General > Workspace from the Virtualize main menu.
- Enable the Refresh using native hooks or polling option and restart the server.
- From the command line:
- Open the org.eclipse.core.resources.prefs file in the
<WORKSPACE>/.metadata/.plugins/org.eclipse.core.runtime/.settings/
directory. Add the
refresh.enabled=true
property, for example:Code Block eclipse.preferences.version=1 version=1 refresh.enabled=true
Restart the server.
- Open the org.eclipse.core.resources.prefs file in the
- From the GUI:
- Add the following Java option to your startup command on all nodes in the cluster to put the server:
-J-Dparasoft.auto.deploy.new=false
- Restart your servers.
...