Synchronizing Captured Stores

Synchronization ensures that users access the latest versions of files when checking out or viewing files in a replicated store environment.

The following topics are discussed:

Related Topics
FCS Compressed Synchronization

Synchronization Methods

Synchronization occurs in one of two ways:


  • ENOVIA Live Collaboration automatically synchronizes files for a user's preferred location during checkout and open for viewing operations.
  • System Administrators can use MQL commands to synchronize files for a business object or for a store to ensure that all locations contain the most recent copy of the files.

For complete details on synchronization, see the chapter "Building the System Basics" in the MQL Guide.

Automatic Synchronization

Synchronization occurs automatically when a user checks out or opens a file for viewing and the file at the user's preferred location is not the latest version. In such a case, ENOVIA Live Collaboration copies the latest version of the file to the user's preferred location and then checks out or opens the local file.

Manual Synchronization

In order to publish newly checked-in files to other locations associated with the store, System Administrators must use the MQL sync command against either the business object or the store. For details, see the chapter "Building the System Basics" in the MQL Guide.

Proxy Server for FCS Synchronization

A proxy server may be setup for FCS synchronization operations where file transfers occur between locations inside and outside of ENOVIA Live Collaboration. Proxy servers allow firewalls to be passed more easily and are especially important for companies that exchange data between divisions and subsidiaries or with partners and clients.

All FCS synchronization operations use HTTP protocol (FTP is no longer used) to handle file transfers. A proxy server setup requires that all the nodes are able to communicate with each other over HTTP.

To setup a proxy server, configure the ENOVIA File Collaboration Server as a proxy by adding the "-Dhttp.proxyHost=proxyHost" and "-Dhttp.proxyPort=proxyPort" options to mxEnv.sh or the application server startup script JAVA_OPTIONS environment variable. For the MQL client, add them to MX_JAVA_OPTIONS in the enovia.ini file for the ENOVIA Studio Modeling Platform or startup script for UNIX.

For example:

MX_JAVA_OPTIONS="-Xss512k -Xms640m -Xmx640m -Dmatrix.debug=true 
-Dhttp.proxyHost=Host -Dhttp.proxyPort=Port" 

JAVA_OPTIONS="${MX_JAVA_OPTIONS}"

For HTTPS, use https.proxyHost and https.proxyPort.

ENOVIA Live Collaboration Server currently does not support HTTP authentication on client side proxies.