Page tree
Skip to end of metadata
Go to start of metadata



Replication tool distribution Package

Replication tool works on the following platforms: Windows (x64): Win7, Win8, Windows Server 2008, Windows Server 2012; Linux (x64): CentOS7, Ubuntu 16.04.

The distribution package of the Replication Tool is ZIP-archive for Windows and ZIP- archive for Linux containing the following files:

Windows

Script

Purpose

bin/admintool.batruns the admin tool mode
bin/b2b_replication.exeapplication file
bin/client.batruns replication client
bin/client.service.install.batinstalls the replication tool as a Windows service in client mode
bin/client.service.run.batruns the replication tool as a Windows service in client mode
bin/client.service.stop.batstops the replication tool as a Windows service in client mode

bin/client.service.uninstall.bat

uninstalls the replication tool as a Windows service in client mode
bin/server.batruns replication server

bin/server.service.install.bat

installs the replication tool as a Windows service in server mode

bin/server.service.run.bat

runs the replication tool as a Windows service in server mode
bin/server.service.stop.batstops the replication tool as a Windows service in server mode

bin/server.service.uninstall.bat

uninstalls the replication tool as a Windows service in server mode
bin/standalone.batruns the standalone mode
bin/replication.propertiesproperties file
doc/Replication tool.docxinstructions file

Linux

Script

Purpose

bin/admintool.shruns the admin tool mode
bin/b2b_replicationapplication file
bin/server.shruns replication server
bin/client.shruns replication client
bin/standalone.shruns the srtandalone mode
bin/linux_replication.propertiesproperties file
doc/Replication tool.docxinstructions file


After the first launch of the replication tool the following files will appear in the setup folder:

  • b2b_replication.pid - contains a process identifier, it is used by replication tool control scripts
  • persistent.properties - stores statuses of FIX sessions being replicated
  • replication.log - replication tool log file

FIX Antenna based application settings

For correct usage of the Replication tool, the user must set the several properties of the current FIX Antenna based application.

The settings for the FIX Antenna C++ based application

Property NameProhibited Value(s)Allowed Value(s)
StorageType 

transient

splitPersistent

null

Persistent

PersistentMM

MessageStorage.TimestampUnit

microsecond

nanosecond

millisecond
LogIncomingMessages falsetrue

The settings for the FIX Antenna Java based application

Property NameProhibited Value(s)Allowed Value(s)
storageFactory

SlicedFileStorageFactory

InMemoryStorageFactory

FilesystemStorageFactory

MMFStorageFactory

incomingStorageIndexedfalsetrue
outgoingStorageIndexedfalsetrue
timestampsInLogsfalsetrue

Resetting of sequence numbers in the FIX Antenna Java's session is not supportable. A new session must be created instead.

Installation


RT supports two main working modes: 

  • Client-server mode allows to synchronize  files between primary and back up the server(s) in real time
  • Standalone mode allows copying files on the same machine in real time

A detailed description of the setup process for each mode is given below.

For the Windows operating system

Client-Server Mode 

A client-server mode is used in the case when there is a need to replicate data to a different host(s).

The corresponding installation process is described below.

Configure server instance of the replication tool on the host where the primary files are created:

  • Unzip distribution package into the home directory of the replication tool.
  • Make the following changes in the "Server configuration" section of the replication.properties  configuration file: 
    • Set replication.server.port where the server will listen to connections from clients. Make sure the port is open for external connections on your firewall.
    • Set replication.server.login and replication.server.password. Make sure you use the same values when configuring client.
    • Define the location of logs to be replicated (source directory) and change path properties accordingly: 

List aliases of the logs folders to be replicated in the replication.server.folders property. 
If you replicate one directory you can leave this property empty.

Set the default path to the source logs directory in the replication.server.folder.default.path property. 
If you replicate one directory, use it here. If you replicate several directories, use one of them here.

Set path to each directory being replicated in the corresponding replication.server.folder.AAA.path property, where AAA is the directory alias from the replication.server.folders property.
If you replicate one directory, you can skip this step. The default value set in the  replication.server.folder.default.path property will be used instead.
If you replicate several directories set path to each of them under corresponding alias. 

  • Start the Replication tool in server mode for Windows. 

Start the replication manually. You can use the server.bat script from the bin folder of the distribution package. As well, the command "b2b_replication.exe"  is used to start the replication tool server.

Start the replication as a Windows service. For the installation of the Replication Tool as a Windows service and schedules its automatic launch, the command "b2b_replication.exe --installService -n <ServiceServerName>" should be used or the file "server.service.install.bat". Then the user can start the installed service by using the Windows application service or type the command "%SystemRoot%\system32\net.exe start <ServiceServerName>" or use the file "server.service.run.bat".

  • If the server is started successfully you will see the following message in the console and in the replication.log
Server console
[NOTE] 20141016-10:18:11.460 [7804] [ReplicationServer] - Waiting for incoming connection.
  • Make sure the port is open for external connections on your firewall.
  • Make sure the server is listening to clients on the port specified using the following command:
cmd
C:\B2BITS\replication_tool>netstat -na | find "1090" 
 TCP    0.0.0.0:1090           0.0.0.0:0              LISTENING

Configure client instance(s) of the replication tool on the destination host(s):

  • Unzip distribution package into the home directory of the replication tool.
  • Make the following changes in the "Client Configuration" section of the replication.properties configuration file: 
    • Set replication.client.host and replication.client.port . Make sure you use the same values as for the server replication.server.port property.
    • Set replication.client.login and replication.client.password. Make sure you use the same values as for the server replication.server.login and replication.server.password property.  
    • Define the location of logs to be replicated (source directory) and change path properties accordingly: 

List aliases of the logs folders to be replicated in the replication.client.folders property. 
Folders' aliases should match the ones from the replication.server.folders list from the server configuration file. If the property is empty or not specified, all folders represented by the server are accepted and replicated into the default destination folder.

Set the default path to the source logs directory in the replication.client.folder.default.path property.
If you replicate one directory, use it here. If you replicate several directories, use one of them here.

Set path to each directory being replicated in the corresponding replication.client.folder.AAA.path property, where AAA is the directory alias from replication.client.folder.default.path property.

If you skip this step, the default destination directory will be used for all logs being replicated.

  • Start the replication tool in client mode for Windows. 

    Start the replication manually. You can use the client.bat script from the bin folder of the distribution package. As well, the command "b2b_replication.exe --client"  is used to start the replication tool client.

    Start the replication as a Windows service. For the installation of the Replication Tool as a Windows service and schedules its automatic launch, the command "b2b_replication.exe --installService  -n <ServiceClientName> --serviceStartArgs --client" should be used or the file "client.service.install.bat". Then the user can start the installed service by using the Windows application service or type the command "%SystemRoot%\system32\net.exe start <ServiceClientName>" or use the file "client.service.run.bat".

  • If the client instance(s) is started successfully and set a connection to the server you will see the following message in the console and in the replication.log:
Client console
[NOTE]  20141016-10:35:31.623 [5508] [ReplicationClient] - Connected to server.

Standalone Mode

Standalone mode is a mode when the client (subscriber) and server (publisher) are running within the same process. There is no TCP/IP connection in this mode. Standalone mode is preferable in a case when logs being replicated and copy should be located on the same machine. In order to set up the replication tool you need:

  • Unzip distribution package into the home directory of the replication tool.
  • Define the location of logs to be replicated (source directory). Change server configuration in the replication.properties configuration file accordingly: 

List aliases of the logs folders to be replicated in the replication.server.folders property. 
If you replicate one directory you can leave the property empty.

Set the default path to the source logs directory in the replication.server.folder.default.path property. 
If you replicate one directory, use it here. If you replicate several directories, use one of them here.

Set path to each directory being replicated in the corresponding replication.server.folder.AAA.path property, where AAA is the directory alias from the replication.server.folders property.
If you replicate one directory, you can skip this step. The default value set in the replication.server.folder.default.path property will be used instead.
If you replicate several directories set path to each of them under corresponding alias. 

  • Create directory (or directories) to store logs copy (destination directory(ies)). Change client configuration in the replication.properties configuration file accordingly: 

Set default path to the destination directory in the replication.client.folder.default.path property.

Set destination directory for each source directory in the corresponding replication.client.folder.AAA.path property, where AAA is the directory alias from the replication.server.folders property. If you skip this step, the default destination directory will be used for all logs being replicated. 

  • Start the replication process for Windows.

Start the replication manually. You can use the standalone.bat script from the bin folder of the distribution package. As well, the command "b2b_replication.exe --standalone"  is used to start the replication tool in standalone mode.

Start the replication as a Windows service. For the installation of the Replication Tool as a Windows service and schedules its automatic launch, the command "b2b_replication.exe --installService  -n <ServiceStandaloneName> --serviceStartArgs --standalone" should be used. Then the user can start the installed service by using the Windows application service or type the command "%SystemRoot%\system32\net.exe start <ServiceStandaloneName>".

For the Linux operating system

Client-Server Mode 

A client-server mode is used in the case when there is a need to replicate data to a different host(s).

The corresponding installation process is described below.


Configure server instance of the replication tool on the host where the primary files are created:

  • Unzip distribution package into the home directory of the replication tool.
  • Make the following changes in the "Server configuration" section of the linux_replication.properties configuration file: 
    • Set replication.server.port where the server will listen to connections from clients. Make sure the port is open for external connections on your firewall.
    • Set replication.server.login and replication.server.password. Make sure you use the same values when configuring client.
    • Define the location of logs to be replicated (source directory) and change path properties accordingly: 

List aliases of the logs folders to be replicated in the replication.server.folders property. 
If you replicate one directory you can leave this property empty.

Set the default path to the source logs directory in the replication.server.folder.default.path property. 
If you replicate one directory, use it here. If you replicate several directories, use one of them here.

Set path to each directory being replicated in the corresponding replication.server.folder.AAA.path property, where AAA is the directory alias from the replication.server.folders property.
If you replicate one directory, you can skip this step. The default value set in the  replication.server.folder.default.path property will be used instead.
If you replicate several directories set path to each of them under corresponding alias. 

  • Start the replication tool in server mode for Linux.

Run server.sh to start the replication process or use the command "./b2b_replication --propfile=./linux_replication.properties".

  • If the server is started successfully you will see the following message in the console and in the replication.log
Server console
[NOTE] 20141016-10:18:11.460 [7804] [ReplicationServer] - Waiting for incoming connection.
  • Make sure the port is open for external connections on your firewall.
  • Make sure the server is listening to clients on the port specified using the following command:
cmd
C:\B2BITS\replication_tool>netstat -na | find "1090" 
 TCP    0.0.0.0:1090           0.0.0.0:0              LISTENING

Configure client instance(s) of the replication tool on the destination host(s):

  • Unzip distribution package into the home directory of the replication tool.
  • Make the following changes in the "Client Configuration" section of the linux_replication.properties configuration file: 
    • Set replication.client.host and replication.client.port . Make sure you use the same values as for the server replication.server.port property.
    • Set replication.client.login and replication.client.password. Make sure you use the same values as for the server replication.server.login and replication.server.password property.  
    • Define the location of logs to be replicated (source directory) and change path properties accordingly: 

List aliases of the logs folders to be replicated in the replication.client.folders property. 
Folders' aliases should match the ones from the replication.server.folders list from the server configuration file. If the property is empty or not specified, all folders represented by the server are accepted and replicated into default destination folder.

Set the default path to the source logs directory in the replication.client.folder.default.path property.
If you replicate one directory, use it here. If you replicate several directories, use one of them here.

Set path to each directory being replicated in the corresponding replication.client.folder.AAA.path property, where AAA is the directory alias from replication.client.folder.default.path property.

If you skip this step, the default destination directory will be used for all logs being replicated.

  • Start the replication tool in client mode for Linux.

Run client.sh to start the replication process or use the command "./b2b_replication --client --propfile=./linux_replication.properties".

  • If the client instance(s) is started successfully and set a connection to the server you will see the following message in the console and in the replication.log:
Client console
[NOTE]  20141016-10:35:31.623 [5508] [ReplicationClient] - Connected to server.

Standalone Mode

Standalone mode is a mode when the client (subscriber) and server (publisher) are running within the same process. There is no TCP/IP connection in this mode. Standalone mode is preferable in a case when logs being replicated and copy should be located on the same machine. In order to set up the replication tool you need:

  • Unzip distribution package into the home directory of the replication tool.
  • Define the location of logs to be replicated (source directory). Change server configuration in the linux_replication.properties configuration file accordingly: 

List aliases of the logs folders to be replicated in the replication.server.folders property. 
If you replicate one directory you can leave the property empty.

Set the default path to the source logs directory in the replication.server.folder.default.path property. 
If you replicate one directory, use it here. If you replicate several directories, use one of them here.

Set path to each directory being replicated in the corresponding replication.server.folder.AAA.path property, where AAA is the directory alias from the replication.server.folders property.
If you replicate one directory, you can skip this step. The default value set in the replication.server.folder.default.path property will be used instead.
If you replicate several directories set path to each of them under corresponding alias. 

  • Create directory (or directories) to store logs copy (destination directory(ies)). Change client configuration in the replication.properties configuration file accordingly: 

Set default path to the destination directory in the replication.client.folder.default.path property.

Set destination directory for each source directory in the corresponding replication.client.folder.AAA.path property, where AAA is the directory alias from the replication.server.folders property. If you skip this step, the default destination directory will be used for all logs being replicated. 

  • Start the replication process for Linux.

Start the standalone.sh or use the command "b2b_replication --standalone --propfile=./linux_replication.properties" to start replication process.

       

Properties description

Property

Is Required

Default Value Description

Server configuration section



The section is used in Standalone mode and Client-Server mode on the server-side.
replication.server.portY1090Server listen port.
replication.server.passwordY-A password that must be used by the client to be able to login to the server.
replication.server.loginY-A client's login that must be used by the client to be able to login to the server.
replication.server.foldersN-

A comma-separated list of aliases of folders to be monitored.

If not specified or empty, default settings are used. If not empty "replication.server.folder.AAA.path" property for each folder from the list should be specified, where "AAA" is the folder alias.

replication.server.folder.default.recursiveYtrue

If true then sub-folders are recursively added to the monitor list for replication.

If false then only files from the folder itself are replicated.

replication.server.folder.default.pathN-The default path to a folder to be monitored.
replication.server.folder.default.maxItemsPerUpdateY100

A maximum number of log records that can be transferred in one message for this folder.
Increasing this value may increase throughput but decrease response time and vice-versa.

replication.server.folder.default.filterN.*

Used only if replication.server.folder.default.recursive = true.

FIX session logs are added recursively to the monitoring list if the relative path matches this regexp. If not specified all FIX session logs are added. Please find further information.

replication.server.folder.AAA.recursiveN-

If true then all sub-folders of the folder AAA are recursively added to the monitor list for replication.

If false then only files from the folder itself are replicated.

If not specified, replication.server.folder.default.recursive value is used for the folder.

replication.server.folder.AAA.pathRequired if alias AAA is specified in the replication.server.folders property-Path to the monitored folder with alias AAA
replication.server.folder.AAA.maxItemsPerUpdate

A maximum number of log records that can be transferred in one message for this folder.
If not specified, replication.server.folder.default.maxItemsPerUpdate value is used for the folder.

replication.server.folder.AAA.filterN-

Used only if replication.server.folder.AAA.recursive = true or if replication.server.folder.AAA.recursive is not specified and replication.server.folder.default.recursive = true.

Sub-folders of the folder AAA are added recursively to the monitoring list if the relative path matches this regexp. If not specified all sub-folders are added. Please find further information.

 replication.server.timeoutMs N10000  Time interval of milliseconds from the connection to the receiving invitation message from the client.
 replication.server.filePollingIntervalM N 1Files poll interval. Server checks for new records in logs on this interval, milliseconds.
 


replication.server.foldersPollIntervalS
 N 10Folders poll interval. Server checks for folders' changes in this interval.

It is actual for *nix systems if the filesystem doesn't support Inotify functionality,

Otherwise and on the Windows platform server uses a notification mechanism to work on demand.

The value is in seconds.

 

replication.server.confsPollIntervalS

 N 10Conf files poll interval. Server checks for modification of .conf file on this interval, seconds.
Client configuration section


The section is used in Standalone mode and Client-Server mode on the client-side.
replication.client.hostY-IP address or host name to connect.
replication.client.portY-Port to connect. It should be the same as replication.server.port value from the server configuration file.
replication.client.loginY-Client login. It should be the same as replication.server.login value from the server configuration file.
replication.client.passwordY-Password. It should be the same as replication.server.password value from the server configuration file.

replication.client.folders

N-

A comma-separated list of aliases of folders to be accepted.

Folders' aliases should match the ones from the replication.server.folders list from the server configuration file.

The client ignores any folder represented by the server if their alias is not listed here, except the case when the property is empty or not specified at all. In this case, all folders represented by the server are accepted and replicated into the default destination folder.

replication.client.folder.default.pathN-Default destination folder path.
replication.client.folder.default.filterN.*

Replicated FIX session logs filter. If specified only FIX session logs from this folder and all sub-folders that correspond to the regexp are accepted.

If not specified all FIX session logs represented by the server are accepted by the client. Please find further information.

replication.client.folder.default.recursiveNtrue

If it is true client accepts sub-folders of the folder recursively.

replication.client.folder.AAA.path Required if alias AAA is specified in the replication.client.folders property

Path to store folder with alias AAA

 replication.client.timeoutMs N 10000 Timeout for reconnect try
 

replication.client.foldersPollIntervalS

 N 10 This value overrides the same value in server configuration.
 

replication.client.confsPollIntervalS

 N 10 This value overrides the same value in server configuration.
 

replication.client.heartBeatIntervalS

 5

Heartbeat interval. This is heartbeat interval used in TCP/IP communication (non-standalone mode) to detect connection break.

The value is in seconds.

 

replication.client.postStatsIntervalM

 N 5

Statistics post interval. Client posts statistics information into the log on this interval.

Setting this value to '0' disables statistics posting. This value is in minutes.

 replication.client.folder.default.maxItemsPerUpdate N 100 This value overrides the same value in server configuration.
Admintool configuration section

This section is used in Admintool and Client mode.

replication.admintool.host


Y-

IP address or hostname to connect.

 Note: Admintool connects to client instance, not server one.

replication.admintool.portY-

For Client mode: port to open listener for administrative commands from Admintool.

For Admintool mode: port to connect.

replication.admintool.login

Y-

For Client mode: admintool login which must be used by admintool to be able to login to the client.

For Admintool mode: admintool login.

replication.admintool.password

Y-

For Client mode: admintool password which must be used by admintool to be able to login to the client.

For Admintool mode: admintool password.

replication.admintool.heartBeatIntervalS

 N 50 This value has the same meaning as for client
Logger configuration section

This section is used for all modes.

Log.File.RootDir

Y./
Log.DeviceY-

Target device. Supported values are:

  • File
  • Console
  • File Console
Log.DebugIsOnYfalseTurns on/off logging on a certain level.
Log.NoteIsOnYfalseTurns on/off logging on a certain level.
Log.WarnIsOnYfalseTurns on/off logging on a certain level.
Log.ErrorIsOnYfalseTurns on/off logging on a certain level.
Log.FatalIsOnYfalseTurns on/off logging on a certain level.
Log.CyclingY-Turns cycling on/off.
Log.File.NameY-Log file name.
Log.File.Recreate

Y-

If true then file will be recreated on each start.
If false then new records will be appended to the existent file.

Log.File.AutoFlushYtrue

If set to true then the buffer will be flushed after each logging call.
If set to false then flush is not called.
Setting to true decreases program performance; setting to false increases risk of records loss in case of program failure.


Command Line Options

Command

Description

-h [ --help ] 

Displays the help message.
-p [ --pidfile ] arg

Specifies pid file to use.

The default value is b2b_replication.pid.

-c [–propfile] arg

Specifies configuration file to use.

The default value is replication.properties.

-s [--client]

Starts tool as a client (subscriber).

-a [--standalone]

Starts tool in standalone mode when the client (subscriber) and server (publisher) are running within the same process.

-t [ --admintool ]Starts tool as admin tool.
--persistentfile arg

Specifies a persistent properties file. This file is used to store folders’ states and is applicable to client and standalone mode only.

The default value is persistent.properties.

-l [ --nologo ] 

Tells the tool to avoid showing startup banner. It is useful, for example, in admintool mode if further output processing is used.

--admintoolCommand arg

Specifies admintool command to execute in admintool mode. Commands supported: 'list', 'stop', 'start', 'isstopped'. The default is 'list'.

--admintollCommandArg argSpecifies argument(s) for admintoolCommand. This option can be used more than once if several arguments need to be passed.
--admintoolCommand start --admintoolCommandArg arg1

Starts previously stopped folder replication. Arguments:

  • arg1: folder tag - required.
--admintoolCommand stop --admintoolCommandArg arg1 --admintollCommandArg arg2

Stops folder replication. Arguments:

  • arg1: folder tag - required
  • arg2: stop type:
    • regular - stops folder immediately
    • gracefully - waits until no more data is available to replicate and then stops. If there is an attempt to stop the folder that is already waiting to stop than it joins the wait. Default value.
    • force - stops immediately even if there a graceful stop is in progress. First of all, press the "Ctrl" and "C" keys at the same time to end the graceful stopping command.
--admintoolCommand isstopped --admintoolCommandArg arg1

Displays “true” if the folder is stopped or “false” otherwise. Arguments:

  • arg1: folder tag
--admintoolCommand listLists all folders with their state and message count.

Notes:

  • Replication tool acts as a server when neither client nor standalone mode are chosen. The server mode is the default.
  • Replication tool does not permit to use more than one of “--client”, “--standalone” or “--admintool” option at the same time but if it is the case, the priority is the following:
    • 1 - “–client”
    • 2 - “–standalone”
    • 3 - “–admintool”


Specific commands to configure Replication tool as Windows service 
-i [--installService]Installs the tool as a Windows service.

-u [--uninstallService]

Uninstalls Windows service installed for the tool.
-n [--serviceName] argSpecifies service name to use for --installService and --uninstallService commands. The default value is “ReplicationService”.
-d [--dependService] argUsed with “–installService”, specifies service the service being installed depends on. Can be used more than once if more than one service must be added to the dependency list.
--serviceStartArgs argUsed with “–installService”, specifies command line options to be passed when service being installed is started by Windows Service Manage.

The user must run service commands as a system administrator

Admin tool

Admin tool is the utility to easily monitor and control the replication process. It allows to change the replication folder's configuration by using several commands instead of configuring properties files.

Configuration:

For Window operating system

Admin tool is used to connect to the client and control the replication process remotely using simple command-line instructions. In order to use replication tool in the administrative mode you need:

  1. Set admintool parameters in the Admintool configuration section of the replication.properties/replication.client.properties configuration file on the client's side:
    1. Set replication.admintool.port
    2. Set replication.admintool.login and replication.admintool.password.
  2. Set admintool parameters in the Admintool configuration section of the configuration file on the admintool's side: 
    1. Set replication.admintool.host and replication.admintool.port. Make sure you use the same values as for the client's replication.admintool.port.
    2. Set replication.admintool.login and replication.admintool.password. Make sure you use the same values as for the client's replication.admintool.login and replication.admintool.password.
  3. Start replication tool in admintool mode. Run the admintool.bat/ b2b_replication --admintool for this purpose. See Examples for more details.

Note: you can launch admintool in the client's folder with the same configuration file. In this case, they will share the same set of properties in the Admintool configuration section file.

For Linux operating system

Admin tool is used to connect to the client and control the replication process remotely using simple command-line instructions. In order to use replication tool in the administrative mode you need:

  1. Set admintool parameters in the Admintool configuration section of the linux_replication.properties/replication.client.properties configuration file on the client's side:
    1. Set replication.admintool.port
    2. Set replication.admintool.login and replication.admintool.password.
  2. Set admintool parameters in the Admintool configuration section of the configuration file on the admintool's side: 
    1. Set replication.admintool.host and replication.admintool.port. Make sure you use the same values as for the client's replication.admintool.port.
    2. Set replication.admintool.login and replication.admintool.password. Make sure you use the same values as for the client's replication.admintool.login and replication.admintool.password.
  3. Start replication tool in admintool mode. Run the b2b_replication -t [–admintool] for this purpose. See Examples for more details.

Note: you can launch admintool in the client's folder with the same configuration file. In this case, they will share the same set of properties in the Admintool configuration section file.

Admintool Script Usage

There are examples of admin tool commands.

Note: for Linux add the argument "--propfile=./linux_replication.properties".

  1. List all monitored folders:

    cmd
    b2b_replication.exe --admintool --admintoolCommand list
    
    Alternative:
    admintool.bat list
    
  2. Stop replication of the folder FE1 gracefully:

    cmd
    b2b_replication.exe --admintool --admintoolCommand stop --admintoolCommandArg FE1
    
    Alternative:
    admintool.bat stop FE1
    
  3. Start over replication of the folder FE1:

    cmd
    b2b_replication.exe --admintool --admintoolCommand start --admintoolCommandArg FE1
    
    Alternative:
    admintool.bat start FE1
    
  4. Check if replication of the folder is stopped:

    cmd
    b2b_replication.exe --admintool --admintoolCommand isstopped --admintoolCommandArg FE1
    
    Alternative:
    admintool.bat isstopped FE1
    
  5. Stop replication of the folder FE1 immediately:

    cmd
    b2b_replication.exe --admintool --admintoolCommand stop --admintoolCommandArg FE1 --admintoolCommandArg regular
    
    Alternative:
    admintool.bat stop FE1 regular
  6. Stop replication of the folder FE1 immediately even though a graceful stop is in progress:

    cmd
    press the "Ctrl" and "C" keys at the same time, then enter the command into the command line:
    b2b_replication.exe --admintool --admintoolCommand stop --admintoolCommandArg FE1 --admintoolCommandArg force
    
    Alternative:
    admintool.bat stop FE1 force
    

Examples

Note: for Linux add the argument "--propfile=./linux_replication.properties".

  1. Start tool in server mode with default properties file:

    cmd
    b2b_replication
    
    Alternative:
    server.bat
  2. Start tool in server mode with custom properties file myreplication.properties:

    cmd
    b2b_replication --propfile=myreplication.properties
    
  3. Start tool in client mode with custom persistent properties file mypersistent.properties:

    cmd
    b2b_replication --client --persistentfile=mypersistent.properties
    
    Alternative:
    client.bat
    
  4. Start tool in standalone mode with the default configuration:

    cmd
    b2b_replication --standalone
    
    Alternative:
    standalone.bat
    
  5. Install Windows service with custom name and two dependencies in standalone mode:

    cmd
    b2b_replication --installService --serviceName=HFTReplication --dependService=Service1 --dependService=Service2 --serviceStartArgs="--standalone"
    
  6. Uninstall Windows service from the example above:

    cmd
    b2b_replication --uninstallService -serviceName=HFTReplication
    
    Alternative:
    server.service.uninstall.bat/ client.service.uninstall.bat
    
  7. Server configuration section
    # Folders list to monitor. It is comma-separated list of folders' tags that server represents to clients.
    # If it is empty or not defined then it is threated in the same way if it value was set to 'default'.
    
    replication.server.folders = hftdma, hftdma2 
    
    # Default folder configuration.It gets in power if no folders are configured.# This configuration values except 'path' are taken for other configurations if particular values are not defined.
    # Folder path. It is path to the working folder for the tag.
    
    replication.server.folder.default.path = D:/replication 
    
    # if the value is true then server looks for all sub-folders recursively and adds them to the monitor list.
    # It uses configuration values for the tag in this case for all sub-folders. Default is 'false'.
    
    replication.server.folder.default.recursive = false 
    
    # folder walk regexp filter. If 'recursive' is true then server walks through
    # sub-folders recursively and adds them if relative path matches this regexp only.
    # If this parameter is not defined then all sub-folders are added.
    #replication.server.folder.default.filter = .* 
  • No labels