Running the File Collaboration Server (FCS) Synchronization Server

The File Collaboration Server (FCS) Synchronization Server daemon is launched via the ENOFCSSyncServer.bat (Windows) or ENOFCSSyncServer.sh (UNIX) script. This script starts a Java process running. Process behavior is defined by the XML rule file passed (among other arguments) to the starting shell.

The FCS Synchronization Server daemon process should run in a server environment, as it needs to access the connection (bootstrap) file.

You can monitor synchronization server daemon activity in the generated logs. See the -logPath and -logSize arguments below.

System administrator privileges are required to run the FCS Synchronization Server.

This task shows you how to:

Run the FCS Synchronization Server on Windows

To run the FCS Synchronization Server on Windows:

  1. Change to the installation folder: SERVER_INSTALL\OS\code\bin\
  2. Run the following command with the appropriate command-line parameters (see FCS Synchronization Server Parameters):

    ENOFCSSyncServer.bat

FCS Startup Script Sample Code (Windows)

The following is sample code for the ENOFCSSyncServer script on Windows. You will need to change the variables in the sample code to match your setup/environment:

CSR\OS\code\bin\ENOFCSSyncServer.bat
-user EV6ADM 
-password EV6PASSWD
-maxRetries 5
-maxSyncRunnerThreads 10
-rulesCheckSecondElapse 10
-ruleFiles E:\PATH_TO_RULES_FILE\rules.xml

A dedicated logger (name: FCS.FCSSyncDaemon) must be configured in the logback.xml file in order to enable FCS Sync Server logs.

Example with a logpath “/tmp/” and logSize “50MB”:

<appender name="ROLLING-FCSSyncDaemon" class="ch.qos.logback.core.rolling.RollingFileAppender">
    <file>/tmp/fcssyncd0.out</file>

    <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">
      <fileNamePattern>/tmp/fcssyncd%i.out</fileNamePattern>
      <minIndex>1</minIndex>
      <maxIndex>2</maxIndex>
    </rollingPolicy>

    <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">
      <maxFileSize>50MB</maxFileSize>
    </triggeringPolicy>
    <encoder>
      <pattern>
[%d{yyyy-MM-dd HH:mm:ss.SSS,GMT} GMT - %logger{64} - [%thread] - %-5level]: %msg%n 
      </pattern>
    </encoder>
</appender>

<logger name=" FCS.FCSSyncDaemon " level="INFO" additivity="false">
                <appender-ref ref="ROLLING-FCSSyncDaemon" />
</logger>
Note: The logger name for FCS Sync Server is FCS.FCSSyncDaemon for R2020x and higher releases.

To avoid mismatches with other processes such as Tomee, use a dedicated logback.xml file for the FCS Sync Server:

Copy the original logback.xml file and rename it as fcssyncserver_logback.xml for example.

Before launching the bat ENOFCSSyncServer.(bat/sh), set the variable below in order to provide logback code infrastructure where to find the configuration file:

Windows example: set MXMRUN_JAVAOPTS=-Dlogback.configurationFile=logback_conf_file_path\fcssyncserver_logback.xml

Unix example: export MXMRUN_JAVAOPTS=-Dlogback.configurationFile=logback_conf_file_path/fcssyncserver_logback.xml

Run the FCS Synchronization Server on UNIX

To run the FCS Synchronization Server on UNIX/Linux:

  1. Change to the installation folder: SERVERHOME/scripts/
  2. Run the following command with the appropriate command-line parameters (see FCS Synchronization Server Parameters): 

    ENOFCSSyncServer.sh

FCS Startup Script Sample Code (Unix)

The following is sample code for the ENOFCSSyncServer script on Unix. You will need to change the variables in the sample code to match your setup/environment:

CSR/scripts/ENOFCSSyncServer.sh 
-user EV6ADM 
-password EV6PASSWD 
-maxRetries 5 
-maxSyncRunnerThreads 10 
-rulesCheckSecondElapse 10 
-ruleFiles /PATH_TO_RULES_FILE/rules.xml